 Hi everybody, I'm Mark Collier with the OpenStack Foundation, and I wanted to show you OpenStack Havana today, really focusing in on a couple of the new services that have been added. So I'm not going to go over some of the stuff I've shown you in the past with Grizzly and other releases, you can certainly go back and look at those videos, but I thought you'd mostly want to hear about what's new, particularly around these two services. Now those services are OpenStack Orchestration and OpenStack Metering, and along the way I'll point out a few other nice improvements, but I'm really going to focus in on those for this video. So one of the things we've done is actually improved the display up here of the resources utilization. So right now, of course, I'm not using any resources, I haven't kicked off any orchestration or started any instances, but as we do that, you'll see that change. So I'm going to go ahead and dive straight in here to orchestration. So this is here on the Project tab, which is the view that most end users will have, and you'll see orchestration and then stacks. So the stacks are really these templates in the OpenStack Orchestration system. It's also known as HEAT, that's the code name, so you may hear the term HEAT from time to time. But OpenStack Orchestration is what you'll see here in the dashboard. So the first thing you need to understand about this is that it's a template system, template-driven system, and that really helps you automate a lot of the complex deployment. So in this particular case, I'm going to use this template that was up on GitHub, there's quite a few up there. And this one is designed to launch a couple of servers to power a WordPress site. So pretty common. WordPress powers a lot of the web. And so here we are utilizing the OpenStack Orchestration system to go ahead and launch this. And so this will be my WordPress stack. And I'm going to go ahead and click rollback on failure, so if there's a problem, it will rollback automatically for me, so that's really nice. Set a password and then, of course, set the key for the Keystone. So I'm going to go ahead and launch this stack. And you'll see here in a few minutes we'll have created these two instances. Now one of them is for the database and the other is for the front end of the application. So pretty common. And over time, of course, you may grow to much bigger deployments. I'm running this here on my laptop. So I've created this cloud with DevStack, which is something many of you may be familiar with. It's quite a popular way to create a small cloud to kick the tires and see what it's like and do some testing. So in this particular case, I'm only going to create a couple of smaller instances. And you'll start to see those showing up here on the instance tab. So now we've actually got both of these instances running. And it says WordPress Stack, so it tells you which stack it is along with the fact that this is the web server and this is the database server. And that was all set up in that template, including the type of image that we were using, which in this case is a Fedora 17. And the type of size was configured there when we kicked that off. And if I go back into the stacks view under orchestration, I can actually see visually what my servers are doing here. So of course, small deployment. This will be even more useful when you have hundreds of servers and you can see visually how they've been deployed here by the orchestration system. And as you look at the overview to get more details on what you've deployed and the resources, again, this becomes even more useful as you have bigger deployments. But you can see the database server and the web server that we created. And you can see the status. The events, again, are going to be pretty self-explanatory here. We recorded an event that there's kicked off a process to create the server. And then when it was complete, that was recorded here. So that kind of gives you a little sense for what the orchestration, OpenStack Orchestration system is all about. One of the new things that's available in OpenStack Havana is actually the ability to resize your instance. So go ahead and show you that as we go along here. So I'm going to make this instance a little bit bigger. So going from a small to a medium size flavor. Flavors are, of course, the configurations of memory and disk that you set up for your users in the admin view. So they can figure out what the flavors are they can choose from. So we're going to make that a little bit bigger. Let's assume, for example, that our database server is just really getting hammered right now and we find out that that is an area that we need to add more resource to. So we are able to resize it here in real time. So while that's happening, I'll go ahead and show you the other big news here in Havana, which is the OpenStack metering service. So that's going to be shown here in the admin tab, which is really where the operators live, as opposed to the end users. And right here under the resource usage tab, that's where you're going to look. And we'll see here that I don't have a lot of resources that I'm using. Because again, we just spun up a couple of instances here on this small cloud. But it does give you a view into all this type of data. So the disk, networking, object storage, usage. And this becomes really useful for both public and private cloud scenarios. So in a public cloud, of course, you want to know what your users, i.e. your customers are doing, so you can charge them appropriately. And all this data is being collected and reported back. And we're just seeing, of course, the dashboard view into it. But a lot's going on behind the scenes. And that data is available through APIs. You can plug it into other types of monitoring systems. You can actually plug it into the OpenStack orchestration engine to provide auto-scaling, for example. So you may have a metering, OpenStack metering alarm that can tell you, OK, this server is getting overutilized. Why don't you go ahead and spin up more web servers on the front end? And so you can work those two new capabilities and tandem to actually provide auto-scaling. So as applications are becoming more cloud-aware, OpenStack is becoming more application-aware. So I think that's pretty cool. And that gives you a little sense for what's happening here from the resource perspective in the OpenStack metering. Now, if I go back here to my projects tab, let's take a look at this instance that I was resizing and see how it's going. So the last step here, when it's just about done, is it wants to ask you to confirm that you're sure you want to do this. And I said yes, and boom, it's done. So that gives you a little bit of a sense for some of the new capabilities. One last thing I'll show you before I sign off is that we can now not just boot from volume, but we can actually boot the instance from an image or volume snapshot in such a way that it creates a new volume in the process. So almost like a cloning situation here. So you can quickly spin up a new instance that's just like the old one, but you keep the old one as well. So that's a nice capability, as well as availability zone. So as you set up your cloud in different regions, whether it's geographical or different parts of your data center, and you actually configure availability zones, you want to have the end users that have the ability to target those availability zones. And now they can do that right here in the dashboard. So with that, I'll just sign off and say, again, I'm Mark Collier with the OpenStack Foundation, and I hope you have a good time with OpenStack.