Jump to: navigation, search


This page contains Logs of 2020 Interop WG meetings.

Last 2020 meeting

OIF - Interop, Branding to be taken after new commitee is formed Manila - As on Dec 18 meeting no change Ironic - On Hold till Julia PTL is ready, after the OIF decision Next week call -Prakash to send email

Friday Dec 18th

Attendees: Prakash, Arkady, Vida, Martin, Goutham Topics:

   - last meeting AIs, updates
   - refstack website needs maintenance

- Look at Interop web pages to fix them (Notes to be added) - http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019185.html - .next files need to be updated - gmann will do this after the draft guidelines are approved by the OSF Board

 - Updating the guidelines as per Dec 8th Board meeting - https://review.opendev.org/c/osf/interop/+/766778

- Website needs updates, to expose add-ons

     - the new guideline is not updated on refstack (server) side
   - https://refstack.openstack.org/api/v1/guidelines/
         - https://refstack.openstack.org/#/results/f75c4c91-8bdd-471f-823e-41fa7c7538eb 
             - (when you open a result page you cannot see the new guideline in the Guideline Versions drop-down menu)
     - wrong issues links in opendev.org - http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019416.html
     - https://opendev.org/osf/refstack-client - Issues link redirects to https://storyboard.openstack.org/#!/project/openstack/refstack-client
  - notice the namespace , it's 'openstack' and it should be 'osf'
     We also should review and update https://www.openstack.org/brand/interop/ documentation
   also https://refstack.openstack.org/#/about#about
   alsohttps://refstack.openstack.org/#/guidelines still does not show 2020.11 guidelines
   - bug tracking revival/options:
- https://launchpad.net/refstack

- https://launchpad.net/~refstack-bugs/+members#active - Chris Hoge can still be contacted - Danny Carreno <danny@openstack.org> - AI: Goutham contact the admin (Catherine Diep) of this group (and related groups)

- https://storyboard.openstack.org/#!/project/700 

- Should Heat engine can sub Kubernetes as revamping of OpenStack as a whole to be based on KCP? - bring it board for discussion but Technical committee should take a dig at this - Should tempest add go libs (ginkos & go*) - Marketing message on Interop contribution to compile the 2020 Open Infrastructure Foundation annual report. (Deadline Jan 13,2021) https://etherpad.opendev.org/p/2020-Wallaby-interop-brainstorming (Lin 23 onwards to end)

Friday Dec 11th

Attendees: Prakash Ramchandran, Martin Kopec, Vida Haririan, Ghanshyam Mann, Goutham Pacha Ravi

     - Review Board meeting inputs
     - Discussion to extend the interop program across all OIF projects
     - TBI (Trademark and Branding Initiative) proposed/to-be-formed within the foundation board

- TBI will be functional only after the new board is formed - elections will begin in 2021 - 2021 Election Info: https://www.openstack.org/election/2021-individual-director-election/ https://www.openstack.org/election/2021-individual-director-election/CandidateList - Action Items from the last meeting - Refstack Maintenance - Current Refstack Maintainers: https://review.opendev.org/admin/groups/8cd7203820004ccdb67c999ca3b811534bf76d6f,members - Need to get Martin Kopec added there:

       - http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019263.html

- Reform the core team for: - openstack/python-tempestconf - openstack/refstack - openstack/refstack-client - x/ansible-role-refstack-client (moving to osf/ via https://review.opendev.org/765787) - needs your +1s, please - Proposal: - "refstack-core" group

 - Update the groups with new members and erplace any other refstack corewith this new group.

- include "interop-core" group in the refstack-core group so we can manage both of these individually https://review.opendev.org/admin/groups/ad95fb605fa544dab35712194df7faaa10ec7a22,members

  - includes chair/co-chair no change. in existing one.

- Action Items for this week: - gmann will send email to revive the "refstack-core" group, gain control and seed it with interested members (the email will call for any interested contributors to reach out) - gmann - martin (mkopec@redhat.com) - Goutham - vhari (vhariria@redhat.com) - interop-core

- How do we cater to OIF & or OSF Kubernetes Distros for comformance testing or leave that to upstream kubernetes & arrange discussions with CNCF? -next call

- Prow -Build and test k8s projects - Sonobouy

- KoO using for Cloud Provider OpenStack with Prow - - KoO using for Cloud Provider Openstack + Manila using Zuul - - https://github.com/kubernetes/cloud-provider-openstack <-- this is where OpenStack integrations live, and are being tested - Kubernetes "starter-kit" for OpenStack: https://governance.openstack.org/tc/reference/tags/starter-kit_kubernetes-in-virt.html

Dec 4th


   Prakash Ramachandran
   Arkady Kanevsky
   Goutham Pacha Ravi
   Vida Haririan
   Martin Kopec

Agenda: - Refstack Maintenance - AI -1 (Investigating Refstack and providing input to Interop team) -Martin (Redhat) can help - Repositories: - https://opendev.org/osf/refstack (server project) - AI Prakash to lookinto and get back on who mainatins it & how add-on programs gets added/advisory files like dns not getting added - need codes to fix the add-ons integration with marketplace stats - Patch to add add-ons: https://opendev.org/osf/refstack/commit/0f55b39a6bd013cd808c74b56ff4d1d838f3cd2e etc/refstack.conf.sample Like #154 #additional_capability_urls = https://api.github.com/repos/openstack/interop/contents/add-ons - Need code review (GMaan) - https://opendev.org/osf/refstack-client - runs tempest tests and generates subunit file - cannot upload results to the refstack server - (martin) it can, however only manually using refstack-client's API, the ansible-role-refstack-client is a wrapper around refstack-client to allow running tests in an automation (CI, Jenkins jobs ..), see below - https://opendev.org/x/ansible-role-refstack-client - Need to move to osf repo (add to Board presentation, we can schedule it for next Geriit reboot) -> https://review.opendev.org/c/openstack/project-config/+/765787 osf mirroring responsibility is osf's - it appears so Infra team needs to follow gudielines ? - https://docs.opendev.org/opendev/infra-manual/latest/creators.html#mirroring-projects-to-git-mirrors Propose Martin as commiter for Refstack -Gautham can handle this - Martin created this ansible role to automate installation of the refstack client, collating results and uploading them to the refstack server - it automates everyting needed for running refstack tests - preparation (installing refstack-client, generating tempest.conf), running tests and uploading results to Refstack after the tests are finished

 (the result uploading is allowed only with a key identifying refstack account the results will be stored under - so the role will copy the user's key to either local ~/.ssh or even a remote one on a target machine if needed)
   - all this can be done by a single playbook run

- the role provides several vars to contol the behavior of the testing - e.g. var for specifying a guideline, a tempest version to use, refstack-client version to use, a var for specifying custom tempest.conf or accounts.yaml (the role will generate them by default)

- Shared File Systems Add-On advisory follow up - https://review.opendev.org/c/osf/interop/+/762193 (AI - Gautham to update advisory & Prakash to revise Board presentation to include this + other items above) What next: - Needs code reviews, needs to be merged - done - Goutham will add the 2020.11 advisory "Shared File System" today - done: name in Project File - https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml

Friday Nov 27th




   Getting Interop Draft ready for Board approval by email & later at Board meeting Dec.
   Cancelling the meeting , but verify code review by Ravi & updated by Ghanshyam
   Sent email to Mark to rveiew the workflow.
   From my side I will give a +2 for either Mark or Arkady to close and release.

Friday Nov 20

Iterop Meeting cancelled - Gerrit maintaenance http://lists.opendev.org/pipermail/service-announce/2020-October/000012.html

Friday Nov 13th

Attendeees: Prakash Goutham Ravi (gouthamr) Vida Arkady Julia David Paterson (dpaterson)

Agenda: 1. Interop Guidelines for 2020.10.json - 2020.10.json (https://opendev.org/osf/interop) - Arkady to try submit to osf/interop - escale to osf staff if needed - Need pointers to results in Markets 2. Interop add-on Guidelines for existing - https://opendev.org/osf/interop/src/branch/master/add-ons 2.a DNS (Designate) - dns.2020.10.json - Need pointers to results 2.b Orchestration(Heat) -orchestration.2020.10.json - Need pointers results 3. Interop add-on guidelines for new proposals - https://www.openstack.org/marketplace/ 3.a FileSystem (Manila) - No plans for Victoria 3.b Metal as a Service (Ironic) - No plans for Victoria 4. What's next for Interop 2021 with containers & Kubernetes/magnum ? - Need Volunteers with go skills for new conformance test proposals - Need Board level guideleines from Foundation

Q: How do we tie vendor certification to the interop tests? refstack.openstack.org has anonymized results, and nothing about add-on programs A: These are linked via the Marketplace website

    Example marketplace link: https://www.openstack.org/marketplace/public-clouds/ovh-group/ovh-public-cloud (expand test results)

 == Friday Nov 6th (Decision for Victoria release from core and add-on modules) ==

Attendees: Prakash Ramchandran Vida Haririan (vhari)

Notes: (vhari) Please confirm if this is the new path to master branch? https://opendev.org/osf/interop/src/branch/master/add-ons - This is the right palce to submit add-on patch for Manila & ironic -Prakash Commit changes to : https://opendev.org/osf/interop/src/branch/master/add-ons/2020.10.json Make proposed changes to dns.2020.06.dns and submit Need document field defenitions used in json file -> Prakash provided 11/6/20++

https://storyboard.openstack.org/#!/story/2008328 I have a working draft with cosmetic changes for review pramchan@ubuntu132:~/interop$ git log --oneline 3a42a6d (HEAD -> master) created Draft for 2020.10 but looks unable to submit it to interop stable? https://opendev.org/osf/interop pramchan@ubuntu132:~/interop$ diff 2020.10.json 2020.06.json https://opendev.org/osf/interop/master/ 3c3 < "id": "2020.10", --- > "id": "2020.06", 5,6c5,6 < "reference": "https://opendev.org/osf/interop/master/doc/source/schema/2.0.json", < "source": "https://opendev.org/osf/interop/master/2020.10.json", --- > "reference": "https://opendev.org/openstack/interop/raw/branch/master/doc/source/schema/2.0.json", > "source": "https://opendev.org/openstack/interop/raw/branch/master/2020.06.json", 73,76c73,76 < "target_approval": "2020.10", < "replaces": "2020.06", < "releases": ["train", "ussuri", "victoria","wallaby"], < "status": "draft" --- > "target_approval": "2020.06", > "replaces": "2019.11", > "releases": ["stein", "train", "ussuri", "victoria"], > "status": "approved" 3209,3226d3208 < "sections": {} < } < }, < "designate": { < "informational": { < "guidance": "Not a core capability, add-on program is available.", < "sections": {} < } < }, < "manila": { < "informational": { < "guidance": "Not a core capability, add-on program is being added.", < "sections": {} < } < }, < "ironic": { < "informational": { < "guidance": "Not a core capability, add-on program is being added.",

Verify above is correct Please note - https://opendev.org/osf/interop/src/branch/master/add-ons/dns.2020.06.json

 Checklist for PTLs (core - keystone, glance, nova, neutron, cinder & swift) and add-ons (heat & designate)

1. Did the Victoria switch for Jenkins to Zuul V3 and move to new Ubuntu Focal impact your DevStack and Tempesting module feature testing in any way for Interop?

2. Pease check https://opendev.org/osf/interop/src/branch/master/2020.06.json#L72 We will drop stein and add wallaby, hence train release notes will be the base line for feature retention and compliance baseline testing

Please verify what are the changes you may need for Victoria cycle for Logo program for your modules list all core - keystone, glance, nova, neutron, cinder & swift and add-ons (heat & designate) "required": [] "advisory": [] "deprecated": [] "removed": []

3. Reply by email the changes expected for us the review based on your Victoria release notes or add notes to https://releases.openstack.org/victoria/?_ga=2.174650977.277942436.1604012691-802386709.1603466376

4. Discussions on Manila - Need Volunteer
5. Disucssions on Ironic - Need Voluteers
6. Discussion on future Kata GoLang  -  Kata (with tempest vs k8s test tools  or  https://onsi.github.io/ginkgo/ +  Airship, Starlingx, Zuul on infralab ?) - Need volunteers

Friday October 23rd & 30th

Attendees ( Refere PTG Session 1 & 2) https://etherpad.opendev.org/p/interop-wallaby-ptg

Attendees Prakash Ramchandran Arkady Kanevsky Deferred except for announcing PTG items

Agenda https://etherpad.opendev.org/p/interop-wallaby-ptg Where are we at Interop Quaestionnair with Allison -Action Item (Prakash) Reviewed all above.

Friday October 9th

Attendees Prakash Ramchandran Arkady Kanevsky David Paterson Goutham Pacha Ravi (gouthamr)


   Review Last calls summary
   PTG slots: http://ptg.openstack.org/ptg.html
   - 2 hours on Monday: 1300-1500 UTC (Room: Austin)
   - 4 hours on Friday: 1300-1700 UTC (Room: Austin)

   What Capabilities need addressing for  Account, Container, Object (https://docs.openstack.org/swift/latest/)
   1. Swift - https://github.com/openstack-archive/interop/blob/master/doc/source/process/PlatformCap.rst
        Swift API supports three objects - 
   2. OpenStack Manila inclusion  (Goutham Pacha Ravi (gouthamr) - PTL, Manila -     Project : manila (Filesystem))
         - project has full blown testing
         - Protocol support no different from the Cinder storage protocols, in one sense
         - How many third party vendors provide tempest results 
         - What's the common set of capabilities
         - Add On Module
         - like Heat, Designate
   - have an add on module called "File System Storage"
   - No admin API is ever tested in interop 
   - Interop is run for Ussuri right now, will be run for Victoria when it is released

- Testing a release means you're testing three releases prior

   - Interop is run after a release, and when a new release is adopted, the oldest one is dropped from the list supported
   - Weightage assigned to individual tests
   - Vendors commercially supporting submit test results to marketplace

- Todo: Identify the capabilities in terms of API/resources CRUD tests on these resources - identify these tests - drop any that relate to admin Pre-provisioned accounts are used in tests (manila-tempest-plugin has supported this for a while) Microversion testing: - Adopt a baseline that is common for the last three releases - Baseline moves as we drop support to older releases - Baseline currently (Oct 2020): https://docs.openstack.org/manila/latest/contributor/api_microversion_history.html#maximum-in-stein https://etherpad.opendev.org/p/interop2020 https://www.openstack.org/software/project-navigator/openstack-components#openstack-services

Notes to be circulated for these two to get feedback from community on OpenSTack-Discussions email - AI Prakash We need Swift PTL to be informed that Interop would like to have a Swift driver for helping commercial Back ends to be tested for comaptaibility like Ceph RGW (PowerFlex) We need Manila PTL to define the Interop for File System.

   2. K8s conformance APIs (core k8s APIs?)
   3 BMaaS conformance APIs (? Ironic, MaaS, Tinker Bell?)

Sept 25


 Prakash Ramchandran  
 Mark Voelker
 David Paterson    
        Interop Certification test results submission? Shambu for Dell seeking clarification 
        When yo test Run test locally it gets posted to Refstack portal (if you do: "./refstack-client upload -v -k .tempest/.testrepository/0.json"). All one needs isto send that link of test results to interop@openstack.org

https://refstack.openstack.org/#/ You will get message like following Hello and thanks so much for your interest in the OpenStack Foundation and our supported projects! Someone from our staff will get back to you ASAP. To add additional comments, reply to this email or click the link below: https://support.openstack.org/hc/requests/38315 The ticket number issued will be followed up by OpenStack Staff (like Jimmi Mecarthur or some one in his team)

        Interop - Planning for discussions on topic
        Proposed Discussion Title - https://ethercalc.openstack.org/7xp2pcbh1ncb (Two slots on Friday 30th Oct -reserved for any additional discussions with conatiner & ironoc teams, Option is see if we can get udates om NFV4 standards for container managament)
       InteropWG Looking to new Branding Opportunities
     Abstract (1000 chars)
Interop WG has been reviewing opportunities to maintain and build on defcore, refStack & Steller contributors in past. The current team would like to debate, to see what the new opportunities emerge from market disruption due to Hybrid Cloud, Edge, Container footprint over Bare-Metal & with Kubernetes clusters orchestration as the baseline for Infrastructure. Current challenges include Tempest test spread plus updates to refStack . Board is willing address all aspects from license, legal, object storage, bring in Policies for Open-Infra branding opportunities. We like to hear through Q&A session more ideas like kubernetes-ready-Stack, BMaaS add-ons etc 

https://etherpad.opendev.org/p/2020-Wallaby-interop-brainstorming Add-ons - Ironic, k8s conformnace for Open Infra/OpenStack modules, ceph k8s ready openstack (k8s over OpenStack)- crate volume (offer cinder or Manila for PVs) - Run Sunobuy tests for eg. over this like VIO using Swift, RHOSP with Cinder, Any OpenStack Distro or hoster OpenStack Service needing k8s conformance Cloud Provider for OpenStack: https://github.com/kubernetes/cloud-provider-openstack Octavia Load Balacer for Ingress Controller funtion

== Sept 11 == 


   Prakash Ramchandran
   Arkady Kanevsky
   The old Interop presentation panel not selected for Summit  to be moved to forum with minor changes
FYI only       

[1] https://wiki.openstack.org/wiki/Forum [2] https://www.openstack.org/summit/2020/ [3] https://cfp.openstack.org [4]https://wiki.openstack.org/wiki/Forum/Virtual2020

Added two slots for InteropWG Oct 30 - Friday 13-14UTC & 16-17 UTC incase we need other presentaions for containers (NFV4 Standards) , BMaaS / Ironic (APIs and consumption by Airship), Container Interop by OpenSatck (Magnum, Zun, Kuryr & Kolla teams)

OCT 26 Forum plans- https://ethercalc.openstack.org/7xp2pcbh1ncb - Any inputs to/from Board for new Logo Programs -Discussions on CNTT/OPNFV Merger and Proposed RA2 using KubeVirt (https://kubevirt.io/) for VMs along with K8s for Containers? Impact on Interop for VM + COntainer workloads

August 28th

Prakash Cancelling No Quoram

Aug 14

Attendees: Prakash Ramchandran Ghanshyam Mann Arkady Kanevsky

Review Forum submission for Project Updates -Prakash + Mark - not clear what is Project Update to Forum, as we don't have any Project for Interop to report? Forum Submissiom request completed for Interop WG - Prakash - https://openstackfoundation.formstack.com/forms/oct2020_vptg_survey - Filled in with cross project meetings with Intergated projects , Ironic, Container related projected(Mgnum, Kuryr, Kola, Zun), Tempest - Process - Horizontal - AT start of PTG can be brought asking PTL to acknowledge schedule..and particpate - https://ethercalc.openstack.org/7xp2pcbh1ncb - Process - Project Specific - (RefStack , Tempest) Swift - will depend on polling (working with Allison- Follow up) results and any changes to current Tempest coverage Intergated projects + add-ons (as is exisiting Logo Programs) - Need Deltas Ironic - add-ons (BM Logo) - Admin API ? should be kept aways? User needs to inherit Admin permission for Ironic APIs to make it interoperable Container - Refer Friday Juy 17th meeting notes Foundation Discussions for Open Infrastructure Logo Programs (Market Place feedback or End users need to bring to table , 4Os plus can add to Interop) - Bring to Panel Discussions OPNFV-CNTT is merging in LFN as OPNFV LLC (without chnage of name) driven by GSMAA + LFN likely Jon 2021. CNCF driver Cluster API based testing for Containerized Plane...need watching Tempest - Test Capabilities limited to Integrated Projects, add-ons like Heat & Designate is within - Its limited to QA with Integrated stack Open Infra projects have their own CI/CD & Testing RefStack is broken for Ussuri ? Need to generate a report...or file a bug for Ussuri - Check with Mark?

Seperate from Proposed Panel Submit under - Open Development https://www.openstack.org/summit/2020/vote-for-presentations#/24735 Follow up on Action Intems from last call -

                             Operator Survey - Follow up with Allison -Prakash -sent email -
                             New Guidleines for Victoria - Mark? Await an initial patch or we can take up later Victoria Time frame -TBD
                             Any feedback on Tags for Interop - Ghanshyam from TC (How to enable tag  assert:supports-api-interoperability) - Gmann working with Manila  -TBD
                              - assert:supports-api-interoperability -refer  - https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml

Friday July 31

Prakash Ramchandran Mark Voelker Arkady Kanevsky

Arkady - Everyone can update their user profile for Individual projects Q? about Interop About each about projects Do they use this for

https://www.openstack.org/user-survey/faq (2014) interop@openstack.org

Marketplace needs decouple from Branding? seperate Decion : All questions should go to Operator and hence Decision makers - Echosystem Operator Survey - Follow up with Allison (Action Intem - Line170-176) What is there now and response + cc Mark+Ghashyam ...

Review projects for k8s conformance/Openstack provider APIs Kourier - https://developers.redhat.com/blog/2020/06/30/kourier-a-lightweight-knative-serving-ingress/ Navisite Cloud Director (NCD) - https://navisite.uservoice.com/knowledgebase/articles/1902673-vcloud-director-api https://docs.vmware.com/en/VMware-Cloud-Director/index.html k8s conformance - https://github.com/cncf/k8s-conformance OpenStack confrmance - https://opendev.org/osf/refstack OpenStack Integrations testing - https://github.com/openstack/tempest

CI Jobs k8s  -https://github.com/kubernetes/test-infra
k8s Openstack Provider - https://github.com/kubernetes/cloud-provider-openstack
Swift is independent - Do you care about what back end is used with Swift API?
Swift, Swiftstack, Ceph, ECS, ...

kubernetes - line 103-116(Tempest should have coverage for openstck API which the provider calling) Community has intrest ? lets wait on this? Identify requrients ? kubernets Ironic - one cycle

New guidelines for Victoria- Ask PTL/Project Teams if they have anything for 2020.12(?) Guideline:

  * Any capabilities in the guidelines that have been depricated inTrain, Ussuri, Victoria
  * Any new capabilities that should be added? Must be supported in Train, Ussuri, and Victoria
https://cfp.openstack.org - Project updates for Interop delata... (Add the csfp on Forum  and we can knock out 10 slides later - add all 3 names Prakash, Mark & Arkady - Since Ghanshyam is leading Forum sessions
Since topics are limited we move the meeting once in two weeks - Next meeting will be on August 14th, 28th...

Friday July 24th

Open Agenda Sent email and followed up with Follow ups Replied email to Allison/Danny/Interop team. https://Dell.zoom.us/j/92074400967

On Jul 17, 2020, at 6:30 PM, Ghanshyam Mann <gmann@ghanshyammann.com> wrote: I agree with adding question 5th to user survey (along with existing 2 questions) and adding all 5 to marketplace survey to get their feedback.


On Fri, 17 Jul 2020 16:30:52 -0500 prakash RAMCHANDRAN <pramchan@yahoo.com> wrote ----

In short yes both user-survey & marketplace survey. 1. Based on review of user-survey pointed below, if I understand correctly the questions in them relate to existing deployments , its scale and use cases for OSF decision making. 2. The other question you have posted below is questions related to, if the decision makers used the Logo program guidance formulated by InteropWG and challenges they faced in evaluating offers from commercial providers supporting OpenStack. We like to add the question 5 from InteropWG to be added to user-survey in case they like to deploy Bare metal & "Kubernetes-ready OpenStack" in their deployments as below or some edited form to bring in as decision makers focus on using facts presented in marketplace by participants in logo program.{5.What would you like to see improve in current Marketplace Logo Program?[a] Do you want to add Interop for bare metal service?[b] Do you want to see a new Logo progam called "Kubernetes-Ready OpenStack"? This designation would basically say "any Kubernetes distribution that supports the OpenStack cloud provider should run on this vendor's OpenStack product"}

3. Sure you can add question to users-survey regarding Object Storage Swift and the back end drivers they use for maintaining them in-tree. Plus any additional guidelines or logo programs we may need to enhance its usability. 4. Finally, we do want to hear from marketplace participants polling as all questions 1-5 (https://etherpad.opendev.org/p/interop-polling-2020) we have framed for reviving their interests in leveraging and enhancing InteropWG future branding opportunities for OSF.

Hope this clears the questions you have posed and lets know what we can do to sustain and enhance InteropWG efforts.Like other InteropWG members to pitch-in or a simple +1 reply to let Alison handle the rest. ThanksPrakash For InteropWG On Friday, July 17, 2020, 12:23:27 PM PDT, Allison Price <allison@openstack.org> wrote:

              Hi Prakash,

I can help. Going to move some folks to bcc because I have a few questions that I want to clarify with you as I review these additions. Are you wanting these added to the OpenStack User Survey (openstack.org/user-survey) that we share results on annually? Or are you referring to a different survey? Some of these questions seem more directed towards Marketplace vendors, so I wasn’t sure if there was another survey you were referencing. There are already two Interop questions added in the survey that I have included a screenshot of below. Some of these questions, we can get the information from other responses in the User Survey, like around Object Storage

Any additional context will be helpful, including what you’re hoping to understand from the results. Happy to help in any way I can. Thanks,Allison

On Jul 17, 2020, at 2:11 PM, Mark Collier <mark@openstack.org> wrote: adding Allison price, who works on a lot of our survey designs. Allison, can you take a look? On Jul 17, 2020, at 1:57 PM, prakash RAMCHANDRAN <pramchan@yahoo.com> wrote:

Ashlee, Here is InteropWG suggested questions to OSF Exec team to edit as necessary and provide us feedback from marketplace participants as well include as part of Open Infrastructure Summit 2020 for annual OpenStack 2020 survey. OpenDev Etherpad OpenDev Etherpad

Since you have been facilitating other Projects to add their questions for poll, here is our efforts to help arrive at what's the direction interopWG need to take based on feedback. If you have any questions to clarify please reply all as we have been formulating this questions over several meetings and deliberations and have documented the logic etc. in our regular community meetings in https://etherpad.opendev.org/p/interop

ThanksFor InteropWG Prakash

Friday Juy 17th

Refer to remianing one from last week - went through last weeks AIs.

Some discussions on Licensing Open Stack Open License (OS OL) for Open Infra projects exception processing This is part of discussions to be taken to board based on new https://openinfralabs.org/ inclusiaon as new project or seperate org Described university network use case for Manageability but turns out Interop can not touch admin APIs. Hence we look at some of the followings Some discussion of possible interop programs:

   * If I as a vendor want to offer Kuberentes and OpenStack to end users...
      * I'll probably provide Kubernetes conformance test suite results (to show I have an interoperable K8s) and RefStack results (to show I have an interoperably OpenStack).
     * There's not really anything we (InteropWG) need to do for this use case...it's covered by the existing tools/programs.
  * If I as a vendor want to offer a product that runs OpenStack in Kubernetes...
     * Again, there's not a lot for us to do here: if OpenStack is what is exposed to the end user, then I simply need to run RefStack against that OpenStack to show compliance with Powered guidelines
  * If I as a vendor want to provide an OpenStack offering that provides all the necessary API's and capabilities needed by the OpenStack cloud provider for K8s (K8s on top of OpenStack):
     * https://github.com/kubernetes/cloud-provider-openstack
     * Are all these API's coverged in the OpenStack Powered program today?  ¯\_(ツ)_/¯
     * Should we have a new logo program (let's call it "Kubernetes-Ready OpenStack" for the moment) that lets vendors certify that their product is interoperable with the OpenStack cloud provider?
     * This could be done with a new guideline document that includes tests & designated sections of code specifically for the API's that the OpenStack cloud provider calls.
     * This designation would basically say "any Kubernetes distribution that supports the OpenStack cloud provider should run on this vendor's OpenStack product"
     * How many vendors would be interested in this? - Can we add his to poll question? +1+1+1

July 10th

AI-03 - (for Core + Add-ons for OpenStack Integrated Projects) - Can you volunteer to add tag assert:supports-api-interoperability to your projects? Any comments on what Projects need to do to claim this based on 2020.06 - interop - https://opendev.org/osf/interop/src/branch/master/2020.06.json

- We should send email notcies to marketplace participants to update their distros/hsoted solutions/public cloud etc. - OSF foundation should havd the list to send. - We should send the Quationnair as poll to marketplace and other reevant partciapnts (openirrastructure.labs/ OPen Infrastucuture)

Can someone take a crack at documenting how to for one project like nova compute api does now? - assert:supports-api-interoperability Need guidelines standardization for interoperability

           - Version & Discovery should be consistant despite variations in flow 

AI-04 - Seeking volunteers to maintain - Refstack - https://opendev.org/osf/refstack - Maintenance of refstack - Ganesh Hiregaudar (VMWare) + Pavan Dikonkar (team) and/or University/Student support.

AI-05 - Can someone volunteer to present  at next Interop meeting Friday 3rd at 17 UTC (10 AM PDT) - https://github.com/cncf/k8s-conformance

Presenter to be identified. ??*

  • . Ideas for new logo programs to propose to Board working with TC

- Any legal disclaimers or change required - Conformance or validation vs. compliance? - Revising Object Storage Logo for Swift Compliance (For Platinum/Gold partners) - Bare Metal Ironic - Independent then how will it release and maintain Interop in Victoria? - https://releases.openstack.org/victoria/index.html - cycle-with-intermediary? likely 3 releases / when will we introduce interop (assert interop)


- Container Projects (Zun, Magnum, Kola, Kuryr) - Container projects - How do they follow release goverance https://governance.openstack.org/tc/reference/projects/release-management.html / how will we introduce k8s conforamce? how with or without tempest? - Airship Cloud to StarlingX Edge Interop, Can we introduce k8s conformance - what is anyway, any tests - - kubernetes Conformance for OpenStack & Open Infra Projects. - Where is CI/CD in CNCF for k8s conformance- Can we borrow or we already have in Tempest for Zun? - Can Serchlight - Resource Type {OS::

Next Friday - July 3rd - Meeting Canceled due to July 4 long week end in USA

Friday June 26th

1.Interop Ussuri Guidelines established - documented the details in here and merged. https://storyboard.openstack.org/#!/story/2007510


(Add above your suggestions) level 2 Q&A 1. Do you use data on add-on programs in the OpenStack Marketplace? 1.1 If yes which ones?

2. To supersede or abandon this.https://blueprints.launchpad.net/refstack/+spec/interop-2020.06 - Ghanshyam or Mark - please confirm AI-01 - GM to update/close? launchpad item - https://blueprints.launchpad.net/refstack/+spec/interop-2020.06 With following two references to storyboard for all API guidelines for 2020.06.json. https://storyboard.openstack.org/#!/story/2007509 https://storyboard.openstack.org/#!/story/2007510

3. Marketplace participants AI-02 Regards to Survey questions - https://storyboard.openstack.org/#!/story/2007511

6/26/2020 - AT todays Interop call it was decided to add following questions and is being circulated for updates via openstack-discuss list.

1. Do you use OpenStack Marketplace data for your decision on use of OpenStack Cloud? - User Survey/Operator Survey 2. Do you look for at Interoperability OpenStack Powered Logo when selecting an OpenStack product reports available to you on different offerings in Marketplace portal? -User Survey/OperatorSurvey 3. If you offer OpenStack Cloud do you use the OpenStack logo programs.? -Ecosystem Survey/Opertor Survey 4. If you are using Object Storage for your cloud do you use Swift? - User Survey/Operator Survey 5.What would you like to see improve in current Marketplace Logo Program? -Ecosystem Survey/Operator Survey [a] Do you want to add Interop for bare metal service? [b] Do you want to see a new Logo progam called "Kubernetes-Ready OpenStack"? This designation would basically say "any Kubernetes distribution that supports the OpenStack cloud provider should run on this vendor's OpenStack product"

4. The Content & Procedure of Survey to be identified and agreed

    - How to send message to Vendors , Distro's, Hosting Partners and other  Marketplace participants to test for Logo updates for 2020.06 Ussuri cycle          -  Consistency in meeting times on irc and websites 
           - Update site for logo - https://www.openstack.org/brand/interop/
           - update site for irc meeting time - https://refstack.openstack.org/#/about#about 

5. Implementing updates to project governance - https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml How to enable tag assert:supports-api-interoperability (for Core + Add-ons for Integrated Projects) tags:

       - tc:approved-release
       - starter-kit:compute
       - vulnerability:managed
       - assert:follows-standard-deprecation
       - assert:supports-upgrade
       - assert:supports-rolling-upgrade
       - assert:supports-accessible-upgrade
       - stable:follows-policy
       - assert:supports-api-interoperability

Chair / Interop WG (Prakash Ramchandran) Co-Chairs (Mark V.Voelker & Ghanshyam Maan) Rep. from Board (Arkady Kanevsky)

Friday 19th

Meeting cancelled

Please use thi bride for PTG June 1 : monday 6/1/2020 **************************************************************************

Please join Interop WG meeting Jun1 UTC 13-15 (2 hrs) Austin room zoom link - https://www.openstack.org/ptg/rooms/austin


Management Meetings (Master for all refrences) Refere to link for technical details for 2020.06 guideliens - https://etherpad.opendev.org/p/interop2020 / Meeting Bridge : https://zoom.us/j/914761969 (NA/EU -PDT Fridays 10 AM) 10-10.45 Please use? Meeting Bridge: : (APJ -BJT Fridays 9 AM ) - APJ Bridge

May 29th - PDT 10.00 AM

Bridge will try both
https://meetpad.opendev.org/Interop-WG-weekly-meeting (Sorry this did not work) 
< password: 101045 **********************************************************************************************

Attendees Prakash Ghanshyam Mark (late) Topics 1. Meetpad does not work as expected /Decided that we will use Zoom instead

2. Nova - compute api testing https://refstack.openstack.org/#/results/d950f90f-fcc9-4216-962e-2bd0ce4b6fea We just pickedup NOT PASSED in "next " to see why compute list failure show up in Refstack when the regular nova is passing it? stack@ubuntu-os-host:~/tempest$ tempest run --regex tempest.api.compute.servers.test_list_server_filters.ListServerFiltersTestJSON.test_list_servers_filtered_by_ip Make sure the Usuri has cirros image to test

3. Tasks to complete for approving guidelines for 2020.06 by June 10th a. Verify all changes Reviewed relevant APIs Identity (Keystone) https://docs.openstack.org/api-ref/identity/v3/index.html# Comute + Image (Nova, Glance) https://docs.openstack.org/api-ref/compute/ https://docs.openstack.org/api-ref/image/v2/index.html Networking (Neutron) https://docs.openstack.org/api-ref/network/v2/index.html Block Storage - Cinder https://docs.openstack.org/api-ref/block-storage/v3/index.html Object Store (Swift) https://docs.openstack.org/api-ref/object-store/

add-ons Orchestartion https://docs.openstack.org/api-ref/orchestration/v1/index.html DNS https://docs.openstack.org/api-ref/dns/

b. Clean up the flagged tests

Myay 29th - AsiaPacifc meeting 9 AM BJT Dr Li Kiai Prakash Ramchandran Tried - https://meetpad.opendev.org/Interop-WG-weekly-meeting (Failed) Tried - , https://Dell.zoom.com.cn/j/94921799892?pwd=R3RESHVQWWl6WC8vTUcvUEROTW9sUT09 - Failed

The Audio did not work and decides to abnndon but send info to marketing@99cloud.net for follow up for adding topics to https://etherpad.opendev.org/p/interop_virtual_ptg_planning_june_2020

Friday May 22

Prakash Ramchandran Mark Voelker

Request email to community for guidelines review

Interop WG approvel sceduled for June 11 - https://wiki.openstack.org/wiki/Governance/Foundation#OpenStack_Board_of_Director_Meetings

Friaday May 15th

Prakash Ramchandran Kanevsky Arkady Ghanshyam Mann

Ussuri Release announcement http://lists.openstack.org/pipermail/openstack-announce/2020-May/002035.html

Reviewing Release Notes for API changes https://review.opendev.org/#/c/722137/

TODO: Ghanshyam to remove the deprecated tests from new guidlines and add a patch https://review.opendev.org/#/c/728564/ Review 'Advisory' with Mark and apply new patch Prakash to check for new 'Required' capabilities from Ussuri release. Send mail to PTL on openstack-discuss about new core capabilities: Core + adds-on Review microversion(or any API versioning mechanism) is deffered to post release.

Review Next in Refstck for test passings https://refstack.openstack.org/#/results/d950f90f-fcc9-4216-962e-2bd0ce4b6fea

Friday May 8

Prakash Ramchandran Mark Voelker

Worked through core and add-ons reviiewing scores and API and finally decided to commit Patch 4. Mark Added Prakash for +2 Interop WG Reop Prakash Added for Arkady +2 InteropWG Repo We still will retaning Egle Sigler for the work she has done and hope she may return infuture. For now Draft is mearged for testing. Once we have few tests run by current or any new Marketplace Distro or Vendor offerings Plest test for 2020.06 draft and provide feedback...over next few weeks x

Board Approval request? - Got email from Alan scheduling it for June planning for PTG https://etherpad.opendev.org/p/interop_virtual_ptg_planning_june_2020

Core Scoring - Cutoff - 74 of 102 A - Atomic - 6 U - Used by Clients (Nova, Neutron etc.) - 10 C - Complete - 10 W - Widely Deployed - (muliple Proviers) - 8 D - Discoverable (Service through keystone and introspection) - 8 D - Documented - 8 F - Foundation - Tests for uinversl Dependencies - 9 F - Future Direction (TC recommended for verions & compatible) - 11 P - Proximity reletaed to Coe - 8 S - Stable - 9 S - Sticky -Must pass per release - 9 U - Used by Tools of External Providers like Rackspace, RightScale, JCloud - 6

Add-ons scorinng Cutoff 60 AUCDDF A - Atmoic - 6 U - Used by Clients - 10 C - Complete -10 D -Discoverable -8 D - Documented - 8 F- Future -11

Reviewed relevant APIs Identity (Keystone) https://docs.openstack.org/api-ref/identity/v3/index.html# Comute + Image (Nova, Glance) https://docs.openstack.org/api-ref/compute/ https://docs.openstack.org/api-ref/image/v2/index.html Networking (Neutron) https://docs.openstack.org/api-ref/network/v2/index.html Block Storage - Cinder https://docs.openstack.org/api-ref/block-storage/v3/index.html Object Store (Swift) https://docs.openstack.org/api-ref/object-store/

add-ons Orchestartion https://docs.openstack.org/api-ref/orchestration/v1/index.html DNS https://docs.openstack.org/api-ref/dns/

Tempest for Testing APIs with idempotetnt_id for tests with 1-to-may releations / API testing may use multiple ids in guidelines file https://opendev.org/openstack/tempest/src/branch/master/tempest/api/compute/test_versions.py

Friday May 1

eed few decisions 1. Should-add ons for Heat and Designate be in separate file like 2020.06.json or 2020.06.nn.json - keep it seperate but can submit as sinle patch

  Past guidelines: https://opendev.org/openstack/interop/src/branch/master/add-ons/

Chat notes for Mark for creating add-ons for 2020 for orchestartion & dns

  wget https://github.com/openstack/interop/blob/master/add-ons/orchestration.2019.11.json

Or rather: wget https://github.com/openstack/interop/blob/master/add-ons/orchestration.2019.11.json

Complete 3rd Patch Done - https://review.opendev.org/722137 [Call for content review]

Please add your name for review if you have time, we need few +1s and two +2's Mark & Egle can review and give +2 All others including Arkady, Ghansyam, Dr Likai & Mohammad can provide a +1 after reviewing for us to close with zero or more patches as needed based on review.

2. If separate can some one volunteer or should I add to single file and we filter out test results for logo mark as part of validations. The Process used to be Next in Refstack Window lie https://refstack.openstack.org/#/results/d950f90f-fcc9-4216-962e-2bd0ce4b6fea So pre-approval testing was done through next json file. Since we are short on time have decided to lump in basic plus add-ons as one patch and after code review we will merge and let tests be done with pending board approval. But will ask for approval at next Baord meeting

3. Do we review in meeting and make a call and then send to opestack-discuss mail for confirming release changes for needed 80 + 18 current api scenario's (Compute + Storage) or other way round? This is answered in 2 above as we are short circuting the process, as all we cars is user level APIs for respective modules and scores included from 2019.11.json gudieleines

4. Plans for beyond June In Victoria for interop. There are two ways to support Edge Cloud logos in OpenStack 1.Use hierarchial Openstack with Central and Distributed nodes with different stack components (specifically Glance matser and Glance with replication for local availability of images to boot for Edge Applications per tenant) 2. Federated Edges with Stacks as they need to run OpenStack at scale individual locations need

How to do this and what APIs additions this brings in, we willreview next week. 1.

5. Other suggestions from Asia Pacific team.

Check this out for Compute https://etherpad.opendev.org/p/interop2019 or https://refstack.openstack.org/#/results/d950f90f-fcc9-4216-962e-2bd0ce4b6fea See if can get something for 2020.06 without approval?

API-Docs - https://docs.openstack.org/api-ref/ US/EU APJ

Friday 24, April 2020 / 10 AM PDT

Present Prakash Ramchandran Arkady Kanevsky Ghanshyam Mann


    To Review : https://blueprints.launchpad.net/refstack/+spec/interop-2020.06 (new bp reday for review -refer tech work link at the top)
   Fix metadat -> 2020..06 to 2020.06 -Arkady (Done)
   Mark's reviews & questions - discuss and fix online
    Add DNS? combine or seperate?

Add Orchestration? combine or seperate? Drop Ceilometer? ( No replacers with Aodh or any telemetry modules?) - For now dropping out, will check with Mark/Mohammad for add-on for telemetry

Sure this is draft not approved, we can correct. - fixed removed approved to draft

Also any other thoughts on alternate orchestration based on kubernetes api as sub for heat orchestration? TBD - for now assiging heat orchestartion work to Mark if he can volunteer

Heat creates VM stacks and k8s for crio based for containers or pods (? stacks not sure, may be clusters+pods/+servcies).

Also openstack control plane using containers as CAPO provider.

Let's do review these crazy possibilities too. What was the logic earlier in 2019.11 to keep DNS and Orchestration out of core? Comparing the flexibility offered by k8s to use cluster DNS as a "Service" over coreDNS as internal name registry for PODs. In OpenStack case we have mixup between Glance rgeistry versus designate versus Heat and may need relook as how to simplify, if we really want to make it flexible.

    Revise the story2000-7507,-7509,-7510
    Review OpenStack Controle Plane in CAPI - 
    Review Image needed for container based Openstack Controller in SCI Image builder - https://image-builder.sigs.k8s.io/capi/providers/openstack.html

Friday 24, April 2020 / 9 AM BJT

Present Prakash Ramchandran Dr Li Kai

How do we handle new Profiles for NFV, Edge, Hybrid Cloud, HPC We shoul look at Contianer based OpenStack Control plane as a target. This will also mean we need an image that we can use for different mdules or service_types as in microservcies We can review Adjecensies as how Airship uses OpenStack Control plane and workloads - Refer https://etherpad.opendev.org/p/interop2020 Zun APIs for Capsules/PoDs may be an answer along with Magnum or kuryr https://wiki.openstack.org/wiki/Kuryr We will see if add-ons like orchestartion & desgnate , we can add for Zun...

Friday 17, April 2020 /10 AM PDT

Prakash Ramchandran

                  Mark T. Voelker
                  Arkady Kanevsky
        Discovering what to do now and beyond in 2020

              Discussed on CAPI over OpenStack API for K8s based cluster
              Whay not do Direct in OpenStack through Zun or OoK like Airshi?                            

Friday 10 , April 2020 /10 AM PDT

Attendees: Prakash Ramchandran

                  Mark T. Voelker
                  Mohammad Naser
   Prakash started working on Train Refstack and created a BP for    Train
   https://blueprints.launchpad.net/refstack/+spec/refstack-train-api - Superseded as suggeted by Mark.
   story2007510 -on hold
   story2007507 -on hold
   story2007509 -on hold
   Define the Specs: INPROGRESS (will be revised based on new bp/2020.06 refer next week entry)
   Approve the Specs: TODO
   Implement the Specs for One Vendor: TODO


   2019.06 does cover Train but not Usuri [1], 2019.11 covers both [2]               

[1] https://opendev.org/openstack/interop/src/branch/master/2019.06.json#L75 [2] https://opendev.org/openstack/interop/src/branch/master/2019.11.json#L75

    More discussions on covering Hybrid and Multi-cloud

Friday 10. April 20 / 9 AM BJT (6.30 PDT Thu) -APJ bridge

Attendees: Prakash Ramchandran

                 Dr Li Kai 

https://Dell.zoom.com/wc/join/94921799892 (APJ -BJT Fridays 9 AM ) - APJ Bridge Password 200011 Topic: Briefing APJ partcpants what was presented to Board 0n April 4 - https://wiki.openstack.org/wiki/Governance/Foundation/14April2020BoardMeeting

           Feedback needs to adddress new areas
             Sugessions from Dr Li Kai for looking at  Edge &  Hybrid CLoud Interoperability

Friday 3, April 2020

Attendees: Prakash Ramchandran

                  Mark T. Voelker
                  Ghanshyam Maan


   Where to Start and What to do?
   Reviwe RefStack, Tempest and Interop


   Show we expand the Program to cover NFV, Containers etc. - First get to do minimum for next release
   Can we look at K8s compliance for OpenStack Projects. - May be not since Source codes may  not be owned by or Licenses my differ
   Think out-of box for other compliance + Compatibility logo marks like Oen Infra Logog Mark etc.
   Prakash to review Refstack & Tempest
   Prakash Preparing slides for Board for rebooting InteropWG -Shared tentative Slides