| commit | fd8196d373cc5ac3eb0c191ef5b916cf2fa7193d | [log] [tgz] |
|---|---|---|
| author | Andy Bavier <andy@onlab.us> | Sat Jan 20 10:44:53 2018 -0700 |
| committer | Andy Bavier <andy@onlab.us> | Sat Jan 20 10:46:28 2018 -0700 |
| tree | dc785577741ab9090863eb33f301338e8b536ef9 | |
| parent | 03905bc417bc043c48e4f607ae6b6b533e1ec34f [diff] |
Fix synchronizer hanging Change-Id: Idbe822f9a37afe8e657368f9d3086a03e312888b
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