VIRTUMANIA Episode 21: Announcing WUPaaS. Exploring vSphere 4.1. Denying ESXi. Predicting VMWorld.
The VMUNDERGROUND invades VIRTUMANIA Episode 21 with a special VMWorld 2010 Warm Up Party announcement! Rick Vanover is my co host and we are joined by special guests Sean Clark and Brian Knudtson. The following is the podcast summary:
VIRTUMANIA Podcast Episode 21 – Announcing WUPaaS. Exploring vSphere 4.1. Denying ESXi. Predicting VMWorld. Rich Brambley (@rbrambley) of VMETC and Rick Vanover (@rickvanover) of Rickatron.us are joined this episode by Sean Clark (@vseanclark) of VMUnderground.com and Brian Knudtson (@bknudtson) of Knudt.net. This week we talk about everything VMworld 2010, point out some changes introduced with vSphere 4.1, air some concerns about using ESXi in the future, and announce the 2010 theme of the VMUnderground VMWorld Warm Up Party. Virtumania is an Infosmack Production.
Before, between, and after the important stuff we also have some fun with Sean’s hat, swagger wagons, iPads (again!), Dr. Seuss, VMworld 2010, and more!
Listen to the podcast with the embedded player or subscribe to get a weekly copy so you can listen when convenient.
Check out the VM /ETC VIRTUMANIA Page to listen to past episodes as well as episodes of Infosmack.
The following links offer more information on some of the topics mentioned in VIRTUMANIA Episode 21:
WUPaaS – VMWorld 2010 VMUnderground Warm UP Party as a Service
Warm-up Party Info
ESX4 is the last version with a Service Console
vSphere 4.1 and ESXi (virtualizationpractice.com)
“Up until now I have been really fighting this evolution to ESXi. When you find something that works well, change can be a little unnerving. On that note, VMware has really addressed a great deal of my concerns with the release of vSphere 4.1 ESXi.”
VMware Advances Foundation for Cloud Computing With VMware vSphere 4.1 and Expanded Virtualization Management Portfolio (vmware.com)
ESXi Hosts, AD Integrated Security Gotcha (virtualizationreview.com)
“Using Active Directory-integrated security in this configuration can impact your licensing responsibility if device client access licenses (CALs) are used. I reached out to Microsoft to clarify how this applies.”