settingsLogin | Registersettings

[Openstack] extend attached volumes

0 votes

Colleagues,

can't find ways to resize attached volume. I'm on Pike.

As far as I understand, it required to be supported in Nova, because
Cinder need to check with Nova whether it's possible to extend this volume.

Well,
- Nova's API microversion is 2.51, which seems to be enough to support
"volume-extended" API call
- Properties of image are hwdiskbus='scsi' and
hwscsimodel='virtio-scsi', type bare/raw, located in Cinder
- hypervisor is KVM
- volume is bootable, mounted as root, created as snapshot from Cinder
volume
- Cinder's backend is CEPH/Bluestore

and both "cinder extend" and "openstack volume set --size" returns
"Volume status must be '{'status': 'available'}' to extend, currently
in-use".

I did not find any configuration options neither in nova nor in cinder
config files, which can help with this functionality.

What I'm doing wrong?

Thank you.

--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
asked Sep 26, 2017 in openstack by Volodymyr_Litovka (1,100 points)   1 6 8

6 Responses

0 votes

Detach the volume, then resize it, then re-attach.

Best,
-jay

On 09/26/2017 09:22 AM, Volodymyr Litovka wrote:
Colleagues,

can't find ways to resize attached volume. I'm on Pike.

As far as I understand, it required to be supported in Nova, because
Cinder need to check with Nova whether it's possible to extend this volume.

Well,
- Nova's API microversion is 2.51, which seems to be enough to support
"volume-extended" API call
- Properties of image are hwdiskbus='scsi' and
hwscsimodel='virtio-scsi', type bare/raw, located in Cinder
- hypervisor is KVM
- volume is bootable, mounted as root, created as snapshot from Cinder
volume
- Cinder's backend is CEPH/Bluestore

and both "cinder extend" and "openstack volume set --size" returns
"Volume status must be '{'status': 'available'}' to extend, currently
in-use".

I did not find any configuration options neither in nova nor in cinder
config files, which can help with this functionality.

What I'm doing wrong?

Thank you.

--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
responded Sep 26, 2017 by Jay_Pipes (59,760 points)   3 10 13
0 votes

Hi Jay,

I know about this way :-) but Pike introduced ability to resize attached
volumes:

"It is now possible to signal and perform an online volume size change
as of the 2.51 microversion using the|volume-extended|external event.
Nova will perform the volume extension so the host can detect its new
size. It will also resize the device in QEMU so instance can detect the
new disk size without rebooting." --
https://docs.openstack.org/releasenotes/nova/pike.html

On 9/26/17 5:04 PM, Jay Pipes wrote:
Detach the volume, then resize it, then re-attach.

Best,
-jay

On 09/26/2017 09:22 AM, Volodymyr Litovka wrote:

Colleagues,

can't find ways to resize attached volume. I'm on Pike.

As far as I understand, it required to be supported in Nova, because
Cinder need to check with Nova whether it's possible to extend this
volume.

Well,
- Nova's API microversion is 2.51, which seems to be enough to
support "volume-extended" API call
- Properties of image are hwdiskbus='scsi' and
hwscsimodel='virtio-scsi', type bare/raw, located in Cinder
- hypervisor is KVM
- volume is bootable, mounted as root, created as snapshot from
Cinder volume
- Cinder's backend is CEPH/Bluestore

and both "cinder extend" and "openstack volume set --size" returns
"Volume status must be '{'status': 'available'}' to extend, currently
in-use".

I did not find any configuration options neither in nova nor in
cinder config files, which can help with this functionality.

What I'm doing wrong?

Thank you.

--
Volodymyr Litovka
   "Vision without Execution is Hallucination." -- Thomas Edison


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
responded Sep 26, 2017 by Volodymyr_Litovka (1,100 points)   1 6 8
0 votes

I think this feature is actually implemented in nova. So you have to use
the nova volume-extend option to do what you want. This is just my
interpretation of the release notes though. I haven't tried it.

On Tue, Sep 26, 2017 at 10:20 AM, Volodymyr Litovka doka.ua@gmx.com wrote:

Hi Jay,

I know about this way :-) but Pike introduced ability to resize attached
volumes:

"It is now possible to signal and perform an online volume size change as
of the 2.51 microversion using the volume-extendedexternal event. Nova
will perform the volume extension so the host can detect its new size. It
will also resize the device in QEMU so instance can detect the new disk
size without rebooting." -- https://docs.openstack.org/
releasenotes/nova/pike.html

On 9/26/17 5:04 PM, Jay Pipes wrote:

Detach the volume, then resize it, then re-attach.

Best,
-jay

On 09/26/2017 09:22 AM, Volodymyr Litovka wrote:

Colleagues,

can't find ways to resize attached volume. I'm on Pike.

As far as I understand, it required to be supported in Nova, because
Cinder need to check with Nova whether it's possible to extend this volume.

Well,
- Nova's API microversion is 2.51, which seems to be enough to support
"volume-extended" API call
- Properties of image are hwdiskbus='scsi' and
hwscsimodel='virtio-scsi', type bare/raw, located in Cinder
- hypervisor is KVM
- volume is bootable, mounted as root, created as snapshot from Cinder
volume
- Cinder's backend is CEPH/Bluestore

and both "cinder extend" and "openstack volume set --size" returns "Volume
status must be '{'status': 'available'}' to extend, currently in-use".

I did not find any configuration options neither in nova nor in cinder
config files, which can help with this functionality.

What I'm doing wrong?

Thank you.

--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
openstack


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
openstack

--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
openstack


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
responded Sep 26, 2017 by John_Petrini (1,880 points)   4 5
0 votes

On 09/26/2017 10:20 AM, Volodymyr Litovka wrote:
Hi Jay,

I know about this way :-) but Pike introduced ability to resize attached
volumes:

"It is now possible to signal and perform an online volume size change
as of the 2.51 microversion using the|volume-extended|external event.
Nova will perform the volume extension so the host can detect its new
size. It will also resize the device in QEMU so instance can detect the
new disk size without rebooting." --
https://docs.openstack.org/releasenotes/nova/pike.html

Apologies, Volodymyr, I wasn't aware of that ability!

responded Sep 26, 2017 by Jay_Pipes (59,760 points)   3 10 13
0 votes

As far as I understood, the chain is the same - admin extend volume by
using Cinder, but unlike earlier implementation, if volume is in-use,
Cinder will ask Nova whether Nova support extending attached volumes (by
checking Nova's API microversion) and if yes, will resize volume
informing Nova using "volume-extended" call. On Nova's side, it will
inform QEMU about this change... then either user can manually resize or
it will happen on next reboot.

I can be wrong, of course, but there is no neither "nova volume-extend"
nor word "extend" in "nova --help" :-)

On 9/26/17 5:35 PM, John Petrini wrote:
I think this feature is actually implemented in nova. So you have to
use the nova volume-extend option to do what you want. This is just my
interpretation of the release notes though. I haven't tried it.

On Tue, Sep 26, 2017 at 10:20 AM, Volodymyr Litovka <doka.ua@gmx.com
doka.ua@gmx.com> wrote:

Hi Jay,

I know about this way :-) but Pike introduced ability to resize
attached volumes:

"It is now possible to signal and perform an online volume size
change as of the 2.51 microversion using
the|volume-extended|external event. Nova will perform the volume
extension so the host can detect its new size. It will also resize
the device in QEMU so instance can detect the new disk size
without rebooting." --
https://docs.openstack.org/releasenotes/nova/pike.html
<https://docs.openstack.org/releasenotes/nova/pike.html>

On 9/26/17 5:04 PM, Jay Pipes wrote:
Detach the volume, then resize it, then re-attach.

Best,
-jay

On 09/26/2017 09:22 AM, Volodymyr Litovka wrote:
Colleagues,

can't find ways to resize attached volume. I'm on Pike.

As far as I understand, it required to be supported in Nova,
because Cinder need to check with Nova whether it's possible to
extend this volume.

Well,
- Nova's API microversion is 2.51, which seems to be enough to
support "volume-extended" API call
- Properties of image are *hw_disk_bus='scsi'* and
*hw_scsi_model='virtio-scsi'*, type bare/raw, located in Cinder
- hypervisor is KVM
- volume is bootable, mounted as root, created as snapshot from
Cinder volume
- Cinder's backend is CEPH/Bluestore

and both "cinder extend" and "openstack volume set --size"
returns "Volume status must be '{'status': 'available'}' to
extend, currently in-use".

I did not find any configuration options neither in nova nor in
cinder config files, which can help with this functionality.

What I'm doing wrong?

Thank you.

-- 
Volodymyr Litovka
   "Vision without Execution is Hallucination." -- Thomas Edison



_______________________________________________
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Post to     : openstack@lists.openstack.org
<mailto:openstack@lists.openstack.org>
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Post to     : openstack@lists.openstack.org
<mailto:openstack@lists.openstack.org>
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
-- 
Volodymyr Litovka
   "Vision without Execution is Hallucination." -- Thomas Edison


_______________________________________________
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Post to     : openstack@lists.openstack.org
<mailto:openstack@lists.openstack.org>
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
responded Sep 26, 2017 by Volodymyr_Litovka (1,100 points)   1 6 8
0 votes

On Sep 26, 2017 11:03 AM, "Jay Pipes" jaypipes@gmail.com wrote:

On 09/26/2017 10:20 AM, Volodymyr Litovka wrote:

Hi Jay,

I know about this way :-) but Pike introduced ability to resize attached
volumes:

"It is now possible to signal and perform an online volume size change as
of the 2.51 microversion using the|volume-extended|external event. Nova
will perform the volume extension so the host can detect its new size. It
will also resize the device in QEMU so instance can detect the new disk
size without rebooting." -- https://docs.openstack.org/rel
easenotes/nova/pike.html

I think using Ceph is your issue. From those release notes:

"Currently only the libvirt compute driver with iSCSI and FC volumes
supports the online volume size change."

-Erik

Apologies, Volodymyr, I wasn't aware of that ability!

Best,
-jay


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
responded Sep 26, 2017 by Erik_McCormick (3,880 points)   2 3
...