openstack team mailing list archive

[Jesse Andrews <anotherjesse@xxxxxxxxx>]

With *all* services, if you know the endpoint you can query them
directly with the auth mechanism (either token or ec2 access/secret).

OpenStack has an identity service (keystone) that returns a catalog of
services (for discovery)

You don't need to look at the catalog if you know the endpoints.

Just set the AWS endpoint how you would normally.

That said: horizon can build a eucarc that has an access/secret & ec2
endpoint for you.  It does so by doing the same thing devstack does:

  * looks in the catalog for the ec2 endpoint, and writes it the file
  * requests an access/secret for a user from keystone.

If you have all that, you can skip ahead to go :) and use your tools.

The assumption is a user of an openstack cloud would need to determine
those things, and we expose them in keystone (discovery and
tokens/access/secrets)

Jesse

On Thu, Mar 22, 2012 at 1:39 PM, Joshua Harlow <harlowja@xxxxxxxxxxxxx> wrote:
> I’m confused.
>
> So this means ec2 won’t work because it can’t have a service catalog?
>
> All of those variables should of been set:
>
> export OS_AUTH_URL=http://172.21.102.236:5000/v2.0
> export OS_PASSWORD=ac31bec851146d3c7f00
> export OS_TENANT_NAME=demo
> export OS_USERNAME=demo
>
>
> On 3/22/12 1:39 PM, "Dolph Mathews" <dolph.mathews@xxxxxxxxx> wrote:
>
> Accidentally hit send...
>
> Anyway... which does not necessarily correspond to a normal user with a
> service catalog.
>
> The error message should explain this and direct you to use an OS_USERNAME,
> OS_PASSWORD, OS_TENANT_* and OS_AUTH_URL instead (which can have a service
> catalog).
>
> -Dolph Mathews
>
> On Mar 22, 2012, at 1:42 PM, Joshua Harlow <harlowja@xxxxxxxxxxxxx> wrote:
>
> Keystone client broken?? Hi all,
>
>
> When trying to use eucarc
> (https://github.com/openstack-dev/devstack/blob/master/eucarc) or the
> devstackPY copy called euca.sh (
> https://github.com/yahoo/Openstack-DevstackPy/blob/master/euca.sh )
>
> I am getting the following:
>
> ++ keystone catalog --service ec2
> ++ awk '/ publicURL / { print $4 }'
> 'Client' object has no attribute 'service_catalog'
> + export EC2_URL=
> + EC2_URL=
> ++ keystone ec2-credentials-create
> 'Client' object has no attribute 'auth_tenant_id'
> + CREDS=
> ++ echo ''
> ++ awk '/ access / { print $4 }'
> + export EC2_ACCESS_KEY=
> + EC2_ACCESS_KEY=
> ++ echo ''
> ++ awk '/ secret / { print $4 }'
> + export EC2_SECRET_KEY=
> + EC2_SECRET_KEY=
> + NOVA_KEY_DIR=
> ++ keystone catalog --service s3
> ++ awk '/ publicURL / { print $4 }'
> 'Client' object has no attribute 'service_catalog'
>
> Has there been some changes that are causing this??
>
> Seems like maybe the keystone client is not working anymore?
>
> -Josh
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>