 Hi, good morning. Welcome to the Kola project update for the Rocky release. I'm Eduardo, a PSTAC Kola PTL. My friend, Surya, let's go to what's new in the new release. First of all, what's Kola? Kola provides a production container ready for undeployment tools to pay out in a PSTAC deployments. The project is composed by three subprojects of PSTAC Kola, which is Docker images and building tools. Kola Ansible, which is the deployment tool based in Ansible playbooks to deploy OpenSTAC. And Kola CLI, command line interface and API to configure and deploy Kola Ansible environments. Project history, it was founded through the killer release. And then, one release later, during the VIN 10, during Liberty Cycle. And now, with Rocky, we're in the seven stable release. In the latest user survey, we increased a lot of production environments, 115 production environments with Kola Ansible, and 25, only the Docker images we produce with Puppet, Nomad, and other deployment tools. Just a small note, these deployments are only from the English hardware. So all the Chinese are not translated to English yet. So probably it's going to be much more deployments for the release. For the Kola images, we have added eight new Docker images for LogStars, Monasca, Prometheus, DraftD, Neutron, InfoLogs, IPI, and Driver, and Apache Storm. We also have support for BlueStore in third cluster, which supports both BlueStore and legacy storage systems. In the Kola build scripts, we also support now network mode, so you can define if you want to use NAT or Nethost for image building. We also have decreased the size of the images a bit by removing documentation from the packages and not just packages in the new releases. And also, we now include security updates for every package we install. The Ubuntu-based images have been upgraded to Bionic Release, and we have added new Neutron drivers into the Neutron images, like networking ansible and networking body metal. Now, in this release, we finally have previously the images to Docker Hub, so you can just pull the images and you don't have to build images every time you want to deploy OpenStack with Kola ansible. Thus, the images are run at the IE job before pushing to Docker Hub, so all the images are less built, and the core services are tested before pushing to Docker Hub. Our daily builds also include the latest security updates for the packages. For the future in the Kola images, we aim to optimize a bit more the images to decrease the size and remove all the packages. We are also planning to migrate to Python 3. This is not going to be soon, because many OpenStack projects don't support Python 3 yet, and there's also no OpenStack distribution supporting Python 3 yet. CentOS is not supporting, so we cannot move everything to Python 3 yet. We aim to provide more CI jobs for the images before pushing to Docker Hub, so we can ensure more services are tested before having the images I've seen for consuming. We also aim to provide more CI jobs for third-party tools for Kola images users, like TripleO and OpenStack Helm. We need volunteers to do this job. TripleO has already pushed a patch for this, so they're just testing the images and more CI jobs for pushing the images. Hello, everyone. So what updates we have from Kola and Siebel side? So in Rocky, we supported the safe BlueStore OSD, and by default, we are supporting for now the OSD types only. Maybe in the future, the other types of the storage will be supported by the SAP itself. And some of the new roles for the OpenStack services is added in Rocky, like Freezer Sedular, and Apache Kafka, Apache ZooKeeper, and Partial Momonatska. For now, it is done, but in Rocky, we supported a Partial one. And we talk about the zero downtime upgrade. So in pretty much a stable stage, we have for the glance service, Cinder and Irony. And some of the more core services is implemented for the Stain one, like Neutron, Noa, and Swift. So in Rocky updates, we have these tables one. And if you talk about the monitoring for the open source tool for the monitoring purpose, so we supported in Rocky Prometheus, which is very much popular as an open source tool. So we have the role for Prometheus one too. And now you can restrict the limits on the container image with the help of COLA Ansible roles at the runtime. So you can restrict your resources up to limit option provided by the COLA Ansible script. And we also have now developed to the providing the developer option for OpenStack core services to create your own development environment into containers itself with the help of COLA Ansible script. Now, some of the changes that we did in Rocky in the Neutron. So you can see the ML2 plugin. You can have OpenVC, Linux, Beige, or Hyper-V L2 agent. So you can now customize with COLA Ansible script for the Neutron service. And if you talk about the info blocks, IPM driver, so it's used for the Neutron subproject intercommunication, so you can configure the driver of the info blocks in Neutron COLA Ansible role itself. And the Open Networking Operating System is also supported. So here you can do with the COLA Ansible script also. And networking bare metal is also comes into picture with the same supported by the Neutron project. And you can do some user local setting for the horizon project itself that enables you to debug some of the JavaScript and CSS level codes in the horizon itself. And we also added some of the more option in the COLA Ansible CLI. So it is like fork, check, and if. With the fork, we added for the large amount of deployments. So it makes sense adding the fork and doing the fork for the Ansible model. And for the check, we added this option with the COLA script to run your mock test after the post-deployment. As we already did in the pre-check before deployment of the COLA Ansible, so with the check, you can run your mock test after the post-deployment. And if you talk about what is the future of the COLA Ansible, so we are targeting these are the features that we'll be talking for a stay in or a train cycle. So fast forward is a priority one that we are looking for the next release. And zero downtime upgrade for the all core services as well as some of the supporting services of the OpenStack. And CI improvements is very needed for these deployment techniques and features in the field of upgrades, as well as some non-core projects, deployments, and running the functional test in the CI itself. And we can use Rally, RefStack, and Tempest to automate our testing in GateJob. And we are also targeting database backup recovery, restoring tools with the help of COLA Ansible, when your control base and database allows and how COLA Ansible will cope up with that. And COLA dashboard is one of the features that you can expect and which is, we'll be doing the POC for now. So that is for a very good interface to get the deployment with the help of COLA Ansible. No, our community is no single vendor community. So we have a lot of diversity and no company owns more than 20% of the contributions. We are the global distributed community with many contributors from Asia, Europe, and the US. In the ROCK Release, we have 125 contributors contributing COLA Ansible and almost 160 reviewers with nearly 5,000 reviews in ROCK Release. We have 720 commits in ROCK Release. 80% is done by other contributors, which means no single company owns the code, so it's a good number to know. We're going to join the team. Our IC channel is OpenStack COLA and Free Node Network. Meeting Suicide at OpenStack Meeting 4 on Wednesdays, 15 UTC. You can ask anything at the mailing list with COLA Attacks. And books, reviews, and patches are welcome. Filtered by Wesley's in EC Physics at Launchpad. You can start with FAST and ECFIX to start contributing into COLA. Thanks to all the contributors who made this release possible. Thank you for coming. Any questions so far? Any questions? Easy. Thank you.