Anuket Project

Meeting 041621

Owned by Brandon Wick
Last updated: Apr 18, 2021

Attendees

Scot Steele (AT&T) Brandon Wick Heather Kirksey Jim Baker Bob Monkman (Deactivated) Beth Cohen Jill Lovato Anjali Goyal

Agenda

  • Anuket & EUAG
  • Anuket Assured Badging
  • Anuket Ambassador Logo

Anuket & EUAG

Anuket was a topic on the last EUAG call

  • Joint EUAG / Anuket session for June LFN Developer & Testing Forum. Beth to help propose and run it. 
  • Randy Idea: Need for HW availability and abstraction (RM)

Assured Badging Categories 

Badging Proposal: https://docs.google.com/document/d/1ei36v-gW0dE9p1J2PVQ55Cesxe2QRKEB6_g11wdDucE/edit#

CVC came up with Badging Proposal write up with problem statement.

There are currently many more tests based on Heat than Tosca. ONAP is more Tosca integrated. If going broader, we need to adopt the standards of neighboring communities (application ecosystem), e.g. CNCF & Helm 3. 

Performance and Benchmarking str not yet included. We need to think about how this could be applied in the future. 

Interop means deploying on RC1, RC2 with some Functest integration.

Categories of proposed “Anuket Assured” Badges:

Proposed categories have been aligned with the taxonomy of the CNTT efforts and include:

  • VM Platform and Infrastructure (Anuket RC1)
  • Cloud Platform and Infrastructure (Anuket RC2)
  • VNF workload (Anuket RC1)
  • CNF workload  (Anuket RC2)

In addition to these, additional categories are:

  • CNF Conformance (CNCF based tests)
  • ONAP *NF Compliance and Lifecycle  - VNF exists today, CNF will likely be released as part of the ONAP I-release.

New badging needs to be extensible. Lab badging separate criteria. We should encourage lab participation. 

Current badges were shown. Mapping to releases was indicated via a Month/Year Date. This might trigger some pushback from vendors, e.g. perceptions of an older badge. 

An example from Cloud Foundry was shown. Certified Distros + other categories with icons: https://www.cloudfoundry.org/the-foundry/.

Benefit: Communicates a good deal of info, w/o communicating too much in the badge itself. 

We need some very high level badges + clean website to subdivide the categories + potential landscape integration. 

We also need to understand and communicate the value of the program/badge (WIIFM). There was consensus on this point.  

There should be a good way to expand this via cottage industry players (e.g. integrators). Idea for Anuket: Need to update every release about what people are doing with each release. Scott/Bob to help with this. 

Group proposal: Smaller number of top level badges e.g. Infra & Workload and supplement with topic icons indicating areas of applicability. The date the badge is received should be shown in the portal, not on the badge. Labels like "CNF" "VNF" will be shown on the site (not on the badge).

Brandon & Heather to take these recommendations to the LF CS team so start working out how the badges and icons could work together. 

Anuket Ambassador Logo

Brandon showed a first draft of the Anuket Ambassadors badge to the group. It was determined that we don't need both a logo and badge and that the badge should be enough. A dark background was preferred overall, but perhaps with a different background color. The gray circle around the badge should be replaced with a different color. Brandon will take these changes to CS and send prepare a second rev.

The group will meet again in 2 weeks.