This patch adds a new resource to support ``minimum_packet_rate_rule``
QoS rule in Neutron.
Related-Bug: #1922237
Story: 2009686
Task: 43997
See-Also: https://review.opendev.org/785236
Change-Id: I29e205979b40e3e0d0746e1c22fa679736c853b7
In Zed cycle, we have dropped the python 3.6/3.7[1] testing
and its support. Removing the py36 centos8 job as well as
updating the python classifier also to reflect the same.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
Change-Id: I5073a67df7a0b73dac21de4302743712f5541941
The CloudWatch API was removed during Queens cycle[1]. This change
removes the remaining parameters because these have been kept for
enough cycles to let users aware of the removal.
Change-Id: I4f57f02332cb1b61a0681794e519dd5ecfbec6c3
In some cases, some resources may require more than
one service_extension. In this case, we should allow
resources to define a list of required resources.
Change-Id: Iee0104a741cc050047824d23b8ab5ee9871c4f28
In some circumstances, it is necessary to have
arbitrary image properties on Glance images.
An example is described here:
https://storyboard.openstack.org/#!/story/2008951
This patch adds the ability to specify those
properties using the WebImage resource.
Story: 2008951
Task: 42575
Change-Id: I23475185671c52b02eb57f1aa537f206b51c384a
The shared_services_types parameter defines the shared services located
in the other region. This parameter by default include volume and
volumev2 but doesn't include volumev3 which represents Bloack Storage
API v3.
This change adds volumev3 to the default items so that all of volume
services are included by default.
Change-Id: Idde186b2d88321e7902e4330780aabc369754b14
As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to do two things:
1. Change the default value of '[oslo_policy] policy_file''
config option from 'policy.json' to 'policy.yaml' with
upgrade checks.
2. Deprecate the JSON formatted policy file on the project side
via warning in doc and releasenotes.
Also replace policy.json to policy.yaml ref from doc and code.
[1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: I1aa12bcd2638390f25d57ce8abeeec248121dc02
Allow operators to set a different (presumably looser) policy on PATCH
updates that don't make any changes to the stack, but just retrigger a
new update traversal (that will result in e.g. replacing any unhealthy
resources).
Change-Id: Id29e7ec7f6cf127177ea7ab29127b0568afaa18b
Task: 37305
Adds a attribute to the neutron ProviderNet resource to get the
segments of a provider network.
Change-Id: I27656822fd10dffbcaeda016c27a47974313a65d
Story: 2007260
Task: 38622
This commit updates default policies to account for system scope
and default roles. This is part of a broader change to provide a
consistent and secure authorization experience across OpenStack
projects.
- Introduces basic/reusable check strings in base.py
- Implements secure RBAC for build info API
- Implements secure RBAC for the action API
- Implements secure RBAC for cloud formations
- Implements secure RBAC for events
- Implements secure RBAC for the resource API
- Implements secure RBAC for the service API
- Implements secure RBAC for software configs
- Implements secure RBAC for software deployments
- Implements secure RBAC for stacks
- Adds unit tests for legacy and new secure-rbac policies.
Change-Id: Iff1e39481ea3b1f00bd89dba4a00aed30334ecec
Allow following db configs when calling wrap_db_retry:
* database.db_max_retries
* database.db_retry_interval
* database.db_inc_retry_interval
* database.db_max_retry_interval
So database cofig can now control db retries.
Please reference [1] for what each config options can do.
[1] https://opendev.org/openstack/oslo.db/src/branch/master/oslo_db/options.py
Change-Id: I034625733c2d22f0f5635f58e9df3d5785e58cf5
The VitrageTemplate resource is responsible for
adding a Vitrage template. This template can be
used, for example, to execute a Mistral healing
workflow.
Depends-On: If05f0907d8f43f64327c7774170e5b559286fc06
Depends-On: I56560d014a02b5f2ddbc08689d39147fbe4ffca4
Change-Id: Ie862e88ccb82c819b93fa2dbc5f21af61b138046
Story: 2002684
Task: 22504
The default value of domain caused the user to be unable to create
role which no domain.
The patch delete the default value of domain.
Change-Id: Ic67b22c435e29f67bafa8e14ab502ebec5b07ec5
Story: 2002671
Task: 22488
Useing get_attr, pulling index 0 in the segments list
of a network to associate the a subnet with the "first"
segment is useful since the "first" segment is created
by neutron behind the scenes on network create. A resource
reference cannot be used since the "first" segment is'nt
a heat resource.
The issue is the order of the segments list is'nt reliable.
On stack update index 0 may be a different segment, and
we end up trying to update the segment_id for a subnet.
Changeing the segment association is not allowed, so
the stack update fails.
While not perfect, sorting the list so that segments where
name is None comes first will ensure that index 0 can be used.
The template author should ensure segments defined in the heat
template all have a names set, so that only the segment creted
implicitly by neutron have 'None' name.
Closes-Bug: #1894920
Change-Id: I097aba2a97144327bec188e6c71629d0f6c95901
Don't override ResourceStatus.ACTIONS, as it's used internally by the
Resource class.
Change-Id: Icf306e981c19e3d5410905befa7907dcdba33337
Story: 2008013
Task: 40663
This resource depends on Neutron API extension
``uplink-status-propagation`` and the default is
``False``. If this property is set to ``True``,
the VF link state can follow that of PF.
See release note at
https://docs.openstack.org/releasenotes/neutron/stein.html.
Change-Id: I46749f0458fd69e3f62d03e5b4648e1704750e15