|
ODL M3 Documenatation Status
Paul Zimmerman
Hi ODL Release Team,
The ODL Documentation project is currently behind schedule. Due to lack of resources, we have not completed User Guide drafts. We recently got a couple of writers from Brocade, and I have had some discussions with Cisco managers to get more bodies on the Docs project, so we are trying to catch back up. However, we are currently red.
|
||||||||
|
|
||||||||
|
Re: ODL M3 Documenatation Status
Colin Dixon
Thanks for letting us know. Is there anything else that the community could do to help? I guess the obvious thing is to figure out if there are more resources that can be shaken free.
On Thu, Jul 3, 2014 at 12:24 PM, Paul Zimmerman (pzimmerm) <pzimmerm@...> wrote:
|
||||||||
|
|
||||||||
|
Re: ODL M3 Documenatation Status
Paul Zimmerman
That’s really the main issue… we don’t have enough folks to do the work.
From: Colin Dixon [mailto:colin@...]
Thanks for letting us know. Is there anything else that the community could do to help? I guess the obvious thing is to figure out if there are more resources that can be shaken free.
--Colin
On Thu, Jul 3, 2014 at 12:24 PM, Paul Zimmerman (pzimmerm) <pzimmerm@...> wrote:
Hi ODL Release Team,
The ODL Documentation project is currently behind schedule. Due to lack of resources, we have not completed User Guide drafts. We recently got a couple of writers from Brocade, and I have had some discussions with Cisco managers to get more bodies on the Docs project, so we are trying to catch back up. However, we are currently red.
|
||||||||
|
|
||||||||
|
Re: ODL M3 Documenatation Status
Mathieu Lemay
+1 on that... On Jul 3, 2014 2:08 PM, "Paul Zimmerman (pzimmerm)" <pzimmerm@...> wrote:
|
||||||||
|
|
||||||||
|
Re: ODL M3 Documenatation Status
Colin Dixon
Do you want to send an e-mail to discuss (or somewhere else) appealing for resources? I wish that I had seen this before the TSC meeting and I could have asked there as well. --Colin
On Thu, Jul 3, 2014 at 1:26 PM, Mathieu Lemay <mlemay@...> wrote:
|
||||||||
|
|
||||||||
|
AAA M3 status
Nguyen, Liem Manh <liem_m_nguyen@...>
Hi folks,
FYI… I updated the AAA status page to reflect our current status. We lost a couple of engineers working on MD-SAL AuthZ; so, we may not have a fully-productized MD-SAL AuthZ system for Helium. But, we will provide a blueprint and sample code for performing AuthZ at the application/service layer. Also, we seem to have lost an engineer working on OSGi security integration for AAA, but that’s a stretch goal for AAA to start out with. We are on-track with AuthN.
Regards, Liem
|
||||||||
|
|
||||||||
|
OpenDaylight Helium M3 Report Out Template
Phil Robb
Hello Helium Project Contacts and others interested in a solid ODL Helium Release: I would like to remind all of the Project-Primary-Contacts that M3 is next Monday on July 7th, 2014.
The M3 developer irc meeting will be held next Wednesday, July 9th, 2014 at 3:30pm UTC - 8:30am PDT at #opendaylight-meeting. Prior to the developer meeting, all participating projects should update their project plans indicating the status of all deliverables up to and including those designated for M3. For those projects that have not yet done this, please see an example such as the OVSDB Integration project (https://wiki.opendaylight.org/view/OpenDaylight_OVSDB:Helium_Release_Plan).
Some folks have started to send out their M3 report-outs, but I would like to suggest that all projects provide clear and specific status on deliverables that should be present as part of M3. Also, if any of the deliverables are not fully, 100% complete please clearly identify that, and indicate a high-confidence future date when the deliverable will be completed. If you are unable to provide a high confidence date due to unresolved dependencies, a lack of resources, etc. please indicate that as well. Those projects late, but with a high-confidence date will be considered "yellow" and the projects with unresolved issues will be considered "Red".
Here is a proposed template for the M3 Report out. If you have suggested alterations please respond with them. If not, please use this template to submit your M3 Report Out, and please send it to release@....
==== <PROJECT NAME> OpenDaylight Helium M3 Status update. Project Release Plan has been updated and is located here: <URL to Project Plan>
M2 Deliverable Status: Final Release Plan Complete: YES/NO Gerrit/Jenkins merge process successfully pushes project binary artifacts to Nexus repo: YES/NO
M3 Deliverable Status: Continuous Integration Test Working: YES/NO Continuous Integration Testing is where your project has a Jenkins job which will rebuld and retest to an appropriate level when a project you depend on publishes new artifacts to the nexus repo.
Project Documentation has started: YES/NO Project Development Status Summary: Please indicate a summary of deliverables completed for M3 and a RED/YELLOW/GREEN indicator regarding your project's overall status. If YELLOW or RED please indicate why and what can or will be done to return the project to a GREEN status.
== End of Template== Thanks, Phil. -- Phil Robb Director - Networking Solutions The Linux Foundation
(O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb
|
||||||||
|
|
||||||||
|
L2Switch: OpenDaylight Helium M3 Status update
Amit Mandke (ammandke) <ammandke@...>
Hi All,
Project: L2 Switch
OpenDaylight Helium M3 Status update.
Project Release Plan has been updated here: https://wiki.opendaylight.org/view/L2_Switch:SimultaneousReleasePlan2014
M2 Deliverable Status:
Modular Packet Handler: DONE
Ethernet Packet Decoder:DONE
Final Release Plan Complete: YES
Gerrit/Jenkins merge process successfully pushes project binary artifacts to Nexus repo: YES
M3 Deliverable Status:
Endpoint Tracker
: DONE
Create L2Switch Distribution: DONE
Project Development Status Summary:
Over All status: GREEN
-Amit
|
||||||||
|
|
||||||||
|
ODL-SDNi App: OpenDaylight Helium M3 Status update
Rafat Jahan <rafat.jahan@...>
Hi All,
Project: ODL-SDNi App OpenDaylight Helium M3 Status update. Project Release Plan has been updated and is located here: https://wiki.opendaylight.org/view/ODL-SDNi_App:Helium M2 Deliverable Status: SDNi aggregator code to access opendaylight - Base network Service Functions for data to be available with RestAPI: Done Final Release Plan Complete: YES Gerrit/Jenkins merge process successfully pushes project binary artifacts to Nexus repo: YES M3 Deliverable Status: RestAPI to be implemented for topology data retreival from SDNi Aggregator: Done Continuous Integration Test Working: YES Project Documentation has started: YES Project Development Status Summary: Over All status: GREEN Thanks and Regards, Rafat Jahan Tata Consultancy Services Cell:- 9886420332 Mailto: rafat.jahan@... Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Consulting ____________________________________________ =====-----=====-----=====
|
||||||||
|
|
||||||||
|
Openflow Protocol Library: OpenDaylight Helium M3 Status update
Michal Polkorab
Hello,
below you can find Openflow Protocol Library (openflowjava) Helium M3 status update: Project: Openflow Protocol Library
OpenDaylight Helium M3 Status update.
Project Release Plan has been updated and is located here: https://wiki.opendaylight.org/view/Openflow_Protocol_Library:RELEASE_Plan_2014
M2 Deliverable Status:
Final Release Plan Complete: YES
Extensibility support done: YES
Gerrit/Jenkins merge process successfully pushes project binary artifacts to Nexus repo: YES
M3 Deliverable Status:
TLS support done : YES
Continuous Integration Test Working: YES
Project Documentation has started: YES Project Development Status Summary:
All deliverables are GREEN.
Regards
Michal Polkorab
MichalPolkoráb Software Developer Mlynské Nivy 56 / 821 05 Bratislava / Slovakia +421 918 378 907 / michal.polkorab@... reception: +421 2 206 65 111 / www.pantheon.sk
|
||||||||
|
|
||||||||
|
LispFlowMapping: OpenDaylight Helium M3 Status update
David Goldberg <David.Goldberg@...>
Hello,
below you can find LispFlowMapping Helium M3 status update: Project: LispFlowMapping OpenDaylight Helium M3 Status update.
Project Release Plan has been updated and is located here: https://wiki.opendaylight.org/view/OpenDaylight_Lisp_Flow_Mapping:SimultaneousReleasePlan2014
M2 Deliverable Status: Final Release Plan Complete: YES SMR : YES
M3 Deliverable Status: Nothing was planned for M3
Project Development Status Summary: All deliverables are GREEN.
Thanks,
David Goldberg Software Engineer ConteXtream Ltd.
|
||||||||
|
|
||||||||
|
[OpenDaylight Release] Southbound plugin to the OpenContrail Platform M3 Update
Priyanka Chopra <pchopra@...>
Dear All,
This email is to meet the Helium Simultaneous Release Plan requirement to report out status at Milestones (both positive and negative) on Deliverables for that Milestone: https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan#Cross_Project_Milestone_and_Release_Candidate_Reporting
|
||||||||
|
|
||||||||
|
PacketCable PCMM: OpenDaylight Helium M3 Status Update
Thomas Kee <t.kee@...>
Hi,
Below find the PacketCable PCMM (packetcable) Helium M3 status update:
Project: PacketCable PCMM
OpenDaylight Helium M3 Status update.
Project Release Plan has been updated and is located here:
M2 Deliverable Status:
Release Plan: YES
COPS driver connections and all gate messages: YES
Ensure build compliance with new maven build strategy: YES
Complete northbound model and southbound COPS driver: YES
M3 Deliverable Status:
IPv6 compliance : NO
Review and finalize MD-SAL model and external APIs: NO
Junit Test with Soft CMTS working: YES
Checkin github hosted source code to ODL Gerrit: YES
Project Development Status Summary:
All deliverables are a shade of YELLOW.
Regards,
Thomas Kee
|
||||||||
|
|
||||||||
|
BGPCEP Helium M3 Status Update
Dana Kutenicsova -X (dkutenic - Pantheon Technologies SRO@Cisco) <dkutenic@...>
BGPCEP
OpenDaylight Helium M3 Status update.
Project Release Plan has been updated and is located here:
https://wiki.opendaylight.org/view/BGP-LS/PCEP:Helium_Release_Plan
M2 Deliverable Status:
Final Release Plan Complete: YES
Gerrit/Jenkins merge process successfully pushes project binary artifacts to Nexus repo: YES
API design of BGP speaker: NO (ETA 07/18/14) BGP Update message serializer: YES M3 Deliverable Status:
Continuous Integration Test Working: NO
Project Documentation has started: YES
Project Development Status Summary: Create model for AdjRibsIn/Out: YES Support for Segment Routing: YES Support for BGP statistics: NO (lowered priority till M4) Overall status: Yellow - due to high demand on delivering features for PCEP that weren't planned for this release, we are approximately one month delayed in other development Dana
|
||||||||
|
|
||||||||
|
Toolkit: Helium M3 Status
Andrew Kim <h.andrew.kim@...>
Project: Toolkit OpenDaylight Helium M3 Status update
Project Release Plan has been updated here https://wiki.opendaylight.org/view/Toolkit:Helium_Release_Plan
M2 Deliverable Status Release Plan: IN PROGRESS, will hash out by July 18th Basic Archetypes: DONE Draft Templates: IN PROGRESS
Final Release Plan Complete: NO Gerrit/Jenkins merge process successfully pushes project binary artifacts to Nexus repo: YES
M3 Deliverable Status Continuous Integration Test Working: YES Project Documentation has started: YES
Project Development Status Summary: GREEN -Andrew
|
||||||||
|
|
||||||||
|
DLUX: OpenDaylight Helium M3 status update
Harman Singh (harmasin) <harmasin@...>
Hi All,
Project : DLUX
Opendaylight Helium M3 status update.
Release plan of dlux project is updated and available at https://wiki.opendaylight.org/view/OpenDaylight_dlux:Release_Plan_Helium
M2 Deliverable Status:
Final Release plan: done
CSS and application design : done
Node UI : done
M3 Deliverable Status:
Topology UI : Complete
Flow UI : Complete
Statistics UI: Complete
Project Development Status Summary:
Overall Status : Green
We added another task to make UI modular for any external applications. We are planning to finish that in M4.
Thanks,
Harman
|
||||||||
|
|
||||||||
|
AAA Helium M3 status update
Nguyen, Liem Manh <liem_m_nguyen@...>
Hello,
This is the M3 status update for AAA.
AAA Project
Project release plan has been updated and is located here: https://wiki.opendaylight.org/view/AAA:Helium
M2 Deliverable Status
Release plan complete: YES Gerrit/Jenkins merge process successfully pushes project binary artifacts to Nexus repo: NO
M3 Deliverable Status
Continuous integration test: YES Project Documentation has started: YES AuthN framework with token-based authentication: YES IdM APIs: YES SSSD Integration: NO MD-SAL AuthZ: NO Access Policy: NO
Project Development Status Summary
AuthN is green, MD-SAL AuthZ is yellow due to lack of resources.
Thanks, Liem
|
||||||||
|
|
||||||||
|
Controller M3 Status
Ed Warnicke (eaw) <eaw@...>
Controller
OpenDaylight Helium M3 Status update.
Project Release Plan has been updated and is located here: https://wiki.opendaylight.org/view/OpenDaylight_Controller:Helium_Release_Plan#Release_Milestones
M2 Deliverable Status:
Final Release Plan Complete: YES
Gerrit/Jenkins merge process successfully pushes project binary artifacts to Nexus repo: YES
M3 Deliverable Status:
Continuous Integration Test Working: YES
Continuous Integration Testing is where your project has a Jenkins job which will rebuld and retest to an appropriate level when a project you depend on publishes new artifacts to the nexus repo.
Project Documentation has started: - It is not clear what this means, as it doesn’t appear to have any clear definition.
Project Development Status Summary:
MD-SAL: Lazy deserialization from Binding-Independent Format:
DONE
MD-SAL: Datastore Tracer:
DROPPED
MD-SAL: Clustering: Design Documentation Review:
DONE
Reviewed with: Group Based Policy Team, Jan Medved, Robert Varga, Tony Tkacik, Colin Dixon, Prasanna Huddar, Srikar Rajamani, Chandramouli Venkataraman, Sasidharan Sambhasivan
MD-SAL: Clustering: Initial Sharding Manager:
DONE
MD-SAL: Clustering: Distributing Shards in a cluster:
Delayed - To be completed by 7/09/2014
MD-SAL: Clustering: Initial Remote Data Change Notification Manager:
DONE
MD-SAL: Clustering: Initial Remote Routed RPCs:
Delayed - To be completed by 7/09/2014
MD-SAL: Clustering: Initial Notifications:
Delayed - To be completed by 7/18/2014
From M2: Switch over to default use of openflowplugin:
DONE
Overall: Yellow trending to Green.
Ed
|
||||||||
|
|
||||||||
|
TTP M3 Update
Colin Dixon
The Table Type Patterns project is BEHIND schedule. We have yet to deliver either of the deliverables from the M2 and M3 deadline. 1.) Preliminary support for reading/writing JSON TTP files (From M2)2.) Ability to host a set of named TTPs, browse their capabilities, and select interest in them (M3) The next significant challenge will be hitting the API frees on 8/4. We are hoping to do this relatively quickly by adding a YANG description of an Augmentation to FlowCapableNodes to create a TTPCapableNode.
|
||||||||
|
|
||||||||
|
SNMP4SDN Helium M3 status
謝宜玲 <ylhsieh@...>
Folks,
Here is the M3 status update for SNMP4SDN.
SNMP4SDN Project
Project release plan updated here: https://wiki.opendaylight.org/view/SNMP4SDN:Release_Plan_2014
M2 Deliverable Status
Release plan complete: done VLAN configuration: done
M3 Deliverable Status
Flow configuration on ACL: delayed (to be done by M4) Statistics retrieval (and hardware properties retrieval in M4): deferred to Lithium
Project Development Status Summary
Yellow (Flow configuration is currently the main supported function in SNMP4SDN plugin. Flow configuration on Ethernet switch could be done in three locations - forwarding table, VLAN configuration, and ACL; the first two ones are implemented (status as green), and the last one is postponed to M4 (status as yellow).)
Thanks, Christine
This email may contain confidential information. Please do not use or disclose it in any way and delete it if you are not the intended recipient.
|
||||||||
|
|
||||||||
