openstack team mailing list archive

[Akira Yoshiyama <akirayoshiyama@xxxxxxxxx>]

Hi Kevin,

We use euca2ools for Nova and Swift with Keystone in Diablo.But
there are some problem.

- Swift S3 API lacks additional keystone middleware and API capability
  like ec2_token for Nova and Keystone.
- Nova lacks auth driver to generate credentials with Keystone.
 (nova-manage project zipfile failed.)
- ec2_token had a bug:
  https://bugs.launchpad.net/keystone/+bug/869778

So we have to make s3token middleware for Swift, keystone auth driver
for Nova and some patches to fix bugs.

I hope Essex can be used with euca2ools.

Regards,
    Akira Yoshiyama <akirayoshiyama@xxxxxxxxx>

2012/2/3 Kevin Jackson <kevin@xxxxxxxxxxxxxxxxxxx>:
> 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?
>
> 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
> --
> Kevin Jackson
> @itarchitectkev