| commit | 1815195327a505042d93c019ba9d8289099e42bd | [log] [tgz] |
|---|---|---|
| author | Matteo Scandolo <teo@opennetworking.org> | Tue Jun 12 14:04:32 2018 -0700 |
| committer | Matteo Scandolo <teo@opennetworking.org> | Thu Jun 14 08:56:09 2018 -0700 |
| tree | 1767d8ec0cae66f95281ddfb85b76b912788f8a5 | |
| parent | 2252da4c081f13350a409e909bcc4c024faef689 [diff] |
[CORD-3022] Splitting config and removing unused files Change-Id: I4d88142896efe3ceff34f0826f36223f29a47687
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