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

2017-02-24 Thread 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?

2017-02-21 Thread 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] [all] Re-evaluating the suitability of the 6 month release cycle

2015-02-26 Thread Ritesh Raj Sarraf


On 02/26/2015 07:06 PM, Ed Leafe wrote:
 I think you've nailed where the disconnect is between the two sides of this 
 issue: what exactly do we see OpenStack being? You brought up several Linux 
 vendors who ship on a longish cycle, and who provide LTS for their releases. 
 But Linux itself is on no such cycle, nor does it provide long term anything.


But Linux is one monolith project.

 OpenStack can't be all things to all people. Following the Linux analogy, we 
 need a few companies who want to become OpenStack distributors, packagers, 
 and supporters, in the manner of RedHat, Canonical, etc., are for Linux. As a 
 development project, we need to be able to move fluidly, and the release 
 cycle deadlines and freezes get in the way of that. As a packager and 
 distributor, the release cycle scheduler *helps* immeasurably. We can't be 
 both.

I am fairly new to OpenStack, but from what I've ascertained so far,
there are, now, individual sub-releases of individual projects. That
could be a difficult task for any Linux vendor, to distribute.

There's one project, Calibre - EBook Management Software, that does
weekly releases. But again, it is easy for them, because they are a
single controlled project.

For something big as OpenStack, IMO, close co-ordination is needed.

-- 
Given the large number of mailing lists I follow, I request you to CC me
in replies for quicker response


__
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