Re: [Openstack] EC2 API (euca2ools) vs OpenStack API (novaclient)
Thanks All, @Jaypipes - I'm quickly coming to a point where I'm looking at describing tasks using both nova client and euca2ools - its certainly not a bad thing, the issue would be on simplicity (i.e. showing people how things can be done vs you could do this or you could do that - that choice bit leads to confusion). I've been using nova client to get my environment off the ground, but equally using the euca2ools to do some basic stuff like launch instance (as per the hat-tip) has been going great - it was the all-round integration that was the issue. The clear thing it seems though is that its good to know that if I am encountering issues that its not because I'm fighting a losing battle with some design choices, there's a genuine reason and there will be some fix, even if that fix gets resolved in the next few months. I'll start making notes on the bugs and raise them as appropriate. Cheers, Kev -- Kevin Jackson @itarchitectkev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] EC2 API (euca2ools) vs OpenStack API (novaclient)
On 02/06/2012 04:48 AM, Kevin Jackson wrote: Thanks All, @Jaypipes - I'm quickly coming to a point where I'm looking at describing tasks using both nova client and euca2ools - its certainly not a bad thing, the issue would be on simplicity (i.e. showing people how things can be done vs you could do this or you could do that - that choice bit leads to confusion). I understand completely. I've been using nova client to get my environment off the ground, but equally using the euca2ools to do some basic stuff like launch instance (as per the hat-tip) has been going great - it was the all-round integration that was the issue. The clear thing it seems though is that its good to know that if I am encountering issues that its not because I'm fighting a losing battle with some design choices, there's a genuine reason and there will be some fix, even if that fix gets resolved in the next few months. Yep. I'll start making notes on the bugs and raise them as appropriate. Awesome! :) Cheers, -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] EC2 API (euca2ools) vs OpenStack API (novaclient)
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 akirayoshiy...@gmail.com 2012/2/3 Kevin Jackson ke...@linuxservices.co.uk: 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 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] EC2 API (euca2ools) vs OpenStack API (novaclient)
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 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] EC2 API (euca2ools) vs OpenStack API (novaclient)
In fact, we've added some features in Essex that brings back support for the euca2ools with keystone. We are very close to having it working with swift as well, so this should be a viable deployment option by the time the essex release. Vish On Feb 3, 2012, at 7:05 AM, Jay Pipes wrote: 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 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] EC2 API (euca2ools) vs OpenStack API (novaclient)
Kevin, It is possible to get Keystone + euca2ools working with Nova, at least against Diablo, With a hat tip to Kiall for his repository: First, use https://github.com/managedit/openstack-setup/blob/master/keystone_data.sh.tmpl as a guide to configure Keystone correctly, particularly the endpoints. Second, grab, populate and source https://github.com/managedit/openstack-setup/blob/master/openrc.tmpl to setup your environment properly. Most of the euca2ools should then work. Hope this helps. Michael - Michael Fork Cloud Architect, Emerging Solutions IBM Systems Technology Group From: Kevin Jackson ke...@linuxservices.co.uk To: openstack@lists.launchpad.net Date: 02/03/2012 04:29 AM Subject:[Openstack] EC2 API (euca2ools) vs OpenStack API (novaclient) Sent by:openstack-bounces+mjfork=us.ibm@lists.launchpad.net 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 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
