Remove or update the corresponding CI jobs. Use the new custom Cirros
image in the HTTP job to avoid relying on CentOS.
Temporary increase complexity requirements while we have a deprecation
warning in the provisioner.
Change-Id: I5e65f9949ee3b78430309017800b88c1ba21dd02
It appears our jobs end up encountering some performance issues
on some RAX hosts where the overall runtime is already close to
the maximum for the job window.
Ultimately what happens is the performance ends up putting the boot
of the workload VM just a little bit later and we end up failing
the job as the VM is still early in booting up.
Change-Id: I309220d7f61f87b7457668fcf586d4ea152d363b
When netboot is removed from Ironic, we need a job to cover local boot
in legacy mode. The new job will do it.
Also drop "local" from the job name, it's the default.
Change-Id: I6cad4556d770a733245d12f9a211e8ff7a3d884b
Turns out we seem to be using bios boot with all of the metalsmith
jobs, but we need to further test UEFI and ensure that we cover
uefi and partition/wholedisk code in the ramdisk... and these
jobs are actually not bad for this purpose.
Since we ultimately want to replace the centos7 job, but centos8.2
has some incompatabilities with our IPA image and bootloader
installation process with partition images, we need to resolve
those issues before making this job voting OR replacing the
centos7 job.
Change-Id: Ibe6c543179c811c3ef43feca173a4e744c7f5671
Instead of wrapping the metalsmith CLI, the metalsmith_deployment role
now uses the metalsmith_instances module. There are differences between
the instances formats of the role and the module which are partially
resolved with a simple transformation module called
metalsmith_deployment_defaults.
A 'candidates' attribute is added to metalsmith_instances, but keeping
the single 'name' attribute to remain compatible with the TripleO
usage.
Unresolved differences between the 2 are described below:
metalsmith_instances doesn't have a per-instance state attribute,
instead it has one state attribute for all instances. I propose that
support for per-instance state is dropped. This was never documented
in the README.rst anyway.
extra_args only applies to a CLI. Apart from --dry-run these arguments
are either for output formatting or Ironic API authentication. I propose
that this option is dropped. A metalsmith_debug arg is added to make
the ouput more verbose.
Change-Id: Ia30620821182c58050813e807cdde50a27d03c15
Per clarkb, should any step in pre.yaml fail, zuul presently retries
the entire job up to the built in retry limit which cannot be changed
or disabled on a job basis. In the terms of setting up devstack, this
is not ideal as devstack is not perfect and can often fail for unrelated
reasons such as package mirrors being updated or even another project
or component failing to setup properly.
As such, in order to be good neighbors and minimize the amount of
time it takes to troubleshoot such issues, we need to move the
devstack setup into the main part of the CI job.
Change-Id: I08d6f3132ebc045ba7e2d1295efe39af7c57187c
The pipe | can be interpreted as a filter and cause errors.
The correct way to define when a 'succeeded' condition is met
should be by using the word 'is'.
Change-Id: Ica8091d96a8a5f1ec93ec4f6bfb7e3f24672f29a
We're close to the limit on some testing nodes, so, while building
a CentOS image:
1) Delete files as soon as we no longer need them.
2) Do not copy kernel/ramdisk unnecessary
Move the libvirt pool for testing VMs to /opt since some testing
nodes have small root partitions.
Also move irrelevant vars out of zuul definitions.
Change-Id: I2a34b19ee823109899dc21031e663a3ea848a5c5
Also limit lower-constraints to only direct dependencies, otherwise
things conflict with each other (and of little use anyway).
Change-Id: Ice8b6a72f5833d625352ffd09f64608afc4eac67
With the more recent versions of ansible, we should now use
"is" instead of the "|"
This should update it.
Change-Id: I5af1d3d7aa33fc3d0c1c32e35e3c27d8def1d9b8
This involves unpacking the downloaded qcow2 to extract kernel/ramdisk.
The job timeout is increased since we're working with a bigger image.
Change-Id: Ia4d984b2675667ef6a28e6ce9e2f8284cdd64200
This change switches the CLI to use openstacksdk for populating
authentication arguments and creating a session. As a side effect,
using clouds.yaml is now supported and used in the CI.
Change-Id: If20ddc46f10d9deb34e595310313bd87e2e7243b