Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 04/15/2015 09:50 PM, Robert Collins wrote: > On 16 April 2015 at 11:59, Sean Dague wrote: > >> I think the completeness statement here is as follows: >> >> 1. For OpenStack to scale to the small end, we need to be able to >> overlap services, otherwise you are telling people they basically hav

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 16 April 2015 at 11:59, Sean Dague wrote: > I think the completeness statement here is as follows: > > 1. For OpenStack to scale to the small end, we need to be able to > overlap services, otherwise you are telling people they basically have > to start with a full rack of hardware to get 1 wor

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 04/15/2015 06:44 PM, Robert Collins wrote: > On 16 April 2015 at 01:50, Sean Dague wrote: >> On 04/12/2015 06:43 PM, Robert Collins wrote: > >>> Thoughts? If there's broad apathy-or-agreement I can turn this into a >>> spec for fine coverage of ramifications and corner cases. >> >> I'm definit

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 16 April 2015 at 07:58, Clint Byrum wrote: > Excerpts from Sean Dague's message of 2015-04-15 06:50:11 -0700: >> == End game? >> >> *If* pip install took into account the requirements of everything >> already installed like apt or yum does, and resolve accordingly >> (including saying that's no

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 16 April 2015 at 01:50, Sean Dague wrote: > On 04/12/2015 06:43 PM, Robert Collins wrote: >> Thoughts? If there's broad apathy-or-agreement I can turn this into a >> spec for fine coverage of ramifications and corner cases. > > I'm definitely happy someone else is diving in on here, just bewar

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 16 April 2015 at 00:51, Jeremy Stanley wrote: > On 2015-04-15 11:06:20 +0200 (+0200), Thierry Carrez wrote: >> And the doc is indeed pretty clear. I assumed "requirements.txt" would >> describe... well... requirements. But like Robert said they are meant to >> describe specific deployments (sho

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 15 April 2015 at 09:35, Joe Gordon wrote: > > > On Sun, Apr 12, 2015 at 6:09 PM, Robert Collins > wrote: >> >> On 13 April 2015 at 12:53, Monty Taylor wrote: >> >> > If we pin the stable branches with hard pins of direct and indirect >> > dependencies, we can have our stable branch artifacts

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 15 April 2015 at 09:33, Joe Gordon wrote: > > > On Tue, Apr 14, 2015 at 2:36 AM, Thierry Carrez > wrote: >> >> Robert Collins wrote: >> > On 13 April 2015 at 22:04, Thierry Carrez wrote: >> >> How does this proposal affect stable branches ? In order to keep the >> >> breakage there under cont

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 14 April 2015 at 21:36, Thierry Carrez wrote: > Robert Collins wrote: >> On 13 April 2015 at 22:04, Thierry Carrez wrote: >>> How does this proposal affect stable branches ? In order to keep the >>> breakage there under control, we now have stable branches for all the >>> OpenStack libraries a

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

Excerpts from Sean Dague's message of 2015-04-15 06:50:11 -0700: > == End game? > > *If* pip install took into account the requirements of everything > already installed like apt or yum does, and resolve accordingly > (including saying that's not possible unless you uninstall or upgrade > X), we'd

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 04/12/2015 06:43 PM, Robert Collins wrote: > Right now we do something that upstream pip considers wrong: we make > our requirements.txt be our install_requires. > > Upstream there are two separate concepts. > > install_requirements, which are meant to document what *must* be > installed to im

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 2015-04-15 11:06:20 +0200 (+0200), Thierry Carrez wrote: > And the doc is indeed pretty clear. I assumed "requirements.txt" would > describe... well... requirements. But like Robert said they are meant to > describe specific deployments (should really be have been named > deployment.txt, or at l

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

> On Apr 15, 2015, at 5:06 AM, Thierry Carrez wrote: > > Joe Gordon wrote: >> On Tue, Apr 14, 2015 at 2:55 PM, Chris Dent > > wrote: >>On Tue, 14 Apr 2015, Joe Gordon wrote: >>deploy requirements - requirements.txt - which are meant to >>be

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

Joe Gordon wrote: > On Tue, Apr 14, 2015 at 2:55 PM, Chris Dent > wrote: > On Tue, 14 Apr 2015, Joe Gordon wrote: > deploy requirements - requirements.txt - which are meant to > be *local > to a deployment*, and are commonly expecte

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On Tue, Apr 14, 2015 at 2:55 PM, Chris Dent wrote: > On Tue, 14 Apr 2015, Joe Gordon wrote: > > Upstream there are two separate concepts. >>> >>> install_requirements, which are meant to document what *must* be >>> installed to import the package, and should encode any mandatory >>> version cons

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On Tue, 14 Apr 2015, Joe Gordon wrote: Upstream there are two separate concepts. install_requirements, which are meant to document what *must* be installed to import the package, and should encode any mandatory version constraints while being as loose as otherwise possible. E.g. if package A de

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On Sun, Apr 12, 2015 at 6:09 PM, Robert Collins wrote: > On 13 April 2015 at 12:53, Monty Taylor wrote: > > > What we have in the gate is the thing that produces the artifacts that > > someone installing using the pip tool would get. Shipping anything with > > those artifacts other that a direct

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On Tue, Apr 14, 2015 at 2:36 AM, Thierry Carrez wrote: > Robert Collins wrote: > > On 13 April 2015 at 22:04, Thierry Carrez wrote: > >> How does this proposal affect stable branches ? In order to keep the > >> breakage there under control, we now have stable branches for all the > >> OpenStack

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On Sun, Apr 12, 2015 at 3:43 PM, Robert Collins wrote: > Right now we do something that upstream pip considers wrong: we make > our requirements.txt be our install_requires. > > Upstream there are two separate concepts. > > install_requirements, which are meant to document what *must* be > instal

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

Robert Collins wrote: > On 13 April 2015 at 22:04, Thierry Carrez wrote: >> How does this proposal affect stable branches ? In order to keep the >> breakage there under control, we now have stable branches for all the >> OpenStack libraries and cap accordingly[1]. We planned to cap all other >> li

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

I think what we are trying to do is two separate things. One is to define the dependencies that packagers use. This would likely be minimum versions with caps that are known to fail (not assumed). The second is to define a set of verifiably known working deps. This would likely need an update m

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 13 April 2015 at 22:04, Thierry Carrez wrote: >> This observation led to yet more IRC discussion and eventually >> https://etherpad.openstack.org/p/stable-omg-deps >> >> In short, the proposal is that we: >> - stop trying to use install_requires to reproduce exactly what >> works, and instead

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

Robert Collins wrote: > On 13 April 2015 at 13:09, Robert Collins wrote: >> On 13 April 2015 at 12:53, Monty Taylor wrote: >> >>> What we have in the gate is the thing that produces the artifacts that >>> someone installing using the pip tool would get. Shipping anything with >>> those artifacts

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On Mon, 13 Apr 2015, Robert Collins wrote: In short, the proposal is that we: - stop trying to use install_requires to reproduce exactly what works, and instead use it to communicate known constraints (> X, Y is broken etc). - use a requirements.txt file we create *during* CI to capture exactly

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

> On 13/4/2015, at 3:53, Robert Collins wrote: > > On 13 April 2015 at 13:09, Robert Collins wrote: >> On 13 April 2015 at 12:53, Monty Taylor wrote: >> >>> What we have in the gate is the thing that produces the artifacts that >>> someone installing using the pip tool would get. Shipping any

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 13 April 2015 at 13:09, Robert Collins wrote: > On 13 April 2015 at 12:53, Monty Taylor wrote: > >> What we have in the gate is the thing that produces the artifacts that >> someone installing using the pip tool would get. Shipping anything with >> those artifacts other that a direct communica

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 13 April 2015 at 12:53, Monty Taylor wrote: > What we have in the gate is the thing that produces the artifacts that > someone installing using the pip tool would get. Shipping anything with > those artifacts other that a direct communication of what we tested is > just mean to our end users.

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 13 April 2015 at 12:01, James Polley wrote: > > > That sounds, to me, very similar to a discussion we had a few weeks ago in > the context of our stable branches. > > In that context, we have two competing requirements. One requirement is that > our CI system wants a very tightly pinned requir

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 04/12/2015 08:01 PM, James Polley wrote: > On Mon, Apr 13, 2015 at 9:12 AM, Monty Taylor wrote: > >> On 04/12/2015 06:43 PM, Robert Collins wrote: >>> Right now we do something that upstream pip considers wrong: we make >>> our requirements.txt be our install_requires. >>> >>> Upstream there a

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On Mon, Apr 13, 2015 at 9:12 AM, Monty Taylor wrote: > On 04/12/2015 06:43 PM, Robert Collins wrote: > > Right now we do something that upstream pip considers wrong: we make > > our requirements.txt be our install_requires. > > > > Upstream there are two separate concepts. > > > > install_require

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 04/12/2015 06:43 PM, Robert Collins wrote: > Right now we do something that upstream pip considers wrong: we make > our requirements.txt be our install_requires. > > Upstream there are two separate concepts. > > install_requirements, which are meant to document what *must* be > installed to im