Fedora Atomic 27 has end of life for a while, it's time to replace it
with Fedora Atomic 29 now.
Task: 36356
Story: 2006441
Change-Id: Iab131745854b0b908be17bd17c7510cd54dde1f5
This patch brings the Fedora Atomic version used in gating to
the latest one which includes some improvements alongside a newer
version of Docker (which seems to run things better overall).
Change-Id: Iad0a1f57b29aec9a0cdb2a104fdaa5970133cfb4
In Fedora Atomic 27 etcd and flanneld are removed from the base image.
Install them as a system containers.
* update docker-storage configuration
* add etcd and flannel tags as labels
Change-Id: I2103c7c3d50f4b68ddc11abff72bc9e3f22839f3
Closes-Bug: #1735381
Until [1] is in kubernetes we need to redirect from /v2 to
/identity/v2 for the cloud provider to work.
[1] https://github.com/gophercloud/gophercloud/pull/423
Change-Id: I5206e75e9528ceb8428c70df67e6ba26d01c4772
* Swarm-mode is the fastest cluster to deploy since it doesn't
require to pull anything from outside.
* Add the output nodes for swarm-mode too.
* Disable copy logs (I think a better practice is to copy logs
on demand).
* Don't run test_create_list_sign_delete_clusters, because it is
very unstable on the CI.
Partially-Implements: blueprint swarm-mode-support
2nd commit message:
Update to Fedora Atomic 26
This patch moves the current master to test against Fedora Atomic 26,
in addition, it switches to downloading from Fedora mirrors.
2nd-Change-Id: I9a97c0eb78b2c9d10e8be1501babb19e73ee70c1
3rd commit message:
Set default iptables FORWARD policy to ACCEPT
With the release of Docker 1.13 which is available in Fedora
Atomic 26, it no longer sets the policy of the FORWARD chain
to ACCEPT[1]. Therefore, CNI networking such as Flannel will
cease to work.
This patch sets the policy to ACCEPT so that traffic can work
once again for deployments which are based on Docker versions
which are newer than 1.13
[1]: https://github.com/moby/moby/pull/28257
3rd-Change-Id: I1457602748619f38f87542fc01a2996ee80e58b7
Closes-Bug: #1708454
Co-Authored-By: Mohammed Naser <mnaser@vexxhost.com>
Change-Id: I86d4dcc94fff622be4ee2acc8dd60ed81bc5d433
"m-api" is already used by Manila so switch to "magnum-api"
and "magnum-cond" for devstack.
Change-Id: I0f5e57dd263164652813088fe624f62cda664727
Closes-Bug: #1569879
It looks the official Fedora mirror is unstable right now, so we
uploaded the image to fedorapeople. This is a temprorary solution.
Once the official mirror become stable, we switch back to it.
Note: alt.fedoraproject.org seems to have a newer image and
the official mirrors (download.fedoraproject.org) do not seem to have
gotten the new image yet. So when download.fedoraproject.org
redirects (302) to a mirror the image does not exist there. We can
pull image from alt directly, but we opted for using fedorapeople as
we don't want to introduce load on alt.
Co-Authored-By: Hongbin Lu <hongbin.lu@huawei.com>
Closes-Bug: #1567124
Change-Id: I441898d846d1768b9723b293196b5339271a377e
Change the devstack image to the default Atomic 23 image.
Update templates not to rely on interface naming because the names
changed between Atomic 21 and Atomic 23 images.
Add a functional test to validate minion node registration.
Update docs to refer to a generic Atomic image.
Co-Authored-By: Hongbin Lu <hongbin.lu@huawei.com>
Implements: blueprint atomic23
Change-Id: Id67244e3f452b3c7c3c46fdabcca3a5c141a76c0
It is possible not to give SCREEN_LOGDIR variable in devstack.
And also, SCREEN_LOGDIR is creating in stack.sh itself [1].
So we can remove our code which is creating SCREEN_LOGDIR.
This code breaks stack.sh process if user doesn't give this
variable.
[1]: 2688eedc51/stack.sh (L454)
Change-Id: I5c6ce81a97635b60fc1633397a24f93dc590fad6
Closes-Bug: #1548197
As new oslo.versionedobjects 1.0.0 release, we not need
this work-around now. So remove it.
Closes-Bug: #1518147
Change-Id: I7cba6de5ebbb655647a4c833d04c4930c9cd1fbc
As oslo.versionedobjects include new fix
https://review.openstack.org/#/c/246721/
but it not release new version to include that fix
so jenkins still failed for that. We need pin to not
use version with that issue.
Change-Id: Ib589fb019f94a9f44925b378dccfadabdd9e5463
This reverts commit 4115c9ae8d. That
commit is a temporary fix for the functional gate. Now, the issue has
been fixed in the neutron-lbaas repo [1]. Therefore, we reverted the
temporary fix here.
[1] https://review.openstack.org/#/c/241481
Change-Id: Idd204e094d4a24f4b3440ee3f4294ea9407b467f
This patch should fix the functional gate. The issue is that devstack
switch to stevedore aliases for interface_driver configuration [1],
but lbaas doesn't use aliases. This patch fixed the broken config.
This patch should be considered as a temporary workaround. We need
to investigate why devstack doesn't populate the correct config at
the first place.
[1] https://review.openstack.org/#/c/237519/
Closes-Bug: #1512933
Change-Id: I73b9e146ad4cc253e6a04bcadc07f124a7c96df5
Kubernetes Release 1.0 was announced at OSCON
A new Fedora Atomic image has been built with version 1.0.4 and
this series of patches will update the templates, scripts, documents
to work with the new image.
The api has also been changed from v1beta3 to v1 and the beta
api is no longer available, so the interface between Magnum and
Kubernetes master are updated as well in this series of patches.
This particular patch will bring up a V1 cluster with the
bay-create command. Because the switch to the V1 API requires
all the code changes to be applied at once, this patch pulls
in portion of 3 patches together. The changes include:
1. devstack plugin downloads the new image.
2. k8s conductor and other code calls the new V1 client and
k8s methods.
3. Configuration for k8s services and docker updated with
new parameters.
4. Minion registration and example code updated to V1.
5. Functional tests updated to V1.
6. Gate test setup points to the new image.
Co-Authored-By: Hongbin Lu <hongbin.lu@huawei.com>
Change-Id: I046931ad491e8b7ee45943852901eac5c3df913e
Partially-Implements: blueprint kubernetes-v1
Currently, we instruct users to manually configure IP tables for IP
masquerading. We should take a step forward to automatically configure
IP tables in Magnum's devstack plugin.
Note: The functional gate test needs this patch to allow internet access
inside the provisioned bay.
Change-Id: Ia2ca494f85bfed76a80027bc3310494494d704cd
Closes-Bug: #1478106
As magnum has been added in requirements project, we
not need to add such hack any more.
Closes-Bug: #1460874
Change-Id: I4f661c398186067cd2b5a1f3a13ae77bb3809396
- convert the magnum command line in post_test_hook.sh
into test cases
- delete key-pair after functional tests are run
- adding test for creating/deleting baymodels
- adding test for creating/deleting bays
- Remove dummy test (tests/functional/test_magnum.py)
templates.
Partially Implements blueprint: improve-functional-tests
Change-Id: I2937f2659a29e0f9b411c10b080db79bc46ce910
This change introduces kubernetes 0.15 into the system.
Co-Authored-By: Andrew Melton <andrew.melton@rackspace.com>
Change-Id: Ia81910546a06a0663a96302aa81c901e144d463f
Partially-implements: blueprint python-k8scient
So running "magnum-template-manage list-templates" in
post_test_hook shows a traceback as mentioned in the
bug linked below. Since the requirements repo is frozen
and not yet open for liberty. We need to work around this
problem for now.
Closes-Bug: #1443729
Change-Id: I3284af4a3e01c6738c2e1bdbf57f1d6e019b6d88
Magnum has been converted to new devstack plugin model, so we need
to update the dev-quickstart doc.
This patch also fix a content repeat issue in devstack plugin script.
Change-Id: Ibcb93a7e83a5c7f3a3f3727b957b1c45beeed5ae
Closes-Bug: #1441514
Switch over to the new plugin style as documented here:
http://docs.openstack.org/developer/devstack/plugins.html
Makes it very easy to setup a CI job. Added a new
directory for functional job and the tests are run
from the post_test_hook.sh. There's even a "magnum bay-list"
in the shell script to show that we are actually making
calls to the magnum API endpoint and things are working
fine. Note that this is just the minimal plumbing needed
and there's a lot more effort needed to come up with
proper test cases for testing magnum functionality.
Closes-Bug: #1439621
Change-Id: I88d45015338ef55713b32de196f9071c8fc2031b
Michal Nasiadka
yatin