Updated from global requirements

Change-Id: Ie4b40c04509a4a6956760eb9ec59fd14e958b722
Template not required on stack-adopt

With this change, template is not required on stack-adopt and
also parameters from the original stack are adopted.

Change-Id: Id5a28400bb8e27a3b852f12d9af4c2dc7c144725
Closes-Bug: #1300336
(cherry picked from commit 8c54f483189fef2799357457c3b1e8bc0f9e87c5)
Clean up signalling events after stack updates

We provide an Event object to every stack update in order to signal it that
we need to cancel the update; this change ensures that we delete it when
the thread is complete. Previously we were leaking memory on every update.

Change-Id: Ie0fbe3ec3ab57a2cb9dd5e551db15285b2b423c0
Closes-Bug: #1376857
(cherry picked from commit 6f13c2d0a4ff2004654a690c1e84a0c9d40ed577)
Don't send multiple update-cancel messages to an event

Change-Id: Ib64da11ed5584c1a2eef98378d3201a6949fac7d
Closes-Bug: #1376900
(cherry picked from commit 75242b9c67aafa80b4d4a13cfae6c50ba7f85b79)
Update translations for Juno

Change-Id: I9d429c042cc254b7659dcc5a06be1a645cc8bf06
Merge "Template not required on stack-adopt" into proposed/juno
Merge "Clean up signalling events after stack updates" into proposed/juno
Merge "Don't send multiple update-cancel messages to an event" into proposed/juno
Merge "Update translations for Juno" into proposed/juno
Add missing extra "greenthread" arg to remove_event()

See: http://eventlet.net/doc/modules/greenthread.html
the callback gets passed a "gt" arg.

Change-Id: I9bd44857662e45a1da2d4287017eb966dea8276d
Closes-bug: #1379072
(cherry picked from commit c73d607246b6bec3f5c79fdcee57adf5cfa3cc19)
Update references to auth_token middleware

There's references to the auth_token middleware in keystoncelient.
The auth_token middleware has been moved to keystonemiddleware and
the version in keystoneclient shouldn't be used anymore.

If these references aren't updated, then when options are changed in
keystonemiddleware.auth_token the heat-api will fail to start because
there's duplicate options in keystoneclient.middleware.auth_token.

Change-Id: I04573aa5ff967afe3e00329f797fcc71b779e7b3
Closes-Bug: #1379082
Do not attempt a stack update when it is deleting

If a stack is in any delete state(inprogress, failed),
don't attempt to update it.

Closes-bug: #1379113
Change-Id: I1de99702a385ac8ddeffc568270d2d3b51674323
Make sure that the properties are stored on updates

Previously properties_data was only stored on creation, now
this is getting passed to the update mechanism too.
Later we can look at reworking this into a single mechanism.

Closes-bug: #1377681
Change-Id: If3d476f34b9e61a3c99f63ba33734a875353c8fc
(cherry picked from commit d32370233eaf2a5c32888f269bd1dc5e0e787467)
Don't update a LoadBalancer under autoscaling control

Unfortunately, Autoscaling currently uses the update() method of a
LoadBalancer resource to do updates, with the result that the current
member list gets persisted (good) and used to compare in the event of
future *stack* updates (bad).

With this patch, we assume that LoadBalancers under the control of
Autoscaling will never have a members list property supplied in the
template.  We then ignore any updates to Autoscaling LoadBalancers that
don't actually modify the template.

The test changes revert the changes made in order to be able to merge
d32370233eaf2a5c32888f269bd1dc5e0e787467, before which LoadBalancers were
behaving correctly.

Change-Id: I9c02ab3d3dfbee0a8a90dd0ba345a5acdaf8a610
Closes-Bug: #1379619
(cherry picked from commit 7506d2c22fcd3d6e825ee660a4b20c5947cc7e9a)