Image Title

Search Results for OpenStack Summit 2013:

Dimitrios Stiliadis - OpenStack Summit 2013 - theCUBE


 

okay we're back live here at the OpenStack summit in Portland Oregon I'm John furry the founder SiliconANGLE comment rose mykos Dave a latte from Wikibon org this is silicon angles the cube our flagship program we go out to the events and extract the signal from the noise and certainly here OpenStack there's not a lot of noise but a lot of signal a lot of developers a lot of use cases really really the Alpha geeks the practitioner is really putting new technology into place to power this modern era of computing cloud mobile and social David Floria we're here with Demetri stilly at us from nudge networks and mountain view welcome to the cube thank you David I want to get your take on this before we set up this interview because honestly we've heard from right scale there in the management side just previous we've had Rackspace on earlier there on the Omni on the provider side we had big switch-on software-defined networking and now Dimitri's company the software is eating the world what's your take on the SDN market right now relative to OpenStack relative to open saying well what you're clearly wanting to do in every part of it is separate out all of the different layers and you ought to be able to separate out the physical and the the logical and the the software is the way that that's going to be done so instead of having to have a switch which is a piece of hardware and the software you want to separate the two out so that you have the logical function and the physical function from from the two pieces so that's very important to be able to contribute to every layer take new technologies along with you and then define the software element of that as the piece that you keep constant as technologies themselves adjust so durable code we walk manageable and build on and we clean can take advantage of new technologies as they come along and obviously I coming back to you what are you contributing what I think needs to be contributing was the white space in that area that you're going after right so see when people started thinking about the cloud and OpenStack and to always kind of think they they quickly realize that the network is a fundamental piece right you have to start with the network you have to interconnect your components and so on the angle that we are taking is yes it's good with in your data center within your cloud you have to create this network services interconnect applications and so on but much more importantly you need to be able to dynamically connect these applications with your existing network services right so you have a large amount of enterprise VPN services you have hybrid clouds coming out so you need to be able the moment you activate a network service in the data center to be able to seamlessly interconnect this now with your enterprise side with other network services in other data centers in other clouds and so on right so the network is always a network of networks and we have to bring everything together we cannot just restrict ourselves with is the confinements of a single administrative model so that's that's a fundamental part of what we are trying to to bring here together okay and so how are you fitting in with the the network layer right so our view is say that first of all we need to talk both both languages if you don't think of it as a as a translation thing right so we need to understand the language of the cloud we need to understand the language of the application developers in the cloud they want to use some abstract mechanism to define their network services and install them if you want in the hypervisors and OpenStack quantum seems to be the prevalent way to do that so that's language number one but then we have all these thousands of networks out there where their language is bgp so what we are doing is we are marrying the two we allow you to codon define services in OpenStack and we allow you to define the mekinese between interconnect the service is automatically with all the other networks that are out there right so I call it sometimes we are just translating between languages all right a language translator live from an application point of view they want to consume resources and previously networks and the computers were the main things they consumed but it seems now that sorry computing and storage with the main things they consumed but it now it seems that networks themselves have to pay a much bigger role in providing a quality of service to those places Rick you've got a quality of service down in the nano seconds when you get to the server level and used to have milliseconds for the for the storage side it's now coming down to micro second what are you doing to make sure that that quality of service no it is not just the bandwidth but it's also the latency are you planning to marry that see the weight datacenter networks of all these people are quickly realizing that the same if you want principles that we used in order to build the Internet itself can be used inside the data center so if you think about the internet right in the internet there is voice services that is video services there is all these other services running and they are actually running by assuming you have a well-engineered IP network and then you run the service is at the edges if you want all that you push all the intelligence at the edges it's the same thing where the network on the data center is going the data center network becomes a very scalable IP fabric it it is very well managed if you want very well traffic engineer and you push the edges at the hypervisors you push essentially the services at the hypervisors where traffic is differentiated so if you see for example a tenant misbehaving you are going to block him at the hypervisor layer if you're going to provide us or map different tenants to different classes of traffic it's happening at the hypervisor so the center of the network behaves like a scalable IP fabric and all the intelligence it's pushed around the edges and the reason you want to do that is because this allows you the ultimate scalability right the network or doesn't need to know about every flow that goes into the through through the corner of the network there right you don't need to know the IP addresses of virtual machines you don't need to know what individual virtual machines no need to know I want to do there you just need to worry about aggregates so you can engineer and scale the core make it very cheap and because you make it very tip you can increase the capacity at the core and you can say distribute all the intelligence at the edges of the network right but so you said that you can do the hypervisor and that's obviously on the compute side that side of it but what about the data network isn't that a don't you need to regulate the priorities and flex all the data through and isn't that today that's that's a very big part of it yes but it is still happening at the hypervisor right the the first touch of it enough an application with a network it is not anymore the top of rack sheets let's say on the data center but it does it is actually the hypervisor virtual sheets right that's the first time that you see a packet when a packet comes out of a virtual machine the first time you see it is at the hypervisor itself and at this layer when the first time you see the bucket of the hypervisor itself is where you apply all your policies right in other words the edge of the network is not the hardware is not the switch on the top of rack the edge of the network is inside the server now ok yeah ok excellent so I want to ask you we have a couple minutes left here I wanted we have two minutes less I want to get your perspective on the state of the business around OpenStack what is your view ok because your chief architects you're looking at the tech yes and you but you have to intersect the business objectives what are you seeing as the core business drivers that are that are causing you to make your technology in a certain way right so it's clear that what people want to do is they they want to provide this ability to their end users to consume services rapidly right that is what is driving this call OpenStack development and more important the community came together in order to unify view on the core engine and the core AP is in order to make this consumption of services very easy and in order to allow the application developers to move from one cloud to the other and so on right what we do is what we try to do is in addition is expanding view on this model amazing the network as consumable as the storage and compute facilities right and I'm not talking just about the network in the data center I'm talking about also the network in the way that the service in the data center of a cloud provider will interconnect with the enterprise read if you see then the next if you want Holy Grail that everybody is talking about is the hybrid cloud the hybrid cloud is only possible if you can connect the network and the services in the service provider cloud with a network and services in the in the in the enterprise itself right so they what links the two together is the network so we have to make this network to be consumable final question for you is actually DevOps is a mindset we heard from right scale that that adoption is in mainstream enterprises and service providers but the word infrastructure as code is becoming more popular outside of the the geeks and the album the architects the coders what in your mind how would you describe infrastructure as code to the folks out there give it a try it's okay no right answer it's a moving target that's what it is realities it's that the applications and code is a living organization it's constantly changing and you cannot assume at any point it's static right it's not there it's not the good old days if you want and that's what it really means right it's a living organism it it will constantly adapt to the new to the new requirements out there like switches in the old days you knew exactly ports and you you knew i was going now it's all kinds of weird stuff happening right it's all stuff you you have to be you you have to accept change if you want right so it's the actually there is a there is an okay Isaac Asimov code right there another the author of the science fiction yes that's the only constant is change yeah we should be no project just on the network genome here Software Defined Networking Dmitry stylianos thanks for jumping inside the cube again you're here like with a lot of the chief architects making things happen congratulations thanks for joining us thank you we'll be right back with more analysis from David's lawyer after the at break on a breakdown day 1 and day chu here in more depth from the analysts here at opens Dec 2 SiliconANGLE Gibbons exclusive coverage of OpenStack summit be right back

Published Date : Apr 16 2013

**Summary and Sentiment Analysis are not been shown because of improper transcript**

ENTITIES

EntityCategoryConfidence
DavidPERSON

0.99+

Isaac AsimovPERSON

0.99+

Dimitrios StiliadisPERSON

0.99+

David FloriaPERSON

0.99+

two piecesQUANTITY

0.99+

Dec 2DATE

0.99+

first timeQUANTITY

0.99+

twoQUANTITY

0.99+

both languagesQUANTITY

0.99+

bothQUANTITY

0.98+

Dmitry stylianosPERSON

0.98+

first touchQUANTITY

0.98+

DimitriPERSON

0.98+

DavePERSON

0.97+

OpenStackTITLE

0.97+

todayDATE

0.97+

WikibonORGANIZATION

0.95+

thousands of networksQUANTITY

0.95+

OpenStack Summit 2013EVENT

0.95+

firstQUANTITY

0.93+

OpenStackEVENT

0.92+

singleQUANTITY

0.92+

OpenStack summitEVENT

0.92+

a couple minutesQUANTITY

0.87+

Demetri stillyPERSON

0.86+

two minutes lessQUANTITY

0.84+

one cloudQUANTITY

0.83+

every layerQUANTITY

0.82+

Portland OregonLOCATION

0.81+

a lot of signalQUANTITY

0.77+

a lot of developersQUANTITY

0.77+

SiliconANGLEORGANIZATION

0.76+

John furryPERSON

0.76+

RackspaceORGANIZATION

0.72+

micro secondQUANTITY

0.7+

GibbonsPERSON

0.66+

nano secondsQUANTITY

0.66+

OpenStackORGANIZATION

0.65+

day 1QUANTITY

0.61+

OmniORGANIZATION

0.59+

noiseQUANTITY

0.59+

theCUBEORGANIZATION

0.57+

a lotQUANTITY

0.54+

partQUANTITY

0.52+

oneQUANTITY

0.48+