 It sounds like most people are communicating through the chat. Hey, we're live now. Oh, OK, go Allison. I think I did something. All right, thank you. So now we're live on the tool. OK. So let's see if it's actually on this. We're fine with our team that it's working. Thank you all for being the first session. You're welcome. It's always a good evening. OK. All right, I'm trying to read back through the. I think we've covered most of the questions. OK. Well, I think we only have a couple minutes left here. I want to just that I think what we need to do is kind of identify the most top five interesting places that would be to go add messages to APIs, looking at things like volume migration and whatever we think people use a lot that are likely to have failures and kind of sketch out what the next few are that we should add. Because it's not terribly hard to add this stuff. We just need to kind of figure out what the useful places are to do that. Yeah, that's a good point. I think we should add that as a PTG topic because we're kind of light on those anyway. Yeah, so the client API can display the messages. As Eric said earlier, there's some integration with some of the calls. So if you're pulling, I think pulling on the volume create, an error occurs that also has a message associated with it. You will get the message. But also, you can just use the, well, the Python sender client, right? I don't know about the open stack. Yeah, I don't think it's integrated to any of the things like volume creation and open stack client. That could be done for sure. But I don't think that has happened. So yeah, some partial answer there. As far as the question about extending the message list for vendor drivers, I think probably we don't want to do that because in general, you probably want to end up with a message from the volume manager that tells you the back end failed to do X. Probably having vendor-specific info coming out of this API is not really the right place for it. Yeah, I agree. I think for the particular back ends and the drivers can log messages and then the operators can find them. But we want to keep these very generic so that we want them to be consistent across clouds. And we also want them to not give away information about the configuration or about the particular back ends in use. So that's with that. And I lost track of what time we're supposed to end. I think we have like six minutes left. OK. So I will shut up because I've talked. Yeah, we go till 8.15. OK. Central. You just happened to be on the correct time zone. Yes. I got to do that for you, Mike. The version that just works. OK, we're up to 127 people. So that's pretty amazing. Yeah, that's crazy. And yet it's still quiet. I know. We've never had a room where it could actually fit 127 people, I don't think, for this. No, that's probably not true. We've definitely never had 127. OK. So someone asked, OK, there are just two Cinder discussions this week. Yes. So that's true. There's another one on Wednesday. Information's at the top of the ether pad. Also, I didn't want to say. So we have the PTG happening next week, which is where the design sessions are being done. So we're still in the process of planning exactly what we'll be discussing. So if there are particular items that you would like the team to discuss or bring to our attention, I put a link to the planning ether pad on the ether pad for this session. So feel free to put information on there. If you'd like to attend, that's fine, because we have plenty of room since it's being held virtually. But also, if there's something you'd like the team to discuss, there's a particular problem that you'd like to make us aware of, that would be a great thing to do to just put some information on the sheet. And if you can make it, that's good. If you wouldn't be able to attend, but still want to bring it to our attention, if you just put sufficient detail on the ether pad, that'll be great, and we can still discuss it. OK, if we need more time, we can run long. But that's a possibility. But I'm going to shut up so that other people can speak. I feel like I've got to fill the time, and that's not good. Yeah, so as far as the internationalization goes, let's come up again in the, we should be able to use the regular Python translation of strings. And then if we recognize the headers that are coming from Horizon, we should be able to reply with the correct language user message, just using the regular HTTP functions. So I'll look into that to verify that we've got that set up properly. And that's my understanding of how that's supposed to work. Yeah, so I think it's just a matter of making sure that the proper headers are being passed. But these are all marked as translatable strings in the code, so theoretically everything should work fine. OK, so we're closing in on the end of the session. So if you have general points or you want to follow up on this, the ether pads are a good place to put more questions. I also, in the Cinder project information, for general online 28 on the ether pad for this session, there's our contributing page. Even if you're not planning to contribute, it's actually a useful place to go to see all the deliverables of our project and how we communicate. So if you want to communicate with us, there's the mailing list. There's also IRC, and you can also show up to one of the Cinder weekly meetings to bring something to our attention. So please take advantage of those. We'd like to hear from users because it's really helpful to know what it is that people are focusing on so that we can focus our efforts as we stabilize the service and add features. All right, so I said it wasn't going to fill time, but I obviously did not stick to that. Thank you, everyone, for attending. It was quite a great number of people. And please continue to stay in touch with us as a project. We have another session at, I think it's 11 o'clock central time. So you can do the conversion to your local one on Wednesday. That one's focused on the third party CI. So you might want to attend that and also give you an opportunity to ask more questions. So thank you for everyone for attending and enjoy the rest of the conference. Cool. Thanks, Brian. Thanks, everybody, for attending. Yeah, you're welcome. Thanks. Thanks for taking the notes, Jay. Yeah, no problem. Back to my old demo. Bye. Bye. Yeah, thanks, Yvonne. Bye. So am I supposed to just end this? Or a question from my side? Sure. How to look into the server again to hope to another meeting? It is so overloaded, you even cannot look in anymore. Oh. Oh. Do not know. But if you have an internal communication channel, please let them know. OK. I will. There's like a speaker support email. I'll just send them something right away. So the problem is just that the general site is taking people off. You have a nice navigation on the page, which is you click your meetings. It's personalized, but you cannot even get a look in anymore. Yeah. All what you see is checking credentials, and then the thing is gone. That's been happening to me, too. OK. I know that's not. It's a try. Yeah, it's happened to me, too. One thing I did notice, though, partly, well, this only helped part way to get to a different error message. I have privacy badger on my web browser, and that apparently is interfering with some of the widgets that they've got on the site pages. So you might want to check to see if you've got any kind of blocking stuff in your web browser. I even use it in the home office. I even use my personal PC because with the PC at work, it doesn't work at all. And there are Firefox, and it worked at the beginning. Yeah, an hour ago, but now nothing happens anymore. OK. Yeah, I think you may be right that it's just an overload situation. But I'll send a message to you. Yeah, just so that they're aware. So thanks and sorry. Thank you very much. OK, have a good time. Bye-bye. Yeah, goodbye. Thank you. We still have people here, so I'll hang out for a while if people have questions and want to follow up. But officially, the session's over, so although it was Rudolph was saying, you may not be able to join the other sessions you want to join anyway.