With development and test teams creating VM’s like crazy, this needs to be taken into consideration. I’d love to hear from you if you’re doing this?Īnother difference is that VMware vCloud Director is licensed per VM, whereas Lab Manager is per processor. Mike Laverick actually commented () that this could be achieved with VMware vShield but I have no experience of this with vCloud Director. VMware Lab Manager uses virtual routers (very small Linux based VM’s) to isolate networks in fenced configurations. However, I’ve used Vyatta virtual networking appliance in the past to provide access to private VLAN’s using NAT which achieves a similar solution, albeit a very manual task and only good for static environments. If you use ring-fenced network configurations with Lab Manager then you will have to find an alternative as this isn’t available in vCloud Director. I’m sure (and I only speculate here) that this would be possible with future versions of vCloud Director. So what are these gaps? VMware Lab Manager supported linked clone technology way before VMware View did, but this isn’t available with vCloud Director. Remember that Lab Manager will continue to be supported until 2013 and I’m sure the next major release of vCloud will fill some of the gaps in features between the two products. Many of you will be wondering what to do now as Lab Manager has been heavily invested in for the development and test teams. Over the past few years I have spent a considerable amount of time supporting a large development team with Lab Manager since version 2.5 so I’m kind of sad to see it go, but this is an exciting time in a new era of VMware vCloud Director… This week VMware officially announced that VMware vCenter Lab Manager will not see further major releases and support will continue until 1st May 2013. Bye Bye Old Friend, end of the line for VMware vCenter Lab Manager
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |