lp:heat/grizzly

Created by Steve Baker on 2012-12-30 and last modified on 2012-12-30
Get this branch:
bzr branch lp:heat/grizzly

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Heat Core security contacts
Project:
OpenStack Heat
Status:
Development

Import details

Import Status: Invalid

This branch is an import of the HEAD branch of the Git repository at https://github.com/openstack/heat.git.

Last successful import was on 2013-01-02.

Import started on 2013-04-26 on pear and finished on 2013-04-26 taking 40 seconds — see the log
Import started on 2013-04-26 on pear and finished on 2013-04-26 taking 25 seconds — see the log
Import started on 2013-04-26 on pear and finished on 2013-04-26 taking 40 seconds — see the log
Import started on 2013-04-26 on pear and finished on 2013-04-26 taking 30 seconds — see the log

Recent revisions

1185. By Zane Bitter on 2012-12-21

RPC API: Simplify describe_stack_resources call

Remove the part with the physical_resource_id, which can now be done
through the find_physical_resource call.

Change-Id: Idff625014121aaa6ff3697b36fe38facaf54a499
Signed-off-by: Zane Bitter <email address hidden>

1184. By Zane Bitter on 2012-12-21

Use the new find_physical_resource RPC call

Change-Id: I79890f897912dd75acb6561598bb34862f09a534
Signed-off-by: Zane Bitter <email address hidden>

1183. By Zane Bitter on 2012-12-21

RPC API: Add a separate find_physical_resource call

The logic for this is currently mixed up with describe_stack_resources.

Change-Id: I14dadfc3ae6cde337dfb1bdee011cb7b32e5e4d9
Signed-off-by: Zane Bitter <email address hidden>

1182. By Zane Bitter on 2012-12-21

CFN API: Fix DescribeStackResources with physical ID

DescribeStackResources failed when called with a physical resource ID
instead of a stack name. Also add a unit test to alert us to any future
breakage.

Change-Id: I931cd0f74fa225253b06195609ec233ef86353c3
Signed-off-by: Zane Bitter <email address hidden>

1181. By Zane Bitter on 2012-12-21

Handle duplicate physical resources IDs

Because the unit tests create multiple stacks in different tenants with the
same physical resource ID, the database lookup code must change to
accomodate this.

This enables us to add a unit test for the describe_stack_resources RPC
API call for the case where we pass a physical resource ID to lookup.

Change-Id: Id37b15bee595ba10f207235a3ff59526e4423be6
Signed-off-by: Zane Bitter <email address hidden>

1180. By Zane Bitter on 2012-12-21

RPC API: Clean up list_events results

Just return a list, rather than wrapping it in an object. The client API
processes can (and do) do whatever wrapping they need.

Change-Id: Ia77facbc7577ec96d1fa0e6e2784f4e5cff68614
Signed-off-by: Zane Bitter <email address hidden>

1179. By Zane Bitter on 2012-12-21

RPC API: Clean up list_stacks results

Just return a list, rather than wrapping it in an object. The client API
processes can (and do) do whatever wrapping they need.

Change-Id: I4a8e64e8e4a0f127e8fa5c12738353a1f3a0c22f
Signed-off-by: Zane Bitter <email address hidden>

1178. By Zane Bitter on 2012-12-21

RPC API: Clean up show_stack results

Just return a list, rather than wrapping it in an object. The client API
processes can (and do) do whatever wrapping they need.

Change-Id: Ibb9955a9c3fc25b88cf3914f2a3ea7cedaf2aa9b
Signed-off-by: Zane Bitter <email address hidden>

1177. By Jeff Peeler on 2012-12-20

Include new doc directory

Change-Id: If5041669717aaa9287bff315b9b6e4f9db7b374f
Signed-off-by: Jeff Peeler <email address hidden>

1176. By Steven Hardy on 2012-12-20

run_tests.sh fixup venv/novenv logic

The section which prompts y/n for creating a new venv can never be
reached with any combination of CLI options (since always_venv=0 and
never_venv=0 can never happen simultaneously)

This actually makes the --no-virtual-env option pointless, so we may
as well remove it and explicitly set it as the default (it was anyway
previously but by virtue of the never_venv option being undefined)

Change-Id: I3c803533fda55a6814b7536b5c1328312acd3d57
Signed-off-by: Steven Hardy <email address hidden>

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.