|
SNBI M3 status
Frank Brockners
SNBI (secure network bootstrapping infrastructure) OpenDaylight Helium M3 Status update. Project Release Plan has been updated and is located here: https://wiki.opendaylight.org/view/SecureNetworkBootstrapping:ReleasePlan
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 Project Documentation has started: YES (see https://wiki.opendaylight.org/view/SNBI_Architecture_and_Design)
Project Development Status Summary: Neighbor discovery Controller: Southbound plugin, discovery phase - status: build successful, green Forwarding element: discovery phase - status: in coding, red Forwarding element code is dependent on portable foundation (associated network model etc.), which is also late (see below). Team is working on a get well plan. Likely neighbor discovery for the FE needs to be pushed out to M4. RegistrarBoot Certificate management infra for controller - status: build successful, green Portable Foundation/Container base image for forwarding elements Publish documentation of portable foundation networking model - status: published – green Base portable foundation docker image in public docker repo - status: plan to publish by Jul/11th, yellow
Overall: Yellow (mostly green for controller pieces, schedule delay for pieces related to the forwarding element)
Frank |
||||||||||||||||
|
|
||||||||||||||||
|
Re: OpenDaylight Helium M3 Report Out Template
Sarath Babu G <sarathbg@...>
Hi,
Update the M3 milestone status for the VTN Project (https://wiki.opendaylight.org/view/OpenDaylight_Virtual_Tenant_Network_(VTN):Helium_Release_Plan).
Thanks, Sarath.
From: release-bounces@... [mailto:release-bounces@...]
On Behalf Of Phil Robb
Sent: Friday, July 4, 2014 2:38 AM To: release@... Subject: [release] OpenDaylight Helium M3 Report Out Template
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
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. ---------------------------------------------------------------------------------------------------------------------------------------------------- |
||||||||||||||||
|
|
||||||||||||||||
|
Dynamic Resource Reservation Project M3 Status Update
Mathieu Lemay
Dynamic Resource Reservation OpenDaylight Helium M3 Status update.
Project Release Plan has been updated and is located here: https://wiki.opendaylight.org/view/Reservation:Helium_Release_Plan
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 Project Documentation has started: NO, we plan to provide guidance on documentation later this week. Project Development Status Summary: - Prototype TL1 Southbound implementation: IN PROGRESS TL1 communication and interaction library: done.
Proper MD-SAL integration: not started. - Information Models: IN PROGRESS
Multi-layer Information Model: done Reservation Information Model: not started
Overall Summary The project was Red because the team has underestimated other work on controller, DLUX and karaf. It is now trending on Yellow, in order to be back on Green by next milestones we plan to take the following items:
- Reduce the scope of this first iteration and drop the advanced scheduling (meaning only immediate reservations are supported, (those that start right away) )
- Allocate additional resources to the project - Initially support only OpenFlow southbound plugin (TL1 and Netconf to be supported only if time allows it)
|
||||||||||||||||
|
|
||||||||||||||||
|
Integration M3 Status
Luis Gomez
Integration
OpenDaylight Helium M3 Status update. Project Release Plan has been updated and is located here: https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Helium_Release_Plan Project Development Status Summary: Test Documentation: Hydrogen test cases available in Testopia DELAYED - Will be completed next week OF Performance Test: Inventory + CBench PARTIAL - Inventory done, CBench in progress Flowmod Test: Flow verifcation test DONE Netconf Test: Test connection to Netopeer Netconf server DONE - Ready but outside LF Neutron Test: Start feasibility study DELAYED - Still gathering info Release Vehicles: Generate Helium Release Vehicles UNKOWN - We do not know release vehicles for Helium yet Overall: Red because of Release Vehicles not defined yet, otherwise yellow. BR/Luis |
||||||||||||||||
|
|
||||||||||||||||
|
Re: OpenDaylight Helium M3 Report Out Template
Sarath Babu G <sarathbg@...>
Hi,
Sorry I missed to update the template in the earlier email.
VTN Project OpenDaylight Helium M3 Status update.
Project Release Plan has been updated and is located here: https://wiki.opendaylight.org/view/OpenDaylight_Virtual_Tenant_Network_(VTN):Helium_Release_Plan
M2 Deliverable Status:
Final Release Plan Complete: YES
Gerrit/Jenkins merge process successfully pushes project binary artifacts to Nexus repo: YES (VTN Manager Module)
M3 Deliverable Status:
Continuous Integration Test Working: YES Integration tests for the OVSDB VTN Neutron integration is in progress. Will be completed by M5.
Project Documentation has started: YES https://wiki.opendaylight.org/view/OpenDaylight_Virtual_Tenant_Network_(VTN):Main
Project Development Status Summary: Enhancement of VTN Neutron support – GREEN Got update from OVSDB team that the API will be modified in the subsequent release. Investigating the same and the support for the same will be added in VTN by M4. Improvement of VTN Coordinator installation – GREEN
Overall status - GREEN
Thanks, Sarath.
From: Sarath Babu G
Sent: Tuesday, July 8, 2014 4:45 PM To: release@... Subject: RE: [release] OpenDaylight Helium M3 Report Out Template
Hi,
Update the M3 milestone status for the VTN Project (https://wiki.opendaylight.org/view/OpenDaylight_Virtual_Tenant_Network_(VTN):Helium_Release_Plan).
Thanks, Sarath.
From:
release-bounces@... [mailto:release-bounces@...]
On Behalf Of 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
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. ---------------------------------------------------------------------------------------------------------------------------------------------------- |
||||||||||||||||
|
|
||||||||||||||||
|
SFC M3 Status
Paul Quinn (paulq) <paulq@...>
Service Function Chaining (SFC)
OpenDaylight Helium M3 Status update. Project Release Plan has been updated and is located here: https://wiki.opendaylight.org/view/Helium_Release_Plan 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: NO Project Development Status Summary: Finalize YANG models: GREEN.
Review and determine southbound plugin protocols and requirements: YELLOW. In progress, should be completed by 7/11/2014
NB API Implementation: GREEN. API generated from YANG models above.
Overlay integration design: YELLOW. In progress. Updated expected 7/10/2014
|
||||||||||||||||
|
|
||||||||||||||||
|
OVSDB Plugin NW Virt M3 Release Plan Status Updates
Brent Salisbury <brent.salisbury@...>
Here is the M3 Helium release updates. Apologies for the delay, we wanted to get community approval in our weekly call this afternoon prior to finalizing it. Thanks for everyone’s hard work up to now and in the coming months. Respect, -Brent |
||||||||||||||||
|
|
||||||||||||||||
|
REMINDER - OpenDaylight Helium M3 Developer IRC Meeting Tomorrow
Phil Robb
Hello Helium Project Contacts: I just wanted to remind everyone that the M3 Developer meeting is tomorrow, Wednesday, July 9th, 2014 at 3:30pm UTC - 8:30am PDT on #opendaylight-meeting. Please plan on attending and bring any topics you would like to have addressed.
One topic of discussion will be around Documentation. All projects are to have started their documentation by the M3 milestone, but we, as a group, need to better define how each project's documentation will fit into the Helium Release documentation as a coherent, and coordinated whole. In addition, the Docs team is currently "RED" due to a lack of people needed to produce the docs overall. Let's see if we can work together to come up with a way to coordinate everyone's documentation contributions and get the docs project out of the RED.
I would like to shout out a HUGE thank you to all of the projects that have sent out their M3 Report-Out emails. The vast majority of projects have reported and I've recently sent a reminder-email to the small number of projects that have not yet reported in. To check the current (M3) status of the project overall, please see the following table on the Helium Release Page: https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan#Participating_Projects
If I got any of those Project-Status updates wrong, feel free to change the wiki and/or let me know. If you have any questions or comments, don't hesitate to reach out to me.
Thanks, Phil. -- Phil Robb Director - Networking Solutions The Linux Foundation (O) 970-229-5949
(M) 970-420-4292 Skype: Phil.Robb |
||||||||||||||||
|
|
||||||||||||||||
|
Re: REMINDER - OpenDaylight Helium M3 Developer IRC Meeting Tomorrow
Ed Warnicke (eaw) <eaw@...>
Could you send out an invite for those of us who just go where our calendars tell us to? :)
toggle quoted message
Show quoted text
Ed On Jul 8, 2014, at 4:47 PM, Phil Robb <probb@...> wrote:
|
||||||||||||||||
|
|
||||||||||||||||
|
Invitation: ODL Helium M3 Developer Meeting @ Wed Jul 9, 2014 9:30am - 10:30am (probb@linuxfoundation.org)
Phil Robb
|
||||||||||||||||
|
|
||||||||||||||||
|
Re: TTP M3 Update
Colin Dixon
Having actually read Phil's e-mail, here's the version using his template. More details can be found on the release plan page linked below. Cheers, --Colin
Table Type Patterns OpenDaylight Helium M3 Status update. Project Release Plan has been updated and is located here: https://wiki.opendaylight.org/view/Table_Type_Patterns:Helium_Release_Plan
M2 Deliverable Status: Final Release Plan Complete: YES Gerrit/Jenkins merge process successfully pushes project binary artifacts to Nexus repo: YES
TTP codec: PARTIAL (expected M4) M3 Deliverable Status: Continuous Integration Test Working: YES Project Documentation has started: YES (architectural), DELAYED (expected M4) (user and developer)TTP registry: DELAYED (expected M4) Project Development Status Summary: YELLOW
|
||||||||||||||||
|
|
||||||||||||||||
|
Re: Invitation: ODL Helium M3 Developer Meeting @ Wed Jul 9, 2014 9:30am - 10:30am (probb@linuxfoundation.org)
Colin Dixon
Are we actually doing this via G+ hangouts or was that just you accidentally forgetting to remove the video call before sending the invitation? Along those lines, will there be a WebEx?On Tue, Jul 8, 2014 at 4:59 PM, Philip Robb <probb@...> wrote:
|
||||||||||||||||
|
|
||||||||||||||||
|
Re: Invitation: ODL Helium M3 Developer Meeting @ Wed Jul 9, 2014 9:30am - 10:30am (probb@linuxfoundation.org)
Colin Dixon
Nevermind. I should read. Cheers,It will be in #opendaylight-meeting and there will be no WebEx or G+ hangout.
|
||||||||||||||||
|
|
||||||||||||||||
|
OpenFlow Plugin M3 Status
Abhijit Kumbhare
Project: OpenFlow Plugin
OpenDaylight Helium M3 Status update. Project Release Plan has been updated and is located here: https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Helium_Release_Plan
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: YES (changes started to be documented on the wiki/bugzilla) Project Development Status Summary: Overall status: Yellow trending to green. Port/Queue Config: Partially done (queue config done, port config will be done M5 as it is low priority than the other tasks like clustering)
Handling of reserve ports: DONE Threading Model & Packet Handling Priority - phase II: DONE as per the plan (but profiling did not yield expected improvements - more investigation needed)
|
||||||||||||||||
|
|
||||||||||||||||
|
Re: (updated email template) OVSDB Plugin NW Virt M3 Release Plan Status Updates
Brent Salisbury <bsalisbu@...>
Added the release plan into the email template. Thanks! --- # Project: OVSDB Plugin # ### OpenDaylight Helium M3 Status update ### -Project Release Plan has been updated and is located here: ### 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 for the plugins OVSDB Library/Schema -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. *Yes -Project Documentation has started: *No, will add to weekly agenda. ### Project Development Status Summary ### * Extensibility for Nicira extensions are the primary blocker. Required NXMs are complete as of patchhttps://git.opendaylight.org/gerrit/#/c/7722/. CSCO/Ed also need an extension so this is helping expedite the availability in ofplugin/ofjava projects. NXAST type extensions cannot be done using Set/Field/OXM/NXM objects so this will need custom serializers/deserializers (maybe experimenter field) to accomplish. * Protos: OVSDB plugin library, NBAPI rework is up next once the library integration into OS/ODL/Neutron is finished this week. * Protos: OF- Implementing a Java API IT and improving how it is presented to the user. * Once the necessary OF/Extensions are in place, OpenStack services LB/FW/etc will be the primary focus and depending on dependencies a mad dash to the end. Thus the yellow status on the project as we look towards the slim margins for timing errors towards release. Regards, -Brent On Jul 8, 2014, at 5:32 PM, Brent Salisbury <brent.salisbury@...> wrote:
|
||||||||||||||||
|
|
||||||||||||||||
|
Yangtools M3 Status Update
Tony Tkacik
Yang Tools OpenDaylight Helium M3 Status update.
Project Release Plan has been updated and is located here: https://wiki.opendaylight.org/view/YANG_Tools:Helium_Release_Plan
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
Project Documentation has started: YES
|
||||||||||||||||
|
|
||||||||||||||||
|
Hydrogen stable
Dana Kutenicsova -X (dkutenic - Pantheon Technologies SRO@Cisco) <dkutenic@...>
Hello,
unfortunately I got late to testing the stable Hydrogen proposal and I've discovered I'd need a few more cherry-picks from yangtools and controller. Namely: |
||||||||||||||||
|
|
||||||||||||||||
|
Hydrogen stable
Dana Kutenicsova -X (dkutenic - Pantheon Technologies SRO@Cisco) <dkutenic@...>
Hello,
(sorry, outlook got weird and send out previous message prematurely). unfortunately I got late to testing the stable release candidate and I discovered that I'd need a few more cherry-picks from yangtools/controller to get PCEP working. Namely: remote: https://git.opendaylight.org/gerrit/8671 remote: https://git.opendaylight.org/gerrit/8672 remote: https://git.opendaylight.org/gerrit/8673 remote: https://git.opendaylight.org/gerrit/8674 remote: https://git.opendaylight.org/gerrit/8675 Tony took care of those, and all of them are already merged to stable branches. Also followup bgpcep commits (merged to stable): https://git.opendaylight.org/gerrit/#/c/8857/ https://git.opendaylight.org/gerrit/#/c/8859/ I'd appreciate if you can do one more spin for the release candidate. Regards, Dana |
||||||||||||||||
|
|
||||||||||||||||
|
Minutes from the OpenDaylight Helium M3 Developer Meeting
Phil Robb
Can be found here.... Phil. -- Phil Robb Director - Networking Solutions The Linux Foundation (O) 970-229-5949 (M) 970-420-4292
Skype: Phil.Robb |
||||||||||||||||
|
|
||||||||||||||||
|
Re: Hydrogen stable
Ed Warnicke (eaw) <eaw@...>
TSC,
toggle quoted message
Show quoted text
We have a request to respin stable/hydrogen due to bugs found and fixed during testing of the
testing period the TSC allowed last week. In discussions on the M3 meeting about doing a respin, there was a request that:
1) The decision for respin be made by the TSC at tomorrows call
2) The release list be notified that that call be made tomorrow.
3) The requestors of the respin are asked to attend the TSC call tomorrow.
release list,
If a respin happens, all Hydrogen projects would be wise to retest the new release candidates.
Personally, I would suggest that if the TSC decides to respin we do it fairly immediately, so I would
also personally counsel that projects be prepared for a respin shortly after the TSC meeting tomorrow (it is
subject to the TSC decision, but if the TSC decides to, its may happen quickly).
Also… if you haven’t tested the current release candidates and fixed any problems you find,
please do so today.
Dana,
Can you attend the TSC meeting tomorrow to talk about the need for respin?
Ed On Jul 9, 2014, at 9:27 AM, Dana Kutenicsova -X (dkutenic - Pantheon Technologies SRO at Cisco) <dkutenic@...> wrote:
|
||||||||||||||||
|
|