We experienced issues caused by network resources created with the same
name, which makes ansible playbooks to behave differently.
Due to fact, that there is not yet OpenShift infraID accessible on the
stage of creating network resources, there is a need to create
deployment unique identifier in some other way. This patch implements
generating such identifier independent from OpenShift deployment id.
Co-authored-by: Maysa De Macedo Souza <maysa.macedo95@gmail.com>
When following this guide using RHEL or older Fedora there is an issue
with the openstack.cloud with latest version (2.0.0) as it will need
openstacksdk in version 1.0 or higher, which is unavailable in mentioned
Linux distribution.
In 4.15 Kuryr is no longer a supported NetworkType, following its
deprecation in 4.12. This commit removes mentions of Kuryr from the
documentation and code, but also adds validation to prevent
installations from being executed when `networkType` is set to `Kuryr`.
Compact clusters have been supported for a while in IPI.
To also allow compact clusters on UPI, the security group rules
for UPI should be adapted enabling the same ingress traffic
that is enabled for workers.
In 4.12, the default CNI will be OVNKubernetes.
This change will deploy ovnk by default as well
as adjust tests, docs and comments to reflect
the same.
Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
The UPI workflow needs the bootstrap ignition file to be hosted
somewhere. Prior to this patch, the first proposed example used Swift.
However, the example was using commands that are not available in the
openstack client shipped with the recommended operating systems and
repositories.
This patch removes the Swift example and focuses the workflow on using
Glance instead, along the lines of what the IPI installer does. The UPI
docs still mention that any hosting system can be used, including Swift.
This patch adds:
* explanation on how the name of the RHCOS image on Glance must match
the content of inventory.yaml;
* instructions for removing the image after use.
* a scripted unique name for the RHCOS image in Glance, so that the UPI
tests can be run in parallael.
With this patch, the documentation for installing on OpenStack with UPI
is made machine-readable.
Additionally, UPI resources are added to the CI container image.
Adds docs for manually creating worker nodes with SR-IOV NICs attached. These
docs walk users through what basic components are needed and why, as well as
providing examples using the openstack command line client.
Fixes: OSASINFRA-2159
- Update package names for Fedora, now python3
- Replace the usage of swiftclient by openstackclient
for container/object creates (which uses clouds.yaml)
- Fix logs alignment
If the external network is not provided, the router will not be created
and external connectivity will be a respopnsibility of the operator.
Floating IPs will be set if available, on an individual basis. The
external network is a requirement for FIPs; if not provided, the
playbooks will error.
The bootstrap FIP is now required to be created manually like the other
FIPs.
Similar to 0bf09af3bc that fixed the same
issue for IPI, we need to trim EOLs from the ca-cert bundle in the UPI
scripts otherwise ignition might not accept it as valid.
Because the script is passed on the command line to the python
interpreter, it's enclosed in simple quotes. As a consequence, we should
use double quotes for strings otherwise we get a SyntaxError.
The example script to remove apiVIP and ingressVIP attributes from the
`install-config.yaml` file used an invalid python keyword. This commit
fixes it.
By turning the release into a variable, we make the snippet to download
the OpenStack UPI playbooks more user-friendly. It's now easier to
switch from version to version.