| commit | 9f3aa87a00132818aac28a7ab5a24d203e501475 | [log] [tgz] |
|---|---|---|
| author | Scott Baker <smbaker@gmail.com> | Tue Mar 06 22:13:02 2018 -0800 |
| committer | Scott Baker <smbaker@gmail.com> | Tue Mar 06 22:28:39 2018 -0800 |
| tree | 3fa1f9bc40cd7f2586a605852c464637b0a9ec02 | |
| parent | ee4918b8dd2966a880f694e577bfcb876830f164 [diff] |
CORD-2509 migrate sdn-controller service from static to dynamic load Change-Id: Ie9146708fc4262a2376d2071531a7b792ac35d54
To onboard this service in your system, you can add the service to the mcord.yml profile manifest (location: $CORD/build/platform-install/profile_manifests/mcord.yml):
xos_services:
- name: sdncontroller
path: orchestration/xos_services/sdn-controller
keypair: mcord_rsa
In addition, you should add the synchronizer for this service to the docker_images.yml (location: $CORD/build/docker_images.yml):
- name: xosproject/sdncontroller-synchronizer
repo: sdn-controller
path: "xos/synchronizer"
dockerfile: "Dockerfile.synchronizer"
To build the synchronizer as a container, following codes should be written in scenario files, e.g., cord, local, mock, and so on:
docker_image_whitelist: - "xosproject/sdncontroller-synchronizer"
For this, the exact location for each scenario is as follows:
Once you have added the service, you will need to rebuild and redeploy the XOS containers from source.
$ cd $CORD/build $ make xos-teardown $ make clean-openstack $ make clean-profile $ make -j4 build $ make compute-node-refresh