16:01:48 #startmeeting tsc 16:01:48 Meeting started Thu Jul 5 16:01:48 2018 UTC. The chair is abhijitkumbhare. Information about MeetBot at http://ci.openstack.org/meetbot.html. 16:01:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:48 The meeting name has been set to 'tsc' 16:02:06 #chair skitt dfarrell07 jamoluhrsen 16:02:06 Current chairs: abhijitkumbhare dfarrell07 jamoluhrsen skitt 16:02:13 #info jamoluhrsen 16:02:18 #info vorburger 16:02:20 #info Brady Johnson 16:02:26 #project SFC 16:02:30 vorburger, #info is only for TSC members 16:02:36 #topic Agenda bashing and roll call 16:02:39 #info rovarga 16:02:40 #info shague 16:02:44 #info abhijitkumbhare 16:02:44 #info skitt 16:02:52 #project bgpcep, mdsal, yangtools, coretutorials 16:03:04 #project odlparent controller netvirt ovsdb 16:03:26 #info lori 16:03:33 #project lispflowmapping 16:03:41 #info #project netvirt 16:04:09 rovarga: and comma's blow up the regex :) 16:04:10 #info anipbu 16:04:28 #info gzhao (proxy) 16:04:37 #project usc 16:04:54 #info-for-non-TSC-member-who-has-to-attend-this-meeting-anyway-just-to-pound-in-#project vorburger 16:04:57 #topic Action Item check 16:05:20 #info Accessing CSIT debug environments 16:06:12 shague: what doesn't? 16:06:43 #project bgpcep mdsal yangtools coretutorials 16:07:03 #project odlparent infrautils controller daexim neutron genius archetypes serviceutils 16:07:19 dashboard https://jira.opendaylight.org/secure/Dashboard.jspa?selectPageId=10403# 16:07:19 #info Come back on this topic next week 16:07:25 #topic ODL Parent Update 16:07:41 skitt: vorburger: so who is actually representing controller? 16:08:15 #info Plan to result ODL Parent 4 in August 16:08:25 rovarga: yeah the regex is just a string.split() and then compare the whole word to a list of known projects, so "," is included in compare. easy to fix to be more lenient 16:08:27 #info rgoulding for AAA 16:08:49 Not sure meetbot got the topic change... ? 16:09:16 #topic Releases 16:09:41 #link https://jira.opendaylight.org/secure/Dashboard.jspa?selectPageId=10403 Release Dashboard 16:09:47 rovarga, I don’t think there has to be a bijection, projects can be multiply represented 16:10:01 #info jhershbe 16:10:20 #project neutron 16:10:23 rovarga: is #project XOR ? I thought #project was "commmiters present" - is it "PTL" ? 16:10:37 jhershbe: only TSC members need to info 16:10:47 #topic Clustering 16:11:56 #info Lots of ongoing efforts on this 16:12:26 vorburger: well, dfarrell07 can probably clarify, but I thought it was about representation 16:13:12 vorburger: i.e. I am not usually flashing bgpcep, since Claudio is usually in. today I am, as I am standing in for him 16:13:29 #info Victor Packard going thru the clustering jobs 16:13:52 I'm not sure what the question is exactly but I think it's okay to #info a project twice 16:14:14 rovarga: vorburger: I think couple weeks agao dfarrell07 clarified that the rep is a committer. 16:14:40 shague, rovarga, vorburger yes, in the Managed Release docs only a committer can rep a project 16:16:01 #info we now have a trimmed down controller cluster job that will run in 30m and hit sporadic failures. this might be easier to use for debugging 16:17:18 dfarrell07: well, my question is whether pount-project is a flash of badges, or declaration of project representation 16:17:49 rovarga: declaration of project representation 16:20:39 #info We need more developers to focus on clustering issues besides rovarga and pantelis_ due to their cycles 16:22:20 #info There are around 8 developers trying to get on-board on the clustering code but the ramp up time is steep 16:23:15 ##info A code walk thru session would be helpful 16:24:54 rovarga: it's not 8 new devs, it's heaping our existing devs on clustering 16:25:49 rovarga: pantelis_: I'm looking at an (internally reported) bug which I suspect is that thing somewhere in clustering which does that System.exit.. we still have that (oxygen), right? Remind me where that was? 16:26:27 vorburger: restart of container, look for karaf.restart or something like that 16:26:43 and when that triggers, there is no recourse 16:27:05 rovarga: "look for karaf.restart" in code or log you mean? 16:27:11 in code 16:28:25 Previous comment did not go thru - retyping: 16:28:29 #info A code walk thru session would be helpful 16:29:17 rovarga: would the pattern seen on https://gist.github.com/vorburger/615d2c1f73632dd273a66ff1b627c3c5 make you think this is the "karaf.restart" thing? 16:29:50 rovarga: org.apache.karaf.main.Main launch only once, then org.apache.karaf.main.lock.SimpleFileLock lock, then lots of stuff happening, and then a sudden abrupt 16:30:22 vorburger: I don't know 16:30:30 rovarga: abrupt "org.apache.karaf.main.lock.SimpleFileLock lock" again, without the org.apache.karaf.main.Main launch, and full restart cycle - that's a karaf.restart? 16:30:33 vorburger: we are loud when restarting things 16:33:19 rovarga: https://github.com/opendaylight/controller/blob/master/opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/akka/osgi/impl/QuarantinedMonitorActorPropsFactory.java ? 16:33:49 #info Two courses of action needed: 1) Going thru issues in detail & 2) Code walk thru session 16:35:19 vorburger: yes 16:36:33 https://jira.opendaylight.org/issues/?filter=10345 16:36:36 #action vpickard pantelis_ jamoluhrsen to get on a call together to go thru the issues in detail 16:36:58 #topic Fluorine middlepoint check - Grievances 16:37:11 rovarga: FYI that 'LOG.warn("Restarting karaf container");' never makes it.. probably shuts down too fast? Would adding a stupid sleep there be a crazy idea? 16:37:11 #link https://jira.opendaylight.org/issues/?filter=10345 16:37:52 vorburger: never makes it? are you saying the container is shutting down without flushing logs? 16:37:54 #link https://jira.opendaylight.org/browse/TSC-119?filter=10345 TSDR 16:38:12 vorburger: and yes, unsubstianted sleeps are always crazy 16:38:35 #link https://jira.opendaylight.org/browse/TSC-118?filter=10345 ALTO 16:38:53 https://jira.opendaylight.org/secure/Dashboard.jspa?selectPageId=10400 16:39:03 fluorine dashboard: https://jira.opendaylight.org/secure/Dashboard.jspa?selectPageId=10400 16:39:25 https://jira.opendaylight.org/browse/TSC-117?filter=10345 ODL-Parent 16:39:29 rovarga: that's what https://gist.github.com/vorburger/615d2c1f73632dd273a66ff1b627c3c5 looks like no? I'm trying to understand why there is no "org.apache.karaf.main.Main launch" in Karaf code 16:39:47 #link https://jira.opendaylight.org/browse/TSC-117?filter=10345 ODL-Parent 16:42:04 #link https://jira.opendaylight.org/browse/TSC-75?filter=10345 Monitor Neutron committers 16:42:53 vorburger: if you want to keep using that issue to track places odlparent MRI caused slowness, you can retarget it at end of release 16:42:57 #info vorburger and jhershbe are new committers as Isaku stepped out 16:44:13 #link https://jira.opendaylight.org/browse/TSC-74?filter=10345 Monitor BGP -PCEP committers 16:45:46 #info Claudio has been responsive for handling issues, but keep this open as we still have very few committers 16:46:47 https://jira.opendaylight.org/issues/?filter=10333 16:48:18 #link https://gerrit.linuxfoundation.org/infra/#/c/11139/ review this 16:49:22 vorburger: I do not know. I would need to understand the deployment scenario, see all the logs and spend some time on it to formulate what it does or does not look like. 16:50:03 #link https://gerrit.linuxfoundation.org/infra/#/c/11139/30/docs/lifecycle/project_data_template.rst give feedback please 16:54:10 #action aadam Make a due date mandatory for TSC JIRA tickets which are grievances 16:57:05 jhershbe: can I assume you read ./opendaylight/md-sal/sal-distributed-datastore/src/site/asciidoc/distributed-data-store.adoc ? 16:57:15 #action aadam to improve the grievance fields (what should be mandatory and what should be dropped) 16:57:44 rovarga, I did not because I did not know it was there ;-) 16:57:55 jhershbe: fgrep -rn ' 16:58:04 #link https://lists.opendaylight.org/pipermail/integration-dev/2018-July/012256.html midway checkpoint stats 16:58:08 jamoluhrsen: got it 16:58:15 #topic Midway Checkpoint stats 16:58:20 rovarga, the issues I was looking at were in controller so that's where I started looking ;-) 16:58:24 #link https://lists.opendaylight.org/pipermail/integration-dev/2018-July/012256.html midway checkpoint stats 16:58:27 jhershbe: fgrep -rni 'term' opendayligh/mdsal/sal-distributed-datastore ... anything you are looking for stuff 16:58:55 nite@nitebug : ~/odl/controller on master $ ls -l ./opendaylight/md-sal/sal-distributed-datastore/src/site/asciidoc/distributed-data-store.adoc 16:58:57 -rw-rw-r--. 1 nite nite 18623 Jun 21 16:03 ./opendaylight/md-sal/sal-distributed-datastore/src/site/asciidoc/distributed-data-store.adoc 16:59:00 rovarga, thanks 16:59:03 it *is* in the controller ... 16:59:19 rovarga, ah, ok. 16:59:37 #info BGPCEP autorelease failures (15) stands out 17:00:37 rovarga, looks very useful, thanks 17:01:11 skitt, ^^^ 17:01:29 jhershbe, yeah that’s what I was thinking of too 17:01:37 vpickard, look at the above too 17:01:39 * bjohnson I have to disconnect now 17:01:46 skitt: ack, thanks 17:02:16 #undo 17:02:16 Removing item from minutes: 17:02:16 skitt, I asked a few people and no one pointed me to that till now :-( Not blaming anyone, of course. 17:02:54 #info Autorelease failures for BGPCEP (15) & NetConf (7) also stands out 17:03:00 #info rovarga says high bgpcep autorelease failure count is partly related to project being first to hit version bump issues 17:03:02 #undo 17:03:02 Removing item from minutes: 17:03:07 #info rovarga says high bgpcep autorelease failure count is partly related to project being first to hit version bump issues 17:03:25 #undo 17:03:25 Removing item from minutes: 17:03:27 #info Autorelease failures for BGPCEP (15) & NetConf (7) stand out 17:03:41 #info rovarga says high bgpcep autorelease failure count is partly related to project being first to hit version bump issues 17:04:09 #topic TWS this Monday 17:04:57 #info End user feedback from Sprint 17:05:21 CaseyLF: I would send your TWS announcement sooner rather than the day 17:05:26 #info All developers & TSC members are encouraged to attend 17:05:32 #undo 17:05:32 Removing item from minutes: 17:05:51 #info All developers & TSC members are encouraged to attend as this is an important topic 17:08:00 #info Topics for the next few TWS - Clustering code walk thru in 2 weeks; Publishing of models to github 17:08:27 rovarga: any other TWS topic I missed? 17:08:42 #topic Cookies 17:08:46 abhijitkumbhare: not that I know of 17:08:51 #endmeeting