aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2016-03-10Merge "Updated the heat_template_version"Jenkins2-2/+2
2016-03-10Merge "Fixup systemctl_swift stop/start during the controller upgrade"Jenkins1-4/+17
2016-03-09Merge "Add Rabbit IPv6 only support"Jenkins5-2/+34
2016-03-09Fixup systemctl_swift stop/start during the controller upgrademarios1-4/+17
During the controller upgrade in major_upgrade_controller_pacemaker_1.sh we use systemctl to stop all swift services and then start them again in _pacemaker_2.sh In the case of stand-alone swift nodes the deployer may have used the ControllerEnableSwiftStorage: false so that only the swift-proxy service is left on controllers (wrt swift). The systemctl_swift function used during upgrades is changed to factor this in. Change-Id: Ib22005123429f250324df389855d0dccd2343feb
2016-03-09Merge "Add missing createUser line to /etc/snmp/snmpd.conf"Jenkins5-5/+5
2016-03-09Merge "Change the CinderISCSIHelper to lioadm"Jenkins3-3/+3
2016-03-09Make External Load Balancer templates work with IPv6Dan Sneddon8-0/+444
This change modifies the network isolation templates that allow for fixed IP addresses on the controllers' IPs and VIPs, and makes them compatible with IPv6 addresses. The latest version of the patchset creates an from_service_v6.yaml in order to properly handle service VIPs on IPv6 networks. Note that since OVS is not currently compatible with IPv6 tunnel endpoints, this patch does not yet enable IPv6 for the Tenant network by default. Change-Id: If881b000c6000ec13b54c0ee39f1c8940f079ae3 Co-Authored-By: Giulio Fidente <gfidente@redhat.com>
2016-03-09Merge "Update enable-tls.yaml with new endpoints"Jenkins1-0/+6
2016-03-09Add Rabbit IPv6 only supportMartin Mágr5-2/+34
Adds Rabbit environment variable required for IPv6 only support Change-Id: Iec209ca83a5b0708ac828c4afaf9d2222e597f24
2016-03-08Merge "Store events in Ceilometer"Jenkins1-0/+6
2016-03-08Merge "Set host in nova.conf for compute nodes"Jenkins1-0/+4
2016-03-08Change the CinderISCSIHelper to lioadmGiulio Fidente3-3/+3
Previously we used to always set CinderISCSIHelper to lioadm from the client. With [1] we aim at cleaning up the client from any default so this change move the actual default into the templates. 1. Iabc94ad1cce6f1744429aca9f866a59a698f5680 Change-Id: I662e4b0e3cf909ec2583d087ca1d246715caf0f7 Related-Bug: 1554564
2016-03-08Update enable-tls.yaml with new endpointsBen Nemec1-0/+6
A couple of new endpoints have been added, and if they're not in the configured value for EndpointMap it will cause problems. Sahara is not added as ssl-enabled because I don't believe it has been added to the loadbalancer yet. Note that there is work underway to CI overcloud SSL, which should catch problems like this in the future. Change-Id: Ia8a106fd94da7be8675ea84f5fbb9ac959771d10
2016-03-08Merge "Permits configuration of Cinder enabled_backend via hieradata"Jenkins5-3/+6
2016-03-08Increase default netdev_max_backlog to 10xGiulio Fidente1-0/+2
It has been observed that on large clouds the netdev backlog buffer might overflow. This change increases the default by ten times. The /proc/net/softnet_stat file contains a counter in the 2nd column that is incremented when the netdev backlog queue overflows. If this value is incrementing over time, then netdev_max_backlog needs to be increased [1]. [1]. https://bugzilla.redhat.com/show_bug.cgi?id=1283676 Change-Id: Iec12324fd3a24e8b608b1e1849c270cc24cb0e60
2016-03-08Merge "Fixup the memcached servers string in nova.conf for v6"Jenkins2-1/+16
2016-03-08Store events in CeilometerRichard Su1-0/+6
Adds an option to toggle whether events are stored in Ceilometer. The default is false and remains unchanged. Change-Id: I9accb679b97cf7172c67f3cd5f218bdaee507c94 Related-Bug: rhbz#1312373
2016-03-08Merge "Add an environment to use a swap partition"Jenkins1-0/+90
2016-03-07Merge "Move ordering constraints from httpd to openstack-core"Jenkins1-42/+57
2016-03-07Set host in nova.conf for compute nodesJames Slagle1-0/+4
In order for instance HA to function safely, nova-compute needs access to the name by which nova knows the current compute node. Since the names of the nova-compute and neutron ml2 agents must be the same for vif binding to work, it also sets the host value in neutron.conf. Change-Id: I7d07c57b7276815c72d08acaa86f673e43eb0498
2016-03-07Merge "Make AllNodesExtraConfig depend on the validation deployments"Jenkins1-1/+7
2016-03-07Merge "Set /64 cidr_netmask for pcmk VIPs when IPv6"Jenkins1-6/+42
2016-03-07Merge "Fix rabbit_hosts list for glance-api for IPv6"Jenkins3-8/+3
2016-03-07Merge "Allow to enable IPv6 on Corosync"Jenkins4-2/+22
2016-03-07Merge "Use MysqlVirtualIPUri for nova_api and sahara database"Jenkins1-2/+2
2016-03-07Merge "Make the Neutron subnet ipv6_{ra,address}_mode configurable"Jenkins5-10/+50
2016-03-07Merge "Revert "Deploy Aodh services, replacing Ceilometer Alarm""Jenkins12-309/+3
2016-03-07Merge "Function library for major upgrades"Jenkins2-0/+16
2016-03-07Merge "Add IPv6 versions of the Controller NIC configs"Jenkins10-13/+565
2016-03-07Merge "Fixup swift device string to delimit the ipv6 address with []"Jenkins2-3/+3
2016-03-07Merge "Introduce a UpgradeScriptDeliveryWorfklow as part of tripleo upgrades"Jenkins4-25/+114
2016-03-07Fixup the memcached servers string in nova.conf for v6marios2-1/+16
As discussed at https://bugzilla.redhat.com/show_bug.cgi?id=1299265 when providing a list of IPv6 addresses as the memcache_node_ips the resulting nova.conf entry can't be parsed properly. This adds a memcache_node_ips_v6 which has the required format like inet6:[ADDR1],inet6:[ADDR2],inet6:[ADDR3] Closes-Bug: 1536103 Change-Id: I7f95fa063cbba279c4c2e270841f0a279d2be2f6
2016-03-07Fixup swift device string to delimit the ipv6 address with []marios2-3/+3
The swift device string is formatted in the outputs of the controller template and swift-storage templates. For ipv6 we need to delimit the address with [] as discussed in https://bugzilla.redhat.com/show_bug.cgi?id=1296701#c0 Change-Id: Ie611d62c3668a65a7be52777a613d265682c6a8b Co-Authored-By: Jiri Stransky <jistr@redhat.com> Closes-Bug: 1534135
2016-03-06Add an environment to use a swap partitionJames Slagle1-0/+90
This environment can be used with AllNodesExtraConfig to enable swap on a device with the given label as specified by the swap_partition_label parameter. If Ironic is used to create the swap partition, the partition will have a label of swap1, so that's a reasonable default for the parameter. The partition is also written to /etc/fstab as a swap mount so that it will be enabled on reboot. Change-Id: I5cd68c13dbfe53eecf6c6ad93151eadc980a902d
2016-03-04Revert "Deploy Aodh services, replacing Ceilometer Alarm"James Slagle12-309/+3
This just a revert to see if reverting this gets back to a normal CI run time. This reverts commit f72aed85594f223b6f888e6d0af3c880ea581a66. Change-Id: I04a0893f6cf69f547a4db26261005e580e1fc90b
2016-03-05Set /64 cidr_netmask for pcmk VIPs when IPv6Emilien Macchi1-6/+42
We'll use /32 for IPv4, the default pacemaker was already using. Change-Id: Iab584c3e50efc3ecc0ec87bb080bf2d5d802199d Co-Authored-By: Giulio Fidente <gfidente@redhat.com>
2016-03-05Allow to enable IPv6 on CorosyncEmilien Macchi4-2/+22
To enable IPv6 in Corosync, you'll need to set the --ipv6 parameter when building the cluster. To do so, we need to specify this parameter in puppet configuration when running ::pacemaker::corosync class. So we have now a new parameter: CorosyncIPv6 which is a boolean, False by default. If set to True, it will pass right options to enable IPv6 when building the Pacemaker cluster. Change-Id: I485f1399964ddd7a201ed19ec6580b8a136b3acd
2016-03-05Make the Neutron subnet ipv6_{ra,address}_mode configurableGiulio Fidente5-10/+50
Use of slaac does not permit stati assignment of IPs to a Neutron port, so we default to dhcpv6-stateful instead. Change-Id: Id7f104be60ae05785a3d0a33516d7875a4698ed1
2016-03-05Add IPv6 versions of the Controller NIC configsDan Sneddon10-13/+565
This change adds Controller NIC configs for the sample NIC config templates that are compatible with IPv6 on the External network. These controller-v6.yaml templates include a default route for IPv6 on the External network, and a default route for IPv4 on the Control Plane. The Heat parameters ExternalNetworkDefaultRoute and ControlPlaneDefaultRoute are used to set these values. Change-Id: Ifed8cb359eae1d9d623d3eb2fe40ea8a0d1d889a
2016-03-05Merge "Add IPv6 Support to Isolated Networks"Jenkins39-30/+1009
2016-03-05Fix rabbit_hosts list for glance-api for IPv6Giulio Fidente3-8/+3
Previously we were always appending the :port suffix to the list of rabbitmq nodes but the syntax was invalid for IPv6. This change wires rabbit_hosts from the templates as it happens already for the other services. Port can be customized using rabbit_port. Change-Id: Iecc7a97d46d7de17e85398c57996c104c9125b0e
2016-03-05Use MysqlVirtualIPUri for nova_api and sahara databaseGiulio Fidente1-2/+2
Without this the nova_api and sahara database_connection string won't add brackets around the IP address, when IPv6, causing db sync to fail. Change-Id: I262e5de993ae59ad665edb043119aac2e09c6fdc
2016-03-04Make AllNodesExtraConfig depend on the validation deploymentsJames Slagle1-1/+7
AllNodesExtraConfig should really only run after the validation deployments are done, which validate that basic networking is functioning. In particular, creating a swap file during AllNodesExtraConfig while the validation deployments are still running might cause temporary network outages which could fail the validations. Change-Id: Ia2a10318de47854a9b8932d72243ce0a85603556 Partial-Bug: #1553243
2016-03-04Merge "Allow for usage of pre-allocated IPs for the management network"Jenkins4-0/+54
2016-03-04Merge "Run keystone-manage bootstrap for HA deployment too"Jenkins1-3/+1
2016-03-04Run keystone-manage bootstrap for HA deployment tooJiri Stransky1-3/+1
This is necessary to keep creating the Default domain. Change-Id: Ib9911819e89f30270d4f7597639b33f30ad2e3a6 Closes-Bug: #1549867
2016-03-04Merge "Set notification driver for nova to send"Jenkins1-1/+1
2016-03-04Add IPv6 Support to Isolated NetworksDan Sneddon39-30/+1009
This change adds a new set of network templates with IPv6 subnets that can be used instead of the existing IPv4 networks. Each network can use either the IPv4 or IPv6 template, and the Neutron subnet will be created with the specified IP version. The default addresses used for the IPv6 networks use the fd00::/8 prefix for the internal isolated networks (this range is reserved for private use similar to 10.0.0.0/8), and 2001:db8:fd00:1000::/64 is used as an example default for the External network (2001:db8::/32 are the documentation addresses [RFC3849]), but this would ordinarily be a globally addressable subnet. These parameters may be overridden in an environment file. This change will require updates to the OpenStack Puppet Modules to support IPv6 addresses in some of the hieradata values. Many of the OPM modules already have IPv6 support to support IPv6 deployments in Packstack, but some OPM packages that apply only to Instack/TripleO deployments need to be updated. IPv6 addresses used in URLs need to be surrounded by brackets in order to differentiate IP address from port number. This change adds a new output to the network/ports resources for ip_address_uri, which is an IP address with brackets in the case of IPv6, and a raw IP address without brackets for IPv4 ports. This change also updates some URLs which are constructed in Heat. This has been tested and problems were found with Puppet not accepting IPv6 addresses. This is addressed in the latest Puppet. Additional changes were required to make this work with Ceph. IPv6 tunnel endpoints with Open vSwitch are not yet supported (although support is coming soon), so this review leaves the Tenant network as an isolated IPv4 network for the time being. Change-Id: Ie7a742bdf1db533edda2998a53d28528f80ef8e2
2016-03-04Allow for usage of pre-allocated IPs for the management networkSteven Hardy4-0/+54
Id3d4f12235501ae77200430a2dc022f378dce336 added support for pre-allocated IPs on the other overlay networks, but because the patch adding the managment network (I0813a13f60a4f797be04b34258a2cffa9ea7e84f) was under review around the same time, we missed adding the from_pool capability to the ManagementNetwork. Change-Id: If99f37634d5da7e7fb7cfc31232e926bd5ff074a
2016-03-03Merge "Deploy Aodh services, replacing Ceilometer Alarm"Jenkins12-3/+309