This transition the train branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.
Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.
Change-Id: Ie46c08bcfcb5c1fb61f8e50e7e33b4cac0adffbc
This transition the train branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.
Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.
Change-Id: I6c30311adaf109b6f21858acaca5aad3b8fe8924
This transition the train branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.
Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.
Change-Id: Iea6d6e52484dd48139dfe566de7030ff0426b3b9
This transition the train branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.
Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.
Change-Id: Iee71a4c958e2628452a51700b924e5b56518f0cb
This transition the train branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.
Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.
Change-Id: I96f9486a547194219bb87b2ae123fad53eaea810
This transition the train branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.
Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.
Change-Id: Ia5f16b5a6d26ca1638c1d63c474e395b4edc1ce0
This transition the train branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.
Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.
Change-Id: I39709bb1a4579b2955e88243467a6487ffdfb451
This transition the train branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.
Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.
Change-Id: If75520ab66d65d95d925427575a2865db955ee10
This transition the train branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.
Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.
Change-Id: I95c1f916352e09d466f23eb104029bbf1f25754d
This transition the train branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.
Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.
Change-Id: I2ae62d363578a110fa6be1539b7a40c25403fece
Reviewer note:
Deprecated options have been removed from oslo.db this is why a major
version is required.
Change-Id: Iaaeeb0b029db04958eaa3c5399ae1580a8ea2914
To go along with Wallaby official release
This is also the last train tag before EM transition for neutron and
networking-ovn (no need for newer tags in other stadium projects)
Change-Id: I1f0303eceb9de95de443f999a43d048f31e5f0ce
During the recent xena ptg, the ironic community had a discussion about
the need to move the ironic-python-agent-builder project from an
independent model to the standard release model.
When we initially split the builder from ironic-python-agent, we decided
against it, but considering some problems we encountered during the
road, the ironic community seems to be in favor of the change.
The reasons for this are mainly to strictly align the image building
project to ironic-python-agent releases, and ease dealing with the
occasional upgrade of tinycore linux, the base image used to build the
"tinyipa" ironic-python-agent ramdisk.
We decided to split them at some point, and we'd like to keep them
separated, but we realized that it would make sense to keep them synced
by branch.
The ironic contributor suffered CI pain over the
past year where code handling distributions has broken several times.
Largely these breaks have had to be navigated around with specific
version pinning, and settings changes, because we were unable to fix
something a release or two back inside the tooling, in this case
ironic-python-agent-builder. In other words, if the ironic team had that
capability and those branches/tags, we would have been less in a world of
pain because we wouldn't have had to make changes on every job/branch
across every repository where we were hitting issues with ipa-b. Reduction
of pain is why this change is being proposed.
We should also notice that the Kolla team also use ipa-builder and they
faced similar issues with Kayobe.
These changes propose to cut ipa-builder for Wallaby in a retro active
manner (Wallaby is already out at this point).
These changes use the same model that the one used by
ironic-python-agent.
These changes create a new tag (2.7.0) based on the same hash that the
previous independent version (2.6.0), mostly to properly init the series
with a meaningful version number, avoid misleading with future bugfix
releases versionned with a minor bump, create the wallaby branch from the
right point, avoid errors with our tooling related to missing tags for a
series.
These changes also init ipa-builder for Xena.
http://lists.openstack.org/pipermail/openstack-discuss/2021-April/022032.html
Change-Id: Ia899b39dbc68b245e1b84518363de5420af500c0
$ git log --oneline --no-merges 21.2.0..HEAD
560414036d Update image_base_image_ref during rebuild.
7003618884 Rebase qcow2 images when unshelving an instance
a968289b1f Add config parameter 'live_migration_scheme' to live migration with tls guide
c2044d4bd0 Use absolute path during qemu img rebase
2e89699c33 Make _rebase_with_qemu_img() generic
812ce632d5 Raise InstanceMappingNotFound if StaleDataError is encountered
687250f60e libvirt: Use specific user when probing encrypted rbd disks during extend
8f65de96a0 Add missing exception
79df36fecf Prevent archiving of pci_devices records because of 'instance_uuid'
f32286c62e libvirt: Increase incremental and max sleep time during device detach
121e481a88 libvirt: 'video.vram' property must be an integer
Change-Id: I6a2c2aa05ff64d469ff44751ce3f738d8a5ade27
$ git log --oneline --no-merges 22.2.0..HEAD
210abc09b8 guestfs: With libguestfs >= v1.41.1 decode returned bytes to string
7b4f479647 Dynamically archive FK related records in archive_deleted_rows
21241b38dd Add functional test for bug 1837995
382d64ea36 Centralize sqlite FK constraint enforcement
c7d9d6d9dd Fix the vGPU dynamic options race
276b8db5af Add config parameter 'live_migration_scheme' to live migration with tls guide
5d1adb2604 libvirt: Use specific user when probing encrypted rbd disks during extend
3d84097eab api: Log os-resetState as an instance action
831abc9f83 Use absolute path during qemu img rebase
eda11a4875 libvirt: Skip encryption metadata lookups if secret already exists on host
Change-Id: I299c231697d97d073a54922269edfa5b1dc9d6b6
$ git log --oneline --no-merges 23.0.0..HEAD
e98935f705 guestfs: With libguestfs >= v1.41.1 decode returned bytes to string
4f49545afa [neutron] Get only ID and name of the SGs from Neutron
972a86d61f libvirt: Ignore device already in the process of unplug errors
f99f667a96 libvirt: Simplify device_path check in _detach_encryptor
200c743400 compute: Reject requests to commit intermediary snapshot of an inactive instance
Change-Id: I8b49c1dfd50884113cad3048f936ac86b44d1a24
This sets the end date for the Wallaby key, adds the Xena key
starting today and links to a minimal export of the corresponding
public key and its details on the keyserver network.
Change-Id: I012696f62c41915b71dfc12f3c658decc26e9644
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: Ia9e4cab5a22aa9e9d0e13c4a1f9313c3fcb1ec66
clone_repo script does not fail if the branch does not exist, but
checks out the master branch [1], so we have to make sure the required
branch exists.
This patch also adds a check that there were no more patches merged
after the given branch was tagged EOL.
[1] https://opendev.org/openstack/releases/src/branch/master/tools/clone_repo.sh#L187
Change-Id: Ia1ededfc3cebbae807719750dc5e2d5949ce9a21
In order to cut first major release we need to merge some partially
breaking changes. In order not to affect immediately everyone with that
and have freedom to test things thorougly let's do it in a special
branch.
Change-Id: I4622c743d6e95cc8fc8154b5943c49af7405bc05
