Getting ready for the new Ubuntu LTS release
It looks good, and it feels fast. Rebooting a VM takes 9 seconds, which is faster than ever. No need to schedule maintenance windows any more (not that I did anyway ).
Network interface configuration and DNS resolution
Things have changed. Both interface configuration and name resolution configuration are now done in
/etc/network/interfaces. There is a new flag for autoconfiguration, so no need to echo things to /proc anymore. For our dual stack staticly configured servers the configuration looks like this:
Note that despite the comment on the second line (see interfaces(5)), not everything is explained there. You have to look at resolvconf(8) as well.
There is a bug that effectively overrides the
privext value with what's in /etc/sysctl.d/10-ipv6-privacy.conf. You have to work around it by commenting out the two lines there.
Our setup consists of VMware ESXi 4.1 boxes, and I configured the Precise VMs with a vmxnet3 NIC, and a paravirtualised SCSI hard disk, and the linux-image-virtual kernel.
When it comes to the VMware tools, there are a few options:
1 - Do nothing
This is the simplest approach, and usually my favourite. A freshly installed VM will load a number of VMware modules that apparently are part of the 3.2 kernel these days:
Also, it will load the
I'd say all of this is an improvement over the "do nothing" approach in Lucid, because back then no specific VMware modules would be loaded at all. But now, VCenter still displays "Not installed" as the VMware Tools status...
2 - Distro provided OpenVM-tools
This is slightly more work than the "do nothing" scenario, but it's very easy because everything sits in the Ubuntu repository. To install the OpenVM-tools on a server be sure to leave out the recommended packages, so that you don't end up with tons of unnecessary X-server packages:
open-vm-dkms package takes care of automatically rebuilding modules whenever there is a kernel upgrade. You can see this in action when installing it:
After this there are quite some vm modules loaded:
VCenter now says the VMware Tools status is "Unmanaged" - slightly better than nothing.
3 - VMware provided tools
This is the most work, but it's not too hard.
It basically comes down to:
- in vSphere client: right-click Guest -> Install/Upgrade VMware tools
- In the guest:
mount /dev/cdrom /media/cdrom, then extract the tar.gz
- Install the tools using
I will run some test to see which scenarios allow VCB to make backups.
/sbin/halt doesn't power off any more
bug functionality change appears to have been introduced in 11.10.
Easy workaround: "