<div dir="ltr">Hello All,<div><br></div><div style>Can you please provide some guidance as to what I'm doing wrong.</div><div style><br></div><div style>I've added both, "ETH0_GATEWAY / ETH0_NETMASK" and "NETWORK_ADDRESS / NETWORK_MASK" custom attributes to my virtual network configuration as outlined in the docs I was pointed to: <a href="http://opennebula.org/documentation:rel4.0:cong">http://opennebula.org/documentation:rel4.0:cong</a></div>
<div style><br></div><div style>However, the VM still comes up with a gateway of .1 and netmask of 255.255.255.0</div><div style><br></div><div style>Also, these attributes are not reflected in the running VMs templage:</div>
<div style><br></div><div style><div>CPU="0.5"</div><div>GRAPHICS=[</div><div> LISTEN="0.0.0.0",</div><div> PORT="5953",</div><div> TYPE="VNC" ]</div><div>MEMORY="1024"</div>
<div>NAME="one-53"</div><div>TEMPLATE_ID="4"</div><div>VCPU="2"</div><div>VMID="53"</div><div><br></div><div><br></div><div style>So I'm thinking there's something wrong with my network configuration because the correct network information is not being passed from the virtual network config to the VM config.</div>
<div style><br></div><div style>Can someone point me in the correct direction please?</div><div style><br></div><div style>Thanks,</div><div style>Jon A</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, Apr 22, 2013 at 12:53 PM, Ruben S. Montero <span dir="ltr"><<a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi Jon<div><br></div><div>You may also be interested in using a virtual router. OpenNebula includes a VR appliance that can be easily feed with the virtual networks information through context. This will set up a DHCP server (among other things) to configure the NICs that way....</div>
<div><br></div><div><a href="http://opennebula.org/documentation:rel4.0:router" target="_blank">http://opennebula.org/documentation:rel4.0:router</a><br></div><div><br></div><div>Cheers</div><div><br></div>
<div>
Ruben</div><div><br></div></div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Mon, Apr 22, 2013 at 6:14 PM, Javier Fontan <span dir="ltr"><<a href="mailto:jfontan@opennebula.org" target="_blank">jfontan@opennebula.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The contextualization cdrom is created on VM deployment so I fear you<br>
will have to configure the network interface manually.<br>
<div><div><br>
On Mon, Apr 22, 2013 at 4:00 PM, Jon <<a href="mailto:three18ti@gmail.com" target="_blank">three18ti@gmail.com</a>> wrote:<br>
> Hello Javier,<br>
><br>
> I see, so the network configuration is handled by VM contextualization not<br>
> the virtual network config. Got it. Thanks for the links to the docs.<br>
><br>
> How does that affect hot plug networking? E.g. is the new nic manually<br>
> configured by the VM user, or can a running VM be contextualized?<br>
><br>
> Thanks Again, everyone has been so helpful. I really appreciate it.<br>
> Jon A<br>
><br>
> On Apr 22, 2013 5:21 AM, "Javier Fontan" <<a href="mailto:jfontan@opennebula.org" target="_blank">jfontan@opennebula.org</a>> wrote:<br>
>><br>
>> I forgot to mention that you can also use the CLI to add the network<br>
>> contextualization. When creating the template using parameters add<br>
>> "--net_context", for example:<br>
>><br>
>> $ onetemplate create --name "some name" --cpu 1 --memory 512 --disk<br>
>> centos --nic public --net_context --ssh ssh_keys/test.pub<br>
>><br>
>> <a href="http://opennebula.org/doc/4.0/cli/onetemplate.1.html" target="_blank">http://opennebula.org/doc/4.0/cli/onetemplate.1.html</a><br>
>><br>
>> On Mon, Apr 22, 2013 at 1:14 PM, Javier Fontan <<a href="mailto:jfontan@opennebula.org" target="_blank">jfontan@opennebula.org</a>><br>
>> wrote:<br>
>> > It seems that you have the context packages installed in the VM but<br>
>> > you are not adding contextualization variables to the VM. When there<br>
>> > are no contextualization parameters the context packages will fallback<br>
>> > to default values. For example, the netmask will be /24.<br>
>> ><br>
>> > You can get more information on how to do that manually in the context<br>
>> > doc [1]. From Sunstone you can also check the network<br>
>> > contextualization checkbox when creating the template, that option<br>
>> > will add the variables needed to the template.<br>
>> ><br>
>> > [1] <a href="http://opennebula.org/documentation:rel4.0:context_overview" target="_blank">http://opennebula.org/documentation:rel4.0:context_overview</a><br>
>> ><br>
>> > On Sun, Apr 21, 2013 at 8:41 PM, Jon <<a href="mailto:three18ti@gmail.com" target="_blank">three18ti@gmail.com</a>> wrote:<br>
>> >> Hello All,<br>
>> >><br>
>> >> First the great news, it seems that the OpenVSwitch bug has been<br>
>> >> resolved:<br>
>> >><br>
>> >>>> Sun Apr 21 11:49:37 2013 [VMM][I]: post: Executed "sudo<br>
>> >>>> /usr/bin/ovs-ofctl add-flow ovsbr0<br>
>> >>>> in_port=24,dl_src=02:00:44:47:83:46,priority=40000,actions=normal".<br>
>> >>>> Sun Apr 21 11:49:37 2013 [VMM][I]: post: Executed "sudo<br>
>> >>>> /usr/bin/ovs-ofctl add-flow ovsbr0<br>
>> >>>> in_port=24,priority=39000,actions=drop".<br>
>> >><br>
>> >> This is awesome, as virtual machines deploy correctly now; I'm one step<br>
>> >> closer to getting a running OpenNebula deployment.<br>
>> >><br>
>> >> However, it seems that OpenNebula is not configuring the network quite<br>
>> >> right, I've assigned a /28 to my OpenNebula server, <a href="http://8.8.8.65/28" target="_blank">8.8.8.65/28</a>, and<br>
>> >> when I<br>
>> >> assign an IP to a VM, the VM configures the network as a /24<br>
>> >><br>
>> >> eth0 Link encap:Ethernet HWaddr 02:00:44:47:83:46<br>
>> >> inet addr:8.8.8.8.70 Bcast:8.8.8.8.255 Mask:255.255.255.0<br>
>> >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
>> >> RX packets:6358 errors:0 dropped:0 overruns:0 frame:0<br>
>> >> TX packets:72 errors:0 dropped:0 overruns:0 carrier:0<br>
>> >> collisions:0 txqueuelen:1000<br>
>> >> RX bytes:385057 (376.0 KiB) TX bytes:6403 (6.2 KiB)<br>
>> >> Interrupt:11 Base address:0xc000<br>
>> >><br>
>> >> So my question is, how do I configure the network so it uses the<br>
>> >> correct<br>
>> >> subnet?<br>
>> >><br>
>> >> I've configured everything so far directly via SunStone.<br>
>> >><br>
>> >> Here's my VM template:<br>
>> >><br>
>> >>>> oneadmin@loki:~$ onetemplate show template-4<br>
>> >>>> TEMPLATE 4 INFORMATION<br>
>> >>>> ID : 4<br>
>> >>>> NAME : template-4<br>
>> >>>> USER : oneadmin<br>
>> >>>> GROUP : oneadmin<br>
>> >>>> REGISTER TIME : 03/28 02:04:14<br>
>> >>>><br>
>> >>>> PERMISSIONS<br>
>> >>>> OWNER : um-<br>
>> >>>> GROUP : ---<br>
>> >>>> OTHER : ---<br>
>> >>>><br>
>> >>>> TEMPLATE CONTENTS<br>
>> >>>> CPU="0.5"<br>
>> >>>> DISK=[<br>
>> >>>> IMAGE_ID="4" ]<br>
>> >>>> GRAPHICS=[<br>
>> >>>> LISTEN="0.0.0.0",<br>
>> >>>> TYPE="VNC" ]<br>
>> >>>> MEMORY="1024"<br>
>> >>>> NIC=[<br>
>> >>>> NETWORK_ID="0" ]<br>
>> >>>> REQUIREMENTS="ID=\"0\""<br>
>> >>>> UNDEFINED="2.00"<br>
>> >>>> VCPU="2"<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>
>> > Javier Fontán Muiños<br>
>> > Project Engineer<br>
>> > OpenNebula - The Open Source Toolkit for Data Center Virtualization<br>
>> > <a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:jfontan@opennebula.org" target="_blank">jfontan@opennebula.org</a> | @OpenNebula<br>
>><br>
>><br>
>><br>
>> --<br>
>> Javier Fontán Muiños<br>
>> Project Engineer<br>
>> OpenNebula - The Open Source Toolkit for Data Center Virtualization<br>
>> <a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:jfontan@opennebula.org" target="_blank">jfontan@opennebula.org</a> | @OpenNebula<br>
<br>
<br>
<br>
--<br>
Javier Fontán Muiños<br>
Project Engineer<br>
OpenNebula - The Open Source Toolkit for Data Center Virtualization<br>
<a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:jfontan@opennebula.org" target="_blank">jfontan@opennebula.org</a> | @OpenNebula<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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br></div></div>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
</div>
</blockquote></div><br></div>