[openstack-dev] [nova] About live-resize spec

Matt Riedemann mriedemos at gmail.com
Wed Sep 20 13:10:39 UTC 2017

On 9/20/2017 12:16 AM, Chen CH Ji wrote:
> spec [1] has been there since 2014 and some patches proposed but 
> abandoned after that, can someone
> please provide some info/background about why it's postponed or due to 
> some limitations that nova hasn't been implemented yet?
> some operators suggested that this is a valuable funcationality so 
> better to have it in the near feature... thanks
> [1]:https://blueprints.launchpad.net/nova/+spec/instance-live-resize
> Best Regards!
> Kevin (Chen) Ji 纪 晨
> Engineer, zVM Development, CSTL
> Notes: Chen CH Ji/China/IBM at IBMCN Internet: jichenjc at cn.ibm.com
> Phone: +86-10-82451493
> Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian 
> District, Beijing 100193, PRC
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

We talked about this during the newton midcycle and from what I remember 
we wanted to make this depend on having the ability for users to know 
what they are capable of doing with their server instance in any given 
cloud. This has grown into the cross project capabilities API 
discussions that happen with the API work group.

At this point, I don't think we have anyone working on doing anything 
for a capabilities API in nova, nor do we have cross project agreement 
on a perfect solution that will work for all projects. At the PTG in 
Denver I think we just said we care less about having a perfect 
guideline for all projects to have a consistent API, and more about 
actually documenting the APIs that each project does have, which we do a 
pretty good job of in Nova.

So I think live resize would be fine to pick up again if you're just 
resizing CPU/RAM from the flavor and if we provide a policy rule to 
disable it in clouds that don't want to expose that feature.

Cloudbase was originally driving it for Hyper-v so you might want to 
talk with Claudiu Belu.




More information about the OpenStack-dev mailing list