z.archive.ttp-dev@lists.opendaylight.org | [release] TTP M3 Status

Home Messages Hashtags Subgroups

This group is locked. No changes can be made to the group while it is locked.

Date Date 1 - 2 of 2

[release] TTP M3 Status

an.ho@huawei.com #113 Hi TTP Team, For M3, TTP project has two missing items. Could your team please provide an ETA for when the items can be completed. 1. Added automated system testing (csit) for your top-level features [1]? Link to gerrit patch? 2. Create Beryllium System Test Plan Wiki (#9) for your team. Please take a moment to create one for your project base on the template here [2] or provide an ETA for completion. In the “Feature Pro-activeness”, remember to include any local ports (e.g. TCP port 6633 for openflow) that your feature needs to bind to. Best Regards, An Ho [1] https://wiki.opendaylight.org/view/CrossProject:Integration_Group:System_Test:Step_by_Step_Guide [2] https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template toggle quoted message Show quoted text From: release-bounces@... [mailto:release-bounces@...] On Behalf Of Colin Dixon Sent: Thursday, October 15, 2015 6:33 PM To: release@... Cc: ttp-dev@... Subject: [release] TTP M3 Status See below. Thanks, --Colin Table Type Patterns Functionality Freeze: 1. Final list of externally consumable APIs defined: Yes If you had any Tentative APIs, have they been moved to Provisional or Dropped? Yes: https://wiki.opendaylight.org/view/Table_Type_Patterns/Beryllium/Release_Plan#Externally_Consumable_APIs If any of your Tentative APIs were dropped, have you notified all projects that were expecting them? Yes, but trivially as no projects were formally expecting them Also please list all dropped APIs. Pipeline Snippet Utilities 2. Are all your inter-project dependencies resolved (i.e., have the other projects you were counting on given you what you needed)? Yes If no, please list the features you were expecting that haven't been delivered and the project you were expecting to receive them from. Note that you can only reasonably hold a project to something if you formally asked for it during the release planning process and they acknowledged that ask saying they would do it. 3. Were there any project-specific deliverables planned for this milestone? No If so, were they delivered? n/a Karaf Features Defined: 4. Are all your project's features that are intended for release added to the features.xml and checked into the integration git repository? No, we expect to add an additional driver feature (please provide link to features.xml) https://github.com/opendaylight/ttp/blob/master/features/src/main/resources/features.xml (please provide link to the gerrit patch that checks into the integration git repository) https://github.com/opendaylight/integration-distribution/blob/master/features/index/src/main/resources/features.xml#L81 5. List all top-level, user-facing, and stable Karaf features for your project. * Top-level: odl-ttp-model-rest, odl-ttp-driver (TBD), CLI tools * User-facing: odl-ttp-model-rest, CLI tools * odl-ttp-model-rest: Provides a YANG model (and thus accompanying data store information and REST APIs) for a central repository of TTPs and the TTPs associated with OpenFlow switches. * odl-ttp-driver (TBD): provides a mapping from an application-oriented TTP to a device-oriented TTP. Exact application-oriented and device-oriented TTPs are still being investigated. Documentation: 6. List the kinds of documentation you will provide including at least: * user guide for: od-ttp-model-rest and CLI tools * developer guide for: odl-ttp-model-rest, CLI tools and odl-ttp-driver (TBD) 7. Have you checked in the AsciiDoc outlines to the docs repository? Yes for everything but hte odl-ttp-driver developer guide (link to gerrit patch) https://github.com/opendaylight/docs/tree/master/manuals/user-guide/src/main/asciidoc/ttp and https://github.com/opendaylight/docs/tree/master/manuals/developer-guide/src/main/asciidoc/ttp Integration and Test: 8. Have you started automated system testing for your top-level features. No If yes, link to test report If no, why? We haven't had time yet for the odl-ttp-model-rest, we still aren't quite sure how to write a system test for the CLI tools and we are still developing the odl-ttp-driver. 9. Have you filled out basic system test plan wiki page from template for each top-level feature (karaf and not karaf) and a comprehensive system test plan template including functionality, cluster, scalability, performance, longevity/stability for each stable feature? No If yes, link to test plans If no, why? See above.**
Curt Beckmann #119 Hi An, Apologies for the slow response. We plan to address these items by the Offset 2 M4 milestone, which is currently shown as 11/12 in the Beryllium Release Plan. It’s not clear if this milestone moves as a result of the Beryllium schedule change approved yesterday in the TSC, but either way, we will target 11/12 to deliver the 2 items. I have taken a first step by creating our test report page[1], but have not yet customized it. I have added a link to the Integration list [2], marked as draft. I will begin working on customizing our test report next week as we implement our tests. Curt [1] https://wiki.opendaylight.org/view/Table_Type_Patterns/Beryllium/System_Test_Report [2] https://wiki.opendaylight.org/view/CrossProject:Integration_Group/Project_System_Test_Report toggle quoted message Show quoted text From: release-bounces@... [mailto:release-bounces@...] On Behalf Of An Ho Sent: Wednesday, October 21, 2015 7:06 PM To: Colin Dixon; release@... Cc: ttp-dev@... Subject: Re: [release] TTP M3 Status Hi TTP Team, For M3, TTP project has two missing items. Could your team please provide an ETA for when the items can be completed. 1. Added automated system testing (csit) for your top-level features [1]? Link to gerrit patch? 2. Create Beryllium System Test Plan Wiki (#9) for your team. Please take a moment to create one for your project base on the template here [2] or provide an ETA for completion. In the “Feature Pro-activeness”, remember to include any local ports (e.g. TCP port 6633 for openflow) that your feature needs to bind to. Best Regards, An Ho [1] https://wiki.opendaylight.org/view/CrossProject:Integration_Group:System_Test:Step_by_Step_Guide [2] https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template From: release-bounces@... [mailto:release-bounces@...] On Behalf Of Colin Dixon Sent: Thursday, October 15, 2015 6:33 PM To: release@... Cc: ttp-dev@... Subject: [release] TTP M3 Status See below. Thanks, --Colin Table Type Patterns Functionality Freeze: 1. Final list of externally consumable APIs defined: Yes If you had any Tentative APIs, have they been moved to Provisional or Dropped? Yes: https://wiki.opendaylight.org/view/Table_Type_Patterns/Beryllium/Release_Plan#Externally_Consumable_APIs If any of your Tentative APIs were dropped, have you notified all projects that were expecting them? Yes, but trivially as no projects were formally expecting them Also please list all dropped APIs. Pipeline Snippet Utilities 2. Are all your inter-project dependencies resolved (i.e., have the other projects you were counting on given you what you needed)? Yes If no, please list the features you were expecting that haven't been delivered and the project you were expecting to receive them from. Note that you can only reasonably hold a project to something if you formally asked for it during the release planning process and they acknowledged that ask saying they would do it. 3. Were there any project-specific deliverables planned for this milestone? No If so, were they delivered? n/a Karaf Features Defined: 4. Are all your project's features that are intended for release added to the features.xml and checked into the integration git repository? No, we expect to add an additional driver feature (please provide link to features.xml) https://github.com/opendaylight/ttp/blob/master/features/src/main/resources/features.xml (please provide link to the gerrit patch that checks into the integration git repository) https://github.com/opendaylight/integration-distribution/blob/master/features/index/src/main/resources/features.xml#L81 5. List all top-level, user-facing, and stable Karaf features for your project. * Top-level: odl-ttp-model-rest, odl-ttp-driver (TBD), CLI tools * User-facing: odl-ttp-model-rest, CLI tools * odl-ttp-model-rest: Provides a YANG model (and thus accompanying data store information and REST APIs) for a central repository of TTPs and the TTPs associated with OpenFlow switches. * odl-ttp-driver (TBD): provides a mapping from an application-oriented TTP to a device-oriented TTP. Exact application-oriented and device-oriented TTPs are still being investigated. Documentation: 6. List the kinds of documentation you will provide including at least: * user guide for: od-ttp-model-rest and CLI tools * developer guide for: odl-ttp-model-rest, CLI tools and odl-ttp-driver (TBD) 7. Have you checked in the AsciiDoc outlines to the docs repository? Yes for everything but hte odl-ttp-driver developer guide (link to gerrit patch) https://github.com/opendaylight/docs/tree/master/manuals/user-guide/src/main/asciidoc/ttp and https://github.com/opendaylight/docs/tree/master/manuals/developer-guide/src/main/asciidoc/ttp Integration and Test: 8. Have you started automated system testing for your top-level features. No If yes, link to test report If no, why? We haven't had time yet for the odl-ttp-model-rest, we still aren't quite sure how to write a system test for the CLI tools and we are still developing the odl-ttp-driver. 9. Have you filled out basic system test plan wiki page from template for each top-level feature (karaf and not karaf) and a comprehensive system test plan template including functionality, cluster, scalability, performance, longevity/stability for each stable feature? No If yes, link to test plans If no, why? See above.**

1 - 2 of 2

1

Previous Topic Next Topic

Home Hashtags Subgroups Terms