16:01:15 <devinavery> #startmeeting MD-SAL Status Call
16:01:15 <odl_meetbot> Meeting started Tue Jul  8 16:01:15 2014 UTC.  The chair is devinavery. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:01:15 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:15 <odl_meetbot> The meeting name has been set to 'md_sal_status_call'
16:01:33 <devinavery> #chair colindixon
16:01:33 <odl_meetbot> Current chairs: colindixon devinavery
16:02:09 <colindixon> hey devinavery, I’m actually on another call and so I can’t take notes :-/
16:02:09 <colindixon> sorry
16:02:35 <devinavery> colindixon: no worries - saw you were here so I promoted you. :) Thanks,.
16:02:59 <colindixon> no worries
16:03:03 <colindixon> I might follow here though
16:03:50 <icbts> i can hear you :)
16:03:58 <icbts> I’m via the webex
16:06:35 <edwarnicke> https://git.opendaylight.org/gerrit/#/c/8705/
16:07:00 <devinavery> #info Not meeting recording today due to webex limitation
16:08:45 <rgowrishankar> #info Tony's team working on bug fixes and increasing test coverage on MD-SAL
16:09:44 <rgowrishankar> #topic Dlux demo
16:11:21 <devinavery> #info dLux is a standalone project right now.
16:11:22 <rgowrishankar> #info Dlux standalone bundle running using node.js
16:11:28 <devinavery> #info uses restconf to retrieve the data in the UI.
16:11:50 <devinavery> rgowrishankar: I’ll let you scribe. :)
16:11:58 <devinavery> so we don’t duplicate efforts. :)
16:12:02 <rgowrishankar> ok :)
16:12:06 <devinavery> let me know if you need a hand off
16:13:00 <rgowrishankar> #info Demo shows the ability to see flows and node connectors and the statistics. Anything in the md-sal inventory api can be shown in Dlux. All of it is java script based
16:13:03 <rgowrishankar> sure..
16:14:49 <rgowrishankar> #info Topology is graph showing devices and the interconnects. Hovering on a switch shows all the interconnects for the switch. Capability to zoom in and zoom out. It currently picks up only the first topology in the network topology. Future enhancement: to show multiple topologies in tabs
16:15:52 <rgowrishankar> #info localhost:8080/dlux/index.html to load dlux ui
16:16:00 <dbainbri> are requirements like pagination working their way back to the RESTCONF as enhancements?
16:16:16 <rgowrishankar> pre-req: mvn, grunt. read me in dlux project has the reqs..
16:16:32 <rgowrishankar> #info pre-req: mvn, grunt. read me in dlux project has the reqs..
16:18:32 <rgowrishankar> #info q:are requirements like pagination working their way back to the RESTCONF as enhancements? answer: need lots of enhancements from the restconf. Example: old ui had span port config, connection mgr, static route config which are not available for MD-SAL.
16:19:44 <rgowrishankar> #info: Matheiu working on a solution to the problem on how to let plugins bring applications to the ui. plan is to make ui more modular. people should be able to plugin code and pages by registering with dlux.
16:21:15 <rgowrishankar> #info: q: Luis: This calls the inventory and topology UI.. Can we show hosts? answer: L2switch is going to track the host information and we need to wait for that.
16:21:31 <rgowrishankar> #info: Need instructions for mac and windows to run dlux.
16:23:19 <rgowrishankar> #info: What needs to be done to get dlux into the distrbutions? Madhu working on creating jar file and putting it into nexus (maybe today).
16:25:07 <rgowrishankar> #info: yang ui. gathering modules from yang using the modules call. any model in the md-sal will be shown in the ui.
16:27:07 <rgowrishankar> #info: as data is typed in the request that will be sent to the controller is also shown and updated in real-time. Q: Do we also get the URI that the message is sent to? A: The URI is not yet auto-generated.
16:30:26 <rgowrishankar> Q: Can modules not in the core MD-SAL directory be shown in the yang ui? A: there is no mechanism to convert the yang model into yin format for non-core modules. An enhancement to the core is needed.
16:33:33 <rgowrishankar> Q: If flow cannot be pushed, will it be shown on UI? A: if controller is not running, then error message will be shown.
16:34:09 <rgowrishankar> Q: What about if data is wrong and request fails? A: We are not doing any double checks..
16:40:17 <rgowrishankar> #info: Make the enhancement to check the operational data after sending the config data.
16:41:38 <rgowrishankar> #info: can progress be made without waiting for the yin representation to be available?
16:42:02 <rgowrishankar> #info: ability to group the functionality by module to make navigation easier
16:43:31 <rgowrishankar> #info: the real ask to simplify the fields for users..
16:45:16 <rgowrishankar> #info: if model is augmented in a different bundle, will the augmentation will show up here? if the module exposes data in xml or json format it will be possible. another Q: is it possible to link the flows view to the topology view? A: enhancement possible
16:46:32 <rgowrishankar> #info: timeline on these changes not known. Probably possible before next milestone
16:47:18 <rgowrishankar> #topic: MD-SAL archetype
16:47:54 <rgowrishankar> #info: ability to quickly get started on md-sal project
16:48:08 <rgowrishankar> #info: wiki: GettingStarted:Developer_Main
16:48:22 <devinavery> #link https://wiki.opendaylight.org/view/OpenDaylight_Toolkit:MD-SAL-Simple_Archetype Archetype LInk
16:50:17 <rgowrishankar> #info: mvn:archetype:generate -DarchetypeGroupId=org.opendaylight.toolkit -DarchetypeArtifactIf=md-sal-app-simple
16:50:58 <rgowrishankar> # asks a bunch of questions on folders to be created. .gitignore is auto-created to ignore auto-generated files
16:52:07 <rgowrishankar> #info generate directory can be removed after folders have been generated
16:56:31 <rgowrishankar> #info: the config subsystem is already setup for you. It also provides stub codes to the databrokers to get the apis needed.
16:57:33 <rgowrishankar> #archetype-demo-web: sample on how to write your own rest interface in case you are not interested in using restconf
16:58:25 <devinavery> #endmeeting