GitLab

Change-Id: Ia3c745dbb514aef8fc5bc7829920f0e49a35c2d8
Signed-off-by: Spyros Trigazis <spyridon.trigazis@cern.ch>

Magnum cluster deletion is not behaving as expected. While it appears to
delete successfully, _delete_complete routine in
magnum/drivers/heat/driver.py is never called because the status of
nodegroups have not had the chance to sync with Heat before
_check_delete_complete is called. As a result, for example, trustee user
accounts are left orphaned. This PS changes or order of activities so
that _delete_complete is invoked successfully.

Story: 2007965
Task: 40459

Change-Id: Ibadd5b57fe175bb0b100266e2dbcc2e1ea4efcf9
(cherry picked from commit 1cdc0628)

Now Magnum is not deploying any service or workload on k8s
worker nodes which need to get credentials from local to talk
to Magnum control plane. So the cloud-config file should be
removed from worker nodes to reduce the attach surface from
a security point of view.

Task: 40791
Story: 2008090

Change-Id: I72e418491cbd19291527bbe4b504d599c740fea9
(cherry picked from commit c84653cd)

Task: 40801
Story: 2008098

Change-Id: I1802e4002d9aa89a321f130a16fd8021a773b73a
(cherry picked from commit 385bc970)

Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.

Until the requirements repository has as stable/victoria branch, tests will
continue to use the upper-constraints list on master.

Change-Id: Ica4ddd5eb3d2a3deec6c4807bac863fa08cc79e1

Change-Id: I850b1073ae565b7a98fcd885d80eed1e368dee5f

As per victoria cycle testing runtime and community goal,
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).

Add noqa doe C901 and F811 pep8 for Focal, failure can be
seen in - https://review.opendev.org/#/c/743130

Depends-On: https://review.opendev.org/#/c/738328/

Change-Id: I95fa40551d842ce652ab937b8848c64f09a3e131
Story: #2007865
Task: #40190

From k8s v1.19.x, kube-apiserver binary can't accept any parameter,
and actually we're not using the pass-in KUBE_API_PORT. So it's
safe to drop it.

Change-Id: I12a0bb3441d18c3b68a8db4ab3234e04e5218cd2

Change-Id: I455ed0106dd257acbde58af408de0bf6e6abe7d3

When using delete_on_termination and the booting of the instance fails
on the first attempt, the second attempt will fail with Heat.  The
reason is that with delete_on_termination set to True, Nova will delete
the volume when Heat deletes the ERROR'd instance and it will then
result in the follow-up boot to fail with an error along the line of
unable to find volume, which masks the real failure from the user (which
could potentialy be aquota issue).

With this patch, we no longer set this and instead use the default of
false.  This will not mean we will leak volumes because when we delete
the stack, Heat will do all the right things and delete them in order,
making sure the volume disappears eventually.

Change-Id: I362cea7bf57825035d13d234d0181a2b1fca5743

Change-Id: Icd923f9e020dfe27f4e9b14e40f0ad53da49e0ff
Signed-off-by: Spyros Trigazis <spyridon.trigazis@cern.ch>

The password contains special characters, so we need to
quote the password string on docker login.

Change-Id: Ie826c78309395765911db01e6d412426e46f176e
Signed-off-by: Spyros Trigazis <spyridon.trigazis@cern.ch>

Now k8s cluster owner can do CA cert rotate to re-generate CA of
the cluster, service account keys and the certs of all nodes will
be regenerated as well. Cluster user needs to get a new kubeconfig
to access kubernetes API. This function is only supported by
Fedora CoreOS driver.

To test this patch with python-magnumclient, you need this patch
https://review.opendev.org/#/c/724243/, otherwise, you will see
an error about "not enough values to unpack", though the CA cert
rotate request has been processed by Magnum server side correctly.

Task: 39580
Story: 2005201

Change-Id: I4ae12f928e4f49b99732fba097371692cb35d9ee

Change-Id: I161b0af3ef7fbf3f81ece9a4a5689ec84d8b715d

In I157a3b01d169e550e79b94316803fde8ddf77b03, support for
master_lb_allowed_cidrs  was introduced but only for the fedora coreos
driver. However, this parameter is also supplied to fedora atomic
clusters but the template does not expect this parameter. As a result,
cluster creation fails due to backward incompatibility. This PS
addresses this issue.

Task: 40632
Story: 2007478

Change-Id: Ia781288f7aa35146582b10d5762aa05e3b107dce

The magnum-container-publish job first
has to run the container-build job,
so it doesn't make sense for the publish job
timeout to be shorter than the build job timeout.

Change-Id: I7f8b1b91eba733ecda01dc385c594d04f238a30b

Also update v1.17 and v1.18 to the latest
patch versions.

Change-Id: Id5e9d346733cf8a3b2e2d0da7f86340800aec090

 + Adds placeholder ConfigMap and with a template
   keystone-sync-policy that can be edited by the cluster
   admin
 + Docs for sync policy added
 + Docs for auth policy edited for grammar, spelling
   and clarity.

Task: 39136
Story: 1755770

Change-Id: I0afc19c630e077c079f7f6a52439f4aee8bf5eb8

Additionally remove non-voting status of coverage job. 1% toleration is
enabled for allowed_extra_missing lines. If we need to lower the 90%
threshold for coverage in the future, this can be decided then.

Change-Id: I7bc80c34dc6e6e054c61181410d88e7b747310c9

+ Fedora coreos cluster template
+ Steps to cread Fedora Atomic 27 image
+ Deprecation notice for CoreOS, Fedora Atomic

Change-Id: I381c4d5dbcd0c920a41040f6d5fec341144c05f0

As part of the Victoria cycle, all legacy jobs need to either be
converted or dropped. Since we no longer use these jobs that have been
parked in the experimental queue, it makes sense to drop them.

Change-Id: I16f15d8fb6887ff9076b20d473d9d39cec455b96

Adding the master_lb_enabled option when creating a cluster,
which will benefit both the cloud provider side and the end
user side. For cloud prodiver, they don't have to maintain
separate cluster templates with or w/o master_lb_enabled enabled.
For end user, they can easily use one single template to create
different clusters with different configs.

Task: 39680
Story: 2007634

Change-Id: I0b586f05168ece84fd340ef7493a56688191053d

Change-Id: Ic6fef848726b7b20eaf0cd09f67d9ea21b5ac067