Hi,
We're using modified novarc generated by nova-manage without keystone.
I'm not sure that nova-manage works well with keystone but parhaps it can't.
So we registered some users and credentials to keystone, and modified EC_*
variables in novarc to fit them.
I think that we have to make nova-ma
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 lon
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
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 the
4 matches
Mail list logo
