You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »


Create VMs

For sites

Create two kubernetes clusters aka sites. Each site should have one master and at least three worker nodes with below config -

VCPUs4
Disk20 GB
RAM16 GB


Configure Kubernetes Clusters


Prepare sites

Note that we are using "coredns" feature gate instead of "kube-dns".


Site 1 (Primary Site)

Follow steps from below link to install a kubernetes cluster using kubeadm, with four VMs created in above step -

https://wiki.onap.org/display/DW/Deploying+Kubernetes+Cluster+with+kubeadm

Steps before "Configuring SDNC-ONAP" should only be followed.


Follow steps from following link to deploy SDN-C: Deploying SDN-C using helm chart

Before deploying SDN-C Cluster on secondary kubernetes cluster, configure the values.yaml file for SDN-C chart to enable GeoRedundancy.

The values.yaml file is what defines the GEO partitioning for the clusters, so for the primary cluster myODLCluster should have the IP address of the master node of the primary cluster and the peerODLCluster should have the IP address of the master node of the secondary (standby) cluster.

And the secondary cluster, it would be the reverse of the primary cluster.

Example of <oom repo>/kubernetes/sdnc/values.yaml

enableODLCluster: true
geoEnabled: true

peerODLCluster: 10.147.114.5
myODLCluster: 10.147.114.140


Site 2 (Secondary/Backup Site)

Follow steps from below link to install another kubernetes cluster with SDN-C using kubeadm, with four VMs created in above step -

https://wiki.onap.org/display/DW/Deploying+Kubernetes+Cluster+with+kubeadm

Steps before "Configuring SDNC-ONAP" should only be followed.


Follow steps from following link to deploy SDN-C: Deploying SDN-C using helm chart

Before deploying SDN-C Cluster on secondary kubernetes cluster,

a)  configure the values.yaml file for SDN-C chart to enable geo redundancy.

The values.yaml file is what defines the GEO partitioning for the clusters, so for the primary cluster myODLCluster should have the IP address of the master node of the primary cluster and the peerODLCluster should have the IP address of the master node of the secondary (standby) cluster. And the secondary cluster, it would be the reverse of the primary cluster.

Example of <oom repo>/kubernetes/sdnc/values.yaml

enableODLCluster: true
geoEnabled: true

peerODLCluster: 10.147.114.5
myODLCluster: 10.147.114.140


b) configure the geographic site id for secondary site for MySQL chart as below:

Configure geographic site id

for secondary site (site 2)

vi kubernetes/common/mysql/values.yaml

Change the following fields with the new value:

field

new value

old value

geoSiteId21
geoEnabledtruefalse
  • No labels