| commit | 855fbc32925e66a9ed307d3c3a0ad5e19f29be66 | [log] [tgz] |
|---|---|---|
| author | Sapan Bhatia <sapan@opennetworking.org> | Fri Jan 05 00:14:27 2018 +0000 |
| committer | Gerrit Code Review <gerrit@opencord.org> | Fri Jan 05 00:14:27 2018 +0000 |
| tree | 1931d43c591d4be20675fa63a90c4af288ccad70 | |
| parent | 78246f2d8f7a687d59cb9c01499d0b4456348043 [diff] | |
| parent | 4b906af327cd1e106e6696af76060d97fce13c77 [diff] |
Merge "CORD-2467: Start filebeat in synchronizer containers"
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