[kuryr][tc] Final call for Kuryr PTL/DPL liaisons
Hello Everyone, Kuryr project ends up being a leaderless project for the 2024.2 Dalmatian cycle[1]. There is no volunteer to serve as PTL or DPL liaisons yet. As the next step, I have proposed to mark this project Inactive: - https://review.opendev.org/c/openstack/governance/+/916945 If you would like to serve as a leader and help maintain this project, this is the right time to step up by replying to this email or commenting in gerrit change 916945. [1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 Ref: https://governance.openstack.org/tc/reference/emerging-technology-and-inacti... -gmann
Hi, I believe it makes sense to mark the project as inactive or even retired. In the past cycles Kuryr was maintained by a team of Red Hat developers, because kuryr-kubernetes was offered as a CNI choice for OpenShift. Observing customers' issues with Kuryr and Neutron scalability, and seeing that other non-OpenStack-native CNI's are starting to offer a comparable networking performance, we've decided to deprecate Kuryr in OpenShift 4.12 (released early 2023) and it got removed in 4.15 (released recently). This means that the incentive to keep the project alive is gone and it's a wise decision to put it as inactive. However we need to make sure this won't affect Zun. To my knowledge Zun is utilizing kuryr-libnetwork in its CI testing. I'm think I'm okay with moving kuryr-libnetwork into Zun's control as they are probably the only active users of that code. Thanks, Michał On Wed, 2024-04-24 at 13:01 -0700, Ghanshyam Mann wrote:
Hello Everyone,
Kuryr project ends up being a leaderless project for the 2024.2 Dalmatian cycle[1]. There is no volunteer to serve as PTL or DPL liaisons yet. As the next step, I have proposed to mark this project Inactive: - https://review.opendev.org/c/openstack/governance/+/916945
If you would like to serve as a leader and help maintain this project, this is the right time to step up by replying to this email or commenting in gerrit change 916945.
[1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 Ref: https://governance.openstack.org/tc/reference/emerging-technology-and-inacti...
-gmann
---- On Thu, 25 Apr 2024 05:03:51 -0700 Michał Dulko wrote ---
Hi,
I believe it makes sense to mark the project as inactive or even retired. In the past cycles Kuryr was maintained by a team of Red Hat developers, because kuryr-kubernetes was offered as a CNI choice for OpenShift. Observing customers' issues with Kuryr and Neutron scalability, and seeing that other non-OpenStack-native CNI's are starting to offer a comparable networking performance, we've decided to deprecate Kuryr in OpenShift 4.12 (released early 2023) and it got removed in 4.15 (released recently). This means that the incentive to keep the project alive is gone and it's a wise decision to put it as inactive.
However we need to make sure this won't affect Zun. To my knowledge Zun is utilizing kuryr-libnetwork in its CI testing. I'm think I'm okay with moving kuryr-libnetwork into Zun's control as they are probably the only active users of that code.
First of all thanks for maintaining this project and updates about the current situation. Good point on Zun dependency, I am tagging Zun on this email to get their opinion. Until we retire Kuryr, kuryr-libnetwork will stay (will not released) but it is good to think about the alternative when we see the project is Inactive. -gmann
Thanks, Michał
On Wed, 2024-04-24 at 13:01 -0700, Ghanshyam Mann wrote:
Hello Everyone,
Kuryr project ends up being a leaderless project for the 2024.2 Dalmatian cycle[1]. There is no volunteer to serve as PTL or DPL liaisons yet. As the next step, I have proposed to mark this project Inactive: - https://review.opendev.org/c/openstack/governance/+/916945
If you would like to serve as a leader and help maintain this project, this is the right time to step up by replying to this email or commenting in gerrit change 916945.
[1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 Ref: https://governance.openstack.org/tc/reference/emerging-technology-and-inacti...
-gmann
Hi, Yes. Zun would like to take over openstack/kuryr-libnetwork and its dependency openstack/kuryr. Please ping me if I need to submit or review any PR about that. Thanks. Best regards, Hongbin On Fri, Apr 26, 2024 at 7:01 AM Ghanshyam Mann <gmann@ghanshyammann.com> wrote:
---- On Thu, 25 Apr 2024 05:03:51 -0700 Michał Dulko wrote ---
Hi,
I believe it makes sense to mark the project as inactive or even retired. In the past cycles Kuryr was maintained by a team of Red Hat developers, because kuryr-kubernetes was offered as a CNI choice for OpenShift. Observing customers' issues with Kuryr and Neutron scalability, and seeing that other non-OpenStack-native CNI's are starting to offer a comparable networking performance, we've decided to deprecate Kuryr in OpenShift 4.12 (released early 2023) and it got removed in 4.15 (released recently). This means that the incentive to keep the project alive is gone and it's a wise decision to put it as inactive.
However we need to make sure this won't affect Zun. To my knowledge Zun is utilizing kuryr-libnetwork in its CI testing. I'm think I'm okay with moving kuryr-libnetwork into Zun's control as they are probably the only active users of that code.
First of all thanks for maintaining this project and updates about the current situation. Good point on Zun dependency, I am tagging Zun on this email to get their opinion. Until we retire Kuryr, kuryr-libnetwork will stay (will not released) but it is good to think about the alternative when we see the project is Inactive.
-gmann
Thanks, Michał
On Wed, 2024-04-24 at 13:01 -0700, Ghanshyam Mann wrote:
Hello Everyone,
Kuryr project ends up being a leaderless project for the 2024.2 Dalmatian cycle[1]. There is no volunteer to serve as PTL or DPL liaisons yet. As the next step, I have proposed to mark this project Inactive: - https://review.opendev.org/c/openstack/governance/+/916945
If you would like to serve as a leader and help maintain this project, this is the right time to step up by replying to this email or commenting in gerrit change 916945.
[1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 Ref:
https://governance.openstack.org/tc/reference/emerging-technology-and-inacti...
-gmann
---- On Fri, 26 Apr 2024 01:35:32 -0700 Hongbin Lu wrote ---
Hi, Yes. Zun would like to take over openstack/kuryr-libnetwork and its dependency openstack/kuryr. Please ping me if I need to submit or review any PR about that. Thanks.
Thanks Hongbin, Feel free to propose the governance change to move those repo under Zun. -gmann
Best regards,Hongbin On Fri, Apr 26, 2024 at 7:01 AM Ghanshyam Mann gmann@ghanshyammann.com> wrote: ---- On Thu, 25 Apr 2024 05:03:51 -0700 Michał Dulko wrote --- > Hi, > > I believe it makes sense to mark the project as inactive or even > retired. In the past cycles Kuryr was maintained by a team of Red Hat > developers, because kuryr-kubernetes was offered as a CNI choice for > OpenShift. Observing customers' issues with Kuryr and Neutron > scalability, and seeing that other non-OpenStack-native CNI's are > starting to offer a comparable networking performance, we've decided to > deprecate Kuryr in OpenShift 4.12 (released early 2023) and it got > removed in 4.15 (released recently). This means that the incentive to > keep the project alive is gone and it's a wise decision to put it as > inactive. > > However we need to make sure this won't affect Zun. To my knowledge Zun > is utilizing kuryr-libnetwork in its CI testing. I'm think I'm okay > with moving kuryr-libnetwork into Zun's control as they are probably > the only active users of that code.
First of all thanks for maintaining this project and updates about the current situation. Good point on Zun dependency, I am tagging Zun on this email to get their opinion. Until we retire Kuryr, kuryr-libnetwork will stay (will not released) but it is good to think about the alternative when we see the project is Inactive.
-gmann
> > Thanks, > Michał > > On Wed, 2024-04-24 at 13:01 -0700, Ghanshyam Mann wrote: > > Hello Everyone, > > > > Kuryr project ends up being a leaderless project for the 2024.2 > > Dalmatian cycle[1]. There is no > > volunteer to serve as PTL or DPL liaisons yet. As the next step, I > > have proposed to mark this project > > Inactive: > > - https://review.opendev.org/c/openstack/governance/+/916945 > > > > If you would like to serve as a leader and help maintain this > > project, this is the right time > > to step up by replying to this email or commenting in gerrit change > > 916945. > > > > [1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 > > Ref: > > https://governance.openstack.org/tc/reference/emerging-technology-and-inacti... > > > > -gmann > > > >
Updates on Kuryr project status: - openstack/kuryr and openstack/kuryr-libnetwork have been moved to the Zun project[1] - openstack/kuryr-kubernetes and openstack/kuryr-tempest-plugin are the remaining deliverables with no maintainers. If you or any of your known member/organization is interested in maintaining the remaining two deliverables, feel free to reply to this email or ping any of the TC members in #openstack-tc IRC channel. We will keep it open until the next two weeks and based on the response we can take the next step. [1] https://review.opendev.org/c/openstack/governance/+/917517 -gmann ---- On Fri, 26 Apr 2024 10:12:24 -0700 Ghanshyam Mann wrote ---
---- On Fri, 26 Apr 2024 01:35:32 -0700 Hongbin Lu wrote ---
Hi, Yes. Zun would like to take over openstack/kuryr-libnetwork and its dependency openstack/kuryr. Please ping me if I need to submit or review any PR about that. Thanks.
Thanks Hongbin,
Feel free to propose the governance change to move those repo under Zun.
-gmann
Best regards,Hongbin On Fri, Apr 26, 2024 at 7:01 AM Ghanshyam Mann gmann@ghanshyammann.com> wrote: ---- On Thu, 25 Apr 2024 05:03:51 -0700 Michał Dulko wrote --- > Hi, > > I believe it makes sense to mark the project as inactive or even > retired. In the past cycles Kuryr was maintained by a team of Red Hat > developers, because kuryr-kubernetes was offered as a CNI choice for > OpenShift. Observing customers' issues with Kuryr and Neutron > scalability, and seeing that other non-OpenStack-native CNI's are > starting to offer a comparable networking performance, we've decided to > deprecate Kuryr in OpenShift 4.12 (released early 2023) and it got > removed in 4.15 (released recently). This means that the incentive to > keep the project alive is gone and it's a wise decision to put it as > inactive. > > However we need to make sure this won't affect Zun. To my knowledge Zun > is utilizing kuryr-libnetwork in its CI testing. I'm think I'm okay > with moving kuryr-libnetwork into Zun's control as they are probably > the only active users of that code.
First of all thanks for maintaining this project and updates about the current situation. Good point on Zun dependency, I am tagging Zun on this email to get their opinion. Until we retire Kuryr, kuryr-libnetwork will stay (will not released) but it is good to think about the alternative when we see the project is Inactive.
-gmann
> > Thanks, > Michał > > On Wed, 2024-04-24 at 13:01 -0700, Ghanshyam Mann wrote: > > Hello Everyone, > > > > Kuryr project ends up being a leaderless project for the 2024.2 > > Dalmatian cycle[1]. There is no > > volunteer to serve as PTL or DPL liaisons yet. As the next step, I > > have proposed to mark this project > > Inactive: > > - https://review.opendev.org/c/openstack/governance/+/916945 > > > > If you would like to serve as a leader and help maintain this > > project, this is the right time > > to step up by replying to this email or commenting in gerrit change > > 916945. > > > > [1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 > > Ref: > > https://governance.openstack.org/tc/reference/emerging-technology-and-inacti... > > > > -gmann > > > >
---- On Thu, 30 May 2024 09:33:56 -0700 Ghanshyam Mann wrote ---
Updates on Kuryr project status:
- openstack/kuryr and openstack/kuryr-libnetwork have been moved to the Zun project[1]
- openstack/kuryr-kubernetes and openstack/kuryr-tempest-plugin are the remaining deliverables with no maintainers.
If you or any of your known member/organization is interested in maintaining the remaining two deliverables, feel free to reply to this email or ping any of the TC members in #openstack-tc IRC channel.
We will keep it open until the next two weeks and based on the response we can take the next step.
No volunteer or response so I proposed to retire both the repos - https://review.opendev.org/c/openstack/governance/+/922507 -gmann
[1] https://review.opendev.org/c/openstack/governance/+/917517
-gmann
---- On Fri, 26 Apr 2024 10:12:24 -0700 Ghanshyam Mann wrote ---
---- On Fri, 26 Apr 2024 01:35:32 -0700 Hongbin Lu wrote ---
Hi, Yes. Zun would like to take over openstack/kuryr-libnetwork and its dependency openstack/kuryr. Please ping me if I need to submit or review any PR about that. Thanks.
Thanks Hongbin,
Feel free to propose the governance change to move those repo under Zun.
-gmann
Best regards,Hongbin On Fri, Apr 26, 2024 at 7:01 AM Ghanshyam Mann gmann@ghanshyammann.com> wrote: ---- On Thu, 25 Apr 2024 05:03:51 -0700 Michał Dulko wrote --- > Hi, > > I believe it makes sense to mark the project as inactive or even > retired. In the past cycles Kuryr was maintained by a team of Red Hat > developers, because kuryr-kubernetes was offered as a CNI choice for > OpenShift. Observing customers' issues with Kuryr and Neutron > scalability, and seeing that other non-OpenStack-native CNI's are > starting to offer a comparable networking performance, we've decided to > deprecate Kuryr in OpenShift 4.12 (released early 2023) and it got > removed in 4.15 (released recently). This means that the incentive to > keep the project alive is gone and it's a wise decision to put it as > inactive. > > However we need to make sure this won't affect Zun. To my knowledge Zun > is utilizing kuryr-libnetwork in its CI testing. I'm think I'm okay > with moving kuryr-libnetwork into Zun's control as they are probably > the only active users of that code.
First of all thanks for maintaining this project and updates about the current situation. Good point on Zun dependency, I am tagging Zun on this email to get their opinion. Until we retire Kuryr, kuryr-libnetwork will stay (will not released) but it is good to think about the alternative when we see the project is Inactive.
-gmann
> > Thanks, > Michał > > On Wed, 2024-04-24 at 13:01 -0700, Ghanshyam Mann wrote: > > Hello Everyone, > > > > Kuryr project ends up being a leaderless project for the 2024.2 > > Dalmatian cycle[1]. There is no > > volunteer to serve as PTL or DPL liaisons yet. As the next step, I > > have proposed to mark this project > > Inactive: > > - https://review.opendev.org/c/openstack/governance/+/916945 > > > > If you would like to serve as a leader and help maintain this > > project, this is the right time > > to step up by replying to this email or commenting in gerrit change > > 916945. > > > > [1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 > > Ref: > > https://governance.openstack.org/tc/reference/emerging-technology-and-inacti... > > > > -gmann > > > >
Hi gmann and all, Tacker has decided to drop dependency on kuryr-kubernetes, but the change is not completed yet. So, could you wait to remove the repo until it's ready? Thanks, Yasufumi On 2024/06/22 2:53, Ghanshyam Mann wrote:
---- On Thu, 30 May 2024 09:33:56 -0700 Ghanshyam Mann wrote ---
Updates on Kuryr project status:
- openstack/kuryr and openstack/kuryr-libnetwork have been moved to the Zun project[1]
- openstack/kuryr-kubernetes and openstack/kuryr-tempest-plugin are the remaining deliverables with no maintainers.
If you or any of your known member/organization is interested in maintaining the remaining two deliverables, feel free to reply to this email or ping any of the TC members in #openstack-tc IRC channel.
We will keep it open until the next two weeks and based on the response we can take the next step.
No volunteer or response so I proposed to retire both the repos
- https://review.opendev.org/c/openstack/governance/+/922507
-gmann
[1] https://review.opendev.org/c/openstack/governance/+/917517
-gmann
---- On Fri, 26 Apr 2024 10:12:24 -0700 Ghanshyam Mann wrote ---
---- On Fri, 26 Apr 2024 01:35:32 -0700 Hongbin Lu wrote ---
Hi, Yes. Zun would like to take over openstack/kuryr-libnetwork and its dependency openstack/kuryr. Please ping me if I need to submit or review any PR about that. Thanks.
Thanks Hongbin,
Feel free to propose the governance change to move those repo under Zun.
-gmann
Best regards,Hongbin On Fri, Apr 26, 2024 at 7:01 AM Ghanshyam Mann gmann@ghanshyammann.com> wrote: ---- On Thu, 25 Apr 2024 05:03:51 -0700 Michał Dulko wrote --- > Hi, > > I believe it makes sense to mark the project as inactive or even > retired. In the past cycles Kuryr was maintained by a team of Red Hat > developers, because kuryr-kubernetes was offered as a CNI choice for > OpenShift. Observing customers' issues with Kuryr and Neutron > scalability, and seeing that other non-OpenStack-native CNI's are > starting to offer a comparable networking performance, we've decided to > deprecate Kuryr in OpenShift 4.12 (released early 2023) and it got > removed in 4.15 (released recently). This means that the incentive to > keep the project alive is gone and it's a wise decision to put it as > inactive. > > However we need to make sure this won't affect Zun. To my knowledge Zun > is utilizing kuryr-libnetwork in its CI testing. I'm think I'm okay > with moving kuryr-libnetwork into Zun's control as they are probably > the only active users of that code.
First of all thanks for maintaining this project and updates about the current situation. Good point on Zun dependency, I am tagging Zun on this email to get their opinion. Until we retire Kuryr, kuryr-libnetwork will stay (will not released) but it is good to think about the alternative when we see the project is Inactive.
-gmann
> > Thanks, > Michał > > On Wed, 2024-04-24 at 13:01 -0700, Ghanshyam Mann wrote: > > Hello Everyone, > > > > Kuryr project ends up being a leaderless project for the 2024.2 > > Dalmatian cycle[1]. There is no > > volunteer to serve as PTL or DPL liaisons yet. As the next step, I > > have proposed to mark this project > > Inactive: > > - https://review.opendev.org/c/openstack/governance/+/916945 > > > > If you would like to serve as a leader and help maintain this > > project, this is the right time > > to step up by replying to this email or commenting in gerrit change > > 916945. > > > > [1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 > > Ref: > > https://governance.openstack.org/tc/reference/emerging-technology-and-inacti... > > > > -gmann > > > >
---- On Wed, 03 Jul 2024 21:02:42 -0700 Yasufumi Ogawa wrote ---
Hi gmann and all,
Tacker has decided to drop dependency on kuryr-kubernetes, but the change is not completed yet. So, could you wait to remove the repo until it's ready?
Hi Yasufumi, Sure, I will keep it WIP until the Tacker dependency is resolved. No hurry. -gmann
Thanks, Yasufumi
On 2024/06/22 2:53, Ghanshyam Mann wrote:
---- On Thu, 30 May 2024 09:33:56 -0700 Ghanshyam Mann wrote ---
Updates on Kuryr project status:
- openstack/kuryr and openstack/kuryr-libnetwork have been moved to the Zun project[1]
- openstack/kuryr-kubernetes and openstack/kuryr-tempest-plugin are the remaining deliverables with no maintainers.
If you or any of your known member/organization is interested in maintaining the remaining two deliverables, feel free to reply to this email or ping any of the TC members in #openstack-tc IRC channel.
We will keep it open until the next two weeks and based on the response we can take the next step.
No volunteer or response so I proposed to retire both the repos
- https://review.opendev.org/c/openstack/governance/+/922507
-gmann
[1] https://review.opendev.org/c/openstack/governance/+/917517
-gmann
---- On Fri, 26 Apr 2024 10:12:24 -0700 Ghanshyam Mann wrote ---
---- On Fri, 26 Apr 2024 01:35:32 -0700 Hongbin Lu wrote ---
Hi, Yes. Zun would like to take over openstack/kuryr-libnetwork and its dependency openstack/kuryr. Please ping me if I need to submit or review any PR about that. Thanks.
Thanks Hongbin,
Feel free to propose the governance change to move those repo under Zun.
-gmann
Best regards,Hongbin On Fri, Apr 26, 2024 at 7:01 AM Ghanshyam Mann gmann@ghanshyammann.com> wrote: ---- On Thu, 25 Apr 2024 05:03:51 -0700 Michał Dulko wrote --- > Hi, > > I believe it makes sense to mark the project as inactive or even > retired. In the past cycles Kuryr was maintained by a team of Red Hat > developers, because kuryr-kubernetes was offered as a CNI choice for > OpenShift. Observing customers' issues with Kuryr and Neutron > scalability, and seeing that other non-OpenStack-native CNI's are > starting to offer a comparable networking performance, we've decided to > deprecate Kuryr in OpenShift 4.12 (released early 2023) and it got > removed in 4.15 (released recently). This means that the incentive to > keep the project alive is gone and it's a wise decision to put it as > inactive. > > However we need to make sure this won't affect Zun. To my knowledge Zun > is utilizing kuryr-libnetwork in its CI testing. I'm think I'm okay > with moving kuryr-libnetwork into Zun's control as they are probably > the only active users of that code.
First of all thanks for maintaining this project and updates about the current situation. Good point on Zun dependency, I am tagging Zun on this email to get their opinion. Until we retire Kuryr, kuryr-libnetwork will stay (will not released) but it is good to think about the alternative when we see the project is Inactive.
-gmann
> > Thanks, > Michał > > On Wed, 2024-04-24 at 13:01 -0700, Ghanshyam Mann wrote: > > Hello Everyone, > > > > Kuryr project ends up being a leaderless project for the 2024.2 > > Dalmatian cycle[1]. There is no > > volunteer to serve as PTL or DPL liaisons yet. As the next step, I > > have proposed to mark this project > > Inactive: > > - https://review.opendev.org/c/openstack/governance/+/916945 > > > > If you would like to serve as a leader and help maintain this > > project, this is the right time > > to step up by replying to this email or commenting in gerrit change > > 916945. > > > > [1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 > > Ref: > > https://governance.openstack.org/tc/reference/emerging-technology-and-inacti... > > > > -gmann > > > >
On 2024/07/05 1:33, Ghanshyam Mann wrote:
---- On Wed, 03 Jul 2024 21:02:42 -0700 Yasufumi Ogawa wrote ---
Hi gmann and all,
Tacker has decided to drop dependency on kuryr-kubernetes, but the change is not completed yet. So, could you wait to remove the repo until it's ready?
Hi Yasufumi,
Sure, I will keep it WIP until the Tacker dependency is resolved. No hurry. Ghanshyam,
Thanks! I'll notice soon if our update is done. Yasufumi
-gmann
Thanks, Yasufumi
On 2024/06/22 2:53, Ghanshyam Mann wrote:
---- On Thu, 30 May 2024 09:33:56 -0700 Ghanshyam Mann wrote ---
Updates on Kuryr project status:
- openstack/kuryr and openstack/kuryr-libnetwork have been moved to the Zun project[1]
- openstack/kuryr-kubernetes and openstack/kuryr-tempest-plugin are the remaining deliverables with no maintainers.
If you or any of your known member/organization is interested in maintaining the remaining two deliverables, feel free to reply to this email or ping any of the TC members in #openstack-tc IRC channel.
We will keep it open until the next two weeks and based on the response we can take the next step.
No volunteer or response so I proposed to retire both the repos
- https://review.opendev.org/c/openstack/governance/+/922507
-gmann
[1] https://review.opendev.org/c/openstack/governance/+/917517
-gmann
---- On Fri, 26 Apr 2024 10:12:24 -0700 Ghanshyam Mann wrote ---
---- On Fri, 26 Apr 2024 01:35:32 -0700 Hongbin Lu wrote ---
Hi, Yes. Zun would like to take over openstack/kuryr-libnetwork and its dependency openstack/kuryr. Please ping me if I need to submit or review any PR about that. Thanks.
Thanks Hongbin,
Feel free to propose the governance change to move those repo under Zun.
-gmann
Best regards,Hongbin On Fri, Apr 26, 2024 at 7:01 AM Ghanshyam Mann gmann@ghanshyammann.com> wrote: ---- On Thu, 25 Apr 2024 05:03:51 -0700 Michał Dulko wrote --- > Hi, > > I believe it makes sense to mark the project as inactive or even > retired. In the past cycles Kuryr was maintained by a team of Red Hat > developers, because kuryr-kubernetes was offered as a CNI choice for > OpenShift. Observing customers' issues with Kuryr and Neutron > scalability, and seeing that other non-OpenStack-native CNI's are > starting to offer a comparable networking performance, we've decided to > deprecate Kuryr in OpenShift 4.12 (released early 2023) and it got > removed in 4.15 (released recently). This means that the incentive to > keep the project alive is gone and it's a wise decision to put it as > inactive. > > However we need to make sure this won't affect Zun. To my knowledge Zun > is utilizing kuryr-libnetwork in its CI testing. I'm think I'm okay > with moving kuryr-libnetwork into Zun's control as they are probably > the only active users of that code.
First of all thanks for maintaining this project and updates about the current situation. Good point on Zun dependency, I am tagging Zun on this email to get their opinion. Until we retire Kuryr, kuryr-libnetwork will stay (will not released) but it is good to think about the alternative when we see the project is Inactive.
-gmann
> > Thanks, > Michał > > On Wed, 2024-04-24 at 13:01 -0700, Ghanshyam Mann wrote: > > Hello Everyone, > > > > Kuryr project ends up being a leaderless project for the 2024.2 > > Dalmatian cycle[1]. There is no > > volunteer to serve as PTL or DPL liaisons yet. As the next step, I > > have proposed to mark this project > > Inactive: > > - https://review.opendev.org/c/openstack/governance/+/916945 > > > > If you would like to serve as a leader and help maintain this > > project, this is the right time > > to step up by replying to this email or commenting in gerrit change > > 916945. > > > > [1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 > > Ref: > > https://governance.openstack.org/tc/reference/emerging-technology-and-inacti... > > > > -gmann > > > >
Hi all, Sorry for waiting for a long time to fix the change. We tacker team have finished to remove the dependency and ready the patch to be merged[1]. [1] https://review.opendev.org/c/openstack/tacker/+/926504 Thanks, Yasufumi On 2024/07/05 1:33, Ghanshyam Mann wrote:
---- On Wed, 03 Jul 2024 21:02:42 -0700 Yasufumi Ogawa wrote ---
Hi gmann and all,
Tacker has decided to drop dependency on kuryr-kubernetes, but the change is not completed yet. So, could you wait to remove the repo until it's ready?
Hi Yasufumi,
Sure, I will keep it WIP until the Tacker dependency is resolved. No hurry.
-gmann
Thanks, Yasufumi
On 2024/06/22 2:53, Ghanshyam Mann wrote:
---- On Thu, 30 May 2024 09:33:56 -0700 Ghanshyam Mann wrote ---
Updates on Kuryr project status:
- openstack/kuryr and openstack/kuryr-libnetwork have been moved to the Zun project[1]
- openstack/kuryr-kubernetes and openstack/kuryr-tempest-plugin are the remaining deliverables with no maintainers.
If you or any of your known member/organization is interested in maintaining the remaining two deliverables, feel free to reply to this email or ping any of the TC members in #openstack-tc IRC channel.
We will keep it open until the next two weeks and based on the response we can take the next step.
No volunteer or response so I proposed to retire both the repos
- https://review.opendev.org/c/openstack/governance/+/922507
-gmann
[1] https://review.opendev.org/c/openstack/governance/+/917517
-gmann
---- On Fri, 26 Apr 2024 10:12:24 -0700 Ghanshyam Mann wrote ---
---- On Fri, 26 Apr 2024 01:35:32 -0700 Hongbin Lu wrote ---
Hi, Yes. Zun would like to take over openstack/kuryr-libnetwork and its dependency openstack/kuryr. Please ping me if I need to submit or review any PR about that. Thanks.
Thanks Hongbin,
Feel free to propose the governance change to move those repo under Zun.
-gmann
Best regards,Hongbin On Fri, Apr 26, 2024 at 7:01 AM Ghanshyam Mann gmann@ghanshyammann.com> wrote: ---- On Thu, 25 Apr 2024 05:03:51 -0700 Michał Dulko wrote --- > Hi, > > I believe it makes sense to mark the project as inactive or even > retired. In the past cycles Kuryr was maintained by a team of Red Hat > developers, because kuryr-kubernetes was offered as a CNI choice for > OpenShift. Observing customers' issues with Kuryr and Neutron > scalability, and seeing that other non-OpenStack-native CNI's are > starting to offer a comparable networking performance, we've decided to > deprecate Kuryr in OpenShift 4.12 (released early 2023) and it got > removed in 4.15 (released recently). This means that the incentive to > keep the project alive is gone and it's a wise decision to put it as > inactive. > > However we need to make sure this won't affect Zun. To my knowledge Zun > is utilizing kuryr-libnetwork in its CI testing. I'm think I'm okay > with moving kuryr-libnetwork into Zun's control as they are probably > the only active users of that code.
First of all thanks for maintaining this project and updates about the current situation. Good point on Zun dependency, I am tagging Zun on this email to get their opinion. Until we retire Kuryr, kuryr-libnetwork will stay (will not released) but it is good to think about the alternative when we see the project is Inactive.
-gmann
> > Thanks, > Michał > > On Wed, 2024-04-24 at 13:01 -0700, Ghanshyam Mann wrote: > > Hello Everyone, > > > > Kuryr project ends up being a leaderless project for the 2024.2 > > Dalmatian cycle[1]. There is no > > volunteer to serve as PTL or DPL liaisons yet. As the next step, I > > have proposed to mark this project > > Inactive: > > - https://review.opendev.org/c/openstack/governance/+/916945 > > > > If you would like to serve as a leader and help maintain this > > project, this is the right time > > to step up by replying to this email or commenting in gerrit change > > 916945. > > > > [1] https://etherpad.opendev.org/p/2024.2-leaderless#L99 > > Ref: > > https://governance.openstack.org/tc/reference/emerging-technology-and-inacti... > > > > -gmann > > > >
participants (4)
-
Ghanshyam Mann
-
Hongbin Lu
-
Michał Dulko
-
Yasufumi Ogawa