Tuesday, 2019-01-29

*** edmondsw has quit IRC00:38
*** jamesmcarthur has joined #openstack-tc01:04
*** jamesmcarthur has quit IRC01:09
*** tosky has quit IRC01:34
*** lbragstad has quit IRC01:35
*** ricolin_ has joined #openstack-tc02:01
*** whoami-rajat has joined #openstack-tc02:37
*** jamesmcarthur has joined #openstack-tc03:23
*** jamesmcarthur has joined #openstack-tc03:24
*** lbragstad has joined #openstack-tc03:47
*** ricolin_ has quit IRC04:11
*** ricolin has joined #openstack-tc04:11
*** diablo_rojo has quit IRC04:12
*** jamesmcarthur has quit IRC04:15
*** jamesmcarthur has joined #openstack-tc04:16
*** jamesmcarthur has quit IRC04:21
*** spsurya has joined #openstack-tc05:05
*** edmondsw has joined #openstack-tc06:19
*** jamesmcarthur has joined #openstack-tc06:24
*** jamesmcarthur has quit IRC06:28
*** Luzi has joined #openstack-tc06:56
*** e0ne has joined #openstack-tc07:59
openstackgerritGhanshyam Mann proposed openstack/governance master: Add Version Based Feature Discovery in Technical Vision  https://review.openstack.org/62151608:30
ttxICYMI: K8s introduced a concept of Working Group a few months ago -- temporary in nature, clear objective / disband criteria, does not own code. https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md08:42
*** tosky has joined #openstack-tc08:42
ttxExample WG: dims's effort to move project infra off Google and into CNCF / the project: https://github.com/kubernetes/community/tree/master/wg-k8s-infra08:43
*** jpich has joined #openstack-tc09:01
evrardjpo/09:03
gmanno/09:04
gmannTC Office hour started..09:04
gmanntc-members updated the patch for feature discover in vision doc- https://review.openstack.org/#/c/621516/09:06
gmannevrardjp: ^^09:06
evrardjp:)09:06
ttxo/09:06
*** ricolin has quit IRC09:07
evrardjpttx: what's your take on the k8s wg?09:19
ttxyou mean their concept of WGs, or that specific k8s-infra WG?09:24
ttxI really like the idea of separating transient from permanent groups09:25
ttxWe've been lacking a clear terminology there -- we have called them pop-up teams at one point but that did not really caught on09:25
ttxand we have working groups at the board and the UC level so reusing their naming is a bit hard09:25
gmannttx: but k8s-infra still needs to own infra related code right so that as WG fit well ?09:26
ttxgmann: I don't think they plan to do infra as code09:28
ttxbut then dims can probably explain better09:28
gmannok.09:28
ttx(currently they are using a bunch of hosts on GCE owned by Google with only Google people having access)09:29
gmannyeah.09:29
cmurphyhaving something formal for managing specific cross project long term deliverables or community wide initiatives would help a lot i think09:32
ttxcmurphy: I'll wait for dims to comment based on his experience there... then I can start a thread to assess support for the idea09:33
*** dtantsur|afk is now known as dtantsur09:35
*** zaneb has quit IRC10:16
*** ssbarnea|bkp2 has quit IRC11:01
*** ssbarnea|rover has joined #openstack-tc11:03
*** cdent has joined #openstack-tc12:08
*** fdegir is now known as fdegir_12:10
*** jamesmcarthur has joined #openstack-tc12:24
*** jamesmcarthur has quit IRC12:29
*** fdegir has joined #openstack-tc12:32
*** fdegir_ has left #openstack-tc12:32
*** cdent has quit IRC12:36
dimsgmann : the WG does it work through various SIGs that it is related to. the SIGs own the repos12:56
dimsthink of WG as cross cutting ...12:56
dimsat some point the infra WG will dissolve into something more permanent ... we don't yet know what that will be.12:57
dimscmurphy : +1 on "something formal for managing specific cross project long term deliverables or community wide initiatives"12:58
*** cdent has joined #openstack-tc13:09
*** e0ne has quit IRC13:13
*** mriedem has joined #openstack-tc13:28
*** e0ne has joined #openstack-tc13:29
*** e0ne has quit IRC14:51
*** e0ne has joined #openstack-tc14:54
*** Luzi has quit IRC15:05
*** openstackgerrit has quit IRC15:51
*** jamesmcarthur has joined #openstack-tc16:16
*** jamesmcarthur has quit IRC16:21
*** jamesmcarthur has joined #openstack-tc16:23
*** fdegir has quit IRC16:26
*** e0ne has quit IRC16:31
*** jpich has quit IRC17:32
ttxdims: ok I can start a thread on that to see what people think17:42
*** e0ne has joined #openstack-tc17:46
clarkbI'll mention it here too as it is a broad audience. pycodestyle 2.5.0 released a few hours ago and has blown up the openstack integrated gate17:54
smcginnisOh joy.17:59
*** diablo_rojo has joined #openstack-tc18:01
*** jamesmcarthur has quit IRC18:06
*** jamesmcarthur has joined #openstack-tc18:08
*** openstackgerrit has joined #openstack-tc18:35
openstackgerritIvan Kolodyazhny proposed openstack/governance master: Add Horizon to 'Help most needed' list  https://review.openstack.org/63379818:35
*** diablo_rojo has quit IRC18:35
*** bsilverman has joined #openstack-tc18:51
*** e0ne has quit IRC18:53
bsilvermanSo, there's LFEdge with Akraino, EdgeX and Home Edge, and there's the OSF with StarlingX, is anyone looking at bridging this?18:54
bsilvermananyone from the OSF, that is.18:55
clarkbildikov: ^19:01
ildikovo/19:02
ildikovand yes19:02
ildikovbsilverman: EdgeX is now under the LFEdge umbrella and both StarlingX and the Edge WG under OSF are  seeking ways to collaborate19:03
ildikovbsilverman: if you have a good use case in mind or further integration points we can work on to tackle then it would be great to chat about it19:04
ildikovbsilverman: we are also continuously reaching out to further groups to collaborate where it makes sense19:04
ildikovclarkb: thanks!19:05
bsilvermanI'm just wondering if each of these groups are headed towards a common goal, yet, are separated by governance, yet, joined in other areas of collaboration.19:05
ildikovedge is not really a well defined area at this point19:06
ildikovand even when we will have more use cases that we can detail out it is still a very large scope for one group to tackle19:06
*** whoami-rajat has quit IRC19:07
bsilvermanildikov: True, I'm just interested to see if these edge groups start trying to create their own open edge infrastructure managers while OpenStack is already here.19:07
*** e0ne has joined #openstack-tc19:07
bsilvermanildikov: I'm already seeing it with the container/k8s crowd, trying to figure out how to manage bare metal and VMs for containers by cobbling together a bunch of open source solutions and writing their own integration when OpenStack already has most of what they need solved.19:09
ildikovso in that sense having this many entities can help with understanding better the different layers from hardware up to the workloads and then consolidate once we have a better understanding19:09
ildikovsorry, my wifi decided to stop working... :/19:10
bsilvermanildikov: Yes, if they have workload management and deployment tools they are developing for general use cases, great, but when it comes to infrastructure or private cloud underlay, the OSF could help them.19:11
ildikovbsilverman: yeah, I understand your point and we are continuously looking into publishing case studies and showing that OpenStack services have a well-defined space in the container space as well19:11
ildikovbsilverman: and we do where we can19:11
ildikovbsilverman: it's a lot of repeating ourselves in the industry at this point as I see it19:12
ildikovbsilverman: and it's always the era of unicorns that somehow never gets old...19:13
ildikovbsilverman: but for instance the first Akraino blueprint is based on Airship, there is a proposal for StarlingX and I believe that there are other blueprints as well including OpenStack services19:14
ildikovI will present on their community call about the work that the OSF Edge WG is doing next Thursday19:14
ildikovwe have a similar activity with ETSI MEC on introducing activities and see where we can collaborate19:15
ildikovwe work a lot with K8s in general and especially in the cloud provider space19:15
*** dtantsur is now known as dtantsur|afk19:17
bsilvermanildikov: I saw that VOLTHA and SEBA were both going to a container based model on bare metal, are they still going in that direction?19:17
ildikovbsilverman: not sure, I would need to check19:17
bsilvermanokay. The model used to be OpenStack, that's why I was wondering.19:18
bsilvermanI know it's a big job to keep an eye on all of these groups :)19:18
ildikovbsilverman: yeah, it certainly is :)19:19
bsilvermanI was just surprised to see, in some sense, competing projects coming out of the LF19:19
ildikovbsilverman: BTW, you should hang out on the #edge-computing-group channel :)19:19
bsilvermansure, what's one more channel to annoy :)19:20
ildikovbsilverman: when it comes to edge they have some projects competing more with each other than our projects19:20
ildikovlol :)19:20
mnaseram I behind on my email or did we not get the usual invite sent out for the board meeting?19:34
clarkbmnaser: with the switch from webex to zoom the automated invites from webex stopped getting sent19:34
mnaser:(19:35
cmurphyjbryce sent a reminder email 5 hours ago19:40
*** fdegir_ has joined #openstack-tc20:15
*** irclogbot_3 has quit IRC20:15
*** irclogbot_3 has joined #openstack-tc20:16
*** jamesmcarthur has quit IRC20:32
*** jamesmcarthur has joined #openstack-tc20:33
*** zaneb has joined #openstack-tc20:36
*** e0ne has quit IRC20:42
*** fdegir_ is now known as fdegir20:55
*** cdent has quit IRC21:17
*** diablo_rojo has joined #openstack-tc21:31
*** diablo_rojo has quit IRC23:07
*** jamesmcarthur has quit IRC23:08
-openstackstatus- NOTICE: http://zuul.openstack.org is not working. https://zuul.openstack.org does work. Please use that while we investigate.23:14
*** jamesmcarthur has joined #openstack-tc23:19
*** jamesmcarthur has quit IRC23:23

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