Step 1 – What features are missing?
This used to be a bigger problem than it is today. The only things we are missing at this point with the vCenter Server appliance are Linked Mode, vCenter Server Heartbeat (EoA) and SQL Server support. If you need any of these features, its game over, stick to the vCenter Server on Windows.
This used to be a bigger problem than it is today. The only things we are missing at this point with the vCenter Server appliance are Linked Mode, vCenter Server Heartbeat (EoA) and SQL Server support. If you need any of these features, its game over, stick to the vCenter Server on Windows.
Step 2 – Figure out the scale limits.The embedded database that is preinstalled with the vCenter Server appliance will support an inventory size of up to 100 vSphere hosts and/or 3,000 Virtual Machines when sized appropriately. If your scale requirements are higher, is anexternal database an option? You can use an external database to meet the vCenter maximum scale of up to 1,000 vSphere hosts and/or 10,000 Virtual Machines. However the only external supported database with the vCenter Server appliance is Oracle. If you are a SQL Server shop, the vCenter Server appliance is not for you.
Step 3 – Do you have any operational/environmental/regulatory requirements?
The vCenter Server appliance is delivered on a SUSE distribution, however VMware does not update the OS level patches and hotfixes as they become available, VMware publishes release updates containing the accumulated patches and hotfixes and in the case of vCenter Server, this could be 6 months out (we do deliver critical security patches (ie Heartbleed). Other considerations include 3rd party agents, tweaking Linux settings and removing things aren’t supported. Backup requirements, too, are sometimes a challenge (if, for instance, the database team requires that databases be backed up separately to the virtual appliance).
The vCenter Server appliance is delivered on a SUSE distribution, however VMware does not update the OS level patches and hotfixes as they become available, VMware publishes release updates containing the accumulated patches and hotfixes and in the case of vCenter Server, this could be 6 months out (we do deliver critical security patches (ie Heartbleed). Other considerations include 3rd party agents, tweaking Linux settings and removing things aren’t supported. Backup requirements, too, are sometimes a challenge (if, for instance, the database team requires that databases be backed up separately to the virtual appliance).
Step 4 – Using the appliance, today, still requires a certain amount of Linux expertise.
Many customers assume that we’re further down the “lock it down and hide Linux” road than we actually are. I’ve spoken to customers who were excited about moving to the vCenter Server appliance because “we don’t have to worry about the OS, any more.” This may not be true if you get into a troubleshooting scenario or require additional configuration settings.
Many customers assume that we’re further down the “lock it down and hide Linux” road than we actually are. I’ve spoken to customers who were excited about moving to the vCenter Server appliance because “we don’t have to worry about the OS, any more.” This may not be true if you get into a troubleshooting scenario or require additional configuration settings.
Step 5 – Migrating to the vCenter Server appliance
Ok so you may have survived the first few steps and ready to adopt the vCenter Server appliance but getting to it maybe more of a challenge. We do not have any migration/data tools available to move your vCenter Server on Windows to the vCenter Server appliance. You will have to deploy a fresh vCenter Server appliance and manually recreate the configuration and manually move the vSphere hosts over to the new vCenter Server appliance. Do you have any auditory requirements? historical data will be lost with the manual migration process and vCOPs will see the vCenter Server appliance as a new vCenter Server environment. This manual process could be eased with the use of PowerCLI but unique to each environment. Using an existing vCenter Server database is not an option.
Ok so you may have survived the first few steps and ready to adopt the vCenter Server appliance but getting to it maybe more of a challenge. We do not have any migration/data tools available to move your vCenter Server on Windows to the vCenter Server appliance. You will have to deploy a fresh vCenter Server appliance and manually recreate the configuration and manually move the vSphere hosts over to the new vCenter Server appliance. Do you have any auditory requirements? historical data will be lost with the manual migration process and vCOPs will see the vCenter Server appliance as a new vCenter Server environment. This manual process could be eased with the use of PowerCLI but unique to each environment. Using an existing vCenter Server database is not an option.
. The kernel configuration is based upon the default RHEL-7 configuration with added functionality enabled as appropriate. The packages are intentionally named kernel-ml so as not to conflict with the RHEL-7 kernels and, as such, they may be installed and updated alongside the regular kernel.