Add attributes schema to OS::Neutron::FloatingIP

FloatingIP now validates attributes against a schema instead of
accepting all possible inputs and filtering on the result returned by
neutron.

Change-Id: I3bf1c3728a9d6faab71c2312f331d73b1460c013
Closes-Bug: #1240893
Allow intrinsic functions to be called in any order

An optional transform function can be passed into the resolve
functions, which allows transforms to occur on the child snippets.

Change-Id: I5d9e061c6a55f3939c5e03c780eaad72a001fccc
Closes-Bug: #1256742
Replace try...except block with assertRaises

So the test logic looks tidy and clean.

Change-Id: I8415fbe1d4c0ce59c5c9f173240fcd6eb15b0c63
Merge "Allow intrinsic functions to be called in any order"
Remove oslo uuidutils.generate_uuid from heat code

`uuidutils.generate_uuid' is going to be removed from oslo, so we need
to remove the call from heat code.

Change-Id: Iba9f86d8b8ec5ebaf4e80e6b729e372816bd5723
Partial-Bug: #1253497
Imported Translations from Transifex

Change-Id: Ic850cf5bc9e4a59ec6fa1c8d1c7a2e57152b174e
Merge "Add attributes schema to OS::Neutron::FloatingIP"
Merge "Remove oslo uuidutils.generate_uuid from heat code"
Merge "Replace try...except block with assertRaises"
Merge "Imported Translations from Transifex"
Remove X-Auth-Url header from authtoken middleware

authtoken middleware's current purpose is to set X-Auth-Url header to a
value read from heat.conf.

Since this value is not really related to anything the keystone
middleware does and is instead read from a config file, it makes sense
to move it from the authtoken middleware into the context middleware

With this change, it makes it possible to authenticate against keystone
prior to reaching heat, forward the auth headers, and still have all the
necessary information on the context.

Closes-Bug: #1259364
Change-Id: Ieb251c18aa091391a28a90c495b61cf41436f8b9