#opendaylight-meeting: tsc

Meeting started by colindixon at 17:01:01 UTC (full logs).

Meeting summary

  1. agenda bashing and roll call (colindixon, 17:01:06)
    1. rovarga for jmedved (rovarga, 17:01:09)
    2. rovarga for jmedved (rovarga, 17:01:15)
    3. Prem_ for Chris Price (Prem_, 17:01:24)
    4. colindixon (colindixon, 17:01:26)
    5. adetalhouet (adetalhouet, 17:01:30)
    6. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=50953#Agenda the agenda in it's usual place (colindixon, 17:01:41)
    7. abhijitkumbhare (abhijitkumbhare, 17:01:51)
    8. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-10-13-17.01.log.txt (colindixon, 17:01:54)
    9. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc_meeting_oct_6__2016/opendaylight-meeting-tsc_meeting_oct_6__2016.2016-10-06-17.02.html last week's meeting minutes (colindixon, 17:02:24)
    10. https://lists.opendaylight.org/pipermail/tsc/2016-October/006124.html colindixon started a thread on when you need to be a committer/PTL/project to participate in the elections (colindixon, 17:03:11)
    11. Anil Vishnoi (vishnoianil, 17:03:34)
    12. LuisGomez, colindixon, jamoluhrsen, phrobb, and tykeal have talked about where to put CSIT for Carbon, it looks like we'll try to migrate to the second availability zone as we build it out (colindixon, 17:03:43)
    13. ACTION: colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way (colindixon, 17:04:03)
    14. ACTION: colindixon and zxiiro to work on trying to build tools to help with what's failing on failures in our jenkins jobs (colindixon, 17:04:24)
    15. edwarnicke (edwarnicke, 17:04:40)
    16. ACTION: dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion (colindixon, 17:04:43)
    17. rovarga says that we do have a jenkins log analyzer plugin, it's just a matter of extending it (colindixon, 17:05:11)
    18. https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer is what we have deployed, we need to populate its knowledge base (rovarga, 17:06:08)
    19. ACTION: phrobb to get the OPNFV plugfest on our events page http://events.linuxfoundation.org/events/opnfv-plugfest/ (colindixon, 17:06:59)
    20. ACTION: phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better (colindixon, 17:07:26)
    21. jamoluhrsen (jamoluhrsen, 17:08:00)

  2. TSC mailing list votes and discussions (colindixon, 17:08:41)
    1. we have the above mentioned when things have to happen to participate in elections (colindixon, 17:08:51)
    2. https://lists.opendaylight.org/pipermail/tsc/2016-October/006101.html Future Summit structure suggestions/feedback (colindixon, 17:09:01)
    3. it seems like the developer community would really like an extra day (colindixon, 17:09:11)
    4. phrobb says he'll make it work to have an extra day if it makes sense and we'll try to keep it within costs (colindixon, 17:10:19)
    5. abhijitkumbhare asks if we could just move the last day of the DDF to a company site given that we'll be in the south bay anyway (colindixon, 17:11:33)

  3. events (colindixon, 17:11:51)
    1. https://www.opendaylight.org/global-events (colindixon, 17:11:52)
    2. OpenStack summit in Barcelona is on 10/24 (colindixon, 17:12:11)
    3. OpenDaylight India Forum on 11/16 (colindixon, 17:12:23)
    4. CaseyODL and phrobb are looking for demos for the booth at OpenStack, please reach out (colindixon, 17:12:38)

  4. boron (colindixon, 17:12:53)
    1. https://lists.opendaylight.org/pipermail/release/2016-October/008419.html <--- The Boron Autorelease job failed to build vbd modules. A patch fixing the issues have been merged. (anipbu, 17:13:03)
    2. Boron-SR1 is in two weeks on October 27 with a cutoff on 10/23 23:59 UTC. (anipbu, 17:13:19)
    3. https://git.opendaylight.org/gerrit/#/q/status:open+branch:stable/boron <--- 29 patches pending for stable/boron (anipbu, 17:13:35)
    4. https://bugs.opendaylight.org/buglist.cgi?bug_severity=blocker&bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=WAITING_FOR_REVIEW&f1=cf_target_milestone&f2=cf_target_milestone&j_top=OR&list_id=67733&o1=substring&o2=substring&query_format=advanced&resolution=---&v1=Boron&v2=--- <--- Two blocker bugs in openflowplugin (anipbu, 17:13:55)
    5. https://git.opendaylight.org/gerrit/#/dashboard/?title=Boron+Status&Yang+File+Changes+Since+Boron=branch:stable/boron+status:merged+file:%22%255E.%252Byang%22+after:2016-09-15 <--- 27 patches modifying yang files without API Freeze Waiver between Boron Release and Boron SR1 (anipbu, 17:14:21)
    6. Bug 6575 is fixed (depends on bug 6710 in mdsal) (abhijitkumbhare, 17:15:38)
    7. colindixon notes that YANG file changes in SRs are problematic if not done in backward compatible ways for users (colindixon, 17:15:51)

  5. stable/beryllium (colindixon, 17:16:33)
    1. Beryllium-SR4 is in one week on October 20 with a cutoff this Sunday at 10/16 23:59 UTC. (anipbu, 17:16:42)
    2. https://git.opendaylight.org/gerrit/#/q/status:open+branch:stable/beryllium <--- 63 patches pending for stable/beryllium (anipbu, 17:16:49)
    3. https://bugs.opendaylight.org/buglist.cgi?bug_severity=blocker&bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=WAITING_FOR_REVIEW&f1=cf_target_milestone&f2=cf_target_milestone&j_top=OR&list_id=67733&o1=substring&o2=substring&query_format=advanced&resolution=---&v1=Beryllium&v2=--- <--- Zero blocker bugs targeted for (anipbu, 17:16:56)
    4. https://git.opendaylight.org/gerrit/#/dashboard/?title=Beryllium+Status&Yang+File+Changes+Since+Beryllium+SR3=branch:stable/beryllium+status:merged+file:%22%255E.%252Byang%22+after:2016-07-28 <--- 10 patches modifying yang files without API Freeze Waiver between Beryllium SR3 and Beryllium SR4 (anipbu, 17:17:16)
    5. colindixon notes that SR4 is the last scheduled release, so if there are patches you care about in the 63 above, get them in (colindixon, 17:18:44)

  6. carbon (colindixon, 17:18:51)
    1. https://lists.opendaylight.org/pipermail/project-proposals/2016-September/000525.html <--- Kindly remind projects to submit project proposals for Carbon Offset 2 by 10/20/2016 (anipbu, 17:18:59)
    2. https://wiki.opendaylight.org/view/Simultaneous_Release:Carbon_Release_Plan#M0:_Declare_Intent <--- We are currently missing M0 status from 21 projects: atrium, capwap, cardinal, centinel, didm, dlux, docs, eman, iotdm, natapp, next, nic, openflowjava, sdninterfaceapp, snbi, snmp, ttp, usecplugin, vtn, yang-push, yangide (anipbu, 17:19:20)
    3. https://wiki.opendaylight.org/view/Simultaneous_Release:Per-Project_Carbon_Release_Plan_Template <--- Carbon M1 Offset 0 is quickly approaching next week. Kindly remind offset 0 projects to begin creating their draft release plan. (anipbu, 17:19:29)
    4. We have completed cleaning up the Weather page with 7 pending weather items still open and the rest archived. (anipbu, 17:19:48)
    5. https://wiki.opendaylight.org/view/Weather (colindixon, 17:20:02)
    6. https://lists.opendaylight.org/pipermail/netconf-dev/2016-October/000669.html <--- The Carbon Autorelease job failed to build netconf modules. A pacth fixing the issues have been merged. (anipbu, 17:20:04)

  7. system integration and test (colindixon, 17:20:45)
    1. we're still seeing some ssh issues in infra and we're working on it, but it's not fixed yet (colindixon, 17:20:58)

  8. infra (colindixon, 17:21:26)
    1. nothing this week, tykeal is out on PTO (colindixon, 17:21:27)

  9. TSC elections (colindixon, 17:21:51)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-October/006136.html the board has approved the elections and we're ready to go (colindixon, 17:22:19)
    2. https://wiki.opendaylight.org/view/TSC:2016_Election this is the tracking page phrobb set up (colindixon, 17:22:30)
    3. it currently proposses starting nominations today and having them last a week (colindixon, 17:22:57)
    4. edwarnicke asks if starting on Monday might make sense so that notifications aren't lost in the weekend, rovarga says he agrees, colindixon says as long as it's measured in weeks it's probably fine (colindixon, 17:25:09)
    5. zxiiro asks if we want a longer nomination period, colindixon agrees (colindixon, 17:26:04)
    6. AGREED: we will open the nomination period today (10/13) and close it at 23:59 UTC 10/26 wednesday, so that we can have the results for the 10/27 TSC call (colindixon, 17:28:13)
    7. depends whether it is a Closeable or an AutoCloseable :) (rovarga, 17:28:44)
    8. AGREED: we will have voting last 2 weeks spanning 10/27 to 23:59 UTC 11/9 wednesday, so we can have results for the 11/10 TSC call (colindixon, 17:29:51)
    9. abhijitkumbhare asks if it's really the case that you can only run in one RG, colindixon says yes and it's to avoid weird incentives and behavior around which one you would choose to win in if you won two (colindixon, 17:32:18)
    10. ACTION: phrobb to kick off the TSC elecition nomination period (colindixon, 17:32:54)
    11. vishnoianil asks if we want to resolve when people need to be PTLs and/or committers to nominate themselves or vote (colindixon, 17:35:30)
    12. https://lists.opendaylight.org/pipermail/tsc/2016-October/006124.html this thread (colindixon, 17:35:42)
    13. we have two options listed in that mail (colindixon, 17:35:52)
    14. edwarnicke says (what colindixon thinks he's heard as mostly consensus) which is if you're eligible to participate in the window and get the vote/nominatino off in time, it's valid (colindixon, 17:36:50)
    15. colindixon heard edwarnicke correctly :) (edwarnicke, 17:37:05)
    16. rovarga poitns out we would want to wait to freeze things for a bit even if we froze them because we have no mdsal or controller PTL at the moment (colindixon, 17:37:19)
    17. edwarnicke points out that there are two ideas: 1.) you must be a committer at the opening of the vote to vote or 2.) you must be a comitter at some point during the vote to vote, both deal with removal in clean ways, by ignoring it (colindixon, 17:45:37)
    18. VOTE: Voted on "when do peopel have to be a committer to vote in the CAL elections: 1.) you must be a committer at the opening of the vote to vote or 2.) you must be a comitter at some point during the vote to vote?" Results are, 1: 5, 2: 3 (colindixon, 17:47:40)
    19. AGREED: you must be a committer at the opening of the vote to vote (colindixon, 17:48:00)
    20. AGREED: as long as you are eligible and get your nomination e-mail out in time, you can nominate yourself even if you qualify after the window for nomination opens (colindixon, 17:48:29)

  10. ExIm creation review (colindixon, 17:48:43)
    1. https://wiki.opendaylight.org/view/Project_Proposals:Data_Export_Import project proposal (colindixon, 17:49:05)
    2. https://lists.opendaylight.org/pipermail/project-proposals/2016-September/000528.html proposed on 9/22/2016 (colindixon, 17:49:14)
    3. this is trying to provide an administration feature that's easy for devops or admins to use to deal with data store data with a particular focus on migrating data between major version updates or between models (colindixon, 17:50:48)
    4. can also be used to chagne things like shard configuration and suck the data out and put it back in (colindixon, 17:51:30)
    5. the basic idea is relatively simple: do an export: gives you a models declaration file and the actual data stored per the netmod-yang-json RFC (colindixon, 17:52:26)
    6. the models declaration file allows you to make sure that the models you need are available when importing data (colindixon, 17:52:50)
    7. on import we have two guardrails: 1.) models declaration file and 2.) as you put the data in there's checking that data comes in (colindixon, 17:53:22)
    8. exports data in a single transaction to get a pretty close to sane snapshot of data, but that's not flawless given that there's no administrative freeze on writes (colindixon, 17:53:59)
    9. all data is loaded into the MD-SAL in a single transaction (colindixon, 17:54:35)
    10. david points out that the data stored in netmod-json-yang format is version independent in terms of the data, so it's easier to migrate from models to models (colindixon, 17:55:09)
    11. rovarga asks what models are actually exported? if it's just the global schema context, that's not so much individual models as it is the almagmation of things in the running controller, not just YANG files (colindixon, 17:56:34)
    12. david notes that it can exclude modules by name or datastore (e.g., config or operational) (colindixon, 17:57:11)
    13. rovarga notes that model exclusion might go wrong if you exclude a model that another model uses a grouping from (colindixon, 17:58:49)
    14. colindixon notes that there are also issues where importing from json doesn't guarantee that the data will be the same in the YANG sense as when it was exported (colindixon, 17:59:26)
    15. edwarnicke also notes that it might be nice to be able to exclude from a point in the tree (colindixon, 17:59:40)
    16. Prem_ asks if they've looked at encryption, david says it's exported to the local filesystem, so not right now (colindixon, 18:00:58)
    17. rovarga asks that people do the schema context export in a way that's compatible with https://bugs.opendaylight.org/show_bug.cgi?id=2880 (colindixon, 18:02:01)
    18. VOTE: Voted on "shall the TSC approve the Data Export Import as an incubation project?" Results are, +1: 8 (colindixon, 18:03:22)
    19. rovarga's +1 was " if encoding is scratched from scope" (colindixon, 18:03:35)
    20. because it is a subset of BUG-2880 (rovarga, 18:03:47)
    21. AGREED: Data Exim is an incubation project (colindixon, 18:03:51)

  11. cookies (colindixon, 18:04:06)


Meeting ended at 18:04:08 UTC (full logs).

Action items

  1. colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way
  2. colindixon and zxiiro to work on trying to build tools to help with what's failing on failures in our jenkins jobs
  3. dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
  4. phrobb to get the OPNFV plugfest on our events page http://events.linuxfoundation.org/events/opnfv-plugfest/
  5. phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better
  6. phrobb to kick off the TSC elecition nomination period


Action items, by person

  1. colindixon
    1. colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way
    2. colindixon and zxiiro to work on trying to build tools to help with what's failing on failures in our jenkins jobs
    3. dfarrell07 colindixon to try to drive some/all of the ongoing TSC discussions to completion
  2. phrobb
    1. colindixon, zxiiro and phrobb to come up with a proposal for tracking project activity in a positive way
    2. phrobb to get the OPNFV plugfest on our events page http://events.linuxfoundation.org/events/opnfv-plugfest/
    3. phrobb and tykeal to look into an ODL infra micro-datacenter in a box to make things work better
    4. phrobb to kick off the TSC elecition nomination period


People present (lines said)

  1. colindixon (96)
  2. odl_meetbot (18)
  3. anipbu (16)
  4. rovarga (9)
  5. edwarnicke (4)
  6. abhijitkumbhare (4)
  7. vishnoianil (4)
  8. jamoluhrsen (4)
  9. adetalhouet (3)
  10. Prem_ (3)
  11. phrobb (0)


Generated by MeetBot 0.1.4.