Matt,
I think discussion on this goes all the way back to Tokyo. There was
work on the Cinder side to send the notification to Nova which I believe
all the pieces were in place for. The missing part (sticking point) was
doing a rescan of the SCSI bus in the node that had the extended volume
attached.
Has doing that been solved since Tokyo?
Jay
On 4/1/2017 10:34 AM, Matt Riedemann wrote:
On 3/31/2017 8:55 PM, TommyLike Hu wrote:
There was a time when this feature had been both proposed in Cinder [1]
and Nova [2], but unfortunately no one (correct me if I am wrong) is
going to handle this feature during Pike. We do think extending an
online volume is a beneficial and mostly supported by venders feature.
We really don't want this feature missed from OpenStack and would like
to continue on. So anyone could share your knowledge of how many works
are left till now and where should I start with?
Thanks
TommyLike.Hu
[1] https://review.openstack.org/#/c/272524/
[2]
https://blueprints.launchpad.net/nova/+spec/nova-support-attached-volume-extend
__________________________________________________________________________
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
The nova blueprint description does not contain much for details, but
from what is there it sounds a lot of like the existing volume swap
operation which is triggered from Cinder by a volume migration or
retype operation. How do those existing operations not already solve
this use case?
__________________________________________________________________________
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
