From egle.sigler at rackspace.com Mon Nov 12 13:05:10 2018 From: egle.sigler at rackspace.com (Egle Sigler) Date: Mon, 12 Nov 2018 13:05:10 +0000 Subject: [Interop-wg] Interop WG Berlin Session Message-ID: Please join for in-person session if you are attending the Berlin Summit. Tuesday, November 13, 1:40pm-2:20pm Hall 7 - Level 1 - 7.1b / London 1 https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22887/interop-wg-berlin-session Etherpad: https://etherpad.openstack.org/p/InteropBerlin2018 thank you, Egle -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2083 bytes Desc: not available URL: From gmann at ghanshyammann.com Thu Nov 29 16:17:05 2018 From: gmann at ghanshyammann.com (Ghanshyam Mann) Date: Fri, 30 Nov 2018 01:17:05 +0900 Subject: [Interop-wg] [dev] [cinder] [qa] Strict Validation for Volume API using JSON Schema Message-ID: <16760426d56.ef4c345622903.2195899647060980382@ghanshyammann.com> Hello everyone, Tempest is planning to add the strict API validation using JSON schema for Volume test [1]. We do the same for all the compute test. With *Strict* JSON schema validation, all the API response will be validated with predefined schema with additionalProperties=False. additionalProperties=False will not allow any additional attribute in API response than what upstream APIs has in their current version. For example: If any vendor has modified the API response and returning additional attributes then Tempest tests going to fail. This will help: - To improve the OpenStack interoperability. Strict validation of API response is always helpful to maintain the interoperability. - To improve the volume API testing to avoid the backward compatible changes. Sometime we accidentally change the API in backward incompatible way and strict validation with JSON schema help to block those. We want to hear from cinder and interop team about any impact of this change to them. [1] https://blueprints.launchpad.net/tempest/+spec/volume-response-schema-validation -gmann From mriedemos at gmail.com Fri Nov 30 02:28:24 2018 From: mriedemos at gmail.com (Matt Riedemann) Date: Thu, 29 Nov 2018 20:28:24 -0600 Subject: [Interop-wg] [dev] [cinder] [qa] Strict Validation for Volume API using JSON Schema In-Reply-To: <16760426d56.ef4c345622903.2195899647060980382@ghanshyammann.com> References: <16760426d56.ef4c345622903.2195899647060980382@ghanshyammann.com> Message-ID: <29d271ff-d5a7-2a28-53c1-3be7b868ad20@gmail.com> On 11/29/2018 10:17 AM, Ghanshyam Mann wrote: > - To improve the volume API testing to avoid the backward compatible changes. Sometime we accidentally change the API in backward incompatible way and strict validation with JSON schema help to block those. +1 this is very useful to avoid unintentionally breaking the API. > > We want to hear from cinder and interop team about any impact of this change to them. I'm mostly interested in what the interop WG would do about this given it's a potentially breaking change for interop without changes to the guidelines. Would there be some sort of grace period for clouds to conform to the changes in tempest? -- Thanks, Matt From mvoelker at vmware.com Fri Nov 30 17:58:45 2018 From: mvoelker at vmware.com (Mark Voelker) Date: Fri, 30 Nov 2018 17:58:45 +0000 Subject: [Interop-wg] [dev] [cinder] [qa] Strict Validation for Volume API using JSON Schema In-Reply-To: <29d271ff-d5a7-2a28-53c1-3be7b868ad20@gmail.com> References: <16760426d56.ef4c345622903.2195899647060980382@ghanshyammann.com> <29d271ff-d5a7-2a28-53c1-3be7b868ad20@gmail.com> Message-ID: <8337FB0D-81D3-4E6C-9039-47BD749C3862@vmware.com> > On Nov 29, 2018, at 9:28 PM, Matt Riedemann wrote: > > On 11/29/2018 10:17 AM, Ghanshyam Mann wrote: >> - To improve the volume API testing to avoid the backward compatible changes. Sometime we accidentally change the API in backward incompatible way and strict validation with JSON schema help to block those. > > +1 this is very useful to avoid unintentionally breaking the API. > >> We want to hear from cinder and interop team about any impact of this change to them. > > I'm mostly interested in what the interop WG would do about this given it's a potentially breaking change for interop without changes to the guidelines. Would there be some sort of grace period for clouds to conform to the changes in tempest? > That’s more or less what eventually happened when we began enforcing strict validation on Nova a few years ago after considerable debate. Clouds that were compliant with the interop guidelines before the strict validation patch landed and started failing once it went in could apply for a waiver while they worked on removing or upstreaming the nonstandard stuff. For those not familiar, here’s the patch that created a waiver program: https://review.openstack.org/#/c/333067/ Note that this expired with the 2017.01 Guideline: https://review.openstack.org/#/c/512447/ While not everyone was totally happy with the solution, it seemed to work out as a middle ground solution that helped get clouds on a better path in the end. I think we’ll discuss whether we’d need to do something like this again here. I’d love to hear: 1.) If anyone knows of clouds/products that would be fail interop testing because of this. Not looking to name and shame, just to get an idea of whether or not we have a concrete problem and how big it is. 2.) Opinions on how the waiver program went last time and whether the rest of the community feels like it’s something we should consider again. Personally I’m supportive of the general notion of improving API interoperability here…as usual it’s figuring out the mechanics of the transition that take a little figuring. =) At Your Service, Mark T. Voelker > -- > > Thanks, > > Matt > > _______________________________________________ > Interop-wg mailing list > Interop-wg at lists.openstack.org > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.openstack.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Finterop-wg&data=02%7C01%7Cmvoelker%40vmware.com%7C82a07fe28afe488c2eea08d6566b9734%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C636791417437738014&sdata=lEx%2BbbTVzC%2FRC7ebmARDrFhfMsToM7Rwx8EKYtE7iFM%3D&reserved=0