| commit | c4e51b52a167988f46b3f24714f9c734e8fafea2 | [log] [tgz] |
|---|---|---|
| author | Matteo Scandolo <teo@opennetworking.org> | Fri Feb 02 08:51:33 2018 -0800 |
| committer | Matteo Scandolo <teo@opennetworking.org> | Fri Feb 02 09:31:51 2018 -0800 |
| tree | 8be60bda375f5301c795c75529dafd30f8fc01bd | |
| parent | fd8196d373cc5ac3eb0c191ef5b916cf2fa7193d [diff] |
[CORD-2687] Removing old tosca engine pieces Change-Id: I6fa54ae4d17e9b1d9e69face2f46475ac900d1e9
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