Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Each initial blueprint is encouraged to take on at least two Committers from different companies
  2. Complete all templates outlined in this document
  3. A lab with exact configuration required by the blueprint to connect with Akraino CI and demonstrate CD. User should demonstrate either an existing lab or the funding and commitment to build the needed configuration.
  4. Blueprint is aligned with the Akriano Akraino Edge Stack Charter
  5. Blueprint code that will be developed and used with Akraino repository should use only Open Source software components either from upstream or Akriano Akraino projects.
  6. For new blueprints submission, the submitter should review existing blueprints and ensure it is not a duplicate blueprint and explain how the submission differs . The functional fit of an existing blueprint for a use case does not prevent an additional blueprint being submitted.

...

Below is a sample Blueprint template defining an Akriano Akraino species. The full template will be maintained on the Akraino Wiki.

...

  • The Validation labs should be able to connect to Akriano Akraino Edge Stack CI hosted by LF to pull in Akraino blueprints for the validation. Necessary Firewalls can be opened by the Akriano Akraino Community on request.
  • All 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 Validation labs should be declared and information should be documented in the wiki
  • All the 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.

...

Submission of results to the Akriano Akraino community is optional in case of commercially sensitive applications.

...

A coordinator can act as the ambassador to external upstream communities in communicating the requirements need to be addressed in the upstream community on behalf of Akriano Akraino Feature or Blueprint project. TSC can appoint either Akriano Akraino level or project level coordinators to facilitate upstream coordination work. Coordinators can act as a technical liaison only and cannot represent strategy aspects of the Akriano Akraino which will be handled by TSC.

...