Skip to main content

Virtualization: How to cope/co-exist with hyper-disruption as a complementer

Just wrote this up on ITtoolbox.

Really , there is too much happening out there and way too fast. This industry is evolving every few weeks. I saw a couple of authors struggling to keep up the pace with all the advancements.

For instance, lets take VMware here. They first brought out ESX 3.0, a couple of writes/authors or experienced folks in the industry got excited and started writing a book on it. A lot of expertise was put into those books. Loads of scripts, loads of perl stuff and massively cool Linux commands. I've personally never seen a windows admin do a dd so it was really cool to see the guys go crazy with all those commands.

Developers start writing utilities like ESX update utility and loads of other little utility. Vmware goes ahead and releases its 3.5. Oops...plans change as authors have to struggle to keep up with the pace of all the changes that come in and get going with all the new (primarily) GUI utilities such as Update manager etc.

Then boom!!! Here you have the firmwarish version of ESX 3i and suddenly you don't need to get into your Linux consoles and all those custom scripts can go home as that thin, flimsy layer of near-embedded hypervisor is a simple keystroke up/down and all those F1, F2, F11 keys.
Read the rest there.
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