Monday, 2019-05-13

*** jamesmcarthur has joined #openstack-tc00:24
*** altlogbot_1 has quit IRC00:50
*** altlogbot_3 has joined #openstack-tc00:56
*** zhurong has joined #openstack-tc01:01
*** jamesmcarthur has quit IRC01:08
*** jamesmcarthur has joined #openstack-tc01:08
*** jamesmcarthur has quit IRC01:24
*** jamesmcarthur has joined #openstack-tc01:54
*** jamesmcarthur has quit IRC01:59
*** jamesmcarthur has joined #openstack-tc01:59
*** ricolin has joined #openstack-tc02:22
*** ricolin_ has joined #openstack-tc02:31
*** jamesmcarthur has quit IRC02:31
*** ricolin has quit IRC02:33
*** jamesmcarthur has joined #openstack-tc02:34
*** jamesmcarthur has quit IRC02:41
*** jamesmcarthur has joined #openstack-tc02:43
*** jamesmcarthur has quit IRC02:57
*** whoami-rajat has joined #openstack-tc03:05
*** zhurong has quit IRC03:31
*** ricolin_ has quit IRC03:44
*** david-lyle is now known as dklyle03:58
*** ricolin_ has joined #openstack-tc04:03
*** dklyle has quit IRC04:03
*** Luzi has joined #openstack-tc04:42
*** jaosorior has joined #openstack-tc04:43
*** diablo_rojo has joined #openstack-tc04:49
*** jaosorior has quit IRC04:52
*** tjgresha has quit IRC04:57
*** tjgresha has joined #openstack-tc04:57
*** jamesmcarthur has joined #openstack-tc04:58
*** jaosorior has joined #openstack-tc05:00
*** jamesmcarthur has quit IRC05:03
*** zhurong has joined #openstack-tc05:11
*** e0ne has joined #openstack-tc05:16
*** diablo_rojo has quit IRC05:16
*** ricolin_ has quit IRC05:31
*** ricolin has joined #openstack-tc05:36
*** e0ne has quit IRC06:29
*** sarob has joined #openstack-tc06:31
*** sarob has quit IRC07:04
ttxdhellmann: probably all repos. They use it more as a data corpus on code reviews than as a study of openstack07:14
*** jpich has joined #openstack-tc07:51
*** ricolin has quit IRC08:15
*** ricolin has joined #openstack-tc08:15
*** ricolin has quit IRC08:19
*** ricolin has joined #openstack-tc08:20
*** ricolin has quit IRC08:21
*** e0ne has joined #openstack-tc08:32
*** wxy-xiyuan has joined #openstack-tc09:39
evrardjpfungi: could you have a look at https://review.opendev.org/#/c/657154 ?09:48
fungievrardjp: sorry, still on vacation but are you asking about the syntax error in the zuul comments? it's saying that either openstack/pyeclib is misnamed or is waiting on a rename. right now we only have a x/pyeclib repository11:54
evrardjpfungi: oh sorry, go on with vacation-ing then :)11:56
evrardjpfungi: I think the process for renaming needs clarification (for example importing new repos require said repos to not have zuul files in it, wondering if that applies here), and I thought you would be well placed to handle this.11:57
evrardjpbut there is nothign urgent there afaik11:57
fungiis it an import of a new repo or are they talking about the existing x/pyeclib repo?11:58
evrardjpexisting11:58
fungithat's what i thought11:59
evrardjpas said above, I think the rename process could be improved, I can't really help right there.11:59
evrardjpbut as said above too, happy vacation-ing, let's resume this later :)12:00
fungiyou can't exercise a change to zuul configuration in openstack/project-config (such as a rename) in a check job because that's a trusted config repo12:00
evrardjpyes, so does the repo being the target of a rename should remove all the possible jobs contained in it, or defined in the project-config?12:01
evrardjpor am I completely confused here?12:02
fungino, just need to wait for the next rename maintenance window before we'll be able to actually rename it to openstack/pyeclib because that also requires simultaneous changes in gerrit, gitea, possibly storyboard, et cetera12:02
evrardjpI understand now.12:03
fungiproject renames (including moving a repository between namespaces) requires downtime for our systems12:03
evrardjpwhen this window will happen, the code will be ready for move, the governance change will pass then.12:03
evrardjpmakes sense.12:05
fungiyes, unless they want to add it in governance as x/pyeclib and then update it in governance after the rename12:05
evrardjpIt was the case before, moving to opendev and gitea didn't magically change a whole stack :)12:05
evrardjpfungi: got it12:06
evrardjpthanks for the clarification!12:06
fungii figured the contention on that was going to be around the fact that liberasurecode is in c and pyeclib links it (so is not "pure" python)12:07
evrardjpoh12:08
evrardjpI hope the language will not be a reason for contention. But that's probably a longer conversation...12:09
fungihttps://opendev.org/x/liberasurecode/src/branch/master/src12:09
fungii personally like c, but i think it'll likely be the first official openstack component in c, so no idea if that means we need new additions to the supported runtimes and pti for c-based projects12:10
*** jamesmcarthur has joined #openstack-tc12:12
*** jamesmcarthur has quit IRC12:31
*** ijolliffe has joined #openstack-tc12:41
*** jamesmcarthur has joined #openstack-tc12:49
*** dirk has quit IRC12:58
*** wxy-xiyuan has quit IRC12:59
*** aprice has quit IRC12:59
scasthe biggest point of contention someone will have is the need to bake in the build toolchain. let us not forget about the venerable phk's musing on the notion: https://queue.acm.org/detail.cfm?id=234925712:59
*** aprice has joined #openstack-tc12:59
scasfor airgapped scenarios, the toolchain is usually stripped out12:59
*** serverascode has quit IRC13:00
*** persia has quit IRC13:00
*** persia has joined #openstack-tc13:00
*** dirk has joined #openstack-tc13:01
*** serverascode has joined #openstack-tc13:02
scasone of the more choice nuggets for a reminder about open source: the software in the FreeBSD ports collection contains at least 1,342 copied and pasted cryptographic algorithms13:06
scasI consider both projects, this one and FreeBSD, to be similar in ideals. both serve similar niches, just in different capacities13:06
*** Luzi has quit IRC13:10
scasI'm also reminded of the now-dead effort to bring FreeBSD support to OpenStack. both camps don't see eye to eye, though both would benefit from mutual cross-pollenation. OpenStack is a bazaar-developed-like-a-cathedral, and FreeBSD development is very cathedral-like beyond ports13:11
scasbut I digress13:11
*** wxy-xiyuan has joined #openstack-tc13:14
*** jamesmcarthur has quit IRC13:26
fungiyeah, i was hopeful for better *bsd penetration in our ecosystem13:35
fungisimilarly disappointed that debian is dropping its kfreebsd kernel architecture officially and moving it to ports for buster13:36
fungitechnically the oracle attempts to support solaris/illumos/whatever in openstack would have been another *bsd13:37
fungialbeit a systemvish bsd13:37
fungi(that was meant to read systemv-ish, not a reference to our lost compatriot vish)13:38
*** flaper87 has quit IRC13:45
*** jamesmcarthur has joined #openstack-tc13:46
*** flaper87 has joined #openstack-tc13:55
*** flaper87 has quit IRC13:55
scaswith my weathered eye, I see why there was less enthusiasm. no docker support, so who the hell wants to try to run kubernetes on /that/?13:56
*** flaper87 has joined #openstack-tc13:56
scasthe BSD answer is to use jails, but nobody likes jails outside of BSD fans13:57
scasnot to mention, the name isn't catchy and there's no fun logo13:57
scasof course kids are going to thumb their noses at it13:58
* scas drinks some water with his salt13:58
scasalso, we don't need the entire golang distribution to be installed for what amounts to some shell scripts and some judicious C /oldman14:00
scasI'd suggest that Kata be more of a re-entry point to BSD to see if perhaps OpenStack itself could have more of a go. get an actual container runtime and see if it picks up would be my off-the-napkin idea14:02
scasthe lack of a container runtime put BSD back in the playing field when it had been working on a revival in the server area. it's now more of an embedded niche, with some facets of other things it can do14:04
scasparticularly FreeBSD with its now-dead Docker support14:04
scasy'all know dtrace would be pretty hot to have in the toolbelt :D14:07
*** gmann has joined #openstack-tc14:07
*** gmann is now known as gmann_pto14:07
fungii'd love to have openbsd routers with pf and relayd in an openstack deployment, but chances of that ever coming to pass are slim14:11
fungii know of no better platform for integrated stateful filtering, layer-7 load balancing and redundant ipsec14:12
scasof course. that would be madness.14:16
scasit would almost be like people working together, but we all know it'd wind up being like one person14:17
scasthat said, a startup in the right nexus could be dangerous.14:19
*** mriedem has joined #openstack-tc14:25
*** jamesmcarthur_ has joined #openstack-tc14:39
*** jamesmcarthur has quit IRC14:43
*** cmorpheus is now known as cmurphy15:40
*** dtantsur is now known as dtantsur|afk16:23
*** whoami-rajat has quit IRC16:31
*** whoami-rajat has joined #openstack-tc16:36
*** e0ne has quit IRC16:42
*** jpich has quit IRC16:46
*** diablo_rojo has joined #openstack-tc17:08
*** jroll has quit IRC17:34
*** jroll has joined #openstack-tc17:35
*** jamesmcarthur_ has quit IRC17:58
*** dklyle has joined #openstack-tc17:59
*** jamesmcarthur has joined #openstack-tc18:03
*** jamesmcarthur has quit IRC18:03
*** dklyle has quit IRC18:08
*** e0ne has joined #openstack-tc18:17
*** dklyle has joined #openstack-tc18:23
*** jamesmcarthur has joined #openstack-tc18:31
*** dklyle has quit IRC18:34
*** jamesmcarthur has quit IRC18:49
*** e0ne has quit IRC18:54
*** jamesmcarthur has joined #openstack-tc19:07
*** gmann_pto has quit IRC19:33
*** persia has quit IRC19:35
*** persia has joined #openstack-tc19:36
*** diablo_rojo has quit IRC19:49
*** diablo_rojo has joined #openstack-tc19:53
*** e0ne has joined #openstack-tc20:14
*** e0ne has quit IRC20:26
*** openstackgerrit has quit IRC21:09
*** dklyle has joined #openstack-tc21:13
*** dklyle has quit IRC21:24
*** ijolliffe has quit IRC21:29
*** jamesmcarthur has quit IRC21:40
*** whoami-rajat has quit IRC21:41
*** mriedem is now known as mriedem_afk21:53
*** dklyle has joined #openstack-tc23:18
*** mriedem_afk has quit IRC23:31

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!