| tag | 508a0212ea8baf9e30880ae41011ec4541e4d747 | |
|---|---|---|
| tagger | Jenkins <do-not-reply@opencord.org> | Thu Sep 27 22:24:51 2018 +0000 |
| object | 4ebeee9c00edf3f65914dceb181ba65cbe347f69 |
Tagged by CORD Jenkins version-tag job: 476, for Gerrit patchset: 11176
| commit | 4ebeee9c00edf3f65914dceb181ba65cbe347f69 | [log] [tgz] |
|---|---|---|
| author | Zack Williams <zdw@opennetworking.org> | Tue Sep 25 16:08:50 2018 -0700 |
| committer | Zack Williams <zdw@opennetworking.org> | Tue Sep 25 16:08:50 2018 -0700 |
| tree | 67593e6a1273c4794420b82bc519343ed4843e5d | |
| parent | dca71c13bad03036c9daabece67fabc237ae378f [diff] |
Update VERSION and XOS parent container Change-Id: I14917af57caebff96c038db8cedf79e10d9d41aa
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