aboutsummaryrefslogtreecommitdiffstats
path: root/puppet
AgeCommit message (Collapse)AuthorFilesLines
2016-07-11Merge "Include bulk in swift proxy pipeline"Jenkins1-0/+1
2016-07-11Move ironic::db data within service templateGiulio Fidente4-13/+8
Change-Id: If0b8fbc783e694f4f744ad848103d40df985fc04
2016-07-11Merge "Move neutron::db data within service template"Jenkins2-10/+7
2016-07-11Merge "Move sahara::db data within service template"Jenkins2-8/+6
2016-07-11Merge "Move heat::db data within service template"Jenkins2-8/+6
2016-07-11Merge "Move cinder::db data within service template"Jenkins2-8/+6
2016-07-11Merge "Move glance::db data within service template"Jenkins2-8/+7
2016-07-11Merge "Move keystone::db data within service template"Jenkins2-8/+7
2016-07-11Merge "Set os-refresh-config timeout to 4 hours"Jenkins5-5/+5
2016-07-11Merge "Template param for what command occ runs"Jenkins5-0/+35
2016-07-09Move neutron::db data within service templateGiulio Fidente2-10/+7
Change-Id: I07a81a2e1cc29df007bba11da82cf6661a55aadf
2016-07-09Move sahara::db data within service templateGiulio Fidente2-8/+6
Change-Id: Ifb87f79e8cd692e6553d03df8394c74f51821e11
2016-07-09Move heat::db data within service templateGiulio Fidente2-8/+6
Change-Id: I3fada6c5b0265bc6536c89da0ef4b709ead13b7d
2016-07-09Move cinder::db data within service templateGiulio Fidente2-8/+6
Change-Id: I2aaf30289cc792e8860ca9c962d80baf7e804cbf
2016-07-09Move glance::db data within service templateGiulio Fidente2-8/+7
Change-Id: I405bc9895160cc867f933e6b0d56546d460d2e3a
2016-07-08Composable Midonet for NeutronDan Prince4-160/+76
Depends-On: I2393fc3c360f5f5786411f64dbcd06f380376093 Change-Id: I606cb1f7ef7d651b5d145bfa10ef3aa1561b1590 Partially-implements: blueprint composable-services-within-roles
2016-07-08Include bulk in swift proxy pipelinePradeep Kilambi1-0/+1
With bulk delete enabled for gnocchi, this option should be included in pipeline as well. Change-Id: I5786c6f14e3aab9e167c22d8f72c5c1688440e95
2016-07-08Move keystone::db data within service templateGiulio Fidente2-8/+7
Change-Id: I934aff4960588a3957b7a7bcc90385ae48d34d1e
2016-07-08Merge "Parametrize and increase default of swift-proxy node_timeout"Jenkins1-0/+5
2016-07-07Merge pacemaker_master/sync_db conditionalsGiulio Fidente1-40/+38
By condensing the pacemaker_master and sync_db conditions we ensure there won't be unrelevant (clustercheck) execs deployed on non-bootstrap nodes. Closes-Bug: 1598907 Change-Id: Iae6aa13682d63096265f4751b2f71019a49f6fa6
2016-07-07Merge "Remove config_identifier from all_nodes extraconfig examples"Jenkins2-16/+0
2016-07-07Merge "Restore the NtpServer parameter name"Jenkins1-3/+3
2016-07-06Merge "Add kernel service"Jenkins7-38/+18
2016-07-06Merge "Allow neutron_options customization for dashboard"Jenkins2-2/+2
2016-07-06Restore the NtpServer parameter nameDan Prince1-3/+3
In 296bffde893dbbf36c62d664e24e2584b89b8070 we moved the NTP into a composable service but changed the name of the parameter to NtpServers. This will break upgrades for users of the previous parameter name. Closes-bug: #1599526 Change-Id: I896b9427416f01b603ac9cc4d8c9ebf5e019cb32
2016-07-05Merge "Split Heat pacemaker roles into separate services"Jenkins4-13/+7
2016-07-05Merge "pacemaker: don't override Service resource for Nova & Neutron"Jenkins1-3/+1
2016-07-05Remove config_identifier from all_nodes extraconfig examplesSteven Hardy2-16/+0
Since https://review.openstack.org/#/c/315616 this is no longer required. Change-Id: I0452d1577a25d19b4351bfe7830a6c7bbe485e67
2016-07-05Merge "Use create-legacy-resource-types during gnocchi-upgrade"Jenkins1-1/+1
2016-07-05neutron: remove tenant MTU configuration optionsIhar Hrachyshka3-47/+1
Since Mitaka, Neutron and Nova do the right thing for MTU, correctly calculating and applying MTU per network, considering its network type and underlying physical network MTU (1500 by default). Neutron now also correctly advertise proper MTU to instances through DHCP and RA mechanisms. With that, there is no reason to have those MTU hacks in deployment tools. Actually, they not only do no good, but break some setups (Jumbo frame aware infrastructure), or at least make them non-optimal (lowering instance MTU to 1400 when it's not needed, or when tunnel overhead does not require 100 bytes). Note that Neutron still has a set of configuration options to allow for custom physical network MTUs (global_physnet_mtu, path_mtu, physical_network_mtus). Those options define underlying infrastructure though, not tenant MTUs. To support Jumbo frames, TripleO should allow to set those options. That said, it's not the immediate goal of the patch, and hence such an effort would require a separate patch. Mitaka+ documentation on MTU configuration for Neutron: http://docs.openstack.org/mitaka/networking-guide/adv-config-mtu.html Change-Id: I540ba5dc69d0506f71b59746efcce94c73f9317f
2016-07-05Merge "overcloud_volume: cleanup unused Puppet code"Jenkins1-22/+0
2016-07-05Merge "volume: deploy snmp using composable role"Jenkins1-10/+0
2016-07-05Add kernel serviceEmilien Macchi7-38/+18
Add a new service that will load and configure kernel modules. Depends-On: If4f1047ff8c193a14b821d8b826f637872cf62bd Change-Id: I8f771712595d0f4826858b855985f65d3621c3f1
2016-07-05Combine BootstrapNodeDeployment with AllNodesDeploymentSteven Hardy5-28/+22
Currently we have a special controller-only deployment which writes the name/ip of the "bootstrap node", e.g the cluster master, which defaults to the first node in the Controller ResourceGroup. Now we're moving to fully composable services/roles, it's possible folks will want to deploy services that expect to detect the bootstrap node (e.g so only one node does a DB sync) for non-controller roles. So, take this opportunity to combine the bootstrap node deployment with the "all nodes" data, such that we deploy the same data for all roles. Because the boostrap node data is per role cluster, rather than truly global, we pass it via input_values into each per-role Deployment. At some future point we might consider renaming this, e.g to something which describes per-cluster config vs "all nodes", but as a first step let's just rationalize the resources. Change-Id: I4011526a13c51b3d0f95c17fe8ed38115b4fdce4
2016-07-05Set os-refresh-config timeout to 4 hoursSteve Baker5-5/+5
This change uses the new os-refresh-config --timeout argument to set a kill timeout for stalled os-refresh-config runs. 4 hours is a reasonable conservative value since it matches the stack timeout - but it can be set shorter in the future based on actual run times. Change-Id: I433f558515df24736263ec0d50de08ad8f78498f Closes-Bug: #1595722 DependsOn: Ibcbb2090aed126abec8dac49efa53ecbdb2b9b2c
2016-07-05Template param for what command occ runsSteve Baker5-0/+35
The ConfigCommand parameter overrides the server resource metadata to specify what command os-collect-config runs whenever any configuration data changes. The default is already 'os-refresh-config' so this change has no effect but it allows a future change to specify an os-refresh-config --timeout argument to fix bug #1595722. Change-Id: I8dd35b6724d8c00e5495faca84ee8fee77641b82 Partial-Bug: #1595722
2016-07-04Replace NodeConfigIdentifiers with DeployIdentifierSteven Hardy10-80/+36
We added NodeConfigIdentifiers to trigger config to be re-applied on update, but then later added DeployIdentifier which forces config to *always* be applied on update, so we can simplify things by just referencing the DeployIdentifier directly. Change-Id: I79212def1936740825b714419dcb4952bc586a39
2016-07-04overcloud_volume: cleanup unused Puppet codeEmilien Macchi1-22/+0
overcloud_volume contains some code that is already deployed by OS::TripleO::Services::CinderVolume service. Change-Id: I3446883cb89dcf179a854e2adef81b899117f66a
2016-07-04volume: deploy snmp using composable roleEmilien Macchi1-10/+0
Change-Id: Ibc9abf7043c37104d03cd72d882e10cdb53fe6a2
2016-07-04Switch Ceph Monitor/OSD/Client/External to composable rolesGiulio Fidente16-387/+301
Change-Id: I1921115cb6218c7554348636c404245c79937673 Depends-On: I7ac096feb9f5655003becd79d2eea355a047c90b Depends-On: I871ef420700e6d0ee5c1e444e019d58b3a9a45a6
2016-07-04Merge "Remove NFS bits from overcloud_compute manifest"Jenkins1-12/+0
2016-07-04pacemaker: don't override Service resource for Nova & NeutronEmilien Macchi1-3/+1
Nova & Neutron services are already managed by puppet-tripleo in profiles, and we already override Service resource for some services to manage them with Pacemaker. Dropping this code here will allow us to run TripleO in AIO setup as we don't manage everything with Pacemaker. Change-Id: Idcfc6ea26ca41534ce407be0eb3dafe7bcd2ef2d
2016-07-04Merge "Don't set selinux in 'permissive' mode on CephStorage nodes"Jenkins1-2/+0
2016-07-04Merge "Add Rabbit/epmd port to firewall"Jenkins1-0/+1
2016-07-01Remove NFS bits from overcloud_compute manifestEmilien Macchi1-12/+0
They moved to puppet-tripleo. Change-Id: Idd4488fc4b1e8e8024d47f6e3d83ac4f3cecd088 Depends-On: I75d68cc766ad274b16b22f43b7d34d02ab26de13
2016-07-01Merge "First iteration of libvirt and nova-compute as a composable services"Jenkins5-42/+47
2016-07-01Pass RoleData into -post.yaml stacksDan Prince5-33/+28
This patch modifies the interface for the -post stacks so that we pass RoleData instead of just the StepConfig into each -post.yaml template. This will facilitate creating other types of -post.yaml scripts that require more data that just 'step_config'. Things like containers, etc. will require this. Change-Id: I2527fc0098192f092f5e9046033a04bc71be2cae
2016-07-01Output generic role_data in services.yamlDan Prince1-6/+5
This patch updates puppet/services/services.yaml (currently the only interface for 'services' in t-h-t) so that we return a more generic 'role_data' Heat output. This is a move towards making the services themselves a bit more generic so we can accommodate other deployment types (containers, etc.) Change-Id: I8bc32c59a48e6d5f0caa2f26fab394d5d992a4a5
2016-07-01Add Rabbit/epmd port to firewallRaoul Scarazzini1-0/+1
This commit adds the epmd port 4369 to the firewall configuration for the service rabbit. This is necessary for having HA setups working, since without this port the rabbitmq cloned resource starts only on one node and the others are not able to complete the rabbit cluster creation. Change-Id: Iae042dd60a578e158b75539dc3998fc40185b343
2016-07-01Use create-legacy-resource-types during gnocchi-upgradePradeep Kilambi1-1/+1
Gnocchi 2.1 introduces a change where legacy resource types needed by ceilometer are not created by default. Instead a new flag is exposed to create these. We should use this by default. Note that this is an optional flag and is only needed if you want to create legacy resource types. Change-Id: I95ccccb40ce4a8319d0776c4d62c2890cf1fd970 Closes-bug: #1592449