On a single node using multi-backend you should keep in mind all of your
iSCSI traffic going through that node. Usual VG size limits apply of
course as well. Some guidelines I've heard from various OpenStack vendors
in the past suggest 5TB max on a single cinder-volume/LVM node. From there
add m
Is there any limit as well for LVM backends ?
On Mon, Apr 6, 2015 at 2:12 AM, John Griffith
wrote:
>
>
> On Sun, Apr 5, 2015 at 2:42 PM, John Griffith > wrote:
>
>>
>> On Apr 5, 2015 2:10 PM, "mad Engineer" wrote:
>>
>>> Read about cinder multi backend support,for using different backend
>>> t
On Sun, Apr 5, 2015 at 2:42 PM, John Griffith
wrote:
>
> On Apr 5, 2015 2:10 PM, "mad Engineer" wrote:
>
>> Read about cinder multi backend support,for using different backend types.
>> I have 2 servers for running as lvm+iscsi back ends.
>> Is it possible to use these 2 lvm backend nodes for sa
On Apr 5, 2015 2:10 PM, "mad Engineer" wrote:
> Read about cinder multi backend support,for using different backend types.
> I have 2 servers for running as lvm+iscsi back ends.
> Is it possible to use these 2 lvm backend nodes for same volume type and
> schedule block drives between these for th
Read about cinder multi backend support,for using different backend types.
I have 2 servers for running as lvm+iscsi back ends.
Is it possible to use these 2 lvm backend nodes for same volume type and
schedule block drives between these for that volume type.
So that volumes will be distributed betw
