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
After  jobs are return false(SUCCESS) status due
to wrong EXIT_CODE.
After  kubernetes client is updated to v4.0.0 and
no longer contains ConfiugrationObject so we need create
instance of Configuration class.
Also don't use local to create variable as local
can only be used in a function.
Use the heat-container-agent from a system container.
It means that the docker daemon can be started later.
Pass as a software deployment with the heat-agent the following
** pin prometheus to v1.8.2 since its config is not 2.0.0
Add heat-container-agent container image.
Implements: blueprint heat-agent
* It removes magnum tempest plugin reference in favour of using
* We removed tempest tests resides under functional.api.v1.test-*
files as they are tempest tests and keeping the rest as they are
used by functional tests.
Following up of https://review.openstack.org/#/c/487357
Implements: blueprint run-kube-as-container
* 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
* 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.
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. 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
Co-Authored-By: Mohammed Naser <firstname.lastname@example.org>
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
If the devstack vm supports nested virtualization we should
This can done using by setting: DEVSTACK_GATE_LIBVIRT_TYPE=kvm.
This will increase the performance in gate jobs.
Post  we cannot use auth_uri/auth_url containing :5000, :35357.
Update keystone auth_uri and auth_url in magnum.conf to connect
with keystone using /identity/v3 and /identity_admin/v3.
devstack: Allow access to ports 80 and 443
So far, we were allowing access to port 5000 for keystone.
When devstack siwtched to uwsgi we couldn't access keystone
Co-Authored-By: Spyros Trigazis <email@example.com>
New release of Fedora Atomic .
The new release of Fedora Ironic includes the same
Plus several fixes and version bumps.
Add :Z when mounting certs in the swarm containers to set
selinux labels properly.
For multinode jobs a key with the default name id_rsa already
exists. Add a key for magnum named id_rsa_magnum.
Co-Authored-By: yatinkarel <firstname.lastname@example.org>
Recent change in Infra  makes use of local.conf instead of
localrc. Use DEVSTACK_LOCAL_CONFIG to pass the MAGNUM_IMAGE_URL.
After changes in the heat-agents  the auth calls of the nodes
to heat were failing. The mesos image that was used was missing
Update to ubuntu-mesos daily builds.
Get the pod logs for controller-manager and scheduler.
The current copy logs from journalctl because controller-manager
and scheduler used to be managed by systemd.
Atomic image contains:
The ironic image contains exactly the same packages.
* For this upgrade the upstream image is used, which is
uploaded here .
* Minor changes for flannel and docker-storage-setup
* The image will be built in the CI and uploaded to
tarballs.openstack.org as soon as possible.
* Ironic image .
* docker-storage-setup config changes were needed because in
the previous images it was disabled and it was started by us.
* We can have selinux enables in containers since the images
have kernel 4.9.x.
One limitation that we might be facing when try to run large
containers like hyperkube is is the size of the master node
flavor. Increase the master flavor memory to 1024 mb.
Currently magnum CI tests(magnum/tests/contrib/post_test_hook.sh) uses
python clients(nova,neutron, glance) for openstack operations.
We should start using openstack client instead.
The new image includes:
If the services are disabled in the devstack/settings file, it disables
them for everyone who uses the magnum devstack plugin. Some people (like
shade) use both magnum and swift to test things. Putting this in the
gate hook means it's used in all of magnum's jobs, but not in other
Swift Ceilometer and horizon are not used. Disabling them
it will give us space.
Cleanup disabling of octavia and neutron/lbaas.
For ironic driver functional testing on gate only a flavor named
"baremetal" is required which is already created by ironic devstack. So,
creation of flavors "m1.small" and "s1.small" should be skipped for
ironic driver functional testing.
* Update functional_creds.conf.sample
* and functional_creds.conf in post_gate_hook
* Update python_client_base to use keystone v3 credentials
* Get magnum_url from magnum.conf
This patch fixes the issue when functional tests are run
against a deployment that has https based endpoints.
The insecure option is not being passed when initiating
magnumclient or keystoneclient as a result we get SSL
Update the gate and docs to use "ubuntu-mesos-latest" instead of
"ubuntu-14.04.3-mesos-0.25.0.qcow2". The intent is to make the
image upgrade easier (by using a static image name). In fedorapeople,
a soft link was created from "ubuntu-mesos-latest.qcow2" to
The order of enabling devstack plugin is important if project
has dependency of other projects.
Magnum has some dependency of projects, so this patch fixes
the order of enabling plugin.
Now that heat is available as a devstack plugin, we should
use it. In-tree devstack code for heat is planned to be
And also, this patch remove `update_heat_policy` function
in devstack plugin. Because fetching global stack list is
already option to use in Magnum.
Co-Authored-By: OTSUKA, Yuanying <email@example.com>
Proper functionality with lbaas and ironic couldn't
be verified and the infra job was failing.
Disable lbaas on the ironic driver for now.
Partially-Implements: blueprint magnum-lbaasv2-support
LBaaS v1 api is completely removed by neutron, so it
cannot be used now. Added Support of LBaaS v2 API.
Now all COE's uses LBaaS v2.
Co-Authored-By: yatin karel <firstname.lastname@example.org>
Partially-Implements: blueprint magnum-lbaasv2-support
This is patch 3 of 3 to change the internal usage of the terms
Bay and BayModel. This patch updates Bay to Cluster in DB and
Object as well as all the usages. No functionality should be
changed by this patch, just naming and db updates.
Implements: blueprint rename-bay-to-cluster
The test needs a valid CSR which was created in the devstack post_test_hook
in a static way (always the same CSR).
This commit simplifies the process and just adds the CSR to the test itself
so that the CSR string can be used to check the CSR. That way there is no need
to provide a file with the CSR content and point the tempest configuration
via the "csr_location" parameter to that file.
So the "csr_location" parameter is now deprecated for removal.
Also remove the unused "invalid.csr" which was also created in the