Welcome!

Microservices Expo Authors: Elizabeth White, Liz McMillan, Yeshim Deniz, Carmen Gonzalez, Pat Romanski

Related Topics: Containers Expo Blog, Microservices Expo, @CloudExpo, @BigDataExpo, 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
Culture is the most important ingredient of DevOps. The challenge for most organizations is defining and communicating a vision of beneficial DevOps culture for their organizations, and then facilitating the changes needed to achieve that. Often this comes down to an ability to provide true leadership. As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership abi...
The essence of cloud computing is that all consumable IT resources are delivered as services. In his session at 15th Cloud Expo, Yung Chou, Technology Evangelist at Microsoft, demonstrated the concepts and implementations of two important cloud computing deliveries: Infrastructure as a Service (IaaS) and Platform as a Service (PaaS). He discussed from business and technical viewpoints what exactly they are, why we care, how they are different and in what ways, and the strategies for IT to transi...
Without a clear strategy for cost control and an architecture designed with cloud services in mind, costs and operational performance can quickly get out of control. To avoid multiple architectural redesigns requires extensive thought and planning. Boundary (now part of BMC) launched a new public-facing multi-tenant high resolution monitoring service on Amazon AWS two years ago, facing challenges and learning best practices in the early days of the new service.
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
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.
As software becomes more and more complex, we, as software developers, have been splitting up our code into smaller and smaller components. This is also true for the environment in which we run our code: going from bare metal, to VMs to the modern-day Cloud Native world of containers, schedulers and micro services. While we have figured out how to run containerized applications in the cloud using schedulers, we've yet to come up with a good solution to bridge the gap between getting your contain...
As organizations realize the scope of the Internet of Things, gaining key insights from Big Data, through the use of advanced analytics, becomes crucial. However, IoT also creates the need for petabyte scale storage of data from millions of devices. A new type of Storage is required which seamlessly integrates robust data analytics with massive scale. These storage systems will act as “smart systems” provide in-place analytics that speed discovery and enable businesses to quickly derive meaningf...
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 his Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, will explore t...
DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, explored HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
With major technology companies and startups seriously embracing Cloud strategies, now is the perfect time to attend @CloudExpo | @ThingsExpo, June 6-8, 2017, at the Javits Center in New York City, NY and October 31 - November 2, 2017, Santa Clara Convention Center, CA. Learn what is going on, contribute to the discussions, and ensure that your enterprise is on the right path to Digital Transformation.
Everyone wants to use containers, but monitoring containers is hard. New ephemeral architecture introduces new challenges in how monitoring tools need to monitor and visualize containers, so your team can make sense of everything. In his session at @DevOpsSummit, David Gildeh, co-founder and CEO of Outlyer, will go through the challenges and show there is light at the end of the tunnel if you use the right tools and understand what you need to be monitoring to successfully use containers in your...
What if you could build a web application that could support true web-scale traffic without having to ever provision or manage a single server? Sounds magical, and it is! In his session at 20th Cloud Expo, Chris Munns, Senior Developer Advocate for Serverless Applications at Amazon Web Services, will show how to build a serverless website that scales automatically using services like AWS Lambda, Amazon API Gateway, and Amazon S3. We will review several frameworks that can help you build serverle...
The IT industry is undergoing a significant evolution to keep up with cloud application demand. We see this happening as a mindset shift, from traditional IT teams to more well-rounded, cloud-focused job roles. The IT industry has become so cloud-minded that Gartner predicts that by 2020, this cloud shift will impact more than $1 trillion of global IT spending. This shift, however, has left some IT professionals feeling a little anxious about what lies ahead. The good news is that cloud computin...
SYS-CON Events announced today that HTBase will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. HTBase (Gartner 2016 Cool Vendor) delivers a Composable IT infrastructure solution architected for agility and increased efficiency. It turns compute, storage, and fabric into fluid pools of resources that are easily composed and re-composed to meet each application’s needs. With HTBase, companies can quickly prov...
An overall theme of Cloud computing and the specific practices within it is fundamentally one of automation. The core value of technology is to continually automate low level procedures to free up people to work on more value add activities, ultimately leading to the utopian goal of full Autonomic Computing. For example a great way to define your plan for DevOps tool chain adoption is through this lens. In this TechTarget article they outline a simple maturity model for planning this.
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations might...
The rise of containers and microservices has skyrocketed the rate at which new applications are moved into production environments today. While developers have been deploying containers to speed up the development processes for some time, there still remain challenges with running microservices efficiently. Most existing IT monitoring tools don’t actually maintain visibility into the containers that make up microservices. As those container applications move into production, some IT operations t...
For organizations that have amassed large sums of software complexity, taking a microservices approach is the first step toward DevOps and continuous improvement / development. Integrating system-level analysis with microservices makes it easier to change and add functionality to applications at any time without the increase of risk. Before you start big transformation projects or a cloud migration, make sure these changes won’t take down your entire organization.
Software development is a moving target. You have to keep your eye on trends in the tech space that haven’t even happened yet just to stay current. Consider what’s happened with augmented reality (AR) in this year alone. If you said you were working on an AR app in 2015, you might have gotten a lot of blank stares or jokes about Google Glass. Then Pokémon GO happened. Like AR, the trends listed below have been building steam for some time, but they’ll be taking off in surprising new directions b...
@DevOpsSummit has been named the ‘Top DevOps Influencer' by iTrend. iTrend processes millions of conversations, tweets, interactions, news articles, press releases, blog posts - and extract meaning form them and analyzes mobile and desktop software platforms used to communicate, various metadata (such as geo location), and automation tools. In overall placement, @DevOpsSummit ranked as the number one ‘DevOps Influencer' followed by @CloudExpo at third, and @MicroservicesE at 24th.