Configuring the Ops Center Converged Core Naming Convention Support

This section describes a sample CLI command configuration for configuring the feature.

ops-centers smf data
  app-name-override       cn
  repository-local        smfi25
  sync-default-repository true
  netconf-ip              209.165.200.224
  netconf-port            2026
  ssh-ip                  209.165.200.224
  ssh-port                2028
  ingress-hostname        209.165.200.224.nip.io
  initial-boot-parameters use-volume-claims false
  initial-boot-parameters first-boot-password $8$5WnH/gUgKtPAPfXdU8CaURcKnaQOAc9imkIBHnjZLM=
  initial-boot-parameters auto-deploy true
  initial-boot-parameters single-node true
exit

NOTES:

  • <app-name> : Mention the application name. In the above code sample, it is smf.

  • <instance> : Mention the instance name. In the above code sample, it is data.

  • app-name-override <override_value> : Mention the override value. In the above code sample, it is cn.

To download the ops center packages, the default behavior is to derive the ops center package name as smf-ops-center. In this release, if the app-name-override value is set to 'cn', the new behaviour is to derive the package name as cn-ops-center.

Note

This feature ensures that you keep the existing namespaces, yet use the converged ops center name 'cn' from the override field to ensure backward compatibility for the NF pods, which were deployed in previous releases.