OK, thanks. I guess that was a problem I was going to run into next. But
how do you generate the EC2_* shell variables that euca tools need when
using keystone? With the old nova auth this was done with 'nova-manage
project zipfile' but that does not work with keystone because there are
no longer users in the nova database. Am I missing something?
-David
On 10/13/2011 9:21 AM, Akira Yoshiyama wrote:
Hi,
We are testing nova, glance, swift and keystone of diablo release now.
You can use nova + keystone with euca-tools if you applied a patch for
two bugs in keystone/middleware/ec2_token.py that I reported.
But there is no official keystone fileter for swift3 (S3 API for
swift). So, you can't use swift + keystone with euca-tools.
Today I wrote a s3-token keystone filter and patches for keystone and
swift3. We can upload images to keystoned swift with euca-upload-bundle.
Regards,
A. Yoshiyama
NEC, Japan
akirayoshiy...@gmail.com <mailto:akirayoshiy...@gmail.com>
2011/10/13 5:45 "David Kranz" <david.kr...@qrclab.com
<mailto:david.kr...@qrclab.com>>:
Using "devstack" (thank you!) made it easy to see how the
keystone/nova integration was supposed to work and how to use nova
client to create vms, etc. In this case the old method of using
nova-manage to create users and then zipping up credentials to use
with euca tools is not possible. Is there, or is their going to
be, a way to use euca-tools with keystone in place?
_______________________________________________
Mailing list: https://launchpad.net/~openstack
<https://launchpad.net/%7Eopenstack>
Post to : openstack@lists.launchpad.net
<mailto:openstack@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~openstack
<https://launchpad.net/%7Eopenstack>
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
