 Hi, thank you for joining us for another Newton Design Series session. This time with me, I have Rob, who is a Horizon PTL. Rob, can you please tell us a little bit about yourself? Yeah. So yeah, I'm Rob Craswell. I'm the Horizon PTL for the Newton Cycle. And I'm a software engineer with Cisco Systems, where I've been for the last four years and joined OpenStack about two years ago. I've been working on Horizon since then. Great. Thank you so much for joining us today. So before we begin, can you give us a little background on what Horizon is as a project? So Horizon kind of has a dual purpose. It provides a library of widgets and components that people can build a dashboard and extensions that dashboard from, but then it also provides a base dashboard for some of the larger OpenStack components like Nova, Neutron, Glantz. Got it. Thank you. So we're about a month after the Austin Design Summit. What were some of the hot topics that you and your team discussed and what were the outcomes? So with Horizon, we've got an ongoing kind of move to AngularJS and moving on to kind of a JavaScript client-side framework. This has always been quite contentious because it's basically resulted in quite a big rewrite of the project. And that we tend to get a lot back and forth over that. That's always something that comes up and we kind of have to negotiate and go back and forth over how we'll solve those issues going forth and also how much time we want to put into the long-term goals around Angular and things like search like integration versus fixing the problems we have here and now with the existing Python and Django implementation. Got it. And so from a user needs perspective in this cycle, what are some of the items you're hearing about from users and what are you doing to address them in this cycle? So there's a couple of things that repeatedly come up is issues with scalability, specifically on the dashboards themselves. When you start looking into the admin views, so you start looking across multiple projects and regions at once, that tends to get a very non-performant. We also have a lot of inconsistencies to do with things like pagination and filtering because of the implementations in the different projects and because we've always done that, we've attempted to do that service side where the projects provide it, they tend to be, those implementations tend to vary a lot between those different services and they're not always available. One of the things we're probably going to use in the future is plug into the search like project and kind of use that to give us a cash layer that we can build on to get consistent paging and filtering search. Great. So now that we've heard about some of the hot topics and user needs that you are planning to address, based on that list, what are the top three priorities for either new features or enhanced existing features for Newton specifically? So again, this kind of splits into where we're kind of moving forward on the Angular stuff whilst also trying to improve the existing Django content. So this kind of has a few different directions. There's iterative improvements to a lot of the theming work. So we've had some massive rewrites of the HTML and CSS that we use, really stripping out a lot of the bloat that we've put in, a lot of the inconsistencies so that people can extend and theme their deployments of Horizon much easier. This is like this is something that came up constantly in around the kind of Juno, Kilo, Liberty summits, because especially I think with smaller organizations using OpenStack, they tend to just want to lightly brand Horizon rather than make sweeping alterations to it. So that's been a big boost for us. So iterative improvements there. We also last cycle rewrote the panel, the user interface for Swift. So we'll be kind of continuing to extend that with some nice little features and fixed bugs on that. In terms of bigger improvements, there's going to be a lot more kind of structural code added to make Angular features easier to do, to make plugins that extend existing content easier and to make it and sort of continue laying the groundwork for us to use Searchlight in the future. Perfect. So the product workgroup uses this concept of themes. The themes that we typically focus on are things like scalability, resiliency, manageability, modularity and interoperability. Sure. If we were to kind of, you know, go at a high level for a second in the Horizon project, what do you think are the themes that your team is working on in new? The biggest one has to be scale. We have improvements to the on the admins, as I mentioned earlier, the kind of admin views. We've got some small tweaks to make there in the Python and Django work. So, for example, one of the suggestions we had was to require a filter when you go to these views so that when you immediately reach the view, we don't make any data requests until you ask for a smaller scope of data because otherwise the initial request gets crazy. So we have like little bits and things like that that will kind of help improve the scalability of the existing content. And then we have the groundwork for Searchlight in the future, which will start letting us scale and handle tens of thousands of objects in a kind of a much more a much nicer way for the end user, basically. The secondary one, I would say is is probably, I think, with certain the manageability. So just improvements to the way we're handling plugins, settings and theming and branding. So, again, this is all like iterative improvements, bits and pieces that we're building on from previous cycles. But, yeah, those are kind of the two major themes, I think. Great. Well, thank you so much. This was really useful information. Is there anything else you'd like to add? I think that's about it. We are always looking for more contributors, more reviewers. So, you know, if people are interested, get involved. Our IRC is incredibly active and the community is really supportive of new people. So, yeah. And what is the IRC channel? It's OpenStack Horizon. Great. OpenStack Dash Horizon, sorry. Perfect. Thank you so much for joining us today, Rob. Thanks very much.