This commit is part of a series to retire the Packaging Deb
project. Step 2 is to remove all content from the project
repos, replacing it with a README notification where to find
ongoing work, and how to recover the repo if needed at some
future point (as in
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project).
Change-Id: Ib9526e42d9546db85d5612eda8131e1df0c698b8
In kubernetes with atomic we have a set of certificates that we use in
three places:
1. etcd
2. kubernetes apiserver
3. kubernetes service accounts
In order to make service accounts work we need to set the common name
properly in the certificates.
Partial-Bug: #1705694
Change-Id: I04ed3bba938f0d5f340e2141be94058c38c2ed2b
kube-apiserver configuration was modified using sed and / as a
delimiter. However, the arguments were containing / so the sed command
was breaking.
Furthermore, the KUBE_API_ARGS was added without quotes which was
working when using the file in a systemd unit, it does not work when
sourcing with . or source.
Implements: blueprint run-kube-as-container
Change-Id: I49714f51159ea1bf4e9918bbec82749443cc1751
- Use addOnCleanup instead of addOnException. This will make copy
logs to run whether tests pass or fail.
- Also try to copy logs if setupClass Fails.
Change-Id: I76b135ade4c1ed4987f9bcbe1d5ded09ad57deb9
The patch https://review.openstack.org/#/c/437048/ changed the
permission of /etc/sysconfig/heat-params to 600, so non-file owners
would require use of 'sudo' in order to access the file. This patch
fixes it
Closes-Bug: #1704076
Change-Id: I8bb4a12deb92fa5035bbbb8fc6ce4736ed99ea78
As part of the docs migration work[0] for Pike we need to switch to use
the openstackdocstheme.
[0]https://review.openstack.org/#/c/472275/
Change-Id: Id7b352dc0c72a79482e77f92f6b588e5760ad754
Mitaka branch is EOLed. The Ironic team is going to proceed with
removal of SSH-based power and management drivers for virtualized
HW which were deprecated back in newton release.
http://lists.openstack.org/pipermail/openstack-dev/2017-July/119284.html
Change-Id: I7351573a20f3835f481ab1973b6439d8ca2b8f60
Allow setting the size of a volume for etcd storage.
Default is 0 which matches the current behavior - no persistency.
Related-Bug: #1697655
Change-Id: I8a30df63684133a902ae209ba6c124da2a567d3f
Following [1], cluster objects have a docker_volume_size attribute.
If not explicitly set on creation, the value of this attribute should
default to the value of the same field on the cluster's template.
When not provided, the API Cluster object's docker_volume_size field
takes the value wsme.Unset, rather than None.
[1]
79039bb419
Change-Id: Iad5231643c01ec9698c932b59806781034390795
Depends-On: I510ff10d708a237be0cb88d3ff7094d7c81f5875
Closes-Bug: #1702314
When building a fedora atomic image using magnum's DIB element,
setting the DIB_RELEASE environment variable does not affect the
release of the fedora-atomic image built, even when
FEDORA_ATOMIC_TREE_REF and FEDORA_ATOMIC_TREE_URL take their default
values - fedora atomic 24 is always built.
Further, fedora atomic 24 is not supported by magnum for kubernetes
in newton onwards since the configuration of flannel was changed[1].
This change uses the DIB_RELEASE variable to set the default values
of FEDORA_ATOMIC_TREE_URL and FEDORA_ATOMIC_TREE_REF. This ensures
that fedora atomic images have an expected release, and one that by
default is supported by magnum (currently DIB_RELEASE defaults to 25
in diskimage-builder).
[1] https://bugs.launchpad.net/magnum/+bug/1679301
Change-Id: I9e1c846657ac9e65e2cdd8d32c96cdbf85900ba0
Closes-Bug: #1699766
Closes-Bug: #1699765
Seen fails in some cases due to short timeout. This will be a safe
amount of time to avoid failures.
Change-Id: Iabe9751e5d3dba2cb7b57504bf38b55a5c7aba2d
Some of the available checks are disabled by default, like:
[H106] Don’t put vim configuration in source files
Change-Id: I18babfaae830b13a53dcd13ce9233fc28652a787
Add docker_volume_size as an option during cluster create. If not given,
the default is taken from the cluster template.
Add docker_volume_size in the Cluster object and use that instead
of the one from ClusterTemplate.
Update both magnum and magnum cli documentation to reflect the above changes.
Partial-Bug: #1697648
Implements: blueprint flatten-attributes
Change-Id: Ic6d77e6fdf5b068fa5319b238f4fd98b4d499be4
Tony Breeds
yatin