<br><br><div class="gmail_quote">On 24 October 2012 11:08, <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">
Daniel Molina wrote on 23/10/12 20:23:<div><div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 23 October 2012 14:31, <<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 Ruben,<br>
<br>
first of all, sorry for delay with reply!<br>
Please, see my comments inline.<br>
<br>
Ruben S. Montero wrote on 19/10/12 00:34:<br>
<br>
Hi Ricardo + Nikolay<br>
<br>
You are right, one thing we have in our short roadmap is to add a generic metada section<br>
for VMs. This metadata could be updated using the *update* functionality currently present<br>
for other commands.<br>
<br>
sounds encouraging! Is any information when such feature is planned to be implemented?<br>
<br>
<br>
Just to give you the rationale behind not having this yet. As you probably know the VM<br>
template is extended once the VM created with control data (e.g. DISK_ID's, specifric<br>
LEASES, SOURCE for DISK...) for obvious reasons we do not want a user to modify this.<br>
<br>
seems reasonable<br>
<br>
So we will split this in two, one for the control data and other to be used/modified by<br>
the user.<br>
<br>
For now, as Nikolay suggests this limit somehow part of the out-of-the-box functionality<br>
(e.g. adding DESCRIPTION in a bulk submission), this functionality will need a custom<br>
program using OCA. About parsing the out put of onevm show, note that you can always get<br>
the full pool information with onevm list -x (TEMPLATE included) the onevm list command<br>
just parse and pick some of this info and present it in a tabular form...<br>
<br>
Thanks a lot for detailed reply and explanations!<br>
<br>
<br>
JFYI You can easily add new columns to the onevm list command. The following patch adds a new DESCRIPTION column to the onevm list output:<br>
<br>
<a href="https://gist.github.com/8f8499704cbee0e5db84" target="_blank">https://gist.github.com/<u></u>8f8499704cbee0e5db84</a><br>
<br>
The onevm.yaml can be defined per user in $HOME/.one/onevm.yaml or globally in /etc/one/cli/onevm.yaml<br>
</blockquote></div></div>
Hi Daniel,<br>
Thanks for your patch and efforts!<br>
But I wasn't able to archive desired behavior.<br>
<br>
I did the following changes:<br>
$ diff /usr/lib/one/ruby/cli/one_<u></u>helper/onevm_helper.rb{,.orig}<br>
138,141d137<br>
< column :DESCRIPTION, "DESCRIPTION", :size=>12 do |d|<br>
< d["TEMPLATE"]["DESCRIPTION"]<br>
< end<br>
<<br>
143c139<br>
< :TIME, :DESCRIPTION<br>
---<br>
> :TIME<br>
<br>
$ cp /etc/one/cli/onevm.yaml ~/.one/<br></blockquote><div><br></div><div>Sorry I sent you a wrong path, use this instead </div><div><br></div><div>$ mkdir ~/.one/cli/</div><div>$ cp /etc/one/cli/onevm.yaml ~/.one/cli/</div>
<div><br></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
$ diff ~/.one/onevm.yaml /etc/one/cli/onevm.yaml<br>
42,46d41<br>
< :DESCRIPTION:<br>
< :desc: DESCRIPTION<br>
< :size: 20<br>
<<br>
<<br>
57d51<br>
< - :DESCRIPTION<br>
<br>
With help of 'onetemplate update' command I added DESCRIPTION parameter<br>
$ onetemplate show 5|grep -i description<br>
DESCRIPTION="description"<br>
<br>
and instantiate a VM based on that template.<br>
<br>
Although 'onevm show <VMID>' shows the presence of DESCRIPTION parameter 'onevm list' doesn't show DESCRIPTION column (neither column name nor content).<br>
<br>
'one stop' and 'one start' didn't help.<br>
<br>
If you have any guess why it is so then please share it.<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"><div class="im">
<br>
Cheers<br>
<br>
<br>
Regards,<br>
Nikolay.<br>
<br>
<br>
THANKS FOR YOUR FEEDBACK!<br>
<br>
<br>
On Thu, Oct 18, 2012 at 10:21 AM, <<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>><br></div><div class="im">
<mailto:<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></div><div class="im">
Hi Ruben,<br>
<br>
Ruben S. Montero wrote on 17/10/12 14:42:<br>
<br>
Hi<br>
<br>
Why not using the name of the VM for this?.....<br>
<br>
The name of the VM I would like to use to put hostname in it and perhaps use $NAME in<br>
contextualization as e.g.<br>
<br>
CONTEXT=[<br></div>
HOSTNAME="$<a href="http://NAME.domain.org" target="_blank">NAME.domain.org</a> <<a href="http://NAME.domain.org" target="_blank">http://NAME.domain.org</a>> <<a href="http://NAME.domain.org" target="_blank">http://NAME.domain.org</a>>" ]<div>
<div class="h5"><br>
<br>
<br>
But that would make a sense in case when one could be possible to specify IP address in<br>
'onetemplate instantiate' command.<br>
<br>
<br>
Also if you want to append any arbitrary data to the VM (at creation) you can<br>
simply added<br>
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<br>
or in<br>
the Template tab in Sunstone<br>
<br>
As far as I understand that will work for a creation of a single VM but won't if I need to<br>
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.<br>
DESCRIPTION field (something like 'onevm update')?<br>
Moreover, in my opinion it's not convenient to parse the output of 'onevm show'<br>
command when I<br>
need to get a list of all VMs e.g. what have a word "web" in its description. It would<br>
be more<br>
convenient to have a separate column for that as I wrote before. But probably to do<br>
that there<br>
is a need to modify DB schema which is not desirable I guess.<br>
<br>
Regards,<br>
Nikolay.<br>
<br>
<br>
Cheers<br>
<br>
Ruben<br>
<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>><br>
<mailto:<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>>><br>
<mailto:<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>> <mailto:<a href="mailto:knawnd@gmail.com" target="_blank">knawnd@gmail.com</a><br>
<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<br>
certain VM in<br>
order to be able toquery such info later e.g. during 'onevm list' command<br>
execution. I<br>
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<br>
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<br>
development server<br>
<br>
<br>
Regards,<br>
Nikolay.<br>
______________________________<u></u>_________________<br>
Users mailing list<br>
<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>><br>
<mailto:<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.<u></u>opennebula.org</a> <mailto:<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.<u></u>opennebula.org</a>>><br>
<mailto:<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.<u></u>opennebula.org</a> <mailto:<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.<u></u>opennebula.org</a>><br>
<mailto:<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.<u></u>opennebula.org</a> <mailto:<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.<u></u>opennebula.org</a>>>><br>
<br>
<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>
-- 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="http://www.OpenNebula.org" target="_blank">http://www.OpenNebula.org</a>> <<a href="http://www.OpenNebula.org" target="_blank">http://www.OpenNebula.org</a>><br>
<<a href="http://www.OpenNebula.org" target="_blank">http://www.OpenNebula.org</a>> |<br>
<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>><br>
<mailto:<a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.<u></u>org</a> <mailto:<a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.<u></u>org</a>>><br>
<mailto:<a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.<u></u>org</a> <mailto:<a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.<u></u>org</a>><br>
<mailto:<a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.<u></u>org</a> <mailto:<a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.<u></u>org</a>>>> | @OpenNebula<br>
<br>
<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>
<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="http://www.OpenNebula.org" target="_blank">http://www.OpenNebula.org</a>> |<br>
<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>><br>
<mailto:<a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.<u></u>org</a> <mailto:<a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.<u></u>org</a>>> | @OpenNebula<br>
<br>
<br>
______________________________<u></u>_________________<br>
Users mailing list<br>
<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>><br></div></div>
<div class="im">
<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>
Daniel Molina<br>
Project Engineer<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:dmolina@opennebula.org" target="_blank">dmolina@opennebula.org</a> <mailto:<a href="mailto:dmolina@opennebula.org" target="_blank">dmolina@opennebula.org</a><u></u>> | @OpenNebula<br>
</blockquote>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Daniel Molina<br>Project Engineer<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:dmolina@opennebula.org" target="_blank">dmolina@opennebula.org</a> | @OpenNebula<br>