| commit | 3f61a7224e5367e44af856d9fb39da0d3cd5b511 | [log] [tgz] |
|---|---|---|
| author | Matteo Scandolo <matteo.scandolo@gmail.com> | Fri Nov 22 17:34:56 2019 -0800 |
| committer | Matteo Scandolo <matteo.scandolo@gmail.com> | Mon Dec 16 15:52:54 2019 -0800 |
| tree | 5925e9fbaccff2e678aa5415db3e011a3d981c48 | |
| parent | 726d1528bb8db05a519995efcb0f58c656ea4bd1 [diff] |
Adding Code of Conduct Change-Id: I93c1dfc2e66a5695c397cb7010514ab02c1991be
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