VMware just dropped the news that the future version of VCB will not be an installable anymore. VCB will be an API. This will save you that additional (proxy) host that it will normally cost you. This probably also means that software vendors can take the full advantage of their own unique abilities like deduplication, direct restore into a VM… Agentless backups in a decent way. I’ve always thought that VCB was underestimated by a lot of people, but I guess I did know why. This should solve most of the problems people were facing with the integration modules and scripting.
vmworld
Virtual Infrastructure Management Assistant aka VIMA
I was just catching up and read this blog from Scott about managing ESXin a COS-less environment. The most interesting part of this blog is the following:
The subject of deployment is a key issue when we think about losing the Service Console. One approach to handling these issues is deploying physical machines; another would be to deploy virtual machines to handle these tasks. Partners could wrap up the agents that would typically be deployed in the Service Console as a virtual appliance, but then users could end up with numerous virtual appliances. What if VMware were to provide a virtual infrastructure management appliance? That’s what VIMA (Virtual Infrastructure Management Assistant) is.
VIMA is a virtual appliance packaged as OVF and is distributed, maintained, and supported by VMware. This is downloaded and installed by the customer according to their management procedures. This will be a well-known deployment environment that partners can rely upon being present. This will be a 64-bit Linux distribution with VMware Tools, VI Perl Toolkit, the Remote CLI (now known as the VI CLI), and a JRE already present. VIMA can be patched for updates, and it allows you to manage one or more VMware ESX hosts directly or through VirtualCenter. VIMA can enable agents to authenticate themselves, and VIMA will rotate its passwords on the hosts. Additionally, sample code and documentation will be available for programming applications to work in VIMA.
Anyone interested in VIMA can e-mail [email protected] and request access to pre-GA versions of VIMA. VIMA is expected for general release in the fourth quarter of this year. All VIMA releases will work with both ESX and ESXi
Read the full article for more info, but this is again an exciting addition to the portfolio. Having an virtual appliance which can contain agents and communicate with your vCenter Server and your ESX(i) host is a real benefit. You can keep the number of agents down to a minimum with the same flexibility and usability.
Another day…
And more cool stuff announced. I know I have to stay objective and try not to sound like a cheerleader… but man did you see the latest announcements? It’s hard not to get excited, it’s hard not to be enthusiastic, the hell with it I’m not even gonna try it.
And why not one might ask? Well because VMware just announced the fact that vCenter Server will be released as a linux virtual appliance in the future and the vCenter client will be cross platform available. So all you linux minded or mac minded sysadmins out there, keep an eye out for the beta program. This is also a great reason for me to ditch XP on my laptop and start installing Ubuntu, well as soon as it’s available that is! But is definitely one of the best announcements this week in my opinion. I’ve been asked this question, when will VC (client) be available for linux, very very often. Well I still can’t give an answer but it’s on the roadmap! Getting the MS requirement out of the Virtual Environment or should I say vCloud is important for a lot of customers and (most important) SysAdmins.
But that’s not it, the new “limitations” that Dr. Stephen Herrod announced today are overwhelming, 64 nodes in a cluster, 4096 processor cores and 64 TB of RAM. So my question is … what about the current 2TB limitation for LUN’s. Let’s hope that one will be gone soon… And let’s hope VMFS also get’s a make over, no that it’s not functioning at the moment but a VMFS resize option would be nice for instance. Well we will just have to wait and see I guess. But it would fit into the new vStorage initiative. Which, as Chad explained, is also an API where hardware vendors can take advantage off! Like for instance the vCenter SAN Snapshot integration that NetApp, Dell/EQL and EMC announced yesterday.
Well I can rewrite Scott’s entire blog but that just isn’t very useful… So click here and read one of the most extensive live blogs on the VMworld Day 2 Keynote. These were just some random thoughts, I’m going for a walk, just to clear up my mind… a lot of information in a short amount of time.
VMworld is just killing this blog
I just hit an all time high of 4000 unique visitors on one day…. Man this is going insane. Thanks everybody for visiting my website, it makes it worth it. I hope I can be at VMworld next time and do a better job at feeding you with information.
For those that didn’t go to VMworld… part II
So after I shutdown my pc a couple of great articles were released, read ’em or view ’em here:
Rich Bramley: BC3819: Re-architecting Data Protection Processes with Data Deduplication and Virtualization Technologies
VirtualFutute.info: Fault Tolerance
VirtualFuture.info: VDM 3.0
Scott Lowe: TA2668: VMware ESX Architectural Directions
Scott Lowe: BC2621: Fault-Tolerant VMs in VI: Operations and Best Practices
Eric Sloof: Video’s, Video’s, Video’s! Just keep checking his site regularly!