17:02:40 <colindixon> #startmeeting tws 17:02:40 <odl_meetbot> Meeting started Mon Sep 14 17:02:40 2015 UTC. The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:02:40 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:02:40 <odl_meetbot> The meeting name has been set to 'tws' 17:02:43 <colindixon> #topic agenda bashing 17:02:55 <colindixon> #chair zxiiro alagalah 17:02:55 <odl_meetbot> Current chairs: alagalah colindixon zxiiro 17:03:20 <colindixon> #link https://wiki.opendaylight.org/index.php?title=Tech_Work_Stream:Main&oldid=36673#Upcoming_Meeting_Agendas today’s agenda 17:05:35 <colindixon> sorry for disconnecting everyone 17:05:38 <colindixon> host keys are not working 17:07:51 <colindixon> #topic topology/inventory model changes in Beryllium 17:08:40 <colindixon> #info note recording started at 10:08a pacific time 17:09:20 <colindixon> #info the plan in beryllium is to deprecate the inventory model in Beryllium (ideall remove it in Boron) 17:09:47 <colindixon> #info the goal was to move to the IETF topology model (however this is based on an expired draft from the IETF) 17:10:27 <colindixon> #info 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 17:11:50 <colindixon> #link https://tools.ietf.org/html/draft-clemm-netmod-yang-network-topo-01 IETF draft for current topology model in OpenDaylight which is now expired 17:13:00 <colindixon> #link https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo-01 IETF draft for the newest version of the IETF topology model 17:13:35 <colindixon> #link 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 17:14:41 <colindixon> #info ttkacik1 goes through the advantages of the topology model over the inventory model 17:15:49 <colindixon> #info 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 17:16:21 <colindixon> #info 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 17:17:11 <colindixon> #action ttkacik1 will post his asciidoc “presentation”/notes to the maliing list and/or to a project 17:17:49 <colindixon> #info obviously moving from inventory topology will change APIs, instance identifiers, and REST URLs 17:18:14 <colindixon> #info also, moving to the new I2RS topology model will as well, since the module names change as well as some fields 17:18:38 <colindixon> #info 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 17:19:41 <colindixon> #action anipbu to to work with ttkacik1 to post it to the Weather page and also send mail to the release list 17:20:11 <colindixon> #link https://lists.opendaylight.org/pipermail/discuss/2015-September/005652.html a list of projects in beryllium using inventory and topology as compiled by colindixon 17:22:16 <colindixon> #info vina_ermagan asks if you’re going to move to topology in beryllium, what should you use 17:23:08 <colindixon> #info colindixon says *right now*, you should use the 2013-10-21 topology model since that’s where most people are publishing their information 17:24:24 <colindixon> #info 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 17:26:46 <colindixon> #info colindixon asks what it says to our users making them move from inventory to topology1 in Beryllium and then topology1 to topology2 in Boron 17:29:21 <colindixon> #info 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 17:30:33 <vina_ermagan> can we get access to the document Tony is sharing? 17:30:37 <colindixon> vina_ermagan: yeah 17:30:42 <colindixon> I already #actioned him to do that 17:30:56 <vina_ermagan> colindixon: thanks 17:31:06 <colindixon> #topic project-local docs 17:32:07 <colindixon> #info alagalah asks about how we talked about at the end of Lithium when we talked about having docs live in projects 17:32:44 <colindixon> #info alagalah would like to have documentation and code patches logically live together 17:33:13 <colindixon> #link https://wiki.opendaylight.org/view/Documentation/Release_Plans/Beryllium_Release_Plan see the deliverables 17:36:08 <colindixon> #info colindixon is actively working on this 17:36:17 <colindixon> #topic advanced wikiing 17:38:03 <phrobb> #info colindixon shows stream-of-thought notes that he will link to later.... 17:38:20 <colindixon> https://www.mediawiki.org/wiki/Help:Templates 17:38:47 <phrobb> #info Templates are a way to include some content into another page 17:39:44 <phrobb> #info example, Helium Release Template 17:40:08 <phrobb> #info most simple template is the "Current Release" template... 17:40:29 <phrobb> use the "what links from here" link on left to see what pulls that template in... 17:41:01 <phrobb> #info the "Needs Updating" template is a bit more useful... 17:41:46 <phrobb> #info If you see "what links" that page, you'll see where folks have brought in that page to show it needs updating 17:42:13 <phrobb> #info, colindixon now describes categories 17:42:52 <phrobb> #info using "noinclude" is basically documentation on the template and will not be included when the template is included in another page 17:43:13 <phrobb> #info "project Facts" template is the most sophisticated template used by ODL currently 17:44:02 <odl-casey> Yes 17:44:19 <colindixon> https://wiki.opendaylight.org/index.php?title=Special:MostLinkedTemplates 17:44:21 <phrobb> #info 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 17:44:25 <colindixon> https://wiki.opendaylight.org/view/Template:Project_Facts 17:44:42 <odl-casey> #link https://wiki.opendaylight.org/index.php?title=Special:MostLinkedTemplates 17:48:59 <colindixon> https://www.mediawiki.org/wiki/Transclusion 17:49:23 <phrobb> #info transclusion is the process of "translating and including" one wiki page into another 17:49:35 <odl-casey> #link https://www.mediawiki.org/wiki/Transclusion 17:49:38 <odl-casey> :) 17:50:29 <phrobb> #info double brackets is the transclusion syntax {{ :<page to transclude>}} 17:51:28 <phrobb> #info if you "edit" a portion of a page that is transcluded, the editor will take you to the original source transcluded page 17:53:01 <odl-casey> #info Using <noinclude> and <includeonly> is a method to prevent portions of a page from being Transcluded. 17:53:34 <phrobb> #info 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 17:55:57 <phrobb> #info note that there is an <includeonly> and a different <onlyinclude> tags for transcluded pages 17:56:35 <colindixon> https://www.mediawiki.org/wiki/Help:Categories 18:00:36 <odl-casey> #info 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. 18:00:59 <phrobb> #info 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"... 18:01:06 <colindixon> https://wiki.opendaylight.org/view/Wiki_gardening 18:01:28 <phrobb> #info There is a wiki gardening" page that is helpful to anyone wanting to update/improve the wiki?... 18:01:46 <odl-casey> #link https://wiki.opendaylight.org/view/Wiki_gardening 18:04:58 <colindixon> #endmeeting