Click here to close now.




















Welcome!

Microservices Expo Authors: AppDynamics Blog, Liz McMillan, Trevor Parsons, Lori MacVittie, Roger Strukhoff

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
The Internet of Things. Cloud. Big Data. Real-Time Analytics. To those who do not quite understand what these phrases mean (and let’s be honest, that’s likely to be a large portion of the world), words like “IoT” and “Big Data” are just buzzwords. The truth is, the Internet of Things encompasses much more than jargon and predictions of connected devices. According to Parker Trewin, Senior Director of Content and Communications of Aria Systems, “IoT is big news because it ups the ante: Reach out ...
"We got started as search consultants. On the services side of the business we have help organizations save time and save money when they hit issues that everyone more or less hits when their data grows," noted Otis Gospodnetić, Founder of Sematext, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
Auto-scaling environments, micro-service architectures and globally-distributed teams are just three common examples of why organizations today need automation and interoperability more than ever. But is interoperability something we simply start doing, or does it require a reexamination of our processes? And can we really improve our processes without first making interoperability a requirement for how we choose our tools?
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
How do you securely enable access to your applications in AWS without exposing any attack surfaces? The answer is usually very complicated because application environments morph over time in response to growing requirements from your employee base, your partners and your customers. In his session at @DevOpsSummit, Haseeb Budhani, CEO and Co-founder of Soha, shared five common approaches that DevOps teams follow to secure access to applications deployed in AWS, Azure, etc., and the friction an...
Digital Transformation is the ultimate goal of cloud computing and related initiatives. The phrase is certainly not a precise one, and as subject to hand-waving and distortion as any high-falutin' terminology in the world of information technology. Yet it is an excellent choice of words to describe what enterprise IT—and by extension, organizations in general—should be working to achieve. Digital Transformation means: handling all the data types being found and created in the organizat...
This week, I joined SOASTA as Senior Vice President of Performance Analytics. Given my background in cloud computing and distributed systems operations — you may have read my blogs on CNET or GigaOm — this may surprise you, but I want to explain why this is the perfect time to take on this opportunity with this team. In fact, that’s probably the best way to break this down. To explain why I’d leave the world of infrastructure and code for the world of data and analytics, let’s explore the timing...
The Software Defined Data Center (SDDC), which enables organizations to seamlessly run in a hybrid cloud model (public + private cloud), is here to stay. IDC estimates that the software-defined networking market will be valued at $3.7 billion by 2016. Security is a key component and benefit of the SDDC, and offers an opportunity to build security 'from the ground up' and weave it into the environment from day one. In his session at 16th Cloud Expo, Reuven Harrison, CTO and Co-Founder of Tufin,...
You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.
JavaScript is primarily a client-based dynamic scripting language most commonly used within web browsers as client-side scripts to interact with the user, browser, and communicate asynchronously to servers. If you have been part of any web-based development, odds are you have worked with JavaScript in one form or another. In this article, I'll focus on the aspects of JavaScript that are relevant within the Node.js environment.
Discussions about cloud computing are evolving into discussions about enterprise IT in general. As enterprises increasingly migrate toward their own unique clouds, new issues such as the use of containers and microservices emerge to keep things interesting. In this Power Panel at 16th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the state of cloud computing today, and what enterprise IT professionals need to know about how the latest topics and trends affect t...
SYS-CON Events announced today that HPM Networks will exhibit at the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. For 20 years, HPM Networks has been integrating technology solutions that solve complex business challenges. HPM Networks has designed solutions for both SMB and enterprise customers throughout the San Francisco Bay Area.
Summer is finally here and it’s time for a DevOps summer vacation. From San Francisco to New York City, our top summer conferences list is going to continuously deliver you to the summer destinations of your dreams. These DevOps parties are hitting all the hottest summer trends with Microservices, Agile, Continuous Delivery, DevSecOps, and even Continuous Testing. Move over Kanye. These are the top 5 Summer DevOps Conferences of 2015.
Countless business models have spawned from the IaaS industry. Resell Web hosting, blogs, public cloud, and on and on. With the overwhelming amount of tools available to us, it's sometimes easy to overlook that many of them are just new skins of resources we've had for a long time. In his General Session at 16th Cloud Expo, Phil Jackson, Lead Technology Evangelist at SoftLayer, broke down what we've got to work with and discuss the benefits and pitfalls to discover how we can best use them to d...
Puppet Labs has published their annual State of DevOps report and it is loaded with interesting information as always. Last year’s report brought home the point that DevOps was becoming widely accepted in the enterprise. This year’s report further validates that point and provides us with some interesting insights from surveying a wide variety of companies in different phases of their DevOps journey.
Containers are changing the security landscape for software development and deployment. As with any security solutions, security approaches that work for developers, operations personnel and security professionals is a requirement. In his session at DevOps Summit, Kevin Gilpin, CTO and Co-Founder of Conjur, will discuss various security considerations for container-based infrastructure and related DevOps workflows.
Microservices are hot. And for good reason. To compete in today’s fast-moving application economy, it makes sense to break large, monolithic applications down into discrete functional units. Such an approach makes it easier to update and add functionalities (text-messaging a customer, calculating sales tax for a specific geography, etc.) and get those updates / adds into production fast. In fact, some would argue that microservices are a prerequisite for true continuous delivery. But is it too...
What we really mean to ask is whether microservices architecture is SOA done right. But then, of course, we’d have to figure out what microservices architecture was. And if you think defining SOA is difficult, pinning down microservices architecture is unquestionably frying pan into fire time. Given my years at ZapThink, fighting to help architects understand what Service-Oriented Architecture really was and how to get it right, it’s no surprise that many people ask me this question.
"ProfitBricks was founded in 2010 and we are the painless cloud - and we are also the Infrastructure as a Service 2.0 company," noted Achim Weiss, Chief Executive Officer and Co-Founder of ProfitBricks, in this SYS-CON.tv interview at 16th Cloud Expo, held June 9-11, 2015, at the Javits Center in New York City.
One of the ways to increase scalability of services – and applications – is to go “stateless.” The reasons for this are many, but in general by eliminating the mapping between a single client and a single app or service instance you eliminate the need for resources to manage state in the app (overhead) and improve the distributability (I can make up words if I want) of requests across a pool of instances. The latter occurs because sessions don’t need to hang out and consume resources that could ...