[one-users] Context disk location problem when VM_DIR !=$ONE_LOCATION/var

Shi Jin jinzishuai at gmail.com
Fri Feb 25 10:05:56 PST 2011

Thank you.
>From the explanation, it seems to require the VM instance working directory
to be physically in the same place of $ONE_LOCATION/var, even though the
nodes can mount it at a different location using NFS.

I have a few comments
1. Mounting the same disk at different locations on different machines does
not really make much sense to me, although perfectly possible. So I find
this not a critical feature. This is what I think VM_DIR is designed for and
in this sense, the current code works perfectly fine.
2. However, in my plan, I want to put the VM instance working directory
(thus VM_DIR) to be a different physical LUN than the $ONE_LOCATION/var
since I would like to implement different storage features on $VM_DIR and
$ONE_LOCATION. For example, they can have different backup and snapshot
setups. $ONE_LOCATION is more critical and I might want to implement hourly
snapshot/backup while $VM_DIR is  for working image files and I might only
want to do it daily considering the amount of storage required and the
consistency of snapshotting a disk image under use.
This is how I thought the definition of VM_DIR can be of more value.


On Thu, Feb 24, 2011 at 6:59 AM, Javier Fontan <jfontan at gmail.com> wrote:

> I've benn testing againg the scripts and work nice for me. Check this
> explanation:
> http://dev.opennebula.org/issues/445#note-4
> On Sat, Feb 19, 2011 at 7:00 AM, Shi Jin <jinzishuai at gmail.com> wrote:
> > Hi there,
> > I used to let the VM_DIR to be the default of $ONE_LOCATION/var.
> > Now I set it to something else. But I am having problem with the context
> > disk.
> > When I specify the context, the disk.1 is still in the $ONE_LOCATION/var
> > while disk.0 and the deployment.0 are already in the VM_DIR and most
> > importantly deployment.0 still assumes the disk.1 in the same place as
> > disk.1.
> > I traced down the problem to be the tm_context.sh script which called
> > fix_dst_path to actually change the output file from in VM_DIR
> > to $ONE_LOCATION/var in the case of the two being different. Is this a
> bug?
> > Simply comment out this line would get it working again.
> > I am using the tm_nfs driver.
> > Thank you very much.
> > Shi
> >
> > --
> > Shi Jin, Ph.D.
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opennebula.org
> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> >
> >
> --
> Javier Fontan, Grid & Virtualization Technology Engineer/Researcher
> DSA Research Group: http://dsa-research.org
> Globus GridWay Metascheduler: http://www.GridWay.org
> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org

Shi Jin, Ph.D.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20110225/8e19413a/attachment-0002.htm>

More information about the Users mailing list