Re: [openstack-dev] The end of OpenStack packages in Debian?

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Allison,

On Thu, 2017-02-23 at 19:07 -0500, Allison Randal wrote:
> > For the LIO-fb target in Debian, we've been depending on the rtslib-fb
> package,
> > which you've maintained so far. Should we pick it up under the pkg-linux-
> target
> > team ?
> 
> Hi Ritesh,
> 
> For the sake of consistency, it probably makes more sense to maintain
> rtslib-fb within the Debian Python Modules Team. If you'd like to chat
> in more detail about which Debian team is the best fit, we can narrow
> this thread down to just the PKG OpenStack mailing list.

rtslib-fb is a core component for the LIO(-fb) project. We already maintain
configshell-fb and targetcli-fb under pkg-linux-target group.

It is perfectly fine to have it under DPMT, as long as it is maintained. Only
if in case there are no takers, then we can consider taking this package.

Thanks,
Ritesh

- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAliwGCYACgkQpjpYo/Lh
dWlhBA//VQ0wNnq5izj6G3CztB1PotY7RyUJOU85Vw8FF/xsOI6I3PEkw0aJ1H9x
FhHAxzbWSMduOw2NV/m4m7bOsoqktXwqZ6MKH+vrFJ+7EIQdN0woUFISPKasXRpU
+0Qg1m0btEZQNT+hnMtR6Oq0NDELREteQp7uHGws/XgsDzXg64eu2q19Pa51uWvG
l+zg5KsmC5ZPYew50B8o2yblIMj8csdRZ8jTknCS9O7B5GobIJoAXK7/aMTk1q87
J6JobsbWPk3BfX7ei5Hc73+9fNf11iABwvZnwFKzXxx1dDA3K+DuH9N95EyFY75Q
PhIkMcx+9qRGWnt2FxTgn0RyGaFKc4L5e4loNCS8Pip4EWBGU9kQjT+LX1kZs4xQ
8ymAq7cSO9TiHWlNB5e2eGs3tliAsv6YMD6JibZ1JaLq7ZeonLpXf9VQ90QFlqpl
tRK8KA4WVrXVx5svrYAIcDaiCzyxujZ/tj9U8fRyaC/Y1gcsvSqpNZzGyzy4GyQJ
AcGJZToMCsxgc/dpF842otluiQAPc+CWfZ2HQVoH9p7DnHbSDAayV9pfrx/P5T+w
pfVKnCxlqz1ysfETybNyQerNexOrLZjWYWsfUSGsI7JJKQnWNufH5KO6AmGnnNXI
wHp/yU3K89+ZrCLCoBlXxYdWzPL9CPq/LW/S937jRXlnPI7jJCw=
=+0Pk
-END PGP SIGNATURE-


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Allison Randal]

On 02/21/2017 12:57 PM, Ritesh Raj Sarraf wrote:
> Hello Thomas,
> 
> Sad to see this. But with so much free loading trend, these are bound to 
> happen.
> 
> For the LIO-fb target in Debian, we've been depending on the rtslib-fb 
> package,
> which you've maintained so far. Should we pick it up under the 
> pkg-linux-target
> team ?

Hi Ritesh,

For the sake of consistency, it probably makes more sense to maintain
rtslib-fb within the Debian Python Modules Team. If you'd like to chat
in more detail about which Debian team is the best fit, we can narrow
this thread down to just the PKG OpenStack mailing list.

Thanks,
Allison



signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Thomas Goirand]

On 02/21/2017 12:19 PM, Clint Byrum wrote:
> We may have to agree to disagree on that. The libraries and clients
> should be an order of magnitude simpler than the services to maintain.

The problem isn't simplicity, but the amount of work. Once you've done
all the libraries, there's not much added work to be done to get all the
services uploaded, especially if the package only needs update.
Typically, I was needing 2 to 3 weeks (on each beta or RC) to get all
dependency into shape, and a few days for the services on top.

Cheers,

Thomas Goirand (zigo)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Ritesh Raj Sarraf]

Hello Thomas,

Sad to see this. But with so much free loading trend, these are bound to happen.

For the LIO-fb target in Debian, we've been depending on the rtslib-fb package,
which you've maintained so far. Should we pick it up under the pkg-linux-target
team ?

Ritesh

On Wed, 2017-02-15 at 13:42 +0100, Thomas Goirand wrote:
> Hi there,
> 
> It's been a while since I planed on writing this message. I couldn't
> write it because the situation makes me really sad. At this point, it
> starts to be urgent to post it.
> 
> As for many other folks, Mirantis decided to end its contract with me.
> This happened when I was the most successful doing the job, with all of
> the packaging CI moved to OpenStack infra at the end of the OpenStack
> Newton cycle, after we were able to release Newton this way. I was
> hoping to start packaging on every commit for Ocata. That's yet another
> reason for me to be very frustrated about all of this. Such is life...
> 
> Over the last few months, I hoped for having enough strengths to
> continue my packaging work anyway, and get Ocata packages done. But
> that's not what happened. The biggest reason for this is that I know
> that this needs to be a full time job. And at this point, I still don't
> know what my professional future will be. A company, in Barcelona, told
> me I'd get hired to continue my past work of packaging OpenStack in
> Debian, but so far, I'm still waiting for a definitive answer, so I'm
> looking into some other opportunities.
> 
> All this to say that, unless someone wants to hire me for it (which
> would be the best outcome, but I fear this wont happen), or if someone
> steps in (this seems unlikely at this point), both the packaging-deb and
> the faith of OpenStack packages in Debian are currently compromised.
> 
> I will continue to maintain OpenStack Newton during the lifetime of
> Debian Stretch though, but I don't plan on doing anything more. This
> means that maybe, Newton will be the last release of OpenStack in
> Debian. If things continue this way, I probably will ask for the removal
> of all OpenStack packages from Debian Sid after Stretch gets released
> (unless I know that someone will do the work).
> 
> As a consequence, the following projects wont get packages even in
> Ubuntu (as they were "community maintained", which means done by me and
> later sync into Ubuntu...):
> 
> - congress
> - gnocchi
> - magnum
> - mistral
> - murano
> - sahara
> - senlin
> - watcher
> - zaqar
> 
> Hopefully, Canonical will continue to maintain the other 15 (more
> core...) projects in UCA.
> 
> Thanks for the fish,
> 
> Thomas Goirand (zigo)
> 
> P,S: To the infra folks: please keep the packaging CI as it is, as it
> will be useful for the lifetime of Stretch.
> 
> 
-- 
Given the large number of mailing lists I follow, I request you to CC
me in replies for quicker response

signature.asc
Description: This is a digitally signed message part
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Clint Byrum]

Excerpts from Thomas Goirand's message of 2017-02-21 00:50:35 +0100:
> On 02/19/2017 08:43 PM, Clint Byrum wrote:
> > Excerpts from Thomas Goirand's message of 2017-02-19 00:58:01 +0100:
> >> On 02/18/2017 07:59 AM, Clint Byrum wrote:
> >>> Indeed, DPMT uses all the worst choices for maintaining most of the
> >>> python module packages in Debian. However, something will need to be
> >>> done to spread the load of maintaining the essential libraries, and the
> >>> usual answer to that for Python libraries is DPMT.
> >>
> >> I wish the Python team was more like the Perl one, who really is a well
> >> functioning with a strong team spirit and commitment, with a sense of
> >> collective responsibility. It's far from being the case in the DPMT.
> >>
> >> Moving packages to the DPMT will not magically get you new maintainers.
> >> Even within the team, there's unfortunately *a lot* of strong package
> >> ownership.
> >>
> > 
> > Whatever the issues are with that team, there's a _mountain_ of packages
> > to maintain, and only one team whose charter is to maintain python
> > modules. So we're going to have to deal with the shortcomings of that
> > relationship, or find more OpenStack specific maintainers.
> 
> I think there's a misunderstanding here. What I wrote is that the DPMT
> will *not* maintain packages just because they are pushed to the team,
> you will need to find maintainers for them. So that's the last option of
> your last sentence above that would work. The only issue is, nobody
> cared so far...
> 

I believe your experience is not typical, and the DPMT will in fact
assist with some of the more boring aspects of maintaining those
packages. Are they going to chase new upstream versions? No. But they'll
help with transitions, policy updates, RC bugs, etc.

> > It's also important that the generic libraries
> > we maintain, like stevedore, remain up to date in Debian so they don't
> > fall out of favor with users. Nothing kills a library like old versions
> > breaking apps.
> 
> Stevedore is a very good example. It build-depends on oslotest (to run
> unit tests), which itself needs os-client-config, oslo.config, which
> itself ... no need to continue, once you need oslo.config, you need
> everything else. So to continue to package something like Stevedore, we
> need nearly the full stack. That's equivalent to maintaining all of
> OpenStack (as I wrote: the cherry on top of the cake is the services,
> the bulk work is the Python modules).
> 

We may have to agree to disagree on that. The libraries and clients
should be an order of magnitude simpler than the services to maintain.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Doug Hellmann]

Excerpts from Thomas Goirand's message of 2017-02-21 00:50:35 +0100:
> On 02/19/2017 08:43 PM, Clint Byrum wrote:
> > Excerpts from Thomas Goirand's message of 2017-02-19 00:58:01 +0100:
> >> On 02/18/2017 07:59 AM, Clint Byrum wrote:
> >>> Indeed, DPMT uses all the worst choices for maintaining most of the
> >>> python module packages in Debian. However, something will need to be
> >>> done to spread the load of maintaining the essential libraries, and the
> >>> usual answer to that for Python libraries is DPMT.
> >>
> >> I wish the Python team was more like the Perl one, who really is a well
> >> functioning with a strong team spirit and commitment, with a sense of
> >> collective responsibility. It's far from being the case in the DPMT.
> >>
> >> Moving packages to the DPMT will not magically get you new maintainers.
> >> Even within the team, there's unfortunately *a lot* of strong package
> >> ownership.
> >>
> > 
> > Whatever the issues are with that team, there's a _mountain_ of packages
> > to maintain, and only one team whose charter is to maintain python
> > modules. So we're going to have to deal with the shortcomings of that
> > relationship, or find more OpenStack specific maintainers.
> 
> I think there's a misunderstanding here. What I wrote is that the DPMT
> will *not* maintain packages just because they are pushed to the team,
> you will need to find maintainers for them. So that's the last option of
> your last sentence above that would work. The only issue is, nobody
> cared so far...
> 
> > It's also important that the generic libraries
> > we maintain, like stevedore, remain up to date in Debian so they don't
> > fall out of favor with users. Nothing kills a library like old versions
> > breaking apps.
> 
> Stevedore is a very good example. It build-depends on oslotest (to run
> unit tests), which itself needs os-client-config, oslo.config, which
> itself ... no need to continue, once you need oslo.config, you need

It sounds like we've broken our dependency cycle rule for some of
the libraries. I'll take a look at what can be done about that over
Pike.

Doug

> everything else. So to continue to package something like Stevedore, we
> need nearly the full stack. That's equivalent to maintaining all of
> OpenStack (as I wrote: the cherry on top of the cake is the services,
> the bulk work is the Python modules).
> 
> Cheers,
> 
> Thomas Goirand (zigo)
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Thomas Goirand]

On 02/19/2017 08:43 PM, Clint Byrum wrote:
> Excerpts from Thomas Goirand's message of 2017-02-19 00:58:01 +0100:
>> On 02/18/2017 07:59 AM, Clint Byrum wrote:
>>> Indeed, DPMT uses all the worst choices for maintaining most of the
>>> python module packages in Debian. However, something will need to be
>>> done to spread the load of maintaining the essential libraries, and the
>>> usual answer to that for Python libraries is DPMT.
>>
>> I wish the Python team was more like the Perl one, who really is a well
>> functioning with a strong team spirit and commitment, with a sense of
>> collective responsibility. It's far from being the case in the DPMT.
>>
>> Moving packages to the DPMT will not magically get you new maintainers.
>> Even within the team, there's unfortunately *a lot* of strong package
>> ownership.
>>
> 
> Whatever the issues are with that team, there's a _mountain_ of packages
> to maintain, and only one team whose charter is to maintain python
> modules. So we're going to have to deal with the shortcomings of that
> relationship, or find more OpenStack specific maintainers.

I think there's a misunderstanding here. What I wrote is that the DPMT
will *not* maintain packages just because they are pushed to the team,
you will need to find maintainers for them. So that's the last option of
your last sentence above that would work. The only issue is, nobody
cared so far...

> It's also important that the generic libraries
> we maintain, like stevedore, remain up to date in Debian so they don't
> fall out of favor with users. Nothing kills a library like old versions
> breaking apps.

Stevedore is a very good example. It build-depends on oslotest (to run
unit tests), which itself needs os-client-config, oslo.config, which
itself ... no need to continue, once you need oslo.config, you need
everything else. So to continue to package something like Stevedore, we
need nearly the full stack. That's equivalent to maintaining all of
OpenStack (as I wrote: the cherry on top of the cake is the services,
the bulk work is the Python modules).

Cheers,

Thomas Goirand (zigo)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Clint Byrum]

Excerpts from Thomas Goirand's message of 2017-02-19 00:58:01 +0100:
> On 02/18/2017 07:59 AM, Clint Byrum wrote:
> > Indeed, DPMT uses all the worst choices for maintaining most of the
> > python module packages in Debian. However, something will need to be
> > done to spread the load of maintaining the essential libraries, and the
> > usual answer to that for Python libraries is DPMT.
> 
> I wish the Python team was more like the Perl one, who really is a well
> functioning with a strong team spirit and commitment, with a sense of
> collective responsibility. It's far from being the case in the DPMT.
> 
> Moving packages to the DPMT will not magically get you new maintainers.
> Even within the team, there's unfortunately *a lot* of strong package
> ownership.
> 

Whatever the issues are with that team, there's a _mountain_ of packages
to maintain, and only one team whose charter is to maintain python
modules. So we're going to have to deal with the shortcomings of that
relationship, or find more OpenStack specific maintainers.

My main concern is making sure Debian users can interact with OpenStack.
It's truly unfortunate that we may not have OpenStack's core kept well
maintained in Debian (though I can't see any reason Ubuntu's developers
wouldn't help with that -- feel free to chime in Ubuntu folks). But it's
vital to OpenStack and Debian's interests that Debian users be able
to grab the pieces of the OpenStack SDK that they need to communicate
with OpenStack clouds. It's also important that the generic libraries
we maintain, like stevedore, remain up to date in Debian so they don't
fall out of favor with users. Nothing kills a library like old versions
breaking apps.

I'm not going to rush off and do anything now. I don't have time. But
it's now on my radar, and when I find a window for it to fall into, I'll
start looking at how best to transition these. In the mean time I'll
hold out hope that we'll have good news and you can continue your work.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Thomas Goirand]

On 02/18/2017 05:14 PM, Andrew Bogott wrote:
> Does this
> announcement mean that the Mirantis apt servers (e.g.
> mitaka-jessie.pkgs.mirantis.com) will also be discontinued

Correct, I've been told the server would be decommitionned. In fact, I'm
surprised it is still up-and-running. I've explained that some people
could well still be using it, but it didn't seem someone cared.

FYI, I made a backup on my own laptop, but I don't plan on investing a
dime on setting-up an online service myself.

> Relatedly... is Mirantis likely to make some sort of announcement or
> commitment about the lifespan of that service?  Or is it just there
> until it's not?

Since the end of 2016, I'm not a Mirantis employee, so I can't talk for
them. I can only guess that it is very unlikely any announcement would
be made. I'd very much welcome someone external from the company to
express discontent to the Mirantis marketing team about discontinuation
of this service. So be my guest...

Cheers,

Thomas Goirand (zigo)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Thomas Goirand]

On 02/18/2017 07:59 AM, Clint Byrum wrote:
> Indeed, DPMT uses all the worst choices for maintaining most of the
> python module packages in Debian. However, something will need to be
> done to spread the load of maintaining the essential libraries, and the
> usual answer to that for Python libraries is DPMT.

I wish the Python team was more like the Perl one, who really is a well
functioning with a strong team spirit and commitment, with a sense of
collective responsibility. It's far from being the case in the DPMT.

Moving packages to the DPMT will not magically get you new maintainers.
Even within the team, there's unfortunately *a lot* of strong package
ownership.

Cheers,

Thomas Goirand (zigo)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Andrew Bogott]

On 2/15/17 8:22 PM, gustavo panizzo wrote:

On Wed, Feb 15, 2017 at 01:42:51PM +0100, Thomas Goirand wrote:

Hi there,


Its really sad news, for both You and OpenStack & Debian.


Thank you for your work, Thomas -- I hope you are able to continue it.

I'm slow on the uptake here, for which I apologize.  Does this 
announcement mean that the Mirantis apt servers (e.g. 
mitaka-jessie.pkgs.mirantis.com) will also be discontinued, or are we 
only talking about package contributions to the official Debian distros?


Relatedly... is Mirantis likely to make some sort of announcement or 
commitment about the lifespan of that service?  Or is it just there 
until it's not?


-Andrew

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Clint Byrum]

Excerpts from Thomas Goirand's message of 2017-02-17 01:54:55 +0100:
> On 02/16/2017 05:55 PM, Clint Byrum wrote:
> > Excerpts from Thomas Goirand's message of 2017-02-15 13:43:46 +0100:
> >> All this to say that, unless someone wants to hire me for it (which
> >> would be the best outcome, but I fear this wont happen), or if someone
> >> steps in (this seems unlikely at this point), both the packaging-deb and
> >> the faith of OpenStack packages in Debian are currently compromised.
> >>
> >> I will continue to maintain OpenStack Newton during the lifetime of
> >> Debian Stretch though, but I don't plan on doing anything more. This
> >> means that maybe, Newton will be the last release of OpenStack in
> >> Debian. If things continue this way, I probably will ask for the removal
> >> of all OpenStack packages from Debian Sid after Stretch gets released
> >> (unless I know that someone will do the work).
> >>
> > 
> > Thomas, thanks for all your hard work. I hope you can return to it soon
> > and that this serves as a notice that we need more investment to keep
> > OpenStack viable in Debian and Ubuntu.
> 
> Yeah, thanks!
> 
> > 
> > Can I propose that we start to move some of the libraries and things
> > like OpenStack Client into DPMT/DPAT?  They don't require constant
> > attention, and it will be helpful to have a larger team assisting in
> > the packaging where it doesn't require anything OpenStack specific to
> > keep moving forward.
> 
> 3rd party libs, maybe. Things like OpenStack client and such may not be
> good candidates, as they interact too much with oslo stuff. Also,
> pushing these packages to a different team wont give you more
> contributors. Last, DPMT/DPAT insist in using git-dpm which is horrible,
> while I've successfully pushed all of the packaging into the OpenStack
> CI, which checks the build on every commit. I consider it a way safer
> and nicer than just the "stupid" Git on Alioth. If you want packages to
> go back to Alioth, at least someone has to setup a Jenkins the way I
> used to do, so that packages are build on git push. I don't have such an
> infrastructure anymore at my disposal, Mirantis even is destroying the
> server I used to work on (at this point in time, the FTP data may even
> already be lost for the older releases...).
> 

Indeed, DPMT uses all the worst choices for maintaining most of the
python module packages in Debian. However, something will need to be
done to spread the load of maintaining the essential libraries, and the
usual answer to that for Python libraries is DPMT.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Thomas Goirand]

On 02/16/2017 05:55 PM, Clint Byrum wrote:
> Excerpts from Thomas Goirand's message of 2017-02-15 13:43:46 +0100:
>> All this to say that, unless someone wants to hire me for it (which
>> would be the best outcome, but I fear this wont happen), or if someone
>> steps in (this seems unlikely at this point), both the packaging-deb and
>> the faith of OpenStack packages in Debian are currently compromised.
>>
>> I will continue to maintain OpenStack Newton during the lifetime of
>> Debian Stretch though, but I don't plan on doing anything more. This
>> means that maybe, Newton will be the last release of OpenStack in
>> Debian. If things continue this way, I probably will ask for the removal
>> of all OpenStack packages from Debian Sid after Stretch gets released
>> (unless I know that someone will do the work).
>>
> 
> Thomas, thanks for all your hard work. I hope you can return to it soon
> and that this serves as a notice that we need more investment to keep
> OpenStack viable in Debian and Ubuntu.

Yeah, thanks!

> 
> Can I propose that we start to move some of the libraries and things
> like OpenStack Client into DPMT/DPAT?  They don't require constant
> attention, and it will be helpful to have a larger team assisting in
> the packaging where it doesn't require anything OpenStack specific to
> keep moving forward.

3rd party libs, maybe. Things like OpenStack client and such may not be
good candidates, as they interact too much with oslo stuff. Also,
pushing these packages to a different team wont give you more
contributors. Last, DPMT/DPAT insist in using git-dpm which is horrible,
while I've successfully pushed all of the packaging into the OpenStack
CI, which checks the build on every commit. I consider it a way safer
and nicer than just the "stupid" Git on Alioth. If you want packages to
go back to Alioth, at least someone has to setup a Jenkins the way I
used to do, so that packages are build on git push. I don't have such an
infrastructure anymore at my disposal, Mirantis even is destroying the
server I used to work on (at this point in time, the FTP data may even
already be lost for the older releases...).

Cheers,

Thomas Goirand (zigo)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Dan Prince]

Nice work on the packages Thomas. I've always admired that you got the
Debian packages upstream first :).

Best wishes.

Dan


On Wed, 2017-02-15 at 13:42 +0100, Thomas Goirand wrote:
> Hi there,
> 
> It's been a while since I planed on writing this message. I couldn't
> write it because the situation makes me really sad. At this point, it
> starts to be urgent to post it.
> 
> As for many other folks, Mirantis decided to end its contract with
> me.
> This happened when I was the most successful doing the job, with all
> of
> the packaging CI moved to OpenStack infra at the end of the OpenStack
> Newton cycle, after we were able to release Newton this way. I was
> hoping to start packaging on every commit for Ocata. That's yet
> another
> reason for me to be very frustrated about all of this. Such is
> life...
> 
> Over the last few months, I hoped for having enough strengths to
> continue my packaging work anyway, and get Ocata packages done. But
> that's not what happened. The biggest reason for this is that I know
> that this needs to be a full time job. And at this point, I still
> don't
> know what my professional future will be. A company, in Barcelona,
> told
> me I'd get hired to continue my past work of packaging OpenStack in
> Debian, but so far, I'm still waiting for a definitive answer, so I'm
> looking into some other opportunities.
> 
> All this to say that, unless someone wants to hire me for it (which
> would be the best outcome, but I fear this wont happen), or if
> someone
> steps in (this seems unlikely at this point), both the packaging-deb
> and
> the faith of OpenStack packages in Debian are currently compromised.
> 
> I will continue to maintain OpenStack Newton during the lifetime of
> Debian Stretch though, but I don't plan on doing anything more. This
> means that maybe, Newton will be the last release of OpenStack in
> Debian. If things continue this way, I probably will ask for the
> removal
> of all OpenStack packages from Debian Sid after Stretch gets released
> (unless I know that someone will do the work).
> 
> As a consequence, the following projects wont get packages even in
> Ubuntu (as they were "community maintained", which means done by me
> and
> later sync into Ubuntu...):
> 
> - congress
> - gnocchi
> - magnum
> - mistral
> - murano
> - sahara
> - senlin
> - watcher
> - zaqar
> 
> Hopefully, Canonical will continue to maintain the other 15 (more
> core...) projects in UCA.
> 
> Thanks for the fish,
> 
> Thomas Goirand (zigo)
> 
> P,S: To the infra folks: please keep the packaging CI as it is, as it
> will be useful for the lifetime of Stretch.
> 
> _
> _
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
> cribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Clint Byrum]

Excerpts from Thomas Goirand's message of 2017-02-15 13:43:46 +0100:
> All this to say that, unless someone wants to hire me for it (which
> would be the best outcome, but I fear this wont happen), or if someone
> steps in (this seems unlikely at this point), both the packaging-deb and
> the faith of OpenStack packages in Debian are currently compromised.
> 
> I will continue to maintain OpenStack Newton during the lifetime of
> Debian Stretch though, but I don't plan on doing anything more. This
> means that maybe, Newton will be the last release of OpenStack in
> Debian. If things continue this way, I probably will ask for the removal
> of all OpenStack packages from Debian Sid after Stretch gets released
> (unless I know that someone will do the work).
> 

Thomas, thanks for all your hard work. I hope you can return to it soon
and that this serves as a notice that we need more investment to keep
OpenStack viable in Debian and Ubuntu.

Can I propose that we start to move some of the libraries and things
like OpenStack Client into DPMT/DPAT?  They don't require constant
attention, and it will be helpful to have a larger team assisting in
the packaging where it doesn't require anything OpenStack specific to
keep moving forward.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Renat Akhmerov]

Very sad to hear all that.. Hopefully it’ll be sorted out one way or another.

Thanks Thomas!

Renat Akhmerov
@Nokia

> On 15 Feb 2017, at 23:42, Doug Hellmann  wrote:
> 
> Excerpts from Paul Belanger's message of 2017-02-15 09:51:22 -0500:
>> On Wed, Feb 15, 2017 at 01:43:46PM +0100, Thomas Goirand wrote:
>>> Hi there,
>>> 
>>> It's been a while since I planed on writing this message. I couldn't
>>> write it because the situation makes me really sad. At this point, it
>>> starts to be urgent to post it.
>>> 
>>> As for many other folks, Mirantis decided to end its contract with me.
>>> This happened when I was the most successful doing the job, with all of
>>> the packaging CI moved to OpenStack infra at the end of the OpenStack
>>> Newton cycle, after we were able to release Newton this way. I was
>>> hoping to start packaging on every commit for Ocata. That's yet another
>>> reason for me to be very frustrated about all of this. Such is life...
>>> 
>>> Over the last few months, I hoped for having enough strengths to
>>> continue my packaging work anyway, and get Ocata packages done. But
>>> that's not what happened. The biggest reason for this is that I know
>>> that this needs to be a full time job. And at this point, I still don't
>>> know what my professional future will be. A company, in Barcelona, told
>>> me I'd get hired to continue my past work of packaging OpenStack in
>>> Debian, but so far, I'm still waiting for a definitive answer, so I'm
>>> looking into some other opportunities.
>>> 
>>> All this to say that, unless someone wants to hire me for it (which
>>> would be the best outcome, but I fear this wont happen), or if someone
>>> steps in (this seems unlikely at this point), both the packaging-deb and
>>> the faith of OpenStack packages in Debian are currently compromised.
>>> 
>>> I will continue to maintain OpenStack Newton during the lifetime of
>>> Debian Stretch though, but I don't plan on doing anything more. This
>>> means that maybe, Newton will be the last release of OpenStack in
>>> Debian. If things continue this way, I probably will ask for the removal
>>> of all OpenStack packages from Debian Sid after Stretch gets released
>>> (unless I know that someone will do the work).
>>> 
>>> As a consequence, the following projects wont get packages even in
>>> Ubuntu (as they were "community maintained", which means done by me and
>>> later sync into Ubuntu...):
>>> 
>>> - congress
>>> - gnocchi
>>> - magnum
>>> - mistral
>>> - murano
>>> - sahara
>>> - senlin
>>> - watcher
>>> - zaqar
>>> 
>>> Hopefully, Canonical will continue to maintain the other 15 (more
>>> core...) projects in UCA.
>>> 
>>> Thanks for the fish,
>>> 
>>> Thomas Goirand (zigo)
>>> 
>>> P,S: To the infra folks: please keep the packaging CI as it is, as it
>>> will be useful for the lifetime of Stretch.
>>> 
>> Thanks for all your work. I'm glad we eventually stood up all the packaging
>> infrastructure.
>> 
>> Good luck on your future endeavors.
>> 
> 
> Yes, thank you for everything you've done, Thomas. You have done
> an immense amount of work to ensure that good quality OpenStack
> packages are available to a wide user base.
> 
> Doug
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org 
> ?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> 
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[gustavo panizzo]

On Wed, Feb 15, 2017 at 01:42:51PM +0100, Thomas Goirand wrote:
> Hi there,
> 

Its really sad news, for both You and OpenStack & Debian.

I wish you get a contract soon

On the OpenStack side, I wonder if as a community we could (and if it
make sense to do so)  maintain only a few projects, keystone, nova, 
cinder (lvm), neutron (lb + ovs), glance, horizon. 

thanks for your work. it is really appreciated.

> It's been a while since I planed on writing this message. I couldn't
> write it because the situation makes me really sad. At this point, it
> starts to be urgent to post it.
> 
> As for many other folks, Mirantis decided to end its contract with me.
> This happened when I was the most successful doing the job, with all of
> the packaging CI moved to OpenStack infra at the end of the OpenStack
> Newton cycle, after we were able to release Newton this way. I was
> hoping to start packaging on every commit for Ocata. That's yet another
> reason for me to be very frustrated about all of this. Such is life...
> 
> Over the last few months, I hoped for having enough strengths to
> continue my packaging work anyway, and get Ocata packages done. But
> that's not what happened. The biggest reason for this is that I know
> that this needs to be a full time job. And at this point, I still don't
> know what my professional future will be. A company, in Barcelona, told
> me I'd get hired to continue my past work of packaging OpenStack in
> Debian, but so far, I'm still waiting for a definitive answer, so I'm
> looking into some other opportunities.
> 
> All this to say that, unless someone wants to hire me for it (which
> would be the best outcome, but I fear this wont happen), or if someone
> steps in (this seems unlikely at this point), both the packaging-deb and
> the faith of OpenStack packages in Debian are currently compromised.
> 
> I will continue to maintain OpenStack Newton during the lifetime of
> Debian Stretch though, but I don't plan on doing anything more. This
> means that maybe, Newton will be the last release of OpenStack in
> Debian. If things continue this way, I probably will ask for the removal
> of all OpenStack packages from Debian Sid after Stretch gets released
> (unless I know that someone will do the work).

> 
> As a consequence, the following projects wont get packages even in
> Ubuntu (as they were "community maintained", which means done by me and
> later sync into Ubuntu...):
> 
> - congress
> - gnocchi
> - magnum
> - mistral
> - murano
> - sahara
> - senlin
> - watcher
> - zaqar
> 
> Hopefully, Canonical will continue to maintain the other 15 (more
> core...) projects in UCA.
> 
> Thanks for the fish,
> 
> Thomas Goirand (zigo)
> 
> P,S: To the infra folks: please keep the packaging CI as it is, as it
> will be useful for the lifetime of Stretch.
> 

-- 
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333

keybase: https://keybase.io/gfa

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Thomas Goirand]

On 02/15/2017 07:11 PM, Ondrej Novy wrote:
> Hi,
> 
> 2017-02-15 13:42 GMT+01:00 Thomas Goirand  >:
> 
> Over the last few months, I hoped for having enough strengths to
> continue my packaging work anyway, and get Ocata packages done. But
> that's not what happened. The biggest reason for this is that I know
> that this needs to be a full time job. 
> 
> 
> as second most active openstack-pkg team contributor
> (http://blends.debian.net/liststats/uploaders_pkg-openstack.png) I think
> this not needs to be full time job, but we need more maintainers.

Definitively, we need more maintainers, but it's not happening.

> If things continue this way, I probably will ask for the removal
> of all OpenStack packages from Debian Sid after Stretch gets released
> (unless I know that someone will do the work).
> 
> 
> please don't ask anyone to remove __team maintained__ packages.

If the team stays inactive, for sure, I will ask for removal.

> As a consequence, the following projects wont get packages even in
> Ubuntu (as they were "community maintained", which means done by me and
> later sync into Ubuntu...):
> 
> done by team, not (only) you.
> 
> I know you done most of packaging work, but please don't say: I'm only
> one who did OS packaging. That's not fair to other contributors.

Yes, you've done some work, and many thanks for it, it has been very
useful. However the reality is: since I stopped after the Newton
release, absolutely no work has been done to package Ocata in Debian. At
this point in the OpenStack dev cycle, normally it should have been
fully uploaded *AND* tested against tempest.

Cheers,

Thomas Goirand (zigo)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Ben Finney]

Thomas Goirand  writes:

> All this to say that, unless someone wants to hire me for it (which
> would be the best outcome, but I fear this wont happen), or if someone
> steps in (this seems unlikely at this point), both the packaging-deb
> and the faith of OpenStack packages in Debian are currently
> compromised.

Thanks for your work, Thomas, and yes I hope someone hires you and other
skilled maintainers to continue OpenStack in Debian.

Nadia Eghbal's work documenting the state of critical infrastructure

has led her to create a guide for seeking funding for crucial
free-software infrastructure
.


For those parties who are profiting from OpenStack, or any other
free-software project, you need to read “Roads and Bridges”

and *fund* the maintenance of this infrastructure.

Stories like Thomas's should gavlanise you to put sustained funding in
for the projects that provide your own lifeblood. Step up, join with
others, and make this right.

-- 
 \   “Pray, v. To ask that the laws of the universe be annulled in |
  `\ behalf of a single petitioner confessedly unworthy.” —Ambrose |
_o__)   Bierce, _The Devil's Dictionary_, 1906 |
Ben Finney


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Corey Bryant]

On Wed, Feb 15, 2017 at 7:42 AM, Thomas Goirand  wrote:

> Hi there,
>
> It's been a while since I planed on writing this message. I couldn't
> write it because the situation makes me really sad. At this point, it
> starts to be urgent to post it.
>
> As for many other folks, Mirantis decided to end its contract with me.
> This happened when I was the most successful doing the job, with all of
> the packaging CI moved to OpenStack infra at the end of the OpenStack
> Newton cycle, after we were able to release Newton this way. I was
> hoping to start packaging on every commit for Ocata. That's yet another
> reason for me to be very frustrated about all of this. Such is life...
>
> Over the last few months, I hoped for having enough strengths to
> continue my packaging work anyway, and get Ocata packages done. But
> that's not what happened. The biggest reason for this is that I know
> that this needs to be a full time job. And at this point, I still don't
> know what my professional future will be. A company, in Barcelona, told
> me I'd get hired to continue my past work of packaging OpenStack in
> Debian, but so far, I'm still waiting for a definitive answer, so I'm
> looking into some other opportunities.
>
> All this to say that, unless someone wants to hire me for it (which
> would be the best outcome, but I fear this wont happen), or if someone
> steps in (this seems unlikely at this point), both the packaging-deb and
> the faith of OpenStack packages in Debian are currently compromised.
>
> I will continue to maintain OpenStack Newton during the lifetime of
> Debian Stretch though, but I don't plan on doing anything more. This
> means that maybe, Newton will be the last release of OpenStack in
> Debian. If things continue this way, I probably will ask for the removal
> of all OpenStack packages from Debian Sid after Stretch gets released
> (unless I know that someone will do the work).
>
> As a consequence, the following projects wont get packages even in
> Ubuntu (as they were "community maintained", which means done by me and
> later sync into Ubuntu...):
>
> - congress
> - gnocchi
> - magnum
> - mistral
> - murano
> - sahara
> - senlin
> - watcher
> - zaqar
>
>
Thanks for all of your work, Thomas.  Wishing you the best.

For others following along, we do have up-to-date versions of these
packages in Ocata for Ubuntu.  For a full reports of packages please see:
http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-archive/ocata_versions.html


> Hopefully, Canonical will continue to maintain the other 15 (more
> core...) projects in UCA.


> Thanks for the fish,
>
> Thomas Goirand (zigo)
>
> P,S: To the infra folks: please keep the packaging CI as it is, as it
> will be useful for the lifetime of Stretch.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Regards,
Corey
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Allison Randal]

On 02/15/2017 07:42 AM, Thomas Goirand wrote:
> I will continue to maintain OpenStack Newton during the lifetime of
> Debian Stretch though, but I don't plan on doing anything more. This
> means that maybe, Newton will be the last release of OpenStack in
> Debian. If things continue this way, I probably will ask for the removal
> of all OpenStack packages from Debian Sid after Stretch gets released
> (unless I know that someone will do the work).

I'm happy to volunteer for this. TBH, my goal would be to minimize the
delta on these packages to Ubuntu's versions of the packages, so we can
maintain them collaboratively. But, there's certainly no need to drop
the packages from Debian.

> As a consequence, the following projects wont get packages even in
> Ubuntu (as they were "community maintained", which means done by me and
> later sync into Ubuntu...):
> 
> - congress
> - gnocchi
> - magnum
> - mistral
> - murano
> - sahara
> - senlin
> - watcher
> - zaqar

These are more "nice to have" packages, not really critical. We can ask
around to see if anyone is using the packaged versions, but if not we
should just drop them from Debian.

> Hopefully, Canonical will continue to maintain the other 15 (more
> core...) projects in UCA.

Canonical doesn't have a large team for this work, but I imagine we can
handle it just fine between their team and a few volunteers.

Allison

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Doug Hellmann]

Excerpts from Paul Belanger's message of 2017-02-15 09:51:22 -0500:
> On Wed, Feb 15, 2017 at 01:43:46PM +0100, Thomas Goirand wrote:
> > Hi there,
> > 
> > It's been a while since I planed on writing this message. I couldn't
> > write it because the situation makes me really sad. At this point, it
> > starts to be urgent to post it.
> > 
> > As for many other folks, Mirantis decided to end its contract with me.
> > This happened when I was the most successful doing the job, with all of
> > the packaging CI moved to OpenStack infra at the end of the OpenStack
> > Newton cycle, after we were able to release Newton this way. I was
> > hoping to start packaging on every commit for Ocata. That's yet another
> > reason for me to be very frustrated about all of this. Such is life...
> > 
> > Over the last few months, I hoped for having enough strengths to
> > continue my packaging work anyway, and get Ocata packages done. But
> > that's not what happened. The biggest reason for this is that I know
> > that this needs to be a full time job. And at this point, I still don't
> > know what my professional future will be. A company, in Barcelona, told
> > me I'd get hired to continue my past work of packaging OpenStack in
> > Debian, but so far, I'm still waiting for a definitive answer, so I'm
> > looking into some other opportunities.
> > 
> > All this to say that, unless someone wants to hire me for it (which
> > would be the best outcome, but I fear this wont happen), or if someone
> > steps in (this seems unlikely at this point), both the packaging-deb and
> > the faith of OpenStack packages in Debian are currently compromised.
> > 
> > I will continue to maintain OpenStack Newton during the lifetime of
> > Debian Stretch though, but I don't plan on doing anything more. This
> > means that maybe, Newton will be the last release of OpenStack in
> > Debian. If things continue this way, I probably will ask for the removal
> > of all OpenStack packages from Debian Sid after Stretch gets released
> > (unless I know that someone will do the work).
> > 
> > As a consequence, the following projects wont get packages even in
> > Ubuntu (as they were "community maintained", which means done by me and
> > later sync into Ubuntu...):
> > 
> > - congress
> > - gnocchi
> > - magnum
> > - mistral
> > - murano
> > - sahara
> > - senlin
> > - watcher
> > - zaqar
> > 
> > Hopefully, Canonical will continue to maintain the other 15 (more
> > core...) projects in UCA.
> > 
> > Thanks for the fish,
> > 
> > Thomas Goirand (zigo)
> > 
> > P,S: To the infra folks: please keep the packaging CI as it is, as it
> > will be useful for the lifetime of Stretch.
> > 
> Thanks for all your work. I'm glad we eventually stood up all the packaging
> infrastructure.
> 
> Good luck on your future endeavors.
> 

Yes, thank you for everything you've done, Thomas. You have done
an immense amount of work to ensure that good quality OpenStack
packages are available to a wide user base.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Davanum Srinivas]

On Wed, Feb 15, 2017 at 10:41 AM, Tobias Urdin
 wrote:
> On 02/15/2017 01:46 PM, Thomas Goirand wrote:
>> Hi there,
>>
>> It's been a while since I planed on writing this message. I couldn't
>> write it because the situation makes me really sad. At this point, it
>> starts to be urgent to post it.
>>
>> As for many other folks, Mirantis decided to end its contract with me.
>> This happened when I was the most successful doing the job, with all of
>> the packaging CI moved to OpenStack infra at the end of the OpenStack
>> Newton cycle, after we were able to release Newton this way. I was
>> hoping to start packaging on every commit for Ocata. That's yet another
>> reason for me to be very frustrated about all of this. Such is life...
>>
>> Over the last few months, I hoped for having enough strengths to
>> continue my packaging work anyway, and get Ocata packages done. But
>> that's not what happened. The biggest reason for this is that I know
>> that this needs to be a full time job. And at this point, I still don't
>> know what my professional future will be. A company, in Barcelona, told
>> me I'd get hired to continue my past work of packaging OpenStack in
>> Debian, but so far, I'm still waiting for a definitive answer, so I'm
>> looking into some other opportunities.
>>
>> All this to say that, unless someone wants to hire me for it (which
>> would be the best outcome, but I fear this wont happen), or if someone
>> steps in (this seems unlikely at this point), both the packaging-deb and
>> the faith of OpenStack packages in Debian are currently compromised.
>>
>> I will continue to maintain OpenStack Newton during the lifetime of
>> Debian Stretch though, but I don't plan on doing anything more. This
>> means that maybe, Newton will be the last release of OpenStack in
>> Debian. If things continue this way, I probably will ask for the removal
>> of all OpenStack packages from Debian Sid after Stretch gets released
>> (unless I know that someone will do the work).
>>
>> As a consequence, the following projects wont get packages even in
>> Ubuntu (as they were "community maintained", which means done by me and
>> later sync into Ubuntu...):
>>
>> - congress
>> - gnocchi
>> - magnum
>> - mistral
>> - murano
>> - sahara
>> - senlin
>> - watcher
>> - zaqar
>>
>> Hopefully, Canonical will continue to maintain the other 15 (more
>> core...) projects in UCA.
>>
>> Thanks for the fish,
>>
>> Thomas Goirand (zigo)
>>
>> P,S: To the infra folks: please keep the packaging CI as it is, as it
>> will be useful for the lifetime of Stretch.
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> Somebody please hire Thomas, he's amazing!

Heartily seconded!!

Thanks,
Dims

> Thank you for everything!
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Davanum Srinivas :: https://twitter.com/dims

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Amy Marrich]

+2

On Wed, Feb 15, 2017 at 9:41 AM, Tobias Urdin 
wrote:

> On 02/15/2017 01:46 PM, Thomas Goirand wrote:
> > Hi there,
> >
> > It's been a while since I planed on writing this message. I couldn't
> > write it because the situation makes me really sad. At this point, it
> > starts to be urgent to post it.
> >
> > As for many other folks, Mirantis decided to end its contract with me.
> > This happened when I was the most successful doing the job, with all of
> > the packaging CI moved to OpenStack infra at the end of the OpenStack
> > Newton cycle, after we were able to release Newton this way. I was
> > hoping to start packaging on every commit for Ocata. That's yet another
> > reason for me to be very frustrated about all of this. Such is life...
> >
> > Over the last few months, I hoped for having enough strengths to
> > continue my packaging work anyway, and get Ocata packages done. But
> > that's not what happened. The biggest reason for this is that I know
> > that this needs to be a full time job. And at this point, I still don't
> > know what my professional future will be. A company, in Barcelona, told
> > me I'd get hired to continue my past work of packaging OpenStack in
> > Debian, but so far, I'm still waiting for a definitive answer, so I'm
> > looking into some other opportunities.
> >
> > All this to say that, unless someone wants to hire me for it (which
> > would be the best outcome, but I fear this wont happen), or if someone
> > steps in (this seems unlikely at this point), both the packaging-deb and
> > the faith of OpenStack packages in Debian are currently compromised.
> >
> > I will continue to maintain OpenStack Newton during the lifetime of
> > Debian Stretch though, but I don't plan on doing anything more. This
> > means that maybe, Newton will be the last release of OpenStack in
> > Debian. If things continue this way, I probably will ask for the removal
> > of all OpenStack packages from Debian Sid after Stretch gets released
> > (unless I know that someone will do the work).
> >
> > As a consequence, the following projects wont get packages even in
> > Ubuntu (as they were "community maintained", which means done by me and
> > later sync into Ubuntu...):
> >
> > - congress
> > - gnocchi
> > - magnum
> > - mistral
> > - murano
> > - sahara
> > - senlin
> > - watcher
> > - zaqar
> >
> > Hopefully, Canonical will continue to maintain the other 15 (more
> > core...) projects in UCA.
> >
> > Thanks for the fish,
> >
> > Thomas Goirand (zigo)
> >
> > P,S: To the infra folks: please keep the packaging CI as it is, as it
> > will be useful for the lifetime of Stretch.
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> Somebody please hire Thomas, he's amazing!
>
> Thank you for everything!
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Haïkel]

2017-02-15 13:42 GMT+01:00 Thomas Goirand :
> Hi there,
>
> It's been a while since I planed on writing this message. I couldn't
> write it because the situation makes me really sad. At this point, it
> starts to be urgent to post it.
>
> As for many other folks, Mirantis decided to end its contract with me.
> This happened when I was the most successful doing the job, with all of
> the packaging CI moved to OpenStack infra at the end of the OpenStack
> Newton cycle, after we were able to release Newton this way. I was
> hoping to start packaging on every commit for Ocata. That's yet another
> reason for me to be very frustrated about all of this. Such is life...
>
> Over the last few months, I hoped for having enough strengths to
> continue my packaging work anyway, and get Ocata packages done. But
> that's not what happened. The biggest reason for this is that I know
> that this needs to be a full time job. And at this point, I still don't
> know what my professional future will be. A company, in Barcelona, told
> me I'd get hired to continue my past work of packaging OpenStack in
> Debian, but so far, I'm still waiting for a definitive answer, so I'm
> looking into some other opportunities.
>
> All this to say that, unless someone wants to hire me for it (which
> would be the best outcome, but I fear this wont happen), or if someone
> steps in (this seems unlikely at this point), both the packaging-deb and
> the faith of OpenStack packages in Debian are currently compromised.
>
> I will continue to maintain OpenStack Newton during the lifetime of
> Debian Stretch though, but I don't plan on doing anything more. This
> means that maybe, Newton will be the last release of OpenStack in
> Debian. If things continue this way, I probably will ask for the removal
> of all OpenStack packages from Debian Sid after Stretch gets released
> (unless I know that someone will do the work).
>
> As a consequence, the following projects wont get packages even in
> Ubuntu (as they were "community maintained", which means done by me and
> later sync into Ubuntu...):
>
> - congress
> - gnocchi
> - magnum
> - mistral
> - murano
> - sahara
> - senlin
> - watcher
> - zaqar
>
> Hopefully, Canonical will continue to maintain the other 15 (more
> core...) projects in UCA.
>
> Thanks for the fish,
>
> Thomas Goirand (zigo)
>
> P,S: To the infra folks: please keep the packaging CI as it is, as it
> will be useful for the lifetime of Stretch.
>

I'm sad to hear that as a fellow packager.
You've been a driving force for Debian packaging and improving
OpenStack since its early days.
Your work has helped many people to use OpenStack on Debian and
derived effectively. I hope
that you'll find asap a sponsorship or a dayjob to keep going.

Regards,
H.

> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Tobias Urdin]

On 02/15/2017 01:46 PM, Thomas Goirand wrote:
> Hi there,
>
> It's been a while since I planed on writing this message. I couldn't
> write it because the situation makes me really sad. At this point, it
> starts to be urgent to post it.
>
> As for many other folks, Mirantis decided to end its contract with me.
> This happened when I was the most successful doing the job, with all of
> the packaging CI moved to OpenStack infra at the end of the OpenStack
> Newton cycle, after we were able to release Newton this way. I was
> hoping to start packaging on every commit for Ocata. That's yet another
> reason for me to be very frustrated about all of this. Such is life...
>
> Over the last few months, I hoped for having enough strengths to
> continue my packaging work anyway, and get Ocata packages done. But
> that's not what happened. The biggest reason for this is that I know
> that this needs to be a full time job. And at this point, I still don't
> know what my professional future will be. A company, in Barcelona, told
> me I'd get hired to continue my past work of packaging OpenStack in
> Debian, but so far, I'm still waiting for a definitive answer, so I'm
> looking into some other opportunities.
>
> All this to say that, unless someone wants to hire me for it (which
> would be the best outcome, but I fear this wont happen), or if someone
> steps in (this seems unlikely at this point), both the packaging-deb and
> the faith of OpenStack packages in Debian are currently compromised.
>
> I will continue to maintain OpenStack Newton during the lifetime of
> Debian Stretch though, but I don't plan on doing anything more. This
> means that maybe, Newton will be the last release of OpenStack in
> Debian. If things continue this way, I probably will ask for the removal
> of all OpenStack packages from Debian Sid after Stretch gets released
> (unless I know that someone will do the work).
>
> As a consequence, the following projects wont get packages even in
> Ubuntu (as they were "community maintained", which means done by me and
> later sync into Ubuntu...):
>
> - congress
> - gnocchi
> - magnum
> - mistral
> - murano
> - sahara
> - senlin
> - watcher
> - zaqar
>
> Hopefully, Canonical will continue to maintain the other 15 (more
> core...) projects in UCA.
>
> Thanks for the fish,
>
> Thomas Goirand (zigo)
>
> P,S: To the infra folks: please keep the packaging CI as it is, as it
> will be useful for the lifetime of Stretch.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
Somebody please hire Thomas, he's amazing!

Thank you for everything!


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] The end of OpenStack packages in Debian?

[Paul Belanger]

On Wed, Feb 15, 2017 at 01:43:46PM +0100, Thomas Goirand wrote:
> Hi there,
> 
> It's been a while since I planed on writing this message. I couldn't
> write it because the situation makes me really sad. At this point, it
> starts to be urgent to post it.
> 
> As for many other folks, Mirantis decided to end its contract with me.
> This happened when I was the most successful doing the job, with all of
> the packaging CI moved to OpenStack infra at the end of the OpenStack
> Newton cycle, after we were able to release Newton this way. I was
> hoping to start packaging on every commit for Ocata. That's yet another
> reason for me to be very frustrated about all of this. Such is life...
> 
> Over the last few months, I hoped for having enough strengths to
> continue my packaging work anyway, and get Ocata packages done. But
> that's not what happened. The biggest reason for this is that I know
> that this needs to be a full time job. And at this point, I still don't
> know what my professional future will be. A company, in Barcelona, told
> me I'd get hired to continue my past work of packaging OpenStack in
> Debian, but so far, I'm still waiting for a definitive answer, so I'm
> looking into some other opportunities.
> 
> All this to say that, unless someone wants to hire me for it (which
> would be the best outcome, but I fear this wont happen), or if someone
> steps in (this seems unlikely at this point), both the packaging-deb and
> the faith of OpenStack packages in Debian are currently compromised.
> 
> I will continue to maintain OpenStack Newton during the lifetime of
> Debian Stretch though, but I don't plan on doing anything more. This
> means that maybe, Newton will be the last release of OpenStack in
> Debian. If things continue this way, I probably will ask for the removal
> of all OpenStack packages from Debian Sid after Stretch gets released
> (unless I know that someone will do the work).
> 
> As a consequence, the following projects wont get packages even in
> Ubuntu (as they were "community maintained", which means done by me and
> later sync into Ubuntu...):
> 
> - congress
> - gnocchi
> - magnum
> - mistral
> - murano
> - sahara
> - senlin
> - watcher
> - zaqar
> 
> Hopefully, Canonical will continue to maintain the other 15 (more
> core...) projects in UCA.
> 
> Thanks for the fish,
> 
> Thomas Goirand (zigo)
> 
> P,S: To the infra folks: please keep the packaging CI as it is, as it
> will be useful for the lifetime of Stretch.
> 
Thanks for all your work. I'm glad we eventually stood up all the packaging
infrastructure.

Good luck on your future endeavors.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] The end of OpenStack packages in Debian?

[Thomas Goirand]

Hi there,

It's been a while since I planed on writing this message. I couldn't
write it because the situation makes me really sad. At this point, it
starts to be urgent to post it.

As for many other folks, Mirantis decided to end its contract with me.
This happened when I was the most successful doing the job, with all of
the packaging CI moved to OpenStack infra at the end of the OpenStack
Newton cycle, after we were able to release Newton this way. I was
hoping to start packaging on every commit for Ocata. That's yet another
reason for me to be very frustrated about all of this. Such is life...

Over the last few months, I hoped for having enough strengths to
continue my packaging work anyway, and get Ocata packages done. But
that's not what happened. The biggest reason for this is that I know
that this needs to be a full time job. And at this point, I still don't
know what my professional future will be. A company, in Barcelona, told
me I'd get hired to continue my past work of packaging OpenStack in
Debian, but so far, I'm still waiting for a definitive answer, so I'm
looking into some other opportunities.

All this to say that, unless someone wants to hire me for it (which
would be the best outcome, but I fear this wont happen), or if someone
steps in (this seems unlikely at this point), both the packaging-deb and
the faith of OpenStack packages in Debian are currently compromised.

I will continue to maintain OpenStack Newton during the lifetime of
Debian Stretch though, but I don't plan on doing anything more. This
means that maybe, Newton will be the last release of OpenStack in
Debian. If things continue this way, I probably will ask for the removal
of all OpenStack packages from Debian Sid after Stretch gets released
(unless I know that someone will do the work).

As a consequence, the following projects wont get packages even in
Ubuntu (as they were "community maintained", which means done by me and
later sync into Ubuntu...):

- congress
- gnocchi
- magnum
- mistral
- murano
- sahara
- senlin
- watcher
- zaqar

Hopefully, Canonical will continue to maintain the other 15 (more
core...) projects in UCA.

Thanks for the fish,

Thomas Goirand (zigo)

P,S: To the infra folks: please keep the packaging CI as it is, as it
will be useful for the lifetime of Stretch.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] The end of OpenStack packages in Debian?

[Thomas Goirand]

Hi there,

It's been a while since I planed on writing this message. I couldn't
write it because the situation makes me really sad. At this point, it
starts to be urgent to post it.

As for many other folks, Mirantis decided to end its contract with me.
This happened when I was the most successful doing the job, with all of
the packaging CI moved to OpenStack infra at the end of the OpenStack
Newton cycle, after we were able to release Newton this way. I was
hoping to start packaging on every commit for Ocata. That's yet another
reason for me to be very frustrated about all of this. Such is life...

Over the last few months, I hoped for having enough strengths to
continue my packaging work anyway, and get Ocata packages done. But
that's not what happened. The biggest reason for this is that I know
that this needs to be a full time job. And at this point, I still don't
know what my professional future will be. A company, in Barcelona, told
me I'd get hired to continue my past work of packaging OpenStack in
Debian, but so far, I'm still waiting for a definitive answer, so I'm
looking into some other opportunities.

All this to say that, unless someone wants to hire me for it (which
would be the best outcome, but I fear this wont happen), or if someone
steps in (this seems unlikely at this point), both the packaging-deb and
the faith of OpenStack packages in Debian are currently compromised.

I will continue to maintain OpenStack Newton during the lifetime of
Debian Stretch though, but I don't plan on doing anything more. This
means that maybe, Newton will be the last release of OpenStack in
Debian. If things continue this way, I probably will ask for the removal
of all OpenStack packages from Debian Sid after Stretch gets released
(unless I know that someone will do the work).

As a consequence, the following projects wont get packages even in
Ubuntu (as they were "community maintained", which means done by me and
later sync into Ubuntu...):

- congress
- gnocchi
- magnum
- mistral
- murano
- sahara
- senlin
- watcher
- zaqar

Hopefully, Canonical will continue to maintain the other 15 (more
core...) projects in UCA.

Thanks for the fish,

Thomas Goirand (zigo)

P,S: To the infra folks: please keep the packaging CI as it is, as it
will be useful for the lifetime of Stretch.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev