#opendaylight-meeting: tws

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

Meeting summary

  1. agenda bashing (colindixon, 17:02:43)
    1. https://wiki.opendaylight.org/index.php?title=Tech_Work_Stream:Main&oldid=36673#Upcoming_Meeting_Agendas today’s agenda (colindixon, 17:03:20)

  2. topology/inventory model changes in Beryllium (colindixon, 17:07:51)
    1. note recording started at 10:08a pacific time (colindixon, 17:08:40)
    2. the plan in beryllium is to deprecate the inventory model in Beryllium (ideall remove it in Boron) (colindixon, 17:09:20)
    3. the goal was to move to the IETF topology model (however this is based on an expired draft from the IETF) (colindixon, 17:09:47)
    4. moving to the newer (still not final) version of the IETF topology model is something that we *might* do in Beryllium, but it’s harder since it affects more projects (colindixon, 17:10:27)
    5. https://tools.ietf.org/html/draft-clemm-netmod-yang-network-topo-01 IETF draft for current topology model in OpenDaylight which is now expired (colindixon, 17:11:50)
    6. https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo-01 IETF draft for the newest version of the IETF topology model (colindixon, 17:13:00)
    7. https://meetings.opendaylight.org/opendaylight-meeting/2015/md_sal_interest_call/opendaylight-meeting-md_sal_interest_call.2015-09-08-16.01.html meeting minutes from a full hour meeting covering these issues (colindixon, 17:13:35)
    8. ttkacik1 goes through the advantages of the topology model over the inventory model (colindixon, 17:14:41)
    9. at a high level, it allows for multiple “topologies”, e.g., one per protocol, or multiple for different layers and it also allows dependencies between different elements of different topologies, e.g., describe overlays (colindixon, 17:15:49)
    10. in the newer I2RS topology model, it’s split into the “network” model for things wihout termination points or links, and “network-topology” which has those added in (colindixon, 17:16:21)
    11. ACTION: ttkacik1 will post his asciidoc “presentation”/notes to the maliing list and/or to a project (colindixon, 17:17:11)
    12. obviously moving from inventory topology will change APIs, instance identifiers, and REST URLs (colindixon, 17:17:49)
    13. also, moving to the new I2RS topology model will as well, since the module names change as well as some fields (colindixon, 17:18:14)
    14. the plan is for the topology processing framework to help out with the migration by allowing for easy copying of information between teh three models (colindixon, 17:18:38)
    15. ACTION: anipbu to to work with ttkacik1 to post it to the Weather page and also send mail to the release list (colindixon, 17:19:41)
    16. https://lists.opendaylight.org/pipermail/discuss/2015-September/005652.html a list of projects in beryllium using inventory and topology as compiled by colindixon (colindixon, 17:20:11)
    17. vina_ermagan asks if you’re going to move to topology in beryllium, what should you use (colindixon, 17:22:16)
    18. colindixon says *right now*, you should use the 2013-10-21 topology model since that’s where most people are publishing their information (colindixon, 17:23:08)
    19. in terms of publishing, it’s sort of your choice, most people *now* are using the old one, the new one is likely the direction o the future (colindixon, 17:24:24)
    20. colindixon asks what it says to our users making them move from inventory to topology1 in Beryllium and then topology1 to topology2 in Boron (colindixon, 17:26:46)
    21. the topology processing framework is able to provide the really basic information between these models, and there’s also an SPI to copy data, e.g., augmentations, as long as you provide augmentations in all the models (colindixon, 17:29:21)

  3. project-local docs (colindixon, 17:31:06)
    1. alagalah asks about how we talked about at the end of Lithium when we talked about having docs live in projects (colindixon, 17:32:07)
    2. alagalah would like to have documentation and code patches logically live together (colindixon, 17:32:44)
    3. https://wiki.opendaylight.org/view/Documentation/Release_Plans/Beryllium_Release_Plan see the deliverables (colindixon, 17:33:13)
    4. colindixon is actively working on this (colindixon, 17:36:08)

  4. advanced wikiing (colindixon, 17:36:17)
    1. colindixon shows stream-of-thought notes that he will link to later.... (phrobb, 17:38:03)
    2. https://www.mediawiki.org/wiki/Help:Templates (colindixon, 17:38:20)
    3. Templates are a way to include some content into another page (phrobb, 17:38:47)
    4. example, Helium Release Template (phrobb, 17:39:44)
    5. most simple template is the "Current Release" template... (phrobb, 17:40:08)
    6. the "Needs Updating" template is a bit more useful... (phrobb, 17:41:01)
    7. If you see "what links" that page, you'll see where folks have brought in that page to show it needs updating (phrobb, 17:41:46)
    8. , colindixon now describes categories (phrobb, 17:42:13)
    9. using "noinclude" is basically documentation on the template and will not be included when the template is included in another page (phrobb, 17:42:52)
    10. "project Facts" template is the most sophisticated template used by ODL currently (phrobb, 17:43:13)
    11. https://wiki.opendaylight.org/index.php?title=Special:MostLinkedTemplates (colindixon, 17:44:19)
    12. for example, in the TTP page, many things are expanded out in the projects facts box from a single include of the project facts template (phrobb, 17:44:21)
    13. https://wiki.opendaylight.org/view/Template:Project_Facts (colindixon, 17:44:25)
    14. https://wiki.opendaylight.org/index.php?title=Special:MostLinkedTemplates (odl-casey, 17:44:42)
    15. https://www.mediawiki.org/wiki/Transclusion (colindixon, 17:48:59)
    16. transclusion is the process of "translating and including" one wiki page into another (phrobb, 17:49:23)
    17. https://www.mediawiki.org/wiki/Transclusion (odl-casey, 17:49:35)
    18. double brackets is the transclusion syntax {{ :<page to transclude>}} (phrobb, 17:50:29)
    19. if you "edit" a portion of a page that is transcluded, the editor will take you to the original source transcluded page (phrobb, 17:51:28)
    20. Using <noinclude> and <includeonly> is a method to prevent portions of a page from being Transcluded. (odl-casey, 17:53:01)
    21. colindixon has requested more features for sub-page transclusion using labels. He'll send a mail on how that works once it's installed on our mediawiki (phrobb, 17:53:34)
    22. note that there is an <includeonly> and a different <onlyinclude> tags for transcluded pages (phrobb, 17:55:57)
    23. https://www.mediawiki.org/wiki/Help:Categories (colindixon, 17:56:35)
    24. If you're going to use a category a lot, you may want to create a template to apply automatically apply the category for you. (odl-casey, 18:00:36)
    25. alagalah asks "can we use templates to update stale pages, say for 8 months or more and add a header stating this page is stale"... (phrobb, 18:00:59)
    26. https://wiki.opendaylight.org/view/Wiki_gardening (colindixon, 18:01:06)
    27. There is a wiki gardening" page that is helpful to anyone wanting to update/improve the wiki?... (phrobb, 18:01:28)
    28. https://wiki.opendaylight.org/view/Wiki_gardening (odl-casey, 18:01:46)


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

Action items

  1. ttkacik1 will post his asciidoc “presentation”/notes to the maliing list and/or to a project
  2. anipbu to to work with ttkacik1 to post it to the Weather page and also send mail to the release list


People present (lines said)

  1. colindixon (43)
  2. phrobb (18)
  3. odl-casey (7)
  4. odl_meetbot (4)
  5. vina_ermagan (2)
  6. zxiiro (0)
  7. alagalah (0)


Generated by MeetBot 0.1.4.