General discussion about Chef

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


Chronological Thread 
  • From: James Andrews < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Re: Re: knife-ec2 instance creation and management.
  • Date: Thu, 20 Jun 2013 23:32:27 +0900
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 < " target="_blank"> > 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}



Archive powered by MHonArc 2.6.16.

§