| commit | f1a24ecc3cba82e9a61651e9ed59f3abfd83b334 | [log] [tgz] |
|---|---|---|
| author | Sapan Bhatia <gwsapan@gmail.com> | Wed Jan 03 14:22:20 2018 -0500 |
| committer | Sapan Bhatia <gwsapan@gmail.com> | Wed Jan 03 17:15:13 2018 -0500 |
| tree | c90ee843f02238fe3454eece542f822f9c92c7ab | |
| parent | 1778656df551a26fee7c287a7188bf9d04005f98 [diff] |
CORD-2467: Start filebeat in synchronizer containers Change-Id: I3fb5807f053f85bdadfd4a9e8229a3d2ca77705b
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: sdncontroller
path: orchestration/xos_services/sdn-controller
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/sdncontroller-synchronizer
repo: sdn-controller
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/sdncontroller-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