Comment 2 for bug 1080864

That's what I would expect, yes.

Am I wrong in expecting this? If so, how is it possible to indicate what member or project an image belongs to?

Is the usage case that prompted this - one of our developers brought his own VM to me to launch in our cloud, but he doesn't want other members of the project to be able to launch it. I figured that since there's a column in horizon that indicates if an image is public or not, I drew the conclusion that I would be able to make images public to specific members (or tenants?). My suspicion was further verified when I found the 'glance member-add <ID> <MEMBER>' option.

So I tried it. And it didn't do anything useful that I could see.

So, from your comment, am I to infer that <MEMBER> is actually tenant and not an individual user? I can see where it would be useful to limit an image to either a particular tenant or an individual user.

'keystone tenant-list' will provide the list of current tenants on the cloud, in the uuid format that everyone seems to be using.