summaryrefslogtreecommitdiffstats
path: root/environments
AgeCommit message (Collapse)AuthorFilesLines
2016-09-17Merge "Add fluentd client service"Jenkins1-0/+29
2016-09-17Merge "Add NetApp Manila driver integration and tidy up generic"Jenkins2-7/+36
2016-09-17Add fluentd client serviceLars Kellogg-Stedman1-0/+29
This implements support for installing fluentd agents as a composable service on the overcloud. Depends-On: I2e1abe4d8c8359e56ff626255ee50c9cacca1940 Implements: tripleo-opstools-centralized-logging Change-Id: I23b0e23881b742158fcfb6b8c145a3211d45086e
2016-09-16Merge "Add hyperconverged-ceph environment to include CephOSD on computes"Jenkins1-0/+12
2016-09-13Add NetApp Manila driver integration and tidy up genericmarios2-7/+36
Enables configuring a NetApp backend for the Manila service This was created based on the review at https://review.openstack.org/#/c/188138/ This makes the netapp and generic backends disabled by default in the services/manila-backend-*.yaml. A backend is then enabled via backend-specific environment files, which will set any config parameters and enable that backend. It is expected that multiple manila backend specific environment files might be specified simultaneously. Finally generic and manila config is split into separate service files rather than using manila-base for all the things. Co-Authored-By: Ryan Hefner <rhefner@redhat.com> Co-Authored-By: Ben Swartzlander <ben@swartzlander.org> Closes-Bug: 1618479 Depends-On: Ic6f8e8d27ca20b9badddea5d16550aa18bff8418 Change-Id: I35fce32d0f6a5cc1c3382c2d0e0d6028928fd943
2016-09-10Add support for deploying Ceph RGW roleKeith Schincke3-0/+11
This patch add support for deploying Ceph RGW. Co-Authored-By: Giulio Fidente <gfidente@redhat.com> Change-Id: I88c8659a36c2435834e8646c75880b0adc52e964
2016-09-08Merge "Create entries for overcloud VIPs in /etc/hosts"Jenkins1-0/+5
2016-09-07Merge "OVN heat templates"Jenkins1-0/+18
2016-09-07Create entries for overcloud VIPs in /etc/hostsJuan Antonio Osorio Robles1-0/+5
This will aid us in using FQDNs instead of IPs if DNS is not set. If the deployer already has DNS set up, they can easily disable this profile by adding the use-dns-for-vips.yaml environment file. bp tls-via-certmonger Change-Id: I8c1b3f253d0149d575171c208f9a1342a7b26450 Depends-On: I1bdb2701dfb3e7ef072e674c9882d3be5af7296c
2016-09-06Merge "Update OpenContrail loadbalancer plugin value"Jenkins1-1/+1
2016-09-06Merge "Add missing reference to ExternalPort for DVR"Jenkins1-0/+7
2016-09-06Update OpenContrail loadbalancer plugin valueEmilien Macchi1-1/+1
Update OpenContrail loadbalancer plugin value to match with Newton changes. Closes-Bug: #1620657 Change-Id: I48f1884b95e590c0588c52419ec152bd08bc3992
2016-09-06Merge "Added environment file for SR-IOV deployment"Jenkins1-0/+22
2016-09-03Merge "Set NeutronL3HA to false when deploying DVR"Jenkins1-0/+8
2016-09-01OVN heat templatesBabu Shanmugam1-0/+18
Installs and configures OVN databases and process and also configures the neutron plugin for OVN. Implements: blueprint tripleo-ovn Change-Id: Ic3e415bb0587dd85b71f6c14a96f6b2c86a7b30f
2016-09-01Added environment file for SR-IOV deploymentkarthik s1-0/+22
Change-Id: I9afb1d57d08504346f669239ab3d9cce100c7655 Implements: blueprint tripleo-sriov Signed-off-by: karthik s <ksundara@redhat.com>
2016-08-31Add missing reference to ExternalPort for DVRBrent Eagles1-0/+7
Neutron DVR requires the OS::TripleO::Compute::Ports::ExternalPort to be set to a valid port on the external network. Change-Id: I46b96dba3e264e0e79f7f0cea83b0f66775d6d2a Closes-Bug: 1618611
2016-08-31Availability monitoring agents supportMartin Mágr1-0/+30
- adds possibility to install sensu-client on all nodes - each composable service has it's own subscription Co-Authored-By: Emilien Macchi <emilien@redhat.com> Co-Authored-By: Michele Baldessari <michele@redhat.com> Implements: blueprint tripleo-opstools-availability-monitoring Change-Id: I6a215763fd0f0015285b3573305d18d0f56c7770
2016-08-30Added DPDK environment file and nic configs samplesSaravanan KR1-0/+18
Added an environment file to configure DPDK with OVS by overriding ComputeNeutronOvsAgent. Also added nic configs for configuring DPDK bridge and bond with numbered nic format. Implements: blueprint tripleo-ovs-dpdk Co-Authored-By: Vijay Chundury <vchundur@redhat.com> Change-Id: I82b6f66394a8928f8524706c939508edd08afa9b
2016-08-29Add hyperconverged-ceph environment to include CephOSD on computesGiulio Fidente1-0/+12
This would be useful to test Ceph in CI without a dedicated OSD node. Change-Id: Ie534d327a9418b6119f5811ee62d448795879fb0
2016-08-27Rename opendaylight service to opendaylight_apiSteven Hardy2-2/+2
For compatibility with the custom-roles patches which convert hard-coded hiera mappings (such as opendaylight_api_node_ips) to data generated based on the service_name, we need to either change this name to match the hiera (node_ips and vip) keys, or change the hiera keys to match the service. I took the former approach because it involves less juggling patch dependencies between t-h-t and p-t. Change-Id: Ic179550027f37946097afe0e5b9f504ea19fa7bc Partially-Implements: blueprint custom-roles
2016-08-26Merge "Adds OpenDaylight composable service"Jenkins2-0/+25
2016-08-26Merge "Add deployment of CAs via hieradata"Jenkins1-0/+8
2016-08-26Adds OpenDaylight composable serviceTim Rozet2-0/+25
Introduces environment files for deploying OpenDaylight in two ways: - ODL only managing L2 as an ML2 plugin - ODL managing L2 and L3 DVR, by replacing NeutronL3Agent Two services are added. One to install ODL and configure OVS on the Controllers, and another service to only configure OVS on compute nodes. Paritally-Implements: blueprint opendaylight-integration Depends-On: I666dc0874f1d11a72a62d796f4f6d41f7aa87a3f Change-Id: Ide69e20cbf2ec6151953cb23e51478b770aca17f Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-08-25Merge "Disable the Mon/OSD/Client resources in puppet-ceph-external"Jenkins1-1/+7
2016-08-25Merge "Move resource registry override to enable-tls.yaml"Jenkins3-6/+3
2016-08-25Merge "Fix path to sahara templates"Jenkins1-2/+2
2016-08-25Merge "Updates and fixes to NIC config template routes"Jenkins1-12/+16
2016-08-24Set NeutronL3HA to false when deploying DVRBrent Eagles1-0/+8
This patch sets NeutronL3HA to false when the DVR environment is included on deployment. L3 HA isn't supported with DVR routers and is disabled by defaults in our templates but upgrading users might have it enabled in their existing overclouds. Including the setting here with an appropriate comment gives us some sort of mechanism to convey to the upgrading user what they need to do. This will have no effect on users not using L3 HA or deploying new overclouds. Change-Id: If036ae2b88225f5a7d5f295eb5e6874d2fbb3f72
2016-08-23Move resource registry override to enable-tls.yamlJuan Antonio Osorio Robles3-6/+3
It makes more sense for the enable-tls.yaml file to contain the resource registry override, since it contains parameters that are actually used there. Also, this allows us to reuse the tls-endpoints-public-* files for other methods of enabling TLS (such as with certmonger). Change-Id: I98c63d0007e61968c0490a474eddb42548891fa6
2016-08-22Add deployment of CAs via hieradataJuan Antonio Osorio Robles1-0/+8
This enables us to pass a map of CAs to deploy the CA certificates using puppet and hiera instead of the bash script we were using. It also gives us the feature that we will be able to deploy several CA certificates on the nodes instead of just one as was the case before. Change-Id: I9559487874b80aeb093cc2fa2cfa7c0479d5a8b2 Depends-On: I84273b4cd6576a63fa78dc93ad6b077dd2a780c7
2016-08-22Fix path to sahara templatesSagi Shnaidman1-2/+2
Fix path to sahara templates Change-Id: I7e60ed1800923057efe24badf03d76761da3f498
2016-08-19Merge "Disable Sahara by default"Jenkins1-0/+3
2016-08-19Merge "Remove OS::Tripleo::Services::ManilaShare: from puppet-pacemaker.yaml"Jenkins1-1/+0
2016-08-19Disable Sahara by defaultDan Prince1-0/+3
Users who want Sahara enable now can simply include the environments/services/sahara.yaml Heat environment. Change-Id: I3df96b6e78ba3eddb62e79d854862a7e2d614c51
2016-08-19Disable cinder-backup by defaultGiulio Fidente2-1/+4
The cinder-backup service was not configured in mitaka, so having it disabled by default does not change the existing behavior. Also adds an environment file to enable it in the pacemaker scenario. Change-Id: I9a238e0d4601c9f59aff94fdac837c7d0e90afa0
2016-08-18Merge "Upgrade scripts to migrate aodh alarm data"Jenkins1-0/+10
2016-08-18Remove OS::Tripleo::Services::ManilaShare: from puppet-pacemaker.yamlCarlos Camacho1-1/+0
Already with the same value in overcloud-resource-registry-puppet.yaml Change-Id: Ic274abddef5e229a3517f4f77d8192d6abf81044
2016-08-18Merge "Make sahara run via systemd"Jenkins1-5/+2
2016-08-17Merge "Decouple EndpointMap from SSL certificate params"Jenkins3-52/+113
2016-08-17Make sahara run via systemdMichele Baldessari1-5/+2
Via commit 0327fc2bbb1be9972d99e2e83d54d07410ad01d9 we added sahara as a composable service. Let's make sure sahara-api and sahara-engine run via systemd and not as a pacemaker resource. This is inline with the HA NG spec. Change-Id: I5634ad43771fba798892df6d2297c2634dcb6756
2016-08-17Upgrade scripts to migrate aodh alarm dataPradeep Kilambi1-0/+10
In Newton, Aodh will be using its own mysql DB rather than using ceilometer's mongo instance. This means we need to migrate any existing alarm and alrm history data from ceilometer DB to aodh mysqlDB. Upstream aodh provides us with a aodh-data-migration utility. We need to invoke this during the mitaka->newton upgrade procedure so data is migrated as expected and aodh mysql backend takes over. Closes-bug: #1611794 Change-Id: I17888b57ecf98cd83e92af2f9cdbead066b03aa3
2016-08-17Merge "Update Ironic composable services"Jenkins1-0/+4
2016-08-17Merge "Add cinder-backup service as role"Jenkins4-0/+5
2016-08-15Merge "Convert ServiceNetMap to a nested template"Jenkins1-3/+3
2016-08-12Remove NeutronEnableTunnelling from templatesBob Fournier3-2/+4
As described in https://bugs.launchpad.net/tripleo/+bug/1532830, the OVS agent no longer uses enable_tunneling, which is controlled by NeutronEnableTunnelling, so this change removes NeutronEnableTunnelling from the Heat templates. This change depends on NeutronEnableTunnelling also being removed from python-tripleoclient and puppet-neutron no longer using the enable_tunneling hieradata. Change-Id: I1ff6902ebd15041fc57ffff20a07455f171a004b Closes-Bug: 1532830 Depends-On: I28d33592374f60cb5222a866efaf9d137aca1c5a Depends-On: I73630653330c67444827f32740c44e9d25b5db31
2016-08-12Convert ServiceNetMap to a nested templateSteven Hardy1-3/+3
We introduce a new ServiceNetMap resource which enables some more flexible mappings between the services and their networks. Specifically this patch means: 1. ServiceNetMap no longer has to specify the entire list of all services, operators may if they wish, but a subset is now valid where you want to accept the defaults for some services (the defaults are now accessible via the ServiceNetMapDefaults parameter. 2. We can map some keys which don't fit a pattern that enables conversion from CamelCase to snake_case which is required for compatibility with the service_names in puppet/services* This should be backwards compatible, and in future when we remove internal dependency on the CamelCase names, we could also enable operators to specify e.g heat_api_network in ServiceNetMap which would be more consistent. Change-Id: Ib60198adf76bb69ffbafbfac739e356d153f6194 Partially-Implements: blueprint custom-roles
2016-08-12Decouple EndpointMap from SSL certificate paramsBen Nemec3-52/+113
Having the endpoint map in the same environment as the SSL certificate parameters means that every time a service is added to the overcloud, the user must remember to update their copy of enable-tls.yaml to reflect the new service. To avoid this, let's separate the SSL EndpointMap from the SSL certificates so users can simply pass the shipped list of SSL endpoints and only have to customize the certificate env file. As and added bonus, this means they won't have to put the certificates in enable-tls.yaml specifically. The parameters can be set anywhere, and will be used as long as one of the tls-endpoints envs is also specified. inject-trust-anchor.yaml is not changed, but it could already be used in the same fashion. The root certificate param could be set in any env passed after inject-trust-anchor.yaml, and then inject-trust-anchor.yaml would only be responsible for setting the appropriate resource_registry entry. This way there is no need to customize the in-tree inject-trust-anchor.yaml either. Change-Id: I38eabb903b8382e6577ccc97e21fbb9d09c382b3
2016-08-11Update Ironic composable servicesDmitry Tantsur1-0/+4
* Add service for configuring Nova compute with Ironic * Fix authentication in Ironic APU * Provide a separate environment file for enabling Ironic Change-Id: I211e6d91eacd238b04a1aa37528d5a91523407d9 Partially-Implements: blueprint ironic-integration
2016-08-11Convert EndpointMap to not require per-service VIP parametersSteven Hardy1-1/+0
Currently we have a hard-coded set of per-service parameters, which will cause problems for custom roles and full composability. As a first step towards making this more configurable, remove the hard-coded per-service parameters from overcloud.yaml, and adjust the EndpointMap generation to instead accept two mappings, the ServiceNetMap and a mapping of networks to IPs (effectively this just moves the map lookup inside the endpoint map instead of inside overcloud.yaml) Change-Id: Ib522e89c36eed2115a6586dd5a6770907d9b33db Partially-Implements: blueprint custom-roles