Adding Code of Conduct

Change-Id: I93c1dfc2e66a5695c397cb7010514ab02c1991be
2 files changed
tree: 5925e9fbaccff2e678aa5415db3e011a3d981c48
  1. .gitreview
  2. CODE_OF_CONDUCT.md
  3. Dockerfile.synchronizer
  4. LICENSE.txt
  5. README.md
  6. VERSION
  7. xos/
README.md

sdn-controller Service for vSPGW in Intel EPC

Onboarding

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:

  • for CORD scenario: $CROD/build/scenarios/cord/config.yml
  • for Local scenario: $CROD/build/scenarios/local/config.yml
  • for Mock scenario: $CROD/build/scenarios/mock/config.yml
  • for Opencloud scenario: $CROD/build/scenarios/opencloud/config.yml
  • for Single scenario: $CROD/build/scenarios/single/config.yml

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