CI Evolution description has been initiated in Brahmaputra.
The complete description can be found in CI Evolution
Phase 1 and 2 aimed to be implemented for Danube.
|Infra||This effort provides a common configuration file for installer and test projects to use||Infra WG Discussions|
|Pharos Dashboard||Infra||a tool for community to request hardware resources in Pharos labs||Pharos Dashboard|
Proposal to reduce the number of scenarios in a release(Ulrich Kleber)
|Slide deck Scenario Considerations|
Creation of a testing landing page allowing any test project to expose test cases and associated constraints
Automatic creation of a catalog based on Testing Database
Qtip Re-scoping to address results post-processing and benchmarkingResult consolidation
|Introduction of Stress tests||Test||Lots of tests are run including qualification tests. Frameworks (Yardstick, Rally,..) are available but no stress tests run towards the System Under Test||Introduction of first load/stress tests|
|Documentation||Documentation||Documentation too segmented per project. it is very hard for a new user to know where to start. And even umbrella documents per domain (installation, infrastructure, feature, testing) is not very consistent.||An effort should be done on documentation. For each release all the projects created their own documentation (user guide, release note, installation guide,..). For a new user it is not easy to read everything and get a global overview. For instance there is no global "Installation" or "Testing" documentation. An effort should be made in Danube to provide more "generic" documentation. This would be helpful in identifying features, test cases without having to dive into each project documentation|
|MANO Integration pilot||Integration Pilot||MANO stack Integration pilot in Danube requires identifying ways and means to enable MANO modules to integrate with OPNFV VIM||An effort is made in Danube to add nfvo and vnf artifacts through upstream OPEN-O and OpenBaton and Juju over OPNFV VIM and test sample vnf(vIMS) through functest This can be cleaned for consistency across different stacks in future releases|
|Test cases recommandation for the compliance||Test and dovetail||in order to show the value of the OPNFV, the test gourp can help to recommande the test cases for the OPNFV compliance||test cases in the compliance set will be important for the OPNFV and will cover the test cases in the test projects and features projects.||Dovetail Test Areas and Test Cases|