Fix delete event error in postgres

An error happens when heat delete events in postgres,
 It seems that JOIN/DELETE is not supported in
"sqlalchemy/orm/".

Let heat delete events in postgres in the common
way.

Closes-Bug: #1301827
Change-Id: Id320abf15c4fd9f58e411ad7de7f044a9b5d1c1e
Fix broken link to API reference

The link to the API reference was pointing to api-ref-orchestration,
which is incorrect.  This changes it to api-ref-orchestration-v1.

Closes-Bug: #1320956
Change-Id: I3eb46af60dffc47e62ffbfc9f407f7f1a86a56a1
Do no re-validate parameters for existing stacks

This patch disables validation of stack parameters values when
loading existing stacks from the database. The old behavior was
to always validate stack parameter values when initializing a
Stack object. However, this causes problems especially with
custom constraints when a constraint could be fulfilled during
stack creation but cannot be fulfilled at a later point (e.g.
when a flavor or keypair has been deleted). In such a case,
the existing stack became completely unusable.

This patch changes the behavior to not do parameter validation
for existing stacks. The assumption is that validation at stack
creation time should be sufficient to make sure the stack is valid,
so only valid stacks end up in the database. Therefore, validating
parameters again when loading stacks is not really required.

Change-Id: I0947c2dcfb9db4c81b07de582aab86f262d0c008
Closes-Bug: #1314401
removed deprecated tools

  * tools/experimental_ssh_eventlet.py
  * tools/state_transitions.py

Change-Id: I6fd8642bcabab16bb7062637d7b8b864f09f1c80
Remove mention of update_allowed_keys

Some tests still set this ignore property. Stale comments have
also been deleted.

Change-Id: I866b251e0235ca530fc066a4beeadaa743108091
All resources to use Schema update_allowed

No in-tree resources now use the property update_allowed_properties

Change-Id: I63bb9b5c3fab6f898619cddc3f64f00820fe4f12
Use str_to_num for Number parameter

Current implemenation method 'value' convert all input parameters. But
should ignore type Number, because it may round value with float type.
Also this logic is already implemented in str_to_num method. This patch
forces NumberParam class to use str_to_num in value method.

Closes-Bug: #1323649

Change-Id: I7333cb4d6641d886cffb4812ceaa58db8d86c135
Replacing variable logger on LOG

Commit https://review.openstack.org/#/c/94255/1 introduces check for
translating log messages. This check uses in pattern name 'LOG', so in
heat code also should be used this name intead of 'logger'. Also same
name is used in other projects.

Change-Id: Iba24c7eb1c13e68a91d090d7bcdbcb40d6e16071
Partial-Bug: #1321283
Sync version of sphinx from requirements

This allows the xml builder to be invoked, which is only
available in sphinx 1.2

Change-Id: Ide5cc535d9f087a7674a90a45445eb7e6009f35a
Merge "Fix delete event error in postgres"
Deprecating the old style attribute Schema

There is last patch to migrate on new attribute Schema.
The main changes are:
 - Deprecation warning was added in from_attribute function.
   If attribute have old format, it will be converted to new schema format
   and Deprecation warning will be raised.
 - Translation to new Schema was added in function schema_from_outputs.
 - All generic resources have been changed and use new Schema class now.
 - Some others tests have been fixed and use new Schema class now.

Change-Id: Icf92f2d275a86a13c656b0e74b725a442db3e532
Closes-Bug: #1307319
Use Emacs-friendly file variable to set file encoding

The file encoding line serves a dual purpose: it informs both Python
and Emacs about the file encoding.

PEP 263 explains that a file with non-ASCII characters must specify an
encoding. Without an encoding line, importing the file will raise a
SyntaxError.

The problem is now that while Python will accept both of

  -*- encoding: <some-encoding> -*-
  -*- coding: <some-encoding> -*-

and Emacs only accepts the latter since it looks for a file variable
named "coding", not "encoding". Since the Emacs specific "-*-" syntax
is already used, it seems right to use the correct variable for Emacs.

Change-Id: If5321ac2fad595c529aa3ec5f2852aa71458834b
Merge "Do no re-validate parameters for existing stacks"
Merge "Use str_to_num for Number parameter"
Merge "Remove mention of update_allowed_keys"
Merge "All resources to use Schema update_allowed"
Merge "removed deprecated tools"
Merge "Sync version of sphinx from requirements"
Merge "Replacing variable logger on LOG"
Add Boolean parameter type

Add a boolean parameter type to allow passing in boolean values via
parameters.

blueprint boolean-parameter-type

Change-Id: I693d0aa5bdc54bb57b8363633f1b41c59ccae7d3