 Okay. Good to go. Hey, all. I'm Erno Kuvea. I'm the PTL of the Glance Project. I'm just giving a quick update this morning what has been going on on Rocky, and what we will have been in a plans for first time in this cycle. So, first of all, big news. Images API version 1. Oh, we don't have a... There we go. So, Images API version 1 is gone finally. We actually got rid of the code, so it's not even possible to enable again. We have a couple of security related things going on in the last cycle. First of all, as a new feature, we got the implementation of multi-hash, which means that we don't need to rely anymore on MD5 checksums for hashing images, checking integrity. It's defaulting to shop 5TL at the moment, and it's configurable per deployment. Glance will automatically calculate the new checksums when you upload images. And as long as Glance client is up to date on the latest stable in the Nova nodes and Cinder nodes, it will automatically use also the new checksums on the verification. So, we are facing the MD5 sums out bit by bit. And they are still calculated. They are still populated when you create new images. So, we have backward compatibility there. The field is not gone yet. And let's see if it will ever be gone. So, the checksum field is there. But as long as the client is on the current level, and the SSL lib is configured so that the algorithms are present, we are actually not using the MD checksum anymore. And then our longest running favorite security issue, the OSSN 0075, which is basically if on really rare cases, one needs to run the database perch on Glance. It used to remove all the fields on deleted images to certain age. And that caused the possibility that a user could actually create an image with same image ID that had existed before. And because it doesn't have a database record before or the old database record has been deleted, it could contain totally different image and payload than the original image with that UUID. And say it had been public before, people have been using the image. If the user makes it available, for example by putting it as a community image, you could actually end up running an image with, for example, malicious payload in there. And the latest change what we did for that is that we will not anymore remove the image IDs from the database during the perch. So we clean everything else, and we leave those ID records there, which prevents anyone creating that same image ID with a different image load. Then next big thing what we got that has been on the wish list for quite a while has been the automatic image conversion. So if you're using the interoperable image import, it's possible for the deployer now to enable the image conversion plugin, and that allows the user basically upload any image that QM image can handle. And regardless, say you use Cephase backend, you would prefer that all your images are in raw format. When Glance is doing the import, it will automatically go and convert those images to raw before uploading them to the backend. And this is something which is totally transparent to the user apart from the fact that the container format will be changing, and the data won't have the same checksums what the user would obviously calculate from their own image. But it doesn't need any user input, it just you configure it on the deployment and it just works. We also got multiple backends. As a experimental API, we are stabilizing that API this cycle. So please give it a try, give us a feedback. This allows you to configure Glance with multiple same types of backends. So you could have two different Swift clusters, multiple different Ceph clusters, as a Glance backends with different type of disks or different locations. And you configure them with their ID, which is basically just admin configurable ID for the type of backend. You could call it Ceph, you can call it fast, slow, cheap, whatever you prefer so you don't need to expose your backend details to the user. And then when a user is creating the image, then they can either specify a specific backend what they want to use or they can just leave it out of the query and Glance will use the default backend to store damage. Then a couple of other things. So we still don't work under, let's say Apache under Uwisky so do not try to run Glance in those configurations. We have been making noise about it since Pike. We realized any of our asynchronous jobs within Glance don't work. So there is, Glance comes up nicely under Uwisky. Everything looks like it works and then you start realizing that some calls just never return or the call returns fine and for example image import and the import job never kicks off so the image never gets created. So just a note again, do run Glance as an independent service and you won't be ending up to having those issues. Another thing on Rocky, like we said when we were introducing the interoperable image import, it will be the default option and in Rocky Cycle it is enabled by default which means that for example the staging area which is a path to the disk on local disk on Glance API node where Glance stores damage data before uploading it to the backend for example during damage conversion or when web download is used that needs to be configured now as well. So that's a hard requirement. Another thing what we have been discussing for quite a long time and we have been asking feedback, no one has actually reported using this. So we finally deprecated the owner's tenant option and it will be just silently ignored and it will be removed in SteinCycle. Sure. Yeah, now it's all there. And then... Oh great, I'm losing the end bottom as well. So... SteinCycle, we are stabilizing the multiple backend API like I mentioned. We have some updates on the locations API. It's not suggested to use but currently it is for example the only option if you want to use HTTP backend and there is some use cases for that so we are bringing a little enhancement on that API that allows you to basically smuggle during that locations call on the JSON patch a checksum information for your image because if you create an image via the locations API the image data will not flow through the Glance API. Glance won't calculate the checksums so we are bringing a small improvement there and making it possible to actually provide those checksums so that the images can be verified even they are created through the locations API. We have also small improvement coming with all visibility filtering so when you are doing image listing you can specify visibility all and it will actually return list of all images that your project has access to instead of you needing to go through all the different visibility with the different requests and then combine those lists. We have a story info coming in the image client call so that the image list will be able to return which backend store on the multi store case the image is actually sitting currently you can only see it on the image show call and then we are working on having a little bit of cluster of awareness in Glance so that the Glance API nodes can actually start talking to each other this is quite a bit of working towards stage requirements so we can start doing features like pre-caching image data to certain locations on certain API nodes and that kind of work. We are currently very very small team which means that we won't be able to do a huge little lot during the cycle any help, especially any reviewing help would be greatly appreciated and that's basically our current state I hope I have just 6 minutes give or take so any questions? Go ahead. The question was about the multiple backend and how it's handled so there is a configuration file on the API config where you specify what backend driver you are using what is the path to that backend you give it the backend ID which is basically a string and you can give it a description and that's a preset list of backends so if you want to change that list or let's say add new backends you can do that live as well so you go you change that config file and then you just give a sick hope to Glance and it will populate the list again so you don't need to restart Glance to change it but it is a pre-configured list Anything else? Cool. Thank you very much. I'll be here around today still so if you have anything else just come and have a chat with me.