| commit | 1778656df551a26fee7c287a7188bf9d04005f98 | [log] [tgz] |
|---|---|---|
| author | Woojoong Kim <woojoong@opennetworking.org> | Mon Oct 16 17:00:51 2017 -0700 |
| committer | Pingping Lin <pingping@onlab.us> | Wed Oct 18 17:14:38 2017 -0700 |
| tree | 94dd6ee748616ce3e5be84e6e8aeeafe161c40e5 | |
| parent | efd926ecc78b183b869805b2315f3594ca5eac4d [diff] |
[CORD-2088] Create a new service, sdn-controller, for vSPGW Change-Id: Icfecdc3ef9bb3691267a35644a5d5d1930a63a6f (cherry picked from commit 8400e1151753e263b0fa3c506ffcba8c5bdca1b6)
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