#opendaylight-meeting: tws

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

Meeting summary

  1. openflowplugin migration (colindixon, 17:43:03)
    1. abhijitkumbhare says that they have input from most projects on the spreadsheet, still reaching out to a few (colindixon, 17:43:19)
    2. ACTION: abhijitkumbhare will put down a loose plan about when/how to do the migration, current plan is OFP M3 (colindixon, 17:43:39)
    3. https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=251530127 the tracking spreadsheet (colindixon, 17:43:51)
    4. colindixon also suggests downstream projects get it written down on their release plans so they know what they need to do and whent (colindixon, 17:44:07)

  2. demos/tutorials at openstack in austin (colindixon, 17:44:13)
    1. CaseyODL and gzhao are looking for people to do demos, reach out to them if you're willling, they currently only have 1-2 (colindixon, 17:44:32)
    2. they will also have videos going on in the background, if you have a demo video, let them know (colindixon, 17:44:45)
    3. live is still preferrred (colindixon, 17:44:51)

  3. tutorials project (colindixon, 17:44:55)
    1. CaseyODL asks if renaming the coretutorials project would be a good idea if it's where we're going to house demos (colindixon, 17:45:09)
    2. colindixon says he doesn't thing the name is the problem, the problem is finding people to care for and maintain tutorials and demos, that's failed twice now: coretutorials and tookit (colindixon, 17:45:36)
    3. vishnoianil suggests using interns (colindixon, 17:45:44)
    4. colindixon suggests making sure the code is tested as best we can (testing tutorials is hard) (colindixon, 17:46:06)
    5. at the very least projects should need to run through the tutorial/demo manually at M5 of one of the RCs at the end of the release if we really want to have them work for each release (colindixon, 17:47:08)
    6. vishnoianil's idea is less about using interns, but instead having some crowdsourced, hackathon where we have 5-6 people try to write a tutorial demo in a given topic area, pick the best one and give them some kind of "award" as well as hosting that repo (colindixon, 17:47:59)
    7. vishnoianil these could then be not really maintained because they could exit for only a release at a time, or one of the hack-a-thons would upgrade an old one to the new releas (colindixon, 17:48:21)
    8. CaseyODL says that we will have 3 interns working on some of this soon (different from vishnoianil's suggestion) (colindixon, 17:48:44)
    9. colindixon thinks maybe having them live in people's projects in a way so that if they break, they break that project, and that project has to fix it and it's encouraged to actually maintain it (colindixon, 17:49:59)
    10. vishnoianil points out that's one kind of tutorial, which is very project specific, like showing how to use OpenFlow plugin to install a flow, meter, and group, while others are maybe spread over multiple projects (colindixon, 17:50:35)
    11. we don't have good ideas for the second kind that we're aware of (colindixon, 17:50:56)
    12. anipbu and CaseyODL both say (and colindixon and anipbu agree) that we really do need a centralized list of the tutorials and demos that are avialable even if they're not centralized in the code repositories (colindixon, 17:51:34)
    13. having a demo/tutorial template with system test showing how to test it would be really awesome to help people get started (colindixon, 17:52:05)
    14. we already have system tests that do some of these tutorials, e.g., we have system tests for vishnoianil's idea around doing flows, meters and groups (colindixon, 17:54:40)
    15. https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:End_to_End_Flows abhijitkumbhare points out that this is already written up on the wiki here (colindixon, 17:55:09)
    16. https://github.com/opendaylight/ovsdb/tree/master/resources/commons (vishnoianil, 17:55:48)
    17. vishnoianil says that OVSDB also has a postman collection of rest calls to exercise various features (see the line above this one) (colindixon, 17:55:59)
    18. abhijitkumbhare points out that the end-to-end flows might need updating of the wiki page, colindixon notes it woudl be really cool if the tutorial instructions pulled the code snippets, e.g., REST URLs and bodies, directly from the system test so they they were always up-to-date (colindixon, 17:56:56)
    19. that's really hard with the wiki, maybe easier with AsciiDoc or readthedocs (colindixon, 17:57:19)
    20. it can also be made moot if we updated correctly every time for every release, but that's been hard in the past (colindixon, 17:57:36)

  4. next week's TWS (colindixon, 17:58:26)
    1. https://wiki.opendaylight.org/view/Tech_Work_Stream:Main#Upcoming_Meeting_Agendas (colindixon, 17:58:40)
    2. zxiiro could cover setting up maven sites and javadoc (colindixon, 17:58:53)
    3. we could talk about inventory vs. topology vs. new topology (colindixon, 17:59:09)
    4. we could talk about fast release and/or phased release in anticipation of Carbon (colindixon, 17:59:37)
    5. colindixon thinks that phased == semantic versioning and would be part of that, but it woudl be a really good topic (colindixon, 17:59:57)
    6. https://www.youtube.com/watch?v=TEC31OUG9HA skitt's talk from the DDF on semantic versioning (colindixon, 18:00:34)


Meeting ended at 18:01:23 UTC (full logs).

Action items

  1. abhijitkumbhare will put down a loose plan about when/how to do the migration, current plan is OFP M3


People present (lines said)

  1. colindixon (39)
  2. odl_meetbot (4)
  3. gzhao (1)
  4. vishnoianil (1)
  5. anipbu (1)


Generated by MeetBot 0.1.4.