| commit | 08d2a527390fcfc6db032fd2b893f52ad259fdb6 | [log] [tgz] |
|---|---|---|
| author | Pingping Lin <pingping@onlab.us> | Wed May 30 14:58:19 2018 -0700 |
| committer | Pingping Lin <pingping@onlab.us> | Wed May 30 15:06:24 2018 -0700 |
| tree | c7a1f2f4efd3a34babfe06e2abc309fa55f498c8 | |
| parent | f4d9e61298adb485aa0317179d2204a7038ff42c [diff] |
change location of docker file & add version file Change-Id: If22f97e269b2efc5b89bf23011d5ccda03547be9
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