Update tox in Python modules/projects

[Sebastian Kalinowski]

We should update minimum tox version in tox.ini to one of the recent one and remove all the deprecated/integrated into core settings from our tox.ini. For example:

https://github.com/stackforge/fuel-web/blob/4b325a95b0217a26a17f526cb734b3748cb03e12/nailgun/tox.ini#L9

setenv = VIRTUAL_ENV={envdir}

Since tox 1.8 VIRTUAL_ENV var is set by tox directly and it doesn't have to be set in tox.ini anymore.

tox will need to be updated also on our CI servers.

[Ihor Kalnytskyi (ikalnytskyi)]

Actually, I don't even know why it's important to set up this damn variable. I thought it's used for various third-party scripts and not intended for general use. I mean, if we remove it - all should work fine.

[Sebastian Kalinowski (prmtl)]

It's set to tell that we are in virtualenv - virtualenv sets VIRTUAL_ENV env also.

[Ihor Kalnytskyi (ikalnytskyi)]

Yep, I know what it does. The point is I don't know why should we have it. I mean, afaik it's a helper stuff for outside world and not intended to be used by tests.

[Dmitry Pyzhov (dpyzhov)]

This bug does not affect build. So we can merge fix even after SCF

[OpenStack Infra (hudson-openstack)]

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

[Nikolay Markov (nmarkov)]

This one is now blocked by https://bugs.launchpad.net/fuel/+bug/1441074

[Nikolay Markov (nmarkov)]

Request for this: https://review.openstack.org/#/c/171108/

Also, looks like this bug is frozen until new tox is in our CI process.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: master
Review: https://review.openstack.org/171108
Reason: This review is > 4 weeks without comment and currently blocked by a core reviewer with a -2. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -2 on this review to ensure you address their concerns.

[Dmitry Pyzhov (dpyzhov)]

We passed SCF in 8.0. Moving the bug to 9.0.