| commit | 033b2ce6d35ffa5d27e4e5f5996ee94038ded1ee | [log] [tgz] |
|---|---|---|
| author | Woojoong Kim <woojoong@opennetworking.org> | Tue Oct 10 10:09:06 2017 -0700 |
| committer | Pingping Lin <pingping@onlab.us> | Mon Oct 16 15:58:17 2017 -0700 |
| tree | 080c07a51b0d2b8f29961d09216855f4875fcf48 | |
| parent | e30f6062c23f88fd89349d00f04a845a519cd64a [diff] |
[CORD-2031] Migration of vHSS service to 4.1 Change-Id: Iaab41b6cbfa8fb5036ae04bb9f30f3a55bcdbd1e (cherry picked from commit c8c6ddd43f0657c2146ac4a8b5ff03141b6375db)
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