Our virtual platform is currently hosted with a company that strangely still uses ESXi 4.0. We have the ability to install RHEL5 from their supplied templates and can make copies of existing VMs with customization such as hostname and IPs; things one would expect a robust hypervisor to support. Unfortunately, this support is not extended to RHEL6. We can make identical copies and then modify them to the configuration we need, but the modifications aren't made during the copy.
Needless to say, this adds overhead and time to the creation of new VMs. It's faster to just create blank VMs and kickstart them. Our kickstart solution is only half of what it could be, though. We are in the planning stages of a move to a more dedicated stack of hardware with the wonderful upgrade to...wait for it...ESXi 4.1. I don't have a great deal of VMware experience, but I suspect that a minor version number isn't going to introduce the functionality that we are looking for. Am I correct in this assumption? The deployment of a proper kickstart solution rests in the knowledge I'm provided here. I don't want to spend time designing a solution that will never be used if 4.1 supports proper RHEL6 VM copies. However, if it doesn't, I need to get in gear and get that solution in place sooner rather than later. -Mathew "When you do things right, people won't be sure you've done anything at all." - God; Futurama
_______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
