Open Stack

Eoghan Glynn wrote:
>> In particular, where would that library code live ? In Nova tree ?
>> Or in a separate tree under nova's responsibility, like
>> python-novaclient ?
> 
> The former I think, if feasible, as the library would depend on a
> fair chunk of the nova innards, common utils, config options etc.
> so wouldn't be trivial to split off.
> [...]
> Now suppose the the *same* versioning was used as you suggest, would
> it still be possible to produce more than one artifact from the nova
> release process (e.g. multiple tarballs, binaries)?

It's not possible with the current CI setup we have, and I'd argue it's
not desirable. It's good that a given source tree results in a given
source code tarball...

Doug seems to have a slightly different vision for option 5, which
sounds much more doable to me (external library).

>> That option seems to be adding a new corner case
>> category of OpenStack project within the "library" project type,
>> with its own release model... 
> 
> Yes, agreed, it does feel like a new thing without a direct precedent.

I fear that when the ML thread favored option 5 it did not really take
into account the added complexity on the release side of things
(probably my fault for not diving into it earlier). All things
considered, it might not be the simplest route.

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack