Updated golang version since it's required for 1.26+
Removing builds for 1.24 and below - since those are long time
end of life
Bumping build job timeout to 3600s since it's timing out now
Change-Id: I1a40f10d438281c2cbd9a0c73c24d311f7c57b3f
* Add v1.21/v1.22
* Update v1.18/v1.19 to newest point releases
* Drop v1.16/v1.17
* Update the go version in the build Dockerfile
Change-Id: If31d8027fa3541f6124777392539200dd68ae7af
Additionally:
- update syntax for compatibility with Ansible 2.9+.
- explicitly check for "not found" to prevent rebuild due to
other types of errors, e.g. "pull rate limit".
Story: 2007264
Task: 42009
Change-Id: I68ca057e500ea293bde398288432a67eb758af25
At present, the only mechanism we have for publishing a stable heat
container agent image through manual tagging. This PS aims to automate
this through the CI by only building them if they have not already been
published. This should allow us to keep better track of which commit was
used to build a given heat container agent image.
Story: 2007264
Task: 40045
Change-Id: Ifb80575c18a34584afddc8b83084702713a802b7
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>
Eventlet used by many openstack packages depends on greenlet which does
not have a pip release supported by Python 3.9 (default Python version
on Fedora 33). Therefore, pin Fedora to version 32 until new greenlet
release is cut which includes the required fix [0].
Also update default heat_container_agent_tag to victoria-dev.
[0] https://github.com/python-greenlet/greenlet/pull/161
Change-Id: Ice75ae880925cd15c096eb6d1cdabf7f802bccde
Story: 2007264
Task: 39941
The publish step was using helm_version which has been renamed to
helm_versions to accomodate build of v2 and v3 clients.
Story: 2007514
Task: 39733
Change-Id: I69aa13b708a95530a4a86eb066885f3e56a91273
Despite the policy that Kubernetes project maintains release branches
for the most recent three minor releases (1.18, 1.17, 1.16) [0],
v1.15.12 has been released so this change partially restores the
builder for this tag as an alternative to completely reverting
26411c2970df4c939c63ff173ea66e53eba5aede.
[0] https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-versions
Story: 2005124
Task: 39686
Change-Id: Ia458c5a87ba2357f845eb095548403cc7a25b58c
Since Train release, we use upstream hyperkube image for fedora-atomic
(when use_podman=True label is set) and fedora-coreos drivers. The last
image we needed to build through the CI was for v1.15.x (because the
Kubernetes project maintains release branches for the most recent three
minor releases: 1.18, 1.17, 1.16 [0]) and v1.16.x+ has never been
supported by the fedora-atomic driver without the use_podman label.
This PS proposes removing the Ansible tasks to build these containers
through the CI. This does not affect already published older images:
https://hub.docker.com/search?q=openstackmagnum%2Fkubernetes&type=image.
[0] https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-versions
Story: 2005124
Task: 39398
Change-Id: I458767dc12b46d665777ebe019c46565f37dd959
Use buster-slim base image which is the latest stable [0].
[0] https://www.debian.org/releases/index.en.html
Story: 2007514
Task: 39525
Change-Id: I1ff8224cf064b7138f8868b2ac17710014f1e988
Remove buildimage jobs, they have been disabled in April 2019 and the
project uses upstream images now.
Remove them so that the legacy parent job can be removed, this repo
is one of the final users.
Change-Id: Ieb4fe3e6122270b4e9114012dee5af747d88d539
When we start or restart the heat-agent, we run
configure_container_agent.sh which writes a few scripts. Make sure that
the scipts do not exist before writing to avoid overwriting any values
created on runtime.
When the heat-agent starts, /etc/os-collect-config.conf includes only
the reference to the os-refresh-config command. After the agent
bootstap, this file contains the credentials to check for software
deployments in the [heat] section. Before this patch, when the agent
restarted /etc/os-collect-config.conf was cleared resulting the agent to
stop working. I have the survive restarts, skiping only
os-collect-config.conf should be enough, but it is better to not touch
files on just service restart.
Additionally, fix file permissions for /etc/os-collect-config.conf.
Change heat-container-agent tag to ussuri-dev.
Change-Id: I3efd4e55e885b95721f13279b44dc1246e2fd2e4
Signed-off-by: Spyros Trigazis <spyridon.trigazis@cern.ch>
Add Dockerfile and CI config for building cluster autoscaler
container images specifically for magnum.
The autoscaler is built with the build tag "magnum" so that
only the magnum provider is included in the binary. This cuts
the size of the image in half compared to building with all
cloud providers.
The container-build job in .zuul.yaml has to have its timeout
increased, as the build time was already close to the timeout.
Change-Id: Iecbae5866278afe1687a4533b71af60fce537a4a
Based on the policy of heat-container-agent tag, now it's updated
as train-dev and as long as we release Train, it will be updated
with train-stable.
Change-Id: Iec43df292dbd6a7e7ee33a0d4b8670b653a7ebbd
The periodic jobs for building images are all failing, add some
low-hanging fruits for fixing:
1) Remove usage of own Fedora image build tools, they were removed as
part of change Ie6a8496c202ff0bf330dd0f434cff8777e5ef112.
2) Add openstack/tripleo-image-elements and
openstack/heat-templates as required-repo for the build
jobs, they are requirements.
Still, these are still failing, let's disable the periodic jobs.
They have been broken since ages without fixing. There's no
record of a successful run under Zuul v3.
Last images at http://tarballs.openstack.org/magnum/images/ are from
2017.
Change-Id: I01122fa029b4124d912e80ea43bca07b8f2ebe5c
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Ie288c147a3cbdd19abd257bf14972c316db6d67c
Add enable_tiller label to install tiller in k8s_fedora_atomic
clusters. Defaults to false.
Add tiller_tag label to select the version of tiller. If the
tag is not set the tag that matches the helm client version in
the heat-agent will be picked. The tiller image can be stored
in a private registry and the cluster can pull it using the
container_infra_prefix label.
Install tiller securely using helper container.
TODO:
*add instructions on how RBAC is designed
https://docs.helm.sh/using_helm/#example-deploy-tiller-in-a-namespace-restricted-to-deploying-resources-in-another-namespace
* add docs on how to install addon in the cluster using this tiller
* how users can get the creds to talk to tiller
NOTE:
The main goal of this tiller is internal usage!
Users can still deploy other tillers in other namespaces.
story: 2003902
task: 26780
Change-Id: I99d3a78085ba10030200f12bbfe58a72964e2326
Signed-off-by: dioguerra <dy090.guerra@gmail.com>
