We obsoleted the CephFS native parameter but missed to update it
in the Ceph profile.
Change-Id: I12a91da7df6079d391fa9583c4f2c926d123044f
Closes-Bug: #1783341
Expose configuration parameteres for NUMA
aware vswitches.
The related nova changes are done in change:
https://review.openstack.org/#/c/564440/
Depends-On: Ia8fd65a75bc732087128e9e32ba72b2491423898
Change-Id: I318ba9c262f64c0d416a017ed836ae0729acedb4
Add 'neutron::plugins::ml2::physical_network_mtus' as a
NeutronML2PhysicalNetworkMtus in heat template to allow
set MTU in ml2 plugin
Change-Id: I2f9666a5422a1272d53c869e4dad8581ab605b37
Closes-Bug: 1782123
to eliminate special 'docker' names.
Containerized manila is now the standard way to deploy
so we can avoid confusion by just using the regular
manila environment file names for these rather than having
some manila environment files with 'docker' in their names.
Note that we are using the content of
environments/manila-cephfsnative-config-docker.yaml
for
environments/manila-cephfsnative-config.yaml. This resolves an
issue wherein the parameters in the latter file were not updated
when support for the CephFS-NFS back end was added [1].
Closes-Bug: #1782622
[1] Ib408c7827e5fba0c1b01388db26363806fc64370
Change-Id: I08431d848158846a434fecc98d3bee838c7fad68
By settings these hiera keys we will actually do a deep comparison
of all pacemaker resources and update them accordingly.
This means that rerunning a deploy against an existing overcloud
will actually detect if a pacemaker resource needs updating and
will update the definition and restart of said resource. The code
will wait for the resource to be up (aka the cluster to settle
after an update).
Depends-On: I62d5662327333e17e1c32a029695b3d3a904ca10
Change-Id: I0b9ed429e6b1bd4a62b4462bf6312782f29b7d6b
Using str_replace when looking up hostnames in
HostnameMap may return unpredictable results.
For example if the map contain:
HostnameMap:
overcloud-compute-12: cmp-12-london
overcloud-compute-123: cmp-123-berlin
When we do string replace for a hostname that is
not in the map (example: 'overcloud-compute-124')
it will match on the substring. The result would
be 'cmp-12-london4'.
This change replaces the str_replace with a yaql
expression that will return the value of they key
matching the hostname provided. If the key is not
in the map, the hostname is returned.
Closes-Bug: #1781560
Change-Id: Ia3a6a3539cd566131cd81b4d755190aa5b61a573
Adding mandatory OVS-DPDK parameter to the roles file instead of
environment file, as it requires to be added for each custom role.
Change-Id: I33fa198228e3e3adcb8e93146d9a9caa46a28895
Nameservers are configured on the ctlplane subnets by the
undercloud installer, the nameservers are used early during
the deployment, prior to running os-net-config.
Remove the default DnsServer's in THT, replacing it with
an empty list and use get_attr to get the values for
DnsServers for the overcloud from the ctlplane subnet(s).
A conditinal is used in puppet/role.role.j2.yaml so that
the parameter value is used whenever it is not [] (default)
to provide backwards compatibilityi and in case the user
want to use different DnsServers for the overcloud and
undercloud.
Partial: blueprint tripleo-routed-networks-templates
Change-Id: I5f33e06ca3f4b13cc355e02156edd9d8a1f773cd
The route to metadata service is set up in host_routes
of ctlplane subnets by extraconf post deploy::
extraconfig/post_deploy/undercloud_ctlplane_network.py
Use get_attr on the server resource to resolve attribute
value from the subnet(s) and pass it to the parameter
'EC2MetadatIp' used in the THT/network/config/* templates.
Changes the default for 'EC2MetadatIp' to ''.
Removes the comment that the value should be overriden in
parameters_defaults. It also removes the parameter from
network-environment templates.
A conditinal is used in puppet/role.role.j2.yaml so that
the parameter value is used whenever it is not '' (the
default) to provide backwards compatibility in case the
user set a different value for this parameter in
network-environment.yaml.
When deploying a routed control plane the network config
templates would previously need to be updated to carry
'EC2MetadatIpLeafX' parameters for each leaf. By getting
the value to pass from the server resource this change
reduces the required nic-config template customisation.
(Reduces the risk of user error.)
Partial: blueprint tripleo-routed-networks-templates
Change-Id: I9c019ec840a44ca8c5f98be55daea365bc6554ec
Use get_attr on the server resource to resolve attribute
value from the subnet(s) and pass it to the parameter
'ControlPlaneDefaultRoute' used in the THT/network/config/*
templates.
Changes the default for 'ControlPlaneDefaultRoute' to ''
as well as the comment that the value should be overriden
in parameters_defaults. It also removes the parameter from
network-environment templates.
A conditinal is used in puppet/role.role.j2.yaml so that
the parameter value is used whenever it is not '' (the
default) to provide backwards compatibility in case the
user set a different value (different from the one used in
undercloud.conf) for this parameter in
network-environment.yaml.
When deploying a routed control plane the network config
templates would previously need to be updated to carry
'ControlPlaneXDefaultRoute' parameters for each leaf. With
8 Leafs in addition to the network local to the undercloud
that is 8 parameters less to place in the configuration.
By getting the value to pass from the server resource this
change reduces the required nic-config template
customisation (reduces the risk of user error).
Partial: blueprint tripleo-routed-networks-templates
Change-Id: I5139249d55e9ac01761c270b8c0f31ef35595940
Use get_attr on the server resource to resolve attribute
value from the subnet(s) and pass it to the parameter
'ControlPlaneSubnetCidr' used in the THT/network/config/*
templates.
As the value is now resolved from resource attributes,
this changes the default for 'ControlPlaneSubnetCidr' to ''
as well as the comment that these value should be overriden
in parameters_defaults. It also removes the parameter from
network-environment templates.
A conditinal is used in puppet/role.role.j2.yaml so that
the parameter value is used whenever it is not '' (the
default) to provide backwards compatibility in case the user
set a different value (different from the one used in
undercloud.conf) for this parameter in
network-environment.yaml.
When deploying a routed control plane the network config
templates would previously need to be updated to carry
'ControlPlaneXSubnetCidr' parameter (in case the subnet
mask is not the same for all the routed network leafs).
With 8 Leafs in addition to the network local to the
undercloud that is 8 parameters less to place in the
configuration. By getting the value to pass from the
server resource this change reduces the required nic-config
template customisation (reduces the risk of user error).
Partial: blueprint tripleo-routed-networks-templates
Change-Id: I92ee0f9a2107cdf1ca5903d3756a235a79c36c73
With the standalone deployment mechanism, the default list of enabled
OpenStack services is Keystone, Nova (and related), Neutron (and
related), Glance, Cinder, Swift and Horizon. The default list of
disabled of OpenStack services is Aodh, Barbican, Ceilomter,
Congress, Designate, Gnocchi, Heat, Ironic, Manila, Mistral, Panko,
Sahara, Tacker and Zaqar. Disabled services can be enabled by
passing the appropriate environment files to re-enable them during
the deployment.
Change-Id: Ibf49ac61f4a50b429e72ebeb5b35f6524ae8f24d
Related-Blueprint: all-in-one
The AllNodesExtraMapData parameter is used to inject additional
hieradata into the all_nodes hierdata file on each node. The injected
data will be deeploy merged with the calculated all_nodes data for the
stack.
The parameter can be taken advantage of for split-controlplane use cases
where the hieradata from the control stack needs to be populated into
the separate compute stacks.
To easily get the hieradata out of the control stack, a new stack output
is added, AllNodesConfig.
Partially Implements: blueprint split-controlplane
Change-Id: I7b865bf82520006eef3ac2f36df34b1f3c34e642
The nova_compute container kolla config is currently set to recursively change
the ownership of /var/lib/nova to nova:nova on startup.
This is necessary when upgrading from an non-container deployment to a
containerized deployment as the nova uids are not consistent across the host
and container image.
If the nova instancedir is an NFS mount then open filehandles are
broken and every VM using that NFS export fails with I/O errors.
This change re-implements the nova statedir ownership logic to target only the
files/directories controlled by nova.
Requires dist-git change: https://review.rdoproject.org/r/14734
Change-Id: I57d421feb6356d28002e77fb9bfa50a397758cbf
Closes-bug: 1778465
Use the {{role.name}}IPs for network port resources in
Composable Role to enable setting predictable ip address
on network ports.
We currently support predictable ip addressing using the
from_pool templates. The from_pool creates a 'fake' neutron
port. Because of this we loose access to properties of
the ports subnet, properties that is useful to simplyfy
advanced configurations such as routed spine-and-leaf.
Creating a neutron port also open the possibility to use ML2
plugins in the future (Neutron Ansible ML2) to do port
binding that configures network devices.
The parameter (interface) to use this is the same as with
from_pool. Example:
parameter_defaults:
{role.name}IPs:
{network.name_lower}:
- 10.0.0.1
{network.name_lower}:
- 172.16.1.1
We just don't need to override the resource registry. I.e
the following is not used/required.
resource_registry:
``OS::TripleO::{{role.name}}::Ports::{{network.name}}Port``
NOTE: This does not remove the from_pool templates. We may
want to deprecate them, but in that case we need to
ensure it is possible to upgrade an environment that
used them by changeing the resource registry to use
the default port templates in this change.
Related: blueprint tripleo-routed-networks-templates
Change-Id: I3f9b55ffbf6b6626b4d0dfbec3867811cb74de14
Adds the host_routes on the neutron ports subnet to the output
of the Tripleo Ports template. This will allow use of get_attr
in the role to pass routes for a subnet to NetworkConfig.
Partial: blueprint tripleo-routed-networks-templates
Change-Id: I46896153ea59ae0a6a8dff0208de2b0d168927ae
With https://review.openstack.org/#/c/561784 we change the default
migration port range to '61152-61215'.
nova::migration::qemu::configure_qemu needs to be set to true that
the config gets applied via puppet-nova.
Change-Id: Iad4b392c9fe7426f2ce10a02fadd8b1aeee34ef6
Closes-bug: 1779820
Depends-On: Idadfc7b3507977f1385e846a48a734ed0e5f0a32
ODL is configured to log to console and then access the logs
via docker logs. Older logs are being deleted too fast. So
moving back to logging to file which is default setting in ODL
THT.
https://github.com/openstack/tripleo-heat-templates/blob/
master/puppet/services/opendaylight-api.yaml#L60
Change-Id: I29724cfb23e13c8293d1b7b4341cbd409ae1b7a6
Closes-Bug: 1779629