Hello Christopher,<div><br></div><div>actually to be honest there's something I didn't quite understand about your use-case. What the manual procedure you followed to make the data/config volume to be accessible from the VMs? How is it shared? Or is it dynamically mounted by the VM, and if so, how?</div>
<div><br></div><div>regards,<br>Jaime</div><div><br><div class="gmail_quote">On Mon, Sep 10, 2012 at 5:53 PM, christopher barry <span dir="ltr"><<a href="mailto:cbarry@rjmetrics.com" target="_blank">cbarry@rjmetrics.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks for looking into this Jaime.<br>
<br>
Ideally, we would not need a template per machine, but just one for all<br>
machines using a specific readonly base image. Not sure if that's what<br>
you meant below or not...<br>
<br>
I would love to be in the loop as you plan this feature.<br>
<br>
Thanks!<br>
<span class="HOEnZb"><font color="#888888"><br>
-C<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Mon, 2012-09-10 at 12:20 +0200, Jaime Melis wrote:<br>
> Hello,<br>
><br>
><br>
> Short answer: can't be achieved currently, but it's an interesting use<br>
> case and we will include it in OpenNebula 3.8 [1].<br>
><br>
><br>
> Long answer:<br>
> What you need is a DISK which will not be cloned (CLONE = NO), will<br>
> not be saved (SAVE = NO) and that it's marked as readonly (READONLY =<br>
> YES). Currently there are some inconsistencies regarding these<br>
> attributes: they are overridden by the image persistency (CLONE and<br>
> SAVE) and type (READONLY). This renders these attributes useless in<br>
> this scenario.<br>
><br>
><br>
> We need to modify the core in order to make it work, and we will<br>
> release it with OpenNebula 3.8. Once it's working you will be able to:<br>
> 1) Register the base OS image<br>
> 2) Create a new template per VM where:<br>
> -- the base OS disk is set as DISK = [ IMAGE_ID = <ID>, SAVE = NO,<br>
> CLONE = NO, READONLY = YES ]<br>
> -- each one has its own CONTEXT<br>
> 3) Once the VM boots it performs the aufs setup.<br>
><br>
><br>
> [1] <a href="http://dev.opennebula.org/issues/1449" target="_blank">http://dev.opennebula.org/issues/1449</a><br>
><br>
><br>
> Cheers,<br>
> Jaime<br>
><br>
> On Fri, Aug 31, 2012 at 8:35 PM, christopher barry<br>
> <<a href="mailto:cbarry@rjmetrics.com">cbarry@rjmetrics.com</a>> wrote:<br>
> Greetings Nebulars<br>
><br>
> I'm re-posting this, as it didn't get an answer last time. I<br>
> could use<br>
> some advise/guidance.<br>
><br>
> Here is the scenario I'm trying to create:<br>
><br>
> * I have a base OS image as a logical volume in an array.<br>
><br>
> * I want all guests to boot this same image read-only - no<br>
> copies.<br>
><br>
> * the initramfs in the base image will mount the context iso<br>
> to<br>
> determine it's own unique data/config disk - also a logical<br>
> volume.<br>
><br>
> * this data/config volume is unioned with aufs read/write over<br>
> the<br>
> readonly base image in the initramfs, so that they together<br>
> form the<br>
> complete 'root' filesystem.<br>
><br>
> * all disks are served via iSCSI<br>
><br>
><br>
> Each data/config disk needs to be persistent, and belong to a<br>
> unique<br>
> guest, but everyone shares the exact same read-only OS disk.<br>
><br>
> Can anyone speak to the best method of integrating this<br>
> scenario with<br>
> ONE? I've tested this outside of ONE, but now I need to make<br>
> it work in<br>
> ONE. Would I need a separate template for each machine? I've<br>
> heard<br>
> mention of maybe needing to make the OS disk an ISO image,<br>
> does anyone<br>
> know why that would be a requirement?<br>
><br>
><br>
> Regards,<br>
> -C<br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opennebula.org">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>
><br>
><br>
><br>
><br>
> --<br>
> Jaime Melis<br>
> Project Engineer<br>
> OpenNebula - The Open Source Toolkit for Cloud Computing<br>
> <a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:jmelis@opennebula.org">jmelis@opennebula.org</a><br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Jaime Melis<br>Project Engineer<br>OpenNebula - The Open Source Toolkit for Cloud Computing<br><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:jmelis@opennebula.org" target="_blank">jmelis@opennebula.org</a><br>
</div>