Updated list of scenarios with links to results. Note that this list adds two scenarios (ovn, fdio) from Fuel that showed improvements since the first list was published, and retracts one scenario from Apex (ovn), which failed HC.
Scenario Installer Deployment HC os-nosdn-nofeature-ha Apex Y <https://build.opnfv.org/ci/job/apex-deploy-baremetal-hunter/29/> Y <https://build.opnfv.org/ci/job/functest-apex-baremetal-daily-hunter/1/console> os-nosdn-nofeature-noha Apex Y <https://build.opnfv.org/ci/job/apex-deploy-baremetal-hunter/29/> Y <https://build.opnfv.org/ci/job/functest-apex-baremetal-daily-hunter/1/console> os-nosdn-nofeature-noha Fuel@x86 Y <https://build.opnfv.org/ci/job/fuel-deploy-baremetal-daily-hunter/57/> Y <https://build.opnfv.org/ci/view/fuel/job/functest-fuel-baremetal-daily-hunter/25/console> os-nosdn-ovs-noha Fuel@x86 Y <https://build.opnfv.org/ci/view/fuel/job/fuel-deploy-baremetal-daily-hunter/86/> Y <https://build.opnfv.org/ci/view/fuel/job/functest-fuel-baremetal-daily-hunter/46/console> os-odl-nofeature-noha Fuel@x86 Y <https://build.opnfv.org/ci/view/fuel/job/fuel-deploy-baremetal-daily-hunter/85/> Y <https://build.opnfv.org/ci/view/fuel/job/functest-fuel-baremetal-daily-hunter/46/console> os-ovn-nofeature-noha Fuel@x86 Y <https://build.opnfv.org/ci/view/fuel/job/fuel-deploy-baremetal-daily-hunter/83/> Y <https://build.opnfv.org/ci/view/fuel/job/functest-fuel-baremetal-daily-hunter/43/console> os-nosdn-fdio-noha Fuel@aarch64 Y <https://build.opnfv.org/ci/view/fuel/job/fuel-deploy-baremetal-daily-hunter/84/> Y <https://build.opnfv.org/ci/view/fuel/job/functest-fuel-baremetal-daily-hunter/44/console> os-nosdn-nofeature-ha Fuel@x86 Y <https://build.opnfv.org/ci/job/fuel-deploy-baremetal-daily-hunter/57/> Y <https://build.opnfv.org/ci/view/fuel/job/functest-fuel-baremetal-daily-hunter/25/console> os-nosdn-ovs-ha Fuel@x86 Y <https://build.opnfv.org/ci/view/fuel/job/fuel-deploy-baremetal-daily-hunter/86/> Y <https://build.opnfv.org/ci/view/fuel/job/functest-fuel-baremetal-daily-hunter/46/console> os-odl-nofeature-ha Fuel@x86 Y <https://build.opnfv.org/ci/view/fuel/job/fuel-deploy-baremetal-daily-hunter/85/> Y <https://build.opnfv.org/ci/view/fuel/job/functest-fuel-baremetal-daily-hunter/46/console> David On Thu, May 9, 2019 at 7:11 AM David McBride <[email protected]> wrote: > Sure, I can do that. > > I expect that we will have a similar set of artifacts to what is > documented on the download page for the previous release, and what's > reported on the documentation compliance page, minus artifacts from > projects that have withdrawn from the release or left OPNFV, but that > varies somewhat from release-to-release. The largest degree of uncertainty > is with new projects. > > David > > On Thu, May 9, 2019 at 7:01 AM Frank Brockners (fbrockne) < > [email protected]> wrote: > >> David, >> >> >> >> Thanks – could you supply the Jenkins links? >> If I understand your email correctly, you say that apart from the >> scenarios, we don’t really know what we’d release, correct? >> >> >> >> Thanks, Frank >> >> >> >> *From:* David McBride <[email protected]> >> *Sent:* Donnerstag, 9. Mai 2019 15:51 >> *To:* Frank Brockners (fbrockne) <[email protected]> >> *Cc:* TSC OPNFV <[email protected]>; Bin Hu <[email protected]>; >> TECH-DISCUSS OPNFV <[email protected]> >> *Subject:* Re: [opnfv-tech-discuss] status of Hunter release #hunter >> #release >> >> >> >> Frank, >> >> >> >> For the past several releases, I've relied on deployment and health check >> status for each scenario as reported by Jenkins. Scenario owners consider >> all test results and decide whether to release and communicate that intent, >> for each scenario, on the scenario status page. >> >> >> >> If projects submit an intent-to-participate, and don't withdraw from the >> release, then I presume that they will have deliverables. We don't require >> projects to provide a comprehensive list of deliverables in their release >> plan, so I don't have that information, aside from what's reported on the >> scenario status page, and the documentation compliance page. >> >> >> >> David >> >> >> >> On Thu, May 9, 2019 at 2:54 AM Frank Brockners (fbrockne) < >> [email protected]> wrote: >> >> David, >> >> >> >> Thanks for the summary. To be able to form an opinion on how to vote, >> could you supply the following additional information? >> >> >> >> On the scenarios: Could you supply a pointer to the test results? E.g. >> http://testresults.opnfv.org/master/functest/status-apex.html is found >> empty. >> >> >> >> On the additional artefacts: Could you supply a list of the artefacts you >> refer to below along with the draft documentation that we are planning to >> release? Without that info it is a little difficult to understand what the >> release will comprise and whether the listed projects will indeed supply >> something that is consumable. E.g. FDS, despite listed, will not release >> any artefact for Hunter. >> >> >> >> Thanks, Frank >> >> >> >> *From:* [email protected] < >> [email protected]> *On Behalf Of *David McBride >> *Sent:* Mittwoch, 8. Mai 2019 22:49 >> *To:* TSC OPNFV <[email protected]> >> *Cc:* Bin Hu <[email protected]>; TECH-DISCUSS OPNFV < >> [email protected]> >> *Subject:* [opnfv-tech-discuss] status of Hunter release #hunter #release >> >> >> >> Team, >> >> >> >> I took an action in Tuesday's TSC meeting to publish the status of the >> Hunter release. >> >> >> >> The following scenarios are passing deployment and health check: >> >> >> >> *Scenario* >> >> *Installer* >> >> os-nosdn-nofeature-ha >> >> Apex >> >> os-nosdn-nofeature-noha >> >> Apex >> >> os-ovn-nofeature-ha >> >> Apex >> >> os-nosdn-nofeature-noha >> >> Fuel@x86 >> >> os-nosdn-ovs-noha >> >> Fuel@x86 >> >> os-odl-nofeature-noha >> >> Fuel@x86 >> >> os-nosdn-nofeature-ha >> >> Fuel@x86 >> >> os-nosdn-ovs-ha >> >> Fuel@x86 >> >> os-odl-nofeature-ha >> >> Fuel@x86 >> >> >> >> Other scenarios found on the scenario status page, >> <https://wiki.opnfv.org/display/SWREL/Hunter+Scenario+Status> planned >> for Hunter 8.0, but not listed here, will be deferred to Hunter 8.1, due to >> deployment or HC failures. >> >> In addition, the following projects will be providing artifacts for the >> Hunter release: >> >> Apex >> >> Barometer >> >> Bottlenecks >> >> C-RAN >> >> Calipso >> >> Clover >> >> Container4NFV >> >> Doctor >> >> Edge Cloud >> >> FDS >> >> Fuel >> >> Functest >> >> High Availability >> >> IPv6 >> >> NFVBench >> >> OPNFVDOC >> >> OVN4NFV >> >> SampleVNF >> >> SFC >> >> SNAPS-OO >> >> Stor4NFV >> >> StorPerf >> >> VSPerf >> >> Yardstick >> >> >> >> Let me know if you have any questions. >> >> >> >> David >> >> >> >> -- >> >> *David McBride* >> >> Release Manager, OPNFV >> >> Mobile: +1.805.276.8018 >> >> Email/Google Talk: [email protected] >> >> Skype: davidjmcbride1 >> >> IRC: dmcbride >> >> >> >> >> -- >> >> *David McBride* >> >> Release Manager, OPNFV >> >> Mobile: +1.805.276.8018 >> >> Email/Google Talk: [email protected] >> >> Skype: davidjmcbride1 >> >> IRC: dmcbride >> > > > -- > *David McBride* > Release Manager, OPNFV > Mobile: +1.805.276.8018 > Email/Google Talk: [email protected] > Skype: davidjmcbride1 > IRC: dmcbride > -- *David McBride* Release Manager, OPNFV Mobile: +1.805.276.8018 Email/Google Talk: [email protected] Skype: davidjmcbride1 IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#23124): https://lists.opnfv.org/g/opnfv-tech-discuss/message/23124 Mute This Topic: https://lists.opnfv.org/mt/31547970/21656 Mute #release: https://lists.opnfv.org/mk?hashtag=release&subid=2783016 Mute #hunter: https://lists.opnfv.org/mk?hashtag=hunter&subid=2783016 Group Owner: [email protected] Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
