First time here? Check out the FAQ!
2019-06-30 21:09:16 -0600 | received badge | ● Teacher (source) |
2019-02-15 09:29:43 -0600 | received badge | ● Famous Question (source) |
2019-02-12 13:46:25 -0600 | received badge | ● Notable Question (source) |
2019-02-12 13:46:25 -0600 | received badge | ● Notable Question (source) |
2019-02-11 23:44:06 -0600 | received badge | ● Popular Question (source) |
2019-02-11 15:44:21 -0600 | commented question | Extending an in-use cinder volume? Progress! I was missing a version header with the API call. Adding |
2019-02-11 15:44:21 -0600 | answered a question | Network setup Hi, dough. I just spent a lot of frustration getting this exact thing to work as well, so I hope I can share what worked for me. (Also taking this opportunity for my own sake to write down what actually worked.) I am also using packstack on CentOS 7 (I didn't end up getting it to work correctly with devstack that I tried initially.) Some of my terminology might be wrong since I'm still learning myself. Also, I might be missing a step or two, since this is from my (rather fresh) memory. VirtualBox Networking Setup First of all, I configured two network interfaces in VirtualBox, both of them bridged to my home LAN, the plan being to use the first NIC ( I configured the second network interface to allow promiscious mode in VirtualBox. This is neccessary to allow VM traffic to work. This is done through the VM settings inside of the VirtualBox GUI. Management / API network setup You will need to setup a static IP address from one of your 5 addresses for use as your packstack box's IP address. This is accomplished using the standard methods on CentOS. On my machine, this is how my Neutron router / subnet setup By default on Packstack, there is already a What you need to do is to create a new subnet, specifying the default gateway and netmask, as well as giving it the range of 5 IP addresses provided to you by your school. You'll need to use the To actually achieve this state in the CLI refer to the docs, instead I'll show you how my working setup works: (more) |
2019-02-11 15:44:09 -0600 | answered a question | Extending an in-use cinder volume? After some investigation this is what I have learned:
|
2019-02-11 14:42:24 -0600 | received badge | ● Editor (source) |
2019-02-11 08:50:13 -0600 | commented question | Extending an in-use cinder volume? @eblock |
2019-02-11 06:53:19 -0600 | received badge | ● Supporter (source) |
2019-02-11 05:45:01 -0600 | commented question | instance resizing on a running vm What a co-incidence, I just posted the same question (although related just to disk space). By the time I finished writing my question your question popped up. https://ask.openstack.org/en/question/119853/extending-an-in-use-cinder-volume/ (https://ask.openstack.org/en/question...) |
2019-02-11 04:33:36 -0600 | asked a question | Extending an in-use cinder volume? Hello! I have a recently deployed CentOS 7 VM with OpenStack rocky deployed using the PackStack all-in-one deployment, in order to evaluate and learn about OpenStack. In the PackStack setup, the LVM Volume Driver is used by Cinder. The Libvirt driver is used by Nova. (The volume_type is shown as iscsi, I'm not sure why, I think this might be misleading.) Right now I'm investigating the use case of being able to extend a volume that is currently attached to a running instance, in order to provision extra storage space on the fly. As far as I can tell, work was done in 2017 to add this functionality to Pike, as per the following specs:
What I'm trying to do is to extend an online volume - i.e. grow the available disk space available to an instance without rebooting it, and without adding an additional volume. Consulting the https://docs.openstack.org/cinder/rocky/reference/support-matrix.html#operation_online_extend_support (Cinder Driver Support Matrix (Rocky)), I have also been able to confirm that this is supported by the LVM driver. According to the Nova spec:
So, as far as I can tell, the configuration I'm running (PackStack all-in-one) should support this functionality. However, I have not been able to find this functionality exposed anywhere in the OpenStack CLI or Horizon. So, I tried an API call as per the https://developer.openstack.org/api-ref/block-storage/v3/index.html?expanded=extend-a-volume-size-detail#volume-actions-volumes-action (API Documentation (Block Storage volume actions)). The API call below aims to try to extend the volume that's currently attached to the VM from 1 GB to 2 GB. As we can see, an error is thrown by Cinder, indicating that an in-use volume cannot be extended. What am I missing? Is there something about OpenStack as deployed by Packstack that is incompatible with this functionality - i.e. being able to resize volumes on the fly? Or is the functionality simply not there, despite the documentation to the contrary? For reference, here's a view of the cinder volume and the nova instance to which it is connected: (more) |