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
This replaced multiple for loops with a single loop.
This changes the ordering in the rendered file to have
one section per network, instead of one section per
perameter such as VLAN, AllocationPools.
It also reduces the use of jinja conditionals. This
results in some duplicated comment strings in the
jinja template.
This is a micro optimization, but this makes sense
as a follow on will add the possibility to add
multiple subnets on each network in network_data.yaml.
I.e we avoid additional nested loops over the subnets.
Related: blueprint tripleo-routed-networks-templates
Change-Id: I0f11acaf7c25ff5d240db1daae2dc2b051c0a3b2
swift-proxy and gnocchi both run on step_4. However, swift_proxy should
be ready before gnocchi. This patch moves gnocchi_db_sync to step_5 to
be sure that swift-proxy is started before gnocchi. gnocchi_db_sync has
higher start_order to start before other gnocchi services.
Change-Id: I0044c78c4a6d751fc9d0cf6b54ed634032933934
Closes-Bug: 1781162
After CI scenario deployment is finished the container ends in unhealthy
state because sensu-client is not successfully connected to RabbitMQ.
We will need to implement default connection to overcloud RabbitMQ instance
for the service to have this service deployed in CI job.
Change-Id: I1aec0c71a945c06a6d914638b45cae074288a90d
Closes-Bug: #1781108
OVN metadata agent uses haproxy as part of its implementation.
Running it in a separate container prevents dataplane breakages
(ie. restarting VMs or spawning new ones) on agent restart/stop.
This patch triggers the creation of such sidecar container and
mounting of haproxy wrapper for spawning it in a separate
container.
Change-Id: I59e08384080cda0b6c0f03c9ed8fb6f6a5661e6b
Related-Bug: #1749209
Signed-off-by: Daniel Alvarez <dalvarez@redhat.com>
w/a https://github.com/ansible/ansible/issues/42621
Include ansible-role-container-registry roles/tasks
with handlers having the right variables scope.
Closes-Bug: #1781198
Change-Id: I26cc07aa05912c3e84d59003686eae210e924a16
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
We used `raw_get` because of a bug we found in ansible a while back.
This doesn't seem to be a problem anymore so we're switching back to
subscript syntax to remove a bit of boilerplate.
Change-Id: Ib5873ca617fbe38ffc6bc4d52cb4c936a94472c5
The OSA assisted HA deployment is not recommended for production
environments, besides it being limited. Therefore, we're relying on our
deployment of HAproxy + Keepalived to provide HA on top of OpenShift in
addition to adding more OpenShift nodes.
Depends-On: Ib573758b515264d1dda90cc9de61f4fa6659dc7d
Change-Id: I7ab677e4803e9df5f6641204cb0b6ccc5b1eb79f
1. manila-backend-vnx.yaml:
a. remove ManilaVNXServerMetaPool since meta_pool is not used by Manila VNX driver
b. add ManilaVNXServerContainer
2. cinder-dellemc-vnx-config.yaml:
a. remove default value of CinderDellEMCVNXStorageSecurityFileDir since it is not medatory option for Cinder VNX driver
Change-Id: Ie48cec52df720f3a13700d6048ecf78ba9067b51
Closes-bug: #1774942
Implement a post script for the standalone to generate a basic
clouds.yaml for use with various tools. This one does not reuse the
undercloud post because the undercloud script performs a bunch of
undercloud specific functions.
Change-Id: I0496f4dd2026ab6c705683126c8f50302a0861b9
Update the standalone role to include compute and other OpenStack
services. This list can be used to deploy a standalone all-in-one
nova/neutron/cinder/glance node.
Depends-On: I796a192b46c3372bebb41096c1051f01445b7e57
Depends-On: If55cf8f90ee7be4acd40fda1f72bb1f31d218b57
Change-Id: I6713469bfbd4fe9fc47d3cb2d3571fe10871f34e
Related-Blueprint: all-in-one
When we initially install our heat hosts configuration, we need to make
sure the short hostname for the host is not currently defined within the
hosts file as it will conflict with our definitions later in the file.
We only do this on initial installation as we don't want to touch the
file after the initial deployment outside of the matching host entries.
This also is restricted to just the short hostname which is consumed via
the configuration management for determining bootstrap configurations as
well as used by some services during startup (rabbitmq)
Change-Id: If55cf8f90ee7be4acd40fda1f72bb1f31d218b57
Related-Blueprint: all-in-one
In case the nova-api service is not running in the MySQL
master node, the FFU tasks will fail as it might not have
MySQL installed.
Avoid executing Nova DB tasks on FFU if MySQL not installed,
point to the MySQL server.
Resolves: rhbz#1593910
Closes-bug: 1780425
Change-Id: I02bc48d535707d579ecd590f970b1a08962a0111
This saves some time in undercloud deployment, because those images
don't have to be pulled from the undercloud registry.
This change also adds a --verbose so the output is more useful.
Change-Id: I8064d51bed9f3133a8192e9c1a7870f6bb69e2ab
Depends-On: Id75d5288c308e58143662703da3dddbdbcb0cdd9
Refactored the inventory generation to allow for scaling up the
openshift stack. They deployment process now checks whether the
origin-node container is already running in the openshift nodes. All
the nodes where origin-node is not present are considered as new.
The new_masters/new_nodes sections will be populated accordingly and
the `scaleup.yml` playbook will be used instead of the `deploy_cluster`
one *only* if the stack is being updated.
Unfortunately, openshift-ansible's implementation is not as idempotent
as TripleO's, which requires differentiating between deployments,
scaleup and between new and old nodes.
Change-Id: I15c4e855a3ccfba6ce8d516b5b59e7508c4885cc
The hiera check for bootstrap node was using 'manila-share'
for service name, which returns nil. Changing the service
name to 'manila_share', the hiera lookup for
'manila_share_short_bootstrap_node_name' succeeds.
Change-Id: Id3c001f8f0ee9dc156f22a027f66516d6812f51a
