aboutsummaryrefslogtreecommitdiffstats
path: root/roles/Controller.yaml
AgeCommit message (Collapse)AuthorFilesLines
2017-07-17Add composable services for the Veritas HyperScale.abhishek.kane1-0/+1
Add a composable service for each of: - the Veritas HyperScale's Cinder backend. - installing the Veritas HyperScale controller packages. Change-Id: I99ee827825ec2a6a3c695de1ca1c1015859fe398 Depends-On: I316b22f4f7f9f68fe5c46075dc348a70e437fb1d Depends-On: I9168bffa5c73a205d1bb84b831b06081c40af549 Signed-off-by: abhishek.kane <abhishek.kane@veritas.com>
2017-07-07Add in roles data validationAlex Schultz1-1/+1
With the merging of Iad3e9b215c6f21ba761c8360bb7ed531e34520e6 the roles_data.yaml should be generated with tripleoclient rather than edited. This change adds in a pep8 task to verify that the appropriate role files in roles/ have been modified to match how our default roles_data.yaml is constructed. Additionally this change adds a new tox target called 'genrolesdata' that will all you to automatically generate roles_data.yaml and roles_data_undercloud.yaml Change-Id: I5eb15443a131a122d1a4abf6fc15a3ac3e15941b Related-Blueprint: example-custom-role-environments
2017-07-04Enable Neutron LBaaS IntegrationRyan Hefner1-0/+1
Allows the configuration of the Neutron LBaaS agent. Implements: blueprint lbaasv2-service-integration Change-Id: Iae2bf7faeea93d5275994b2ee10f9bf863ed6152 Depends-On: Ieeb21fafd340fdfbaddbe7633946fe0f05c640c9
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-14Merge "Move iscsid to a container"Jenkins1-0/+1
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-12Move iscsid to a containerDan Prince1-0/+1
This configures iscsid so that it runs as a container on relevant roles (undercloud, controller, compute, and volume). When the iscsid docker service is provision it will also run an ansible snippet that disables the iscsid.socket on the host OS thus disabling the hosts systemd from auto-starting iscsid as it normally does. Co-Authored-By: Jon Bernard <jobernar@redhat.com> Change-Id: I2ea741ad978f166e199d47ed1b52369e9b031f1f
2017-06-07Standardize example role definitionsAlex Schultz1-0/+120
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