Open Stack

devstack creates /etc/openstack/clouds.yaml (os-client-config
configuraiton files) which specifies to use keystone v3.
neutronclient supports os-client-config and keystoneauth which handles
the difference of keystone API.
Note that clouds.yaml is very convenient way to use OpenStack CLI [1].

As Michal commented, you can also use OS_PROJECT_DOMAIN_xx and OS_USER_DOMAIN_xx
for keystone v3 API.

[1] http://docs.openstack.org/developer/python-neutronclient/usage/cli.html#using-with-os-client-config

Akihiro

2016-01-14 18:13 GMT+09:00 Michal Rostecki <mrostecki at mirantis.com>:
> On 01/12/2016 02:10 PM, Smigiel, Dariusz wrote:
>>
>> Hello,
>> I'm trying to gather all the info necessary to migrate to keystone v3 in
>> Neutron.
>> When I've started to looking through possible problems with clients, it
>> occurred that 'neutron' and 'nova' clients do not want to operate with
>> Keystone v3.
>> For keystone client, it's explicit written, that this version is
>> deprecated and not supported, so it's not working with Keystone API v3. But
>> for nova and neutron, there is nothing.
>> I didn't see any place where I can find info, that "old" clients shouldn't
>> be used with Keystone API v3.
>>
>> Am I doing something wrong?
>>
>> http://paste.openstack.org/show/483568/
>>
>
> Hi,
>
> Looks like you're missing OS_PROJECT_DOMAIN_ID and OS_USER_DOMAIN_ID env
> variables, needed for Keystone v3.
>
> Unfortunately, I don't see them in devstack's openrc[1]. Maybe it's a good
> moment to add them here.
>
> [1] https://github.com/openstack-dev/devstack/blob/master/openrc
>
> Cheers,
> Michal
>
>
> __________________________________________________________________________
> 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