The Mesos slave has many different flags and different user have
different requirement for different parameters, add isolation,
work_dir, image_providers parameters for slave in mesos bay to
give end user more choice. for example Set the parameters to
support Container Images in Mesos Containerizer
Note: support Container Images in Mesos Containerizer needs mesos
version >= 0.28
Partially-Implements:blueprint mesos-slave-flags
Change-Id: Ib4fd7076704a3266f0cf2addf08896729ec6062f
Partial fix for problems output by checkbashisms for file
magnum/templates/swarm/fragments/configure-docker-storage.sh only.
Change-Id: I6fc8c789a2b5a1838c0ae98521e236c80a199323
Partial-Bug: #1561232
From http://logs.openstack.org/64/302064/6/check/
gate-magnum-python27/6c92a13/console.html the log clearly
said bay-xx-xx-xx-xx is an invalid UUID. Using UUIDFields
with invalid UUIDs is no longer supported, so in our test
let's use real UUID case for that.
Change-Id: I0f3dbd8748293741cb5501365aee710220eb3ea0
Co-Authored-By: Spyros Trigazis <strigazi@gmail.com>
In order for automated image builds to run, create
this script that can be called from magnum jobs, to
install needed dependencies for diskimage-builder
and fedora-atomic builds.
That script will be run on the VM that will be
spinned to run the image builds, targetted for ubuntu-trusty.
Change-Id: Icf5a2c79e47e632be2ac49bc9ccc528b4f604eb2
Implements blueprint fedora-atomic-image-build
The usage of ca-show and ca-sign have been changed in [1].
So we should update the doc.
[1] https://review.openstack.org/#/c/303272/
Change-Id: I14d98da2560e73e6d2f5cb64b089cc904974c8c5
* Rename tenant to project in functional test In particular,
rename "admin_tenant_name" to "admin_project_name" and
rename "tenant_name" to "project_name". These configs have been
renamed in tempest [1], so Magnum needs to adapt the change.
* Temporarily remove "subjectAltName" from CSR config, because
it caused failure of certificate signing, possibly, due to a
bug or imcompatible change in pyOpenSSL 16.0.0.
[1] https://review.openstack.org/#/c/301167/
Change-Id: I41438cbfaefd9d04d7e73a4f46f5ece1494b349c
Closes-Bug: #1568212
Closes-Bug: #1567691
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
Magnum SSH into each bay node and copy logs when a test fails.
The specified SSH key path is relative to the home directory ("~"),
which didn't get expanded correctly.
Change-Id: Ie7265adf8027309a4482247283dd52a18397d5d7
Closes-Bug: #1566501
Trust can only be deleted by the user who creates it. So when
other users in the same project want to delete the bay, we need
use the trustee which can impersonate the trustor to delete the
trust.
Change-Id: I9f87cdf07066d316722e798cd0755f0fff5c2a02
Closes-Bug: #1552457
Currently, we use the users auth token, which expires after a while.
We need to use a trust instead.
Remove user_token at the same time.
Change-Id: Id1d34c59eccd70be24c5b9e00cd921b5a9d59860
Partially-Implements: blueprint use-trust-for-tls-cert-generation
Cpu metric is important to a cluster, add cpu util to notification bus.
After this patch get applied, we will get following metrics:
{'metrics': [{'unit': '%', 'name': 'cpu_util', 'value': 30.0}, {'unit':
'%', 'name': 'memory_util', 'value': 4.795204795204795}]
Change-Id: I450c8b5afe766be4da4fb42c2ecb47db52b245f3
Introduce reno to handle release notes as files in-tree.
Also added documentation on how to add re for changes, after this we
will require changes to add reno if they have some significant changes.
Implements: blueprint add-reno-for-release-management
Change-Id: Ifc18b78ab5ce89375b85f6ac4344ffafa7f1c48b
This will force pip install to use the upper-constraints.txt specified
version of pip modules. When you don't do this, you are out on the
bleeding edge and become unstable everytime some python library in the
wide world changes in a way that you don't expect.
Change-Id: I962329075b11d3790dc586ba33fe19fc64f1e4f9
Closes-Bug: #1563038
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
Cryptography 1.3.1 has been released which closes this bug, meaning this
patch can now be reverted. As the problem has now been fixed.
https://github.com/pyca/cryptography/issues/2844 is now closed.
This reverts commit a75b5fb77a.
Change-Id: I387ff9fe099460f98303cf930b79db1632791ccd
Previously,the kubernetes bay type did not support the Magnum Container
Volume Model. This patch adds support for volume through the following:
1. Add volume_driver, region_name to
kubernetes bay type.
2. Update kubernetes unit tests to support container volume.
3. Update kubernetes heat templates for container volume model.
Note: The Container Volume Model of Kubernetes need the
kubernetes Version >= 1.1.1 and docker version >= 1.8.3
Change-Id: I8f568087f8e8254cb14a81edb526e596da33abcc
Partially-Implements: blueprint magnum-integrate-with-cinder
Cpu metric is important to a clutser, add cpu util to notification bus.
After this patch get applied, we will get following metrics:
{'metrics': [{'unit': '%', 'name': 'cpu_util', 'value': 30.0}, {'unit':
'%', 'name': 'memory_util', 'value': 4.795204795204795}]
Change-Id: I44cc2edf2a33ff2991ba0b006d802dc3efee42b6
It consumes an external deployed tree, and generates a
cloud bootable image based on that. It relies on lvm element
to generate the volumes needed for the image.
Change-Id: Ie681064d799279519adcc8e1bcf7a61ff9120042