| commit | 4b906af327cd1e106e6696af76060d97fce13c77 | [log] [tgz] |
|---|---|---|
| author | Sapan Bhatia <gwsapan@gmail.com> | Wed Jan 03 14:22:21 2018 -0500 |
| committer | Sapan Bhatia <gwsapan@gmail.com> | Wed Jan 03 17:15:14 2018 -0500 |
| tree | 00f08705afebd81bf30cad0e137909dbcce25a60 | |
| parent | 033b2ce6d35ffa5d27e4e5f5996ee94038ded1ee [diff] |
CORD-2467: Start filebeat in synchronizer containers Change-Id: Ic863f33c38e5d0c5a12bd292b1f149275e749d5d
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