Open Stack

Yes, technically nova-volume can run anywhere. Referring back to the the
ref arch you would run the volume api on the controller node and the
actual volume service on the compute nodes. There are some obvious
considerations to be made (such as performance of the disks, usage of the
system with vm's, instance/image storage), but if you have space remaining
it could be a good way to use it.

Jason


On 5/1/12 3:01 PM, "Igor Laskovy" <igor.laskovy at gmail.com> wrote:

>Thanks Jason, Vivek for this clarifications.
>
>Is it possible to run nova-volumes on each compute node by themselves
>use? Than this will locate all data of current instance on one compute
>node from decentralization storage vision.
>
>
>On Tue, May 1, 2012 at 3:20 PM, Jason Cannavale
><jason.cannavale at rackspace.com> wrote:
>> Hi Igor, Vivek,
>>
>> Apologies for the confusion. This site was put together quite some time
>>ago
>> (between Cactus and Diablo releases) and only took into consideration
>>the
>> nova and swift projects, and has not been updated since that time.
>> Unfortunately, there was no consideration for nova-volumes, however your
>> assumption is correct that the huge local storage on the compute nodes
>>was
>> for the image download from glance to the compute node, booting the
>>image,
>> and providing some local storage for the instances themselves.
>>
>>
>> In the case of images and snapshots the document makes the assumption
>>that
>> swift was the backend for glance. In this case you would have
>>glance-api and
>> glance-registry running on the controller node with the swift
>>middleware and
>> would follow the swift portion of the reference architecture.
>>
>>
>> Jason
>>
>> From: Vivek Singh Raghuwanshi <vivekraghuwanshi at gmail.com>
>> Date: Tuesday, May 1, 2012 12:59 PM
>> To: Igor Laskovy <igor.laskovy at gmail.com>
>> Cc: "openstack-operators at lists.openstack.org"
>> <openstack-operators at lists.openstack.org>
>> Subject: Re: [Openstack-operators] Question regarding to
>> referencearchitecture.org
>>
>> Yes and to store images and snapshorts
>>
>> On Tue, May 1, 2012 at 5:11 PM, Igor Laskovy <igor.laskovy at gmail.com>
>>wrote:
>>>
>>> Hi all!
>>>
>>> I am new to the openstack. I have question regarding to
>>> http://www.referencearchitecture.org/physical-deployment/ .
>>> This design shown a two controller nodes, one brand iSCSI DAS and a
>>> lot of compute nodes. Controller nodes has small local storages and
>>> connectivity to iSCSI DAS. Compute nodes, according to "Rule of
>>> Thumb): 4 to 8 GB RAM and 1 Spindle Per Core", has a lot of local
>>> spaces each one.
>>> So how work Nova-volumes here? It is running on controller node and
>>> use VG "nova-volumes" which based on disk via attached iSCSI DAS?
>>> After that euca-create-volume create volume and will expose it to the
>>> compute node via iSCSI again? If it is correct, what is the point to
>>> use huge local storages at compute nodes, for boot image of instances
>>> only?
>>>
>>> Igor Laskovy
>>> _______________________________________________
>>> Openstack-operators mailing list
>>> Openstack-operators at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>>
>>
>> --
>> ViVek Raghuwanshi
>> Mobile -+91-09595950504
>>
>> Skype - vivek_raghuwanshi
>>
>>
>
>
>
>-- 
>Igor Laskovy