| commit | 03905bc417bc043c48e4f607ae6b6b533e1ec34f | [log] [tgz] |
|---|---|---|
| author | Andy Bavier <andy@onlab.us> | Wed Jan 17 15:49:00 2018 -0700 |
| committer | Andy Bavier <andy@onlab.us> | Fri Jan 19 17:00:29 2018 -0700 |
| tree | 7695d825d85b814acc5ffe23a26015a41aaac8b2 | |
| parent | 855fbc32925e66a9ed307d3c3a0ad5e19f29be66 [diff] |
CORD-2409 HSS playbook Change-Id: Ie7150633966908bf260d834f0ac7ffc9f34e20f4
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