History

Numan Siddique 5f313f27c9 Add 'ovn-controller' service Presently the ovn-controller service (puppet/services/neutron-compute-plugin-ovn.yaml) is started only on compute nodes. But for the cases where the controller nodes provide the north/south traffic, we need ovn-controller service runninng in controller nodes as well. This patch - Renames the neutron-compute-plugin-ovn.yaml to ovn-controller.yaml which makes more sense and sets the service name as 'ovn-controller'. - Adds the service 'ovn-controller' to Controller and Compute roles. - Adds the missing 'upgrade_tasks' section in ovn-dbs.yaml and ovn-controller.yaml Depends-On: Ie3f09dc70a582f3d14de093043e232820f837bc3 Depends-On: Ide11569d81f5f28bafccc168b624be505174fc53 Change-Id: Ib7747406213d18fd65b86820c1f86ee7c39f7cf5		2017-07-27 18:22:03 +00:00
..
common	Disable network validation in multinode jobs	2017-07-08 14:49:42 +00:00
environments	Add 'ovn-controller' service	2017-07-27 18:22:03 +00:00
pingtests	CI/scenarios : Add scenario007 for OVN services	2017-07-23 14:11:26 +00:00
scripts	Setup FreeIPA to serve DNS in the setup script	2017-02-15 15:21:53 +02:00
README.rst	Fix grammar	2016-11-29 21:49:18 -05:00

README.rst

TripleO CI environments

TripleO CI environments are exclusively used for Continuous Integration purpose or for development usage. They should not be used in production and we don't guarantee they work outside TripleO CI.

For more informations about TripleO CI, please look: https://github.com/openstack-infra/tripleo-ci