I’ve got a working environment up and running with a KVM host using OpenVSwitch. For images deployed from the Marketplace, I can assign them the network that gives them address space directly on the attached LAN and I can connect / ping / SSH etc. So far so good.
Basically - upload the ISO (I’m using Ubuntu mini 14.04) , create an empty hard disk, create a template with both of those - boot the ISO and then start the installation process to disk. Everything works up until it attempts to contact the ubuntu archive where it fails.
Checking the networking, I find I’m unable to get any ping response - but I can see that a port is created on the host. Opennebula shows that a network address has been assigned.
Has anyone else had issues with networking when installing from ISO media? This may be less of an OpenNebula issue and more of a Ubuntu / KVM / OpenvSwitch problem.
Basically - upload the ISO (I’m using Ubuntu mini 14.04) , create an
empty hard disk, create a template with both of those - boot the ISO
and then start the installation process to disk. Everything works up
until it attempts to contact the ubuntu archive where it fails.
Checking the networking, I find I’m unable to get any ping response -
but I can see that a port is created on the host. Opennebula shows
that a network address has been assigned.
Has anyone else had issues with networking when installing from ISO
media? This may be less of an OpenNebula issue and more of a Ubuntu /
KVM / OpenvSwitch problem.
At my work, we are doing ISO install near every week to check our Ubuntu
derivative install process.
We are using KVM with OpenVswitch.
The only point is that the ISO is not contextualized, so the network
address assigned by OpenNebula is not automatically configured.
We need to configure the network manually or with DHCP during the
install process.
On tty2 during the install process, you can have a shell to check ip
parameters, you should check at least:
I really appreciate that feedback. I think that should point me in the right direction and it explains perfectly why a straight ISO install results in this issue.
I had another look at this and I have a DHCP server on the network that I’m attaching to. However, the virtual network defined in OpenNebula also had a range defined and was applying that IP when starting up the VM. Naturally, as pointed out, this fails because of lack of contextualisation. The mix of the two ends up meaning that the VM fails to get network connectivity.
I fixed it by creating a dedicated startup network with a fixed mac address and a lease of a single fixed IP. On the DHCP server, I mapped that same mac address to the same IP as defined in the startup network in OpenNebula. Once both the DHCP server and OpenNebula were in agreement about the address, I got external network connectivity.
Now I can download the Ubuntu contextualisation package, install it and then turn the thing in to an image.
I’m sure there are better ways of doing this but still, at least it’s working.