[interop][cinder] review of next.json

Kanevsky, Arkady Arkady.Kanevsky at dell.com
Thu May 6 18:11:29 UTC 2021

Thanks Brian.
I reviewed the patch and will add other for review.

Yes on #2. Interop is testing portability of applications. Thus, admin APIs are out of scope.
We do use admin token in some cases to setup environment for user testing, as it is done by refstack.

#3. We can add multiple users scenarios to test coverage.
Volume sharing can be part of it.


-----Original Message-----
From: Brian Rosmaita <rosmaita.fossdev at gmail.com> 
Sent: Thursday, May 6, 2021 10:59 AM
To: openstack-discuss at lists.openstack.org
Subject: [interop][cinder] review of next.json


Hello Interop WG,

We began a review of next.json [0] at yesterday's cinder meeting and a few issues came up.

1. The 'description' for the volumes capabilities should be updated; here's a patch:

   https://urldefense.com/v3/__https://review.opendev.org/c/osf/interop/*/789940__;Kw!!LpKI!2qbmsgFRsMwjN02DrU4T1EChrp_HEOngd55x-7TPdBqnN5Yl0sCmHwSx0bWKD3NlENau$ [review[.]opendev[.]org]

2. Are capabilities that require an admin (or system-scoped) token still excluded?

3. Are capabilities that require multiple users for testing (for example, volume transfer) excluded?


[0] https://urldefense.com/v3/__https://opendev.org/osf/interop/src/branch/master/next.json__;!!LpKI!2qbmsgFRsMwjN02DrU4T1EChrp_HEOngd55x-7TPdBqnN5Yl0sCmHwSx0bWKD0CCThmp$ [opendev[.]org]

More information about the openstack-discuss mailing list