F.1 CNC Console Instances Configuration Examples
The following section lists the CNC Console instances configuration examples for single cluster and multi-cluster deployment of supported NFs.
Note:
- In the following examples, mCnccIams port is assumed as "80". The mCnccIams port configuration must be added only if port is other than "80".
- To enable cnDBTier menu for NFs, see the NF Instance Configuration With cnDBTier Menu Enabled section.
Note:
For OCI:- To deploy CNC Console on OCI, in all the below mentioned sample
configurations for various deployments, ensure setting the cncc-iam.enabled flag to
false and oci-iam.enabled flag to
true..
global: oci-iam: enabled: true cncc-iam: enabled: false mcncc-core: enabled: true acncc-core: enabled: true - the following multicluster configuration is not applicable as Multi-Cluster is not supported on OCI.
Support for Instance Configuration over IPV6 Family IPs
- CNC Console supports configuration of NF and Common Service Instances over IPv6
Family IPs as well. For configuring an IPv6 IP in the Instances:
- IP must be enclosed in square brackets "[]" as per IPv6 standards
- The complete IP String must be enclosed in double quotes (""). For example, "[2606:b400:605:b82e::]"
Sample Configuration Using
IPV6
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager & Agent Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: "[2606:b400:605:b82e::]"
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.con6.svc.trypticon.lab.us.oracle.com
port: 80
instances:
- id : Cluster1-bsf-instance1
type: BSF
owner: Cluster1
ip: "[2606:b400:605:b82e::1]"
port: 80
- id: Cluster1-kibana
type: CS
owner: Cluster1
ip: "[2606:b400:605:b82e::3]"
apiPrefix: /jazz/kibanaF.1.1 BSF Instances Configuration Examples
F.1.1.1 BSF Single Cluster Deployment Instance Configuration Examples
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
instances:
- id : Cluster1-bsf-instance1
type: BSF
owner: Cluster1
fqdn: bsf-ocbsf-config-mgmt.bsf.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
instances:
- id : Cluster1-bsf-instance1
type: BSF
owner: Cluster1
fqdn: bsf-ocbsf-config-mgmt.bsf.svc.cluster.local
port: 80F.1.1.2 BSF Multicluster Deployment Instance Configuration Examples
(M-CNCC Core on Cluster1, A-CNCC Core on Cluster1, and A-CNCC Core on
Cluster2)
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-bsf-instance1
type: BSF
owner: Cluster1
fqdn: bsf-ocbsf-config-mgmt.bsf.svc.cluster.local
port: 80
- id : Cluster2-bsf-instance1
type: BSF
owner: Cluster2
fqdn: bsf-ocbsf-config-mgmt.bsf1.svc.cluster.local
port: 80
- id : Cluster2-bsf-instance2
type: BSF
owner: Cluster2
fqdn: bsf-ocbsf-config-mgmt.bsf2.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-bsf-instance1
type: BSF
owner: Cluster1
fqdn: bsf-ocbsf-config-mgmt.bsf.svc.cluster.local
port: 80
- id : Cluster2-bsf-instance1
type: BSF
owner: Cluster2
fqdn: bsf-ocbsf-config-mgmt.bsf1.svc.cluster.local
port: 80
- id : Cluster2-bsf-instance2
type: BSF
owner: Cluster2
fqdn: bsf-ocbsf-config-mgmt.bsf2.svc.cluster.local
port: 80Note:
In this example, local NF and A-CNCC Core is considered to be deployed in Manager Cluster, its an optional configuration.CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-bsf-instance1
type: BSF
owner: Cluster2
fqdn: bsf-ocbsf-config-mgmt.bsf1.svc.cluster.local
port: 80
- id : Cluster2-bsf-instance2
type: BSF
owner: Cluster2
fqdn: bsf-ocbsf-config-mgmt.bsf2.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-bsf-instance1
type: BSF
owner: Cluster2
fqdn: bsf-ocbsf-config-mgmt.bsf1.svc.cluster.local
port: 80
- id : Cluster2-bsf-instance2
type: BSF
owner: Cluster2
fqdn: bsf-ocbsf-config-mgmt.bsf2.svc.cluster.local
port: 80F.1.2 DD Instance Configuration Examples
F.1.2.1 DD Single Cluster Deployment Instance Configuration Examples
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.occne-12ipcluster port: 80
instances:
- id : Cluster1-dd-instance1
type: DD-UI
owner: Cluster1
fqdn: ocnaddgui.ocnadd-deploy.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnadd
- id : Cluster1-dd-instance1
type: DD-API
owner: Cluster1
fqdn: ocnaddbackendrouter.ocnadd-deploy.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnaddapiSample Configuration for HTTPS Enabled Deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.occne-12ipcluster
port: 443
instances:
- id : Cluster1-dd-instance1
type: DD-UI
owner: Cluster1
fqdn: ocnaddgui.ocnadd-deploy.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnadd
- id : Cluster1-dd-instance1
type: DD-API
owner: Cluster1
fqdn: ocnaddbackendrouter.ocnadd-deploy.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnaddapiF.1.2.2 DD Multicluster Deployment Instances Configuration Examples
M-CNCC Core on Cluster1, A-CNCC Core on Cluster1 and A-CNCC Core on
Cluster2
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.occne-12ipcluster
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-dd-instance1
type: DD-UI
owner: Cluster1
fqdn: ocnaddgui.ocnadd-deploy.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnadd
- id : Cluster1-dd-instance1
type: DD-API
owner: Cluster1
fqdn: ocnaddbackendrouter.ocnadd-deploy.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnaddapi
- id : Cluster2-dd-instance1
type: DD-UI
owner: Cluster2
fqdn: ocnaddgui.ocnadd-deploy2.svc
port: 80
apiPrefix: /occne-13ipcluster/ocnadd
- id : Cluster2-dd-instance1
type: DD-API
owner: Cluster2
fqdn: ocnaddbackendrouter.ocnadd-deploy2.svc
port: 80
apiPrefix: /occne-13ipcluster/ocnaddapiSample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.occne-12ipcluster
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-dd-instance1
type: DD-UI
owner: Cluster1
fqdn: ocnaddgui.ocnadd-deploy.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnadd
- id : Cluster1-dd-instance1
type: DD-API
owner: Cluster1
fqdn: ocnaddbackendrouter.ocnadd-deploy.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnaddapi
- id : Cluster2-dd-instance1
type: DD-UI
owner: Cluster2
fqdn: ocnaddgui.ocnadd-deploy2.svc
port: 80
apiPrefix: /occne-13ipcluster/ocnadd
- id : Cluster2-dd-instance1
type: DD-API
owner: Cluster2
fqdn: ocnaddbackendrouter.ocnadd-deploy2.svc
port: 80
apiPrefix: /occne-13ipcluster/ocnaddapiNote:
In this example local NF and A-CNCC Core is considered to be deployed in Manager Cluster, its an optional configuration.CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-dd-instance1
type: DD-UI
owner: Cluster2
fqdn: ocnaddgui.ocnadd-deploy2.svc
port: 80
apiPrefix: /occne-13ipcluster/ocnadd
- id : Cluster2-dd-instance1
type: DD-API
owner: Cluster2
fqdn: ocnaddbackendrouter.ocnadd-deploy2.svc
port: 80
apiPrefix: /occne-13ipcluster/ocnaddapiSample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-dd-instance1
type: DD-UI
owner: Cluster2
fqdn: ocnaddgui.ocnadd-deploy.svc
port: 80
apiPrefix: /occne-13ipcluster/ocnadd
- id : Cluster2-dd-instance1
type: DD-API
owner: Cluster2
fqdn: ocnaddbackendrouter.ocnadd-deploy2.svc
port: 80
apiPrefix: /occne-13ipcluster/ocnaddapiF.1.3 NRF Instances Configuration Examples
F.1.3.1 NRF Single Cluster Deployment Instance Configuration Examples
NRF Single-Cluster Configuration
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
instances:
- id : Cluster1-nrf-instance1
type: NRF
owner: Cluster1
fqdn: ocnrf-nrfconfiguration.nrf.svc.cluster.local
port: 80 Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
instances:
- id : Cluster1-nrf-instance1
type: NRF
owner: Cluster1
fqdn: ocnrf-nrfconfiguration.nrf.svc.cluster.local
port: 80 F.1.3.2 NRF Multicluster Deployment Instance Configuration Examples
(M-CNCC Core on Cluster1, A-CNCC Core on Cluster1, and A-CNCC Core on
Cluster2)
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-nrf-instance1
type: NRF
owner: Cluster1
fqdn: nocnrf-nrfconfiguration.nrf.svc.cluster.local
port: 80
- id : Cluster2-nrf-instance1
type: NRF
owner: Cluster2
fqdn: ocnrf-nrfconfiguration.nrf1.svc.cluster.local
port: 80
- id : Cluster2-nrf-instance2
type: NRF
owner: Cluster2
fqdn: ocnrf-nrfconfiguration.nrf2.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-nrf-instance1
type: NRF
owner: Cluster1
fqdn: ocnrf-nrfconfiguration.nrf.svc.cluster.local
port: 80
- id : Cluster2-nrf-instance1
type: NRF
owner: Cluster2
fqdn: ocnrf-nrfconfiguration.nrf1.svc.cluster.local
port: 80
- id : Cluster2-nrf-instance2
type: NRF
owner: Cluster2
fqdn: ocnrf-nrfconfiguration.nrf2.svc.cluster.local
port: 80Note:
In this example, local NF and A-CNCC Core are considered to be deployed in Manager Cluster, it is an optional configuration.CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-nrf-instance1
type: NRF
owner: Cluster2
fqdn: ocnrf-nrfconfiguration.nrf1.svc.cluster.local
port: 80
- id : Cluster2-nrf-instance2
type: NRF
owner: Cluster2
fqdn: ocnrf-nrfconfiguration.nrf2.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-nrf-instance1
type: NRF
owner: Cluster2
fqdn: ocnrf-nrfconfiguration.nrf1.svc.cluster.local
port: 80
- id : Cluster2-nrf-instance2
type: NRF
owner: Cluster2
fqdn: ocnrf-nrfconfiguration.nrf2.svc.cluster.local
port: 80F.1.4 NSSF Instances Configuration Examples
F.1.4.1 NSSF Single Cluster Deployment Instance Configuration Examples
NSSF Single Cluster Configuration
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
instances:
- id : Cluster1-nssf-instance1
type: NSSF
owner: Cluster1
fqdn: ocnssf-nsconfig.ocnssf-nssf.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
instances:
- id : Cluster1-nssf-instance1
type: NSSF
owner: Cluster1
fqdn: ocnssf-nsconfig.ocnssf-nssf.svc.cluster.local
port: 80 F.1.4.2 NSSF Multicluster Deployment Instance Configuration Examples
(M-CNCC Core on Cluster1, A-CNCC Core on Cluster1, and A-CNCC Core on
Cluster2)
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-nssf-instance1
type: NSSF
owner: Cluster1
fqdn: ocnssf-nsconfig.ocnssf-nssf1.svc.cluster.local
port: 80
- id : Cluster2-nssf-instance1
type: NSSF
owner: Cluster2
fqdn: ocnssf-nsconfig.ocnssf-nssf2.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-nssf-instance1
type: NSSF
owner: Cluster1
fqdn: ocnssf-nsconfig.ocnssf-nssf1.svc.cluster.local
port: 80
- id : Cluster2-nssf-instance1
type: NSSF
owner: Cluster2
fqdn: ocnssf-nsconfig.ocnssf-nssf2.svc.cluster.local
port: 80Note:
In this example local NF and A-CNCC Core is considered to be deployed in Manager Cluster, its a optional configuration.
CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-nssf-instance1
type: NSSF
owner: Cluster2
fqdn: ocnssf-nsconfig.ocnssf-nssf2.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-nssf-instance1
type: NSSF
owner: Cluster2
fqdn: ocnssf-nsconfig.ocnssf-nssf2.svc.cluster.local
port: 80F.1.5 NWDAF Instance Configuration Examples
F.1.5.1 NWDAF Single Cluster Deployment Instance Configuration Examples
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.occne-223cluster
port: 80
instances:
- id : Cluster1-nwdaf-instance1
type: NWDAF-UI
owner: Cluster1
fqdn: nwdafgui.nwdaf-gui.svc
port: 80
apiPrefix: /occne-223cluster/nwdaf-gui/ocnwdaf
- id : Cluster1-nwdaf-instance1
type: NWDAF-API
owner: Cluster1
fqdn: nwdaf-portal-service.nwdaf-gui.svc
port: 80
apiPrefix: /occne-223cluster/nwdaf-gui/ocnwdafapiSample Configuration for HTTPS Enabled Deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.occne-223cluster
port: 443
instances:
- id : Cluster1-nwdaf-instance1
type: NWDAF-UI
owner: Cluster1
fqdn: nwdafgui.nwdaf-gui.svc
port: 80
apiPrefix: /occne-223cluster/nwdaf-gui/ocnwdaf
- id : Cluster1-nwdaf-instance1
type: NWDAF-API
owner: Cluster1
fqdn: nwdaf-portal-service.nwdaf-gui.svc
port: 80
apiPrefix: /occne-223cluster/nwdaf-gui/ocnwdafapiF.1.5.2 NWDAF Multicluster Deployment Instances Configuration Examples
M-CNCC Core on Cluster1, A-CNCC Core on Cluster1 and A-CNCC Core on
Cluster2
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.occne-223cluster
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-nwdaf-instance1
type: NWDAF-UI
owner: Cluster1
fqdn: nwdafgui.nwdaf-gui.svc
port: 80
apiPrefix: /occne-223cluster/nwdaf-gui/ocnwdaf
- id : Cluster1-nwdaf-instance1
type: NWDAF-API
owner: Cluster1
fqdn: nwdaf-portal-service.nwdaf-gui.svc
port: 80
apiPrefix: /occne-223cluster/nwdaf-gui/ocnwdafapi
- id : Cluster2-nwdaf-instance1
type: NWDAF-UI
owner: Cluster2
ip: 10.xx.xx.xx
port: 80
apiPrefix: /occne-224cluster/nwdaf-gui/ocnwdaf
- id : Cluster2-nwdaf-instance1
type: NWDAF-API
owner: Cluster2
ip: 10.xx.xx.xx
port: 80
apiPrefix: /occne-224cluster/nwdaf-gui/ocnwdafapiSample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.occne-223cluster
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-nwdaf-instance1
type: NWDAF-UI
owner: Cluster1
fqdn: nwdafgui.nwdaf-gui.svc
port: 80
apiPrefix: /occne-223cluster/nwdaf-gui/ocnwdaf
- id : Cluster1-nwdaf-instance1
type: NWDAF-API
owner: Cluster1
fqdn: nwdaf-portal-service.nwdaf-gui.svc
port: 80
apiPrefix: /occne-223cluster/nwdaf-gui/ocnwdafapi
- id : Cluster2-nwdaf-instance1
type: NWDAF-UI
owner: Cluster2
ip: 10.xx.xx.xx
port: 80
apiPrefix: /occne-224cluster/nwdaf-gui/ocnwdaf
- id : Cluster2-nwdaf-instance1
type: NWDAF-API
owner: Cluster2
ip: 10.xx.xx.xx
port: 80
apiPrefix: /occne-224cluster/nwdaf-gui/ocnwdafapiNote:
In this example local NF and A-CNCC Core is considered to be deployed in Manager Cluster, its an optional configuration.CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-nwdaf-instance1
type: NWDAF-UI
owner: Cluster2
ip: 10.xx.xx.xx
port: 80
apiPrefix: /occne-224cluster/nwdaf-gui/ocnwdaf
- id : Cluster2-nwdaf-instance1
type: NWDAF-API
owner: Cluster2
ip: 10.xx.xx.xx
port: 80
apiPrefix: /occne-224cluster/nwdaf-gui/ocnwdafapiSample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-nwdaf-instance1
type: NWDAF-UI
owner: Cluster2
ip: 10.xx.xx.xx
port: 80
apiPrefix: /occne-224cluster/nwdaf-gui/ocnwdaf
- id : Cluster2-nwdaf-instance1
type: NWDAF-API
owner: Cluster2
ip: 10.xx.xx.xx
port: 80
apiPrefix: /occne-224cluster/nwdaf-gui/ocnwdafapiF.1.6 Policy Instances Configuration Examples
F.1.6.1 Policy Single Cluster Deployment Instance Configuration Examples
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
instances:
- id : Cluster1-policy-instance1
type: POLICY
owner: Cluster1
fqdn: policy-occnp-config-mgmt.policy.svc.cluster.local
port: 80 Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
instances:
- id : Cluster1-policy-instance1
type: POLICY
owner: Cluster1
fqdn: policy-occnp-config-mgmt.policy.svc.cluster.local
port: 80 F.1.6.2 Policy Multicluster Deployment Instance Configuration Examples
(M-CNCC Core on Cluster1, A-CNCC Core on Cluster1 and A-CNCC Core on Cluster2)
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-policy-instance1
type: POLICY
owner: Cluster1
fqdn: policy-occnp-config-mgmt.policy.svc.cluster.local
port: 80
- id : Cluster2-policy-instance1
type: POLICY
owner: Cluster2
fqdn: policy-occnp-config-mgmt.policy1.svc.cluster.local
port: 80
- id : Cluster2-policy-instance2
type: POLICY
owner: Cluster2
fqdn: policy-occnp-config-mgmt.policy2.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-policy-instance1
type: POLICY
owner: Cluster1
fqdn: policy-occnp-config-mgmt.policy.svc.cluster.local
port: 80
- id : Cluster2-policy-instance1
type: POLICY
owner: Cluster2
fqdn: policy-occnp-config-mgmt.policy1.svc.cluster.local
port: 80
- id : Cluster2-policy-instance2
type: POLICY
owner: Cluster2
fqdn: policy-occnp-config-mgmt.policy2.svc.cluster.local
port: 80Note:
In this example, local NF and A-CNCC Core are considered to be deployed in Manager Cluster, it is an optional configuration.CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-policy-instance1
type: POLICY
owner: Cluster2
fqdn: policy-occnp-config-mgmt.policy1.svc.cluster.local
port: 80
- id : Cluster2-policy-instance2
type: POLICY
owner: Cluster2
fqdn: policy-occnp-config-mgmt.policy2.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-policy-instance1
type: POLICY
owner: Cluster2
fqdn: policy-occnp-config-mgmt.policy1.svc.cluster.local
port: 80
- id : Cluster2-policy-instance2
type: POLICY
owner: Cluster2
fqdn: policy-occnp-config-mgmt.policy2.svc.cluster.local
port: 80F.1.7 PROVGW Instances Configuration Examples
F.1.7.1 PROVGW Single Cluster Deployment Instance Configuration Examples
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
instances:
- id : Cluster1-provgw-instance1
type: PROVGW
owner: Cluster1
fqdn: provgw1-provgw-config.provgw.svc.cluster.local
port: 80Sample Configuration for HTTPS Enabled Deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
instances:
- id : Cluster1-provgw-instance1
type: PROVGW
owner: Cluster1
fqdn: provgw1-provgw-config.provgw.svc.cluster.local
port: 80F.1.7.2 PROVGW Multicluster Deployment Instances Configuration Examples
M-CNCC Core on Cluster1, A-CNCC Core on Cluster1 and A-CNCC Core on
Cluster2
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-provgw-instance1
type: PROVGW
owner: Cluster1
fqdn: provgw1-provgw-config.provgw.svc.cluster.local
port: 80
- id : Cluster2-provgw-instance1
type: PROVGW
owner: Cluster2
fqdn: provgw1-provgw-config.provgw2.svc.cluster.local
port: 80
- id : Cluster2-provgw-instance2
type: PROVGW
owner: Cluster2
fqdn: provgw1-provgw-config2.provgw2.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-provgw-instance1
type: PROVGW
owner: Cluster1
fqdn: provgw1-provgw-config.provgw.svc.cluster.local
port: 80
- id : Cluster2-provgw-instance1
type: PROVGW
owner: Cluster2
fqdn: provgw1-provgw-config.provgw2.svc.cluster.local
port: 80
- id : Cluster2-provgw-instance2
type: PROVGW
owner: Cluster2
fqdn: provgw1-provgw-config2.provgw2.svc.cluster.local
port: 80Note:
In this example local NF and A-CNCC Core is considered to be deployed in Manager Cluster, its a optional configuration.CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-provgw-instance1
type: PROVGW
owner: Cluster2
fqdn: provgw1-provgw-config.provgw2.svc.cluster.local
port: 80
- id : Cluster2-provgw-instance2
type: PROVGW
owner: Cluster2
fqdn: provgw1-provgw-config2.provgw2.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-provgw-instance1
type: PROVGW
owner: Cluster2
fqdn: provgw1-provgw-config.provgw2.svc.cluster.local
port: 80
- id : Cluster2-provgw-instance2
type: PROVGW
owner: Cluster2
fqdn: provgw1-provgw-config2.provgw2.svc.cluster.local
port: 80F.1.8 SCP Instances Configuration Examples
F.1.8.1 SCP Single Cluster Deployment Instance Configuration Examples
SCP Single Cluster Configuration
CNC Console Configurationglobal:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
instances:
- id : Cluster1-scp-instance1
type: SCP
owner: Cluster1
fqdn: ocscp-scpc-configuration.scp.svc.cluster.local
port: 80 Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
instances:
- id : Cluster1-scp-instance1
type: SCP
owner: Cluster1
fqdn: ocscp-scpc-configuration.scp.svc.cluster.local
port: 80 F.1.8.2 SCP Multicluster Deployment Instance Configuration Examples
(M-CNCC Core on Cluster1, A-CNCC Core on Cluster1 and A-CNCC Core on Cluster2)
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-scp-instance1
type: SCP
owner: Cluster1
fqdn: ocscp-scpc-configuration.scp.svc.cluster.local
port: 80
- id : Cluster2-scp-instance1
type: SCP
owner: Cluster2
fqdn: ocscp-scpc-configuration.scp1.svc.cluster.local
port: 80
- id : Cluster2-scp-instance2
type: SCP
owner: Cluster2
fqdn: ocscp-scpc-configuration.scp2.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-scp-instance1
type: SCP
owner: Cluster1
fqdn: ocscp-scpc-configuration.scp.svc.cluster.local
port: 80
- id : Cluster2-scp-instance1
type: SCP
owner: Cluster2
fqdn: ocscp-scpc-configuration.scp1.svc.cluster.local
port: 80
- id : Cluster2-scp-instance2
type: SCP
owner: Cluster2
fqdn: ocscp-scpc-configuration.scp2.svc.cluster.local
port: 80Note:
In this example local NF and A-CNCC Core are considered to be deployed in Manager Cluster, it is an optional configuration.
CNC Console Configuration (Agent
Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-scp-instance1
type: SCP
owner: Cluster2
fqdn: ocscp-scpc-configuration.scp1.svc.cluster.local
port: 80
- id : Cluster2-scp-instance2
type: SCP
owner: Cluster2
fqdn: ocscp-scpc-configuration.scp2.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-scp-instance1
type: SCP
owner: Cluster2
fqdn: ocscp-scpc-configuration.scp1.svc.cluster.local
port: 80
- id : Cluster2-scp-instance2
type: SCP
owner: Cluster2
fqdn: ocscp-scpc-configuration.scp2.svc.cluster.local
port: 80F.1.9 SEPP Instances Configuration Examples
F.1.9.1 SEPP Single Cluster Deployment Instance Configuration Examples
SEPP Single Cluster Configuration
CNC Console Configurationglobal:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
instances:
- id : Cluster1-sepp-instance1
type: SEPP
owner: Cluster1
fqdn: ocsepp-config-mgr-svc.sepp.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
instances:
- id : Cluster1-sepp-instance1
type: SEPP
owner: Cluster1
fqdn: ocsepp-config-mgr-svc.sepp.svc.cluster.local
port: 80F.1.9.2 SEPP Multicluster Deployment Instance Configuration Examples
(M-CNCC Core on Cluster1, A-CNCC Core on Cluster1, and A-CNCC Core on Cluster2)
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-sepp-instance1
type: SEPP
owner: Cluster1
fqdn: ocsepp-config-mgr-svc.sepp.svc.cluster.local
port: 80
- id : Cluster2-sepp-instance1
type: SEPP
owner: Cluster2
fqdn: ocsepp-config-mgr-svc.sepp1.svc.cluster.local
port: 80
- id : Cluster2-sepp-instance2
type: SEPP
owner: Cluster2
fqdn: ocsepp-config-mgr-svc.sepp2.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-sepp-instance1
type: SEPP
owner: Cluster1
fqdn: ocsepp-config-mgr-svc.sepp.svc.cluster.local
port: 80
- id : Cluster2-sepp-instance1
type: SEPP
owner: Cluster2
fqdn: ocsepp-config-mgr-svc.sepp1.svc.cluster.local
port: 80
- id : Cluster2-sepp-instance2
type: SEPP
owner: Cluster2
fqdn: ocsepp-config-mgr-svc.sepp2.svc.cluster.local
port: 80Note:
In this example, the local NF and A-CNCC Core are considered to be deployed in Manager Cluster, it is an optional configuration.
CNC Console Configuration (Agent
Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-sepp-instance1
type: SEPP
owner: Cluster2
fqdn: ocsepp-config-mgr-svc.sepp1.svc.cluster.local
port: 80
- id : Cluster2-sepp-instance2
type: SEPP
owner: Cluster2
fqdn: ocsepp-config-mgr-svc.sepp2.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-sepp-instance1
type: SEPP
owner: Cluster2
fqdn: ocsepp-config-mgr-svc.sepp1.svc.cluster.local
port: 80
- id : Cluster2-sepp-instance2
type: SEPP
owner: Cluster2
fqdn: ocsepp-config-mgr-svc.sepp2.svc.cluster.local
port: 80F.1.10 UDR Instances Configuration Examples
F.1.10.1 UDR Single Cluster Deployment Instance Configuration Examples
UDR Single Cluster Configuration
CNC Console Configurationglobal:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
instances:
- id : Cluster1-udr-instance1
type: UDR-PROV
owner: Cluster1
fqdn: udr1-ingressgateway-prov.udr.svc.cluster.local
port: 80
- id : Cluster1-udr-instance1
type: UDR-CONFIG
owner: Cluster1
fqdn: udr1-nudr-config.udr.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
global:
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
instances:
- id : Cluster1-udr-instance1
type: UDR-PROV
owner: Cluster1
fqdn: udr1-ingressgateway-prov.udr.svc.cluster.local
port: 80
- id : Cluster1-udr-instance1
type: UDR-CONFIG
owner: Cluster1
fqdn: udr1-nudr-config.udr.svc.cluster.local
port: 80global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
instances:
- id : Cluster1-udr-instance1
type: UDR-PROV
owner: Cluster1
fqdn: udr1-ingressgateway-prov.udr.svc.cluster.local
port: 80
- id : Cluster1-udr-instance1
type: UDR-CONFIG
owner: Cluster1
fqdn: udr1-nudr-config.udr.svc.cluster.local
port: 80F.1.10.2 UDR Multicluster Deployment Instance Configuration Examples
(M-CNCC Core on Cluster1 , A-CNCC Core on Cluster1, and A-CNCC Core on Cluster2)
CNCC Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-udr-instance1
type: UDR-PROV
owner: Cluster1
fqdn: udr1-ingressgateway-prov.udr.svc.cluster.local
port: 80
- id : Cluster1-udr-instance1
type: UDR-CONFIG
owner: Cluster1
fqdn: udr1-nudr-config.udr1.svc.cluster.local
port: 80
- id : Cluster2-udr-instance1
type: UDR-PROV
owner: Cluster2
fqdn: udr1-ingressgateway-prov.udr1.svc.cluster.local
port: 80
- id : Cluster2-udr-instance1
type: UDR-CONFIG
owner: Cluster2
fqdn: udr1-nudr-config.udr1.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNCC Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-udr-instance1
type: UDR-PROV
owner: Cluster1
fqdn: udr1-ingressgateway-prov.udr.svc.cluster.local
port: 80
- id : Cluster1-udr-instance1
type: UDR-CONFIG
owner: Cluster1
fqdn: udr1-nudr-config.udr1.svc.cluster.local
port: 80
- id : Cluster2-udr-instance1
type: UDR-PROV
owner: Cluster2
fqdn: udr1-ingressgateway-prov.udr1.svc.cluster.local
port: 80
- id : Cluster2-udr-instance1
type: UDR-CONFIG
owner: Cluster2
fqdn: udr1-nudr-config.udr1.svc.cluster.local
port: 80Note:
In this example, local NF and A-CNCC Core are considered to be deployed in Manager Cluster, it is an optional configuration.
CNCC Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-udr-instance1
type: UDR-PROV
owner: Cluster2
fqdn: udr1-ingressgateway-prov.udr1.svc.cluster.local
port: 80
- id : Cluster2-udr-instance1
type: UDR-CONFIG
owner: Cluster2
fqdn: udr1-nudr-config.udr1.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNCC Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-udr-instance1
type: UDR-PROV
owner: Cluster2
fqdn: udr1-ingressgateway-prov.udr1.svc.cluster.local
port: 80
- id : Cluster2-udr-instance1
type: UDR-CONFIG
owner: Cluster2
fqdn: udr1-nudr-config.udr1.svc.cluster.local
port: 80F.1.11 Common Service Instances Configuration Examples
F.1.11.1 Common Service Single Cluster Deployment Instance Configuration Examples
Common Service Single Cluster Configuration
CNC Console Configurationglobal:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.jazz
port: 80
instances:
- id: Cluster1-grafana
type: CS
owner: Cluster1
fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
apiPrefix: /jazz/grafana
- id: Cluster1-kibana
type: CS
owner: Cluster1
fqdn: occne-kibana.occne-infra.svc
apiPrefix: /jazz/kibana
- id: Cluster1-jaeger
type: CS
owner: Cluster1
fqdn: occne-tracer-jaeger-query.occne-infra.svc
apiPrefix: /jazz/jaeger
- id: Cluster1-prometheus
type: CS
owner: Cluster1
fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
apiPrefix: /jazz/prometheus
- id: Cluster1-alertmanager
type: CS
owner: Cluster1
fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
apiPrefix: /jazz/alertmanager
- id: Cluster1-promxy
type: CS
owner: Cluster1
fqdn: occne-promxy-apigw-nginx.occne-infra.svc
apiPrefix: /jazz/promxy
- id: Cluster1-opensearch
type: CS
owner: Cluster1
fqdn: occne-opensearch-dashboards.occne-infra.svc
apiPrefix: /jazz/dashboard
- id: Cluster1-jaegeres
type: CS
owner: Cluster1
fqdn: occne-tracer-elasticsearch-jaeger-query.occne-infra.svc
apiPrefix: /jazz/esjaegerSample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.jazz
port: 443
instances:
- id: Cluster1-grafana
type: CS
owner: Cluster1
fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
apiPrefix: /jazz/grafana
- id: Cluster1-kibana
type: CS
owner: Cluster1
fqdn: occne-kibana.occne-infra.svc
apiPrefix: /jazz/kibana
- id: Cluster1-jaeger
type: CS
owner: Cluster1
fqdn: occne-tracer-jaeger-query.occne-infra.svc
apiPrefix: /jazz/jaeger
- id: Cluster1-prometheus
type: CS
owner: Cluster1
fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
apiPrefix: /jazz/prometheus
- id: Cluster1-alertmanager
type: CS
owner: Cluster1
fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
apiPrefix: /jazz/alertmanager
- id: Cluster1-promxy
type: CS
owner: Cluster1
fqdn: occne-promxy-apigw-nginx.occne-infra.svc
apiPrefix: /jazz/promxy
- id: Cluster1-opensearch
type: CS
owner: Cluster1
fqdn: occne-opensearch-dashboards.occne-infra.svc
apiPrefix: /jazz/dashboard
- id: Cluster1-jaegeres
type: CS
owner: Cluster1
fqdn: occne-tracer-elasticsearch-jaeger-query.occne-infra.svc
apiPrefix: /jazz/esjaegerF.1.11.2 Common Service Multicluster Deployment Instance Configuration Examples
(M-CNCC Core on Cluster1 , A-CNCC Core on Cluster1, and A-CNCC Core on Cluster2)
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.jazz
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id: Cluster1-grafana
type: CS
owner: Cluster1
fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
apiPrefix: /jazz/grafana
- id: Cluster1-kibana
type: CS
owner: Cluster1
fqdn: occne-kibana.occne-infra.svc
apiPrefix: /jazz/kibana
- id: Cluster1-jaeger
type: CS
owner: Cluster1
fqdn: occne-tracer-jaeger-query.occne-infra.svc
apiPrefix: /jazz/jaeger
- id: Cluster1-prometheus
type: CS
owner: Cluster1
fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
apiPrefix: /jazz/prometheus
- id: Cluster1-alertmanager
type: CS
owner: Cluster1
fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
apiPrefix: /jazz/alertmanager
- id: Cluster1-promxy
type: CS
owner: Cluster1
fqdn: occne-promxy-apigw-nginx.occne-infra.svc
apiPrefix: /jazz/promxy
- id: Cluster1-opensearch
type: CS
owner: Cluster1
fqdn: occne-opensearch-dashboards.occne-infra.svc
apiPrefix: /jazz/dashboard
- id: Cluster1-jaegeres
type: CS
owner: Cluster1
fqdn: occne-tracer-elasticsearch-jaeger-query.occne-infra.svc
apiPrefix: /jazz/esjaeger
- id: Cluster2-grafana
type: CS
owner: Cluster2
fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
apiPrefix: /rivendell-2210/grafana
- id: Cluster2-kibana
type: CS
owner: Cluster2
fqdn: occne-kibana.occne-infra.svc
apiPrefix: /rivendell-2210/kibana
- id: Cluster2-jaeger
type: CS
owner: Cluster2
fqdn: occne-tracer-jaeger-query.occne-infra.svc
apiPrefix: /rivendell-2210/jaeger
- id: Cluster2-prometheus
type: CS
owner: Cluster2
fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
apiPrefix: /rivendell-2210/prometheus
- id: Cluster2-alertmanager
type: CS
owner: Cluster2
fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
apiPrefix: /rivendell-2210/alertmanager
- id: Cluster2-promxy
type: CS
owner: Cluster2
fqdn: occne-promxy-apigw-nginx.occne-infra.svc
apiPrefix: /rivendell-2210/promxy
- id: Cluster2-opensearch
type: CS
owner: Cluster2
fqdn: occne-opensearch-dashboards.occne-infra.svc
apiPrefix: /rivendell-2210/dashboard
- id: Cluster2-jaegeres
type: CS
owner: Cluster2
fqdn: occne-tracer-elasticsearch-jaeger-query.occne-infra.svc
apiPrefix: /rivendell-2210/esjaegerSample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.jazz
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id: Cluster1-grafana
type: CS
owner: Cluster1
fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
apiPrefix: /jazz/grafana
- id: Cluster1-kibana
type: CS
owner: Cluster1
fqdn: occne-kibana.occne-infra.svc
apiPrefix: /jazz/kibana
- id: Cluster1-jaeger
type: CS
owner: Cluster1
fqdn: occne-tracer-jaeger-query.occne-infra.svc
apiPrefix: /jazz/jaeger
- id: Cluster1-prometheus
type: CS
owner: Cluster1
fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
apiPrefix: /jazz/prometheus
- id: Cluster1-alertmanager
type: CS
owner: Cluster1
fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
apiPrefix: /jazz/alertmanager
- id: Cluster1-promxy
type: CS
owner: Cluster1
fqdn: occne-promxy-apigw-nginx.occne-infra.svc
apiPrefix: /jazz/promxy
- id: Cluster1-opensearch
type: CS
owner: Cluster1
fqdn: occne-opensearch-dashboards.occne-infra.svc
apiPrefix: /jazz/dashboard
- id: Cluster1-jaegeres
type: CS
owner: Cluster1
fqdn: occne-tracer-elasticsearch-jaeger-query.occne-infra.svc
apiPrefix: /jazz/esjaeger
- id: Cluster2-grafana
type: CS
owner: Cluster2
fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
apiPrefix: /rivendell-2210/grafana
- id: Cluster2-kibana
type: CS
owner: Cluster2
fqdn: occne-kibana.occne-infra.svc
apiPrefix: /rivendell-2210/kibana
- id: Cluster2-jaeger
type: CS
owner: Cluster2
fqdn: occne-tracer-jaeger-query.occne-infra.svc
apiPrefix: /rivendell-2210/jaeger
- id: Cluster2-prometheus
type: CS
owner: Cluster2
fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
apiPrefix: /rivendell-2210/prometheus
- id: Cluster2-alertmanager
type: CS
owner: Cluster2
fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
apiPrefix: /rivendell-2210/alertmanager
- id: Cluster2-promxy
type: CS
owner: Cluster2
fqdn: occne-promxy-apigw-nginx.occne-infra.svc
apiPrefix: /rivendell-2210/promxy
- id: Cluster2-opensearch
type: CS
owner: Cluster2
fqdn: occne-opensearch-dashboards.occne-infra.svc
apiPrefix: /rivendell-2210/dashboard
- id: Cluster2-jaegeres
type: CS
owner: Cluster2
fqdn: occne-tracer-elasticsearch-jaeger-query.occne-infra.svc
apiPrefix: /rivendell-2210/esjaeger Note:
In this example, local NF and A-CNCC Core are considered to be deployed in Manager Cluster, it is an optional configuration.
CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id: Cluster2-grafana
type: CS
owner: Cluster2
fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
apiPrefix: /rivendell-2210/grafana
- id: Cluster2-kibana
type: CS
owner: Cluster2
fqdn: occne-kibana.occne-infra.svc
apiPrefix: /rivendell-2210/kibana
- id: Cluster2-jaeger
type: CS
owner: Cluster2
fqdn: occne-tracer-jaeger-query.occne-infra.svc
apiPrefix: /rivendell-2210/jaeger
- id: Cluster2-prometheus
type: CS
owner: Cluster2
fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
apiPrefix: /rivendell-2210/prometheus
- id: Cluster2-alertmanager
type: CS
owner: Cluster2
fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
apiPrefix: /rivendell-2210/alertmanager
- id: Cluster2-promxy
type: CS
owner: Cluster2
fqdn: occne-promxy-apigw-nginx.occne-infra.svc
apiPrefix: /rivendell-2210/promxy
- id: Cluster2-opensearch
type: CS
owner: Cluster2
fqdn: occne-opensearch-dashboards.occne-infra.svc
apiPrefix: /rivendell-2210/dashboard
- id: Cluster2-jaegeres
type: CS
owner: Cluster2
fqdn: occne-tracer-elasticsearch-jaeger-query.occne-infra.svc
apiPrefix: /rivendell-2210/esjaegerSample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id: Cluster2-grafana
type: CS
owner: Cluster2
fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
apiPrefix: /rivendell-2210/grafana
- id: Cluster2-kibana
type: CS
owner: Cluster2
fqdn: occne-kibana.occne-infra.svc
apiPrefix: /rivendell-2210/kibana
- id: Cluster2-jaeger
type: CS
owner: Cluster2
fqdn: occne-tracer-jaeger-query.occne-infra.svc
apiPrefix: /rivendell-2210/jaeger
- id: Cluster2-prometheus
type: CS
owner: Cluster2
fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
apiPrefix: /rivendell-2210/prometheus
- id: Cluster2-alertmanager
type: CS
owner: Cluster2
fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
apiPrefix: /rivendell-2210/alertmanager
- id: Cluster2-promxy
type: CS
owner: Cluster2
fqdn: occne-promxy-apigw-nginx.occne-infra.svc
apiPrefix: /rivendell-2210/promxy
- id: Cluster2-opensearch
type: CS
owner: Cluster2
fqdn: occne-opensearch-dashboards.occne-infra.svc
apiPrefix: /rivendell-2210/dashboard
- id: Cluster2-jaegeres
type: CS
owner: Cluster2
fqdn: occne-tracer-elasticsearch-jaeger-query.occne-infra.svc
apiPrefix: /rivendell-2210/esjaegerF.1.12 CNC Console Instances Configuration With cnDBTier Menu Enabled
F.1.12.1 CNC Console Single-Cluster Configuration with cnDBTier Menu Enabled
CNC Console Core
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
instances:
- id : Cluster1-cncc-instance1
type: CNCC
owner: Cluster1
- id : Cluster1-cncc-instance1
type: DBTIER
owner: Cluster1
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
instances:
- id : Cluster1-cncc-instance1
type: CNCC
owner: Cluster1
- id : Cluster1-cncc-instance1
type: DBTIER
owner: Cluster1
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80F.1.12.2 CNC Console Multicluster Configuration with cnDBTier Menu Enabled
(M-CNCC Core on Cluster1, A-CNCC Core on Cluster1, and A-CNCC Core on
Cluster2)
CNC Console Core (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.jazz
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-cncc-instance1
type: CNCC
owner: Cluster1
- id : Cluster1-cncc-instance1
type: DBTIER
owner: Cluster1
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80
- id : Cluster2-cncc-instance1
type: CNCC
owner: Cluster2
- id : Cluster2-cncc-instance1
type: DBTIER
owner: Cluster2
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.jazz
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-cncc-instance1
type: CNCC
owner: Cluster1
- id : Cluster1-cncc-instance1
type: DBTIER
owner: Cluster1
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80
- id : Cluster2-cncc-instance1
type: CNCC
owner: Cluster2
- id : Cluster2-cncc-instance1
type: DBTIER
owner: Cluster2
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80Note:
In this example, local NF and A-CNCC Core is considered to be deployed in Manager Cluster, its an optional configuration.CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-cncc-instance1
type: CNCC
owner: Cluster2
- id : Cluster2-cncc-instance1
type: DBTIER
owner: Cluster2
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-cncc-instance1
type: CNCC
owner: Cluster2
- id : Cluster2-cncc-instance1
type: DBTIER
owner: Cluster2
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80F.1.13 OCCM Instance Configuration Examples
F.1.13.1 OCCM Single Cluster Configuration
OCCM Single Cluster Configuration
CNC Console Configurationglobal:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
instances:
- id : Cluster1-occm-instance1
type: OCCM
owner: Cluster1
fqdn: occm.occm.svc.cluster.local
port: 80 Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
instances:
- id : Cluster1-occm-instance1
type: OCCM
owner: Cluster1
fqdn: occm.occm.svc.cluster.local
port: 80 F.1.13.2 OCCM Multicluster Configuration
(M-CNCC Core on Cluster1 , A-CNCC Core on Cluster1, and A-CNCC Core on Cluster2)
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-occm-instance1
type: OCCM
owner: Cluster1
fqdn: occm.occm.svc.cluster.local
port: 80
- id : Cluster2-occm-instance1
type: OCCM
owner: Cluster2
fqdn: occm.occm.svc.cluster.local
port: 80
- id : Cluster2-occm-instance2
type: OCCM
owner: Cluster2
fqdn: occm.occm.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNCC Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-occm-instance1
type: OCCM
owner: Cluster1
fqdn: occm.occm.svc.cluster.local
port: 80
- id : Cluster2-ocm-instance1
type: OCCM
owner: Cluster2
fqdn: occm.occm.svc.cluster.local
port: 80
- id : Cluster2-occm-instance2
type: OCCM
owner: Cluster2
fqdn: occm.occm.svc.cluster.local
port: 80Note:
In this example, local NF and A-CNCC Core are considered to be deployed in Manager Cluster, it is an optional configuration.
CNCC Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-occm-instance1
type: OCCM
owner: Cluster2
fqdn: occm.occm.svc.cluster.local
port: 80
- id : Cluster2-occm-instance2
type: OCCM
owner: Cluster2
fqdn: occm.occm.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNCC Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-occm-instance1
type: OCCM
owner: Cluster2
fqdn: occm.occm.svc.cluster.local
port: 80
- id : Cluster2-occm-instance2
type: OCCM
owner: Cluster2
fqdn: occm.occm.svc.cluster.local
port: 80F.1.14 NEF Instance Configuration Examples
F.1.14.1 NEF Single Cluster Configuration
NEF Single Cluster Configuration
CNC Console Configurationglobal:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
instances:
- id : Cluster1-nef-instance1
type: NEF
owner: Cluster1
fqdn: ocnef-consoledataservice.nef.svc.cluster.local
port: 80 Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
instances:
- id : Cluster1-nef-instance1
type: NEF
owner: Cluster1
fqdn: ocnef-consoledataservice.nef.svc.cluster.local
port: 80 F.1.14.2 NEF Multicluster Configuration
(M-CNCC Core on Cluster1 , A-CNCC Core on Cluster1, and A-CNCC Core on Cluster2)
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-nef-instance1
type: NEF
owner: Cluster1
fqdn: ocnef-consoledataservice.nef.svc.cluster.local
port: 80
- id : Cluster2-nef-instance1
type: NEF
owner: Cluster2
fqdn: ocnef-consoledataservice.nef.svc.cluster.local
port: 80
- id : Cluster2-nef-instance2
type: NEF
owner: Cluster2
fqdn: ocnef-consoledataservice.nef.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNCC Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-nef-instance1
type: NEF
owner: Cluster1
fqdn: ocnef-consoledataservice.nef.svc.cluster.local
port: 80
- id : Cluster2-nef-instance1
type: NEF
owner: Cluster2
fqdn: ocnef-consoledataservice.nef.svc.cluster.local
port: 80
- id : Cluster2-nef-instance2
type: NEF
owner: Cluster2
fqdn: ocnef-consoledataservice.nef.svc.cluster.local
port: 80Note:
In this example, local NF and A-CNCC Core are considered to be deployed in Manager Cluster, it is an optional configuration.
CNCC Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-nef-instance1
type: NEF
owner: Cluster2
fqdn: ocnef-consoledataservice.nef.svc.cluster.local
port: 80
- id : Cluster2-nef-instance2
type: NEF
owner: Cluster2
fqdn: ocnef-consoledataservice.nef.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNCC Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-nef-instance1
type: NEF
owner: Cluster2
fqdn: ocnef-consoledataservice.nef.svc.cluster.local
port: 80
- id : Cluster2-nef-instance2
type: NEF
owner: Cluster2
fqdn: ocnef-consoledataservice.nef.svc.cluster.local
port: 80F.1.15 NF Instance Configuration With cnDBTier Menu Enabled
F.1.15.1 NF Single Cluster Configuration With cnDBTier Menu Enabled
NF instance configuration should include DBTIER instance configuration to enable DBTIER menu items for NF.
Here is the example for SCP instance configuration. Similar configuration should be performed for other NFs.
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 80
instances:
- id : Cluster1-scp-instance1
type: SCP
owner: Cluster1
fqdn: ocscp-scpc-configuration.ocscp.svc.cluster.local
port: 80
- id : Cluster1-scp-instance1
type: DBTIER
owner: Cluster1
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: false
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local
port: 443
instances:
- id : Cluster1-scp-instance1
type: SCP
owner: Cluster1
fqdn: ocscp-scpc-configuration.ocscp.svc.cluster.local
port: 80
- id : Cluster1-scp-instance1
type: DBTIER
owner: Cluster1
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80 F.1.15.2 NF Multicluster Configuration With cnDBTier Menu Enabled
(M-CNCC Core on Cluster1, A-CNCC Core on Cluster1, and A-CNCC Core on
Cluster2)
CNC Console Core (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.jazz
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-scp-instance1
type: SCP
owner: Cluster1
fqdn: ocscp-scpc-configuration.ocscp.svc.cluster.local
port: 80
- id : Cluster1-scp-instance1
type: DBTIER
owner: Cluster1
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80
- id : Cluster2-scp-instance1
type: SCP
owner: Cluster2
fqdn: ocscp-scpc-configuration.ocscp.svc.cluster.local
port: 80
- id : Cluster2-scp-instance1
type: DBTIER
owner: Cluster2
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Manager Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.jazz
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-scp-instance1
type: SCP
owner: Cluster1
fqdn: ocscp-scpc-configuration.ocscp.svc.cluster.local
port: 80
- id : Cluster1-scp-instance1
type: DBTIER
owner: Cluster1
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80
- id : Cluster2-scp-instance1
type: SCP
owner: Cluster2
fqdn: ocscp-scpc-configuration.ocscp.svc.cluster.local
port: 80
- id : Cluster2-scp-instance1
type: DBTIER
owner: Cluster2
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80 Note:
In this example, local NF and A-CNCC Core is considered to be deployed in Manager Cluster, its an optional configuration.CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-scp-instance1
type: SCP
owner: Cluster2
fqdn: ocscp-scpc-configuration.ocscp.svc.cluster.local
port: 80
- id : Cluster2-scp-instance1
type: DBTIER
owner: Cluster2
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNC Console Configuration (Agent Cluster)
global:
oci-iam:
enabled: false
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-scp-instance1
type: SCP
owner: Cluster2
fqdn: ocscp-scpc-configuration.ocscp.svc.cluster.local
port: 80
- id : Cluster2-scp-instance1
type: DBTIER
owner: Cluster2
fqdn: mysql-cluster-db-monitor-svc.cndbtier.svc.cluster.local
port: 80