Ah, i see this is possible in ec2_vol, we are going to pursue that route. 
Hopefully we can get ec2 module modified to support security group 
mutations when in a VPC and will submit a pull request if we do!

Thank you,
iain


On Wednesday, June 18, 2014 5:37:08 PM UTC-7, iain wright wrote:
>
> Hi Louis et. all,
>
> This just bit us (performing modifications of security groups/volumes of 
> running instances using ec2 module in the context of a VPC)
>
> Did you ever end up modifying the module to support these mutations in a 
> VPC based enviornment? We'd love to use them if so!
>
> Thank you,
> iain
>
>
> On Wednesday, June 4, 2014 9:26:01 AM UTC-7, Louis Garman wrote:
>>
>> I'll create a pull request.
>>
>> As an aside, updating *any* of the ec2 module parameters will not update 
>> the instance. Which is often in practice is undesirable or impossible, 
>> because most of the parameters would require a restart (think 
>> instance_type, etc). However, 'volumes' is one such parameter that could 
>> be updatable (but isn't, I tried). I worked around that by creating a 
>> 'ec2_vol', and specifying the instance_id in there.
>>
>> On Wednesday, 4 June 2014 17:12:27 UTC+1, Louis Garman wrote:
>>>
>>> Yes, you can update an instance's list of security groups if that 
>>> instance is in a VPC:
>>>
>>>
>>> http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_SecurityGroups.html
>>>  
>>> (see "Differences Between Security Groups for EC2-Classic and EC2-VPC")
>>>
>>>
>>> On Wednesday, 4 June 2014 17:07:39 UTC+1, Brent Langston wrote:
>>>>
>>>> Yep. that must be the difference. I'm all VPC.
>>>>
>>>> --------
>>>> Brent
>>>> --------
>>>>
>>>>
>>>> On Wed, Jun 4, 2014 at 11:28 AM, Brian Coca <[email protected]> wrote:
>>>>
>>>>> ah, VPC instances have different rules, 'classic' is non VPC from what 
>>>>> I can see.
>>>>>
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "Ansible Project" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to [email protected].
>>>>> To post to this group, send email to [email protected].
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/ansible-project/CADn%2BHsxWHtgdmYzFQX7cqhNn4tCi%2BiosqmhyvaY1t%2BWhXxnWrg%40mail.gmail.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/ansible-project/CADn%2BHsxWHtgdmYzFQX7cqhNn4tCi%2BiosqmhyvaY1t%2BWhXxnWrg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/edd958a5-7504-408c-bf40-394ad8d4dd12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to