Skip to main content

Cloud Computing reality check

John spoke to some folks and despite concerns there see to be growing interest in Cloud Computing. Obviously it is very clear that we were focusing on the wrong layer a bit too long (Virtualization, I mean) and its rapid commoditization with the increasingly (aspirational) consumerization of IT.

Following is a recap of some of what was discussed during those two sessions:

• One big question people had was how to go about integrating cloud-based applications and data with on-premises applications and data. This will be an issue for virtually any company moving into the cloud. As just one example of how that might be done, SnapLogic offers integration packs designed to work with some software as a service applications. InformationWeek will take a deeper dive into this subject in the next few weeks.

• A related issue is data quality. As companies move e-mail and other applications into the cloud, the integration points (Active Directory, for example) will become weak links and IT problems if your data isn't clean.

• There are a range of IT governance issues, not the least of which is e-discovery. Some questions that came up: How do you run e-discovery against hosted e-mail? And what privacy protections are in place so that your company's legal experts can access what's needed, but not the cloud service provider? Another way of looking at this is the "chain of custody" of your corporate data in the cloud.

• The point was made that many IT departments overlook or underestimate the network bandwidth requirements for cloud computing. One CIO said he increased network capacity by a factor of five when he moved some of his company's IT workload intoAmazon (NSDQ: AMZN)'s Elastic Compute Cloud. That's not a rule of thumb for everyone, but it's a good example of what one company had to do.

• There were a lot of questions, and not many answers, on service level agreements. It became clear that IT pros need to do their homework on SLAs as they shop among cloud service options.


Source

Comments

  1. Good post. I think most IT departments are woefully behind being ready for the cloud because they haven't fully implemented information security policies and standards. The danger of the cloud is separating the application from the data, and making sure that there are clear perimeters around each. Without implementing all the information security measures, vendors can take a position of plausible deniability.

    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