SDC Reconfiguration - Temp

Owned by Shekar Sundaramurthy
Last updated: Apr 24, 2018 by Roger Maitland
1 min read





Hi,

As we discussed we are splitting our be server into two dockers as a result you will now have two new dockers as part of the sdc deployment.

The new dockers are:

onap/sdc-onboard-cassandra-init:latest  this docker is responsible for configuring the key spaces needed for the onboarding be.

onap/sdc-onboard-backend:latest   this is the second be server that we have.



I have add a picture to describe the dependency between our dockers.



https://git.onap.org/sdc/tree/sdc-os-chef/kubernetes/sdc/templates/configmaps/sdc-environment-configmap.yaml this now has a new value for the ip of the onboarding docker and the port used for it (ONBOARDING_BE_VIP, ONBOARDING_BE and onboarding ports).

https://git.onap.org/sdc/tree/sdc-os-chef/kubernetes/sdc/templates/deployments/sdc-onboard.yaml the deployment yaml for the onboarding docker.

https://git.onap.org/sdc/tree/sdc-os-chef/kubernetes/sdc/templates/jobs/sdc-onboard-cassandra-init.yaml this is the job definition for the init onboard Cassandra.

https://git.onap.org/sdc/tree/sdc-os-chef/kubernetes/sdc/templates/services/all-services.yaml we add a new service for the onboarding back end server.



If there are any questions or issues please contact me or Areli.



The code is already available in the master branch and the dockers are available in nexus.