Ok in that case, with Grizzly you can use the “multi-backends” feature:
https://wiki.openstack.org/wiki/Cinder-multi-backend

and that should do it :)

On 08 Nov 2013, at 05:29, Guilherme Russi <[email protected]> wrote:

> It is a hard disk, my scenario is one Controller (where I have my storage 
> cinder and my network quantum) and four compute nodes.
> 
> 
> 2013/11/8 Razique Mahroua <[email protected]>
> ok !
> what is your actual Cinder backend? Is it a hard disk, a SAN, a network 
> volume, etc…
> 
> On 08 Nov 2013, at 05:20, Guilherme Russi <[email protected]> wrote:
> 
>> Hi Razique, thank you for answering, I want to expand my cinder storage, is 
>> it the block storage? I'll use the storage to allow VMs to have more hard 
>> disk space.
>> 
>> Regards.
>> 
>> Guilherme.
>> 
>> 
>> 
>> 2013/11/8 Razique Mahroua <[email protected]>
>> Hi Guilherme !
>> Which storage do you precisely want to expand?
>> 
>> Regards,
>> Razique
>> 
>> 
>> On 08 Nov 2013, at 04:52, Guilherme Russi <[email protected]> wrote:
>> 
>> > Hello guys, I have a Grizzly deployment running fine with 5 nodes, and I 
>> > want to add more storage on it. My question is, can I install a new HD on 
>> > another computer thats not the controller and link this HD with my cinder 
>> > that it can be a storage too?
>> > The computer I will install my new HD is at the same network as my cloud 
>> > is. I'm asking because I haven't seen a question like that here. Does 
>> > anybody knows how to do that? Have a clue? Any help is welcome.
>> >
>> > Thank you all.
>> >
>> > Best regards.
>> > _______________________________________________
>> > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> > Post to     : [email protected]
>> > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> 
>> 
> 
> 

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Reply via email to