<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 09/13/2013 07:46 PM, Nelson Peixoto
wrote:<br>
</div>
<blockquote cite="mid:002d01ceb0a9$1c867ae0$559370a0$@fiocruz.br"
type="cite">
<pre wrap="">Hi Olivier,
Thanks for the reply. Anyway... about those variables, is there such a thing
as a reference guide for them? </pre>
</blockquote>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="http://opennebula.org/documentation:rel4.2:cong">http://opennebula.org/documentation:rel4.2:cong</a><br>
<br>
you can define your own variables in the template:<br>
<br>
myvar = "something"<br>
<br>
or use existing variables from network and image template with
keywords from each template.<br>
<blockquote cite="mid:002d01ceb0a9$1c867ae0$559370a0$@fiocruz.br"
type="cite">
<pre wrap="">I see there are several ways to use a
variable inside a VM template but it is not clear which are them and what
values can be applied onto them.
The question about the hosts is mainly because so far I could not manage to
understand the interaction in between OpenNebula virtual networks and each
KVM installation in the hosts, and how to deal with the routes so that each
VM can "see" each other.
Right now, I have two hosts for the VM's, both of them with a KVM
installation. By default, KVM sets up a virbr0 interface with 192.168.122.1
network address.
I wanted to be able to create a single ranged virtual newtork (with a lease
pool), which could be used by both of the hosts when instantiating a VM, so
that I could have more than 255 IP addresses for VM's at a time.</pre>
</blockquote>
host with a bridge will virtualize the VM networks. Nothing special
to do.<br>
Each VM will have its own IP from the network you defined help with
the context (for example with
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<pre class="code" style="padding: 0.5em; border: 1px dashed rgb(85, 85, 85); color: rgb(85, 85, 85); background-color: rgb(245, 245, 245); line-height: 18px; margin: 10px; overflow: auto !important; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: left; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">ip_private = "$NIC[IP, NETWORK=\"public net\"]",</pre>
and the open-nebula context package) or with a DHCP server if you
have one.<br>
<br>
In opennebula you create a network with an IP range. When you launch
a VM, it will pick up a free IP from the range and setup the NIC[IP]
context variable. However openebula does not provide a DHCP. To
setup the IP on the VM, it is done either with the boot context
scripts, either with an external DHCP server that match the range of
MAC address defined in your network.<br>
<br>
<blockquote cite="mid:002d01ceb0a9$1c867ae0$559370a0$@fiocruz.br"
type="cite">
<pre wrap="">
I need to have, for example, 400 VMs instantiated using a single ranged
virtual network, supported by these two hosts. Is it possible? If so, how
should I proceed? Or if not, does that mean I will have to create several
virtual networks, each one limited to x.x.x.1-x.x.x.255 VM's at a time, and
then create several templates for each different virtual networks?
</pre>
</blockquote>
I think you can define a range IP network with a mask of class B (
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="http://opennebula.org/documentation:rel4.2:vnet_template">http://opennebula.org/documentation:rel4.2:vnet_template</a>)
<blockquote cite="mid:002d01ceb0a9$1c867ae0$559370a0$@fiocruz.br"
type="cite">
<pre wrap="">
I do not know if I am being clear in the explanation... thanks for the
comprehension...
Best regards,
Nelson Peixoto.
I later created a virtual network in OpenNebula, ranged type, 192.168.
-----Mensagem original-----
De: Olivier Sallou [<a class="moz-txt-link-freetext" href="mailto:olivier.sallou@irisa.fr">mailto:olivier.sallou@irisa.fr</a>]
Enviada em: sexta-feira, 13 de setembro de 2013 11:27
Para: <a class="moz-txt-link-abbreviated" href="mailto:nelsonpeixoto@fiocruz.br">nelsonpeixoto@fiocruz.br</a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:users@lists.opennebula.org">users@lists.opennebula.org</a>
Assunto: Re: [one-users] Virtual Machine contextualization variables
On 09/12/2013 05:36 PM, <a class="moz-txt-link-abbreviated" href="mailto:nelsonpeixoto@fiocruz.br">nelsonpeixoto@fiocruz.br</a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Dear friends,
It is my first post in here. I have been trying out OpenNebula 3.2 and
I have a doubt on using context variables.
I have two hosts for the VMs and i want to be able to capture, via
context variable, for each VM I instantiate, which host is it on (IP or
</pre>
</blockquote>
<pre wrap="">FQDN).
</pre>
<blockquote type="cite">
<pre wrap="">
I managed to find this page
(<a class="moz-txt-link-freetext" href="http://opennebula.org/documentation:archives:rel3.2:template">http://opennebula.org/documentation:archives:rel3.2:template</a>) with a
set of instructions on how to use context variables and a link to some
of the possible values, but I could not find any hint on how to catch
any information on which host is the VM running on.
I want to be able to capture this information and later on use this
data on the VM boot, in order to add some specific network configurations.
So, is there a place with a broader context variable reference guide
or is there a way to catch that info?
</pre>
</blockquote>
<pre wrap="">Hi,
you can't set (yet) any dynamic context variable. All you can do is to set
some "static" variables in the template of your VM.
Via Hooks, you may be able to catch the information (getting all context
data of the VM), and register it in a db/file/... then your VM, once booted,
could try to access this data.
However, your VM network should not depend on the host running the VM.
Regards
Olivier
</pre>
<blockquote type="cite">
<pre wrap="">
Thanks in advance,
Nelson Peixoto.
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opennebula.org">Users@lists.opennebula.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a>
</pre>
</blockquote>
<pre wrap="">
--
Olivier Sallou
IRISA / University of Rennes 1
Campus de Beaulieu, 35000 RENNES - FRANCE
Tel: 02.99.84.71.95
gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83
D3B9 5204 6335 D26D 78DC 68DB 326D 8438
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Olivier Sallou
IRISA / University of Rennes 1
Campus de Beaulieu, 35000 RENNES - FRANCE
Tel: 02.99.84.71.95
gpg key id: 4096R/326D8438 (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
</pre>
</body>
</html>