Open Stack

> > It might be better to work with the python-dbus authors to get a
> > pip-installable package released to PyPI, so that it can be included
> > in the tox virtualenv (though for DevStack we'd still want to use
> > distro packages instead of PyPI, I think).
> I sent Simon an email about that now.
I talked to him today.

The recommendation is to use the available (distribution) packages, because 
he's had bad experiences with the distutils build system, so he wants to 
stick to the Autotools - and the general issues (needing a C compiler, some 
header files) would be the same with other libraries, too.



> > > You'll also need to modify cinder's tox.ini to set "sitepackages =
> > > True" so the virtualenvs created for the unit tests can see the global
> > > site-packages directory. Nova does the same thing for some of its
> > > dependencies.
> > ... I'm a little worried about taking on
> > sitepackages=True in more projects given the headaches it causes
> > (conflicts between versions in your virtualenv and system-installed
> > python modules which happen to be dependencies of the operating
> > system, for example the issues we ran into with Jinja2 on CentOS 6
> > last year).
> But such a change would affect _all_ people, right?
> Hmmm... If you think such a change will be accepted?
So we're back to this question now.


While I don't have enough knowledge about the interactions to just change 
the virtual-env setup in DevStack, I can surely create an issue on 
https://github.com/openstack-dev/devstack.


How would this requirement be done for "production" setups? Should 
installers read the requirements.txt and install matching distribution 
packages?

Or is that out of scope of OpenStack/Cinder development anyway, and so 
I can/should ignore that?


Regards,

Phil

-- 
: Ing. Philipp Marek
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting                 http://www.linbit.com :

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.