VMware announced the availability of vCenter Server 5.0 Update 1b today along with some really good news for the fans of openness:
vCenter Server Appliance Database Support: The DB2 express embedded database provided with the vCenter Server Appliance has been replaced with VMware vPostgres database. This decreases the appliance footprint and reduces the time to deploy vCenter Server further.
Ironically and despite its reference in the release notes, the VMware Product Interoperability Matrix has yet to be updated to include 5.0U1b for reference, so the official impact of an upgrade is as-yet unknown.
Also, couple of new test questions are going to be tricky moving forward as the support for Oracle has been expanded:
- vCenter Server 5.0 Update 1b introduces support for the following vCenter Databases
- Oracle 11g Enterprise Edition, Standard Edition, Standard ONE Edition Release 2 [220.127.116.11] – 64 bit
- Oracle 11g Enterprise Edition, Standard Edition, Standard ONE Edition Release 2 [18.104.22.168] – 32 bit
Besides still not supporting IPv6 and continuing the limitation of 5 hosts and 50 VMs, there is some additional leg work needed to upgrade the vCenter Server Appliance 5.0U1a to U1b as specified in KB2017801:
- Create a new virtual disk with size 20GB and attach it to the vCenter Server Appliance.
- Log in to the vCenter Server Appliance’s console and format the new disk as follows:
- At the command line, type, “echo “- – -” > /sys/class/scsi_host/host0/scan”.
- Type, “parted -s /dev/sdc mklabel msdos”.
- Type, “parted -s /dev/sdc mkpartfs primary ext2 0 22G”.
- Mount the new partition under /storage/db/export:
- Type, “mkdir -p /storage/db/export”.
- Type, “mount /dev/sdc1 /storage/db/export”.
- Repeat the update process.
- You can remove the new disk after the update process finishes successfully and the vCenter Server Appliance is shut down.
SOLORI’s Take: Until the interop matrix is updated, it’s hard to know what you’re getting into with the update (Update: as you can see from Joshua Andrews’ post on SOS tech), but the inclusion of vPostgres – VMware’s vFabric deployment of PostgreSQL 9.1.x – makes taking a look at the “crippled” appliance version a bit more tantalizing. Hopefully, the next release will “unshackle” the vCenter Appliance beyond the 5/50 limitations – certainly vPostgres is up to the task of managing many, many more hosts and VMs (vCD anyone?) Cheers, VMware!