[chef] Re: Re: Chef managing a Eucalyptus cloud

[Seth Chisamore < >]

Eucalyptus's API is compatible with EC2's API, which means (in theory) any client tool that works with EC2 should work. Fog does already allow you to set an API endpoint on the Fog::AWS::Compute class[0].

It would really just be a matter of patching the Knife "ec2 server *" subcommands to support setting this value (via Chef::Config[:knife]).  It might be easier to  create a Knife script that leverages Fog to provision the instances and then let Knife take over for bootstrapping.  Joshua Timberman has an example of doing just this...I'll ask him (he also see this email) to update the Chef wiki page[1] that discusses "knife exec" and Knife scripts.

Seth

--
Opscode, Inc.
Seth Chisamore, Technical Evangelist
T: (404) 348-0505 E: " target="_blank">
Twitter, IRC, Github: schisamo

[0] https://github.com/geemus/fog/blob/master/lib/fog/compute/aws.rb#L22 

[1] http://wiki.opscode.com/display/chef/Knife+Exec

On Tue, Jan 25, 2011 at 10:23 AM, John E. Vincent (lusis) <lusis.org+ "> > wrote:

The underlying utility that knife uses is fog
(http://github.com/geemus/fog). There's not explicit support for
Eucalyptus as of the last time I looked. The issue would be if knife
supports upfront, different API endpoints.

On Tue, Jan 25, 2011 at 9:58 AM,  < "> > wrote:
> We would like to use knife/chef to spin up and bootstrap Eucalyptus instances
> on an Ubuntu Enterprise Cloud.  I know that knife already supports this
> functionality for EC2. Eucalyptus implements the same API as EC2 and I'm
> wondering if anyone else is currently using knife like this?
>