We should all probably be a little angry.
After all, according to the brains back in the 1950s, weren’t we all supposed to be flying around in personal helicopters by now?
Of course, there were some prophecies that weren’t all that great. An article in a 1950 issue of Popular Mechanics predicted that by 2000, we would be eating food reconstituted from sawdust and live in homes with waterproof furniture that could be hosed down for cleaning. (I think I’ll pass on the sawdust sandwiches myself.)
The moral to the story is that predictions about technology can be tricky. One of the more recent disruptive technological events, the emergence of the Cloud, is gathering predictions almost as rapidly as it acquires new converts, ranging from the extinction of distributors to the growth of entirely new business models, such as Cloud brokers.
One prediction, aptly nicknamed "The Cloudburst", is that a major security event will occur within the Cloud, chilling immigration to it. Incidents have already occurred that highlight the impact of such an event, for example, last year the FBI raided a data center in Virginia and crippled the service of numerous organizations in its investigation of a single company.
Understandably, many organizations are taking a security conscious approach, setting up private, internal Clouds. This approach allows then to enjoy most of the benefits of the Cloud, mitigate concerns about data security, and ensures immediate, focused service from their IT department in case of an event. (Our own solution, TrackerSuite.Net, which includes integrated modules for project management, Web timesheets, help desk services and more, is available as such a licensed solution, with the source code included.)
For organizations planning to roll out an internal Cloud, following are a few helpful steps, courtesy of Benjamin Littlejohn’s excellent "Private Cloud Blueprint". The full article is available with a free registration to www.InformationWeek.com.
- Think like a provider. Identify the kinds of applications that will run in the Cloud, who will use them and how the Cloud will be managed.
- Review your storage needs. What will the applications that will run in the Cloud require?
- Handle the network. Consider your needs and plan your network virtualization carefully.
- Automate and orchestrate. Coordinate the activities of your virtualized compute, storage and network resources.
- Monitor, monitor, monitor. Keep a close eye on your new Cloud and measure its performance.
- Sell your Cloud. In order for the initiative to succeed, IT not only has to build the Cloud, but also has to market it to its internal customers to demonstrate its value and gather support.