| commit | ee4918b8dd2966a880f694e577bfcb876830f164 | [log] [tgz] |
|---|---|---|
| author | Matteo Scandolo <teo@opennetworking.org> | Fri Feb 02 08:51:45 2018 -0800 |
| committer | Matteo Scandolo <teo@opennetworking.org> | Fri Feb 02 09:32:16 2018 -0800 |
| tree | cce2989e1325fb15da67335648db09c3b4b318d7 | |
| parent | f1a24ecc3cba82e9a61651e9ed59f3abfd83b334 [diff] |
[CORD-2687] Removing old tosca engine pieces Change-Id: If1b048f872b5946fa3a4130219174857eb927e63
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