Hi Erlon, hi Philipp thank you for your answers.
I will try to explain with a real case:
@Erlon: I have 2 nodes that works as a SAN with targetcli and DRBD for a
raid over network. This cluster can be seen as an "ISCSI node".
Furthermore, I have 2 nodes with openstack-cinder-volume (with
Hi, I'd like to know if it is possible to use openstack-cinder-volume with
a remote LVM. This could be a new feature proposal if the idea is good.
More precisely, I'm thinking a solution where openstack-cinder-volume runs
on a dedicated node and LVM on another node (called "storage node"). On
the
Hi, I'm using cinder with lvm (mitaka release). Actually all works well,
but I noticed that when I create a new bootable volume from an image, the
storage backend has an intensive cpu/disk usage with a load around 12. I
think this happens because cinder use dd with oflag=direct during the copy.
I
er.com>:
> On 01/21/2017 03:00 AM, Marco Marino wrote:
>
>> Really thank you!! It's difficult for me find help on cinder and I think
>> this is
>> the right place!
>> @Duncan, if my goal is to speeding up bootable volume creation, I can
>> avoid to
&g
s.frie...@windriver.com>
> wrote:
>
>> On 01/20/2017 04:07 AM, Marco Marino wrote:
>>
>>> Hi, I'm trying to use cinder with lvm thin provisioning. It works well
>>> and I'd
>>> like to know if there is some reason lvm thin should be avoided in mitak
Hi, I'm trying to use cinder with lvm thin provisioning. It works well and
I'd like to know if there is some reason lvm thin should be avoided in
mitaka release. I'm trying to use with
max_over_subscription_ratio = 1.0
so I don't have problems with over subscription.
I using thin provisioning
Ok, problem solved (it seems)
in /etc/lvm/lvm.conf I need to set
auto_set_activation_skip = 0
and, in my case, I set the same in /etc/cinder/lvm.conf (because I'm using
a cluster configuration for lvm)
Thank you
2017-01-18 16:38 GMT+01:00 Marco Marino <marino@gmail.com>:
> Hi, I
Hi, I'm trying to use lvm thin provisioning with openstack cinder (mitaka)
but I have a problem with snapshots. I'm trying to create a snapshot from a
volume (detached) and then create a new volume from the snapshot.
1) Snapshot creation works well and I have (with lvs)
LV
