We already have resource `OS::Cinder::QoSSpecs` merged. This patch
update releasenotes for that resource.
implements bp update-cinder-resources
Change-Id: Ieba94cc912cb26b5e3ab08b7f2b4bf70216b8abd
In order to support automatically updating the release notes when we
create stable branches, we want the pages to be in a standard order.
This patch updates the order to be reverse chronological, so the most
recent notes appear at the top.
Change-Id: Ib364dcc8eb31275a31c83b68d7914263b183e393
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This creates new resource type whose intended use case is for admin-only
use and to manage the cinder quotas (gigabytes, volumes, snapshots).
implements bp cinder-quota-resource
Co-Authored-By: Andy Hsiang <yh418t@att.com>
Co-Authored-By: Yosef Hoffman <yh128t@att.com>
Change-Id: I49d01d229199d9c472dc59ba2bb95d455f6dfb76
This adds support for the following to the template:
heat_template_version: 2016-10-14
resources:
...
res_a:
type: OS::Nova::Server
external_id: the-new-server-id
properties:
...
Co-Authored-By: Rico Lin <rico.l@inwinstack.com>
blueprint external-resources
Change-Id: I8fda1380504d1d8b1e96649bf20b86d6309fdeca
I missed adding the reno in https://review.openstack.org/#/c/343731/
and there was a minor docs nit mentiond also.
Change-Id: Ib78ca19b96a239c0a06758c259e2e74e10ed26e5
Currently, when one of Monasca's alarm transitions to the ALARM state, the
webhook associated with the Alarm is only invoked once. This is inconvenient
when the user wants to create a stack which will automatically scale up
or scale down more than once if the alarm state continues to be in the same
state.
The new added property 'PERIOD' will now allow the user to tell Monasca to
periodically invoke the webhook until the ALARM state transitions back to an OK
state.
To conform to the existing Heat autoscaling behaviour, we manually create the
monasca notification resource in Heat with a default value of 60 only for the
webhook notification type.
Change-Id: I2466911efa8d05dfe497f521885464ab90b0ae8e
Allow global environment contain global template files.
This can lead to further access to global template files.
For example a template file `my_tmpl.yaml` under global template
directory (`/etc/heat/templates` by default) can be directly accessed in
stack with `get_file`.
Partial-Bug: #1454401
Change-Id: I0a1c9d50441f88144980214fbc8e6757193cfb41
For some deployments 53 may be to high of a value and
a lower value may be used (ie for registration into active
directory, which has lower name limits) so add the ability
to reduce the valid length of server names (but
preserve the current limits by default).
Change-Id: Icd06aba14dbf156b9164b0e25233f2df7099fc9b
In current code, the sequence is listed as below:
Liberty Series Release Notes
Current Series Release Notes
Mitaka Series Release Notes
Here the current release notes should be always at
then end and this patch takes care of it.
Change-Id: Ic4419aee3b441d4dd4125d7c971351f3396e6d23
This may be set to either 'REPLACE' (default) or 'IGNORE'.
This allows template authors to choose the desired behaviour when the
user_data property is changed.
Co-Authored-By: Steve Hardy <shardy@redhat.com>
Change-Id: I3239c7252a2c329330283b86181abd52aee9e967
Closes-Bug: #1539541
This patch adds one release notes item for new added resource
OS::Neutron::RBACPolicy during mitaka.
Change-Id: Ieb9ee24a0edb3826f993e3e2dd2b33c0a6496ed4
Add OS::Neutron::AddressScope resource.
This resource can be associated with multiple
subnet pools in a one-to-many relationship.
The subnet pools under an address scope must not
overlap.
Blueprint: add-neutron-address-scope
Depends-On: I43ab41e419148818e088e60d94cec96188100212
Change-Id: Ie97109a4a053baee4e4629f60ae5582ca286a892
This removes a legacy backwards compatibility codepath. Pre-Icehouse
stacks that have resources which inherit from StackUser may require
manual cleanup after deletion, as their stack user may not be deleted.
This fixes issues with subusers using software config. Heat should not
attempt to delete the stack user if one had not been created before.
The code that this patch removes caused an ID to always be returned.
Additionally, it set the ID in the resource metadata whether a stack
user existed or not, making it impossible to tell if one existed only
from data within the resource.
Change-Id: I50804998fdce1f7de06906ae9a2f47317721a6f6
Closes-bug: #1531606
