Hi Pradeep,
Below is the code which is working fine for me .
instance = compute.servers.create ({
:flavor_id => opts[:flavor],
:key_name => opts[:key],
:image_id => opts[:ami],
:security_group_ids => opts[:security_group],
:subnet_id => opts[:subnet_id],
:tags => {"Name" => opts[:name]}
})
So you should use security_group_ids in your code. Those are unique and
different for VPC and EC2 classic .
On Mon, Apr 7, 2014 at 3:05 PM, Pradeep <[email protected]> wrote:
> For now, security_group_ids is working for me nicely. Thank you Fred.
>
> -Pradeep
>
> On Monday 07 April 2014 03:01:10 PM IST, Frederick Cheung wrote:
>
>> Ah, may well change things - I've never used that before. Security groups
>> are different with a vpc so it wouldn't surprise me if there was a
>> difference
>>
>> Fred
>>
>> On 7 April 2014 at 09:53:27, Pradeep ([email protected]) wrote:
>>
>>> Hi Fred,
>>>
>>> As you said, I tried passing as an array as well. It didn't work. It
>>> took the "default" Security group only. The machine is inside VPC.
>>> Should it make any difference ? Do I need to mentioned vpc-id anywhere ?
>>>
>>> On Monday 07 April 2014 02:18:30 PM IST, Frederick Cheung wrote:
>>>
>>>> You definitely can use the group names, but it needs to be an array -
>>>> :groups => ['Monitoring'],
>>>>
>>> even if there's only the one group.
>>>
>>>>
>>>> Fred
>>>>
>>>>
>>>> On 7 April 2014 at 07:55:40, Pradeep Chhetri (
>>>> [email protected]) wrote:
>>>>
>>>>> Finally figured out that I should use :security_group_ids =>
>>>>> ["sg-xxxxxxx"].
>>>>>
>>>>> On Sunday, 6 April 2014 17:54:00 UTC+5:30, Pradeep Chhetri wrote:
>>>>>
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I am trying to create an instance in AWS in a particular security
>>>>>> group.
>>>>>>
>>>>>> server = conn.servers.create(:image_id => "#{@ami_id}",
>>>>>> :flavor_id =>
>>>>>> "#{@instancetype}",
>>>>>> :key_name =>
>>>>>> "#{@aws_ssh_key_name}",
>>>>>> :groups => "Monitoring",
>>>>>> :subnet_id =>
>>>>>> "#{@subnetid.shuffle.first}",
>>>>>> :user_data => "#{user_data}")
>>>>>>
>>>>>> where Monitoring is the name of the security group.
>>>>>>
>>>>>> But when the machine comes up. It takes the "default" security group.
>>>>>> I
>>>>>> tried replacing "Monitoring" with the security-group-id but still I
>>>>>> wasn't
>>>>>> able to get Monitoring security group in the new instance. Can someone
>>>>>> please help me out.
>>>>>>
>>>>>>
>>>>>> Thank you,
>>>>>>
>>>>>> - Pradeep
>>>>>>
>>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "ruby-fog"
>>>>> group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to [email protected].
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>>
>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "ruby-fog"
>>> group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "ruby-fog" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
Best Regards,
Suresh Prajapati
Mob No: +91-9000173245
----------------------------------------------------------------------------------------
Theory is when you know all and nothing works. Practice is when all works
and nobody knows why. In this case we have put together theory and
practice: nothing works... and nobody knows why!
--
You received this message because you are subscribed to the Google Groups
"ruby-fog" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
