Added links to missing integration information

Change-Id: Id9edfb939554e1afcd2677af4ee6ed36c9a1e02e
Closes-Bug: #1332913
Fix the section name in CONTRIBUTING.rst

The name of the section 'If you'are developer, start here'
has changed in the wiki. This commit updates it to correctly
refer to the good section.

Change-Id: Ief8c1e3dfa75baea945b8c094f17e20183e7f44b
Closes-bug: #1332915
Fixed the reference to 'Creating Unit Tests' in HACKING.rst

Change-Id: Ie9778aceabb4239058468cf64009792253995ec2
Closes-bug: #1332920
Document get_file get_param incompatibility

Adds a doc note that get_file only accepts static
arguments.

Change-Id: I3386a6f70c3ca2a8d32b7d0d56f6eb5c0bf56774
Merge "Added links to missing integration information"
Fix pagination of stack-list

This was broken by the refactor in dde5a81e8060b373982f165856071a80be1d40bb
because the arguments to the DB call are in a different order to the ones
in the API, presumably for historical reasons.

Change-Id: I7503feb62089b252766a510281e0e4513945ad63
Closes-Bug: #1332611
Merge "Document get_file get_param incompatibility"
Merge "Fixed the reference to 'Creating Unit Tests' in HACKING.rst"
Merge "Fix the section name in CONTRIBUTING.rst"
Only do property validation in validate()

This patch changes resource property validation to only validate
properties in the Properties.validate() method.

So far, validation was done for each access to a property's value
in the __getitem__ method of the Properties class. This causes a
lot of un-necessary revalidation and especially with custom
constraints for flavors, images etc. this can become very expensive.

Doing validation in the validate() method should be sufficient since
this invoked as part of the pre-processing of resource actions that
receive new or updated properties (CREATE, UPDATE).

As part of the change in properties.py the validate_data method of
Property was also renamed to get_value with an optional validate
flag, since to the most part this method is really used to get a
sanitized representation of a property's value with only basic
data type checking.

Partial-Bug: #1324102

Change-Id: Ibe0aefbe8fa554c0cf227f16f971baedaa52cd8d
Fix pass incorrect volume_size while building bdm

If specify device_name, snapshot_id, delete_on_termination=True
and not specify volume_size for bdm while create a server,
heat will pass the bdm such as {'vdd': '1234:snap:0:True'} to
novaclient, the volume_size is incorrect,
nova won't create a volume from the snapshot because the
volume_size=0. If not specify volume_size, just to pass ''.

Change-Id: Ic1407671cc7bc6695bcf8e0c9f86fbdbaf245658
Closes-Bug: #1335728
use register_cli_opts instead of register_opts

oslo.config provides api register_cli_opts
to register multiple opts at once and same
is used in this patch to replace the
register_opts

Change-Id: I80b9bf37308c9e7085947200bc7c393c15e5e29d
Closes-bug: #1336224
Merge "Fix pagination of stack-list"
Merge "Fix pass incorrect volume_size while building bdm"
Use None instead of mutables in method params defaults

Mutables in the method params defaults might cause errors and
that's why it's anti-pattern in most of the cases and should be
removed.

Change-Id: I8bc284f12ce72082a0482410ec2c20c2fc087a4b
Closes-Bug: #1327473
Don't expose password in heat-keystone-setup-domain logs

heat-keystone-setup-domain is logging
the password to the log file. This patch
removes the logging as it's security concerns

Change-Id: I0f017a9c114ac60ea9f5e0df012334ead8cb434a
Closes-bug: #1336225
UnitTests: fix mock assertions usage

Some unit tests used mock.Mock().assert_called_once() assertion.

This is wrong as the mock.Mock object has no such interface method,
so due to mock nature such wrong assertion do essentially nothing
and always pass.

Change-Id: I9ed5ba26aa099c362644a4f09d67a2f9bf36f382
Closes-Bug: #1336766
Merge "Use None instead of mutables in method params defaults"
Merge "UnitTests: fix mock assertions usage"
Merge "use register_cli_opts instead of register_opts"