<div>Hi</div><div><br></div>Yes in this case there should not be any path. Here it is working:<div>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><</div>
<div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>img> cat dblock.img </div><div>NAME = "Experiment results"</div><div>TYPE = DATABLOCK</div><div># No PATH set, this image will start as a new empty disk</div>
<div>SIZE = 2048</div><div>FSTYPE = ext3</div><div>PUBLIC = NO</div><div>DESCRIPTION = "Storage for my Thesis experiments."</div></div><div><div><br></div><div>> oneimage create dblock.img </div>
</div><div><br></div><div><br></div><div><div>> oneimage create dblock.img </div><div>pc-ruben:img> oneimage list</div><div> ID USER NAME TYPE REGTIME PUB PER STAT #VMS</div><div>
...</div>
<div> 5 ruben Experiment results DB Nov 24, 2010 20:30 No No rdy 0</div><div><br></div><div><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<</div>
<div><br></div><div><br></div><div>It may be a ruby version issue, which one are you using?</div><div><br></div><div>About the other questions:</div><div><br></div><div>a.- qcow2 feature is already in the source repo, and will be included in the upcoming OpenNebula 2.0.1.</div>
<div>b.- there is not a relationship between the persistent attribute and the image format. When a image is declared as persistent only one VM is able to use it to prevent data inconsistencies in the image.</div><div>c.- spare images: I think I do not really understand your use case. Would not a datablock do the job?</div>
<div><br></div><div>Cheers</div><div><br></div><div>Ruben</div><div><br></div><div class="gmail_quote">On Tue, Nov 23, 2010 at 9:38 PM, Steven Timm <span dir="ltr"><<a href="mailto:timm@fnal.gov">timm@fnal.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I am trying to create the example DATABLOCK volume<br>
as shown on<br>
<br>
<a href="http://www.opennebula.org/documentation:rel2.0:img_template" target="_blank">http://www.opennebula.org/documentation:rel2.0:img_template</a><br>
<br>
bash-3.2$ cat datablock_test.one<br>
NAME = "Experiment results"<br>
TYPE = DATABLOCK<br>
# No PATH set, this image will start as a new empty disk<br>
SIZE = 2048<br>
FSTYPE = ext3<br>
PUBLIC = NO<br>
DESCRIPTION = "Storage for my Thesis experiments."<br>
<br>
bash-3.2$ oneimage register datablock_test.one<br>
Error: mkfs Image: in mkfs command.<br>
<br>
What is missing? Template reference page seems to<br>
indicate that I need SOURCE or PATH required, but<br>
what would be SOURCE if I just want to start with<br>
a blank file system?<br>
<br>
------------------------<br>
<br>
Also I have more questions on the qcow2 format:<br>
a) we are running opennebula 2.0, haven't there been some<br>
bug reports that qcow2 isn't working with latest opennebula.<br>
b) It's my understanding that qcow2 format does quick copy<br>
on write, how does that mesh with a image that is persistent--i.e<br>
in normal circumstances only one system would be using it?<br>
<br>
Does anyone know of a way to send a sparse image along with KVM<br>
or can that only be done in Xen?<br>
Steve<div><div></div><div class="h5"><br>
<br>
<br>
On Fri, 12 Nov 2010, Ruben S. Montero wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi<br>
<br>
Yes OpenNebula supports that functionality. You can define spare file<br>
systems that can be created on the fly and then saved for later usage.<br>
There are two aspects to be considered:<br>
<br>
*Usage*<br>
<br>
This can be implemented with the new image repository using a<br>
DATABLOCK image, more information on this [1]. Also you can define a<br>
FS image to be a plain FS that will be created the first time and then<br>
can be reused, options for disks in [2]. If you use the image repo, be<br>
sure to make the image persistent, and when using the second option<br>
make sure to include SAVE=yes in the disk so you keep the changes.<br>
(Note that SOURCE in the previous image definitions may point to a<br>
block device)<br>
<br>
*Implementation*<br>
<br>
This depends on the storage architecture you are planning for your<br>
cloud. The images can be backed by a device (e.g LVM, you need to make<br>
the devices known to all the WNs) a shared FS (NFS is not an option<br>
but may be Ceph, GlusterFS or Lustre works in your setup). Also you<br>
can use qcow formats that will dynamically grow and may help to move<br>
the disk around. OpenNebula 2.0 can be used to implement these<br>
options. You may need to tune some of the drivers to match your system<br>
tough.<br>
<br>
Let me know if you need more help<br>
<br>
Cheers<br>
<br>
Ruben<br>
<br>
[1] <a href="http://www.opennebula.org/documentation:rel2.0:img_guide" target="_blank">http://www.opennebula.org/documentation:rel2.0:img_guide</a><br>
[2] <a href="http://www.opennebula.org/documentation:rel2.0:template#disks_section" target="_blank">http://www.opennebula.org/documentation:rel2.0:template#disks_section</a><br>
<br>
On Thu, Nov 11, 2010 at 8:00 PM, Steven Timm <<a href="mailto:timm@fnal.gov" target="_blank">timm@fnal.gov</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I have a user who has a need for 250GB of disk storage (eventually)<br>
that he would like to migrate around with his VM. NFS isn't<br>
suitable for this application. This is an application which will<br>
start with a file base and then gradually grow. On Amazon this<br>
could be a use case for EBS but ONE doesn't have anything like that<br>
as far as I can tell.<br>
<br>
My question, can I create an opennebula template that calls out<br>
device "vdc" as a sparse file system eventually growable to 250 GB,<br>
and migrate that and save that as necessary? If so, how?<br>
We are running opennebula 2.0 and using KVM as our hypervisor.<br>
<br>
Steve Timm<br>
<br>
<br>
--<br>
------------------------------------------------------------------<br>
Steven C. Timm, Ph.D (630) 840-8525<br>
<a href="mailto:timm@fnal.gov" target="_blank">timm@fnal.gov</a> <a href="http://home.fnal.gov/~timm/" target="_blank">http://home.fnal.gov/~timm/</a><br>
Fermilab Computing Division, Scientific Computing Facilities,<br>
Grid Facilities Department, FermiGrid Services Group, Assistant Group<br>
Leader.<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br>
</blockquote>
<br>
<br>
<br>
<br>
</blockquote>
<br>
-- <br>
------------------------------------------------------------------<br>
Steven C. Timm, Ph.D (630) 840-8525<br>
<a href="mailto:timm@fnal.gov" target="_blank">timm@fnal.gov</a> <a href="http://home.fnal.gov/~timm/" target="_blank">http://home.fnal.gov/~timm/</a><br>
Fermilab Computing Division, Scientific Computing Facilities,<br>
Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Dr. Ruben Santiago Montero<br>Associate Professor (Profesor Titular), Complutense University of Madrid<br><br>URL: <a href="http://dsa-research.org/doku.php?id=people:ruben" target="_blank">http://dsa-research.org/doku.php?id=people:ruben</a><br>
Weblog: <a href="http://blog.dsa-research.org/?author=7" target="_blank">http://blog.dsa-research.org/?author=7</a><br>
</div>