Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Adds a new neutron compute plugin used to help configure opencontrail
for use on compute nodes.
Change-Id: I67a649445d5f1cb21ab9483bae7f5f4c2c657142
|
|
Adds a new neutron compute plugin used to help configure plumgrid
for use on compute nodes.
Change-Id: Ied6493aba826a602b2ce73359d1acf26ebe89869
|
|
Adds a new neutron compute plugin used to help configure midonet
for use on compute nodes.
Change-Id: I3a6996d3d9557ecad5ccd26a3901caccbf111468
|
|
Adds a new neutron compute plugin used to help configure nuage
for use on compute nodes.
Change-Id: I732ec85d1f0605e562dacb02624a355e425d911a
Depends-On: Ic842ebdc183918ec9a24f83ae39adfba27bc799c
|
|
Create a new resource registry entry for a Neutron "compute plugin".
For ML2 this may be the same os the NeutronComputePlugin but patches
for other vendors will follow that require extra bits on nodes
where VMs will be created.
This patch removes the ML2 code from the compute role and instead
uses the existing composable services.
NOTE: we are able to remove the puppet resource chain to force OVS to
get restarted due to puppet-neutron commit:
Idb1332dd498bb3065720f2ccaf68e6b0e9fa80c3 which should resolve that
issue.
Co-Authored-By: Emilien Macchi <emilien@redhat.com>
Depends-On: I95b9188607ab6c599ad4cde6faa1deb081618f3e
Change-Id: I2496372ca6e6ba9f52e9a8bb6e8dc731c125af13
|
|
Add horizon as a composable service
Depends-on: Iff6508972edfd5f330b239719bc5eb14d3f71944
Change-Id: I734c3e0784c25f30adff2e13faf1155a3e45cefd
Partially-implements: blueprint composable-services-within-roles
|
|
|
|
This patch provides a set of templates that enables
tripleo-heat-templates to be used with a set of already deployed,
installed, and running servers. In this method, Nova and Ironic are not
used to deploy any servers.
This approach is attractive for POC deployments where dedicated
provisioning networks are not available, or other server install methods
are dictated for various reasons.
There are also assumptions that currently have to be made about the software
installed on the already deployed servers. Effectively, they must match the
standard TripleO overcloud-full image.
Co-Authored-By: Steve Hardy <shardy@redhat.com>
Change-Id: I4ab1531f69c73457653f1cca3fe30cc32a04c129
|
|
|
|
|
|
This patch brings back Ceilometer composable roles for controller,
module some adjustments to make it work.
Fixes 3 issues in Ceilometer composable services
1) This patch fixes the hiera maps in the pacemaker ceilometer*
templates. These were lists and should be a map.
2) fixes a critical issue in ceilometer-base.yaml where the
password was incorrectly coded in the YAML using get_param on
a string which wasn't actually a parameter.
3) Fixes the ceilometer_coordination_url so that it uses a YAML anchor
as was implied instead of get_param on a string which wasn't a
parameter.
4) Fixes the default database connection to use mongodb and configured
in puppet-tripleo profile appropriately.
Co-Authored-By: Dan Prince <dprince@redhat.com>
Co-Authored-By: Pradeep Kilambi <pkilambi@redhat.com>
Closes-Bug: #1601844
Change-Id: Ia0a59121b9ffd5e07647f66137ce53870bc6b5d6
|
|
Its absence results in swift using up all the memory available to it when
certain objects are requested, we are not sure exactly what triggers the
problem but we know this fixes it.
Change-Id: Iaf00a8a2a947e0683cc60fef2e75fd7c444d07a8
Closes-Bug: #1595916
|
|
|
|
Change-Id: If0b8fbc783e694f4f744ad848103d40df985fc04
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Change-Id: I07a81a2e1cc29df007bba11da82cf6661a55aadf
|
|
Change-Id: Ifb87f79e8cd692e6553d03df8394c74f51821e11
|
|
Change-Id: I3fada6c5b0265bc6536c89da0ef4b709ead13b7d
|
|
Change-Id: I2aaf30289cc792e8860ca9c962d80baf7e804cbf
|
|
Change-Id: I405bc9895160cc867f933e6b0d56546d460d2e3a
|
|
Depends-On: I2393fc3c360f5f5786411f64dbcd06f380376093
Change-Id: I606cb1f7ef7d651b5d145bfa10ef3aa1561b1590
Partially-implements: blueprint composable-services-within-roles
|
|
With bulk delete enabled for gnocchi, this option should
be included in pipeline as well.
Change-Id: I5786c6f14e3aab9e167c22d8f72c5c1688440e95
|
|
Change-Id: I934aff4960588a3957b7a7bcc90385ae48d34d1e
|
|
|
|
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
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
Since https://review.openstack.org/#/c/315616 this is no longer
required.
Change-Id: I0452d1577a25d19b4351bfe7830a6c7bbe485e67
|
|
|
|
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
|
|
|