Skip to main content

Why Cisco, EMC and VMware need to get Cloud-relevant?

Because they are not there yet despite the fact that they may be in most of those data centers.

Just look at the Wikipedia definition of cloud:

Cloud computing means Internet ('Cloud') based development and use of computer technology ('Computing'). It is a style of computing where IT-related capabilities are provided “as a service”[1], allowing users to access technology-enabled services "in the cloud"[2] without knowledge of, expertise with, or control over the technology infrastructure that supports them[3]. It is a general concept that incorporates software as a service, Web 2.0 and other recent, well-known technology trends, where the common theme is reliance on the Internet for satisfying the computing needs of the users. For example, Google Apps provides common business applications online that are accessed from a web browser, while the software and data is stored on the servers.


And then go ahead and do a search for EMC, Cisco or VMware. They aren't listed. Wikipedia is being read by a lot of readers and decision makers.

Is this the only reason why Cisco should still go after EMC? Absolutely not! There are more reasons than that, but we have discussed that before as well and I'm not about to beat the dead horse yet again :-)

Comments

  1. Not sure what you are talking about here. I had no problem finding entries in Wikipedia for Cisco, EMC (Corporation) and VMware.

    Also the entry you attribute to being for "cloud" is actually the entry for "cloud computing".

    ReplyDelete
  2. FWIW, if you look at EMC... and their recent acquisition of Mozy, they have a significant presence "in the cloud".

    Mozy has over 10 PB of user's data that is "in the cloud". That's probably more data than any of their competitors and gives them a serious foothold...

    Combine that with their acquisition of Pi (Paul Maritz' company) and they could have some pretty neat stuff up their sleeve.

    ReplyDelete

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

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