 Hello, my name is Martin Kopetz and I work as a senior software quality engineer at Red Hat. I'm also the current PtL for OpenStack QAT team and a chair of Interop Working Group. Today, I'm going to give you a brief overview of Interop efforts and give you an update about the things we have recently accomplished as well as what we are planning to focus on in the near future. Firstly, let me briefly introduce the Interop Working Group. The IWG is a working group under the Open Infra Foundation Board of Directors. It helps the foundation to run trademark programs to promote interoperability between OpenStack deployments. In practice, it means that IWG sets base requirements by defining capabilities, code, and must pass tests for all OpenStack products. This definition uses community resources and involvement to drive interoperability by creating the minimum standards for products labeled as OpenStack. You may ask why interoperability? Why is it important? The IWG believes that ensuring interoperability across vendors' clouds is the only way how we can make sure that applications can be run anywhere on any cloud provided by any provider vendor. To achieve that goal, the IWG connects developers, users, and vendors together. IWG provides tooling to make running as well as visualizing the results of interoperability tests as easy as possible. For example, we provide a project called RefStack Client. It makes running tests of a particular guideline easier. RefStack Client is basically a wrapper around Tempest, which is a framework used to validate OpenStack deployments across the whole community. RefStack Client also allows users to upload the results to the RefStack page, which will be shown on the next slide. Another useful tool is RefStack. You can visit the RefStack page at refstack.openstack.org, where you can find all the guidelines and any published test results. This is a screenshot of the RefStack page. Obviously, we couldn't fit the whole content into this slide, so we see only the upper menu right now. We are under the guidelines tab, and below you would see the capabilities and the tests, which belong to this 20-206 guideline for the OpenStack public platform program. By the way, this guideline is our most recent one. Moving on, here is a snippet of the Marketplace page, where you can find whether a particular vendor is certified and with which guideline exactly. Based on the results published on the RefStack page, which you saw on the previous slide, this Marketplace page is updated to reflect the latest compliance results of that particular vendor, obviously, and the interoperability tests and uploaded them to the RefStack. Here's the current list of the MarketSync programs we currently support. First three are so-called CORE programs. The rest are, as we call them, add-on programs. We call them add-ons because they test services, which are optional in an OpenStack deployment. Interesting note, SharedPileSystem is the newest add-on program, which was added in the VolubiCycle. If you're wondering what kind of projects are part of programs, of which programs, here's the list. Nova, Keystone, Notre-Dame, Glance, and Cinder belong to the Compute program. SwiftService belongs to the ObjectStorage one. Then the add-ons, where ManilaService is a part of SharedPileSystem, DesignateService is DNS program, and it belongs to the Orchestration program. In the current cycle, we would like to add two add-on programs, OctaviaService as the LogBalancer program, and BarbicanService as the KeyManager program. These are for this still-in-progress. Maybe you're asking how a new guideline is defined? A draft of a new guideline is created based on API changes and customer usage feedback. Propos guidelines are undergaraged just like any other OpenStack code and documentation. The guidelines are reviewed by each project and TC before they are merged. Based on the feedback, the final version of guidelines is submitted and reviewed by us, IWG, to make sure that the tooling, for example, like RevStack page supports Propos guidelines, then by TC, Technical Committee, and OpenStack Foundation Marketplace owner. Okay, let's summarize our latest updates. We've recently released the 2022.06 guideline. We are working on adding two new add-on programs, LogBalancer and KeyManager program. We are also exploring a possibility of decreasing the number of guidelines releases from twice a year, every cycle cadence to just one release per year, which would mean that we would release a guideline every second cycle. We really appreciate your feedback. At the following wiki page, you can find a questionnaire which will help us to understand your needs with regards to the interoperability testing. Based on the feedback, we can improve our tooling to suit your needs better. Please, if you have time, fill the questionnaire. It will be really appreciated. And yeah, that's it. Thank you for listening.