Comment 2 for bug 897304

Hi! Yeah, totally agree that we should move to a more unified OS_* naming standard across the various dependent projects. There's a little tool in Glance that enables a quick fix for this:

jpipes@uberbox:~/repos/glance$ cat tools/nova_to_os_env.sh
# This file is intended to be sourced to convert old-style NOVA environment
# variables to new-style OS.
#
# The plan is to add this to novarc, but until that lands, it's useful to have
# this in Glance.
export OS_AUTH_USER=$NOVA_USERNAME
export OS_AUTH_KEY=$NOVA_API_KEY
export OS_AUTH_TENANT=$NOVA_PROJECT_ID
export OS_AUTH_URL=$NOVA_URL
export OS_AUTH_STRATEGY=$NOVA_AUTH_STRATEGY

But, long term, the solution is to have a single set of env variables obviously.

As for your questions, here is my opinion:

 * is AUTH_KEY the correct word? (should it be password?)

Meh, not sure :) KEY is more EC2-ish. PASS[WORD] is more Rackspace-ish. I could go either way... Perhaps do AUTH_PASSWORD and alias an AUTH_KEY as that to make things a bit more user-friendly for EC2 users? Or maybe that just adds confusion?

 * should AUTH_STRATEGY default to keystone

Actually, I think the strategy should be a description of the strategy, not the implementing project (that may implement multiple auth strategies!). Something like AUTH_STRATEGY=token would be more appropriate, right?

 * PROJECT_ID should be tenant (id) in both? (and should it be optional?)

Heh, good question :) I think that definitely PROJECT_ID should always equal TENANT_ID, yes. But the question of whether it should be optional goes back to the still-confusing default tenant issue in Keystone. I think I may have to defer to the Keystone devs on that particular decision. Has a default tenant now been removed from Keystone?

-jay