Open Stack

Hi Sean,

I don't think they're supposed to work with that. Both of those clients
have their python API compatible with those variables you've commented. But
the CLI should be used through OpenStack client. Just for an example,
keystoneclient CLI does not support it, but OpenStack client supports
keystone v3 operations. Shouldn't we move towards deprecating the CLI of
individual clients in favor of OpenStack Client?

Henrique

Em qui, 18 de fev de 2016 às 09:05, Sean Dague <sean at dague.net> escreveu:

> On 02/12/2016 07:01 AM, Sean Dague wrote:
> > Ok... this is going to be one of those threads, but I wanted to try to
> > get resolution here.
> >
> > OpenStack is wildly inconsistent in it's use of tenant vs. project. As
> > someone that wasn't here at the beginning, I'm not even sure which one
> > we are supposed to be transitioning from -> to.
> >
> > At a minimum I'd like to make all of devstack use 1 term, which is the
> > term we're trying to get to. That will help move the needle.
> >
> > However, again, I'm not sure which one that is supposed to be (comments
> > in various places show movement in both directions). So people with
> > deeper knowledge here, can you speak up as to which is the deprecated
> > term and which is the term moving forward.
> >
> >       -Sean
>
> So, as expected, there are snags in deleting TENANT variables in
> devstack, which is some of the clients.
>
> It appears that neither glance nor cinder client work with
> OS_PROJECT_NAME, even though they say they do:
>
>
> os1:~> set | grep ^OS_
> OS_AUTH_URL=http://10.42.0.50:5000/v2.0
> OS_CACERT=
> OS_IDENTITY_API_VERSION=2.0
> OS_NO_CACHE=1
> OS_PASSWORD=pass
> OS_PROJECT_NAME=demo
> OS_REGION_NAME=RegionOne
> OS_USERNAME=demo
> OS_VOLUME_API_VERSION=2
>
> os1:~> cinder list
> ERROR: You must provide a tenant_name, tenant_id, project_id or
> project_name (with project_domain_name or project_domain_id) via
> --os-tenant-name (env[OS_TENANT_NAME]),  --os-tenant-id
> (env[OS_TENANT_ID]),  --os-project-id (env[OS_PROJECT_ID])
> --os-project-name (env[OS_PROJECT_NAME]),  --os-project-domain-id
> (env[OS_PROJECT_DOMAIN_ID])  --os-project-domain-name
> (env[OS_PROJECT_DOMAIN_NAME])
>
> os1:~> glance image-list
> You must provide a project_id or project_name (with project_domain_name
> or project_domain_id) via   --os-project-id (env[OS_PROJECT_ID])
> --os-project-name (env[OS_PROJECT_NAME]),  --os-project-domain-id
> (env[OS_PROJECT_DOMAIN_ID])  --os-project-domain-name
> (env[OS_PROJECT_DOMAIN_NAME])
>
>
> The existence of versions of these tools out there which don't support
> OS_PROJECT_NAME will inhibit our attempts to move forward. Thoughts one
> ways we can address this?
>
> --
> Sean Dague
> http://dague.net
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160218/6cbed66a/attachment.html>