Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-29 Thread Daniel P. Berrange
On Tue, Aug 06, 2013 at 11:36:44PM -0300, Monty Taylor wrote: On 08/06/2013 11:14 PM, Robert Collins wrote: On 7 August 2013 11:22, Jay Buffington m...@jaybuff.com wrote: ln -s /usr/lib64/python2.6/site-packages/libvirtmod_qemu.so $(VENV)/lib/python2.6/site-packages/ Why

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-08 Thread Daniel P. Berrange
On Tue, Aug 06, 2013 at 11:36:44PM -0300, Monty Taylor wrote: On 08/06/2013 11:14 PM, Robert Collins wrote: On 7 August 2013 11:22, Jay Buffington m...@jaybuff.com wrote: ln -s /usr/lib64/python2.6/site-packages/libvirtmod_qemu.so $(VENV)/lib/python2.6/site-packages/ Why

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-08 Thread Pádraig Brady
On 08/07/2013 06:54 PM, Monty Taylor wrote: On 08/07/2013 12:53 PM, Joshua Harlow wrote: I agree triple-o will help a lot here although I would disagree that package rollback is an illusion. I would call it more of a hard problem instead since nothing is really impossible :) illusion

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-08 Thread Monty Taylor
On 08/05/2013 02:03 PM, Dean Troyer wrote: [Moving a discussion from https://review.openstack.org/40019 to the ML to get a wider audience] We've been around this block more than once so let's get it all documented in one place and see where to go next. Skip down to # for more

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-08 Thread Pádraig Brady
On 08/08/2013 02:10 PM, Monty Taylor wrote: On 08/05/2013 02:03 PM, Dean Troyer wrote: [Moving a discussion from https://review.openstack.org/40019 to the ML to get a wider audience] We've been around this block more than once so let's get it all documented in one place and see where to

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-08 Thread Joshua Harlow
Just an idea how this could go (without saying just use anvil). Taking from how anvil is doing it the following might work: 1. In devstack pass all the requirement files to multipip to get a unified list back. 2. Use yumfind (maybe a similar utility that integrates with apt-get/apt also?) to

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-08 Thread Ian Wienand
On Thu, Aug 08, 2013 at 10:10:09AM -0300, Monty Taylor wrote: I don't think we will gain much by auto-generating packages. What really is the difference between devstack auto-generating a package and having a human basically doing the same thing and sticking it in a repo? It just seems

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-07 Thread Clint Byrum
Excerpts from Joshua Harlow's message of 2013-08-06 21:03:58 -0700: It does seem sad that the state of package management is this bad. It'd would be equally interesting to hear how others rollback changes (another thing yum doesn't do so well, since it doesn't have a good ability to

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-07 Thread Monty Taylor
On 08/06/2013 11:39 PM, Robert Collins wrote: On 7 August 2013 14:36, Monty Taylor mord...@inaugust.com wrote: On 08/06/2013 11:14 PM, Robert Collins wrote: On 7 August 2013 11:22, Jay Buffington m...@jaybuff.com wrote: ln -s /usr/lib64/python2.6/site-packages/libvirtmod_qemu.so

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-07 Thread Joshua Harlow
I agree triple-o will help a lot here although I would disagree that package rollback is an illusion. I would call it more of a hard problem instead since nothing is really impossible :) If say yum had a git like log then I don't think it would be impossible to yum checkout a previous system

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-07 Thread Jeremy Stanley
On 2013-08-07 15:53:54 + (+), Joshua Harlow wrote: I agree triple-o will help a lot here although I would disagree that package rollback is an illusion. I would call it more of a hard problem instead since nothing is really impossible :) [...] SCO OpenServer (shudder) for all its

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-07 Thread Monty Taylor
On 08/07/2013 12:53 PM, Joshua Harlow wrote: I agree triple-o will help a lot here although I would disagree that package rollback is an illusion. I would call it more of a hard problem instead since nothing is really impossible :) illusion with current packaging systems yum/rpm and

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-06 Thread John Dennis
On 08/06/2013 11:19 AM, Dean Troyer wrote: And that is the crux of the problem. When both can be installed side-by-side and sys.path is in control of the order, things work. This is such a fundamental problem in the distro that I am beginning to thing that we need to address it ourselves.

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-06 Thread Jay Buffington
On Tue, Aug 6, 2013 at 8:35 AM, Joshua Harlow harlo...@yahoo-inc.comwrote: I think jay your usage also was before anvil started to build all the *missing* dependencies automatically (something u inspired me to get going in the first place) so hopefully said updates to rhel.yaml are only now

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-06 Thread Monty Taylor
On 08/06/2013 02:44 PM, Mate Lakat wrote: Hi, I would say, use a separated virtual environment in devstack - without the --system-site-packages switch, of course, and set it up as a user. Install the packages that are needed in order to be able to pip install them (like libxslt-dev). It's

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-06 Thread Jay Buffington
On Tue, Aug 6, 2013 at 12:00 PM, Monty Taylor mord...@inaugust.com wrote: On 08/06/2013 02:44 PM, Mate Lakat wrote: I would say, use a separated virtual environment in devstack - without the --system-site-packages switch, of course, and set it up as a user. Install the packages that are

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-06 Thread Robert Collins
On 7 August 2013 11:22, Jay Buffington m...@jaybuff.com wrote: ln -s /usr/lib64/python2.6/site-packages/libvirtmod_qemu.so $(VENV)/lib/python2.6/site-packages/ Why isn't libvirt-python on pypi? AFAICT, nothing is stopping us from uploading it. Maybe we should just stick it on there and

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-06 Thread Robert Collins
On 6 August 2013 05:03, Dean Troyer dtro...@gmail.com wrote: * Continue to factor the prereq setup out of stack.sh such that requirements.txt is satisfied one way or another before it begins to install OpenStack. tools/install_prereqs.sh and tools/install_pip.sh are the prototypes for this.

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-06 Thread Monty Taylor
On 08/06/2013 11:14 PM, Robert Collins wrote: On 7 August 2013 11:22, Jay Buffington m...@jaybuff.com wrote: ln -s /usr/lib64/python2.6/site-packages/libvirtmod_qemu.so $(VENV)/lib/python2.6/site-packages/ Why isn't libvirt-python on pypi? AFAICT, nothing is stopping us from

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-05 Thread Joshua Harlow
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages I've been doing continuous deployment via rpms on RHEL 6u3 of glance, keystone, neutron and nova for about six months now. I used Anvil for the first three months

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

2013-08-05 Thread Ian Wienand
On Mon, Aug 05, 2013 at 12:03:07PM -0500, Dean Troyer wrote: * proposals to use a tool to automatically decide between package and PyPI (harlowja, sdague): this works well on the surface, but anything that does not take in to account the dependencies in these packages going BOTH ways is going