openstack team mailing list archive

[Glen Campbell <glen.campbell@xxxxxxxxxxxxx>]

I believe that blueprints are strongly encouraged, but I'm not sure they're absolutely required, especially for an API extension since those are explicitly NOT in the core code.

[cid:2B0DFC26-509D-4B57-8993-14695D4F6F4E]

From: Nick Sokolov <chemikadze@xxxxxxxxx<mailto:chemikadze@xxxxxxxxx>>
Date: Tue, 23 Aug 2011 20:44:57 +0400
To: Glen Campbell <glen.campbell@xxxxxxxxxxxxx<mailto:glen.campbell@xxxxxxxxxxxxx>>
Subject: Re: [Openstack] Nova: Admin API blueprints


I am going to merge extention for network manipulating https://code.launchpad.net/~chemikadze/nova/contrib-extention-networks/+merge/72204 . Must I write blueprint?

23.08.2011 19:31 пользователь "Glen Campbell" <glen.campbell@xxxxxxxxxxxxx<mailto:glen.campbell@xxxxxxxxxxxxx>> написал:
> 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 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 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 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.
>
> [cid:8AB30009-39F1-4E53-959A-2ED84BC80963]
> This email may include confidential information. If you received it in error, please delete it.
This email may include confidential information. If you received it in error, please delete it.