Some tests are not performed under py34 environment

[Eva Balycheva]

For example, lets perform MongodbFlavorsTest from:
zaqar.tests.unit.storage.test_impl_mongodb package
under python 2 using this command:
tox -r -epy27 -- MongodbFlavorsTest
The log is normal:
http://paste.openstack.org/show/JWTgydALfVxPw37oQ1bf/

And now let's try to do the same under python 3.
tox -r -epy34 -- MongodbFlavorsTest
The log is not normal because no tests were performed:
http://paste.openstack.org/show/lSim4UIq4OF8eV8VwRPn/

The problem occurs because some environment variables are not defined in tox.ini for py34 environment.
These variables are:
ZAQAR_TEST_MONGODB=1
ZAQAR_TEST_SLOW=1

And when these variables are not defined, many tests are being skipped during testing.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/242182

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/242182
Committed: https://git.openstack.org/cgit/openstack/zaqar/commit/?id=bee3926423d2fb666589cb43396f9c52778eef2c
Submitter: Jenkins
Branch: master

commit bee3926423d2fb666589cb43396f9c52778eef2c
Author: Eva Balycheva <email address hidden>
Date: Wed Oct 21 18:54:59 2015 +0300

    Fix tox not performing some tests in some Envs

    Many tests are being skipped while testing using tox in some
    environments.
    That's because some important environment variables are not defined for
    these environments:
    pypy, py34.
    The variables are:
    ZAQAR_TEST_MONGODB=1
    ZAQAR_TEST_SLOW=1
    This change defines these environment variables in tox.ini. And not only
    for the few environments that need such variables, but for all
    environments. Because it's the most simple way to do it in which I see
    no harm.
    Also this change deletes deprecated python environments (py26 and py33)
    from the list of environments.

    Depends-On: I37937ffe9b71323a92880f678e84c7c24e6872d6
    Change-Id: I3a8cef038ed9a37c8dc29850dfdda31b72c05883
    Closes-Bug: 1508519

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/zaqar 2.0.0.0b1 development milestone.