...
- The Flock 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 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 labs should be declared and information should be documented in the wiki
- All the Flock 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.
3.2.2.3.2.1 Blueprint 1 Blueprint testing
The test plan and associated test cases to validate the blueprint will be published on the Akraino wiki and reviewed by blueprint stakeholders.
...
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.
3.2.2.3.2.2 Application 2 Application and VNF testing
Akraino blueprint releases ensure that applications and virtual network functions (VNFs) can on-board and operate effectively on the Akraino solution. Flock labs can be further used for the validation of Edge applications and VNFs.
...