I haven't looked in detail at this issue yet, though I expected it would have been raised at some point.
Nova has a small module, called auth_shim, that maps back nova projects to keystone tenants. I don't have code at hand at the moment, but I recall the association between tenant and projects was 1:1 However, I think Vishy was working on a better integration between Nova and Keystone, i.e.: getting rid of the shim, aiming at doing it by Diablo release. Unfortunately I haven't looked at this work recently. Cheers, Salvatore > -----Original Message----- > From: netstack- > bounces+salvatore.orlando=eu.citrix....@lists.launchpad.net > [mailto:netstack- > bounces+salvatore.orlando=eu.citrix....@lists.launchpad.net] On Behalf Of > Sumit Naiksatam (snaiksat) > Sent: 24 August 2011 11:00 > To: netstack@lists.launchpad.net > Subject: [Netstack] Quantum tenant <--> Nova ? > > My apologies if this question has already been answered/discussed - what is > a tenant within Quantum mapped to in Nova? I noticed that Nova is still > refers to project-id and apparently uses that a tenant when interfacing with > Keystone. So does a Quantum tenant map to a Nova project? > > Thanks, > ~Sumit. > > -- > Mailing list: https://launchpad.net/~netstack > Post to : netstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~netstack > More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
