| commit | 1d8075465a179691e6c2b52b46d8780f2edd2254 | [log] [tgz] |
|---|---|---|
| author | Kailash Khalasi <kailash@onlab.us> | Tue Jul 03 11:23:08 2018 -0700 |
| committer | Kailash Khalasi <kailash@onlab.us> | Tue Jul 03 11:23:52 2018 -0700 |
| tree | 8bec85432645d22b8db4fb3864eb02ddf96bedda | |
| parent | 31510df6c8a1188fd93b01d75512a78575d0505c [diff] |
CORD-3194 making service name lowercase Change-Id: I8c893d7c8936ab00d3c086231d6e63665b7cc968
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