Re: [openstack-dev] [Nova] Splitting up V3 API admin-actions plugin

2013-12-03 Thread Day, Phil
...@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

Re: [openstack-dev] [Nova] Splitting up V3 API admin-actions plugin

2013-12-02 Thread Lingxian Kong
agree with Alex, maybe 'reset_network' or 'inject_network_info' is just used by XenServer now. and I think the same functionality can be replaced with Neutron or Nova metadata service. am I right? 2013/12/2 Alex Xu x...@linux.vnet.ibm.com On 2013年12月01日 21:39, Christopher Yeoh wrote:

Re: [openstack-dev] [Nova] Splitting up V3 API admin-actions plugin

2013-12-02 Thread Andrew Laski
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

[openstack-dev] [Nova] Splitting up V3 API admin-actions plugin

2013-12-01 Thread Christopher Yeoh
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

Re: [openstack-dev] [Nova] Splitting up V3 API admin-actions plugin

2013-12-01 Thread Alex Xu
On 2013?12?01? 21:39, 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