Best Practice for Deploying Applications in SDN Environments

Comments: 0 Runtime: 2:28 Posted: April 13th, 2015

Each tier of an application has specific needs. Today, there are rules for how three-tiered applications connect to each other and the outside world. In an SDN environment, we need templates for scripting those rules in order to automate the way we deploy applications.  

view video transcript

Each tier of application has specific needs, whether it needs to access to the outside world or to another tier, and the connectivity between these tiers, that creates a template. If I want to deploy this three tiered application, there are rules that today are in place already. These are the rules of how this three tiered application communicates between the tiers and outside.

What SDN does is okay, this is how you're configuring today. Today it's manual, and that's where the ticket comes in, and somebody goes and provisions. What SDN allows you is to script that. You basically define the application with its tiers and the connectivity, and what we call a template, an application template.

Basically, all you're doing is actually just automating the way you deploy applications today. Whatever application you have in the [inaudible 00:00:58] center, the tiers, how they connect to each other, how do they connect to the outside world, you would build a template.

The good thing about a template approach is that you define it once, and then you replicate many times. That takes the manual piece out of it, reducing [at our 01:16] rates, and improving the speed with which you deploy applications. You create a template that resembles what you have today, but the difference is that you can instantiate your application developer can use that template that you, the network or the security guy, has created for his application, and they can deploy it multiple times.

Now, the benefit there is not for the application guy only, but for the network and security guys from a compliance standpoint. Meaning that if they need to modify the way these tiers talk to each other after they've instantiated a thousand instances of this, they just go to the template, modify it, and it automatically gets updated to all these one thousand instances.

Not necessarily you're building something completely new. You're just basically moving workloads that you have today, relationships that you have today, into this SDN environment, but you only do it once, and then you basically distribute and replicate it over and over again with, still, full control, yet flexibility. That's it.

Written by Hussein Khazaal
Business Development, Nuage Networks

With over a decade of experience in the telecommunications industry, Hussein Khazaal is responsible for building the Nuage Networks Partner Ecosystem.