 Good afternoon everybody The brave few that are here Let me take a second just to introduce first of all Pete Chadwick who's at Sousa. He's a director Product management at Sousa for cloud and systems management. My name is Mark Smith I am a product marketing manager for Sousa OpenStack Cloud We got 20 minutes this afternoon just to talk about The importance of containers in an open-stack environment and we're going to talk about whether or not Containers will kill or cure open-stack So let me just start by Talking to you about something that all of you know already right containers are a hot topic. They're in the news all the time This is stuff. We're all aware of industry analysts news reports are talking about containers and their importance to The future business to cloud native workloads the fact that they're critical to the digital business of the future The support for containers will only grow throughout the whole of this year and Then they're now available container platforms are available on every public and private cloud Infrastructure to make sure that customers are well catered for So that's indisputable. There's a hype curve That involves containers all the time But within the open-stack community, they're also a hot topic. So just to put this into context. There are some News reports and some headlines that talk about If you have a container platform that can develop and host Containerized workloads. Why do you need open-stack? So will it kill open-stack? Well, we'll address that question today, but first of all Open-stack users see containers as the top emerging technology in the April 2017 user survey Over 75% of the users said it was their their top emerging technology 451 research say that containers being adopted three times faster on open-stack than Anywhere else in the enterprise market in fact 451 research that said that back in Barcelona for the summit Revised that recently in December to three to five times faster on open-stack Not only that Magnum is now in the top two projects of interest to all open-stack users You would get always called it the top one because it's 37% of users and the top one was 38% so right up there At the front of all of our minds. So let's just put that into context then We're going to role play this Pete is going to play the open-stack guy and I'm going to start as the business guy. So Pete Where do containers fit into open-stack? So I think there's two key issues To think about when you talk about containers. First of all, are you using containers to run applications or are you using? containers to be a service Delivery platform. So we see both things happening within open-stack So Mark already mentioned Magnum and that's really focused on how do I deploy Kubernetes as a service to then build Applications on top of there are also projects like cola and courier that are focused on how do I take the open-stack? Control plane and put that in the container and get all the benefits of easy scalability fault tolerance That you get with a containerized environment So in that perspective, I think both both types of containers have value and fit within the overall open-stack framework Okay, fair enough. Well, let me change my role then. Let me talk to you now as an operations guy Let's talk a little bit about service containers then. How do you build open-stack with service containers? And why would you want to do that? Sure, so there's two things when we talked about it on the previous screen is The value of doing that is the same reason that you'd want to build Containerized workloads anywhere easy portability You get some inherent scalability when you're using something like Kubernetes to manage your orchestrated environment And it and it just provides a simpler a simpler platform for your developers to build out either cloud native Or as we heard today in the keynotes even more legacy stateful applications and roll them out into a To a containerized environment the value of that is the isolation The lower resource utilization than you get with virtual machines and ultimately flexibility and portability The easiest way to do that today is with with Magnum as mark points out. It's one of the top two Top two projects in terms of intent for people to integrate We've already seen customers that have that have installed open-stack specifically to get access to Magnum Because they see it as a very a very powerful way to get access to containerized infrastructure and One of the real values that you get with running something like Kubernetes With Magnum is in an open-stack environment. You get full multi-tenancy today So that you can have each individual development team can have their own dedicated Kubernetes cluster Which is not easy to do with native Kubernetes Okay, thanks Pete. That's that's pretty clear. So let's let's talk about application containers that rather than service containers Which I think is what you're really touching on there Let's talk a bit more about how open-stack fits into that and and what a typical use case for With that would look for the service containers because I talked about application containers. Yeah, I got it backwards You did so from a service container point of view It really just taking taking looking at an open-stack as just an application It's composed of many different services Nova Cinder all the ones You know about and putting each one of those in its own individual container Gives you the same kind of flexibility that you get at the application level where you can You can have that orchestrated by something like Kubernetes so that you get automatic scale So if you're if your cloud grows and you need to add more control Capabilities to have more services more endpoints. You can do that in a fairly transparent transparent fashion Okay, so actually when you were talking about Application containers yes earlier. Yes Let's just talk a little bit about use cases in and and perhaps you could just talk us through what this is all about sure so This is really what we call Kubernetes as a service if you think about Magnum a lot of people talk about as containers as a service But it's not really I mean because it's it gives the end user in an open-stack environment the ability to spin up a cluster of machines orchestrated by heat Deploy Kubernetes on top of that and then have a fully orchestrated set of Cluster hosts of container hosts running virtual running on virtual machines The advantage is that each individual developer can spin up their own separate Kubernetes cluster You also get to benefit within open-stack Because you're using heat that if you start to see heavy demand on the virtual machines running the Kubernetes cluster I can spin up another virtual machine add it to the cluster spread the workload out So you get all the flexibility of a containerized environment with the infrastructure flexibility of open-stack Okay, that makes sense. All right, so let me go back to being a business guy then so That's kind of where we are today what you've just described so where are we going to head next we'll all workloads end up being containerized So no obviously we don't think that the there's a number of customers that have Existing workloads where they're running in virtual machines running on bare metal Then they may or may not see any value in containerizing them I think what's really going to be they're going to focus on is to the extent that you want to divorce your Infrastructure from the underlying or your applications underlying infrastructure. There's a couple ways to look at doing that We actually think that open-stack is the ideal platform to integrate all of your workloads whether it's a Stateful workload whether it's a cloud native workload or it's additional virtual machine The reason for that is that open-stack really has a set of abstraction tools that enable API sitting on top of the software-defined infrastructure We talked today. We saw a demo today in the keynote. We're running Cinder as a standalone service It's part of open-stack But I can run Cinder natively because it provides a set of API's that I can use to set up block devices whether I'm running a container or virtual machine Or a block device But then it abstracts all the different back ends that the storage providers are Enabling so that if I if I'm running that app or I'm running EMC or I'm running Suze enterprise storage which is which is a based upon Seth All of those have manila or sender plug-ins so I can automatically configure a block device and attach that to my workload Whether it's a container whether it's a virtual machine or whether it's a bare metal server So what you're really seeing is that open-stack and the set of projects that comprise open-stack become the unifying API or set of API's that allow you To easily use a software-defined infrastructure whether it's storage virtualization or or networking So really then brings everything together I do everything on one one platform absolutely perfect. Okay, so Let's look ahead a bit further. Let's take a slightly longer range view here then What does the future look like for containers and open-stack? Where are we going ahead as a community? I think they will live happily together forever after There's clearly a value for containers. There's clearly a value for virtual machines There's clearly a value for bare metal servers all of those can be unified within a single infrastructure That's managed by open-stack as we just talked about and so what we see going forward is you're going to have an application delivery layer that can either be used for Actually, you can build Straight infrastructures a server-based applications where I'm building my my workloads onto VMs I can use what we call a micro services the custom micro services app where I'm just building my own applications running directly on courier or on Kubernetes and containers or Ultimately, you'll start to bring in Capabilities such as cloud foundry have cloud foundry sitting on top of your containerized infrastructure providing a very opinionated but very productive application development environment for For the development teams all that sitting on top of a set of APIs in open-stack That'll enable you to get access to the private Software-defined infrastructure and at the same time extending over into public clouds that you can develop truly hybrid work Workloads that span both your data center and public cloud environments So you're actually saying and this is a software-defined infrastructure that will lead us to hybrid cloud. Yes Absolutely because of what you've just been describing. Okay that sounds pretty useful as a Future for open-stack in a containerized and non-containerized world. Yep. Okay. Very good. So one last question then Pete We started off by saying that a lot of people are saying that Containers if you have a platform that will host and allow you to develop containers Why do you need? Why do you need open-stack? So will containers kill open-stack? No, I as I mentioned earlier, I think that open-stack first of all consists of a number of different projects some of which will clearly make sense to be a set of APIs that abstract storage or abstract networking the way and Ideally as as Mark Collier was talking about if the communities come together and work together Instead of replicating all of the good things that something like Cinder has done In a containerized environment just take advantage of that and and reuse that But it also there's also capabilities where people are going to want to run virtual machines They're going to run one want to run bare metal servers and and having all of those Coordinated through all of the projects that open-stack provides. I think we'll continue to provide value Containers just enhance that overall value proposition and I'm going to sum up with everything that Pete just said there No So really good. Okay now you can tell I think from the few minutes We had to talk about containers and open-stack here That Pete knows what he's talking about We are on booth six Just a little ways over there We have a whole bunch of other systems engineers developers and technical people all involved with container as a service Kubernetes Magnum and open-stack, please if you'd like to come along and talk to us We'd be delighted to have a more in-depth conversation or you can just grab us as we get off the stage Thanks very much for everybody. Appreciate it