 OK, so we have like a short time. So I guess we just started. So hi, everyone. I'm Riko Lim. I'm a heat PTO. Then here is also previous heat PTO. And he's a very senior heat core and also a TC member now. So this session is about heat project update, what we do in less cycle, what we plan to do next, and what we might help for you guys to understand the project. So what is heat? You might already see this, and the adoption is for taking long while ago. I believe we got better adoption nowadays. Whatever you're using, you're using Sahara, then you're using heat. You're using Magnum, you're using heat. You're using Parkour, you're using heat. So we are behind everywhere, ha ha. And so we got the documents for the general heat information and the document for our release note. We're trying to update what we think the user need to know. We're trying to update with our release note. So if you have anything you want to see about what we've been doing, you can also check the release note as well. And today's slide will be on the OpenStake Foundation will release the slide. So you can read it. And first of all, thanks for everyone who helped to commit and who helped to review and who helped whatever, like sending emails, giving their feedbacks. We got user feedback as well. So thanks for everyone. And if your name is still not on top of it, it's fine. But you already get a sticker, so that means you have to do it now. So yeah, we need more help. Sorry, I will share the link out maybe later. But yeah, it's hyperlink. But we need help. What I mean we need help, we need people help us to review. We need people to help us to commit. And we need more core reviewers. So if anyone interesting in provide developer operator into a heat project, we are welcome everyone. We have onboarding session tomorrow. So if you're interesting in heat, you please join us. We also got the cross-project forum with sending about auto-scheduling tomorrow as well. So if you feel interesting, you can join us. So let's talk about the Rocky feature. So we have a new feature mostly about a new property, like a property for the zone container for the neutron subnate. We have the different properties about like neutron subnate so the segment ID becomes updatable. And also the new attributes which you might want to use. And we have some attribute improvement for the basically networking in heat. I mean we have other bug improvements for the neutron resource as well, which is because a lot of users are using neutron in heat but they want to be more flexible to have the relationship with other neutron resources. And we have a new resource type called OSHeatDelate. OSHeatDelate, we usually have a resource called test resource. That test resource is capable to feed in some property, sorry, parameters and allow to delay your process during the entire create or update process. Like for example you want to create an instance and delay like waiting for a while and then create other stuff. Then now you can use the OSHeatDelate resource which implement by then and it will allow you to like have a time freeze for your entire process. It also actually has a... Yeah, a random delay in some cases will help. And for the stack API support for feature a template on sweet container, which we have also shared that on the user feedback session earlier, so you're usually capable to provide your template and those files that you need to put into the heat directly in your local file or you provide the URL, entirely URL which must be accessible. But now you can directly using SWIFT as a backend. So you provide the entire container information, SWIFT container information to heat and then heat will load those files in that container. So you don't have to provide other file information anymore. You just give the information in sweet, we will go load it and create your stack for you. And for rocket feature, the first that we move to the storyboard, so don't find the launchpad anymore, trying to find us in the storyboard which is more usable and is more user friendly. So just go there and you will find it like more easy for you to typing your story, your bug and your blueprints and another to declare that heat is capable to do the federation identity. We usually, there is some time that we clear ourselves that incapable to integrate it with Keystone federation, identity federation, but it turns out that we actually capable and which we have some core to actually validate and it seems working. So let's say now we actually for, I assume for a long time actually capable to do federation with heat. Since pike, okay, since pike then. And one of the known issue is the key pair resource. So it's basically is about all the user domain resource. When you have like user domain, like a key pair is specifically created and allow to access just by the user. So let's get a scenario when you have a user create a key pair and that you also create a double instance in your stack. Now you're using another user, that key pair will not be accessible by the second user, but he allowed to access the stack, which makes no sense. So we put it on the known issue now, but it's like you either maybe work wrong and create the same key pair for your second user or we might be able to help you with our one of our, our one of our feature called observable reality, which you can check it out in heat. It basically help you to recreate a key pair if you don't have it. So other things that we, since Selometer Client is removed and so we remove the Selometer Client plugin and so some of the resource is hidden because there's new resource comes out and is more reasonable to use. So make sure you're aware of that of it. And for the new things that we have something in progress, like we have like a multi-cloud support. The patch is still, sorry, the patch is already there. So if you're interested, I like check out the patch. So I'm going, I will spend a little time right after the session, I will create a short link for you guys right away. So sorry about the hyperlink thing. And to, we have a lot of validate improvements and we have like a new resource like, like Blaster resource, Betrage also, the Betrage team also have ideas to have Betrage resource in heat. So which we still underplan with Betrage team together, but the sound of the implementations are already there in the heat. And the starting X project is very friendly trying to more get more integrated with OpenStack. So there's a guy from, very nice guy from starting X actually helped us to bring the features in the starting X, the different implementation in starting X and trying to merge that in the heat as well. So we got some very interesting improvements. We also got some, I still else a very nice improvement from the trip over thing, which is from some of our Red Hat guys and they actually help the new heat service more solely than before, like we fix a lot of bug. So it's getting more and more stable nowadays. And we got like new resource in progress like new tone L2 gateway resource. That will be something that we are currently have patches and we're trying to keep push it. For something that on the plan, that will be to like improve auto scheduling and auto healing integration, which in tomorrow we're going to have talk about auto scheduling with something as well if you're interested in joining us. And we also thinking about the, to improve the documentations, which we aware we have some documentation it's kind of like out of date and we got some very cool new feature, but it's like we're trying to keep rethinking what we can help the user to adopt our project and make it like smoothly as possible. And for, we also trying to implement the notifications for when you call, when you're using the thermometer to do the event notifications or when you trying to using other like monoscot or any project you're trying to have like a notification inside of heat. We have a lot of talk with some other project like monoscot team, like Octavia team about for example like auto scheduling scenario, how it's the auto scheduling work with monoscot, with thermometer, with other stuff. So we have some talk in our PDG and you will see those log in our PDG is a path. So if you have the idea or if you are wondering what we are doing here as a plan to do, that you can go to check our PDG as well that they will bring you some of the information, more detailed information on the discussions and something that we promise to working but we block it is the ETCD support which is for internal heat service usage. We think it might be very useful to bring some of our log management into ETCD management but we kind of a lake of a resource right now and so if anyone interesting bring their resource to us like developer, user feedback and for any kind of resource that if you're interesting on any kind of thing you wish it to be mission accomplished and help us. And so how you get the feedback? So either you can join us on IRC, we have calls in the cluster global. So you're usually capable to find us if not then you're trying to refine us and keep trying and we definitely get the responsible to answer your questions or trying to solve the issues and for you can also document it down like we have this ESA path so make sure that your use case is getting noticed or you can try to find our forum ESA path that for earlier the heat user feedback if you have anything about heat, good or bad or are crazy ideas just tell us. We are more than welcome for everyone to help us to improve it and you can file a story in the storyboard or and any way you can find or you can just grab the Zen here and just you know he's friendly so buy him a beer and he'll solve your questions he'll solve your problems and so that's like basically the same information but we need more reviewers, we need people to help us to if you have issues put it on the storyboard we have a really snow out like we frequently updated and so yeah I think that we have meeting weekly like even if it's not weekly we definitely going to have some guy there at the meeting time so you can see like office hour you can just jump in you actually can jump in to find us like anytime you want we were trying to make it more comfortable for you so I guess that's all I'm going to share here so any so we got two other sessions tomorrow and that's all I want to share so any questions, yes please use the microphone please I'm just a standard open stack heat user and I have a question or let's say you mentioned about placing the heat templates in a swift packet that's great feature actually just wanted to know is it project scoped or is it one side plus templates that are available to all users in the open stack? You want to answer it? It's project scopes, yeah so yeah normal access control on the swift container applies so heat will access the swift container using the user credentials that you supply when you create the stack it's the same as everything else that he talks to so yeah Any questions? Questions about multi-cloud support and multi-cloud support So the question is more details about multi-cloud support and by the way that is the shielding for this entire presentation so Do you want to take multi-cloud support Rika since you're writing it or do you want me to do it? Yeah you can do it So if you're familiar with the multi-region stacks that we have now so you create OS heat stack resource and you can specify it a remote region it's that but you can also specify another cloud and to do that to authenticate to the remote cloud you'll put your credentials into barbican and give heat the idea of the barbican secret and it will go retrieve the secret from barbican log into the other cloud and create this remote stack in the remote cloud that was kind of the the existence of barbican was kind of the thing that prevented us from doing multi-cloud for a long time because we already had that idea in mind but we didn't know where the user could put their secret and we didn't want it in heat so barbican is a safe place to store that so that's what we're doing so that's how it works Okay so So I guess that's it then this order for the project presentation we will be here tomorrow as well and we have sessions tomorrow so if you got more like you want to share you want to know more detail or you want to share anything with us or you have any crazy idea or you happen to know where it's have the good beers or good something and please come to us we are friendly so thanks everyone Thanks everybody