... because the option is deprecated in master[1] and has no effect.
Also, deployed-server-environment.yaml is not required when
the --deployed-server option is used since stable/wallaby[2].
[1] c6cd190a9f63738deafa4c616e0be8e06afedc96
[2] d6fba3f09f8de569b7fcf2bd9519c3112b1cc056
Change-Id: I4411a06026fc5bdf69061a643bc731e91c27640c
This change removes logic for releases older than train, because these
releases are already EOLed. This covers only overcloud-* roles and
playbooks and the other items will be covered by separate changes.
Note that this change also removes the containerized_* variables
because current active releases(>=Train) no longer supports
non-containerized deployment. The containerized_overcloud_upgrade
variable is still left because the variable is still required by
the tripleo-ci-base-multinode-standard job template.
Change-Id: If29ec2c2219a28a1f79db0e552e2c622c0a7bda6
If the specified default machine type is not
supported on the currently deployed OS, this
patch adds the option to specify a parameter
to override the default.
Related Bug: BZ: 2110535
Change-Id: Id0f0bf0d9efb2136ae49b8475e80774dd0578230
These will be useful when there is need to reprovision
these along with overcloud.
In CI jobs these are already generated, this patch is to
make normal quickstart.sh deploy's to have these
scripts generated.
Change-Id: Iaec8c01e61d24165cb83227c767099d37e11de1e
New qemu-kvm-6.1.0 version is buggy version and excluded in master
and wallaby (Ia6a9e01ca2adbde1e7a0b7cce9fe5842a0d54b1b,
Iac4425d655df2f519f5b467e3754dad08ac9b1f5).
New version was impacted q35 machines for CentOS-8 and Stream-9.
qemu-kvm-6.1.0 + NovaLibvirtNumPciePorts: 12 + q35 instances
for CentOS8 and Stream works fine.
Related-Bug: #1950916
Signed-off-by: Amol Kahat <amolkahat@gmail.com>
Change-Id: I39c00edd97e321963d1ced74dcf5a2a27fa032cc
We are creating a new featureset064 that will deploy overcloud with
custom network + custom overcloud name + IPA integration.
For that new featureset, We don't want to add the default
file created from cloud-names.yaml.j2 template but instead use
the values we defined in ci tht templates[1] for custom networks.
Adding a var non_custom_network that defaults to true so that we
can override in fs064.
testproject: https://review.rdoproject.org/r/c/testproject/+/31954
[1] https://review.opendev.org/c/openstack/tripleo-heat-templates/+/812369
Change-Id: I4fec8997d3f74552b72a6e1a33258c684f683eff
Currently the overcloud_baremetal_deploy does not match the
VMs with the flavor/role properly. The way that
currently creates the file may deploy the compute on
a ceph or a controller vm.
This way the vms will be used for the role that
they were created
Closes-Bug: #1949070
Change-Id: I4de262fc049b74482ff7220a11ec864133f1cb75
Temporarily add a workaround for EL9 by setting
~~~
NovaLibvirtNumPciePorts: 12
~~~
It's basically a workaround for a bug [1] in qemu that is currently
being worked on.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2006409
Related-Bug: #1947861
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: Ia2ad24960fc3477390a868e6572c260543b5c37a
tripleo-ci-centos-8-containers-multinode on change
https://review.opendev.org/798642 fails with:
Conflict detected for resource_registry entry:
OS::TripleO::Network::Ports::ControlPlaneVipPort.
The network-v2 workflow will create the ctlplane VIP
prior to the heat stack and automatically include the
required overrides. So there is no reason to manually
override the resource in the job.
Depends-On: I2d14d9e587fce28ea0897bb235c9dedc8f68fa12
Depends-On: Ife4b15a784c70fe031af98f3aa135737232d56a6
Change-Id: I42bcff7e1f1c17c24800343712ddcb8785892b64
The depens-on removes the usage of --skip-nodes-and-networks,
instead the existing --baremtal-deployment option is used to
provide the capability to enable/disable "all-in-one" network+
node provisioning with overcloud deploy command.
Depends-On: Idaab1f28c4d645279eff0c01b24435bf8571299b
Change-Id: I00241ee91cee42770c67fa181482c6e6ad9dedf1
Some roles (Controller with swift, and ObjectStorage) will need the
/srv volume to grow to store swift content. This allows custom
growvols_args to be specified on a per-role basis using the
topology_map.
Change-Id: I87836cef3b8815223ae0b038d6e295bccaa3ee65
With this change we are adding capability to create custom
baremetal environment specific yaml templates:-
* network_data.yaml
* vip_data.yaml
Above files will be created using the var `network_data_details` and
`network_vip_details` defined in downstream env_setting.yml(details
about env_setting.yml in [1])
Also, Updating `overcloud-deploy` role to parameterize the location of
network_data.yaml and vip_data.yaml file, this will help override the
default location.
[1] https://opendev.org/openstack/ansible-role-collect-logs/src/branch/master/docs/static/baremetal-overcloud/environment-settings-structure.rst
Change-Id: Ibfbe2d2af8372f47f6e6a31ca821bfb314ce347f
Migrate overcloud node provision from shell script to
tripleo_operator_node_provision role in tripleo.operator
collections
Signed-off-by: Amol Kahat <amolkahat@gmail.com>
Change-Id: I3745e4c4a34c99b02ada736d4d69c838bdf8793c
Migrate overcloud network vip provision from shell script to
tripleo_overcloud_network_vip_provision role in tripleo.operator
collections.
Signed-off-by: Amol Kahat <amolkahat@gmail.com>
Change-Id: Ie189fa25cb647a50834fcff8ee59df1d1946392d
Migrate overcloud network provision from shell script to
tripleo_overcloud_network_provision role in tripleo.operator
collections.
Signed-off-by: Amol Kahat <amolkahat@gmail.com>
Change-Id: Icc189b72d8a64652d60b8de34b9f5b392af227ff
Since the CI run's the commands to provision networks,
virtual IPs and baremetal nodes individually prior to
running overcloud deploy we can disable these steps
when running overcloud deploy.
NOTE: 'network_provison' is only set to True for Wallaby
and later releases.
Depends-On: I2fa073863f2d292575ee1dbdc0da271434f219f6
Change-Id: I8008344f215be6a54e00d7d27b697375b7f88f0f
Render in the network_config from the node topology_map
and switch the 'node provision' command to use the
'--network-config' option so that the tripleo_network_config
role is applied to deployed nodes prior to running the
overcloud deploy command.
Related: blueprint network-data-v2-ports
Depends-On: https://review.opendev.org/790286
Change-Id: I438220744bdb1d426c8484d8548716278737ff86
Adds support for a new ansible variables ephemeral_heat and
ephemeral_heat_args, which will allow job configs to deploy with
--heat-type in order to use the ephemeral heat deployment.
Implements: blueprint ephemeral-heat-overcloud
Signed-off-by: James Slagle <jslagle@redhat.com>
Change-Id: I29cf6dd8a32242f27a40946688f9dede8968c7f9
When 'network_provision' is enabled run the command
to provsion neutron Virtual IP API resources prior
to creating the heat stack, and include the environment
file to override the stack resource's to use the
'deployed_vip' templates.
Related: blueprint network-data-v2-ports
Depends-On: https://review.opendev.org/779634
Depends-On: https://review.opendev.org/775406
Change-Id: Ic2fefa4d6ed980a74feeb57813e980260b8a5b84
Add a dummy overcloud-vips-deployed.yaml file so
that we can land https://review.opendev.org/779828
before https://review.opendev.org/774903 where there
is a circular dependency.
Change-Id: If10a80ca47e21214f9b9c35d529976eba9958d8a
Related: blueprint network-data-v2-ports
Include the environment file for enabling memcached TLS when TLS
Everywhere is enabled, so that it is tested in the CI (FS039).
Change-Id: I9da7ab89453364e5405ad183b0f08dc2e5b014af
This patch remove useless tripleo-validations calls in the
tripleo-quickstart-extras playbook.
Only validations and standalone is used for now in CI.
The other implementations was legacy implementation that is not
used anymore in CI
Change-Id: I2ef1f06007c646ef4307c0cc0b6f60af414f9234
The overcloud-networks-deployed.yaml must be added after
environments/network-isolation.yaml so that resource's
are actually overriden.
Change-Id: I72c9e16588fd4fa1c90c5835907ff552fab7132e
Related: blueprint network-data-v2
Add option 'network_provision' (default: false).
When enabled composable networks are deployed with
the `openstack overcloud network provision` command
prior to creating the heat stack.
The overcloud-networks-deployed.yaml is added to the
network_args in the deploy command to activate the
network/deployed_networks.yaml template.
Depends-On: https://review.opendev.org/762348
Depends-On: https://review.opendev.org/751875
Depends-On: https://review.opendev.org/762652
Change-Id: I842820bfe9998574e53c79a8a4715e637350ad9c
This is not required as all the roles of the user are
delegated by default to the trustee. Also removes the
tempest configuration related to that.
Change-Id: Id57ecea69a3568767f5b4bea101c14ad1335d286
To make overcloud-deploy role support deployment of multiple overcloud
stacks using a single undercloud node - we have generalized the vars
for stack name and removed hardcoding on "overcloud" name.
We also created a new playbook which install two overcloud stack -
overcloud and overcloud-two.
we also created j2 version of deploy and post-deploy script for
overcloud-two stack.
Intention is to create a new ci periodic job which test multi overcloud
stack deployment, The new ci job will not be executed upstream but
rather in periodic only.
Change-Id: I353a0497cb4d44f82806381ee0a33b978c86be5f