Skip to main content

Strategy: So you've virtualized (sort of), what next?

I've blogged about it here:

But many of you may also fall prey to the "glory of virtualization" and ready to push you data center into the virtual world, in the hope of pleasing your CxO. You may not achieve a completely virtualized data center in the beginning. IT managers and Infrastructure managers are not ready to put their "mission-critical" applications such as e-mail, databases, crm, company portal etc on a virtualized platform. Obviously we always had an answer to that: high level load-balancing and clustering. But the IT managers who are not well averse with the developments in the industry can be blinded by such "hype" and are prone to succumbing to their "bounded awareness" by taking their applications/OSs into the virtual world and forgetting about crucial issues like hypervisor security, server sprawl, ILM (VMLM), existing siloed (siloed does not necessarily have to be a derogatory connotation, it does however impact the agility of your business, given the human intervention, that slows down the whole machinery) business process management approach (ITIL, CMDB, SLA, etc) that will undergo a heavy change as we move towards, or should I say, start-ups move towards grabbing that opportunity to push autonomous, self-healing, self-processing architecture.

These are big issues. I have spoken to some big companies, some even boasting to hold "top accounts" and when I mentioned that "it is very crucial to talk about the issues such as security etc", and I get to hear: "Hey, we have to sell the product, not tell them how it is". What "top account" firms do forget is that customers are talking and reading about it all the time, so if you come in to sell, they might already know the weaknesses of your product against some other competitor, who spent all this time waking you up!. That is why the battle is getting worse all the time. The ones who are choosing to ignore the customers problems, are losing business. I'll rephrase this: If you are not talking to your customer, he'll find someone else to talk to!

Read the rest at ITtoolbox.

Comments

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

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