| commit | fa46ce11b8e39774d180ad0c51679edace3bcf3c | [log] [tgz] |
|---|---|---|
| author | Scott Baker <smbaker@gmail.com> | Tue Mar 06 18:36:50 2018 -0800 |
| committer | Scott Baker <smbaker@gmail.com> | Tue Mar 06 18:36:50 2018 -0800 |
| tree | 4c57a8aa51995174571e6460001337ec90b04590 | |
| parent | 144b09a89a821c743779dc2a875714ef4a4fd9e0 [diff] |
CORD-2509 migrate vhss service from static to dynamic load Change-Id: I07559484ec184ae454469d32aff2fd07162d96b4
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