| commit | f18ea72a3a44d3bf11dec07a455bb50e47372368 | [log] [tgz] |
|---|---|---|
| author | Woojoong Kim <woojoong@opennetworking.org> | Sun Feb 04 16:26:55 2018 -0800 |
| committer | Woojoong Kim <woojoong@opennetworking.org> | Sun Feb 04 16:26:55 2018 -0800 |
| tree | af77af52bd67b71cef09cbaa89283ab01e177579 | |
| parent | 2e973ea17cac3b861e3ee2ad879aa922f96bf36b [diff] |
Change version Change-Id: I6c3f7675d844e38c0488905552a8ccfdf00b2066
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