| commit | 144b09a89a821c743779dc2a875714ef4a4fd9e0 | [log] [tgz] |
|---|---|---|
| author | Andy Bavier <andy@onlab.us> | Mon Feb 12 16:15:22 2018 -0700 |
| committer | Andy Bavier <andy@onlab.us> | Mon Feb 12 16:36:41 2018 -0700 |
| tree | 6b7517f1a1a3911e4567cd0a4574716e49dd98a1 | |
| parent | 2e973ea17cac3b861e3ee2ad879aa922f96bf36b [diff] |
CORD-2724 Enable binding VMs to nodes via node_label Change-Id: Iac5f0e26f57aba4cfea93ab3a3588d40c4c8e2c8
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