<p dir="ltr">Hello Javier,</p>
<p dir="ltr">I see, so the network configuration is handled by VM contextualization not the virtual network config. Got it. Thanks for the links to the docs.</p>
<p dir="ltr">How does that affect hot plug networking? E.g. is the new nic manually configured by the VM user, or can a running VM be contextualized?</p>
<p dir="ltr">Thanks Again, everyone has been so helpful. I really appreciate it.<br>
Jon A</p>
<div class="gmail_quote">On Apr 22, 2013 5:21 AM, "Javier Fontan" <<a href="mailto:jfontan@opennebula.org">jfontan@opennebula.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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">jfontan@opennebula.org</a>> 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">three18ti@gmail.com</a>> wrote:<br>
>> Hello All,<br>
>><br>
>> First the great news, it seems that the OpenVSwitch bug has been 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 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 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 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">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">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">jfontan@opennebula.org</a> | @OpenNebula<br>
</blockquote></div>