We have been working with IT clients who deploy private clouds as part of their operations. The reasons include implementing a change in the delivery of IT services, a new infrastructure for dealing with the overwhelming influx of unstructured data, and a way to deploy and support new applications developed for mobile technology. Each of these reasons makes sense and can fit into an economic model given the projected demands.
The types of private clouds also vary. The simplest we have seen from IT clients is a private cloud that is an object storage system on premise used as a content repository. The most common types of these are:
• A large-scale repository that used by new or modified applications that must deal with large amounts of unstructured data.
• A large, online storage area where data is moved off primary (or secondary) storage to less expensive storage with different data protection characteristics.
• As the repository of data from external sources used for analytics. This data may not require long-term retention.
Most of these operations have built-in the ability to use public cloud resources and they use the term hybrid-cloud. Public cloud use may be in the form of long-term archive of data (deep archive) where the access time is much more relaxed, as sharable information in the form of file sync and share implementations, or as an elastic storage area to handle large influxes that may not be retained for extended time periods. Usually there is a mechanism to handle the transfer and security of data to and from public cloud. This is usually done by gateway devices or software. Storage system vendors are starting to provide built-in storage gateways to manage data movement to the cloud.
These are all justifiable reasons and usages for traditional IT operations to deploy private clouds. But what do you call IT that has changed operations to achieve this? Continuing to use the IT term is simple but it does not convey the fact that IT has fundamentally transformed operations and the value provided. IT as a Service (ITaaS), which is the outcome goal of most transformations, is a significant value and is different from IT of the past. The term cloud is an ambiguous identity used in many different contexts and probably will not have staying power over time.
Historically, what is known as IT has changed names over time, representing major transitions in the industry. Many remember DP or Data Processing as the term for centralized IT of the past. Some of us even go back to an earlier point when the term was EAM, which is an artifact acronym for Electronic Adding Machine. There was also the term IS, which stood for Information Systems and later Information Services. Information Technology is the current broadly accepted definition for business, but a change is in order with the services and capability transitions underway.
What should the new identity be? Maybe there should be a naming contest. Probably the worst thing would be for one vendor’s marketing organization to drive its descriptive name. The new name in this case would be to promote that vendor’s vision and how its products serve the necessary requirement. In this case, there may be a full court press for that identity with paid professionals promoting the name. The new identity needs to convey the data center transformation that has occurred. Hopefully, the name will not have “cloud” in it.
The name change will occur and probably start as one thing and quickly evolve. A few years from now, it will be commonplace. The identity change is a step in the logical progression of computing services (keeping in mind the value is in deriving information from data). Terms such as client-server will become footnotes in the history of the industry. Other ideas that were detours down a rough road will seem like another learning experience everyone had to go through. This is an interesting period to see transitions occurring.
(Randy Kerns is Senior Strategist at Evaluator Group, an IT analyst firm).