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

[Allison Randal]

On 02/24/2017 06:25 AM, Ritesh Raj Sarraf wrote:
> rtslib-fb is a core component for the LIO(-fb) project. We already maintain
> configshell-fb and targetcli-fb under pkg-linux-target group.

Nod, that makes sense. I'd say you should take on maintenance of the
rtslib-fb packages, as long as you're willing to integrate with the
global Debian Python transitions and policy, and to handle the fact that
other projects (like the OpenStack Debian packagers) also use the
module. For OpenStack, we may occasionally need to update the rtslib-fb
packages to specific versions for compatibility with specific OpenStack
releases.

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] [PKG-Openstack-devel] The end of OpenStack packages in Debian?

[Thomas Goirand]

On 02/19/2017 06:44 AM, gustavo panizzo wrote:
> On Sun, Feb 19, 2017 at 01:10:21AM +0100, Thomas Goirand wrote:
>> 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.
> how much space does it need?

About 1.5 GB.

> do you have all openstack releases?

I have from Kilo to Mitaka (Newton is directly hosted in infra, so no
need to host it).

> i'll try to get a place for them, no promises are made

Let me know.

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] [PKG-Openstack-devel] The end of OpenStack packages in Debian?

[Matt Riedemann]

On 2/16/2017 5:26 PM, Thomas Goirand wrote:


Also, the approach to give-up the packaging of "non-important" project
(ie: not-core, like the ones in the list I gave...) in the hope it will
save so much time is IMO simply wrong. What eats all of the package
maintenance time is *not* final projects (trove, watcher, etc.) but all
the OpenStack dependencies. Maybe 90% of my time have been spent on
packaging oslo libraries, clients, and 3rd parties, and making sure they
integrate well with the rest of the distro (python 3 compat, Django
1.10, latest SQLA, etc.). So giving-up on that last extra mile of work
to put the cherry on top of the cake isn't the good approach.



FWIW, +1 to that. When I was doing OpenStack packaging for IBM's distro 
on a daily basis a few years ago the brunt of my time was spent on 
currency on the daily changes in the multitude of dependent package 
version changes. We had spit-balled some ideas on automating some of 
that, but just never found the time.


--

Thanks,

Matt Riedemann

__
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] [PKG-Openstack-devel] The end of OpenStack packages in Debian?

[Thomas Goirand]

On 02/16/2017 12:20 PM, Ondrej Novy wrote:
> Hi,
> 
> 2017-02-16 0:45 GMT+01:00 Thomas Goirand  >:
> 
> 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.
> 
> 
> yep, because there are no branches for it. And because I don't know how
> to create them (in infra which I hate for deb packaging) i can't
> continue my work on Ocata.

1/ Let give you the technical answer

Creating a new debian/ocata branch is just one click away. For example,
if you want to do a debian/ocata branch for Nova, just go here:

https://review.openstack.org/#/admin/projects/openstack/deb-nova,branches

type the name of the branch, the sha or simply debian/newton as a ref,
and you're done. That's really super easy, and you even have the ACLs to
do it!

Though the issue here is that you should first get an Ocata repository
created with reprepro. This, only the OpenStack infra team can do. I
investigated quickly, and it seems it should be a "reprepro pull"
command. You'd have to check for it first though, and make sure all
packages gets imported from the Newton pool.

Once that is done, the first package to fix is openstack-pkg-tools, so
that the debian/ocata branch builds and push in the ocata repository.
That's trivial to do, IMO. Just maybe, the pickup job from the infra
team (ie: when a patch is merged) may need to be fixed to push to the
correct place as well.

In any case, the infra team should be able to help, they've been really
helpful.

2/ The social answer

I really wish somebody takes over the work, if I there's no company is
willing to sponsor mine.

But the fact that none (including you) attempted to get in touch with me
to do it over the course of many months, up to the very end of this
Ocata release isn't a good sign. I still don't believe it will happen. I
hope I'll be proven wrong, but I also don't believe it can realistically
happen with just a few volunteers not working on it full time: someone
must get enough commitment to have a global view of what work remains to
be done, do the tests, write patches. That's not something you just do a
few hours on your week-ends. If someone pretends something else, then
this may imply a drastic drop in packaging quality as well, which I'm
*not* willing to put my name on. Otherwise, I would probably have continued.

Also, the approach to give-up the packaging of "non-important" project
(ie: not-core, like the ones in the list I gave...) in the hope it will
save so much time is IMO simply wrong. What eats all of the package
maintenance time is *not* final projects (trove, watcher, etc.) but all
the OpenStack dependencies. Maybe 90% of my time have been spent on
packaging oslo libraries, clients, and 3rd parties, and making sure they
integrate well with the rest of the distro (python 3 compat, Django
1.10, latest SQLA, etc.). So giving-up on that last extra mile of work
to put the cherry on top of the cake isn't the good approach.

Hoping the above helps, though I'm really not sure it does,
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] [PKG-Openstack-devel] The end of OpenStack packages in Debian?

[Silence Dogood]

I'd like to add that Thomas makes the best openstack packages by far.  He's
been a force of nature in packaging and his attention to detail is second
to none.

On Wed, Feb 15, 2017 at 11:28 AM, Haïkel  wrote:

> 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-devel mailing list
> openstack-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/openstack-devel
>
__
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] [PKG-Openstack-devel] The end of OpenStack packages in Debian?

[Silence Dogood]

I hope they have gotten better.  Last time I tried to contribute to
Ubuntu's packaging effort they took over a ear to respond.

On Feb 15, 2017 11:56 AM, "Allison Randal"  wrote:

> 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-devel mailing list
> openstack-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/openstack-devel
>
__
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