Welcome!

Microservices Expo Authors: Don MacVittie, John Katrick, Elizabeth White, Liz McMillan, Derek Weeks

Related Topics: Containers Expo Blog, @CloudExpo

Containers Expo Blog: Article

A Private Cloud Delivers IT as a Service

This two-part series reveals what a private cloud is about

A private cloud delivers business functions as services and empowers go-to-market, while virtualization virtualizes computing resources supporting the private cloud. They are two different concepts, address different issues, and operate at different levels in enterprise IT. A private cloud goes far beyond virtualization and virtualization is not a private cloud. To conclude this two-part series as listed below, here are the specifics regarding a private cloud vs. virtualization.

An essential part of a private cloud is virtualization that offers opportunities in reducing infrastructure costs, increasing operational efficiency, and improving deployment flexibility. A server instance deployed with a VM offers many advantages over one deployed with a physical machine. And VMs facilitate the implementations of resource pooling, rapid elasticity, and hence a private cloud. Notice that the benefits of virtualization including lower costs, higher efficiency, flexible deployment, etc. however do not translate themselves directly to "capacity on demand" which is much more and what a private cloud delivers.

Virtualization Is Not a Private Cloud
In addition to missing the five essential characteristics as criteria, it is not required to deliver virtualization with SaaS, PaaS, or IaaS. Namely, virtualization is not necessarily presented as a "service" while a private cloud always is. What virtualization offers is to virtualize resources without specifying how the virtualized resources are made available to users. In other words, virtualization introduces a mechanism to facilitate implementations of some, but not all, of the private cloud requirements. To equate virtualization to a private cloud is to mistakenly present part of a solution as the solution itself.

Private Cloud Priorities

The term, cloud, denotes the abilities to exhibit the five essential characteristics with one of the three possible delivery methods of a service as stated in the 5-3-2 Principle of Cloud Computing and NIST SP-800-145. When one claims having a "cloud" solution, we can easily verify it with a few simple questions: Can a user self-serve? How accessible? Is it delivered with (or at least a flavor of) SaaS, PaaS, or IaaS? Is it elastic? Does it have a self-servicing component?

Specific to a private cloud, there are however different priorities on the five essential characteristics. Two of the five essential characteristics remain pertinent, yet become optional in a private cloud setting. Either on premises or hosted by a 3rd party, a private cloud is expected to exhibit three, if not more, of the five essential characteristics of cloud computing. They are resource pooling, elasticity, and self-service as illustrated below:

virtualization vs private cloud by Yung Chou

As mentioned earlier in this article, virtualization is not a private cloud, but an important technical component of a private cloud. A private cloud on the other hand encompasses much more than just virtualizing resources.

From a private cloud's view point, two of the five essential characteristics of cloud computing become optional. They are ubiquitous access and consumption-based charge-back model. This is absolutely not to suggest the two are not applicable. They very much are for any solution qualified with the term, cloud, including a private cloud. There are however legitimate reasons to consider the two differently regarding a private cloud.

Restricted Access

Ubiquitous access in cloud computing implies anytime, anywhere, any device accessibility to a service. C-I-A triadWhile considering a private cloud, there are scenarios in which general accessibility may not be the intent. The required data confidentiality, integrity, and availability of a private cloud may prevent a service owner from offering a general access. Instead, business requirements may demand, in addition to user credentials, a further restricted access based on a combination of isolation at various layers including a device type, IP address range, port designation, domain membership, constrained delegation, protocol transition, etc. Namely, accessibility of a private cloud should be based on corporate information security policies and not necessarily an architecturally defined requirement. The concept of information security can be best summarized with the so-called C-I-A triad as shown above.

Feasibility of Charging Back

While transitioning into cloud computing, a realistic approach for enterprise IT is to build a private cloud by first transforming the existing infrastructure components and applications into a target cloud environment. With infrastructure components and an application architecture already put in place, a charge-back model may not always be technically feasible or administratively necessary. To charge back, show back, or sponsor an application without a consumption-based cost morel is up to an organization's priorities and therefore not necessarily an architectural requirement of a private cloud.

The Essence of Charge-Back Model

Nonetheless, a charge-back mechanism signifies not only the ability to recover costs, but the critical need of designing analytics into a service. By offering self-service and elasticity in a private cloud, the resource utilization can become very dynamic and unpredictable. The ability to monitor, capture, and process utilization data for capacity planning for supporting anytime readiness of a service has become imperative.

System Management Now Even More Critical

There is no question that virtualization is an enabling technology in transforming enterprise IT into a cloud environment. The reality is that virtualization is one component of a private cloud solution. Virtualization is nonetheless unequivocally not a private cloud itself. What a decision maker must recognize is that, for building a private cloud, virtualization, resource pooling, elasticity, and self-service model are to be designed as a whole with consistency, compatibility, and integration. Such that the architecture can fundamentally realize the 5-3-2 Principle of Cloud Computingwith a predictable and maximal ROI in the long run. The discovery, deployment, configuration, and management of a target resource from bare medal to run-time are all to be based on a common management platform and implemented with a comprehensive system management solution. Further, a consistent user experience in managing physical, virtualized, as well as cloud resources is critical to warrant a continual and increasing cost reduction of on-going technical support and training.

A Private Cloud Delivers ITaaS
Above all, a private cloud solution offers a technical architecture to strategically empower go-to-market which has become increasingly critical to the survival of a business facing the unpredictable workloads supported by proliferation of mobile devices and triggered by instant data storms in a highly connected business computing environment. IT professionals must not confuse virtualization with a private cloud. The former is a technically centric and an important piece of private cloud puzzles for virtualizing resources. While the latter focuses on servicing customers with on-demand accessibility and always-on readiness of a target application. The 5-3-2 Principle of Cloud Computing and this two-part series reveal what a private cloud is about. And that is to strategically build a go-to-market vehicle, such that enterprise IT can fulfill business needs and exceed user expectations. With a private cloud, IT can leverage business opportunities generated by market dynamics and offer a user experience with anytime, anywhere, on any device productivity. Ultimately the ability of acquiring IT capabilities on demand with a private cloud is in essence a reality of "IT as a Service."

More Stories By Yung Chou

Yung Chou is a Technology Evangelist in Microsoft. Within the company, he has had opportunities serving customers in the areas of support account management, technical support, technical sales, and evangelism. Prior to Microsoft, he had established capacities in system programming, application development, consulting services, and IT management. His recent technical focuses have been in virtualization and cloud computing with strong interests in hybrid cloud and emerging enterprise computing architecture. He is a frequent speaker in Microsoft conferences, roadshow, and TechNet events.

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.


@MicroservicesExpo Stories
Our work, both with clients and with tools, has lead us to wonder how it is that organizations are handling compliance issues in the cloud. The big cloud vendors offer compliance for their infrastructure, but the shared responsibility model requires that you take certain steps to meet compliance requirements. Which lead us to start poking around a little more. We wanted to get a picture of what was available, and how it was being used. There is a lot of fluidity in this space, as in all things ...
Gaining visibility in today’s sprawling cloud infrastructure is complex and laborious, involving drilling down into tools offered by various cloud services providers. Enterprise IT organizations need smarter and effective tools at their disposal in order to address this pertinent problem. Gaining a 360 - degree view of the cloud costs requires collection and analysis of the cost data across all cloud infrastructures used inside an enterprise.
The dynamic nature of the cloud means that change is a constant when it comes to modern cloud-based infrastructure. Delivering modern applications to end users, therefore, is a constantly shifting challenge. Delivery automation helps IT Ops teams ensure that apps are providing an optimal end user experience over hybrid-cloud and multi-cloud environments, no matter what the current state of the infrastructure is. To employ a delivery automation strategy that reflects your business rules, making r...
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
Admiral Calcote - also known as Lee Calcote (@lcalcote) or the Ginger Geek to his friends - gave a presentation entitled Characterizing and Contrasting Container Orchestrators at the 2016 All Day DevOps conference. Okay, he isn't really an admiral - nor does anyone call him that - but he used the title admiral to describe what container orchestrators do, relating it to an admiral directing a fleet of container ships. You could also say that they are like the conductor of an orchestra, directing...
The past few years have brought a sea change in the way applications are architected, developed, and consumed—increasing both the complexity of testing and the business impact of software failures. How can software testing professionals keep pace with modern application delivery, given the trends that impact both architectures (cloud, microservices, and APIs) and processes (DevOps, agile, and continuous delivery)? This is where continuous testing comes in. D
SYS-CON Events announced today that Synametrics Technologies will exhibit at SYS-CON's 22nd International Cloud Expo®, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. Synametrics Technologies is a privately held company based in Plainsboro, New Jersey that has been providing solutions for the developer community since 1997. Based on the success of its initial product offerings such as WinSQL, Xeams, SynaMan and Syncrify, Synametrics continues to create and hone in...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
The notion of improving operational efficiency is conspicuously absent from the healthcare debate - neither Obamacare nor the newly proposed GOP plan discusses the impact that a step-function improvement in efficiency could have on access to healthcare (through more capacity), quality of healthcare services (through reduced wait times for patients) or cost (through better utilization of scarce, expensive assets).
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task...
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
Many IT organizations have come to learn that leveraging cloud infrastructure is not just unavoidable, it’s one of the most effective paths for IT organizations to become more responsive to business needs. Yet with the cloud comes new challenges, including minimizing downtime, decreasing the cost of operations, and preventing employee burnout to name a few. As companies migrate their processes and procedures to their new reality of a cloud-based infrastructure, an incident management solution...
Cloud Governance means many things to many people. Heck, just the word cloud means different things depending on who you are talking to. While definitions can vary, controlling access to cloud resources is invariably a central piece of any governance program. Enterprise cloud computing has transformed IT. Cloud computing decreases time-to-market, improves agility by allowing businesses to adapt quickly to changing market demands, and, ultimately, drives down costs.
Recent survey done across top 500 fortune companies shows almost 70% of the CIO have either heard about IAC from their infrastructure head or they are on their way to implement IAC. Yet if you look under the hood while some level of automation has been done, most of the infrastructure is still managed in much tradition/legacy way. So, what is Infrastructure as Code? how do you determine if your IT infrastructure is truly automated?
Every few years, a disruptive force comes along that prompts us to reframe our understanding of what something means, or how it works. For years, the notion of what a computer is and how you make one went pretty much unchallenged. Then virtualization came along, followed by cloud computing, and most recently containers. Suddenly the old rules no longer seemed to apply, or at least they didn’t always apply. These disruptors made us reconsider our IT worldview.