| commit | 5132077b36e2cbcbce77edad723bdb459afacb31 | [log] [tgz] |
|---|---|---|
| author | Matteo Scandolo <matteo.scandolo@gmail.com> | Fri Nov 22 17:35:26 2019 -0800 |
| committer | Matteo Scandolo <matteo.scandolo@gmail.com> | Mon Dec 16 15:59:45 2019 -0800 |
| tree | 9f3d59c655483626064725a4a59e226f22f10512 | |
| parent | 30419a69c855a87a36ef141abb502adb2da22f4b [diff] |
Adding Code of Conduct Change-Id: I9d13269357c127dce3a4cca540f946846f643fbe
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: vhss
path: orchestration/xos_services/vhss
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/vhss-synchronizer
repo: vHSS
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/vhss-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