| commit | bf74e13f0ae07e008090f015fdabf5f405c5e137 | [log] [tgz] |
|---|---|---|
| author | Zack Williams <zdw@opennetworking.org> | Tue Sep 25 16:07:35 2018 -0700 |
| committer | Zack Williams <zdw@opennetworking.org> | Tue Sep 25 16:07:35 2018 -0700 |
| tree | ddfd7f8af476f833c250100ee87fb6b33438747d | |
| parent | 847d250983ad356ab7c24d6b15c2851609693a0b [diff] |
Update VERSION and XOS parent container Change-Id: Ie0b1de18e7c31e638ace7047b8d547373175177f
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