[oslo][release] devstack-plugin-(kafka|amqp1) retirement
Hello Osloers,
Our devstack plugins (kafka and amqp1) didn't show a great amount of activity since ussuri, does it still make sense to maintain them?
The latest available SHAs for the both projects comes from Victoria (merged in this period).
Can we retire them or simply retire them from the coordinated releases?
We (the release team) would appreciate some feedback about this point.
Let's open the debat.
Hi Herve,
On Thu, Apr 1, 2021 at 7:25 AM Herve Beraud hberaud@redhat.com wrote:
Hello Osloers,
Our devstack plugins (kafka and amqp1) didn't show a great amount of activity since ussuri, does it still make sense to maintain them?
The latest available SHAs for the both projects comes from Victoria (merged in this period).
Can we retire them or simply retire them from the coordinated releases?
We (the release team) would appreciate some feedback about this point.
Let's open the debat.
The only consumer of these plugins that I'm aware of is oslo.messaging [0]. They are needed in order to run devstack-tempest testing against the non-rabbitmq backends. Perhaps they should be integrated into the oslo.messaging project itself, if possible?
[0] https://codesearch.opendev.org/?q=devstack-plugin-amqp1&i=nope&files...
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
On 4/1/21 6:24 AM, Herve Beraud wrote:
Hello Osloers,
Our devstack plugins (kafka and amqp1) didn't show a great amount of activity since ussuri, does it still make sense to maintain them?
The latest available SHAs for the both projects comes from Victoria (merged in this period).
Can we retire them or simply retire them from the coordinated releases?
These have never been released and are no longer branched. What is their involvement in the coordinated release at this point?
We (the release team) would appreciate some feedback about this point.
Let's open the debat.
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
Le jeu. 1 avr. 2021 à 17:02, Ben Nemec openstack@nemebean.com a écrit :
On 4/1/21 6:24 AM, Herve Beraud wrote:
Hello Osloers,
Our devstack plugins (kafka and amqp1) didn't show a great amount of activity since ussuri, does it still make sense to maintain them?
The latest available SHAs for the both projects comes from Victoria (merged in this period).
Can we retire them or simply retire them from the coordinated releases?
These have never been released and are no longer branched. What is their involvement in the coordinated release at this point?
Yes these deliverables are tagless so no released at all, however, they are coordinated so they are branched during each series.
Though, as said Ben, those deliverables haven't been branched during the previous series (victoria), we suppose that they have been simply forgotten inadvertently,
I proposed a patch to fix that point [1].
However we don't have so many things to branch for the current series [2], no new commits have been merged during the last 7 months (Victoria at this period), so, the question is, do we have reasons to keep them under the coordinated releases umbrella if nothing new happens in this area.
I proposed a patch for Wallaby too, but I'm not convinced that's the right solution.
Maybe Ken is right and maybe that's time to merge these plugins with oslo.messaging, however, I don't know if it's feasible from a devstack point of view.
Adding the QA team to this thread topic to discuss that last point with them.
Thanks for your replies.
[1] https://review.opendev.org/c/openstack/releases/+/784371 [2] https://review.opendev.org/c/openstack/releases/+/784376
We (the release team) would appreciate some feedback about this point.
Let's open the debat.
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
On Thursday, 1 April 2021 17:28:25 CEST Herve Beraud wrote:
Le jeu. 1 avr. 2021 à 17:02, Ben Nemec openstack@nemebean.com a écrit :
On 4/1/21 6:24 AM, Herve Beraud wrote:
Hello Osloers,
Our devstack plugins (kafka and amqp1) didn't show a great amount of activity since ussuri, does it still make sense to maintain them?
The latest available SHAs for the both projects comes from Victoria (merged in this period).
Can we retire them or simply retire them from the coordinated releases?
These have never been released and are no longer branched. What is their involvement in the coordinated release at this point?
Yes these deliverables are tagless so no released at all, however, they are coordinated so they are branched during each series.
Though, as said Ben, those deliverables haven't been branched during the previous series (victoria), we suppose that they have been simply forgotten inadvertently,
I proposed a patch to fix that point [1].
Other devstack plugins are branchless (devstack-plugin-ceph, devstack-plugin- nfs), couldn't those be branchless too?
From my point of view I would argue that yes, however, I don't have the big
picture.
Le jeu. 1 avr. 2021 à 17:42, Luigi Toscano ltoscano@redhat.com a écrit :
On Thursday, 1 April 2021 17:28:25 CEST Herve Beraud wrote:
Le jeu. 1 avr. 2021 à 17:02, Ben Nemec openstack@nemebean.com a écrit
:
On 4/1/21 6:24 AM, Herve Beraud wrote:
Hello Osloers,
Our devstack plugins (kafka and amqp1) didn't show a great amount of activity since ussuri, does it still make sense to maintain them?
The latest available SHAs for the both projects comes from Victoria (merged in this period).
Can we retire them or simply retire them from the coordinated
releases?
These have never been released and are no longer branched. What is
their
involvement in the coordinated release at this point?
Yes these deliverables are tagless so no released at all, however, they
are
coordinated so they are branched during each series.
Though, as said Ben, those deliverables haven't been branched during the previous series (victoria), we suppose that they have been simply
forgotten
inadvertently,
I proposed a patch to fix that point [1].
Other devstack plugins are branchless (devstack-plugin-ceph, devstack-plugin- nfs), couldn't those be branchless too?
-- Luigi
Well, as suggested Luigi let's drop these deliverables (within Wallaby and for the next series).
https://review.opendev.org/c/openstack/releases/+/784376
I kept the Victoria branching but that will be the last one.
https://review.opendev.org/c/openstack/releases/+/784371
Let me know what you think
Le jeu. 1 avr. 2021 à 17:44, Herve Beraud hberaud@redhat.com a écrit :
From my point of view I would argue that yes, however, I don't have the big picture.
Le jeu. 1 avr. 2021 à 17:42, Luigi Toscano ltoscano@redhat.com a écrit :
On Thursday, 1 April 2021 17:28:25 CEST Herve Beraud wrote:
Le jeu. 1 avr. 2021 à 17:02, Ben Nemec openstack@nemebean.com a
écrit :
On 4/1/21 6:24 AM, Herve Beraud wrote:
Hello Osloers,
Our devstack plugins (kafka and amqp1) didn't show a great amount of activity since ussuri, does it still make sense to maintain them?
The latest available SHAs for the both projects comes from Victoria (merged in this period).
Can we retire them or simply retire them from the coordinated
releases?
These have never been released and are no longer branched. What is
their
involvement in the coordinated release at this point?
Yes these deliverables are tagless so no released at all, however, they
are
coordinated so they are branched during each series.
Though, as said Ben, those deliverables haven't been branched during the previous series (victoria), we suppose that they have been simply
forgotten
inadvertently,
I proposed a patch to fix that point [1].
Other devstack plugins are branchless (devstack-plugin-ceph, devstack-plugin- nfs), couldn't those be branchless too?
-- Luigi
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
---- On Thu, 01 Apr 2021 11:05:29 -0500 Herve Beraud hberaud@redhat.com wrote ----
Well, as suggested Luigi let's drop these deliverables (within Wallaby and for the next series).
Having them branchless or branched is completely depends on devstack plugins maintainer and the nature of the setting they do. If they are installing/updating the setting for branched service then yes it makes sense to be branched as devstack is branched. If they are very general setting like ceph or so then branchless also work.
From devstack or QA point of view, both ways are fine.
-gmann
I kept the Victoria branching but that will be the last one. https://review.opendev.org/c/openstack/releases/+/784371 Let me know what you think
Le jeu. 1 avr. 2021 à 17:44, Herve Beraud hberaud@redhat.com a écrit : From my point of view I would argue that yes, however, I don't have the big picture.
Le jeu. 1 avr. 2021 à 17:42, Luigi Toscano ltoscano@redhat.com a écrit : On Thursday, 1 April 2021 17:28:25 CEST Herve Beraud wrote:
Le jeu. 1 avr. 2021 à 17:02, Ben Nemec openstack@nemebean.com a écrit :
On 4/1/21 6:24 AM, Herve Beraud wrote:
Hello Osloers,
Our devstack plugins (kafka and amqp1) didn't show a great amount of activity since ussuri, does it still make sense to maintain them?
The latest available SHAs for the both projects comes from Victoria (merged in this period).
Can we retire them or simply retire them from the coordinated releases?
These have never been released and are no longer branched. What is their involvement in the coordinated release at this point?
Yes these deliverables are tagless so no released at all, however, they are coordinated so they are branched during each series.
Though, as said Ben, those deliverables haven't been branched during the previous series (victoria), we suppose that they have been simply forgotten inadvertently,
I proposed a patch to fix that point [1].
Other devstack plugins are branchless (devstack-plugin-ceph, devstack-plugin- nfs), couldn't those be branchless too?
-- Luigi
-- Hervé BeraudSenior Software Engineer at Red Hatirc: hberaudhttps://github.com/4383/https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
-- Hervé BeraudSenior Software Engineer at Red Hatirc: hberaudhttps://github.com/4383/https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
Le jeu. 1 avr. 2021 à 18:27, Ghanshyam Mann gmann@ghanshyammann.com a écrit :
---- On Thu, 01 Apr 2021 11:05:29 -0500 Herve Beraud hberaud@redhat.com wrote ----
Well, as suggested Luigi let's drop these deliverables (within Wallaby
and for the next series).
Having them branchless or branched is completely depends on devstack plugins maintainer and the nature of the setting they do. If they are installing/updating the setting for branched service then yes it makes sense to be branched as devstack is branched. If they are very general setting like ceph or so then branchless also work.
From devstack or QA point of view, both ways are fine.
Thanks Ghanshyam.
I've no idea if they need specific settings but given the activity of these projects since two series they don't seem to be in that plugin zone.
I personally think that "branchless" could fit well to them. Let's wait for PTL/maintainers reviews.
-gmann
I kept the Victoria branching but that will be the last one. https://review.opendev.org/c/openstack/releases/+/784371 Let me know what you think
Le jeu. 1 avr. 2021 à 17:44, Herve Beraud hberaud@redhat.com a écrit
:
From my point of view I would argue that yes, however, I don't have the
big picture.
Le jeu. 1 avr. 2021 à 17:42, Luigi Toscano ltoscano@redhat.com a
écrit :
On Thursday, 1 April 2021 17:28:25 CEST Herve Beraud wrote:
Le jeu. 1 avr. 2021 à 17:02, Ben Nemec openstack@nemebean.com a
écrit :
On 4/1/21 6:24 AM, Herve Beraud wrote:
Hello Osloers,
Our devstack plugins (kafka and amqp1) didn't show a great amount
of
activity since ussuri, does it still make sense to maintain them?
The latest available SHAs for the both projects comes from
Victoria
(merged in this period).
Can we retire them or simply retire them from the coordinated
releases?
These have never been released and are no longer branched. What is
their
involvement in the coordinated release at this point?
Yes these deliverables are tagless so no released at all, however,
they are
coordinated so they are branched during each series.
Though, as said Ben, those deliverables haven't been branched during
the
previous series (victoria), we suppose that they have been simply
forgotten
inadvertently,
I proposed a patch to fix that point [1].
Other devstack plugins are branchless (devstack-plugin-ceph,
devstack-plugin-
nfs), couldn't those be branchless too?
-- Luigi
-- Hervé BeraudSenior Software Engineer at Red Hatirc: hberaudhttps://
github.com/4383/https://twitter.com/4383hberaud
-----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
-- Hervé BeraudSenior Software Engineer at Red Hatirc: hberaudhttps://
github.com/4383/https://twitter.com/4383hberaud
-----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
On 4/1/21 11:36 AM, Herve Beraud wrote:
Le jeu. 1 avr. 2021 à 18:27, Ghanshyam Mann <gmann@ghanshyammann.com mailto:gmann@ghanshyammann.com> a écrit :
---- On Thu, 01 Apr 2021 11:05:29 -0500 Herve Beraud <hberaud@redhat.com <mailto:hberaud@redhat.com>> wrote ---- > Well, as suggested Luigi let's drop these deliverables (within Wallaby and for the next series). > > https://review.opendev.org/c/openstack/releases/+/784376 Having them branchless or branched is completely depends on devstack plugins maintainer and the nature of the setting they do. If they are installing/updating the setting for branched service then yes it makes sense to be branched as devstack is branched. If they are very general setting like ceph or so then branchless also work. From devstack or QA point of view, both ways are fine.Thanks Ghanshyam.
I've no idea if they need specific settings but given the activity of these projects since two series they don't seem to be in that plugin zone.
I personally think that "branchless" could fit well to them. Let's wait for PTL/maintainers reviews.
I replied on the reviews, but I think branchless is what we intended for the Oslo plugins. We just missed the step of removing the deliverable file.
I can't comment on the containers one because that was never ours (AFAIK).
-gmann > I kept the Victoria branching but that will be the last one. > https://review.opendev.org/c/openstack/releases/+/784371 > Let me know what you think > > Le jeu. 1 avr. 2021 à 17:44, Herve Beraud <hberaud@redhat.com <mailto:hberaud@redhat.com>> a écrit : > From my point of view I would argue that yes, however, I don't have the big picture. > > Le jeu. 1 avr. 2021 à 17:42, Luigi Toscano <ltoscano@redhat.com <mailto:ltoscano@redhat.com>> a écrit : > On Thursday, 1 April 2021 17:28:25 CEST Herve Beraud wrote: > > Le jeu. 1 avr. 2021 à 17:02, Ben Nemec <openstack@nemebean.com <mailto:openstack@nemebean.com>> a écrit : > > > On 4/1/21 6:24 AM, Herve Beraud wrote: > > > > Hello Osloers, > > > > > > > > Our devstack plugins (kafka and amqp1) didn't show a great amount of > > > > activity since ussuri, does it still make sense to maintain them? > > > > > > > > The latest available SHAs for the both projects comes from Victoria > > > > (merged in this period). > > > > > > > > Can we retire them or simply retire them from the coordinated releases? > > > > > > These have never been released and are no longer branched. What is their > > > involvement in the coordinated release at this point? > > > > Yes these deliverables are tagless so no released at all, however, they are > > coordinated so they are branched during each series. > > > > Though, as said Ben, those deliverables haven't been branched during the > > previous series (victoria), we suppose that they have been simply forgotten > > inadvertently, > > > > I proposed a patch to fix that point [1]. > > Other devstack plugins are branchless (devstack-plugin-ceph, devstack-plugin- > nfs), couldn't those be branchless too? > > > -- > Luigi > > > > > -- > Hervé BeraudSenior Software Engineer at Red Hatirc: hberaudhttps://github.com/4383/https://twitter.com/4383hberaud <http://github.com/4383/https://twitter.com/4383hberaud> > -----BEGIN PGP SIGNATURE----- > > wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ > Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ > RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP > F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G > 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g > glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw > m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ > hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 > qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y > F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 > B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O > v6rDpkeNksZ9fFSyoY2o > =ECSj > -----END PGP SIGNATURE----- > > > > -- > Hervé BeraudSenior Software Engineer at Red Hatirc: hberaudhttps://github.com/4383/https://twitter.com/4383hberaud <http://github.com/4383/https://twitter.com/4383hberaud> > -----BEGIN PGP SIGNATURE----- > > wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ > Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ > RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP > F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G > 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g > glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw > m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ > hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 > qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y > F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 > B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O > v6rDpkeNksZ9fFSyoY2o > =ECSj > -----END PGP SIGNATURE----- > >-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
---- On Thu, 01 Apr 2021 10:28:25 -0500 Herve Beraud hberaud@redhat.com wrote ----
Le jeu. 1 avr. 2021 à 17:02, Ben Nemec openstack@nemebean.com a écrit :
On 4/1/21 6:24 AM, Herve Beraud wrote:
Hello Osloers,
Our devstack plugins (kafka and amqp1) didn't show a great amount of activity since ussuri, does it still make sense to maintain them?
The latest available SHAs for the both projects comes from Victoria (merged in this period).
Can we retire them or simply retire them from the coordinated releases?
These have never been released and are no longer branched. What is their involvement in the coordinated release at this point?
Yes these deliverables are tagless so no released at all, however, they are coordinated so they are branched during each series. Though, as said Ben, those deliverables haven't been branched during the previous series (victoria), we suppose that they have been simply forgotten inadvertently, I proposed a patch to fix that point [1]. However we don't have so many things to branch for the current series [2], no new commits have been merged during the last 7 months (Victoria at this period), so, the question is, do we have reasons to keep them under the coordinated releases umbrella if nothing new happens in this area. I proposed a patch for Wallaby too, but I'm not convinced that's the right solution. Maybe Ken is right and maybe that's time to merge these plugins with oslo.messaging, however, I don't know if it's feasible from a devstack point of view.
I do not think there is any difference in devstack plugin's location. Those can be part of the project repo or separate repo. Most of the devstack plugins are part of the project repo. Few devstack plugins in QA project are in separate repo because they are in not related to a specific project.
So I will say to move them to related project repo like oslo.messaging or retire them if no one need which can be decided by Oslo team i think.
-gmann
Adding the QA team to this thread topic to discuss that last point with them. Thanks for your replies.
[1] https://review.opendev.org/c/openstack/releases/+/784371%5B2] https://review.opendev.org/c/openstack/releases/+/784376
We (the release team) would appreciate some feedback about this point.
Let's open the debat.
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
-- Hervé BeraudSenior Software Engineer at Red Hatirc: hberaudhttps://github.com/4383/https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE-----
wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
participants (5)
-
Ben Nemec
-
Ghanshyam Mann
-
Herve Beraud
-
Ken Giusti
-
Luigi Toscano