Code review comment for lp:~sandy-walsh/nova/admin-only-api

2010/11/24 Eric Day <email address hidden>:
> Actually, I liked the previous version, since admin will mean different things to different people. As soon as we draw an arbitrary line of what is admin and what is not, we're starting to get deployment specific.

I'm happy to change my mind if you can give me an example for
something that may or may not be considered admin. It seems pretty
clear cut to me.

> Beyond admin abilities, we may not want to expose functionality due to what is supported. For example, if one host doesn't support volumes, we want to be able to disable any volume related API methods.

I don't think this is how we want to handle that sort of thing. We
should have better mechanism for discovering whether we support volume
operations at all, and if not, don't offer it. It shouldn't require
explicit configuration.

--
Soren Hansen
Ubuntu Developer    http://www.ubuntu.com/
OpenStack Developer http://www.openstack.org/