I forgot to mention that you can also use the CLI to add the network contextualization. When creating the template using parameters add "--net_context", for example:
$ onetemplate create --name "some name" --cpu 1 --memory 512 --disk centos --nic public --net_context --ssh ssh_keys/test.pub http://opennebula.org/doc/4.0/cli/onetemplate.1.html On Mon, Apr 22, 2013 at 1:14 PM, Javier Fontan <jfon...@opennebula.org> wrote: > It seems that you have the context packages installed in the VM but > you are not adding contextualization variables to the VM. When there > are no contextualization parameters the context packages will fallback > to default values. For example, the netmask will be /24. > > You can get more information on how to do that manually in the context > doc [1]. From Sunstone you can also check the network > contextualization checkbox when creating the template, that option > will add the variables needed to the template. > > [1] http://opennebula.org/documentation:rel4.0:context_overview > > On Sun, Apr 21, 2013 at 8:41 PM, Jon <three1...@gmail.com> wrote: >> Hello All, >> >> First the great news, it seems that the OpenVSwitch bug has been resolved: >> >>>> Sun Apr 21 11:49:37 2013 [VMM][I]: post: Executed "sudo >>>> /usr/bin/ovs-ofctl add-flow ovsbr0 >>>> in_port=24,dl_src=02:00:44:47:83:46,priority=40000,actions=normal". >>>> Sun Apr 21 11:49:37 2013 [VMM][I]: post: Executed "sudo >>>> /usr/bin/ovs-ofctl add-flow ovsbr0 in_port=24,priority=39000,actions=drop". >> >> This is awesome, as virtual machines deploy correctly now; I'm one step >> closer to getting a running OpenNebula deployment. >> >> However, it seems that OpenNebula is not configuring the network quite >> right, I've assigned a /28 to my OpenNebula server, 8.8.8.65/28, and when I >> assign an IP to a VM, the VM configures the network as a /24 >> >> eth0 Link encap:Ethernet HWaddr 02:00:44:47:83:46 >> inet addr:8.8.8.8.70 Bcast:8.8.8.8.255 Mask:255.255.255.0 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:6358 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:72 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:385057 (376.0 KiB) TX bytes:6403 (6.2 KiB) >> Interrupt:11 Base address:0xc000 >> >> So my question is, how do I configure the network so it uses the correct >> subnet? >> >> I've configured everything so far directly via SunStone. >> >> Here's my VM template: >> >>>> oneadmin@loki:~$ onetemplate show template-4 >>>> TEMPLATE 4 INFORMATION >>>> ID : 4 >>>> NAME : template-4 >>>> USER : oneadmin >>>> GROUP : oneadmin >>>> REGISTER TIME : 03/28 02:04:14 >>>> >>>> PERMISSIONS >>>> OWNER : um- >>>> GROUP : --- >>>> OTHER : --- >>>> >>>> TEMPLATE CONTENTS >>>> CPU="0.5" >>>> DISK=[ >>>> IMAGE_ID="4" ] >>>> GRAPHICS=[ >>>> LISTEN="0.0.0.0", >>>> TYPE="VNC" ] >>>> MEMORY="1024" >>>> NIC=[ >>>> NETWORK_ID="0" ] >>>> REQUIREMENTS="ID=\"0\"" >>>> UNDEFINED="2.00" >>>> VCPU="2" >> >> _______________________________________________ >> Users mailing list >> Users@lists.opennebula.org >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >> > > > > -- > Javier Fontán Muiños > Project Engineer > OpenNebula - The Open Source Toolkit for Data Center Virtualization > www.OpenNebula.org | jfon...@opennebula.org | @OpenNebula -- Javier Fontán Muiños Project Engineer OpenNebula - The Open Source Toolkit for Data Center Virtualization www.OpenNebula.org | jfon...@opennebula.org | @OpenNebula _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org