@CloudExpo Authors: Liz McMillan, Zakia Bouachraoui, Yeshim Deniz, Pat Romanski, Elizabeth White

Related Topics: @CloudExpo, Microservices Expo

@CloudExpo: Article

Enabling Enterprise Cloud Models

Current design limitations

In moving to the cloud, Enterprise IT needs to get their arms around the cause/effect and limitations that existing datacenter infrastructure design has on their agility to adopt and exploit cloud-computing models. Previous datacenter design choices have resulted in not meeting the needs of the business.

In particular, these design choices have resulted in complexity, waste, performance barriers, and cost models that don't work for the business. Lack of understanding and transparency of what has been done in the past will continue to create misalignment with business needs if not addressed. Moving to an enterprise cloud model without understanding the datacenter infrastructure mistakes is like automating and extending an already bad process.

It is important that the reader does not take this to be an attack on any work products they may have done in the past. All of us in IT have made some if not all the mistakes below - usually due to influences or drivers out of our control.

To fix this and enable enterprise cloud models, we must not employ the following datacenter design limitations that include:

Supply-driven management: Most datacenter infrastructure teams design and manage from the bottom up. The typical approach is to standardize, partition, allocate, and implement a "vanilla" solution of compute and storage that is attached to the network based on the topology of the datacenter floor. Provisioning is then designed for peak workloads leveraging a bottom-up-designed platform that has been selected for typical reasons of vendor rationalization, price, etc. The business workload and service requirements incorporating factors of performance, price, or efficiency are not incorporated and misalignment of needs and inconsistent service delivery begin to occur.

One size fits all: Most datacenter infrastructures and typical vendor strategies are built around a perceived "standardized" footprint. The problem is that this is designed typically from the bottom up with little or no correlation to the workflows, workloads, information, content, and connectivity requirements of the business and its competitive needs. Such disconnects result in poor performance, unnecessary costs, waste, and in agility issues for both the business and IT.

Spaghetti transaction flow: Transaction flow across traditional datacenter infrastructures must deal with a design that does not consider proximity of the various devices that comprise a service unit that delivers processing to users. This results in significant performance impacts (user experience of the business suffers) whereby compute, memory, I/O fabric, disk, storage, and connectivity to external feeds are provided in terms of layout, not in terms of service delivery. Performance can be impacted by 30-fold due to this approach. Moreover, this creates waste in terms of unnecessary network traffic congestion and bandwidth usage (ROE suffers).

Definition of "insanity": The continuous use of a typical datacenter layout incorporates homogenous pooling of various classes of resources. Servers by multiple classes are typically in multiple pools; storage by file or block are in different pools in their own area of the datacenter; network load balancers, network switches, and network routers are pooled/deployed across various areas of the datacenter. This approach is not designed for business impact, business needs, optimal workload throughput, or time-to-provision or optimal space/power usage. The average provisioning cycle in datacenters with this type of layout are measured in weeks or months versus the minutes or days needed to provision, troubleshoot, or perform to meet the needs of the business.

Bottom line: Enterprise Cloud models will enable IT to take business to the next level of competitive advantage. If the supply chain of IT does not provide the delivery paradigm that enables a cloud utility model, it will fail the business in realizing its potential. The journey to the enterprise cloud begins with understanding the limitations of current design approaches.

More Stories By Tony Bishop

Blueprint4IT is authored by a longtime IT and Datacenter Technologist. Author of Next Generation Datacenters in Financial Services – Driving Extreme Efficiency and Effective Cost Savings. A former technology executive for both Morgan Stanley and Wachovia Securities.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

CloudEXPO Stories
With more than 30 Kubernetes solutions in the marketplace, it's tempting to think Kubernetes and the vendor ecosystem has solved the problem of operationalizing containers at scale or of automatically managing the elasticity of the underlying infrastructure that these solutions need to be truly scalable. Far from it. There are at least six major pain points that companies experience when they try to deploy and run Kubernetes in their complex environments. In this presentation, the speaker will detail these pain points and explain how cloud can address them.
The deluge of IoT sensor data collected from connected devices and the powerful AI required to make that data actionable are giving rise to a hybrid ecosystem in which cloud, on-prem and edge processes become interweaved. Attendees will learn how emerging composable infrastructure solutions deliver the adaptive architecture needed to manage this new data reality. Machine learning algorithms can better anticipate data storms and automate resources to support surges, including fully scalable GPU-centric compute for the most data-intensive applications. Hyperconverged systems already in place can be revitalized with vendor-agnostic, PCIe-deployed, disaggregated approach to composable, maximizing the value of previous investments.
When building large, cloud-based applications that operate at a high scale, it's important to maintain a high availability and resilience to failures. In order to do that, you must be tolerant of failures, even in light of failures in other areas of your application. "Fly two mistakes high" is an old adage in the radio control airplane hobby. It means, fly high enough so that if you make a mistake, you can continue flying with room to still make mistakes. In his session at 18th Cloud Expo, Lee Atchison, Principal Cloud Architect and Advocate at New Relic, discussed how this same philosophy can be applied to highly scaled applications, and can dramatically increase your resilience to failure.
Machine learning has taken residence at our cities' cores and now we can finally have "smart cities." Cities are a collection of buildings made to provide the structure and safety necessary for people to function, create and survive. Buildings are a pool of ever-changing performance data from large automated systems such as heating and cooling to the people that live and work within them. Through machine learning, buildings can optimize performance, reduce costs, and improve occupant comfort by sharing information within the building and with outside city infrastructure via real time shared cloud capabilities.
As Cybric's Chief Technology Officer, Mike D. Kail is responsible for the strategic vision and technical direction of the platform. Prior to founding Cybric, Mike was Yahoo's CIO and SVP of Infrastructure, where he led the IT and Data Center functions for the company. He has more than 24 years of IT Operations experience with a focus on highly-scalable architectures.