aboutsummaryrefslogtreecommitdiffstats
path: root/environments
AgeCommit message (Collapse)AuthorFilesLines
2017-06-30New environment file to configure containers.Ian Main1-0/+109
This is part of a larger series that changes the interface used for configuring which containers are used. This needs CI and possibly quickstart updates to use this environment file so CI will continue to pass. Change-Id: I125137ba45f608cf84ea0a7146edd744a549d23b Co-Authored-By: Dan Prince <dprince@redhat.com>
2017-06-30Merge "cisco nexus: keep OVS on the Compute"Jenkins1-1/+0
2017-06-30Merge "Add a docker-ha.yaml environment file for containerized HA deployments"Jenkins1-0/+22
2017-06-29cisco nexus: keep OVS on the ComputeGonéri Le Bouder1-1/+0
The Cisco Nexus-UCSM environment relies on OVS for the communication with compute nodes. This is a partial revert of I4c98008107568b3b65decd7640e25c7d2b1ea9ff. Change-Id: I453d4bc83314a76fd779884fb2f8cd1731d2bcaa Related-Bug: #1687597
2017-06-29Install ansible-pacemaker on O->P upgradeJiri Stransky1-0/+2
This has been omitted in Ocata image, so we need to install this in O->P upgrade again. Change Ic8ce72133c47a4c90d581a0925213877b11a471e adds it to the image, so that we can stop installing it on P->Q upgrade, and start using it for minor updates too. Change-Id: I893792e8d82c716b2f3e7b8878b25ba89ea724f1 Co-Authored-By: Marius Cornea <mcornea@redhat.com> Partial-Bug: #1701208
2017-06-27Merge "Add docker templates for octavia services"Jenkins1-0/+5
2017-06-27Merge "Add non-ha env file."Jenkins1-0/+16
2017-06-27Merge "Adds service for OVS and enables ODL DPDK deployments"Jenkins2-12/+62
2017-06-26Merge "Add split-stack environments"Jenkins2-0/+26
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-26Add docker templates for octavia servicesSteven Hardy1-0/+5
Depends-On: I270f3f6879737fc29370165e4a8fa8c9c19fffb3 Depends-On: I3a169e3321a26ee373ab873426a2d58acbcfe1bd Closes-Bug: #1668932 Co-Authored-By: Or Idgar <oidgar@redhat.com> Co-Authored-By: Brent Eagles <beagles@redhat.com> Co-Authored-By: Martin André <m.andre@redhat.com> Change-Id: I211707072bb0e4ac4aa48e9bbaccb7530f3de0ca
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-23Adds service for OVS and enables ODL DPDK deploymentsTim Rozet2-12/+62
In order to deploy OpenDaylight with DPDK we need to copy the DPDK config for OVS done in the neutron-ovs-dpdk service template, without enabling OVS agent for compute nodes. To do this correctly, we should inherit and openvswitch service which is a common place to set OVS configuration and parameters. Note: vswitch::dpdk config will be called in prenetwork setup with ovs_dpdk_config.yaml so there is no need to include that in the step config for neutron-ovs-dpdk-agent service or opendaylight-ovs-dpdk. Changes Include: - Creates a common openvswitch service template, which in the future will migrate to be its own service. - Renames and fixes OVS DPDK configuration heat parameters in the openvswitch template. - neutron-ovs-dpdk-agent now inherits the common openvswitch template. - Adds opendaylight-ovs-dpdk template which also inherits common ovs template. - Uses OVS DPDK config script to allow configuring OVS DPDK in prenetwork config (before os-net-config runs). This has an issue where hieradata is not present yet, so we have to redefine the heat parameters and pass them via bash. In the future this should be corrected. - Adds opendaylight-dpdk environment file used to deploy an ODL + DPDK deployment. - Updates neutron-ovs-dpdk environment file. Closes-Bug: 1656097 Partial-Bug: 1656096 Depends-On: I3227189691df85f265cf84bd4115d8d4c9f979f3 Change-Id: Ie80e38c2a9605d85cdf867a31b6888bfcae69e29 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-06-20Update cinder-netapp-config environmentBen Nemec1-0/+8
It appears some new parameters were added to this template, so the sample environment needs to be updated to include them. Change-Id: Ifc68cbf7d18acf72d6d1ed2beefbc0cd18d72bf8
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 split-stack environmentsJames Slagle2-0/+26
Add 2 new environments to faciltate deploying split-stack: environments/overcloud-baremetal.j2.yaml environments/overcloud-services.j2.yaml The environments are used to deploy 2 separate Heat stacks, one for just the baremetal+network configuration and one for the service configuration. In order to keep Heat's view of the server's hostname consistent across the 2 stacks the 2 environments set the same HostnameFormat with "overcloud" as the stack name. implements blueprint split-stack-default Change-Id: I0b3f282c08af6fecea8f136908b806db70bada46
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-14Add a docker-ha.yaml environment file for containerized HA deploymentsMichele Baldessari1-0/+22
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 "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