 So, good afternoon everybody, welcome to my short lightning talk today. I would like to talk about heat and how to get started, so this is more to get a brief overview or short introduction on heat and how to get started with it. My name is then Jela Ebert, I'm working for T-Systems. As you might have seen, we have our open telecom cloud product, we wear hairline sponsor, maybe you came to our booth and get some nice t-shirt. Also Christian Beren prepared this presentation with me, he's from Beta Cloud Systems Solutions, but unfortunately he cannot be here today, so you just have to take me. Well, as I mentioned, I would like to talk about heat. So I would tell you shortly what it is, some kind of terminology and what the concepts and architecture are and what is from my point an easy way to get started, to get in touch with heat, what you can do, what documentation, what templates are around and if we still have some time then I have a short video to show some simple presentation on how heat works. What is heat? I had a look around to find a really nice sentence about what heat is and I think this sentence has all in one about what it is. It's one of the main open stack projects and it's the orchestration component of open stack. So you can launch VMs and applications based on templates and I think one of the main things is like you can define your infrastructure as a code. So I just copied that from the open stack org site and yeah, I think that is the main thing heat provides. On the next page I would like to show you a really simple overview on how it works. So you have your template file there where you define how your infrastructure should look like and you have a command line, you have an API interface which then tells the heat engine what to do and the heat engine is yeah, let's say doing all the work and at the end you will have resources like VMs, you will have as an output or like networks, like IP addresses, like software deployments. These templates are YAML based format and yeah, they describe how your infrastructure should look like, means that you can reproduce your infrastructure every time with the same template which is quite neat. So coming to some terminology, we are talking about templates so they are in a special YAML format as I stated before and they describe how your VM, how your application should look like and these templates also define how the resources and the relationships between your VM, your software deployment, your IP address network should be. Within the templates you describe your resources so your VM, your network, your application, so these are represented by these little dots here and a stack is then a group of connected resources that means the stack is the whole thing you deploy. This is all the resources you created by one template are defined by a stack and this stack can be then managed by you with the appropriate heat commands. I was looking around to find a nice picture on how the heat architecture looked like and I thought that's at least an easy one and not so complicated one to see how it works. It's basically a different picture from what we saw on the first page so you have your template, you have an API or a dashboard where you have your rest calls and then this is being queued to the heat engine and the heat engine is the heart of it all which knows the function which knows how to treat the parameters, parse the templates and the heat engine is the one talking to all the other projects like Keystone, like Nova, what to do. So this is the main orchestration thing which is doing all the work. So let's have a look on how to get started. I think the first important thing is to understand how the template looks like and what are the important sections and what you should know. So a template has always the same structure. Do you see my mouse? No, okay. The first is the template version. This needs to be a valid version. This is described in the documentation. So 2015 is something a little bit older. For example, Ocata is 2017 or 224. And the template basically describes which features are available, which hot template to use. So with every release there will be also a new hot template version depending on what functions and features are available. Then you have a description. This is an optional parameter. It's of course nice if you write a template and someone else is going to use it then what is it doing? Then there is a parameter section where you can define all the necessary parameters. You can define default parameters like security group or which network to use or which SSA key to use. And the really important part is the resource part. There is where you define which resources you want to have created, like the VM for example. And the output section is quite nice to define what kind of output do you want to have when the resources have been created. For example, I'm going to create a VM. So it would be nice to have in the output section. This is the IP address to log in or this is the SSH key to log in. We will see how that works later. So I have prepared a really little example which does work. I tried that before. So this is a really, really basic example to create a VM. I just picked a template version and here in the have a short description, okay, simple hot template and in the resource description I say I like to have a VM. It's called my instance. It's of type OS Nova server. That's the resource type which he knows and I'll give that a few properties. So what kind of image to use, which flavor to use, which is my SSH key. If I have more than one subnet in my tenant, then it's good to specify a network otherwise he won't know which one to choose. But the last one, the user data format raw will tell that, for example, that this is not a software deployment, that the cloud init function should be deployed as or executed as they should be in a cloud. So you can define here if you want to have additional software deployments or not. Yes. So you can deploy that and at the end you will get a VM with an IP address and you can log into this. If you want to deploy it, you need to have a few commands. And I think from my point of view, these are the most relevant commands. You can have a stack list to see what kind of stacks you have. You have the stack create commands where you specify the template and the name. With stack show, you can see the output of how your stack looks like, what resources have been created. You can also see the events and, of course, you can also delete your stack. I just got a sign that I do not have that much time left. So I can maybe show the video to you if you like afterwards. But I will also provide it to this presentation. These are the few commands I used in my demo. And the video will be uploaded as well. So I have a tenant on my open telecom cloud running Ubuntu doing these commands. At the end, I would like to give you some really useful links on where you find heat template documentation, the official heat templates from openstack.org, where there are also application lamb stack heat templates, which are easy to use. We also are an open telecom cloud GitHub where you can find some simple templates. Thanks for your attention and listening to me this afternoon.