| commit | 726d1528bb8db05a519995efcb0f58c656ea4bd1 | [log] [tgz] |
|---|---|---|
| author | Zack Williams <zdw@opennetworking.org> | Thu Nov 01 11:13:27 2018 -0700 |
| committer | Zack Williams <zdw@opennetworking.org> | Thu Nov 01 11:13:27 2018 -0700 |
| tree | 2b362c11b5e988b347a66b53c0b79fe74ed76615 | |
| parent | bf74e13f0ae07e008090f015fdabf5f405c5e137 [diff] |
Updated service to use new XOS core version: 2.1.22 Change-Id: I82ae028d313675584cc6726546130daa7c71627e
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