commit | 96a7ca598fe0d1f562ead30e61ff3a3cbd4d15ff | [log] [tgz] |
---|---|---|
author | Woojoong Kim <woojoong@opennetworking.org> | Tue Feb 13 19:00:43 2018 -0800 |
committer | Woojoong Kim <woojoong@opennetworking.org> | Tue Feb 13 19:02:10 2018 -0800 |
tree | 30abdef2eed4704faf1fd6617924c1f5775bd8c7 | |
parent | f18ea72a3a44d3bf11dec07a455bb50e47372368 [diff] |
change hss playbook according to new HSS image Change-Id: I69cc17883351e364e5ab71c9cb0cbf46ff963fd8
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