Understanding OpenStack’s SuccessFebruary 21, 2017
Grazed from Linux Journal. Author: Petros Koutoupis
At the time I got into the data storage industry, I was working with and developing RAID and JBOD (Just a Bunch Of Disks) controllers for 2 Gbit Fibre Channel Storage Area Networks (SAN). This was a time before "The Cloud". Things were different—so were our users. There was comfort in buying from a single source or single vendor. In an ideal world, it should all work together, harmoniously, right? And when things go awry, that single vendor should be able to solve every problem within that entire deployment.
That is why, enterprise companies typically bought from a single storage vendor and invested deeply in them. You either bought HP, Dell, EMC, Sun Microsystems or NetApp, which also was successfully carving a new market in Network Attached Storage (NAS). For example, once an EMC shop, always an EMC shop. Hundreds of thousands to even millions of dollars were spent to ensure that you were enabled for high availability, fault tolerance, training, support and more. Again, through that single vendor.
This model lasted for quite some time, but in the recent decade, things started to evolve. Customer’s wanted more. New technologies, both hardware and software, began to emerge and offer very attractive functionality—virtualization (with VMware) is the first that comes to mind, external Flash arrays, software-defined storage—almost all of which helped to kickstart this thing we call the cloud. The list goes on.
These same shops started to express some frustration in this. They wanted all of these extra features that those same single vendors either did not offer or were too slow in bringing something competitive to market. Instead of running products through a single vendor and using more unified management frameworks to maintain it all, they are now toggling back and forth across multiple management interfaces from multiple vendors to accomplish simple tasks. This is all well and good when the workload is small, but it does not scale very well when that workload increases. How can you log in to a single dashboard and monitor or manage your virtual/physical machines, network, storage and more? What can bring all this moving pieces together?
Read more from the source @ http://www.linuxjournal.com/content/understanding-openstacks-success