Welcome!

Virtualization Authors: Elizabeth White, Carmen Gonzalez, Victoria Livschitz, Pat Romanski, Lori MacVittie

Related Topics: Virtualization, Cloud Expo

Virtualization: Blog Feed Post

The Cloud Metastructure Hubub

How Infrastructure 2.0 might leverage publish-subscribe technology like PubSubHubub to enable portability of applications

Pieter_Bruegel_TowerBabel
Tower of Babel by Pieter Bruegel the Elder.
One of the topics surrounding cloud computing that continues to rear its ugly head is the problem of portability across clouds. Avoiding vendor lock-in has been problematic since the day the first line of proprietary code was written and cloud computing does nothing to address this. If anything, cloud makes this worse because one of its premises is that users (that’s you, IT staff) need not concern themselves with the underlying infrastructure. It’s a service, right, so you just use it and don’t worry about it.

Let’s assume for a moment that you can easily move applications from data center to cloud to cloud. Plenty of folks are working on that, but very few of them address the “rest of the story”: the metastructure.

Metastructure contains the metadata that describes the network, application network, and security infrastructure providing all those “don’t worry about” services cloud providers offer. Load balancing, firewalls, IPS, IDS, application acceleration, secure remote access. If you’ve spent time with your cloud provider tweaking those services – or configuring them yourself – then moving to a new cloud provider is not only a huge investment in time, it’s actually going to be painful because you’re essentially going to have to recreate every metastructure configuration again.

Yes, you’ve done this inside your own data center for years. Every forklift replacement or upgrade of infrastructure has come with its own load of baggage in the configuration arena. Switching out vendor equipment – especially core components – can be extremely painful, especially when configurations need to essentially be “translated” between them. But cloud makes this worse because technically speaking you don’t even have access to the existing configurations. You can’t see them, you can’t have them, and you can’t run them through whatever “upgrade” or “migration” script your new vendor offers to ease the process.

Are you depressed yet?

There’s been some talk of including metastructure data with the virtual machine, but the problem with this is that it almost always requires that the meta data be wrapped up using a proprietary API, such as is provided by VMware. That’s okay if you restrict yourself to only cloud providers that use the same virtualization technology, but not okay if you want to be able to make a move from one technology to another. It also assumes that the metadata is specific to the infrastructure, which is even more unlikely when moving between cloud providers.


HOW ABOUT A CLOUD-BASED CMDB (Configuration Management Database)?


There are several ongoing efforts to address this very scenario because it is so painful. Most of them would, if adopted, require vendors to implement support for a specific standard so that configurations can be managed and exchanged in that standard format. That makes sense, that’s how we’ve always handled translation of data between disparate systems that don’t speak the same language. In the application world we call the process of mapping one format to another “integration” and you can easily evoke a look of terror on a co-worker’s face just by saying the word within their range of hearing. Go ahead, try it. Just make sure they aren’t carrying anything heavy that can be easily thrown at you when you do.

CMDB (Configuration Management Database) technology is another method of addressing the problem of, well, managing configurations. These solutions store configuration of a wide variety of infrastructure solutions – from routers and switches to web and application servers to application delivery controllers. They do a great job of managing configuration and can even “push” configuration out to devices if so desired. But the configurations stored and managed in a CMDB are product-specific, not generic, so they can’t adequately today address the problem of portability.

You can probably see where this is going: a cross between CMDB and a nice, industry-wide standard would probably do the trick, wouldn’t it? And if it was public (in the sense that any application or service is public on the network – that is, accessible via the Internet to any cloud provider or customer site) then cloud providers and organizations alike could take advantage of that configuration management mechanism and use it to their advantage. Portability becomes possible rather than fantasy.


PUBSUBHUBUB


Cloud providers and organizations alike are likely to stop right there. Sharing configuration of infrastructure and core components is just asking for trouble. If ever such a cloud-based CMDB were compromised, well…let’s just say it would be A Very Bad Thing.

But what if the actual metadata, the configuration information, were stored either in the enterprise or the cloud provider (or both), and merely pushed and pulled via a public mechanism on-demand?  Configuration isn’t changed all that often and if an organization is moving between clouds they certainly know when they’re doing it. If there was some mechanism through which metastructure could be published and to which infrastructure could subscribe then when changes were made or providers changed that metastructure data could be easily grabbed from the public cloud-CMDB system (cloud catalog, anyone?) and interpreted into product-specific configuration by the products themselves.

Think of  it like SOA clients pulling WSDL (Web Services Description Language) from a UDDI (Universal Description, Discovery, and Integration) server. The SOA client pulls the WSDL, which describes the service(s), configures itself appropriately, and then is able to make use of those services. The intent of introducing UDDI was a service-catalog that could be polled on-demand to provide the latest information about the service and describe it in an abstract, vendor-neutral way such that any client could access any service, regardless of implementation language or environment. Sounds a lot like what we want for infrastructure portability, doesn’t it?

PUBSUBHUBHUBThat’s where PubSubHubub comes in. While this draft standard for a publish-subscribe system is generally being leveraged by software developers to enable faster sharing of information across the Internet, it is also a fine example of a system that could be used by infrastructure 2.0 solutions to share metastructure. Consider the existence of a public PubSubhubub Hub, like Google’s public PubSubHubub Hub, and how it might be leveraged to share metastructure between clouds or the organization and the cloud.

Note that XMPP is used today by at least one cloud provider to enable distributed cloud management in a nature very similar to that of PubSubhubhub.

In any case, the specific implementation of the configuration “hub” is relatively unimportant; what’s important is that (a) customers can publish a vendor-neutral metastructure to an isolated channel that communicates their specific infrastructure needs and (b) providers can subscribe, at will, to customer topics and retrieve metastructure in a way that allows their infrastructure to in turn configuration itself (or be configured by the provider’s system, as is required by the provider’s implementation).

Early on it would be necessary for the cloud provider to provide the “translation” and configuration services simply because even if a metastructure standard existed today (and it doesn’t) it would take months and possibly years before all the possible infrastructure vendors were able to update their systems to interpret the standard. If the provider implements a configuration “gateway”, however, he can immediately take advantage of such a standard and use existing skills and knowledge gained from its automation and orchestration of its cloud to configure the infrastructure appropriately based on the metastructure. This has the added advantage of “hiding” the infrastructure implementation from the outside world, which for some providers is a very important thing to do.


SOME CONFIGURATIONS ARE INHERENTLY VENDOR SPECIFIC


That’s okay for two reasons: first, we ensure that the metadata description is XML-based, because it’s extensible. If we build into the standard a way to extend it naturally such as is provided with XML the interpreters (configuration “gateways”) can either (a) translate if it can or (b) ignore.

Consider the use of OVF (Open Virtualization Format) to further describe what is called a Virtual Machine Contract (VMC):

For each virtual system, the associated metadata is described in a set of specific sections. The VirtualHardwareSection describes the virtual hardware required including the amount of memory, number of CPUs, information about network interfaces, etc. The OperatingSystemSection describes the guest operating system that will run in the virtual system. The ProductSection provides basic information such as the name and vendor of the appliance and can also specify a set of properties that can be used to customize the appliance.

While VMC is very basic at this point, it’s a good start at providing the foundation for building out a more complete, standards-based description of the metastructure necessary to configure an infrastructure to deploy a specific application in a virtual machine format. Using this as the basis for metadata exchange – when fully described – via a public hub could alleviate most of the issues with sharing infrastructure metadata (metastructure) across clouds in a generally vendor non-specific manner. In other words, portability of both the virtual machine and the specific infrastructure configurations necessary to optimally execute and deliver the application to the end user in the most fast and secure manner possible.

We’re nowhere near this point, by the way. VMC needs to be fleshed out as far as standard metadata goes for infrastructure (perhaps a good chore for the SRI Infrastructure 2.0 Working Group) and vendors would need to adopt and extend out the ProductSection of VMC for product specific configuration that isn’t included in the base format. And PubSubHubub would need to be proven to be a secure method of exchanging the metastructure across clouds. What is likely is that as we move forward trying to extend the plateau of collaboration down the stack toward the core infrastructure is that a new set of tools, products, solutions, and services will emerge to fill the unavoidable gaps in the standards, e.g. a service-based cloud configuration hub offering translation of proprietary metastructure data to some other proprietary metastructure data.

Perhaps there’s a better way overall, and OVF/VMC and PubSubHubub will simply remain in our memories as the catalyst and template for a different set of standards providing portability across clouds. But there is a way to provide this level of portability and collaboration across clouds, across the infrastructure and the application. The need – and perhaps more importantly the belief that it’s necessary to address the need – is growing.

UPDATE: Christofer Hoff pointed out that vCloud has been submitted to the DMTF for standardization, technically making it "open" rather than "proprietary." It is still only implemented by VMware technologies, so for the time being it might as well be proprietary, but this may change in the future.

Follow me on Twitter View Lori's profile on SlideShare friendfeedicon_facebook AddThis Feed Button Bookmark and Share

Related blogs & articles:

More Stories By Lori MacVittie

Lori MacVittie is responsible for education and evangelism of application services available across F5’s entire product suite. Her role includes authorship of technical materials and participation in a number of community-based forums and industry standards organizations, among other efforts. MacVittie has extensive programming experience as an application architect, as well as network and systems development and administration expertise. Prior to joining F5, MacVittie was an award-winning Senior Technology Editor at Network Computing Magazine, where she conducted product research and evaluation focused on integration with application and network architectures, and authored articles on a variety of topics aimed at IT professionals. Her most recent area of focus included SOA-related products and architectures. She holds a B.S. in Information and Computing Science from the University of Wisconsin at Green Bay, and an M.S. in Computer Science from Nova Southeastern University.

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.


@ThingsExpo Stories
Cultural, regulatory, environmental, political and economic (CREPE) conditions over the past decade are creating cross-industry solution spaces that require processes and technologies from both the Internet of Things (IoT), and Data Management and Analytics (DMA). These solution spaces are evolving into Sensor Analytics Ecosystems (SAE) that represent significant new opportunities for organizations of all types. Public Utilities throughout the world, providing electricity, natural gas and water, are pursuing SmartGrid initiatives that represent one of the more mature examples of SAE. We have s...
The security devil is always in the details of the attack: the ones you've endured, the ones you prepare yourself to fend off, and the ones that, you fear, will catch you completely unaware and defenseless. The Internet of Things (IoT) is nothing if not an endless proliferation of details. It's the vision of a world in which continuous Internet connectivity and addressability is embedded into a growing range of human artifacts, into the natural world, and even into our smartphones, appliances, and physical persons. In the IoT vision, every new "thing" - sensor, actuator, data source, data con...
How do APIs and IoT relate? The answer is not as simple as merely adding an API on top of a dumb device, but rather about understanding the architectural patterns for implementing an IoT fabric. There are typically two or three trends: Exposing the device to a management framework Exposing that management framework to a business centric logic Exposing that business layer and data to end users. This last trend is the IoT stack, which involves a new shift in the separation of what stuff happens, where data lives and where the interface lies. For instance, it's a mix of architectural styles ...
The 3rd International Internet of @ThingsExpo, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that its Call for Papers is now open. The Internet of Things (IoT) is the biggest idea since the creation of the Worldwide Web more than 20 years ago.
The Internet of Things is tied together with a thin strand that is known as time. Coincidentally, at the core of nearly all data analytics is a timestamp. When working with time series data there are a few core principles that everyone should consider, especially across datasets where time is the common boundary. In his session at Internet of @ThingsExpo, Jim Scott, Director of Enterprise Strategy & Architecture at MapR Technologies, discussed single-value, geo-spatial, and log time series data. By focusing on enterprise applications and the data center, he will use OpenTSDB as an example t...
An entirely new security model is needed for the Internet of Things, or is it? Can we save some old and tested controls for this new and different environment? In his session at @ThingsExpo, New York's at the Javits Center, Davi Ottenheimer, EMC Senior Director of Trust, reviewed hands-on lessons with IoT devices and reveal a new risk balance you might not expect. Davi Ottenheimer, EMC Senior Director of Trust, has more than nineteen years' experience managing global security operations and assessments, including a decade of leading incident response and digital forensics. He is co-author of t...
The Internet of Things will greatly expand the opportunities for data collection and new business models driven off of that data. In her session at @ThingsExpo, Esmeralda Swartz, CMO of MetraTech, discussed how for this to be effective you not only need to have infrastructure and operational models capable of utilizing this new phenomenon, but increasingly service providers will need to convince a skeptical public to participate. Get ready to show them the money!
The Internet of Things will put IT to its ultimate test by creating infinite new opportunities to digitize products and services, generate and analyze new data to improve customer satisfaction, and discover new ways to gain a competitive advantage across nearly every industry. In order to help corporate business units to capitalize on the rapidly evolving IoT opportunities, IT must stand up to a new set of challenges. In his session at @ThingsExpo, Jeff Kaplan, Managing Director of THINKstrategies, will examine why IT must finally fulfill its role in support of its SBUs or face a new round of...
One of the biggest challenges when developing connected devices is identifying user value and delivering it through successful user experiences. In his session at Internet of @ThingsExpo, Mike Kuniavsky, Principal Scientist, Innovation Services at PARC, described an IoT-specific approach to user experience design that combines approaches from interaction design, industrial design and service design to create experiences that go beyond simple connected gadgets to create lasting, multi-device experiences grounded in people's real needs and desires.
Enthusiasm for the Internet of Things has reached an all-time high. In 2013 alone, venture capitalists spent more than $1 billion dollars investing in the IoT space. With "smart" appliances and devices, IoT covers wearable smart devices, cloud services to hardware companies. Nest, a Google company, detects temperatures inside homes and automatically adjusts it by tracking its user's habit. These technologies are quickly developing and with it come challenges such as bridging infrastructure gaps, abiding by privacy concerns and making the concept a reality. These challenges can't be addressed w...
The Domain Name Service (DNS) is one of the most important components in networking infrastructure, enabling users and services to access applications by translating URLs (names) into IP addresses (numbers). Because every icon and URL and all embedded content on a website requires a DNS lookup loading complex sites necessitates hundreds of DNS queries. In addition, as more internet-enabled ‘Things' get connected, people will rely on DNS to name and find their fridges, toasters and toilets. According to a recent IDG Research Services Survey this rate of traffic will only grow. What's driving t...
Connected devices and the Internet of Things are getting significant momentum in 2014. In his session at Internet of @ThingsExpo, Jim Hunter, Chief Scientist & Technology Evangelist at Greenwave Systems, examined three key elements that together will drive mass adoption of the IoT before the end of 2015. The first element is the recent advent of robust open source protocols (like AllJoyn and WebRTC) that facilitate M2M communication. The second is broad availability of flexible, cost-effective storage designed to handle the massive surge in back-end data in a world where timely analytics is e...
Scott Jenson leads a project called The Physical Web within the Chrome team at Google. Project members are working to take the scalability and openness of the web and use it to talk to the exponentially exploding range of smart devices. Nearly every company today working on the IoT comes up with the same basic solution: use my server and you'll be fine. But if we really believe there will be trillions of these devices, that just can't scale. We need a system that is open a scalable and by using the URL as a basic building block, we open this up and get the same resilience that the web enjoys.
We are reaching the end of the beginning with WebRTC, and real systems using this technology have begun to appear. One challenge that faces every WebRTC deployment (in some form or another) is identity management. For example, if you have an existing service – possibly built on a variety of different PaaS/SaaS offerings – and you want to add real-time communications you are faced with a challenge relating to user management, authentication, authorization, and validation. Service providers will want to use their existing identities, but these will have credentials already that are (hopefully) i...
"Matrix is an ambitious open standard and implementation that's set up to break down the fragmentation problems that exist in IP messaging and VoIP communication," explained John Woolf, Technical Evangelist at Matrix, in this SYS-CON.tv interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
P2P RTC will impact the landscape of communications, shifting from traditional telephony style communications models to OTT (Over-The-Top) cloud assisted & PaaS (Platform as a Service) communication services. The P2P shift will impact many areas of our lives, from mobile communication, human interactive web services, RTC and telephony infrastructure, user federation, security and privacy implications, business costs, and scalability. In his session at @ThingsExpo, Robin Raymond, Chief Architect at Hookflash, will walk through the shifting landscape of traditional telephone and voice services ...
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at Internet of @ThingsExpo, James Kirkland, Chief Architect for the Internet of Things and Intelligent Systems at Red Hat, described how to revolutioniz...
Bit6 today issued a challenge to the technology community implementing Web Real Time Communication (WebRTC). To leap beyond WebRTC’s significant limitations and fully leverage its underlying value to accelerate innovation, application developers need to consider the entire communications ecosystem.
The definition of IoT is not new, in fact it’s been around for over a decade. What has changed is the public's awareness that the technology we use on a daily basis has caught up on the vision of an always on, always connected world. If you look into the details of what comprises the IoT, you’ll see that it includes everything from cloud computing, Big Data analytics, “Things,” Web communication, applications, network, storage, etc. It is essentially including everything connected online from hardware to software, or as we like to say, it’s an Internet of many different things. The difference ...
Cloud Expo 2014 TV commercials will feature @ThingsExpo, which was launched in June, 2014 at New York City's Javits Center as the largest 'Internet of Things' event in the world.