Wednesday, 2020-06-24

*** jamesmcarthur has joined #openstack-tc00:30
*** jamesmcarthur has quit IRC00:50
*** jamesmcarthur has joined #openstack-tc00:51
*** jamesmcarthur has quit IRC00:58
*** diablo_rojo has quit IRC01:01
mnasero/01:03
gmanno/01:03
*** jamesmcarthur has joined #openstack-tc01:14
*** jamesmcarthur has quit IRC01:23
*** markvoelker has joined #openstack-tc01:30
*** markvoelker has quit IRC01:35
*** jamesmcarthur has joined #openstack-tc01:42
*** jamesmcarthur has quit IRC01:50
*** tetsuro has joined #openstack-tc01:52
*** jamesmcarthur has joined #openstack-tc02:11
*** jamesmcarthur has quit IRC02:11
*** jamesmcarthur has joined #openstack-tc02:11
*** camelCaser has quit IRC02:23
*** camelCaser has joined #openstack-tc02:25
*** jamesmcarthur has quit IRC02:57
*** jamesmcarthur has joined #openstack-tc03:02
*** markvoelker has joined #openstack-tc03:31
*** markvoelker has quit IRC03:36
*** jamesmcarthur has quit IRC04:31
*** evrardjp has quit IRC04:33
*** evrardjp has joined #openstack-tc04:33
*** markvoelker has joined #openstack-tc04:34
*** jamesmcarthur has joined #openstack-tc04:37
*** markvoelker has quit IRC04:39
*** jamesmcarthur has quit IRC04:58
*** jamesmcarthur has joined #openstack-tc04:58
*** dklyle has quit IRC04:58
*** jamesmcarthur has quit IRC05:04
*** jamesmcarthur has joined #openstack-tc05:33
*** jamesmcarthur has quit IRC05:42
*** slaweq_ has joined #openstack-tc06:12
*** jamesmcarthur has joined #openstack-tc06:13
*** slaweq has quit IRC06:13
*** markvoelker has joined #openstack-tc06:14
*** markvoelker has quit IRC06:20
*** jamesmcarthur has quit IRC06:22
*** ralonsoh has joined #openstack-tc06:55
*** rpittau|afk is now known as rpittau06:57
slaweq_njohnston: sorry, I wasn't there yesterday. neutron-vpnaas isn't retired and we don't consider it to be retired for now07:27
*** AJaeger has joined #openstack-tc07:30
AJaegermnaser: for your retirement email, I suggest to differentiate these two: 1) Repos retired and dead - but somehow incorrectly.07:31
AJaeger2) Repos retired but still alive07:31
AJaegerFor example, python-dracclient is in legacy.yaml but still alive, so might get a different treatment than the others.07:32
AJaegerSo, check which of these are still active: dragonflow  networking-l2gw networking-l2gw-tempest-plugin networking-onos openstack-ux python-dracclient solum-infra-guestagent transparency-policy - and tread them separate.07:32
AJaegerThese repos went not through the retirement process as all. smcginnis just started it for dragonflow but it needs done for the rest as well.07:35
AJaegermnaser: I added a section in the etherpad07:37
AJaegermnaser: your list is also wrong, having README.rst is the right thing07:38
AJaegermnaser: I would not add .gitreview file just for the fun of it. It's good for deprecating (only stopping master work) but not needed for these, so I suggest to cut down your list and accept if .gitreview is not in the repo.07:41
*** dmellado has joined #openstack-tc07:43
*** belmoreira has joined #openstack-tc07:48
*** tosky has joined #openstack-tc07:49
*** slaweq_ is now known as slaweq07:49
*** belmoreira has quit IRC08:08
*** belmoreira has joined #openstack-tc08:08
*** markvoelker has joined #openstack-tc08:16
*** jamesmcarthur has joined #openstack-tc08:18
*** markvoelker has quit IRC08:21
*** jamesmcarthur has quit IRC08:23
*** e0ne has joined #openstack-tc09:23
*** tkajinam has quit IRC10:03
openstackgerritAurelien Lourot proposed openstack/governance master: Add Neutron Arista plugin charm to OpenStack charms  https://review.opendev.org/73773410:03
*** markvoelker has joined #openstack-tc10:05
*** markvoelker has quit IRC10:09
*** rpittau is now known as rpittau|bbl10:11
*** jamesmcarthur has joined #openstack-tc10:20
*** jamesmcarthur has quit IRC10:32
*** markvoelker has joined #openstack-tc11:55
*** markvoelker has quit IRC11:59
*** rpittau|bbl is now known as rpittau12:13
*** jamesmcarthur has joined #openstack-tc12:29
*** jamesmcarthur has quit IRC12:34
jungleboyjo/12:58
mnaserAJaeger: my list is a starter for something to work on... I think if we’re gonna normalize it all might just as well as do it. We tell people not to drop gitreview file...13:07
smcginnisWe don't want to have to go back and update everything the next time we decide to change guidance on this though. I think the ones that were done before we made that a recommendation, we should just leave them as they are.13:20
knikollao/13:24
knikollathanks for the feedback, i will update the draft based on the received feedback.13:25
AJaegermnaser: we initially told them to drop gitreview and changed that later. And .gitreview missing is not a problem with a complete retired repo, this is crucial for deprecation (where you have master retired but still stable changes)13:28
mnaserAJaeger: my biggest thing is how do we make sure we properly test that everything is properly retired.. and I’m also willing to make sure the work is done :x13:29
mnaserI feel like I’m getting a lot of pushback trying to drive this when it really doesn’t affect much more the acl change13:30
AJaegermnaser: if you want to do it, go for it - I think it is easier to allow a .gitreview missing on older repos. Just hardcode those repos.13:30
mnaserAJaeger: fair enough, if we’re going to soft retire them, we can do that later or change our minds13:31
AJaegersoft retire? I'm only talking about repos like fairy-slipper that are fully retired but had the .gitreview removed.13:35
AJaegermnaser: did you get my point on the two different kind of repos above?13:35
smcginnisWell, the other issue if we make updates is we no longer have the consistent pattern of telling folks to "git reset HEAD~1" to get the last content.13:36
smcginnisAnd the last updated date would be recent, even if the project hasn't really been touched for years.13:36
AJaegersmcginnis: yeah, you would need to update README.rst to say ~213:36
smcginnisJust seems like there are more important things to be spending time on. Like making sure the ones that are retired have actually been retired.13:37
AJaegersmcginnis, agreed, my priority would be to look at these first: dragonflow  networking-l2gw networking-l2gw-tempest-plugin networking-onos openstack-ux python-dracclient solum-infra-guestagent transparency-policy13:38
AJaeger... and I know you started already with dragonflow, smcginnis13:38
smcginnisI can try to get to some of the others soon.13:49
*** dklyle has joined #openstack-tc13:49
smcginnisNeed to figure out what should happen with python-dracclient. That's actually very active and in use in Ironic. It just left ironic as an official repo, but never was moved to a new home.13:49
AJaegersmcginnis: according to the TC resolution: Retire in openstack and the team can recreate in another namespace like x.13:51
mnaserAJaeger: soft retire as in we can still propose changes to them if need-be13:51
mnaserbut yes, i see the point about those projects who are 'retired' but still have content as a priority.13:52
AJaegermnaser: for those retired ones, do it once and be done with it ;)13:52
mnaseri've taken 3 different approaches so far which have all taken a signficant chunk of time to do only to be told "no"13:53
mnaserand now if i go and add an exception list to the validate legacy job, i feel like a) sucks we have a list of 'badly retired projects' and b) who knows if that doesn't make people happy :)13:53
AJaegermnaser: 'badly retired projects' is in the eye of the beholder, repos that removed .gitreview were properly retired at the time of retirement. And then we changed policies. The same with README.md vs README.rst, that was updated a week ago.14:06
AJaegerSo, I would not speak about "badly retired" but just say: WE changed policies and those confirmed to the previous one but not the new one...14:06
openstackgerritAurelien Lourot proposed openstack/governance master: Add Neutron Arista plugin charm to OpenStack charms  https://review.opendev.org/73773414:11
*** jamesmcarthur has joined #openstack-tc14:15
gmanno/14:43
mnaserAJaeger: sorry, poor usage of words.14:44
AJaegernp14:44
*** jamesmcarthur has quit IRC14:54
*** jamesmcarthur has joined #openstack-tc14:54
clarkbAJaeger: yes that change in needs is why I'm suggesting we should switch openstack retirements to a softer retirement15:00
clarkbAJaeger: allow a small group to push edits and keep the project open in gerrit15:00
clarkbbecause that is the underlying issue. We did what was correct for some time ago and now it needs to change. Some time in the future it seems likely we'll repeat this history15:00
smcginnisIf we keep retired projects open, then we are going to get all those mass script driveby's to it.15:11
clarkbsmcginnis: we can restrict push access to a small group15:11
smcginnisAnd our instructions on how to revert back to the last working code will constantly be needing to be updated along with everything too.15:11
clarkbsmcginnis: only if you continue to make changes (which is already the case)15:11
clarkbto be claer I am on team let retired projects be retired and move on. But I understand the need/use case here and i think a softer retirement fits that need better than what we have now15:12
*** jamesmcarthur has quit IRC15:12
clarkbwhat we have now is incredibly clunky if we accept that retired projects may need to be modified every few years to address some issue15:13
*** jamesmcarthur has joined #openstack-tc15:13
gmannmnaser: i am starting the cleanup for networking-l2gw-tempest-plugin (and its project repo) which has been in tempest plugins blacklist - https://docs.openstack.org/tempest/latest/plugins/plugin-registry#blacklisted-plugins15:19
gmanni am iterating on other plugins also which are in blacklist for long and under openstack/ namespace. 1. if it is retired then move to other namespace otherwise 3. start the retirement as they are failing and no one cares15:20
*** jamesmcarthur has quit IRC15:23
gmannslaweq: any objection on moving  networking-l2gw-tempest-plugin ,networking-l2gw and also networking-onos from openstack/ namespace. if there is active them then can fork it to continue the development under x/ or anyother namespace. all these repo were retired in ocata - https://review.opendev.org/#/c/392010/215:31
slaweqgmann: those projects aren't neutron stadium AFAIK15:32
gmannnetworking-l2gw-tempest-plugin was a late entry in openstack/ namespace without being a official repo anytime.15:32
clarkbgmann: note aiui you don't move them from the openstack/ namespace15:32
clarkbgmann: you retire them in the openstack/ namespace and give people option of forking elsewhere15:32
gmannclarkb: yeah.15:32
gmannmove away i mean retire and then active can fork if they want15:32
gmannslaweq: from 392010, they are not stadium anymore but i want to check in case you have any plan for them?15:33
gmannplan to add in stadium or any active team under neutron maintaining those15:33
slaweqgmann: I don't have any plans15:34
gmannok15:34
slaweqand I don't think that anybody in our team wants to do anything with it15:34
gmannslaweq: ok, thanks.15:34
slaweqyw15:34
fungismcginnis: mnaser's proposed acl change for retired openstack namespace repos prevents anyone besides the tc from pushing changes for review15:45
smcginnisYeah. That part is good.15:45
fungiso should avoid the usual drive-by noise unless tc members are generating it ;)15:45
smcginnisStill would prefer to leave retired projects retired though.15:46
*** ricolin has joined #openstack-tc15:55
fungialso i have a feeling we need to sync up with the ironic team (as former caretakers) and the current maintainers of openstack/python-dracclient so they at least know what's going on before we retire them. looks like they've still got ongoing development and are tagging releases and publishing to pypi through that repo, and the github mirror for it is still intact too15:56
AJaegerfungi: there's no github mirroring setup for dracclient.15:57
AJaegerfungi: I agree, dracclient is "special"15:57
fungiAJaeger: yeah, the mirroring is no longer happening, but there's still an abandoned mirror of it in openstack's github org as of when we stopped replication from gerrit15:58
clarkband there are many recent commits and releases15:58
gmannor if ironic team maintaining than it is good to bring it under governance15:58
fungiseems like it's probably just devs at dell maintaining it, not sure how involved in the rest of ironic they are15:59
smcginnisThey are pretty involved.16:00
smcginnisI'm trying to work with the team to figure out the best way forward.16:00
fungihttps://review.openstack.org/392685 "python-dracclient is intended to only interact with a single vendor's hardware, which the ironic team decided we no longer wish to maintain in ironic's governance. It will continue to be maintained outside of the ironic governance."16:01
smcginnisThe options I've given the team, that we would need to discuss here or in #opendev, would be to see if the community is open to accepting some sort of Dell focused SIG (kind of along the lines of PowerVM and Windows SIGs), move to the x/ namespace, see if OpenDev is willing to host a dell/ namespace, or move out of the community completely.16:03
smcginnisThat last one is the least attractive to me since I believe there is some cross gating currently with ironic patches.16:04
fungilooks like the removal for that repo coincided with this addition/clarification in ironic's deliverable policy: "must not be intended for use with only a single vendor’s hardware" https://docs.openstack.org/ironic/latest/contributor/governance.html#what-belongs-in-ironic-governance16:04
openstackgerritZane Bitter proposed openstack/governance master: Create starter-kit:kubernetes-in-virt tag  https://review.opendev.org/73636916:12
fungismcginnis: from a namespace perspective, i don't think opendev would have any problem hosting a "dell/" namespace (we have "limestone/" and "vexxhost/" for example)16:14
fungismcginnis: if there are reservations about that name, i would expect them to come from dell legal, if anywhere16:15
smcginnisI may know a guy. :)16:18
smcginnisThat really was my recommendation out of the options I gave.16:18
smcginnisSIG would be nice to be recognized officially and to be able to publish to docs.o.o. But not sure if that would be perceived well since it would be so vendor focused.16:18
smcginnisThey would like others involved though, so a nice thing about that would be to make that a little easier.16:19
smcginnisBut still a vendor controlled thing by its nature, so not really a right fit I think.16:19
*** markvoelker has joined #openstack-tc16:24
*** markvoelker has quit IRC16:28
*** rpittau is now known as rpittau|afk16:41
fungiwe've had this discussion for years, unfortunately. the push for vendor-specific "driver projects" as an alternative allowance in governance never got much traction16:41
fungiwe also now have inherently single-affiliation services (just this week one ptl told me they were their project's only contributor) so seems like we wouldn't even need a special allowance16:43
*** markvoelker has joined #openstack-tc17:09
*** markvoelker has quit IRC17:14
*** ricolin has quit IRC17:20
*** e0ne has quit IRC17:42
*** diablo_rojo has joined #openstack-tc18:23
*** belmoreira has quit IRC18:33
*** irclogbot_0 has quit IRC18:34
*** irclogbot_2 has joined #openstack-tc18:38
*** markvoelker has joined #openstack-tc19:10
*** markvoelker has quit IRC19:15
*** ralonsoh has quit IRC19:26
*** markvoelker has joined #openstack-tc19:33
*** markvoelker has quit IRC19:38
*** markvoelker has joined #openstack-tc19:59
*** markvoelker has quit IRC20:04
*** belmoreira has joined #openstack-tc20:21
*** belmoreira has quit IRC20:26
*** slaweq has quit IRC21:36
*** slaweq has joined #openstack-tc21:46
*** slaweq has quit IRC21:52
*** markvoelker has joined #openstack-tc22:00
*** markvoelker has quit IRC22:05
*** markvoelker has joined #openstack-tc22:49
*** tkajinam has joined #openstack-tc22:51
*** markvoelker has quit IRC22:54
*** cloudnull has quit IRC22:56
*** tosky has quit IRC23:03
*** markvoelker has joined #openstack-tc23:37
*** markvoelker has quit IRC23:47

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!