Companies or products are certified for Akraino blueprints if logs are pushed to Akraino Nexus servers, and passed any Akraino Release. Security Badges and System Badges are given through partnered certification program used by blueprints.

Akraino Apps can run on shared community lab, private lab, or cloud infrastructure like GCP, Google Edge Cloud, AWS, Tencent Cloud, Equinix, etc, with or without Public Cloud Edge Interface (PCEI) Blueprint Family.

################ FOR DISCUSSION ONLY ####################

Purpose and Principles

Akraino Certification Program is intended to enable infrastructure and service providers certify their products and capabilities for running Akraino Blueprints while satisfying requirements of the Akraino Release qualification established by the Technical Steering Committee.

In principle, Akraino Blueprints span various architecture domains (e.g. Public Cloud, Private Cloud, Device Edge, Network Edge, Enterprise Premises), a variety of device, server, network hardware, as well as visualized infrastructure (clouds), operating systems and virtualization environments. Akraino Blueprints, in many cases, are based on a Hybrid/Multi-Cloud Architecture that often combines infrastructure elements from multiple architecture domains.

The Akraino Certification Program Principles

1. Best industry practices. The certification process of individual infrastructure components that are used to support Akraino Blueprints must follow best known industry practices in hardware and software integrity, security, performance and management/observability.

2. Hybrid/Multi-Cloud Architecture. For Blueprints that rely on Hybrid Architectures, the certification process should ensure that the individual certified elements can be assembled into a Hybrid/Multi-Cloud Architecture even if the individual elements are from different providers (e.g. hardware, edge, cloud, devices).

3. Security. At the minimum, the Certification Process must comply with Akraino BluVal requirements for hardware, os, virtualization.

4. CI/CD. The certified solution should comply with Akraino CI/CD requirements.

5. Completeness of the certified solution. The outcome of the certification process must result in a complete and tractable solution where all individual components comply with the certification requirements.

6. Performance...

7. Usability. The certified solution should provide "easy" deployment and installation capabilities even if the solution involves multiple providers/components.

Certification Process

At this time this section is used to collect questions to be addressed in order to develop the certification process.

1. Blueprint selection.

   1. Do certification program applicants select blueprints to be certified against?

   2. Will the certification program require applicants to certify against ALL approved blueprints?

2. Component certification.

   1. Would a certification program applicant have an option of offering individual components for certification, e.g. IoT device, servers, network, software?

   2. If yes, then whose responsibility to ensure that the complete solution is also certified?

3. Who initiates certification process.

   1. Will individual Blueprints decide to initiate the certification process and select the applicants?

4. Certification tracking and badge awards

   1. Will applicants perform self-certification?

   2. Will there be a need for an Akraino sub-committee?

5. Recertification and Release alignment.

   1. Will there be a recertification requirements?

   2. Will there be a requirement to re-run certification for new Releases?

############## FOR DISCUSSION ONLY #################

Example

VNF Certification Lifecycle

Security Badges

https://www.psacertified.org/

https://openssf.org/

System Badges

https://developer.arm.com/architectures/system-architectures/arm-systemready

Certified List