<div dir="ltr">Hi<div><br></div><div>These two are on our radar and probably scheduled for the next release. I totally agree that we need to simplify the provision process even more.</div><div><br></div><div>About feature 1. </div><div><br></div><div>We have two issues:</div><div><br></div><div>[1] Clone a running VM. <a href="http://dev.opennebula.org/issues/2637" target="_blank">http://dev.opennebula.org/issues/2637</a></div><div>[2] Clone a template . <a href="http://dev.opennebula.org/issues/2051" target="_blank">http://dev.opennebula.org/issues/2051</a></div><div><br></div><div>Last one includes images (pretty much the procedure outlined by Anandharaj under "New VM request") and I think this will cover exactly your request.</div><div><br></div><div>About feature 2. </div><div><br></div><div>We want to add the ability to update any part of a template for VM, most of it can be done if the VM is running (eg. attach a new disk or nic). Others like memory can be resized when the VM is powered off. You would not need to update and recreate the template.</div><div><br></div><div>[3] <a href="http://dev.opennebula.org/issues/2065" target="_blank">http://dev.opennebula.org/issues/2065</a><br></div><div><br></div><div>So, I believe we can implement the workflow described by Anandharaj with these features (and exposing it through Cloud View)...</div><div><br></div><div>Thanks for your feedback!</div><div><br></div><div>Cheers</div><div><br></div><div>Ruben</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 3, 2014 at 11:34 PM, Nicolas Bélan <span dir="ltr"><<a href="mailto:nicolas.belan@gmail.com" target="_blank">nicolas.belan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
I have exactly the same pb, and same needs ...<br>
I start think about a dedicated web service to handle that, but a
shorter (quicker) way to achieve deployments would be nice !<br>
<br>
I will follow this thread for feebacks too<br>
<br>
Best regards,<br>
NB<br>
<br>
<div>Le 02/10/2014 06:07, Anandharaj
Subramaniam a écrit :<br>
</div>
<blockquote type="cite"><div><div>
<div>
<p class="MsoNormal"><span style="color:#1f497d">Hi All,</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">Just need some
clarification and would like to get you guys feedback on
managing VMs using OpenNebula in your environment.
</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><u><span style="color:#1f497d">Our current
practice as below (using OpenNebula 4.2):</span></u></p>
<p><span style="color:#1f497d"><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:#1f497d">New VM
request</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Clone
existing image (master image) to a new image. All the images
are persistent.
</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Clone
existing template (master template) to a new template.</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Update
the new template – set cpu/vcpu, memory, image (point to
newly created image), ip address, etc</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Instantiate
the template</span></p>
<p><span style="color:#1f497d"> </span></p>
<p><span style="color:#1f497d"><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:#1f497d">Update
the spec of the VM</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Shutdown
/ delete the running VM</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Update
the template belongs to that particular VM – e.g set the new
memory size</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Instantiate
the template</span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1f497d">Note: a) In our setup, every VM will
have their own template as per done in #1</span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1f497d"> b) Reason being update
the template & re-instantiate instead of just update
the memory in VM is because of #3 below</span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:#1f497d"> </span></p>
<p><span style="color:#1f497d"><span>3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:#1f497d">Repair
the VM</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">In some
cases the VM’s filesystem will have some errors (eg: due to
force shutdown / nfs issues) therefore require to run fsck
using live CD.</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Image
type CDROM cannot be attached thru VM list page (click on
the VM -> storage tab)</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Update
the VM’s template – add disk and choose the ISO image,
choose boot = cdrom</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Instantiate
the template and fix the errors using the live CD</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Shutdown
/ delete the running VM</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Update
the VM’s template – remove the ISO image and choose boot =
hd</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Instantiate
the template</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">From the above
scenario, anything that we are doing inefficiently? Im still
new to this OpenNebula so appreciate you guys feedback /
suggestion</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><u><span style="color:#1f497d">Testing
environment (OpenNebula 4.8)</span></u></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">To further
understand on this OpenNebula, I have setup ONE 4.8 and
testing the Cloud View and see how I can improve my
operation / VM administration.</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">The way user
can create VM in Cloud View is the one I need – user define
the VM name, choose the template (OS), set the memory &
CPU and launch it. Very simple. But unfortunately this only
works with non-persistent image type. In my case, I cannot
use non-persistent image because of the reason stated in #2
and #3 above.</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">So what I think
Cloud View can be improved is:</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Based on
config parameter (oned.conf -> ONE_DEPLOY=Persistent),
when user create a VM, a template should be created and the
image should be cloned as persistent image. This is kinda
same behavior as “Save” VM with only different is the image
persistent yes/no and template spec</span></p>
<p style="margin-left:54.0pt"><span style="color:#1f497d"><span>-<span>
</span></span></span><span style="color:#1f497d">Able to
attach / detach CDROM</span></p>
<p class="MsoNormal"><span style="color:#1f497d"></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Feel free to
comment on this and provide some feedback.</span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="color:#1f497d">--</span></p>
<p class="MsoNormal"><span style="color:#1f497d">Regards,</span></p>
<p class="MsoNormal"><span style="color:#1f497d">Anandharaj</span></p>
<p class="MsoNormal"> </p>
</div>
<br>
<hr>
<div>
<b>DISCLAIMER:</b></div>
<br>
<div>
<p style="font-size:8pt;line-height:10pt;font-family:'Cambria','times new roman',serif">
This e-mail (including any attachments) is for the
addressee(s) only and may be confidential, especially as
regards personal data. If you are not the intended recipient,
please note that any dealing, review, distribution, printing,
copying or use of this e-mail is strictly prohibited. If you
have received this email in error, please notify the sender
immediately and delete the original message (including any
attachments).</p>
</div>
<br>
<div>
<p style="font-size:8pt;line-height:10pt;font-family:'Cambria','times new roman',serif">
MIMOS Berhad is a research and development institution under
the purview of the Malaysian Ministry of Science, Technology
and Innovation. Opinions, conclusions and other information in
this e-mail that do not relate to the official business of
MIMOS Berhad and/or its subsidiaries shall be understood as
neither given nor endorsed by MIMOS Berhad and/or its
subsidiaries and neither MIMOS Berhad nor its subsidiaries
accepts responsibility for the same. All liability arising
from or in connection with computer viruses and/or corrupted
e-mails is excluded to the fullest extent permitted by law.</p>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><span><pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a>
</pre>
</span></blockquote>
<br>
</div>
<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<br clear="all"><div><br></div>-- <br></a><div dir="ltr"><a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank"><div><div>-- <br></div></div>Ruben S. Montero, PhD<br>Project co-Lead and Chief Architect</a><div><a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">OpenNebula - Flexible Enterprise Cloud Made Simple<br></a><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.org</a> | @OpenNebula</div></div>
</blockquote></div></div></div>