aboutsummaryrefslogtreecommitdiffstats
path: root/environments
AgeCommit message (Collapse)AuthorFilesLines
2017-06-26Add non-ha env file.Carlos Camacho1-0/+16
This environment file will be used to deploy an Overcloud without the use of pacemaker. Change-Id: I3a486d22b30ffdb6053b3d917dea373c1361df81
2017-06-25Temporarily disable containerized cinderMartin André1-2/+2
The containerized cinder service was merged a bit too soon and it caused several issues in CI. Disable it temporarily to unblock CI until it matures. Change-Id: I8c6c0ce0011fddfec1e2de798d4fc6f34ae78de2 Related-Bug: #1700333
2017-06-23Enable periodic task to discover cell hosts when ironic is usedDmitry Tantsur1-0/+2
Starting with the Ocata release, bare metal nodes are no longer get recognized by nova automatically. To avoid forcing users into running nova manage command each time they enroll a node, we will have to allow enable the periodic task to do so. Change-Id: I8b0afac54dc9bd51dbe2ae4f237e4de50459be0f Closes-Bug: #1697724
2017-06-23Merge "Configuration for containerized MySQL clients"Jenkins1-0/+1
2017-06-20Merge "Comment parameters for registry in docker tls env"Jenkins1-4/+4
2017-06-19Merge "Add nested sample environments for inject-trust-anchor"Jenkins4-0/+50
2017-06-19Merge "Add storage sample environments"Jenkins10-3/+304
2017-06-19Merge "Add neutron-midonet sample environment"Jenkins2-0/+70
2017-06-19Merge "Support config dir for env generator input files"Jenkins7-0/+445
2017-06-19Comment parameters for registry in docker tls envMartin André1-4/+4
This commit brings change from I3896fa2ea7caa603186f0af04f6d8382d50dd97a to docker-services-tls-everywhere.yaml, which original commit message was: These duplicate the defaults in puppet/services/docker.yaml and break things if you include an environment file (e.g that generated by quickstart containers-default-parameters.yaml) before the docker.yaml. Instead it's probably more helpful to include the commented lines showing how to enable use of a local docker registry. Change-Id: Ifa95ef60bc17bd2638ebb6aebf77a819b28c9f0b Related-Bug: #1691524
2017-06-19Re-enable docker service in docker.yamlMartin André1-0/+2
It was removed by mistake from the docker.yaml environment file in I76f188438bfc6449b152c2861d99738e6eb3c61b. Change-Id: If8df98e1ddd0961ab0c9e5df917fef8200db65e6 Closes-Bug: #1698749
2017-06-17Merge "Remove duplicate docker/puppet services.yaml"Jenkins2-5/+0
2017-06-16Merge "Fall back to non-containerized cinder-backup to unblock OVB CI"Jenkins1-2/+2
2017-06-16Merge "Add Ec2Api to container based deployment"Jenkins1-0/+2
2017-06-16Merge "Add templates to configure Ironic inspector"Jenkins1-0/+2
2017-06-16Merge "Fall back to non-containerized cinder-volume to unblock CI"Jenkins1-1/+2
2017-06-16Fall back to non-containerized cinder-backup to unblock OVB CIJiri Stransky1-2/+2
The previous fix Ib10e4f18d967d356a15b97f58c488f8402a73356 made multinode CI pass, but there was still an error during volume scheduling on OVB: OSError: [Errno 13] Permission denied: '/var/lib/cinder/conversion' This was most likely due to cinder-volume was running on host and used host's cinder user, while we still deployed containerized cinder-backup and it chowned /var/lib/cinder under kolla's cinder user whose UID doesn't match the baremetal one. We didn't hit this issue in the multinode job because it doesn't presently deploy cinder-backup service at all. Co-Authored-By: Martin André <m.andre@redhat.com> Change-Id: I9ac74d6717533f59945694b4a43fe56d7ca768c6 Closes-Bug: #1698136
2017-06-16Merge "Pacemaker HA suport for OVN DB servers"Jenkins1-0/+24
2017-06-16Fall back to non-containerized cinder-volume to unblock CIJiri Stransky1-1/+2
CI was stuck on collecting logs. The collect-logs playbook, which normally takes just a few minutes, took more than an hour and was eventually killed. The playbook was stuck on collecting LVM info on the overcloud node, which runs this command: (vgs; pvs; lvs) &> /var/log/extra/lvm.txt Therefore it's very likely that the problematic part is the LVM setup in the containerized cinder-volume service, and falling back to non-contianerized for the time being should get the CI going again. Change-Id: Ib10e4f18d967d356a15b97f58c488f8402a73356 Closes-Bug: #1698136
2017-06-16Merge "Remove reference too puppet/services/ironic-pxe.yaml"Jenkins1-1/+0
2017-06-15Add Ec2Api to container based deploymentSven Anderson1-0/+2
Depends-On: I5dc10ef5cccf6d378c20c68fc4a32d2d3c38233f Change-Id: Ib96040c2e27ad76b1fa6ecb9468bb9d97b3c4518
2017-06-15Merge "Containerize Ceilometer Agent Ipmi"Jenkins2-0/+2
2017-06-15Merge "Modify PreNetworkConfig config inline with role-specific parameters"Jenkins2-16/+18
2017-06-15Merge "Containerize Manila Scheduler service"Jenkins1-0/+1
2017-06-14Merge "Update Panko api port"Jenkins3-9/+9
2017-06-14Merge "Sample environment generator"Jenkins1-0/+33
2017-06-14Merge "Add Nova Consoleauth service to containerized deployment"Jenkins1-0/+1
2017-06-14Merge "Add Nova Vncproxy service to containerized deployment"Jenkins1-0/+1
2017-06-14Update Panko api portPradeep Kilambi3-9/+9
The current port conflicts with trove. This is updated in puppet module. See related change: https://review.openstack.org/#/c/471551/ Change-Id: Iefacb98320eef0bca782055e3da5d243993828d7
2017-06-14Merge "Fix network names when using network isolation"Jenkins1-1/+1
2017-06-14Merge "Dell SC: Add exclude_domain_ip option"Jenkins1-0/+1
2017-06-14Merge "Docker service for Cinder Volume"Jenkins1-0/+1
2017-06-14Merge "Docker services for Cinder Backup"Jenkins1-0/+1
2017-06-14Remove reference too puppet/services/ironic-pxe.yamlDerek Higgins1-1/+0
The file doesn't exist. The pxe setup is part of puppet/services/ironic-conductor.yaml Change-Id: I3a6f038ed69ea44f0594064b6f9657ff1b72e1bb Closes-Bug: #1697927
2017-06-14Merge "Docker services for Cinder Api and Scheduler"Jenkins1-0/+2
2017-06-14Fix network names when using network isolationMichele Baldessari1-1/+1
When we merged If3989f24f077738845d2edbee405bd9198e7b7db we correctly used name_lower for most things but we left out the the OS::TripleO::Network resource which would cause errors like the following: Could not fetch contents for file:///tmp/tripleoclient-LdqQGJ/tripleo-heat-templates/network/internalapi.yaml The reason is that the network filename is called internal_api.yaml. Change-Id: I40f268668ed948e5d41ed0ff5a8fc954cef7b17c Closes-Bug: #1697883
2017-06-14Merge "Containerize Sahara"Jenkins1-0/+3
2017-06-14Merge "Containerized Sensu client"Jenkins1-0/+3
2017-06-14Merge "Containerize multipathd"Jenkins1-0/+1
2017-06-14Merge "Move iscsid to a container"Jenkins2-0/+2
2017-06-13Merge "Change HorizonSecureCookies default to False"Jenkins1-0/+1
2017-06-13Containerize Ceilometer Agent IpmiPradeep Kilambi2-0/+2
Depends-On: I3e865f2e9b6935eb3dfa4b4579c803f0127848ae Change-Id: I09327a63d238a130b6ac0f2361f80e2b244b4b52
2017-06-13Merge "Fix IronicInspectorAdmin to be https"Jenkins1-2/+2
2017-06-13Merge "Make network-isolation environment rendered for all roles"Jenkins2-59/+37
2017-06-13Configuration for containerized MySQL clientsDamien Ciabrini1-0/+1
This service generates the /etc/my.cnf.d/tripleo.cnf file which is being used to configured MySQL clients (e.g. client bind address, client SSL configuration...) We generate the config file in this service and let containerized MySQL clients mount /var/lib/config-data/mysql_client/etc/my.cnf.d/tripleo.cnf it in their own container. This way, when this MySQLClient service is updated, the other containers will automatically pick the updated configuration at next restart. Partial-Bug: #1692317 Change-Id: Idc56d27fb9645ad3b07df8ef08b7e2ce29e6d499
2017-06-13Add Nova Vncproxy service to containerized deploymentSven Anderson1-0/+1
Depends-On: I037858a445742de58bd2f8d879f2b1272b07f481 Change-Id: Ifd138ea553a45a637a1a9fe3d0e946f8be51e119
2017-06-13Add Nova Consoleauth service to containerized deploymentSven Anderson1-0/+1
Depends-On: I037858a445742de58bd2f8d879f2b1272b07f481 Change-Id: I808a5513decab1bd2cce949d05fd1acb17612a42
2017-06-13Make network-isolation environment rendered for all rolesSteven Hardy2-59/+37
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-13Unblock CI by reverting to non-containerized HAProxyJiri Stransky1-1/+0
In change I90253412a5e2cd8e56e74cce3548064c06d022b1 we merged containerized HAProxy setup, but because of a typo in resource registry, CI kept using the non-containerized variant and it went unnoticed that the containerized HAProxy doesn't work yet. We merged a resource registry fix in Ibcbacff16c3561b75e29b48270d60b60c1eb1083 and it brought down the CI, which now used the non-working HAProxy. After putting in the missing haproxy container image to tripleo-common in I41c1064bbf5f26c8819de6d241dd0903add1bbaa we got further, but the CI still fails on HAProxy related problem, so we should revert back to using non-containerized HAProxy for the time being. Change-Id: If73bf28288de10812f430619115814494618860f Closes-Bug: #1697645
2017-06-13Modify PreNetworkConfig config inline with role-specific parametersSaravanan KR2-16/+18
Existing host_config_and_reboot.role.j2.yaml is done in ocata to configure kernel args. This can be enhanced with use of role-specific parameters, which is done in the current patch. The earlier method is deprecated and will be removed in Q releae. Implements: blueprint ovs-2-6-dpdk Change-Id: Ib864f065527167a49a0f60812d7ad4ad12c836d1