37
37
those images to show up in lists, potentially confusing users.
40
Configuring the Glance Client to use Keystone
41
---------------------------------------------
43
Once the Glance API and Registry servers have been configured to use Keystone, you
44
will need to configure the Glance client (``bin/glance``) to use Keystone as
47
Just as with Nova, the specifying of authentication credentials is done via
48
environment variables. The only difference being that Glance environment
49
variables start with `OS_AUTH_` while Nova's begin with `NOVA_`.
51
If you already have Nova credentials present in your environment, you can use
52
the included tool, ``tools/nova_to_os_env.sh``, to create Glance-style
53
credentials. To use this tool, verify that Nova credentials are present by
57
NOVA_USERNAME=<YOUR USERNAME>
58
NOVA_API_KEY=<YOUR API KEY>
59
NOVA_PROJECT_ID=<YOUR TENANT ID>
60
NOVA_URL=<THIS SHOULD POINT TO KEYSTONE>
61
NOVA_AUTH_STRATEGY=keystone
65
If `NOVA_AUTH_STRATEGY=keystone` is not present, add that to your ``novarc`` file
66
and re-source it. If the command produces no output at all, then you will need
67
to source your ``novarc``.
69
Also, make sure that `NOVA_URL` points to Keystone and not the Nova API
70
server. Keystone will return the address for Nova and Glance's API servers
71
via its "service catalog".
73
Once Nova credentials are present in the environment, you will need to source
74
the conervsion script::
76
$ source ./tools/nova_to_os_env.sh
78
The final step is to verify that the `OS_AUTH_` crednetials are present::
81
OS_AUTH_USER=<YOUR USERNAME>
82
OS_AUTH_KEY=<YOUR API KEY>
83
OS_AUTH_TENANT=<YOUR TENANT ID>
84
OS_AUTH_URL=<THIS SHOULD POINT TO KEYSTONE>
85
OS_AUTH_STRATEGY=keystone
40
87
Sharing Images With Others
41
88
--------------------------
added
removed
doc/source/authentication.rst
