[openstack-dev] [Nova] Splitting up V3 API admin-actions plugin
philip.day at hp.com
Tue Dec 3 12:08:10 UTC 2013
+1 from me - would much prefer to be able to pick this on an individual basis.
Could kind of see a case for keeping reset_network and inject_network_info together - but don't have a strong feeling about it (as we don't use them)
> -----Original Message-----
> From: Andrew Laski [mailto:andrew.laski at rackspace.com]
> Sent: 02 December 2013 14:59
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Nova] Splitting up V3 API admin-actions plugin
> On 12/02/13 at 08:38am, Russell Bryant wrote:
> >On 12/01/2013 08:39 AM, Christopher Yeoh wrote:
> >> Hi,
> >> At the summit we agreed to split out lock/unlock, pause/unpause,
> >> suspend/unsuspend functionality out of the V3 version of admin
> >> actions into separate extensions to make it easier for deployers to
> >> only have loaded the functionality that they want.
> >> Remaining in admin_actions we have:
> >> migrate
> >> live_migrate
> >> reset_network
> >> inject_network_info
> >> create_backup
> >> reset_state
> >> I think it makes sense to separate out migrate and live_migrate into
> >> a migrate plugin as well.
> >> What do people think about the others? There is no real overhead of
> >> having them in separate plugins and totally remove admin_actions.
> >> Does anyone have any objections from this being done?
> >> Also in terms of grouping I don't think any of the others remaining
> >> above really belong together, but welcome any suggestions.
> >+1 to removing admin_actions and splitting everything out.
> +1 from me as well.
> >Russell Bryant
> >OpenStack-dev mailing list
> >OpenStack-dev at lists.openstack.org
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev