Welcome!

Microservices Expo Authors: Pat Romanski, Dalibor Siroky, Stackify Blog, Elizabeth White, Liz McMillan

Related Topics: Containers Expo Blog, Microservices Expo, @CloudExpo, @DXWorldExpo, SDN Journal, @DevOpsSummit

Containers Expo Blog: Article

Edge Virtualization and the MicroCloud

Benefits and Difference from Private and Public Clouds

The benefits of public and private clouds based on virtualization are varied and well known. In 2013, more than 40 percent of enterprises have or are adopting virtualized private clouds in the data center, and another 40 percent are evaluating virtualization solutions. Nevertheless, less than 10 years ago, the number of enterprises doing any kind of private cloud virtualization was almost nonexistent.

Some of the benefits driving this rapid adoption in the enterprise, apply equally well for small-to-medium businesses (SMBs) and the edge. These benefits include:

  • Application compartmentalization - containment within the application's own O/S processor and I/O space (prevents single applications from consuming a platform's resources or affecting other applications due to problems)
  • Simplified security and quality of service (QoS) policies - administration across sites, applications, and networks
  • Automated application integration and orchestration - simplification of installation, upgrades, and migrations without platform reboots or network downtime
  • Better scaling and platform optimization - scale is simple addition
  • Improved survivability and performance - treat multiple platforms as one system

For the purposes of this article, "edge virtualization" is described as the MicroCloud - to distinguish it from "public" and "private" clouds typically associated with the data center. The following are distinctive attributes of the edge MicroCloud (versus private and public clouds).

  • It is located at the WAN interface of an SMB (typically the Internet) or a remote site in a larger enterprise (typically MPLS)
  • Network bandwidth is typically constrained
  • The south side of the edge (facing the LAN) is typically less than 200 devices/users
  • Policy (security, QoS, NAC/Network Access Control) is typically required
  • Firewall, NAT and subnet functionality are required
  • The "edge" is typically price and operationally constrained
  • The edge typically applies not only to network functionality but to edge applications as well (e.g., session border control, Wi-Fi controller management, etc.)

It is expected that edge virtualization and software defined networks (SDNs) will completely replace purpose-built appliances and integrated applications at the edge. These are all compelling reasons behind the move to virtualization in the data center, and these same attributes apply equally to the SMB and enterprise edge. When considering a transition to edge virtualization and SDN, you need to look for a solution that provides both powerful networking and orchestration capabilities.

The table below illustrates some of the benefits of virtualization at the edge and is followed by a brief description of each.

Edge Virtualization Feature Example: "Application Compartmentalization"

Virtualization Feature Overview:
One of the advantages of running on a virtual platform, versus adding an application on top of an existing O/S, is the fact that the application can run on the O/S it is optimized for, with resources dedicated for its use. This becomes especially important when the applications are deep and complete, such as with a session border controller or a voice IP key system, particularly when these might need to run on the same platform together or with another complex-type network application.

Example Description:
The following diagram illustrates one of the primary benefits of virtualization: the ability to allow an application to run in its own optimized O/S space with efficiently apportioned resources.

In this diagram, the "Orchestration and Network Manager VM" manages the configuration of the SBC VM as it relates to the disk, network, processor, and RAM. Any additional applications are then appropriately plumbed with proper resource management. This resource allocation is very difficult to do in the absence of virtualization, inasmuch as applications tend to compete with one another in the "user space" of the O/S.

Benefits:
Virtualization allows for quick integration of applications within the same platform. With proper orchestration it is possible to balance application resource needs with platform capabilities. It is not necessary to fine-tune applications to a host O/S, as is done with traditional edge devices.

Edge Virtualization Feature Example: "Simplified Policy Management"

Virtualization Feature Overview:
Policy management is one of the most complex components of any networking application. It becomes particularly complex at the edge when policy needs to be applied across platforms and geographies. Examples include "guest" and "corporate" policies-particularly for wireless access. Policy is typically used to define/limit/grant access to particular resources, such as bandwidth or data for users or devices. The complexity of policy is usually prohibitive in terms of use. Virtualization with proper orchestration greatly simplifies this required but very complex component.

Example Description:
The following diagram illustrates the simplification of policy management across sites. Superimposed upon a real site/policy map are guide blocks that emphasize sites (in columns) and policy (rows). The blue guide block emphasizes where policy (and routing) is set.

Benefits:
Policy management for security and QoS is typically complex and prone to error. Virtualization with proper orchestration greatly simplifies this critical component while improving upon the specific attributes of security and QoS.

Edge Virtualization Feature Example: "Automatic App Integration & Orchestration"

Virtualization Feature Overview:
Virtualization orchestration creates several important benefits. One of the most important of these is the ability to perform automatic integration of applications with respect to the network (automatic wiring) and its associated QoS and security policies. In a traditional implementation without the benefit of virtualization orchestration, integration tends to be fraught with errors, particularly when applied across geographies and between applications. Additionally, updates and changes in a virtual environment can usually be orchestrated as a simple switch from a running VM to the upgraded VM, whereas a traditional environment will typically require a platform reboot-thus causing all applications to lose connectivity for a period of time.

Example Description:
The following diagram illustrates the edge architecture that yields automatic app integration with virtual wiring.

Each of the colored lines represents a virtual wire (circled in red). Orchestration automatically connects these lines to the appropriate virtual switch, interface, or application.

Applications are, in turn, instantiated, configured, and plumbed by the same orchestration software. Each VM will run in its own operating system and be allocated appropriate resources. Additionally, the host hypervisor O/S and each of the VMs are isolated from each other and the WAN and LAN networks by the "network flow manager." This isolation provides both a level of security and an improvement of application upgrades/configurations.

Benefits:
Virtualization and orchestration eliminate many of the problems associated with traditional all-in-one appliances that attempt to run applications that must interact with each other and the network. Configuration mistakes are avoided, and upgrades happen with no downtime.

Edge Virtualization Feature Example: "Scalability and Optimization"

Virtualization Feature Overview:
Traditional methods of application integration usually require platform replacements in order to increase in scale. Additionally, platform optimization tends to be dependent upon the most computing-intensive application, making it difficult to balance between size and number of applications. On the other hand, virtualization has demonstrated excellent scalability and optimization value through simple addition. In fact, the trend is to reduce the size and cost of the platform, allowing more linear growth and optimization.

Example Description:
The following diagram illustrates the evolution of a typical edge configuration towards smaller and less costly virtual platforms that can provide scalable and optimized application and network support.

In order to scale, once a single platform has maximized the number of applications that it runs, it is only necessary to add a second (or third, etc.) platform. This will hold true for most full-size applications, such as web services, databases, file systems, etc., that can inherently take advantage of multiple instances. Furthermore, it is possible to move VMs from one platform to the next in order to optimize the resources of a particular application on a particular platform.

Benefits:
Virtualization in the data center has demonstrated real-world scalability and optimization for applications much more effectively than traditional dedicated platforms. These same attributes will also hold true for edge virtualization.

Edge Virtualization Feature Example: "Survivability and Performance"

Virtualization Feature Overview:
Virtualization not only yields a performance benefit, but also greatly simplifies and improves survivability and distribution (yielding further performance benefits). Survivability in a virtual environment means that even if any application(s) fail(s), the

hypervisor operating system, virtual machines, or other applications do not fail. Applications can be "spun" up in sub-second times when events cause an application, platform, or site failure. Additionally, because of network virtualization, these applications can be distributed across geographies both from a survivability and performance perspective.

Example Description:
From a performance perspective, traditional edge solutions have relied on proprietary and purpose-built hardware, resulting in high costs and underperformance. On the very low end of traditional edge solutions, most hardware is ARM-based, with minimal memory and storage. These solutions typically are purpose-built and rely on open-source applications with a small amount of software integration. Consequently, they are almost never capable of supporting the required performance of commercial or high-end applications. Additionally, because of their singular focus, they tend to be stand-alone devices incapable of surviving any type of failure. Two concrete examples running on the same platform are SDN-based networking and elastic cloud backup. The following figure represents these examples:

In the diagram, there are several points of survivability: 1) loss of connectivity to the data center, 2) platform loss, and 3) primary network loss. In each case the survivability components allow operations to continue, albeit at a reduced level (e.g., LTE speeds vs. Ethernet, routing with no updates, etc.).

Benefits:
Virtualization (platform and network) yields multiple levels of survivability and performance that are difficult to attain with traditional dedicated platforms.

Conclusion
Edge virtualization or MicroClouds can provide enterprises and SMBs with efficiencies that legacy, purpose-built appliances cannot even begin to achieve. The better management of application resources, simpler policy administration, automated application integration and orchestration, and improved scalability, survivability, and performance all lead to significant and measurable cost savings.

Managed service providers and distributed enterprises would both benefit from deploying an edge virtualization strategy. In an example use case scenario of 50 sites where MicroClouds were deployed, there was a 3:1 up-front CAPEX savings and a 5:1 average OPEX savings over 3 years.

Edge virtualization and SDN solutions are here today and ready for production deployments. Integrating them into today's enterprise data centers and SMB environments will establish a foundation for a more efficient, optimized and manageable network over the long term.

More Stories By Richard Platt

Richard Platt is CTO and vice president of engineering at Netsocket, where he is responsible for establishing the company’s technical vision and leading all aspects of its technology development. He has over 25 years experience defining, developing, and commercializing emerging technologies in both start-up and Fortune 100 environments.

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
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
It has never been a better time to be a developer! Thanks to cloud computing, deploying our applications is much easier than it used to be. How we deploy our apps continues to evolve thanks to cloud hosting, Platform-as-a-Service (PaaS), and now Function-as-a-Service. FaaS is the concept of serverless computing via serverless architectures. Software developers can leverage this to deploy an individual "function", action, or piece of business logic. They are expected to start within milliseconds...
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory? In her Day 2 Keynote at @DevOpsSummit at 21st Cloud Expo, Aruna Ravichandran, VP, DevOps Solutions Marketing, CA Technologies, was jo...
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.
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
The cloud era has reached the stage where it is no longer a question of whether a company should migrate, but when. Enterprises have embraced the outsourcing of where their various applications are stored and who manages them, saving significant investment along the way. Plus, the cloud has become a defining competitive edge. Companies that fail to successfully adapt risk failure. The media, of course, continues to extol the virtues of the cloud, including how easy it is to get there. Migrating...
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...
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...
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...
From manual human effort the world is slowly paving its way to a new space where most process are getting replaced with tools and systems to improve efficiency and bring down operational costs. Automation is the next big thing and low code platforms are fueling it in a significant way. The Automation era is here. We are in the fast pace of replacing manual human efforts with machines and processes. In the world of Information Technology too, we are linking disparate systems, softwares and tool...
DevOps is good for organizations. According to the soon to be released State of DevOps Report high-performing IT organizations are 2X more likely to exceed profitability, market share, and productivity goals. But how do they do it? How do they use DevOps to drive value and differentiate their companies? We recently sat down with Nicole Forsgren, CEO and Chief Scientist at DORA (DevOps Research and Assessment) and lead investigator for the State of DevOps Report, to discuss the role of measure...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
"As we've gone out into the public cloud we've seen that over time we may have lost a few things - we've lost control, we've given up cost to a certain extent, and then security, flexibility," explained Steve Conner, VP of Sales at Cloudistics,in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
These days, APIs have become an integral part of the digital transformation journey for all enterprises. Every digital innovation story is connected to APIs . But have you ever pondered over to know what are the source of these APIs? Let me explain - APIs sources can be varied, internal or external, solving different purposes, but mostly categorized into the following two categories. Data lakes is a term used to represent disconnected but relevant data that are used by various business units wit...
With continuous delivery (CD) almost always in the spotlight, continuous integration (CI) is often left out in the cold. Indeed, it's been in use for so long and so widely, we often take the model for granted. So what is CI and how can you make the most of it? This blog is intended to answer those questions. Before we step into examining CI, we need to look back. Software developers often work in small teams and modularity, and need to integrate their changes with the rest of the project code b...
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"Cloud4U builds software services that help people build DevOps platforms for cloud-based software and using our platform people can draw a picture of the system, network, software," explained Kihyeon Kim, CEO and Head of R&D at Cloud4U, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
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 ...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...