<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p dir="ltr"><br>
Den 12 jul 2014 22:49 skrev Niklas Fondberg <niklas@vireone.com>:<br>
><br>
><br>
><br>
> On 12 jul 2014, at 16:57, "Karli Sjöberg" <Karli.Sjoberg@slu.se> wrote:<br>
><br>
>><br>
>> Den 12 jul 2014 15:45 skrev Niklas Fondberg <niklas@vireone.com>:<br>
>> ><br>
>> > Hi,<br>
>> ><br>
>> > I’m new to oVirt but I must say I am impressed! <br>
>> > I am running it on a HP DL380 with an external SAS chassi.<br>
>> > Linux dist is Centos 6.5 and oVirt is 3.4 running all-in-one (for now until we need to have a second host).<br>
>> ><br>
>> > Our company (www.vireone.com) deals with system architecture for many telco and media operators and is now setting up a small own datacenter for our internal tests as well as our IT infrastructure.<br>
>> > We are in the process of installing Zentyal for the SMB purposes on a guest and it would be great to have that guest also serving a fs path directory with NFS + SMB (which is semi crippled on the host after oVirt installation with version 3 et.c.).<br>
>> ><br>
>> > Does anyone have an idea of how I can through oVirt (seen several solutions using virsh and kvm) letting my Zentyal Ubuntu guest have access to a host mount point or if necessary (second best) a seperate partition?<br>
>> ><br>
>> > Best regards<br>
>> > Niklas<br>
>> ><br>
>><br>
>> Why not just give the guest a thin provision virtual hard drive and expand it on a demand basis?<br>
>><br>
>> /K<br>
><br>
> Thanks for the advise but this would not suite us I'm afraid. It would be difficult wrt incremental backups as well as host machine file-routines. <br>
><br>
></p>
<p dir="ltr">Well, going by Occam's raizor; the simplest answer is usually correct. Can't really tell what you mean by file-routines but backups would be well served by snapshots (can't get more incremental than that) and disaster recovery could be as easy
as a rsync from inside the guest to a remote machine.</p>
<p dir="ltr">The biggest pros here is the ease of being able to setup an export domain, attach, export the VM, detach domain, and then attach and import to a "real" setup when the AIO starts feeling crowded later on. Thinking ahead is never a bad thing, no?</p>
<p dir="ltr">/K</p>
</body>
</html>