================================================ #opendaylight-discovery: weekly discovery status ================================================ Meeting started by dbainbri at 17:59:12 UTC. The full logs are available at http://meetings.opendaylight.org/opendaylight-discovery/2015/weekly_discovery_status/opendaylight-discovery-weekly_discovery_status.2015-02-03-17.59.log.html . Meeting summary --------------- * dbainbri (dbainbri, 17:59:23) * nateharmon (nateharmon, 18:02:15) * ACTION: make sure audio conference number is changed (dbainbri, 18:07:29) * transition to a single project (dbainbri, 18:07:58) * M2 milestone due thursday (dbainbri, 18:09:31) * wiki set up (dbainbri, 18:10:33) * will use this time slot for weekly meeint (dbainbri, 18:10:42) * ACTION: dbainbri update weekly meeting invite (dbainbri, 18:10:50) * have bugzilla account (dbainbri, 18:11:03) * AGREED: use trello for stories, enhancements, tasks. bugzilla for defects (dbainbri, 18:13:38) * AGREED: use ODL email list and IRC channel for communication (dbainbri, 18:14:28) * Nathan used Ed Warnicke's MD-SAL archetype to check in initial structure of code (dbainbri, 18:16:22) * Nate will look to push his changes in the archetype back to Ed (dbainbri, 18:21:45) * Nate has been working on the identification module and node augmentation (dbainbri, 18:22:37) * need to start thinking about requirements for integration tests (dbainbri, 18:24:07) * will be using latest snapshot version in the master branch (dbainbri, 18:26:38) * ACTION: dbainbri invite all committers to the the trello board (dbainbri, 18:27:39) * need to work through use cases where OF flow modes and how drivers are invoked (dbainbri, 18:30:21) * ACTION: dbainbri to take a look at the didm directory structure and get feedback back to uchau to more intent project to that same structure (dbainbri, 18:33:18) * uchau (uchau, 18:33:27) * AGREED: identification flow, new node added trapped by single identity module, if flow capable node that magic happens, if not, SNMP identification attempted, if identified type set and magic happens, if fails, type set to UNKNOWN and other plugins can trigger off that and if they can identify they set the type and magic happens, else it stays as UNKNOWN. (dbainbri, 18:41:47) * AGREED: that augmentation for device type is inventory under operational tree. (dbainbri, 18:42:55) * may want to also populate type to config for persistence as well (dbainbri, 18:43:10) * IDEA: is augmentation in the same shared as inventory or do augmentations use a different sharding strategy (dbainbri, 18:45:17) * ACTION: uchau checking with clustering team on sharding of augmentations (dbainbri, 18:46:01) Meeting ended at 18:46:21 UTC. Action items, by person ----------------------- * dbainbri * dbainbri update weekly meeting invite * dbainbri invite all committers to the the trello board * dbainbri to take a look at the didm directory structure and get feedback back to uchau to more intent project to that same structure * uchau * dbainbri to take a look at the didm directory structure and get feedback back to uchau to more intent project to that same structure * uchau checking with clustering team on sharding of augmentations People present (lines said) --------------------------- * dbainbri (27) * odl_meetbot (3) * uchau (1) * nateharmon (1) Generated by `MeetBot`_ 0.1.4