[openstack-dev] excessively difficult to support both iso8601 0.1.4 and 0.1.8 as deps

Matthias Runge mrunge at redhat.com
Thu Nov 28 10:53:26 UTC 2013

On 11/27/2013 06:46 PM, Alan Pevec wrote:
> 2013/11/27 Sean Dague <sean at dague.net>:
>> The problem is you can't really support both iso8601 was dormant
>> for years, and the revived version isn't compatible with the old
>> version. So supporting both means basically forking iso8601 and
>> maintaining you own version of it monkey patched in your own tree.
> Right, hence glance was added https://review.openstack.org/55998 to 
> unblock the previous gate failure. Issue now is that stable/grizzly
> Tempest uses clients from git trunk, which is not going to work since
> trunk will add more and more incompatible dependencies, even if
> backward compatbility is preserved against the old service APIs!
> Solutions could be that Tempest installs clients into separate venv
> to avoid dependecy conflicts or establish stable/* branches for 
> clients[1] which are created around OpenStack release time.
I'd like to propose to switch testing for stable branches:

We should switch to install environments for stable releases through
other methods, such as packages. There are quite a few provisioning
methods out there right now.

The benefit would be, we'd have a very reproducible way to build
identical environments for each run; the cost would be, that we'd need
to create a test environment for each project: install everything but
the project to test via packages.

When choosing packages to install: which one do we want to take? Just a
single source or take for each (major) distribution, thus multiplying
effort here?


More information about the OpenStack-dev mailing list