Add file to the reno documentation build to show release notes for
stable/stein.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/stein.
Change-Id: Ia1a277d1dbec2878b2468337362b9292fc8b0933
Sem-Ver: feature
The Makefile's command to clean only the tinyipa ramdisk build
is `make clean_build`, adjust the name according to the Makefile.
Change-Id: Icb9f2b7213de4be1eda71d92150f76e5efd72887
Replace `ZUUL_REFNAME` in favor of `zuul.branch` to get the correct
branch name when building images.
Change-Id: I6fe33b2f17c742d57d19985169cd9800007b5768
The "primary" host is an artifact of legacy playbooks. It does not exist
in new zuul v3 jobs, and thus the publish does not happen. We probably
need to rework the whole job again one day, but for now use hosts:all.
Change-Id: I398e3b2b36795c7773afc27ead08d70eee0069ed
We allow image_source to be a URL, let us also support URLs for checksums.
This change copies handling of multi-file checksum files from metalsmith.
Change-Id: Ie4d7e5c79b76bdd72d50eeb384cf10519278a80c
Story: #2005061
Task: #29605
As some BIOSes try to boot only from the "first" disk, Ironic
should order potential disks not only by size, but also by name.
This patch proposes to add secondary sorting by device name when
identifying the root disk.
Change-Id: I4017c839eeb9d00d2b4ad5b90e4e9b65b74296c7
Story: #2004976
Task: #29434
Tinycore is the base image for testing Ironic Python Agent.
In the effort of moving toward a full python3 friendly
environment, with this patch we start building the tinyipa
image with python3 by default.
This patch is a Follow-up to
https://review.openstack.org/#/c/635487/
Change-Id: Id446a67a31d25a21b086f85b459c0bec6b58ca7e
Deprecates ironic's CoreOS IPA image ramdisks and removes the
bulk of CoreOS based CI testing in order to save resources.
Change-Id: I26c557dcb2be29ae41576527c2649ee7ff43bc87
This patch uses ``USE_PYTHON3`` variable to build
Ironic Python Agent with python 3 inside a tinycore
image.
It modifies the content of ``buildreqs.lst`` and
``finalreqs.lst``, adding specific package files
based on the python version used to build IPA.
Since we're using python 3.6, bytecode optimized
files have .pyc extension and are located under a
__pycache__ dir [1]; as an optimization option,to
reduce the size of the final image, all bytecode
generated files will be moved to the original
source location and the source code will be
removed.
[1] https://www.python.org/dev/peps/pep-0488/
Change-Id: I3448a5f41eff6736274308f924d9ad8f059e6c44
Story: #2002598
Task: #22210
Depends-On: https://review.openstack.org/634646
The agent stop function will write a byte string 'a' to the pipe
as a signal for the run function to end process.
The run function is expecting a literal string.
In python 2.x the byte string will automatically be converted to
literal, while python 3.x won't do the conversion, causing the
process to never stop.
This patch will fix that behavior, allowing the IPA to correctly
stop using python 3.x.
Story: 2004928
Task: 29308
Change-Id: Iad16e8bed2436d961dea8ddaec1c2724225b4097
Upgrading to a more recent tinycore distribution to prepare
support to deliver a tinyipa image with ironic-python-agent
built with python 3
Most important changes in Tinycore 8.x include:
* kernel updated to 4.8.17
* glibc updated to 2.24
* support for Python 3.6
This patch also removes the need of get-pip.py script in
favor of native pip installation
Change-Id: I9f2f5d9faca7cbf736547b0d0ec39c5c2bb554bc
Story: #2002598
Task: #29131
Commit 041c1795db9249b423622b21191cb88d22594451 has an issue that
prevents building IPA when requirements are not available locally.
Change-Id: I93d5fdb599315922f35a3caaf311b14d8a74a858
Story: #2004776
Task: #28901
The new zuul jobs use just /opt/stack instead of /opt/stack/new,
breaking the constraints handling and using dependencies from source.
This changes corrects it by accepting both directories.
Change-Id: I8d6f8c99e1ab5f26e3537630d0f6086e02a2b1ec
This patch adds code that tries to read the partition table after we've
successfully written an image to make sure the image that we wrote has a
valid partition table so we can more easily guarantee that what we've
written is bootable and not just junk. Without a valid partition table
writing a config drive will fail for whole disk images.
Co-Authored-By: Dmitry Tantsur <dtantsur@redhat.com>
Change-Id: I5cfd8c433a4db3e0d2d5086250e629d16234b7a4
Story: 2001760
Task: 12159
Modify the metadata erasing call chain to retrieve a list of devices
that includes partitions in addition to disks so it can erase metadata
from all of them, otherwise incidentally recreating disk partitions
causes the Linux kernel to discover and automatically recreate some
types of storage entities (eg LVM PVs, VGs, & LVs, RAID members &
devices).
Change-Id: If8f47a083966051856439e3291a6872929b93e3b
Story: #2003673
Task: #26192
