DevStack stopped accepting Ubuntu 20.04 Focal, so we need to bump the
version we use to Jammy. This commit does so.
Change-Id: I7b227dfb29b49ff6a561209938a2c263f5dd2f90
For a long time gate jobs with Amphora are unstable due to LBs being
unstable due to Amphora somehow not working as expected. The gates with
OVN Octavia provider are much more stable for the same cases. This
commit makes all the jobs with Amphora non-voting to fight constant
rechecks that we're forced to do.
Change-Id: I94a7403fa1dd038b7f9f8a922a4f635ed5816067
Network Policy e2e tests are broken for some time now. It doesn't bring
any value to run them at current state. This patch will disable those
tests.
Change-Id: I8ce459edddf6f8307376eae68bbc75d173f0d19a
Turns out, that all the images has been moved from k8s.gcr.io to
registry.k8s.io, so that there is no need to distinguish between those
two locations for older version of k8s (especially the one which we are
relaying on for docker gate). In this patch we switch over to the
registry.k8s.io for all of the supported kubernetes versions.
To make it work it is also requires to bump kubernetes 1.23 to latest
minor version, otherwise there will be issues with pulling coredns
image.
Change-Id: I7ed0ae76108a409bc72bc61ab7c12164e8277257
Depends-On: https://review.opendev.org/c/openstack/devstack-plugin-container/+/874573
1.23 version of Kubernetes is the last one, which supports
dockershim[1], therefore it needs to be pinned to that version to make
it work with docker. Any upcoming Kubernetes version bump will be
ignored for this particular gate, and it will be removed when Kubernetes
makes it EOL[2].
[1] https://kubernetes.io/blog/2022/02/17/dockershim-faq/
[2] https://kubernetes.io/releases/patch-releases/#1-23
Change-Id: Ia509264ad45ef5321412ba244b160dffc1c5cc60
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: I86154b8c7db90ac6fd5467c1b0d29c0b84528ee4
For some reason linuxbridge was set as mechanism driver in OVS gates.
This commit disables that as linuxbridge became experimental in Neutron
and gates fail.
Change-Id: I2dd5c7f19af73badae49d2509efb0016335e6c9e
We face general instability of the Amphora jobs that we have. A while
ago we've made sure that these jobs are scheduled on the clouds that
support nested virtualization in order to boost performance of the
Amphora LB VMs. Now it turns out we haven't configured DevStack to
actually use kvm instead of qemu, so it's possible that we were still
running these jobs with software virtualization.
This commit attempts to reconfigure DevStack to actually use kvm and
nested virtualization.
Change-Id: I57f70c1cb140d4fa54d13b6c759a0179d8adb7b4
According to [1], the needed version for OVN v21.06.0 is
a4b04276ab5934d087669ff2d191a23931335c87
[1]4b0a02635f
Related-Bug: #1967472
Change-Id: I73a11d4a02c811366c177fa31d02599e247fea3a
There is a issue[1] with the old versions we were using,
let's attempt to bump them.
[1] https://bugs.launchpad.net/neutron/+bug/1964339
Change-Id: I4a9a9f877c2a0aea2bf3e43e179afedb653b8464
In I950e81d3f9f23493f26d9f824d3052ed375ae62b I've forced the jobs
explicitly saying "amphora" to run on clouds with nested virtualization
enabled. I however omitted the jobs that are not having "amphora" in the
name - defaults, IPv6 and OVS jobs. This commit fixes this.
Change-Id: I1e70118bb9c7d80e78806c3319c95af7efd01a08
Seems like it's now possible to request nodes from a cloud that supports
nested virtualization. This is super cool for jobs using Amphora and
this commit attempts to switch these jobs to use it.
Depends-On: I203773de2b8c0d1b21ef3f722df7ed7da562a892
Change-Id: I950e81d3f9f23493f26d9f824d3052ed375ae62b
Before switch to kubeadm we used to use manual approach for installing
all the bits with option for switching container runtimes between docker
and cri-o. With this patch we re-gain that ability with simply setting
appropriate container engine variable for devstack-plugin-contaier to
use either CRI-O or default Docker.
Depends-On: https://review.opendev.org/c/openstack/devstack-plugin-container/+/817231
Change-Id: I273888a7428611b40802dc5dd53fcee864ce43da
Gate queue should not have non-voting jobs, so this commit removes
kuryr-kubernetes-tempest-amphora from gate.
Change-Id: I9fca68c995bfb29aa747b187f1b464351762d2c4
Also, rearrange tests files.
Job hierarchy looks as follows:
- kuryr-kubernetes-base (base tempest job)
- kuryr-kubernetes-base-ovn (derived from base for neutron OVN)
- kuryr-kubernetes-tempest-amphora
- kuryr-kubernetes-octavia-base (ovn-octavia-provider)
- kuryr-kubernetes-tempest (alias for the parent,
used in projects kuryr-tempest-plugin and os-vif)
- kuryr-kubernetes-tempest-ovn-provider-ovn (alias for the parent,
used in project ovn-octavia-provider)
- kuryr-kubernetes-tempest-systemd
- kuryr-kubernetes-tempest-centos-7 (this one is probably
broken)
- kuryr-kubernetes-tempest-defaults (default settings for
kuryr-kubernetes, so OVN + amphora + default set of handlers,
default subnet and sg drivers)
- kuryr-kubernetes-tempest-ipv6
- kuryr-kubernetes-tempest-dual-stack
- kuryr-kubernetes-tempest-lower-constraints
- kuryr-kubernetes-tempest-l2
- kuryr-kubernetes-tempest-pools-namespace
- kuryr-kubernetes-tempest-crio (currently broken)
- kuryr-kubernetes-tempest-multinode
- kuryr-kubernetes-tempest-multinode-ha
- kuryr-kubernetes-base-ovs (derived from base for neutron OVS)
- kuryr-kubernetes-octavia-base-ovs (amphora)
- kuryr-kubernetes-tempest-ipv6-ovs
- kuryr-kubernetes-tempest-amphora-ovs
- kuryr-kubernetes-tempest-multinode-ovs
- kuryr-kubernetes-e2e-np (base devstack job)
For convenience, tempest jobs are in two files: one for multinode jobs,
and one for one node jobs. Network policy job is in its own file, since
it have different parent (devstack).
Change-Id: I198f138feb9bd7b6cc659ac8cd788cddd5be9439
This patch is originally an automatically generated patch to ensure
unit testing is in place for all the of the tested runtimes for the
next given cycle (this time yoga). However there was an error during
the patch generation as a gitignore rule excludes all hidden directory.
This patch is now removes the general hidden directory ignore rule,
too, to avoid such errors in the future.
Change-Id: I3341f08a7f331fb8b97b2d75106eefcec9b2d5d7
This patch provides an implementation for joining node to the Kubernetes
cluster by using `kubeadm join` command.
Change-Id: I71d2b99e0c92a12c4e64395f6c4dafa4b69f168f
Depends-On: Ife21874c0a71ba07723094c0f880aabcf5825b77
Currently, by default, kuryr-kubernetes services (controller and CNI
daemon) are suppose to be run as a systemd services. The reality is,
that in most real world deployments we are using containerized services.
In this patch variable KURYR_K8S_CONTAINERIZED_DEPLOYMENT will now have
default value set to True, which means, that without even setting it,
deploying kuryr-kubernetes will be containerized.
Secondly, we agreed[1], that all the gate names should also reflect that
change in their names.
And finally, non working and outdated local.conf samples for
OpenDaylight has to be removed.
Behaviour for sample local.confs wasn't change: using them to spin up
devstack will still use systemd services.
[1] https://etherpad.opendev.org/p/apr2021-ptg-kuryr
Change-Id: I2c13893c80e9e5b3b2ac0cb64dd9bd9a40d99e63
Till now, for installing kuryr-kubernetes and one of the crucial service
- kubernetes, there has been used manual method for installing it in
specified version. Over time it became a burden to follow requirements
and constraints, therefore decision has been made to use recommended way
of installing Kubernetes - kubeadm. In this patch devstack installation
of the kuryr-kubernetes and its dependences has been heavily reworked.
Other than that, OpenShift related functions has been removed, since
they were all outdated and non-working for the long time.
Change-Id: Ife21874c0a71ba07723094c0f880aabcf5825b77
As Devstack is dropping support for Ubuntu Bionic in favor
of Focal and the bionic node is not needed anymore on the crio
gate with the change os repos to kubic OBS project[1], we can
remove the nodeset definition.
[1] d4de1bb990
Change-Id: I64bcfe8f9c5795f1724aa1e3b7278660f79fa7f6
The Neutron community is planning on switching the default network
backend in DevStack to OVN soon and to avoid any gate breakages we need
to explicitly enable ML2/OVS where it makes sense.
This patch is enabling ML2/OVS for the non-OVN jobs in the gate. Prior
to this patch the job were enabling the ML2/OVS services such as q-agt
and q-dhcp but it wasn't setting other required options (e.g Q_AGENT).
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
Change-Id: Iae420403d3d84325830bded8633b2a29430b36bb