Comment 31 for bug 1539351

So the problem here is our API semantics are such that it assumes all the filters in by project, the list instances, etc.

A user could lock their server to stop other users in the project being able to do things like snapshot or delete it.

For billing you can group projects into nested projects, and extra data at a different level.

I think it was previous assumed you would have a project of shared VMs, and dedicated projects for each user for their own VMs, with billing aggregation to group those as a single billing entity.

Is there a use case we are missing here, or things that don't make the above practical?