Considering A Private On-Premise Cloud? Think again, Says Brocade!

While many IT leaders are excited by cloud computing technology, simply installing virtualization software on-premise does not turn transform your local infrastructure into a private cloud. Instead, this “static” implementation is simply one of many painful steps required to achieve “dynamic” cloud maturity, requiring a complex orchestration of servers, storage and network devices.

This message was delivered by data and storage technology firm Brocade, in a recent white paper entitled “Mythbuster: Deploying Virtualization Technology Does Not Automatically Create A Private Cloud.”

In fact, three key elements distinguish a true, automated private cloud:  People, Process and Automation.  Failure to unify these three assets with the underlying Ethernet fabric will most likely result in higher costs and complexity, or worse, failure.

Brocade outlined four stages of  “Infrastructure Maturity,” including acclimation, strategic consolidation, process improvement, and pooling & automation. See diagram below.

The result is that nearly 80% of a recent survey indicate they are stuck on stages 2 and 3 above, and were not getting ROI because infrastructure and IT leaders were plagued by miscommunication, complexity and one-off processes which sabotaged long-term “cloud” goals.

“The issue isn’t that good value or cloud economics can’t be achieved,” said Brocade, ”but rather value cannot be achieved without the following ingredients: virtualization, networks and automation.  Automation cannot occur with the creation of processes (the input and output of interlocking pieces; virtualized hardware, networks and applications).”

Brocade offered a tangible example of “static” implementations (non-automation) including a situation whereby a VM migration would require a service ticket being issued to the networking team that would adjust the port settings on both the existing port as well as the destination port for the virtual machine.

“Upon completion, the ticket would be passed to the server team to perform the move. Lastly the ticket would be sent back to the requester for verification and closure. “

This said Brocade, is time-consuming, antiquated and prone to human and system error.

The answer lies in breaking down technology silos, forcing process standardization and incorporating the deployment of automation tools.  Perhaps it’s clear at this point, why leveraging a remote hosting provider for private, public or hybrid cloud implementations just makes so much sense.    An ISV or enterprise can hit the grounding running with mature, scalable technology without worrying about the operational and technical details underlying the IaaS infrastructure.

This article was brought to you by VI.net, for dedicated server hosting, cloud servers and 24/7 support visit our site here www.vi.net

No Comments

Leave a Reply

You must be logged in to post a comment.

Stop blending in with the rest of the crowd and start leaving your mark on the web