[chef] Re: Re: Re: knife-ec2 instance creation and management.

[James Andrews < >]

Thank you Alex, some good information there.  I am not sure how to handle the 
changes, but for the moment as long as I know what the problem is I can avoid 
it during the learning process.  and revisit it when we are ready to start 
spinning our services.

Thanks
James


On Jun 20, 2013, at 11:45 PM, Alex Koch wrote:

> Here's a blog post from Amazon describing the new VPC behavior and
> probably why you are seeing different behavior with different regions.
> I haven't dealt with it yet so, I'm not sure how to address the
> changes when using knife.
> 
> http://aws.typepad.com/aws/2013/03/amazon-ec2-update-virtual-private-clouds-for-everyone.html
> 
> "The default VPC features are available to new AWS customers and
> existing customers launching instances in a Region for the first time.
> If you’ve previously launched an EC2 instance in a Region or
> provisioned ELB, RDS, or ElastiCache in a Region, we won’t create a
> default VPC for you in that Region.
> 
> If you are an existing AWS customer and you want to start gaining
> experience with this new behavior, you have two options. You can
> create a new AWS account or you can pick a Region that you haven't
> used (as defined above). You can see the set of available platforms in
> the AWS Management Console (this information is also available through
> the EC2 APIs and from the command line). Be sure to check the
> Supported Platforms and Default VPC values for your account to see how
> your account is configured in a specific Region."
> 
> ~ Alex
> 
> On Thu, Jun 20, 2013 at 9:37 AM, James Andrews 
> <
 >
>  wrote:
>> You're probably right.  I'll have to figure out a way around that then if 
>> I want to use other regions.
>> 
>> Thanks.
>> James
>> 
>> 
>> On Jun 20, 2013, at 11:33 PM, Kevin Karwaski wrote:
>> 
>>> I'm fairly certain it's default behavior for new AWS accounts.
>>> 
>>> On Thu, Jun 20, 2013 at 10:32 AM, James Andrews 
>>> <
 >
>>>  wrote:
>>>> I don't ever remember asking for vpc enabled account, how do I turn that
>>>> off?  It made me real miserable for 3 days.
>>>> 
>>>> Thanks
>>>> James
>>>> 
>>>> On Jun 20, 2013, at 11:25 PM, Maciej Pasternacki wrote:
>>>> 
>>>> FWIW, OHAI discovery works for me on regions other than us-east-1 (I have
>>>> some instances in us-west-1 and in eu-west-1). I don't have any VPCs 
>>>> there,
>>>> though. Maybe this works the way you describe only for VPC-enabled 
>>>> accounts?
>>>> 
>>>> -- M
>>>> 
>>>> On 20 June 2013 16:03, Kevin Karwaski 
>>>> <
 >
>>>>  wrote:
>>>>> 
>>>>> Your welcome! Thanks for sharing some of your findings!
>>>>> 
>>>>> -K.
>>>>> 
>>>>> On Wed, Jun 19, 2013 at 6:36 PM, James Andrews 
>>>>> <
 >
>>>>> wrote:
>>>>>> Hi Kevin,
>>>>>> 
>>>>>> Thank you for all your help.  I did some digging and I got it to work.
>>>>>> It was related to vpc, and I'll go ahead an explain it in detail so 
>>>>>> others
>>>>>> don't have to spend 3 days banging their heads against the wall.
>>>>>> 
>>>>>> Amazon sets "default" vpcs for all regions except "N. Virginia".  I use
>>>>>> using "Oregon"  (us-west2).  I tried to delete the vpc but got some 
>>>>>> nasty
>>>>>> warning.  It seems that you are unable to delete these VPCs because if 
>>>>>> you
>>>>>> do you won't be able to create EC2 instances in those regions anymore.
>>>>>> 
>>>>>> After changing my knife.rb file to use us-east-1c and generating a new
>>>>>> pem file.  I was able to execute the knife file to remotely execute
>>>>>> chef-client.  So the moral of the story is use "us-east" region until 
>>>>>> there
>>>>>> is a work around for these other regions.
>>>>>> 
>>>>>> Again, thank you very much.
>>>>>> James
>>>>>> 
>>>>>> 
>>>>>> On Jun 20, 2013, at 7:02 AM, Kevin Karwaski wrote:
>>>>>> 
>>>>>>> Ohai should be capturing this info from the on-instance EC2 metadata
>>>>>>> store; from the output of your curl command above it looks like that
>>>>>>> info is not present on your instance. You ran that curl command from
>>>>>>> the EC2 instance, right?
>>>>>>> 
>>>>>>> Here's what ohai is grabbing:
>>>>>>> 
>>>>>>> https://github.com/opscode/ohai/blob/master/lib/ohai/mixin/ec2_metadata.rb
>>>>>>> 
>>>>>>> 
>>>>>>> This is what I see when I hit the metadata store on an EC2 instance:
>>>>>>> 
>>>>>>> # curl http://169.254.169.254/latest/meta-data/
>>>>>>> ami-id
>>>>>>> ami-launch-index
>>>>>>> ami-manifest-path
>>>>>>> ancestor-ami-ids
>>>>>>> block-device-mapping/
>>>>>>> hostname
>>>>>>> instance-action
>>>>>>> instance-id
>>>>>>> instance-type
>>>>>>> kernel-id
>>>>>>> local-hostname
>>>>>>> local-ipv4
>>>>>>> mac
>>>>>>> metrics/
>>>>>>> network/
>>>>>>> placement/
>>>>>>> profile
>>>>>>> public-hostname
>>>>>>> public-ipv4
>>>>>>> public-keys/
>>>>>>> reservation-id
>>>>>>> 
>>>>>>> # curl http://169.254.169.254/latest/meta-data/public-hostname
>>>>>>> BLAH-BLAH-BLAH.compute-1.amazonaws.com
>>>>>>> 
>>>>>>> Do you see anything cataloged in the EC2 metadata store?
>>>>>>> 
>>>>>>> 
>>>>>>> On Wed, Jun 19, 2013 at 5:52 PM, James Andrews 
>>>>>>> <
 >
>>>>>>> wrote:
>>>>>>>> I get the following after running that curl command.
>>>>>>>> 
>>>>>>>> curl http://169.254.169.254/latest/meta-data/public-hostname
>>>>>>>> <?xml version="1.0" encoding="iso-8859-1"?>
>>>>>>>> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>>>>>>>>       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
>>>>>>>> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en";>
>>>>>>>> <head>
>>>>>>>> <title>404 - Not Found</title>
>>>>>>>> </head>
>>>>>>>> <body>
>>>>>>>> <h1>404 - Not Found</h1>
>>>>>>>> </body>
>>>>>>>> </html>
>>>>>>>> 
>>>>>>>> I ran "knife ec2 server list" I get
>>>>>>>> 
>>>>>>>> Instance ID  Name        Public IP     Private IP     Flavor    Image
>>>>>>>> SSH Key   Security Groups  State
>>>>>>>> i-22371517   i-22371517  54.218.44.44  172.31.41.147  m1.small
>>>>>>>> ami-70f96e40  awsjames  default          running
>>>>>>>> 
>>>>>>>> So it sees the server sees the public IP address  I just don't
>>>>>>>> understand why it's not in the meta data.
>>>>>>>> 
>>>>>>>> James
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> --
>>>>>>> Kevin Karwaski
>>>>>>> Operations Engineer @ {Fiksu}
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Kevin Karwaski
>>>>> Operations Engineer @ {Fiksu}
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Kevin Karwaski
>>> Operations Engineer @ {Fiksu}
>>