Skip to main content

Virtualization: Forget about the hypervisor; get into management

Most of the parties out there, we have already covered (except Platespin, I did chat with some one via email but somehow we couldn't pick it up from there).

Anyways, we are into the next phase, Virtualization 2.0. There are other parties, which I have spoken to, who will also invade these adjacent territories, making the battle even more intense. I've spoken to CEOs who are going to really give firms like CA, HP etc a big headache. These guys are going for the big market, with faster, agile appliances. All deployable without any Forge hardware. But I'm sure the Platespin guys have something to tell me I don't know ;-)

P.S: You will see more of the little, fatless, light-weight firms challenging other little (with some fat) start-ups. So you get my point: The battle is between zero-fat VS some-fat. Overweight folks have a BIG problem.

Here's IW's coverage:

At the same time, newcomers such as Embotics, PlateSpin, and Veeam are expanding the list of tools with which virtual machines may be managed.

After months of describing virtualization as a feature of the operating system, Microsoft relented Nov. 12 and decided its Hyper-V hypervisor, formerly Viridian, would be available as a standalone product. Lost in the shuffle was the upgrade to System Center management tools, which now include System Center Virtual Machine Manager 2007 to provision new virtual machines, centrally monitor and manage running virtual machines, ensure virtual machine security, and update virtual machines.

Virtual Machine Manager is meant to work with Microsoft's other System Center products, including System Center Operations Manager 2007, released earlier this year. Operations Manager monitors and manages the servers running in the data center, according to Bob Kelly, corporate VP of servers and tools, in his address at the TechEd IT Forum 2007 on Nov. 12 in Barcelona, Spain.

Read the rest here.
Labels:

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op
Post a Comment
Read more