| commit | 847d250983ad356ab7c24d6b15c2851609693a0b | [log] [tgz] |
|---|---|---|
| author | Zack Williams <zdw@opennetworking.org> | Tue Jul 03 22:20:35 2018 -0700 |
| committer | Zack Williams <zdw@opennetworking.org> | Tue Jul 03 22:20:35 2018 -0700 |
| tree | 1167fadce46573b6c8f7ff8fd9aeb823b1ffbbef | |
| parent | 1d8075465a179691e6c2b52b46d8780f2edd2254 [diff] |
Release v1.0.0 Change-Id: Id91643162c8dfc3fe67b388a609a84e51541a915
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