Hi Ricardo + Nikolay<div><br></div><div>You are right, one thing we have in our short roadmap is to add a generic metada section for VMs. This metadata could be updated using the *update* functionality currently present for other commands.</div>
<div><br></div><div>Just to give you the rationale behind not having this yet. As you probably know the VM template is extended once the VM created with control data (e.g. DISK_ID's, specifric LEASES, SOURCE for DISK...) for obvious reasons we do not want a user to modify this. So we will split this in two, one for the control data and other to be used/modified by the user.</div>
<div><br></div><div>For now, as Nikolay suggests this limit somehow part of the out-of-the-box functionality (e.g. adding DESCRIPTION in a bulk submission), this functionality will need a custom program using OCA. About parsing the out put of onevm show, note that you can always get the full pool information with onevm list -x (TEMPLATE included) the onevm list command just parse and pick some of this info and present it in a tabular form...</div>
<div><br></div><div>THANKS FOR YOUR FEEDBACK!<br><br><div class="gmail_quote">On Thu, Oct 18, 2012 at 10:21 AM, <span dir="ltr"><<a href="mailto:knawnd@gmail.com" target="_blank">knawnd@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Ruben,<br>
<br>
Ruben S. Montero wrote on 17/10/12 14:42:<div><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi<br>
<br>
Why not using the name of the VM for this?.....<br>
</blockquote></div>
The name of the VM I would like to use to put hostname in it and perhaps use $NAME in contextualization as e.g.<br>
<br>
CONTEXT=[<br>
HOSTNAME="$<a href="http://NAME.domain.org" target="_blank">NAME.domain.org</a>" ]<br>
<br>
But that would make a sense in case when one could be possible to specify IP address in 'onetemplate instantiate' command.<div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Also if you want to append any arbitrary data to the VM (at creation) you can simply added to the VM template as:<br>
<br>
DESCRIPTION="this is a web server, use 1234 as root password"<br>
<br>
This will be stored in the template ans can be queried with the onevm show command or in the Template tab in Sunstone<br>
</blockquote></div>
As far as I understand that will work for a creation of a single VM but won't if I need to create a bunch of VMs with help of 'onetemplate instantiate' command.<br>
Is there any way to modify certain deployed VM's config to add arbitrary data like e.g. DESCRIPTION field (something like 'onevm update')?<br>
Moreover, in my opinion it's not convenient to parse the output of 'onevm show' command when I need to get a list of all VMs e.g. what have a word "web" in its description. It would be more convenient to have a separate column for that as I wrote before. But probably to do that there is a need to modify DB schema which is not desirable I guess.<br>
<br>
Regards,<br>
Nikolay.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Cheers<br>
<br>
Ruben<div><br>
<br>
On Tue, Oct 16, 2012 at 4:02 PM, <<a href="mailto:knawnd@gmail.com" target="_blank">knawnd@gmail.com</a> <mailto:<a href="mailto:knawnd@gmail.com" target="_blank">knawnd@gmail.com</a>>> wrote:<br>
<br>
Dear list,<br>
<br>
I wonder if there is any way to specify some text as a description/comment for a certain VM in<br>
order to be able toquery such info later e.g. during 'onevm list' command execution. I just<br>
don't want to get lost in all my VMs and which one is for what.<br>
I would like to have something like<br>
$ onevm list<br>
ID USER GROUP NAME STAT UCPU UMEM HOST TIME DESCRIPTION<br>
11 oneadmin oneadmin one-11 runn 100 1G <host1> 0d 02h07 web-server<br>
12 oneadmin oneadmin one-12 runn 1001G <host1> 0d 02h03 mail-server<br>
13 oneadmin oneadmin one-13 runn 100 1G <host2> 0d 00h17 development server<br>
<br>
<br>
Regards,<br>
Nikolay.<br>
______________________________<u></u>_________________<br>
Users mailing list<br></div>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a> <mailto:<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.<u></u>opennebula.org</a>><div>
<br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/<u></u>listinfo.cgi/users-opennebula.<u></u>org</a><br>
<br>
<br>
<br>
<br>
-- <br>
Ruben S. Montero, PhD<br>
Project co-Lead and Chief Architect<br>
OpenNebula - The Open Source Solution for Data Center Virtualization<br>
</div><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> <<a href="http://www.OpenNebula.org" target="_blank">http://www.OpenNebula.org</a>> | <a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.org</a> <mailto:<a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.<u></u>org</a>> | @OpenNebula<br>
</blockquote>
<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Ruben S. Montero, PhD<br>Project co-Lead and Chief Architect<br>OpenNebula - The Open Source Solution for Data Center Virtualization<br><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<br>
</div>