...
Multiple labs will be used to validate Akraino projects to ensure production quality of blueprint and/or feature project releases. The Community CI lab is owned by the Akraino community and LF. In addition a number of Edge FLock Validation labs are owned by an Akraino community company, organization or participant.
...
An automation framework should be used for test procedures and leverage existing test automation suites for upstream projects as required. It is the responsibility of the blueprint submitter to ensure that the Edge Flock Validation and Community CI labs can support comprehensive validation of the blueprint and cover all use case characteristics.
...
A full CD that works with the Akraino CI pipeline should be included in the validation project.
3.2.2.3.2 Blueprint and application testing in Akraino Edge
...
Validation lab
Akraino Edge flock Validation labs are owned by an Akraino community company, organization or participant.
The Flock Validation labs can be owned and operated by the supplier of the lab with limited access or no access to the hardware but results of the validation testing need to be shared to the community.
TSC will propose a subcommittee to maintain and coordinate the Flock Validation labs.
Blueprint, application and VNF testing may be performed over a number of Flocks Validations labs concurrently in a coordinated manner as required.
- The Flock Validation labs should be able to connect to Akriano Edge Stack CI hosted by LF to pull in Akraino blueprints for the validation. Necessary Firewalls can be opened by the Akriano Community on request.
- All Flock Validation labs should be available most of the year for the community use and if the lab is not used for validation more than 3 consecutive months then it will be removed from the community list.
- Hardware and Network configuration used within the Flock Validation labs should be declared and information should be documented in the wiki
- All the Flock Validation labs addition, modifications or removable need to be approved by TSC
- All historic results (minimum of 1 year) of blueprint validation, Applications and VNF testing should be maintained in the wiki.
...
- The lab configuration should support functional, performance, security, and other test cases for the blueprint and cover the full stack for the blueprint.
- Any license or support beyond the Community supplied software should be funded, owned and operated by the flock Validation supplier
Open source test tools and vendor tools with appropriate configurations should drive test traffic profiles that mimic in-scope use cases. Akraino coordinators will engage upstream open source communities to get access to upstream community labs for the Akraino blueprint test team. The submitter is responsible to establish access to necessary vendor labs.
...
Akraino blueprint releases ensure that applications and virtual network functions (VNFs) can on-board and operate effectively on the Akraino solution. Flock Validation labs can be further used for the validation of Edge applications and VNFs.
...