| commit | 2252da4c081f13350a409e909bcc4c024faef689 | [log] [tgz] |
|---|---|---|
| author | Pingping Lin <pingping@onlab.us> | Tue May 29 17:48:37 2018 -0700 |
| committer | Pingping Lin <pingping@onlab.us> | Tue May 29 18:36:03 2018 -0700 |
| tree | 6a2613edf5e234e74915b6a0116a97315a01e6a7 | |
| parent | de702003d7ad428d1fea2209cc971f765d5cd06b [diff] |
move dockerfile location & add version Change-Id: I23ceca3153231e771c6a248d769a6809ac88f9ae
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