summaryrefslogtreecommitdiffstats
path: root/roles/ControllerOpenstack.yaml
AgeCommit message (Collapse)AuthorFilesLines
2017-07-27Add 'ovn-controller' serviceNuman Siddique1-0/+1
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-25Adding Tuned ServiceJoe Talerico1-0/+1
Allow the user to set a specific Tuned profile on a given host. Defaults to throughput-performance Change-Id: I0c66193d2733b7a82ad44b1cd0d2187dd732065a
2017-07-17Refactor iscsi initiator-name reset into separate serviceOliver Walsh1-0/+1
This currently assumes nova-compute and iscsid run in the same context which isn't true for a containerized deployment Change-Id: I11232fc412adcc18087928c281ba82546388376e Depends-On: I91f1ce7625c351745dbadd84b565d55598ea5b59 Depends-On: I0cbb1081ad00b2202c9d913e0e1759c2b95612a5
2017-06-14Add a docker-ha.yaml environment file for containerized HA deploymentsMichele Baldessari1-0/+1
This adds a docker-ha.yaml that can be passed to the deployment environments in order to get a containerized HA deployment. Until we make the containerized deplyment the default the operator must first include docker.yaml and *then* docker-ha.yaml in order to get a containerized overcloud with an HA control plane. We also make sure that the ClusterCheck service is set to None by default and is part of the Controller roles. Change-Id: I13204d70aad8dfeaf2bcf2ae30a1bb4715167659
2017-06-13Make network-isolation environment rendered for all rolesSteven Hardy1-0/+6
Currently there's some hard-coded references to roles here, rendering from the roles_data.yaml is a step towards making the use of isolated networks for custom roles easier. Partial-Bug: #1633090 Depends-On: Ib681729cc2728ca4b0486c14166b6b702edfcaab Change-Id: If3989f24f077738845d2edbee405bd9198e7b7db
2017-06-07Standardize example role definitionsAlex Schultz1-0/+98
As we create new standard roles, we should include them from a single location for ease of use and to reduce the duplication of the role definitions elsewhere. This change adds a roles folder to the THT that can be used with the new roles commands in python-tripleoclient by the end user to generate a roles_data.yaml from a standard set of roles. Depends-On: I326bae5bdee088e03aa89128d253612ef89e5c0c Change-Id: Iad3e9b215c6f21ba761c8360bb7ed531e34520e6 Related-Blueprint: example-custom-role-environments