<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>We just create a hidden file in the /etc/one-context.d directory after script execution that we configure each script to validate it exists. If it does, then the script exits. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Rudimentary, sure, but works for us.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> users-bounces@lists.opennebula.org [mailto:users-bounces@lists.opennebula.org] <b>On Behalf Of </b>ML mail<br><b>Sent:</b> Tuesday, March 04, 2014 2:57 AM<br><b>To:</b> Liu, Gene; Javier Fontan<br><b>Cc:</b> users<br><b>Subject:</b> Re: [one-users] ONE context package<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'>While running the script at first boot only is not a bad idea, you will have to think about the case where you change the hostname or change the DNS PTR entry.... Your VM would be stuck with the old hostname. So if you go this way there should be at least a check in the script to see if the hostname or DNS PTR entry have changed, if yes adapt the /etc/hostname and if not do nothing...<br><br>Regards,<br>ML<o:p></o:p></span></p><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt;background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p><div><div><div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>On Monday, March 3, 2014 9:53 PM, "Liu, Gene" <<a href="mailto:Gene.Liu@alcatel-lucent.com">Gene.Liu@alcatel-lucent.com</a>> wrote:</span><span style='font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p></div><div><div id=yiv6280186146><div><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'>It works well on RHEL6.5. Thanks!<br><br>BTW, can these scripts be set run at first boot only? We do not need recreate/overwrite these settings each time VM reboot.<br><br>Thanks!<o:p></o:p></span></p><pre style='background:white'><span style='color:black'>Gene Liu<o:p></o:p></span></pre><pre style='background:white'><span style='color:black'>On 14-03-03 06:53 AM, Javier Fontan wrote:<o:p></o:p></span></pre></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'>Here they are: <o:p></o:p></span></p><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p></div><div><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><a href="http://dev.opennebula.org/attachments/download/768/one-context_4.5.0.deb" target="_blank">http://dev.opennebula.org/attachments/download/768/one-context_4.5.0.deb</a><o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><a href="http://dev.opennebula.org/attachments/download/769/one-context_4.5.0.rpm" target="_blank">http://dev.opennebula.org/attachments/download/769/one-context_4.5.0.rpm</a><o:p></o:p></span></p></div></div><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'>Remember to set DNS_HOSTNAME=yes to use the DNS name or SET_HOSTNAME to fix the name manually.<o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt;background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'>On Mon, Mar 3, 2014 at 10:52 AM, ML mail <<a href="mailto:mlnospam@yahoo.com" target="_blank">mlnospam@yahoo.com</a>> wrote:<o:p></o:p></span></p><div><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'>Hi Javier,<br><br>Thanks for the changes. I am not in a rush so I will test directly with the packages. Let me know when and where the new packages are available and I will make sure to test the .deb one for you and let you know.<br><br>Cheers,<br>ML <o:p></o:p></span></p><div><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt;background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p><div><div><div><p class=MsoNormal style='background:white'><span style='font-family:"Arial","sans-serif";color:black'>On Friday, February 28, 2014 6:21 PM, Javier Fontan <<a href="mailto:jfontan@opennebula.org" target="_blank">jfontan@opennebula.org</a>> wrote:</span><span style='font-family:"Helvetica","sans-serif";color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'>I've uploaded the scripts to the branch feature-2453 for both deb and<br>rpm based distros.<br><br>DNS_HOSTNAME=yes: gets the first ip and tries to get the dns name with "host"<br>SET_HOSTNAME=name.of.the.host: sets the hostname<br><br>I'll try to create the packages before leaving the office but you can<br>follow the instructions there in case you want to create them<br>yourself.<br><br><br>[1] <a href="https://github.com/OpenNebula/one/tree/feature-2453/share/scripts/context-packages" target="_blank">https://github.com/OpenNebula/one/tree/feature-2453/share/scripts/context-packages</a><br><br>On Thu, Feb 27, 2014 at 10:29 PM, ML mail <<a href="mailto:mlnospam@yahoo.com" target="_blank">mlnospam@yahoo.com</a>> wrote:<br>> Hi Javier,<br>><br>> Thanks for the example with using $NAME in the SET_HOSTNAME context variable<br>> that for sure helps not having one template per VM. Although I already see<br>> the next problem, you can't have spaces in your VM name but that's a detail<br>> :)<br>><br>> I totally agree regarding the dynamic hostname based on the PTR DNS record<br>> of the VM, it should not be a default but only activated through a context<br>> variable, like you mention DNS_HOSTNAME variable is fine. Right now no other<br>> ideas just as simple as possible by doing a reverse lookup on the first/main<br>> IP of the VM should be enough I would say.<br>><br>> I guess the "host" command would be the one which should always be<br>> available. I have seen cases where there was no "dig" installed on a base<br>> linux installation and "nslookup" is sort of fading out. In the worst case<br>> if the host command does not exist nothing happens or it could fallback to<br>> dig.<br>><br>> Greetings,<br>> ML<br>><br>><br>> On Thursday, February 27, 2014 4:27 PM, Javier Fontan<br>> <<a href="mailto:jfontan@opennebula.org" target="_blank">jfontan@opennebula.org</a>> wrote:<br>> On Thu, Feb 27, 2014 at 2:13 PM, ML mail <<a href="mailto:mlnospam@yahoo.com" target="_blank">mlnospam@yahoo.com</a>> wrote:<br>><br>>> You are right I had to define the HOSTNAME variable in the template<br>>> context<br>>> and not as a tag in the already running VM. This means that I can't share<br>>> templates among VMs, which is a bit stupid of course. With this solution<br>>> you<br>>> need one template per VM.<br>><br>> Not exactly. The value of custom variables can be a dynamic one [1] so<br>> for example you can set the hostname to the name of the VM:<br>><br>> SET_HOSTNAME="$NAME"<br>><br>> or even a mix of static and dynamic data:<br>><br>> SET_HOSTNAME="$NIC[IP].<a href="http://domain.com/" target="_blank">domain.com</a>"<br>><br>> [1]<br>> <a href="http://docs.opennebula.org/stable/user/virtual_machine_setup/cong.html#using-template-variables" target="_blank">http://docs.opennebula.org/stable/user/virtual_machine_setup/cong.html#using-template-variables</a><br>><br>>> I see the issue with the HOSTNAME environment variable which is actually<br>>> set<br>>> at bootup of Linux so no problem with me for using a name such as<br>>> SET_HOSTNAME like you suggest.<br>><br>> Good, I'll go with this.<br>><br>>> What do you think about having that same script also defining the hostname<br>>> dynamically (if none was defined with the SET_HOSTNAME context variable)<br>>> based on a DNS reverse lookup if the IP address of the VM has a PTR<br>>> record?<br>><br>> I think it's a nice feature but it should only be set if the users<br>> asks for it. For example, if some VM has a hardcoded hostname a user<br>> does not expect it to be changed in case SET_HOSTNAME is not defined.<br>> Another variable can be added like DNS_HOSTNAME=yes or even better,<br>> specifying the IP where to get the name from:<br>><br>> DNS_HOSTNAME="$NIC[IP, NETWORK=\"Public\"]"<br>><br>> Any better idea?<br>><br>> I'm not sure which command to use to do the reverse lookup. One that<br>> is in most of the distributions like host, nslookup or dig.<br>><br>> Cheers<br>><br>>><br>>><br>>><br>>> On Thursday, February 27, 2014 12:27 PM, Javier Fontan<br>>> <<a href="mailto:jfontan@opennebula.org" target="_blank">jfontan@opennebula.org</a>> wrote:<br>>> Hi,<br>>><br>>> ML, I think you should add it in the template context section, custom<br>>> variables.<br>>><br>>> I am adding scripts to configure the hostname in the context phase.<br>>> These are simple scripts (one for rpm and other for deb based distros)<br>>> that do just what you've commented, call hostname and modify the conf<br>>> file. [1]<br>>><br>>> I've just found a problem with it and it is calling the configuration<br>>> variable "HOSTNAME". The shell automatically sets HOSTNAME and even if<br>>> we don't specify it so it's a bit tricky to check wether the user<br>>> intents to configure the hostname or leave it as it is.<br>>><br>>> I am proposing to use the custom variable "SET_HOSTNAME" to configure<br>>> the host name. What do you think?<br>>><br>>> Concerning the addition of scripts in the context package, there is a<br>>> guide in both the documentation [2] and the source code [3] on how to<br>>> create custom packages. Having the required dependencies it's fairly<br>>> easy to add or modify the configuration script you may need.<br>>><br>>> Cheers<br>>><br>>> [1] <a href="http://dev.opennebula.org/issues/2453" target="_blank">http://dev.opennebula.org/issues/2453</a><br>>> [2]<br>>><br>>> <a href="http://docs.opennebula.org/stable/user/virtual_machine_setup/cong.html#generating-custom-contextualization-packages" target="_blank">http://docs.opennebula.org/stable/user/virtual_machine_setup/cong.html#generating-custom-contextualization-packages</a><br>>> [3]<br>>><br>>> <a href="https://github.com/OpenNebula/one/tree/master/share/scripts/context-packages" target="_blank">https://github.com/OpenNebula/one/tree/master/share/scripts/context-packages</a><br>>><br>>> On Thu, Feb 27, 2014 at 8:02 AM, ML mail <<a href="mailto:mlnospam@yahoo.com" target="_blank">mlnospam@yahoo.com</a>> wrote:<br>>>> Regarding the hostname script that's exactly what I did, I also tried to<br>>>> redeploy this persistent image. Where exactly did you set the HOSTNAME<br>>>> variable? I have setted it in the tags of that specific VM (where I would<br>>>> also add the SSH_PUBLIC_KEY variable). But that might be wrong?<br>>>><br>>>> Regards,<br>>>> ML<br>>>><br>>>><br>>>> On Thursday, February 27, 2014 2:47 AM, "Campbell, Bill"<br>>>> <<a href="mailto:bcampbell@axcess-financial.com" target="_blank">bcampbell@axcess-financial.com</a>> wrote:<br>>>> For item 1, no that should do it, just make sure it's executable and it<br>>>> should run. (the vmcontext init.d script will run all scripts in the<br>>>> /etc/one-context.d directory in order). I set this up for Ubuntu, but<br>>>> I'm<br>>>> pretty sure Debian is the same when it comes to setting the hostname.<br>>>> You<br>>>> mention you reboot the VM, you may have to redeploy (as the context<br>>>> script<br>>>> is already generated from your previous deployment package).<br>>>><br>>>> For item 2, you could include it in your base image, or in the example<br>>>> provided, add it to the files repository along with that init.sh script,<br>>>> and<br>>>> then assign both files to the template. This way the files will be<br>>>> included<br>>>> with the context information, will copy the ##-script over to the<br>>>> instance,<br>>>> and restart the vmcontext service.<br>>>><br>>>> ________________________________<br>>>> From: "ML mail" <<a href="mailto:mlnospam@yahoo.com" target="_blank">mlnospam@yahoo.com</a>><br>>>> To: "users" <<a href="mailto:users@lists.opennebula.org" target="_blank">users@lists.opennebula.org</a>><br>>>> Sent: Wednesday, February 26, 2014 11:12:08 AM<br>>>> Subject: Re: [one-users] ONE context package<br>>>><br>>>> Hi Bill,<br>>>><br>>>> Thanks for your answer and example scripts. I have a few more questions<br>>>> or<br>>>> issues regarding your examples:<br>>>><br>>>> - I tried out your small hostname script which I have copied on my Debian<br>>>> 7<br>>>> VM under /etc/one-context.d/98-hostname. I have then set in my VM a tag<br>>>> called HOSTNAME with a value and rebooted the VM. Unfortunately the<br>>>> hostname<br>>>> did not get changed. Did I miss something here?<br>>>><br>>>> - I suppose I would have to re-create the one-context package manually if<br>>>> I<br>>>> would like to include the aforementioned 98-hostname script in the<br>>>> official<br>>>> one-context package, correct? or I could manually copy it into my image<br>>>> before deploying it?<br>>>><br>>>> Regards,<br>>>> ML<br>>>><br>>>><br>>>><br>>>> On Wednesday, February 26, 2014 3:08 PM, "Campbell, Bill"<br>>>> <<a href="mailto:bcampbell@axcess-financial.com" target="_blank">bcampbell@axcess-financial.com</a>> wrote:<br>>>> We don't have the automatic lookup from DNS (that would rely on the DNS<br>>>> record being created first prior to VM deployment), but we use a script<br>>>> that<br>>>> is placed in our base images /etc/one-context.d/ directory that does this<br>>>> (which relies on option 2 as you mention below, a HOSTNAME context<br>>>> variable):<br>>>><br>>>> #!/bin/bash<br>>>><br>>>> if [ -f /mnt/context.sh ]; then<br>>>> . /mnt/context.sh<br>>>> else<br>>>> exit 0<br>>>> fi<br>>>> hostname $HOSTNAME<br>>>> echo $HOSTNAME > /etc/hostname<br>>>><br>>>> exit 0<br>>>><br>>>> The above example is for our Ubuntu instances, so it may need to be<br>>>> modified<br>>>> for RHEL or SUSE based virtuals, if that's what you use.<br>>>><br>>>> In addition, if using 4.4, use the files datastore and create an<br>>>> 'init.sh'<br>>>> script that can then load up additional files that you assign to the<br>>>> template (so you don't need to manually update each image). We use an<br>>>> init.sh script like this to inject new configuration/contextualization<br>>>> options so we don't need to update our base image very often:<br>>>><br>>>><br>>>> #!/bin/sh<br>>>> #<br>>>> # OpenNebula Init Script<br>>>> #<br>>>> # init.sh<br>>>> #<br>>>> # Copies additional context scripts to the appropriate directory<br>>>> #<br>>>> ## Set environment<br>>>> SOURCE=/mnt<br>>>> DEST=/etc/one-context.d<br>>>><br>>>> if [ -f /etc/redhat-release ]; then<br>>>> OSVERSION=RHEL<br>>>> else<br>>>> OSVERSION=UBUNTU<br>>>> fi<br>>>> if [ -f /usr/bin/rsync ]; then<br>>>> echo "Applying additional contextualization scripts..."<br>>>> else<br>>>> if [ "$OSVERSION" != "UBUNTU" ]; then<br>>>> yum -y install rsync<br>>>> else<br>>>> apt-get update && apt-get -y install rsync<br>>>> fi<br>>>> fi<br>>>><br>>>> ## Copy Files. This will IGNORE any *.sh files in the source/destination<br>>>> directories, as all context scripts<br>>>> ## should NOT have the .sh extension.<br>>>> for i in $(ls $SOURCE --ignore=*.sh)<br>>>> do<br>>>> if [ -f $DEST/$i ]; then<br>>>> echo "$i exists in context directory. Skipping..."<br>>>> else<br>>>> rsync -au $SOURCE/$i /etc/one-context.d/<br>>>> chown root.root /etc/one-context.d/*<br>>>> chmod 700 /etc/one-context.d/*<br>>>> service vmcontext restart<br>>>> fi<br>>>> done<br>>>> exit 0<br>>>><br>>>> This will check the OS Version and install the appropriate package. It<br>>>> will<br>>>> NOT copy any file that has the .sh extension, but if you follow the<br>>>> context<br>>>> script standard of ##-<scriptname> then you can add additional context<br>>>> upon<br>>>> deployment. Rudimentary, sure, but works well enough for us.<br>>>><br>>>><br>>>> ________________________________<br>>>> From: "ML mail" <<a href="mailto:mlnospam@yahoo.com" target="_blank">mlnospam@yahoo.com</a>><br>>>> To: <a href="mailto:users@lists.opennebula.org" target="_blank">users@lists.opennebula.org</a><br>>>> Sent: Wednesday, February 26, 2014 5:39:46 AM<br>>>> Subject: [one-users] ONE context package<br>>>><br>>>> Hi,<br>>>><br>>>> I am very happy with the ONE context package for automated<br>>>> contextualization<br>>>> on Debian and CentOS but I miss one feature: automatically and manually<br>>>> setting the hostname of the VM.<br>>>><br>>>> Basically it would be great to have the following two options:<br>>>><br>>>> - automatically set the hostname of the VM based doing a reverse DNS<br>>>> lookup<br>>>> on the IP address, for example I have as reverse DNS entry<br>>>> "<a href="http://one-vm-1-0-16-172.mydomain.com/" target="_blank">one-vm-1-0-16-172.mydomain.com</a>" then the hostname of my VM would be<br>>>> automatically set to "one-vm-1-0-16-172".<br>>>> - using a HOSTNAME tag in the VM to manually enter a hostname and<br>>>> overriding<br>>>> the automatic hostname attribution described above<br>>>><br>>>> What do you think?<br>>>><br>>>> Regards,<br>>>> ML<br>>>><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</a><br>>>><br>>>><br>>>> NOTICE: Protect the information in this message in accordance with the<br>>>> company's security policies. If you received this message in error,<br>>>> immediately notify the sender and destroy all copies.<br>>>><br>>>><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</a><br>>><br>>>><br>>>><br>>>><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</a><br>>>><br>>>><br>>>> NOTICE: Protect the information in this message in accordance with the<br>>>> company's security policies. If you received this message in error,<br>>>> immediately notify the sender and destroy all copies.<br>>>><br>>>><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</a><br>>>><br>>>><br>>>><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</a><br>>><br>>>><br>>><br>>><br>>><br>>> --<br>>> Javier Fontán Muiños<br>>> Developer<br>>> OpenNebula - The Open Source Toolkit for Data Center Virtualization<br>>> <a href="http://www.opennebula.org/" target="_blank">www.OpenNebula.org</a> | @OpenNebula | <a href="http://github.com/jfontan" target="_blank">github.com/jfontan</a> <o:p></o:p></span></p><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><br>><br>>><br>><br>><br>><br>> --<br>> Javier Fontán Muiños<br>> Developer<br>> OpenNebula - The Open Source Toolkit for Data Center Virtualization<br>> <a href="http://www.opennebula.org/" target="_blank">www.OpenNebula.org</a> | @OpenNebula | <a href="http://github.com/jfontan" target="_blank">github.com/jfontan</a><br>><br>><br><br><br><br>-- <br>Javier Fontán Muiños<br>Developer<br>OpenNebula - The Open Source Toolkit for Data Center Virtualization<br><a href="http://www.opennebula.org/" target="_blank">www.OpenNebula.org</a> | @OpenNebula | <a href="http://github.com/jfontan" target="_blank">github.com/jfontan</a><o:p></o:p></span></p></div><p class=MsoNormal style='margin-bottom:12.0pt;background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p></div></div></div></div></div></div></div></div></div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><br><br clear=all><o:p></o:p></span></p><div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p></div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'>-- <br>Javier Fontán Muiños<br>Developer<br>OpenNebula - The Open Source Toolkit for Data Center Virtualization<br><a href="http://www.opennebula.org/" target="_blank">www.OpenNebula.org</a> | @OpenNebula | <a href="http://github.com/jfontan" target="_blank">github.com/jfontan</a> <o:p></o:p></span></p></div><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><br><br><o:p></o:p></span></p><pre style='background:white'><span style='color:black'>_______________________________________________<o:p></o:p></span></pre><pre style='background:white'><span style='color:black'>Users mailing list<o:p></o:p></span></pre><pre style='background:white'><span style='color:black'><a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><o:p></o:p></span></pre><pre style='background:white'><span style='color:black'><a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><o:p></o:p></span></pre></blockquote><p class=MsoNormal style='background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt;background:white'><span style='font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p></div></div></div></div></div></div>
<br><html><body><b>NOTICE: Protect the information in this message in accordance with the company's security policies. If you received this message in error, immediately notify the sender and destroy all copies.</b></body></html>
<br></body></html>