Hi Georg, SNAPS-OO has been designed to work with multiple API versions which will not be removed; however, there currently are not any CI jobs that validate the library against older versions. As the API versions have stayed relatively static since Liberty, here are the currently supported versions:
· Keystone – 2 & 3 · Glance – 1 & 2 · Nova – 2 · Neutron – 2 · Cinder – 2 & 3 · Heat – 1, 2, & 3 (same implementation as all seem compatible) I hope this helps clarify things, Steve From: Georg Kunz <[email protected]> Date: Monday, April 23, 2018 at 1:23 PM To: "[email protected]" <[email protected]>, Steven Pisarski <[email protected]> Cc: Dan Xu <[email protected]>, "[email protected]" <[email protected]> Subject: [opnfv-tech-discuss] SNAPS backwards compatibility Hi Cedric, Hi Steven I need to branch the discussion here because Cedric touched upon an aspect I had on my mind for some time, but never came around to properly talk with you about: How (backwards) compatible is SNAPS in terms of OpenStack releases? I am aware that SNAPS had to be adapted to support newer versions of OpenStack in OPNFV. Does a newer version of SNAPS work with an older version of OpenStack? We are currently considering including SNAPS in the next release of OVP. Dovetail will run against commercial system which potentially use “any older version of OpenStack”. I’d like to understand, based on your experience, how closely SNAPS is tied to a specific version of OpenStack. Thanks Georg From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Monday, April 23, 2018 6:19 PM To: Alec Hothan (ahothan) <[email protected]>; [email protected]; David McBride <[email protected]>; Aaron Smith <[email protected]>; Fatih Degirmenci <[email protected]> Cc: [email protected] Subject: Re: [opnfv-tech-discuss] [barometer] Hi Alec, Several upstream projects such as tempest should run vs master. But for instance, we have to disable RefStack when switching to OpenStack Queens as it’s currently linked to testr (what about master?). I’m not sure we can introduce all new testcases in master and then we may develop in stable/gambia too. (It’s not about git operations) From the time being, most of our testcases will fail if Snaps doesn’t support master, Healthcheck included. Most of first operations simply leverage on Snaps (user or flavor creations). Xtesting (Framework) can easily support all 3 branches. That’s out of my concerns as it’s fully cover by unit tests and we don’t need functional gating for it. Since F, Functest-core only contains all the testcase modules (OpenStack) and then all related python dependencies. Yes following both tracks simply forces a Functest and CI/CD refactoring. Cédric
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
