Google's announcement this week about their intention to create a web-based operating system from its Chrome technology has huge implications for storage, as well as the whole IT industry. Inexpensive, lightweight and always-ready is the big winner in client technology.
Whether Google eventually succeeds with its Chrome strategy is immaterial now that the cat is out of the bag - everybody now understands that a user operating system doesn't have to carry legacy desktop system baggage anymore. The cost of supporting obsolete equipment and software can be dropped and those functions replaced by utility (cloud) services. Among the obsolete stuff that can be left out are lots of storage drivers.
So what happens to data storage when user operating systems are completely web-based? To begin with most user data will be stored for clients by the cloud applications running as SaaS web services. The question of whether those are private or public cloud services depends on a number variables including privacy concerns, single sign-on integration and application service levels. Public service providers can leverage their resources across a larger install base, which will give them an economic advantage, but they need to be able to handle the challenges of multi-tenancy with technologies such as virtual management domains.
Service providers will build infrastructures with the most flexible, scalable products available. In an environment when almost anything can be accomplished in an Internet instant, neither clients or service providers can afford much time for initial setup and service level changes. For storage administrators, this amounts to having autonomic storage that readies all the resources before they are needed to be provisioned.
The concept of reservationless storage is important. If storage resources are connected to an array, why should it be necessary to think about which pools or meta-structures to assign them to first? A storage admin in a web-connected world probably doesn't have the time to plan, re-plan and change logical storage structures when they are in the middle of a services demand surge. When management wants to know why service levels are causing customer problems, the last thing they want to hear is that storage had to be re-distributed because previous plans had to be changed. Thin provisioning and wide striping implementations that require pre-work and re-work won't deliver the goods.
Best practices will move from being a human-managed effort to setting thresholds and warnings for an autonomic, self balancing system. This vision is what is pushing development efforts at 3PAR, much of it is already available in 3PAR InServ arrays today.