Open Stack

Glen Campbell wrote:
> As we discussed at last week's meeting, I have re-factored the generic
> Admin API blueprint into three separate blueprints.
> 
> https://blueprints.launchpad.net/nova/+spec/admin-account-actions
> <https://blueprints.launchpad.net/nova/+spec/admin-account-actions> covers
> actions that an administrator can perform on a tenant/or account, such
> as suspending the account or suspending all of the servers for an account.
> 
> https://blueprints.launchpad.net/nova/+spec/admin-server-actions
> <https://blueprints.launchpad.net/nova/+spec/admin-server-actions> covers actions
> that can be performed by an administrator on a server (suspend and
> resume at the moment).
> 
> Finally, and this is the largest
> change, https://blueprints.launchpad.net/nova/+spec/admin-service-actions <https://blueprints.launchpad.net/nova/+spec/admin-service-actions> covers
> administrative actions on services. This used to be on /hosts but,
> because of my lack of understanding, we were not actually administering
> physical hosts, but the services that run on those hosts. For example,
> we're proposing that a compute node be able to be placed in
> MAINTENANCE_MODE — in this mode, the compute node will no longer accept
> any instance create requests, but will handle any other requests. The
> use case is for when a server is failing (for example, multiple disk
> failures have been detected). The administrator can put the host in
> maintenance mode, ensuring that no new instances are put there, and can
> then force migrations to move instances off of the node. 
> 
> Any and all feedback is appreciated. 

Sounds good -- which, if any, do you want to try to sneak in Diablo ? Or
are all those Essex targets ?

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack