Project: openstack/tempest  683f8bf436dfc60d051c491eaa0f9e3745dde9a3

Add new test "RebuildInstanceWithVolume"

This test is for verifying functionality of rebuilding instance with volume.
The following is the scenario outline:
1. Boot an instance
2. Create a volume
3. Attach the volume to the instance
4. Create a file with timestamp on the volume
5. Rebuild the instance
6. Check existence of the file which was created at step #4
7. Detach the volume

Co-Authored-By: Roman Podoliaka <rpodolyaka@mirantis.com>

Depends-On: I4846418c4dbdae5b1ac1c08e8b9ac8cea5cb2990
Change-Id: I1158719cb906309a29ea83460e7e35d753ad1081

Project: openstack/governance  41f6e72f6f7de2c8f82ca23233158d9dc42df784

Remove rolling-upgrade tag from ceilometer

This tag was prematurely applied to this project, as it currently
doesn't follow point #4 in the tag process -
https://governance.openstack.org/reference/tags/assert_supports-rolling-upgrade.html

"Full stack integration testing with services arranged in a
mid-upgrade manner is performed on every proposed commit to validate
that mixed-version services work together properly. This testing must
be performed on configurations that the project considers to be its
reference implementations. The arrangement(s) tested will depend on
the project (i.e. should be representative of a
meaningful-to-operators rolling upgrade scenario) and available
testing resources. At least one representative arrangement must be
tested full-stack in the gate."

Ceilometer has a simple cold upgrade grenade job, but it doesn't
demonstrate mixed mode in the gate.

Change-Id: Ie546d032114c519653c7dd2ef738023f633d5026

Project: openstack/training-guides  f1f4df9e7d43863a5f10a73d88bc0eb868455a66

[upstream] add Upstream Training in Japan #4

Change-Id: I769c8e2cafb79c49530ae9124eb4eb989f03d9f6

Project: openstack/neutron  03c5283c69f1f5cba8a9f29e7bd7fd306ee0c123

use neutron-lib callbacks

The callback modules have been available in neutron-lib since commit [1]
and are ready for consumption.

As the callback registry is implemented with a singleton manager
instance, sync complications can arise ensuring all consumers switch to
lib's implementation at the same time. Therefore this consumption has
been broken down:
1) Shim neutron's callbacks using lib's callback system and remove
existing neutron internals related to callbacks (devref, UTs, etc.).
2) Switch all neutron's callback imports over to neutron-lib's.
3) Have all sub-projects using callbacks move their imports over to use
neutron-lib's callbacks implementation.
4) Remove the callback shims in neutron-lib once sub-projects are moved
over to lib's callbacks.
5) Follow-on patches moving our existing uses of callbacks to the new
event payload model provided by neutron-lib.callback.events

This patch implements #2 from above, moving all neutron's callback
imports to use neutron-lib's callbacks.

There are also a few places in the UT code that still patch callbacks,
we can address those in step #4 which may need [2].

NeutronLibImpact

[1] fea8bb64ba7ff52632c2bd3e3298eaedf623ee4f
[2] I9966c90e3f90552b41ed84a68b19f3e540426432

Change-Id: I8dae56f0f5c009bdf3e8ebfa1b360756216ab886

Project: openstack/nova  f8de7f11622a4740d649206094b78cd70778de50

PowerVM Driver: spawn/destroy #4: full flavor

Building on Idfefc2db18d0f473a028b7bb8b593d39067e090d, this change set
completes the initial spawn/destroy sequence by bringing in full support
for flavor extra_specs.

Subsequent changes will be done to add disk support, VIFs, config drive
and console.

Change-Id: Icbf542c4bcc123cc003635387e40221fc8ac6466
Partially-Implements: blueprint powervm-nova-compute-driver

* Update nova from branch 'master'
  - Merge "Add docs for compute capabilities as traits"
  - Add docs for compute capabilities as traits
    
    Change I15364d37fb7426f4eec00ca4eaf99bec50e964b6 added the
    ability for the compute service to report a subset of driver
    capabilities as standard COMPUTE_* traits on the compute node
    resource provider.
    
    This adds administrator documentation to the scheduler docs
    about the feature and how it could be used with flavors. There
    are also some rules and semantic behavior around how these traits
    work so that is also documented.
    
    Note that for cases #3 and #4 in the "Rules" section the
    update_available_resource periodic task in the compute service
    may add the compute-owned traits again automatically but it
    depends on the [compute]/resource_provider_association_refresh
    configuration option, which if set to 0 will disable that auto
    refresh and a restart or SIGHUP is required. To avoid confusion
    in these docs, I have opted to omit the mention of that option
    and just document the action that will work regardless of
    configuration which is to restart or SIGHUP the compute service.
    
    Change-Id: Iaeec92e0b25956b0d95754ce85c68c2d82c4a7f1

* Update manila-tempest-plugin from branch 'master'
  - Merge "Scenario test: Create/extend share and write data"
  - Scenario test: Create/extend share and write data
    
    Implements #4 from: http://specs.openstack.org/openstack/manila-specs/specs/release_independent/scenario-tests.html
    
    Change-Id: I4998bcac7a1d902c17d2add00cd42560bf6bbf75
    Depends-On: https://review.openstack.org/#/c/545695/

* Update openstack-tempest-skiplist from branch 'master'
  to 83968651b3aa882cdddaec5b215de8fbbb4fef3a
  - Adds ussuri/victoria/wallaby skips for +bug/1931516
    
    As commented in related bug (see comment #4) we are seeing this
    affect stable/ussuri victoria and wallaby so we need to skip on
    those branches too.
    
    Related-Bug: 1931516
    Change-Id: I3b012a0b73ad361a406e62555cd3bb8a56db35f2

* Update releases from branch 'master'
  to 4992eb6dd0fadf7c7ee6d9b94cd86e12f84e5a49
  - Add release note links for 2023.2 Bobcat (#4)
    
    If any of your deliverables does not have a release note link added
    already under deliverables/bobcat, then please check whether there is
    an open patch on that repository with the topic "reno-2023.2" [1] still
    waiting to be approved.
    
    [1] https://review.opendev.org/q/topic:reno-2023.2+is:open
    
    Change-Id: I5567743a2691f1de598eb592610978d8ec602448

* Update releases from branch 'master'
  to 8c911376e3972a9b3a834f7060ddb375c7955365
  - Add release note links for 2024.2 Dalmatian #4
    
    If any of your deliverables does not have a release note link added
    already under deliverables/dalmatian, then please check whether there is
    an open patch on that repository with the topic "reno-2024.2" [1] still
    waiting to be approved.
    
    [1] https://review.opendev.org/q/topic:reno-2024.2+is:open
    
    Change-Id: Ie31637fe15c64947b391bc8b5513600f00718f49

* Update releases from branch 'master'
  to 040a50005b6693803c7ddbc322d9cd4815029bbc
  - Add release note links for 2025.2 Flamingo (#4)
    
    If any of your deliverables misses a release note link added already
    under deliverables/flamingo/, then please check whether there is an
    open patch on that repository with the topic "reno-2025.2" [1], that
    is still waiting for approval.
    
    [1] https://review.opendev.org/q/topic:reno-2025.2+is:open
    
    Change-Id: I3a8b64b8b721a1f6cc7d7ece836d564525ad6e72
    Signed-off-by: Előd Illés <elod.illes@est.tech>