| commit | 10395813929c768565c8842518d826d4675d9e58 | [log] [tgz] |
|---|---|---|
| author | Woojoong Kim <woojoong@opennetworking.org> | Fri Feb 16 11:53:46 2018 -0800 |
| committer | Woojoong Kim <woojoong@opennetworking.org> | Tue Mar 13 22:08:41 2018 +0000 |
| tree | 9dcb7b201f8518004518e86115c6e765c04b8ea3 | |
| parent | fa46ce11b8e39774d180ad0c51679edace3bcf3c [diff] |
add host name in hosts to resolve sudo timeout Change-Id: I13faa63657eb2c44b0010f18fcdafe240b23ed62 (cherry picked from commit cc12aebb0311eef05d490612c3aecaedfe2d1123)
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