Instance resource should implement the SecurityGroupIds property

[Simon Pasquier]

It should be possible to create an instance associated to an existing security group.

As shown here: https://s3.amazonaws.com/cloudformation-templates-us-east-1/VPC_Instance_With_Association.template

[Zane Bitter (zaneb)]

Note that the distinction between SecurityGroups and SecurityGroupIds is that the former is for "EC2" security groups and the latter for "VPC" security groups. (I don't know the difference either.)

Both should support names/ids of existing security groups passed in to the template as parameters.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/30476

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/30476
Committed: http://github.com/openstack/heat/commit/3eafb93e6846805b541e9fd5b30bb03d024b0d89
Submitter: Jenkins
Branch: master

commit 3eafb93e6846805b541e9fd5b30bb03d024b0d89
Author: Jeff Peeler <email address hidden>
Date: Fri May 24 13:41:45 2013 -0400

    Implement SecurityGroupIds property for instances

    Currently handling SecurityGroups and SecurityGroupIds the same exact
    way, that is both are passed directly to nova. If one wishes to pass
    a security group by parameter of a group to be created in the template,
    it must be in the format of <stackname>.<security group name> since
    there's no way to determine the ID beforehand.

    Fixes bug #1163991

    Change-Id: I26bb43ee89806cefc92ba2d0319340c4cd56ed06