Now that we can use connect_retries with keystone session[1]
for retries, we should revert this change.
This reverts commit 6fb8ac250a.
[1] https://review.opendev.org/676664
Change-Id: I70ad41b12095eede617fd8dc454b5761697ea50a
Entire api extension concept has been removed from nova. API bindings
which have been deprecated since Train release are removed with
https://review.opendev.org/#/c/686516/.
Change-Id: Ifd318a54ef01eb500cebbc11e642b3ae62e5fc79
If the parent resource of a nested stack is locked due to an IN_PROGRESS
update, cancel the nested stack update (which will result in the parent
resource being marked FAILED and releasing the lock so that the new
traversal can begin acting on it). This also cancels all descendants of
the nested stack.
This means that a concurrent update no longer gets blocked at a nested
stack boundary until the previous update has finished.
Change-Id: I5f14453ebab75d89672c6eea12de46d48a5147f3
Task: 17760
The 'local-data' in path /var/lib/os-collect-config/local-data should
be a directory, not a file. However, even if we can fix this, now
os-apply-config will merge configs based on the order [ec2, heat and
local], but actually there is no deployments collected local. Then
unfortunately, the deployments collected from Heat will be
overwriten because the merging order in os-apply-config. At this
moment, we can't change os-apply-config since it's deliberate.
So the only reasonable way we can do now is using
/var/lib/heat-cfntools/cfn-init-data and /var/lib/cloud/data/cfn-init-data.
Story: 2006566
Task: 36851
Change-Id: I3b1ed30967e9235e9e830c5e4156f739303be618
OS::Neutron::FirewallPolicy resource cannot be created without firewall_rules.
I can create firewall policy via the rest api of neutron.And in the rest api
of neutron to create firewall policy ,the firewall_rules is an optional parameter.
This should be consistent with the rest api of neutron.
So I think the firewall_rules should be an optional property
of OS::Neutron::FirewallPolicy resource.
Add releasenote about this.
Change-Id: I74cb22a7995376c2339f24fca9ca5d651d598480
Task: 36037
The wrap_db_retry decorator must be used outside the outermost DB
transaction. Using it on a subtransaction means that the main
transaction gets marked for rollback but not closed, leaving the session
in the 'inactive' state.
This change ensures that the decorator is not used when we update the
previous resource from within a subtransaction as part of creating a
replacement resource, and instead the retry happens outside the main
transaction.
Change-Id: I28bfcc43b108d4d907098b2f0cf3553aab399553
Task: 36957
It is only necessary to pass subtransactions=True to session.begin()
when the new transactions may be called from inside an existing
transaction. There is *no* need to pass it from the top level
transaction in anticipation that there may be subtransactions. The
sqlalchemy docs are not 100% clear on this so we were doing both to be
sure to be sure, but we have confirmed that the latter is not required.
Since passing subtransactions=True when it is not required may cover up
other problems, remove it except in those cases where we know the API
may be called as a subtransaction.
Change-Id: I34cbd3526aef79132f6d97569d48a347e904ab75
Task: 37000
Failures in the gate suggest that it is now somehow possible for the
Glance image created by a snapshot to appear to have been created even
while the Nova server remains in a state like 'image_uploading'. Servers
in this state cannot be rebuilt (to restore a snapshot). To ensure that
the snapshot has actually completed before the resource is marked
SNAPSHOT_COMPLETE, check the task state of the server as well as the
state of the snapshot image in Glance.
Change-Id: I2b5cddcbeab849054d84501dfcec48442f3666d3
Co-Authored-By: Rico Lin <rico.lin.guanyu@gmail.com>
Task: 36964
Remove patches up to the Newton release to speed up
initial deployment and tests, as we don't support
previous versions anymore.
Depends-On: https://review.opendev.org/686996
Change-Id: I49129d926c0ea3d613a4ab698cbeb46c06547813
This change provides the necessary modifications to enable
building of pdf documentation. The resources.py extension
required modification to:
- prevent attributes from being rendered as stray \items
outside of a list environment
- prevent update policies from being rendered as stray
\items outside of a list environment
- remove the 'Note:' admonition around the 'Not implemented'
message when it applies to a sub-property, such as a list.
The admonition was not rendered as a list item, causing the
build to fail due to an empty list.
Change-Id: Id4e533430600b5ff03fd63cdc09b9a00741b8e4e
Implements: User, group, role and project lookup across domains.
Added domain parameter to keystone lookup functions.
Heat templates now support user{domain}, group{domain},
role{domain} and project{domain} to support cross domain
lookup. Keystone constrains will also work across domain.
Release note added.
Story: 2005523
Task: 30642
Change-Id: I2b02787bd8883ced631b81174cee9134445bf170
Fedora CoreOS will replace Fedora Atomic being the next generation
container OS. So it would be nice to support Fedora CoreOS in Heat.
In Fedora CoreOS, the cloud-init will be replaced with Ignition[1],
so the changes proposed in this patch are mainly focusing on how to
support Ignition when using Heat SOFTWARE_CONFIG with Ignition.
Task: 36671
Story: 2006566
Change-Id: I11df2431634de7d8b584b1a2ac733d43959e34fc
Zuul
OpenStack Proposal Bot
Rabi Mishra
Ghanshyam Mann
Zane Bitter
Feilong Wang
ricolin
lidong
ricolin
matthew-fuller
Sampat P