This changes:
1. Support 'Conditions' for AWSTemplateFormatVersion: 2010-09-09
2. Support 'conditions' for heat_template_version: 2016-10-14
3. There is no need to add a new HeatTemplateFormatVersion template,
because we decide to support conditions in AWSTemplateFormatVersion
and heat_template_version: 2016-10-14, so remove the
HeatTemplateFormatVersion.2016-10-14
4. Move the definition of function 'equals' to hot/functions.py
5. Mark 'equals' as condition function which supported in conditions.
Change-Id: I2e7bdfa1c2052e75f35f2bd0003cdc170188d8b8
Blueprint: support-conditions-function
Now that there is a passing gate job, we can claim support for
Python 3.5 in the classifier. This patch also adds the convenience
py35 venv.
Change-Id: Ie64b63a462ae9b2c25ce9ab9e05259350353522e
This adds constraints to be used with properties of neutron
resources for internal/external dns resolution.
Change-Id: I728eec876b9f5e12b92ee8283c0d1a7610d7ed76
Blueprint: neutron-dns-resolution
Release version names are easier for template authors to remember than
seemingly arbitrary dates. It should also make it clearer to new Heat
users that heat_template_version is not like a BIND zone file version
(which would be incremented with each version of the template).
Change-Id: Iae9b6a676702b2a115b18fdfb1ab2afbe5faacde
blueprint support-alias-for-heat-template-version-names
This constraint will validate that a parameter value is a valid resource
type within the context of the template (that is, taking into account
the environment file(s) passed in as well).
Change-Id: I82b18d52982c2731370df9ea4ea0e398bf7702f2
Closes-Bug: #1545857
Remove backwards compatibility for heat.openstack.common.notifier.
We remove that feature since Juno and should be acceptable to drop
support in Newton.
Closes-Bug: 1592490
Change-Id: I6314b3c264cb2609c01063509a4700ca3108a34a
Provides condition function 'equals' for hot template,
'Fn::Equals' for HeatTemplate, which versions
are 2016-10-14.
Change-Id: Ib0ffa76e6c562dfbddca5f9dce807f2c6ea3eb82
Blueprint: support-conditions-function
Two years ago the translation files have been split into several
files, separating the log messages of different log levels from each
other, like X.pot, X-log-warning.pot, X-log-info.pot, and so on.
However, the setup.py command `compile_catalogs`, that comes from the
babel package and compiles the corresponding .po files into .mo
files, only supported one file per python package. This means that
during packaging `compile_catalogs` never compiled the X-log-*.po
files, so the corresponding translations were always missing.
Since babel 2.3 the domain can be set to a space separated list of
domains. This change adds the the additional log level files to the
domain list.
The obsolete check that .po and .pot files are valid is removed from
tox.ini.
Change-Id: I4d05c98b8ddd1a8416d7e0bc0298e86a0adc77d8
Closes-Bug: #1536226
1. Add a HOT template version 'heat_template_version.2016-10-14'
2. Add Newton version '7.0.0' in doc
Change-Id: I8194adbe9a27f982a6b123dda78849d6e5b33eeb
The default values needed for heat's implementation of cors
middleware have been moved from paste.ini into the configuration
hooks provided by oslo.config. Furthermore, these values have been
added to the default configuration parsing. This ensures
that if a value remains unset in heat.conf, it will be set
to use sane defaults, and that an operator modifying the
configuration file will be presented with a default set of
necessary sane headers.
Change-Id: Ie3791007b33788829417ce508a3c719ae626bbce
Closes-Bug: 1551836
There are follow important changes in patch:
- New constraint was added. This constraint emulate delay during
resolving custom constraint for property.
- New property was added for TestResource. This property uses new
constraint.
- Added Rally scenario create-delete, which uses template with
ResourceGroup of TestResources with custom constraint.
Depends-On: I06183138d54c1cb971a58a158a15f3f5b25cba4d
Change-Id: I53d83f59be9bd27db451f87aaae2d8446f287c17
Implement a new mechanism to allow specifying a target in the
environment to send events to. It adds zaqar as the first
implementation.
Depends-On: Ie04f9204f3ba0f75de32253f096f439c512cddee
Change-Id: Icfc3864e08693cb4b4f921641af380b39bcf0bc0
Provide some resources to support Neutron QoS capability.
This patch add OS::Neutron::QoSBandwidthLimitRule
resource plugin.
Change-Id: I0b28d990f9fd086eba089601c42f74bc2a9bf667
Blueprint: support-neutron-qos
Some time ago, we added support for a new "trustee" config section,
aimed at allowing independent configuration of the credentials used
to obtain trust-scoped tokens for deferred authentication. One of the
main reasons for this was to avoid incorrectly using the keystone
auth_token section, and as such a deprecation warning was added when
we fall back to using that config section for heat.
Unfortunately we didn't capture this new section in the sample config
because it's registered via keystoneclient.auth, so this adds support
for this section to the sample config generated via tox -e genconfig,
and adds some notes clarifying usage to the auth_plugin option.
To move to the new config syntax, but maintain the current behavior,
which is to delegate to the heat service user, you can add this section
to your heat.conf
[trustee]
auth_plugin = password
auth_url = http://<keystone hostname or IP>:35357
username = heat
password = password
user_domain_id = default
The generated config documents many more options, all of those supported
by the keystoneclient v3 Password auth plugin, but these are the minimum
to enable delegation to the heat service user in the default domain.
In new deployments this could be set to some other user (such as one created
in the heat domain), but note that the trustee should not be changed for
existing deployments where stacks exist, as the trust stored inside heat
defines a relationship between the stack owner (trustor) and a specific
trustee (which will be the heat service user if the deployment is using
the deprecated path that steals credentials from keystone auth_token).
Change-Id: I30aeb765a2246ce54b10972ae7187655d85cde1f
Partial-Bug: #1300246
Per [1] we now want to use the git repository for knowing the version
instead of just trying to modify the setup.cfg file.
[1]
http://lists.openstack.org/pipermail/openstack-dev/2015-November/080692.html
Change-Id: Ibf6cc90c03041f19596e1d3a47a9884833bdc3ce
Depends-On: I72bd53737472950995c6f5b83e4f12be30e4e951
This adds a baymodel constraint to OS::Magnum::Bay to
verify the baymodel.
Change-Id: I2ac25c419c806c5cf1976e64c682a1add5ea0111
Implements: partial blueprint magnum-resources
Host aggregate map hosts with availability zone as a aggregate set.
We need this constraint to make sure correctness of all hosts.
blueprint support-host-aggregate
Change-Id: Ib9a265f17b30427b15b4a5a4febaa5c70e280462
Add custom constraints for LBaaS v2 resources, and update the resources
to include these constraints where needed.
blueprint: lbaasv2-suport
Change-Id: Id87fab6af9fc6009c721dbc1456908d73d234438
Adds a new map_merge function for Mitaka which can be used
to merge maps. Values in latter maps override those in earlier
ones.
Also, creates a new HOT template version for Mitaka which includes
the new map_merge function.
Implements: blueprint map-merge-function
Change-Id: I2bdfc70d04a4fa14cefcf928ea5947fbe7529cf9
The functional tests are all passing. Add the trove classifiers
to announce python 3.4 support for Heat.
blueprint heat-python34-support
Change-Id: Ie5d76662fce89ec2f4cc1213f39abca4635b3e9c
Bump preversion to mark the start of the Mitaka development branch.
The liberty release branch will be cut from the previous commit.
Change-Id: I00f86cc4a7f8948bb164e997291a8e32c4b66da6
As a follow-up to Ibfd54e7b1bae700e4fb49a32e5bf7c00d1f104d9,
moving all the scripts from bin/ to setuptools entry points.
The devstack change is here: Iffb6d09bfef593d854b38e68200ae6039c4727e7
partial blueprint upgrade-tests
Change-Id: Ic8f5b8dc85098de752bbf673c4b15c06fdc4162a
Add custom constraint for cinder backup and apply
it to related resources property.
Change-Id: I6e7f0dae98fae6f36b46ca6fcf02f77f79f942dd
Blueprint: add-cinder-backup-constraint
Add timezone and cron_expression constraints.
this is required by time_constraints in Ceilometer alarm resources.
Change-Id: I2b348d9eb0f1d1ebf1407dbaeeb975dfa86b40d5
Partial-Bug: #1447942
This the first patch of two to allow roles to be added to existing
users. This patch implements the keystone.user custom constraint,
allowing users to specify the names of existing keystone users in
their templates.
Change-Id: I9041f907a7bb227ba5c31353f431426c82c3ae47
Partial-Bug: #1477218
huangtianhua
Dmitriy Uvarenkov
gengchc2
PanFengyun
rabi
Jason Dunsmore
Jay Dobies
ricolin
Sven Anderson
Michael Krotscheck
Ethan Lynn
Sergey Kraynev
Oleksii Chuprykov
Thomas Herve
Javeme
Steven Hardy
Kanagaraj Manickam
Robert Pothier
Bryan Jones
Dan Prince
Sirushti Murugesan
Thierry Carrez
Tetiana Lashchova
Kanagaraj Manickam