 Hello, and welcome to our little demo stage here today. Hopefully your design summit and the summit all together has gone as well as ours has so far. We're here today to talk a little bit about Denabi and Curvature, which you may have seen over at the Cisco booth already. And we're going to try to give a little bit of a demo and try and get some people to understand a bit more what Curvature and Denabi is about. So Curvature is our new age graphical interactive front end that we've been building over the last six months for OpenStack. We found that when people were using OpenStack, they were finding it very complicated. There was a lot of data on the screen when using Horizon. So we tried to abstract that out and give a bit more of a focus on what's actually running on your OpenStack and how things are connected together. And then we're going to show a little bit about Denabi as well, which is our container structure, which allows people to deploy using saved blueprints, complex topologies, and build other topologies using saved blueprints. So what I'm going to do now is I'm going to pass over to Brad, who is going to show you a demo of the main body of Curvature. Yep. So we're going to attempt a live demo, fingers crossed. And we're just going to show you, first of all, exactly what Curvature looks like. So as you can see here, very familiar to anyone that's used Horizon. This is our login screen. We hit Keystone with our Keystone credentials. And we get back the service catalog, and that's how we determine all the endpoints of what to connect to. So it's a very simple configuration for anyone running this all you need is your Keystone IP address. And you're presented with this, which is a network topology of what is already on our OpenStack deployment at the moment. But before I go into that, I'm just going to talk a little bit about the tools you can see in the upper left. So that's where we do the main interaction with Curvature. So you have the link tool, which used to define a lot of the networking between components. They're removed, obviously, to mark things for deletion. Then you can see an images tab, which contains a list of all of your images from Glantz. We're just using DevStack here, so there's just a Cirrus image. The network tab, which shows a list of all of the layer 2 and layer 3 network components from Quantum. So a router and a network. But also, as things like load balance as a service, and firewall as a service comes in, there can be nodes in there for those things. Containers, which we're going to talk about with Denabe, and volumes, which is a list of all of your Cinder volumes. So in terms of what's actually on the graph, you've got this big world icon. And if we just turn on node labels, that will help you see exactly what's going on. So the one marked public, that represents our external network, our public network. Then you have the router icons, which are the two test icons there. And then you have three networks. And the networks are represented by the little cloud. And they have a color around them so that you can easily see exactly what is inside a network. So we've got a whole bunch of VMs which are running inside each of those different networks. And this is particularly useful if you have a virtual machine running in two networks. So if we just link one of those up, then it's really visible both by the link, but also the overlapping the holes, the colors overlap. And that looks particularly horrible because everything is kind of overlapping there. But if you wiggle it about a bit, which is quite nice, then it all seems to sink into place. So let's walk through a little bit of a deployment using Curvature. So first thing we're going to do is we're going to have a virtual machine inside a network connected to a router, connected to the external network. And we're going to go ahead and deploy that. So we're going to go over to the Images tab and we're just going to drag on an image. It's very simple. Now we're going to drag on a network for that image to be inside. So we're going to give that a name and associate a CIDR for the first subnet in that network. And we're going to hit the random button and hit Save. Then we're going to grab the link tool and we're going to connect that virtual machine inside that network. So we can see that the virtual machine is now inside that network and we're going to grab a router as well and just place that on the graph and connect those up. So at the moment you can see everything's blue and that represents an undeployed state. We haven't actually communicated with OpenStack in terms of building these components at the moment. And that's because we want to concentrate on building out and designing your topology before you deploy it so that you can make changes and so on. So now if we wanted to deploy that, we just hit the big deploy button and the curvature will go off and it will make REST calls to OpenStack, hit all of the APIs and deploy it. So you can see the network and the router have gone black indicating that they are deployed and the virtual machine is orange because it's in a build state. And that's essentially how we can visualize all of the different components of OpenStack and we also get this nice interactive live feedback. Now what we might want to do that we have this topology is we might want to give that virtual machine a floating IP address. So we associate floating IPs based on the external network and we can just double click the external icon, allocate a new floating IP from its allocation pool. That's already happened, that's gone off to OpenStack and now we can click on any VM that has a path to that external network and we can selects from a list of floating IP addresses that have been assigned and associate that virtual machine with that floating IP address. Hit save and then that's all good. Now we can also do lots of other cool things like if you click on any node you'll be able to see a list of information like such as its IP addresses, the type of image it was, bring up a VNC console. We have a bunch of security things to do with key pairs and security groups which we'll probably go into more depth. I'll talk on Thursday, but now's a good time to segue over to Denarbe which is a way of storing some of these networks, apologies. So yeah, let's show how we've integrated Denarbe with Curvature and what Denarbe is, is a platform that sits separately from Curvature that allows you to design a network topology with VMs, level two routers and networks and save and reuse that. So if we go ahead and open the new container builder, we'll start off with a very simple container. You can see we've got all the same controls that we have on the main graph. So if we add, say, two VMs and a network, we can drag those on, configure a network with a random CIDR, in this context that means each instance of this container will get a different CIDR for that and we can link them up in the same way. So what we want to do now as well is also mark the network as what we call an endpoint and what this will do is expose that component on the outside of this container so that we can connect things to this container externally. So if we hit save and call this bottom layer, we can see if we go up to the container tools that that is ready to deploy, but we're not going to. We're going to explore a more complex container case. So if we hit the new container button again, we can see that we've got the containers tab and we can add containers to containers. So if we add two instances of this, you can see the endpoint exposed on the outside there, colored green. We can add a router, network those up as you would expect with the two networks attached to the router and mark that again as an endpoint and if we save that as top layer. So what this does is these components haven't been deployed yet. That has just generated a blueprint and save that in the Denr Bay component using its REST API. So let's go ahead and deploy the top layer container on our graph. Again, same as before, you can see the containers on the graph, the endpoint exposed on the outside. We want to connect that to the XNet and the blue state indicates that it's undeployed. So let's go ahead and deploy that container. So this takes a minute. So what's happening now is we've contacted Denr Bay to ask for this container blueprint to be deployed and that will handle the deployment of the networks, routers, VMs and all the containers inside it. And you can see it's gone black to indicate that that's up. So if we double click, we can take a look inside. We can drill further down the container structure and if we click one of these VMs, we can see that it's got data. We can click the network or we can do the VNC. That just shows that that's up. And yeah, that's curvature with Denr Bay. Thank you very much. So, sorry. So yeah, so if you just want to click through to the next point, that's kind of a basic overview of a quick demonstration of a standard workflow using curvature and Denr Bay. If you'd like to learn more about either of those services, we have a full presentation session on Thursday, 1150 AM, room C120. There's some information on the Cisco website either of those two URLs or if you just search for open stack curvature with the first link that pops up or come along to the booth and say hello. We've got loads to say about either of these and we'd love to hear your questions. So thank you.