Welcome!

OpenStack Journal Authors: Mike Kavis, Liz McMillan, RealWire News Distribution, Jerry Huang, Kevin Benedict

Blog Feed Post

Networking Pidgin: The next step for abstractions?

There is a natural phenomenon that occurs when two groups lacking a common language come together. Essentially, the two groups construct impromptu a means of communicating. This new language pairs parts of the existing languages with new words, sounds, and body language. This new set of linguistic conventions becomes the primary means of communicating over time, allowing trade and exchange of information between the groups. This natural linguistic evolution creates what is called a pidgin.

There are lots of examples of pidgins, but the two that people are most likely familiar with are Hawaiian Pidgin (combining Hawaiian and English) and Louisiana Creole (English and French). Regardless of the languages of origin, pidgins have a common set of characteristics:

  • Uncomplicated clause structure (no nested clauses, for instance)
  • Reduction consonant clusters
  • Basic vowels like a, e, i, o, u
  • No tones
  • Use of separate words to indicate tense, usually preceding the verb (I done look would mean I had looked, for example)

These rules are all in support of simplification. The nuances of the languages are dropped in favor of a simplified, repeatable approach to communication. The result is something that sounds dumbed down to the casual listener. But that dumbing down was necessary to bring two uncommon languages together organically.

So how does this apply to networking?

One of the primary objectives of SDN is to make the network more tightly linked to the applications it serves. This might happen through service agility (automating workflows to shorten the time to provision a new service), or it might happen through the exchange of application requirements in more application-centric deployments. Whatever the exact manifestation, the question that often gets lost in the details is: How do the network and applications actually talk to each other?

To date, the answer is typically some derivative of There’s an API for that. But anyone who has worked with APIs knows that simply throwing up an interface does not mean that communication happens. If that API is too networking-centric, the application people are forced to either learn a new networking dialect or punt the work to the networking team. If the API is too application-centric, the networking people have to either learn application speak or they have to punt the work to the application team.

And the API discussion is really more about mechanics than communication. Sure, the API will ultimately relay information to parts of the system that request it, but it doesn’t necessarily define linguistically how the disparate entities ought to talk. So while product teams have been quick to solve the API problem, they have left the harder problem largely unaddressed. What we ought to be working more diligently on is the abstractions that allow the different groups to communicate. Put differently, we need to be creating our own networking-application pidgin.

But how do pidgins evolve? New languages need three things to evolve: necessity, proximity, and exposure.

There must be a need for the new language. When it is people, that need is typically trade. For IT, the need is driven by a shift from connectivity to experience. Tuning and ultimately guaranteeing application experience requires a common understanding of application requirements (likely in the form of SLAs). CIOs are well past the point that they can call out five 9s and declare success. There is clearly a need for something more.

Beyond need, the communicating partners must be in close proximity. For a language to develop, there has to be an interaction, which implies a physical proximity to each other. In the IT space, this proximity is likely defined at the intersection of infrastructure boundaries. Wherever a boundary exists, there is an interaction. These interactions define where and how language must evolve. In some cases, it might be the intersection of applications and networks, but there will also be similar boundaries between the network and storage, and the network and compute. This likely means that there is more than one pidgin that must evolve.

And finally, for a language to exist, there has to be prolonged exposure. A single interaction will not generate a pidgin. You need frequent contact over a sufficiently long period for a pidgin to emerge. Similarly, we should not expect that the relevant abstractions in networking will be formed after a coarse exchange of requirements. The reality is that these things take time – they are evolutionary. We need experience and iteration to derive the right set of linguistics. It simply cannot be the case that a single company goes out and derives all the abstractions on their own. The multiple parties need to co-exist for these to fully materialize.

Given these requirements, we ought to be asking how we make progress as an industry. The need for contact and exposure suggests that abstractions are not going to be developed within yet another silo. So where are the natural points that disciplines come together?

Right now, I don’t think these venues exist for the most part. But I do think they are forming. OpenDaylight’s first incarnation seems to be mostly network, but I could reasonably see supporting infrastructure coming together. It would make sense, for example, for analytics companies to join the effort. It might make sense for storage controller companies to join early to resolve the controller-controller communication that will be a necessity in the not-too-distant future. There are already obvious tie-ins with OpenStack.

Beyond OpenDaylight, I think there could be similar hope for Big Switch’s Floodlight efforts. They are similar in concept to OpenDaylight, and so they should be looking to attract more members from the supporting areas. We might also see collaboration coming out of the NFV efforts, though those relationships would appear to be between network or cloud services and the supporting infrastructure. And as the ONF takes on northbound interfaces, there might be still more opportunity for prolonged interaction between networking and non-networking folks.

It is not immediately clear to me which efforts are most likely to yield positive outcomes. The best I can do is conclude that we need to be making more explicit efforts to get disparate groups to talk. Without this type of communication, the appropriate pidgins will not be able to emerge. And it feels like a natural evolution is far more likely to succeed than a mandated abstraction cast down from one vendor or even one group of vendors.

As a customer, this means that you ought to be getting plugged into the various points of communication convergence. These will be the most likely to deliver a set of abstractions that serve as a unifying force. So go and take a look at OpenDaylight, Floodlight, NFV, OpenStack, TOSCA, and others. It very likely will be that we are still a ways off from a networking-application (or networking-storage, networking-computer, and so on) pidgin. But if one is going to emerge, it is only going to happen where two groups come together, so being at that intersection puts you in the best position to shape and ultimately adopt the output.

[Today's fun fact: Elephants are the only mammals that can't jump. This is contrary to the Wesley Snipes & Woody Harrelson classic White Men Can't Jump.]

To read more on this topic, check out:

The post Networking Pidgin: The next step for abstractions? appeared first on Plexxi.

Read the original blog entry...

More Stories By Michael Bushong

The best marketing efforts leverage deep technology understanding with a highly-approachable means of communicating. Plexxi's Vice President of Marketing Michael Bushong has acquired these skills having spent 12 years at Juniper Networks where he led product management, product strategy and product marketing organizations for Juniper's flagship operating system, Junos. Michael spent the last several years at Juniper leading their SDN efforts across both service provider and enterprise markets. Prior to Juniper, Michael spent time at database supplier Sybase, and ASIC design tool companies Synopsis and Magma Design Automation. Michael's undergraduate work at the University of California Berkeley in advanced fluid mechanics and heat transfer lend new meaning to the marketing phrase "This isn't rocket science."

Cloud Expo Breaking News
Simply defined the SDDC promises that you’ll be able to treat “all” of your IT infrastructure as if it’s completely malleable. That there are no restrictions to how you can use and assign everything from border controls to VM size as long as you stay within the technical capabilities of the devices. The promise is great, but the reality is still a dream for the majority of enterprises. In his session at 14th Cloud Expo, Mark Thiele, EVP, Data Center Tech, at SUPERNAP, will cover where and how a business might benefit from SDDC and also why they should or shouldn’t attempt to adopt today.
MapDB is an Apache-licensed open source database specifically designed for Java developers. The library uses the standard Java Collections API, making it totally natural for Java developers to use and adopt, while scaling database size from GBs to TBs. MapDB is very fast and supports an agile approach to data, allowing developers to construct flexible schemas to exactly match application needs and tune performance, durability and caching for specific requirements.
APIs came about to help companies create and manage their digital ecosystem, enabling them not only to reach more customers through more devices, but also create a large supporting ecosystem of developers and partners. While Facebook, Twitter and Netflix were the early adopters of APIs, large enterprises have been quick to embrace the concept of APIs and have been leveraging APIs as a connective tissue that powers all interactions between their customers, partners and employees. As enterprises embrace APIs, some very specific Enterprise API Adoption patterns and best practices have started emerging. In his session at 14th Cloud Expo, Sachin Agarwal, VP of Product Marketing and Strategy at SOA Software, will talk about the most common enterprise API patterns and will discuss how enterprises can successfully launch an API program.
The social media expansion has shown just how people are eager to share their experiences with the rest of the world. Cloud technology is the perfect platform to satisfy this need given its great flexibility and readiness. At Cynny, we aim to revolutionize how people share and organize their digital life through a brand new cloud service, starting from infrastructure to the users’ interface. A revolution that began from inventing and designing our very own infrastructure: we have created the first server network powered solely by ARM CPU. The microservers have “organism-like” features, differentiating them from any of the current technologies. Benefits include low consumption of energy, making Cynny the ecologically friendly alternative for storage as well as cheaper infrastructure, lower running costs, etc.
Next-Gen Cloud. Whatever you call it, there’s a higher calling for cloud computing that requires providers to change their spots and move from a commodity mindset to a premium one. Businesses can no longer maintain the status quo that today’s service providers offer. Yes, the continuity, speed, mobility, data access and connectivity are staples of the cloud and always will be. But cloud providers that plan to not only exist tomorrow – but to lead – know that security must be the top priority for the cloud and are delivering it now. In his session at 14th Cloud Expo, Kurt Hagerman, Chief Information Security Officer at FireHost, will detail why and how you can have both infrastructure performance and enterprise-grade security – and what tomorrow's cloud provider will look like.
Today, developers and business units are leading the charge to cloud computing. The primary driver: faster access to computing resources by using the cloud's automated infrastructure provisioning. However, fast access to infrastructure exposes the next friction point: creating, delivering, and operating applications much faster. In his session at 14th Cloud Expo, Bernard Golden, VP of Strategy at ActiveState, will discuss why solving the next friction point is critical for true cloud computing success and how developers and business units can leverage service catalogs, frameworks, and DevOps to achieve the true goal of IT: delivering increased business value through applications.
Web conferencing in a public cloud has the same risks as any other cloud service. If you have ever had concerns over the types of data being shared in your employees’ web conferences, such as IP, financials or customer data, then it’s time to look at web conferencing in a private cloud. In her session at 14th Cloud Expo, Courtney Behrens, Senior Marketing Manager at Brother International, will discuss how issues that had previously been out of your control, like performance, advanced administration and compliance, can now be put back behind your firewall.
More and more enterprises today are doing business by opening up their data and applications through APIs. Though forward-thinking and strategic, exposing APIs also increases the surface area for potential attack by hackers. To benefit from APIs while staying secure, enterprises and security architects need to continue to develop a deep understanding about API security and how it differs from traditional web application security or mobile application security. In his session at 14th Cloud Expo, Sachin Agarwal, VP of Product Marketing and Strategy at SOA Software, will walk you through the various aspects of how an API could be potentially exploited. He will discuss the necessary best practices to secure your data and enterprise applications while continue continuing to support your business’s digital initiatives.
The revolution that happened in the server universe over the past 15 years has resulted in an eco-system that is more open, more democratically innovative and produced better results in technically challenging dimensions like scale. The underpinnings of the revolution were common hardware, standards based APIs (ex. POSIX) and a strict adherence to layering and isolation between applications, daemons and kernel drivers/modules which allowed multiple types of development happen in parallel without hindering others. Put simply, today's server model is built on a consistent x86 platform with few surprises in its core components. A kernel abstracts away the platform, so that applications and daemons are decoupled from the hardware. In contrast, networking equipment is still stuck in the mainframe era. Today, networking equipment is a single appliance, including hardware, OS, applications and user interface come as a monolithic entity from a single vendor. Switching between different vendor'...
Cloud backup and recovery services are critical to safeguarding an organization’s data and ensuring business continuity when technical failures and outages occur. With so many choices, how do you find the right provider for your specific needs? In his session at 14th Cloud Expo, Daniel Jacobson, Technology Manager at BUMI, will outline the key factors including backup configurations, proactive monitoring, data restoration, disaster recovery drills, security, compliance and data center resources. Aside from the technical considerations, the secret sauce in identifying the best vendor is the level of focus, expertise and specialization of their engineering team and support group, and how they monitor your day-to-day backups, provide recommendations, and guide you through restores when necessary.
Cloud scalability and performance should be at the heart of every successful Internet venture. The infrastructure needs to be resilient, flexible, and fast – it’s best not to get caught thinking about architecture until the middle of an emergency, when it's too late. In his interactive, no-holds-barred session at 14th Cloud Expo, Phil Jackson, Development Community Advocate for SoftLayer, will dive into how to design and build-out the right cloud infrastructure.
You use an agile process; your goal is to make your organization more agile. What about your data infrastructure? The truth is, today’s databases are anything but agile – they are effectively static repositories that are cumbersome to work with, difficult to change, and cannot keep pace with application demands. Performance suffers as a result, and it takes far longer than it should to deliver on new features and capabilities needed to make your organization competitive. As your application and business needs change, data repositories and structures get outmoded rapidly, resulting in increased work for application developers and slow performance for end users. Further, as data sizes grow into the Big Data realm, this problem is exacerbated and becomes even more difficult to address. A seemingly simple schema change can take hours (or more) to perform, and as requirements evolve the disconnect between existing data structures and actual needs diverge.
SYS-CON Events announced today that SherWeb, a long-time leading provider of cloud services and Microsoft's 2013 World Hosting Partner of the Year, will exhibit at SYS-CON's 14th International Cloud Expo®, which will take place on June 10–12, 2014, at the Javits Center in New York City, New York. A worldwide hosted services leader ranking in the prestigious North American Deloitte Technology Fast 500TM, and Microsoft's 2013 World Hosting Partner of the Year, SherWeb provides competitive cloud solutions to businesses and partners around the world. Founded in 1998, SherWeb is a privately owned company headquartered in Quebec, Canada. Its service portfolio includes Microsoft Exchange, SharePoint, Lync, Dynamics CRM and more.
The world of cloud and application development is not just for the hardened developer these days. In their session at 14th Cloud Expo, Phil Jackson, Development Community Advocate for SoftLayer, and Harold Hannon, Sr. Software Architect at SoftLayer, will pull back the curtain of the architecture of a fun demo application purpose-built for the cloud. They will focus on demonstrating how they leveraged compute, storage, messaging, and other cloud elements hosted at SoftLayer to lower the effort and difficulty of putting together a useful application. This will be an active demonstration and review of simple command-line tools and resources, so don’t be afraid if you are not a seasoned developer.
SYS-CON Events announced today that BUMI, a premium managed service provider specializing in data backup and recovery, will exhibit at SYS-CON's 14th International Cloud Expo®, which will take place on June 10–12, 2014, at the Javits Center in New York City, New York. Manhattan-based BUMI (Backup My Info!) is a premium managed service provider specializing in data backup and recovery. Founded in 2002, the company’s Here, There and Everywhere data backup and recovery solutions are utilized by more than 500 businesses. BUMI clients include professional service organizations such as banking, financial, insurance, accounting, hedge funds and law firms. The company is known for its relentless passion for customer service and support, and has won numerous awards, including Customer Service Provider of the Year and 10 Best Companies to Work For.