[i18n][mogan][neutron][swift][tc][valet] Cleaning up IRC logging for defunct channels
Freenode imposes a hard limit of 120 simultaneously joined channels for any single account. We've once again reached that limit with our channel-logging meetbot. As a quick measure, I've proposed a bit of cleanup: https://review.opendev.org/682500
Analysis of IRC channel logs indicates the following have seen 5 or fewer non-bot comments posted in the past 12 months and are likely of no value to continue logging:
5 #openstack-vpnaas 2 #swift3 2 #openstack-ko 1 #openstack-deployment 1 #midonet 0 #openstack-valet 0 #openstack-swg 0 #openstack-mogan
Please let me know either here on the ML or with a comment on the review linked above if you have a reason to continue logging any of these channels. I'd like to merge it later this week if possible. Thanks!
On Tue, Sep 17, 2019 at 7:20 AM Jeremy Stanley fungi@yuggoth.org wrote:
Freenode imposes a hard limit of 120 simultaneously joined channels for any single account. We've once again reached that limit with our channel-logging meetbot. As a quick measure, I've proposed a bit of cleanup: https://review.opendev.org/682500
Analysis of IRC channel logs indicates the following have seen 5 or fewer non-bot comments posted in the past 12 months and are likely of no value to continue logging:
5 #openstack-vpnaas
I would like to add the following channels to this list in addition to #openstack-vpnaas. This is what I think recently but I haven't discussed it yet with the team.
- openstack-fwaas - networking-sfc
I see only 5~20 members in these channels constantly. Developments in FWaaS and SFC are not so active, so I don't see a good reason to have a separate channel. They can be merged into the main neutron channel #openstack-neutron.
Is there any guideline on how to guide users to migrate a channel to another channel?
Thanks, Akihiro
2 #swift3 2 #openstack-ko 1 #openstack-deployment 1 #midonet 0 #openstack-valet 0 #openstack-swg 0 #openstack-moganPlease let me know either here on the ML or with a comment on the review linked above if you have a reason to continue logging any of these channels. I'd like to merge it later this week if possible. Thanks! -- Jeremy Stanley
On 17/09/2019 07.11, Akihiro Motoki wrote:
On Tue, Sep 17, 2019 at 7:20 AM Jeremy Stanley fungi@yuggoth.org wrote:
Freenode imposes a hard limit of 120 simultaneously joined channels for any single account. We've once again reached that limit with our channel-logging meetbot. As a quick measure, I've proposed a bit of cleanup: https://review.opendev.org/682500
Analysis of IRC channel logs indicates the following have seen 5 or fewer non-bot comments posted in the past 12 months and are likely of no value to continue logging:
5 #openstack-vpnaasI would like to add the following channels to this list in addition to #openstack-vpnaas. This is what I think recently but I haven't discussed it yet with the team.
- openstack-fwaas
- networking-sfc
I see only 5~20 members in these channels constantly. Developments in FWaaS and SFC are not so active, so I don't see a good reason to have a separate channel. They can be merged into the main neutron channel #openstack-neutron.
If you retire the channel completely, also remove the bot notifications from project-config.
Is there any guideline on how to guide users to migrate a channel to another channel?
I think the following would work:
https://docs.openstack.org/infra/system-config/irc.html#renaming-an-irc-chan...
Andreas
Hi,
On 17 Sep 2019, at 07:11, Akihiro Motoki amotoki@gmail.com wrote:
On Tue, Sep 17, 2019 at 7:20 AM Jeremy Stanley fungi@yuggoth.org wrote:
Freenode imposes a hard limit of 120 simultaneously joined channels for any single account. We've once again reached that limit with our channel-logging meetbot. As a quick measure, I've proposed a bit of cleanup: https://review.opendev.org/682500
Analysis of IRC channel logs indicates the following have seen 5 or fewer non-bot comments posted in the past 12 months and are likely of no value to continue logging:
5 #openstack-vpnaas
I would like to add the following channels to this list in addition to #openstack-vpnaas. This is what I think recently but I haven't discussed it yet with the team.
- openstack-fwaas
- networking-sfc
Ha, I didn’t even know that such channels exists. And from what I can say, if there are any topics related to such stadium projects, we are discussing them on #openstack-neutron channel usually. IMHO we can remove them too.
I see only 5~20 members in these channels constantly. Developments in FWaaS and SFC are not so active, so I don't see a good reason to have a separate channel. They can be merged into the main neutron channel #openstack-neutron.
Is there any guideline on how to guide users to migrate a channel to another channel?
Thanks, Akihiro
2 #swift3 2 #openstack-ko 1 #openstack-deployment 1 #midonet 0 #openstack-valet 0 #openstack-swg 0 #openstack-mogan
Please let me know either here on the ML or with a comment on the review linked above if you have a reason to continue logging any of these channels. I'd like to merge it later this week if possible. Thanks! -- Jeremy Stanley
— Slawek Kaplonski Senior software engineer Red Hat
On Tue, 17 Sep 2019 at 08:28, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
On 17 Sep 2019, at 07:11, Akihiro Motoki amotoki@gmail.com wrote:
On Tue, Sep 17, 2019 at 7:20 AM Jeremy Stanley fungi@yuggoth.org
wrote:
Freenode imposes a hard limit of 120 simultaneously joined channels for any single account. We've once again reached that limit with our channel-logging meetbot. As a quick measure, I've proposed a bit of cleanup: https://review.opendev.org/682500
Analysis of IRC channel logs indicates the following have seen 5 or fewer non-bot comments posted in the past 12 months and are likely of no value to continue logging:
5 #openstack-vpnaas
I would like to add the following channels to this list in addition to #openstack-vpnaas. This is what I think recently but I haven't discussed it yet with the
team.
- openstack-fwaas
- networking-sfc
Ha, I didn’t even know that such channels exists. And from what I can say, if there are any topics related to such stadium projects, we are discussing them on #openstack-neutron channel usually. IMHO we can remove them too.
Yes #networking-sfc was created almost 3 years ago when activity was higher, it was also used at some point for IRC meetings. These meetings have stopped and the channel is really quiet now. So it sounds like a good time to formalize the folding back in neutron chan
I see only 5~20 members in these channels constantly. Developments in FWaaS and SFC are not so active, so I don't see a good reason to have a separate channel. They can be merged into the main neutron channel #openstack-neutron.
Is there any guideline on how to guide users to migrate a channel to another channel?
Thanks, Akihiro
2 #swift3 2 #openstack-ko 1 #openstack-deployment 1 #midonet 0 #openstack-valet 0 #openstack-swg 0 #openstack-mogan
Please let me know either here on the ML or with a comment on the review linked above if you have a reason to continue logging any of these channels. I'd like to merge it later this week if possible. Thanks! -- Jeremy Stanley
— Slawek Kaplonski Senior software engineer Red Hat
Thanks for the feedback. I proposed a patch to stop gerrit notifications to #openstack-fwaas, #openstack-vpnaas and #networking-sfc based on this thread. https://review.opendev.org/682771
On Tue, Sep 17, 2019 at 9:45 PM Bernard Cafarelli bcafarel@redhat.com wrote:
On Tue, 17 Sep 2019 at 08:28, Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
On 17 Sep 2019, at 07:11, Akihiro Motoki amotoki@gmail.com wrote:
On Tue, Sep 17, 2019 at 7:20 AM Jeremy Stanley fungi@yuggoth.org wrote:
Freenode imposes a hard limit of 120 simultaneously joined channels for any single account. We've once again reached that limit with our channel-logging meetbot. As a quick measure, I've proposed a bit of cleanup: https://review.opendev.org/682500
Analysis of IRC channel logs indicates the following have seen 5 or fewer non-bot comments posted in the past 12 months and are likely of no value to continue logging:
5 #openstack-vpnaas
I would like to add the following channels to this list in addition to #openstack-vpnaas. This is what I think recently but I haven't discussed it yet with the team.
- openstack-fwaas
- networking-sfc
Ha, I didn’t even know that such channels exists. And from what I can say, if there are any topics related to such stadium projects, we are discussing them on #openstack-neutron channel usually. IMHO we can remove them too.
Yes #networking-sfc was created almost 3 years ago when activity was higher, it was also used at some point for IRC meetings. These meetings have stopped and the channel is really quiet now. So it sounds like a good time to formalize the folding back in neutron chan
I see only 5~20 members in these channels constantly. Developments in FWaaS and SFC are not so active, so I don't see a good reason to have a separate channel. They can be merged into the main neutron channel #openstack-neutron.
Is there any guideline on how to guide users to migrate a channel to another channel?
Thanks, Akihiro
2 #swift3 2 #openstack-ko 1 #openstack-deployment 1 #midonet 0 #openstack-valet 0 #openstack-swg 0 #openstack-mogan
Please let me know either here on the ML or with a comment on the review linked above if you have a reason to continue logging any of these channels. I'd like to merge it later this week if possible. Thanks! -- Jeremy Stanley
— Slawek Kaplonski Senior software engineer Red Hat
-- Bernard Cafarelli
On 18/09/2019 03.44, Akihiro Motoki wrote:
Thanks for the feedback. I proposed a patch to stop gerrit notifications to #openstack-fwaas, #openstack-vpnaas and #networking-sfc based on this thread. https://review.opendev.org/682771
Do you want to retire the channels completely?
Then remove from logging - a change to opendev/system-config - and remove accessbot as well.
Then, you can follow https://docs.openstack.org/infra/system-config/irc.html#renaming-an-irc-chan...
Andreas
On Wed, Sep 18, 2019 at 3:17 PM Andreas Jaeger aj@suse.com wrote:
On 18/09/2019 03.44, Akihiro Motoki wrote:
Thanks for the feedback. I proposed a patch to stop gerrit notifications to #openstack-fwaas, #openstack-vpnaas and #networking-sfc based on this thread. https://review.opendev.org/682771
Do you want to retire the channels completely?
Then remove from logging - a change to opendev/system-config - and remove accessbot as well.
Then, you can follow https://docs.openstack.org/infra/system-config/irc.html#renaming-an-irc-chan...
Yes, we can retire these channels.
My understanding on the step of this retirement is: - the first step is to stop notifications and my patch will address it. - Regarding the logging and accessbot, I think we can cover it by Jeremy's change. (I think this is what you mentioned on opendev/system-config in my patch) - The renaming process can be done only by the infra root, so what I can do is to ask it to the infra root. All logins to these three channels can be redirected to #openstack-neutron channel.
I don't think we need to rush it. I just try to move this forward gradually.
Akihiro Motoki (amotoki)
Andreas
Andreas Jaeger aj@suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg GF: Felix Imendörffer; HRB 247165 (AG München) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 2019-09-18 08:17:52 +0200 (+0200), Andreas Jaeger wrote: [...]
remove accessbot as well.
[...]
As we discussed in IRC, I don't think removal from accessbot is especially necessary. The accessbot simply evaluates chanserv permissions and then updates them if needed (it never actually joins any channels), so having extra channels in its configuration isn't really a problem and can simplify things if situations change and people decide they want to go back to using those channels in the future.
participants (5)
-
Akihiro Motoki
-
Andreas Jaeger
-
Bernard Cafarelli
-
Jeremy Stanley
-
Slawek Kaplonski