 Hi, thank you for joining us for Newton Design Series. And with me today, I've got Thomas talking about the heat project. Thomas, can you please introduce yourself? Sure. So I'm Thomas Hervé. I've been working at Vedette for about two years now and working on the heat project for the past three. I work from home, at the Palace. Thank you for joining us. Can you tell us a little bit about what heat is as a project? Sure. So heat is an orchestration tool. What it does is it allows you to basically describe a cloud application using a declarative language. It's basically a different way to interact with your open-set cloud. You can use the common line. You can use a horizon. And heat is another way to actually interact with your cloud. And the idea is to be more repeatable and more declarative so that you can do things more complex. And heat manage the details for you like dependencies and tries to handle updates and things like that. Got it. So we're about a month after the Austin Design Summit. So what were some of the hot topics that your team discussed and what were the outcomes and those discussions? Right. So I think we had two main actions in the summit. One is a long-term refactoring that we've been working on, which we call internally convergent. Some might expose that term to users, but it's a bit confusing to them. There's a really nice summit video about it, actually. So to make it short, convergence is a different way that we are trying heat to spawn up resources. Right now, we kind of do the built-in approach, trying to load everything at all. And convergence is a bit more iterative. And it allows us to do interesting things, like unlink spanners more and more nicely so that you can recover external spanners. And it also allows us to accept updates during the actual deployment so that you can change things right away without waiting for all the things to be deployed. We've been working on that subject for almost two years and it's almost to the point that it's ready. And so we're trying to figure out the details so that we can actually make that the default model. And heat is being used by other projects in OpenStack, for example, Chipolo, Magnum, Sarah. So the focus for the next month, I think, is can we activate that and make sure that we don't break those projects and let it work too seamlessly for them. And related to that, another important topic for us is performance. The project I mentioned are actually deploying some relatively big things and heat is somewhat struggling sometimes when you have several hundred resources and be able to maintain cover time to update it. So we want to make sure that we handle those loads very well and that we can actually go a notch and actually handle even things even better. So yeah, I think that's a positive to improve the focus of the project. Got it, thank you. And I think the list will be pretty similar, but what are some of the user needs or problems that you've heard that you're trying to solve in this Newton cycle? Yeah, I think performance was definitely something that we heard about. And there are always things that we need to improve at the time of the level so that people can do more things and be more efficient in the way they're declaring that they're deploying. So we're actually also working on that, but it's more least of small things than a general thing that we can do. Got it. And so if you were to give me a list of, you know, the top three priorities, if you will, for either new features or enhancing existing features within heat during Newton, what would that list be? So yeah, the list, the top of the list converges and there being convergence is obviously there. I think right around the corner is performance announcement. Even if it's always a topic, I think it is mature enough nowadays that we should focus on that. And I think the third is bar use, some place improvements and introducing new functions. We have, for example, conditionals is something that people have been asking for for a while. That allows you to have resources which are activated depending on your environment. Some people are doing interesting thing with something called YACO, which I have mixed feelings about it, but it allows you to do some really powerful things in terms of manipulating your data in the template and being able to actually create more interesting structure. Got it. Okay, and then the product work group uses this notion of themes to capture roadmap and new features, et cetera. So the themes that we generally talk about are things like scalability, resiliency, modularity, interoperability, and matchability. What themes do you perceive your team working on during the cycle? I think convergence is all about resiliency because the core issue that we're trying to solve is then able to handle failures more gracefully. So I think resilience is a good thing. Obviously, scalability is also something related to me and not me. We have some horizontal scalability for cloud operator perspective because you can have many, many stacks and it will be able to handle that well. So the scalability issue that we have, that we have, the scalability issue that we have is about managing very large stacks. I mean, that's obviously an exit that we need to work on as well. Got it. Well, thank you so much for joining us. Do you have anything else that you'd like to add? Well, the main thing for us is to have feedback, I think. It's really interesting to get things from users and have people try it. And sometimes we will have an answer for them right away and I think that's like because people will be able to move on. But sometimes we also won't have an answer and that's the way we can improve the product. And so try hate, try to be creative in the way you write templates and come to us to follow our questions. Awesome. Well, thank you so much again. No problem. Thank you very much.