Dear friends,
I did some tests with making volume available without stopping VM. I'm
using CEPH and these steps produce the following results:
1) openstack volume set --state available [UUID]
- nothing changed inside both VM (volume is still connected) and CEPH
2) openstack volume set --size [
On Sat, Jun 23, 2018, 9:39 AM Volodymyr Litovka wrote:
> Dear friends,
>
> I did some tests with making volume available without stopping VM. I'm
> using CEPH and these steps produce the following results:
>
> 1) openstack volume set --state available [UUID]
> - nothing changed inside both VM (vo
Hi Jay,
We have had similar issues with extending attached volumes that are
iSCSI based. In that case the VM has to be forced to rescan the scsi bus.
In this case I am not sure if there needs to be a change to Libvirt or
to rbd or something else.
I would recommend reaching out to John Berna
On 06/23/2018 08:38 AM, Volodymyr Litovka wrote:
Dear friends,
I did some tests with making volume available without stopping VM. I'm using
CEPH and these steps produce the following results:
1) openstack volume set --state available [UUID]
- nothing changed inside both VM (volume is still conn
>
> In fact, I'm ok with delayed resize (upon power-cycle), and it's not an
> issue for me that VM don't detect changes immediately. What I want to
> understand is that changes to Cinder (and, thus, underlying changes to CEPH)
> are safe for VM while it's in active state.
>
No, this is not consi
Hi Sean,
thanks for the responce, my questions and comments below.
On 6/25/18 9:42 PM, Sean McGinnis wrote:
Not sure if it's an option for you, but in the Pike release support was added
to be able to extend attached volumes. There are several caveats with this
feature though. I believe it only
