Open Stack

On 02/03/2012 04:27 AM, Kevin Jackson wrote:
> Hi all,
> I need some guidance on how to proceed writing up OpenStack -
> tutorials on its use.
> A few months back, pre-Keystone, I could do a lot with euca2ools using
> the EC2 API.  Since Diablo has come on a bit with Keystone, euca2ools
> methods have been hit or miss.  I can do the basics, but not anything
> like using the nova client.
>
> All my notes so far are euca2ools based - but given the amount of
> issues I've come up against, am I just using the wrong tools?  Is it a
> goal of OpenStack to have an EC2 API, or should I be concentrating on
> the OpenStack API?

Personally, I would love to see tutorials that show usage of both tools 
(but of course, I know this is a big ask!) :)

EC2 API support is not going away, and therefore support for euca2ools 
isn't going away. So if there are problems using euca2ools with 
OpenStack, then bugs should be filed and bugs should be fixed.

There is a Nova EC2 API subteam (headed by Chuck Short IIRC, cc'd) that 
should help to verify, triage, fix and track bugs related to EC2, so I 
would definitely advise entering bugs for problems you encounter.

Cheers!
-jay

> http://nova.openstack.org/devref/api.html
>
> Says
>
> Nova has a system for managing multiple APIs on different subdomains.
> Currently there is support for the OpenStack API, as well as the
> Amazon EC2 API.
>
> This sounds great, but euca2ools isn't working in all scenarios
> (simple things like adding in security groups, etc).
> So... do I
>
> 1) drop euca2ools as a way of managing OpenStack
> 2) do I just direct bugs to euca2ools maintainers?
>
> or 3) have I just encountered some bugs and that people have no issues
> with the full suite of euca2ools?  (For the record I'm using Diablo,
> if you suggest I should concentrate on Essex I'm fine with that).
>
> Cheers,
>
> Kev