[one-users] DHCP and OpenNebula
Ruben S. Montero
rsmontero at opennebula.org
Fri Jul 12 16:05:25 PDT 2013
Hi Michael
Just to double check. Could it be that the name of the vSwitch/port groups
in your ESX are not properly set in the Virtual Network template in
opennebula?.
You should be able to use the dummy drivers as long as the BRIDGE attribute
of the virtual network matches an existing **port group** in the ESX's. I
guess that if you try to add a NIC to a non exisiting port group it does
not show up in the guest?
If you want to use the dynamic mode (vmware network) the BRIDGE is the
**vSwitch** name in the ESX, where a dynamic port group will be created.
Cheers
Ruben
On Fri, Jul 12, 2013 at 10:48 PM, Michael Curran <
michael.curran at connectsolutions.com> wrote:
> Spoke too soon ---****
>
> ** **
>
> Yes the NIC is now visible to the OS, but it is no longer trying to join
> the VM Network , and is instead trying to create a one-pg-3 (for network3)
> which does not exist on the ESXi hosts****
>
> ** **
>
> I would assume this means it cannot create a virtual network on the ESX
> hosts, and using the dummy network definition adds the NIC on the already
> created virtual network****
>
> ** **
>
> But as noted in previous comments – there is no ability to find the NIC
> with the dummy network defined****
>
> ** **
>
> Hoping there is information about not being able to create the network in
> the ESXi hosts that could resolve this.****
>
> ** **
>
> Michael Curran | connectsolutions | Lead Network Architect****
>
> Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com****
>
> ** **
>
> *From:* Michael Curran
> *Sent:* Friday, July 12, 2013 3:42 PM
> *To:* Michael Curran; Users OpenNebula
>
> *Subject:* RE: [one-users] DHCP and OpenNebula****
>
> ** **
>
> RESOLVED!!!****
>
> ** **
>
> When setting up the networks, I was following some steps for DHCP that
> suggested using the Dummy driver for networking and vmware with dhcp ****
>
> ** **
>
> I removed the hosts from the cluster and re-added them , but defined the
> network as vmware and now it recognizes the network card!! ****
>
> ** **
>
> Michael Curran | connectsolutions | Lead Network Architect****
>
> Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com****
>
> ** **
>
> *From:* users-bounces at lists.opennebula.org [
> mailto:users-bounces at lists.opennebula.org<users-bounces at lists.opennebula.org>]
> *On Behalf Of *Michael Curran
> *Sent:* Friday, July 12, 2013 2:38 PM
> *To:* Users OpenNebula
> *Subject:* Re: [one-users] DHCP and OpenNebula****
>
> ** **
>
> Hello again,****
>
> ** **
>
> As noted below I can clone a windows VMDK – and buid it with an e1000
> network card attached (screenshots showing the HW attached in vSphere
> attached)****
>
> ** **
>
> I tried to modify the clone image to have the drivers from Intel® Pro
> 1000/MT on the file, but they don’t install because they don’t find the
> network card attached****
>
> ** **
>
> See screen shots for what the network card looks like on a clean VM clone*
> ***
>
> ** **
>
> Michael Curran | connectsolutions | Lead Network Architect****
>
> Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com****
>
> ** **
>
> *From:* users-bounces at lists.opennebula.org [
> mailto:users-bounces at lists.opennebula.org<users-bounces at lists.opennebula.org>]
> *On Behalf Of *Michael Curran
> *Sent:* Friday, July 12, 2013 9:43 AM
> *To:* Users OpenNebula
> *Subject:* Re: [one-users] DHCP and OpenNebula****
>
> ** **
>
> Hello – ****
>
> ** **
>
> I found that the NIC definition goes into the onetemplate template
> settings that I am using and it is now adding the NIC to the hardware as
> e1000****
>
> ** **
>
> However when the Windows VM boots – it does not see ANY hardware NIC’s****
>
> ** **
>
> I have tried the following steps****
>
> ** **
>
> **· **Removed NIC and RE-added via vSphere****
>
> **· **Re-installed vmwaretools (it is already installed in the
> cloned VM, but couldn’t hurt)****
>
> **· **Removed NIC and Re-added it again via vSphere****
>
> ** **
>
> Still no luck in finding the hardware NIC inside the VM – any one else
> experience this issue?****
>
> ** **
>
> Michael Curran | connectsolutions | Lead Network Architect****
>
> Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com****
>
> ** **
>
> *From:* Michael Curran
> *Sent:* Thursday, July 11, 2013 3:48 PM
> *To:* Michael Curran
> *Cc:* Users OpenNebula
> *Subject:* RE: [one-users] DHCP and OpenNebula****
>
> ** **
>
> I tried to use this template to build a VM with a Network NIC – ****
>
> ** **
>
> Does this look correct for NIC assignment within VMware?****
>
> ** **
>
> NAME="myvm-win"****
>
> CPU=1****
>
> MEMORY=512****
>
> DISK=[ IMAGE_ID=13 ]****
>
> NIC=[NETWORK_ID="1",MODEL="E1000"]****
>
> ** **
>
> Has anyone else done NIC assignments with Windows Deployments in Vmware? I
> can get the Windows VM up and running , the NIC shows up in the settings
> (as flexible) with the sunstone GUI****
>
> ** **
>
> But when I open the VM it has no NIC’s inside of it? I choose the dummy
> network driver – maybe that’s not what I needed?****
>
> ** **
>
> Michael Curran | connectsolutions | Lead Network Architect****
>
> Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com****
>
> ** **
>
> *From:* users-bounces at lists.opennebula.org [
> mailto:users-bounces at lists.opennebula.org<users-bounces at lists.opennebula.org>]
> *On Behalf Of *Michael Curran
> *Sent:* Thursday, July 11, 2013 12:19 PM
> *To:* Carlo Daffara
> *Cc:* Users OpenNebula
> *Subject:* Re: [one-users] DHCP and OpenNebula****
>
> ** **
>
> So – ****
>
> ** **
>
> I configured a Virtual Network in OpenNebula GUI (sunstone) and it now
> adds NIC settings to the Windows VM****
>
> ** **
>
> ethernet0.present = "true"****
>
> ethernet0.networkName = "VM Network"****
>
> ethernet0.connectionType = "bridged"****
>
> ethernet0.addressType = "static"****
>
> ethernet0.address = "02:00:c0:a8:fb:01"****
>
> ethernet0.checkMACAddress = "false"****
>
> ** **
>
> But it does not set the ****
>
> ** **
>
> ethernet0.virtualDev =”{e1000|vmxnet3|flexible}” so the VM does not see
> any NICs****
>
> ** **
>
> ** **
>
> Michael Curran | connectsolutions | Lead Network Architect****
>
> Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com****
>
> ** **
>
> *From:* users-bounces at lists.opennebula.org [
> mailto:users-bounces at lists.opennebula.org<users-bounces at lists.opennebula.org>]
> *On Behalf Of *Carlo Daffara
> *Sent:* Thursday, July 11, 2013 7:14 AM
> *Cc:* Users OpenNebula
> *Subject:* Re: [one-users] DHCP and OpenNebula****
>
> ** **
>
> It works exactly like a physical server- if there is network visibility
> (same vlan or default bridge) the booted VM will get its address from DHCP.
> We use this configuration (thus ignoring the opennebula-assigned IP) in
> several customers' networks, especially when the VM cones from
> virtualization of user desktops.
> Cheers
> Carlo Daffara****
>
> Il giorno 11/lug/2013 12:54, "Michael Curran" <
> michael.curran at connectsolutions.com> ha scritto:****
>
> But in that case, I would be assigning IP’s to hosts instead of them
> booting up and just using DHCP to get the IP address****
>
> ****
>
> I want to just assign the NIC and let the OS obtain an IP from DHCP
> instead, on system boot. ****
>
> ****
>
> Still reading the documentation, but not seeing a method for it yet.****
>
> ****
>
> Michael Curran | connectsolutions | Lead Network Architect****
>
> Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com****
>
> ****
>
> *From:* users-bounces at lists.opennebula.org [mailto:
> users-bounces at lists.opennebula.org] *On Behalf Of *Pentium100
> *Sent:* Thursday, July 11, 2013 2:24 AM
> *To:* users at lists.opennebula.org
> *Subject:* Re: [one-users] DHCP and OpenNebula****
>
> ****
>
> From what I understand, OpenNebula encodes the IP in the MAC, for example,
> the VM with assigned IP 10.0.0.2 would get a MAC 02:00:0a:00:00:02. Just
> create an IP:MAC list for the DHCP server and it will work. ****
>
> host a10-0-0-1 { hardware ethernet 02:00:0a:00:00:01; fixed address
> 10.0.0.1; }
> host a10-0-0-2 { hardware ethernet 02:00:0a:00:00:02; fixed address
> 10.0.0.2; }****
>
> and so on...****
>
> ****
>
> On Wed, Jul 10, 2013 at 6:25 PM, Michael Curran <
> michael.curran at connectsolutions.com> wrote:****
>
> Can I leverage an existing DHCP server to assign IP’s to a host , and
> just use OpenNebula to assign the NIC?****
>
> ****
>
> Michael Curran | connectsolutions | Lead Network Architect****
>
> Phone 614.568.2285 | Mobile 614.403.6320 | www.connectsolutions.com****
>
> ****
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org****
>
> ****
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org****
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
--
--
Join us at OpenNebulaConf2013 in Berlin, 24-26 September, 2013
--
Ruben S. Montero, PhD
Project co-Lead and Chief Architect
OpenNebula - The Open Source Solution for Data Center Virtualization
www.OpenNebula.org | rsmontero at opennebula.org | @OpenNebula
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130713/5a082ca4/attachment-0002.htm>
More information about the Users
mailing list