I agree!
A positive root_gb of volume-backed instances which has different volume size
is confusing!
Last week I submit a patch to correct disk
filter(https://review.openstack.org/#/c/194059/).
But if we set instance.root_gb=0 for volume-backed instances, such problems
could be solved fundamentally.
------------------
Luo Gangyi
------------------ Original ------------------
From: "Feodor Tersin";<fter...@hotmail.com>;
Date: Fri, Jun 26, 2015 09:42 PM
To: "openstack-dev@lists.openstack.org"<openstack-dev@lists.openstack.org>;
Subject: [openstack-dev] [Nova] Let's set instance.root_gb=0 forvolume-backed
instances
Some solutions have been proposed to solve these problems [2]. One problem was
even discussed here [3]. However all these solutions are aimed at correcting
specific algorithms to allow them to take into account a type of an instance.
But this does not affect other algorithms, which also use root_gb as local
space size [4]. I.e. other similar problems are retained.
I propose to fix all of this by setting 0 for root_gb, min_size, size [5],
since 0 is a natural value of these attributes.
Any objections?
[1] https://bugs.launchpad.net/nova/+bug/1334974
https://bugs.launchpad.net/nova/+bug/1459491
https://bugs.launchpad.net/nova/+bug/1466305
https://bugs.launchpad.net/nova/+bug/1457517
[2] https://review.openstack.org/#/c/136284/
https://review.openstack.org/#/c/184982/
https://review.openstack.org/#/c/186247/
https://review.openstack.org/#/c/192971/
[3] http://lists.openstack.org/pipermail/openstack-dev/2015-March/058138.html
[4] https://github.com/openstack/nova/blob/master/nova/notifications.py#L407
https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L250
[5] https://bugs.launchpad.net/nova/+bug/1469179__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
