summaryrefslogtreecommitdiffstats
path: root/environments
AgeCommit message (Collapse)AuthorFilesLines
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-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-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
2017-06-12Merge "Fix typo in haproxy docker mapping"Jenkins1-1/+1
2017-06-12Fix IronicInspectorAdmin to be httpsAlex Schultz1-2/+2
As noted in the original patch review I5e743f789ab7dd731bc7ad26226a92a4e71f95a1 the IronicInspectorAdmin should be https. Change-Id: I6e37427da679775f02ff0c5fe55cfee51c122e3d
2017-06-12Add nested sample environments for inject-trust-anchorBen Nemec4-0/+50
Fix a bug that prevented these working. A unit test and documentation for the nested environment functionality is also included. Change-Id: I2d4aeb584eb624178d601cfd6bc0a6473cb5289f
2017-06-12Add storage sample environmentsBen Nemec10-3/+304
Starts converting storage-related sample environments to the tool, and adds a few new ones for demonstration purposes. This has required the addition of a new category of parameter overrides in the tool. There are some parameters that are part of the public API of roles that should not normally be included in a sample environment for that role. Examples are EndpointMap and ServiceNetMap. Those are both passed into most (all?) roles, but their template defaults are not useful (both default to {}). Unless we are explicitly creating a sample environment that overrides those defaults we don't want them included. Parameters such as RoleName and RoleParameters are similar. We can't change them because they are part of the composable roles interface and that would break any existing custom roles, but we don't really want them included normally either. It's possible these could be made completely private, but there have been some very preliminary discussions about generating role samples that might actually want to set them. In order to avoid issues with editing the unit test file in editors that strip trailing whitespace, the minor formatting bug where params like EndpointMap had a trailing space after the name has also been fixed. Change-Id: If11f30c734bfbc17d463a9890c736d7477186fb9
2017-06-12Add neutron-midonet sample environmentBen Nemec2-0/+70
Change-Id: I34d3a9356b119d549acd6fe4f0c8713b0bfa5957
2017-06-12Support config dir for env generator input filesBen Nemec7-0/+445
We're not going to want to list every single sample environment in a single file, so let's also take a directory and just read every yaml file in it. This commit adds support for that as well as some initial environments to demonstrate its use. Change-Id: If2c608f2a61fc5e16784ab594d23f1fa335e1d3c
2017-06-12Sample environment generatorBen Nemec1-0/+33
This is a tool to automate the generation of our sample environment files. It takes a yaml file as input, and based on the environments defined in that file generates a number of sample environment files from the parameters in the Heat templates. A tox genconfig target is added that mirrors how the other OpenStack services generate their sample config files. A description of the available options for the input file is provided in a README file in the sample-env-generator directory. In this commit only a single sample config is provided as a basic example of how the tool works, but subsequent commits will add more generated sample configs. Change-Id: I855f33a61bba5337d844555a7c41b633b3327f7a bp: environment-generator