...
- RI Labs - Intel Lab(?)
- POD10 (CNTT RI PoC) - will be used for initial install of OS via AirShip
- Clarification needed as to why we can start on 15 in parallel or first → for PoC, installation validations, not anticipated to impact POD15 delivery cycle
- https://wiki.opnfv.org/display/pharos/Intel+POD10
- POD15 (CNTT RI target state) - Intel lab utilized: https://wiki.opnfv.org/display/pharos/Intel+POD15
Who needs access?
- Test | Validation | Framework: Rajesh/Sridhar, Mehment/Kyle, Cedric, Pierre (placeholder)
→ Lead Mike to confirm w/ Cedric - Installers: Sridhar (confirm if he will work with AirShip OPNFV install process), Luc, Mike/Kyle/Mark → Lead Sridhar
- Lab Support / Admin (SAs): Trevor - confirm SA role and responsibility (h/w) → Lead Trevor
- Test | Validation | Framework: Rajesh/Sridhar, Mehment/Kyle, Cedric, Pierre (placeholder)
- Lab Access - overview & instructions (POD15)
- VPN > Jump > POD/hosts
To request VPN access please follow Wiki instructions and assign the ticket to Gustave Hellman
https://wiki.opnfv.org/display/pharos/Intel+Labs+VPN+Quickstart
- https://help.github.com/en/articles/generating-a-new-gpg-key → GPG key generation
https://help.github.com/en/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent → SSH key generation
https://jira.opnfv.org/browse/INFRA-354 → Example Request
- Is there a form to Extract RA requirements, and use for installation?
- No formal mechanism, or form, (yet) to extract the RA from the CNTT material.
- Will leverage PDF and SDF descriptor files & file format for now, along with Intel specific lab documents/formats needed for lab setup.
- Who will assist with Airship installation? (10/16)
- Sridhar, Mark/Mike
- POD10 (CNTT RI PoC) - will be used for initial install of OS via AirShip
- Delivery Plan for RI
- Labs Setup / POC to target state
- Create Test Plan
- Finalize Test Harness/Framework
- Manifest Requirements (for POD15 install)
- Results Collection & Normalization
- Deferred: Discuss Ch 8 re-write
- Offline discussion: Open Issues
- New Issues | PRs - confirm ownership / issue & changes
- Kagreenwell issue 270 patch #384 - https://github.com/cntt-n/CNTT/pull/384
- Define Compliance (Issue 363/Trevor) - https://github.com/cntt-n/CNTT/issues/363 - for CVC/OVP Terms and Definition comparison w/ CNTT use of similar terms to ensure alignment.
- Clarify that Certification is not possible as the open source team cannot "commercialize" a product (Issue 375/TBD) https://github.com/cntt-n/CNTT/issues/375
- Update Methodology with clear demarcation of CNTT vs. Community/Supplier Test Responsibilities (Issue #376/TBD) https://github.com/cntt-n/CNTT/issues/376
- GitHub:
- New Issues | PRs - confirm ownership / issue & changes
- Offline discussion: Open Issues
- Next Steps
- RI Labs - confirm availability (10/9), attempt AirShip installer (Sridhar, Mark, Mike, 10/16), confirm & correct deployment issues (10/16-EOM Oct)
- Continued Documentation Revisions & Reviews
Actions:
- 10/2 9 Meeting
- Owner: All → Review/respond to GitHub issues by
- Owner: Impacted Individuals (Test, Installer, Support) - needing access to POD15, request/receive access by
- Owner: Mike - confirm with Cedric O. (Orange) if he will be the "lead" to centralize Implementation & Adoption of Test Hardness/Framework efforts on/by
- Owner: Rajesh - confirm with Sridhar (Spirent) if he will be the "lead" to centralize s/w deployments on/by
- 10/2 Meeting
- Owner: All → Review/respond to GitHub issues by
- Owner: All → Continue adding/editing content to Ch 8 (open Issues, generate PR) by
- Owner: Mike → Contact Bin Hu to open JIRA ticket to formalize use of Intel lab/POD(s) for RI 1.
- (In progress) Sent email requesting support (10/2)
- Owner: Mike → open a PR for minor Lab Req changes from 4x compute nodes to 10x based on need to support B/N/C flavors (2x nodes each)
- Owner: Mike (and Trevor) → open an Issue (#363) to track comparison and confirmation of terms utilized in the Test Chapter align with OVP/CVC (assigned to Trevor)
- Owner: Mike → open new Issues to track discussion and resolution to the following items:
- Define Compliance (Issue 363/Trevor)
- Clarify that Certification is not possible as the open source team cannot "commercialize" a product (Issue 375/TBD)
- Update Methodology with clear demarcation of CNTT vs. Community/Supplier Test Responsibilities (Issue #376/TBD)
- 9/18 Meeting
- Owner: All → Review/respond to GitHub issues by
- Owner: All → Continue adding/editing content to Ch 8 (open Issues, generate PR) by
- 9/11 Meeting
- Owner: All → Review/respond to GitHub issues on priority for Botrange - burn down issues by
- Owner: All → Requesting all team members to review/comment on 8.7 between 9/11-9/17, for discussion 9/18.
- 9/4 Meeting
- Owner: All → Requesting all team members to review/comment on 8.6 between 9/3-9/11, for discussion 9/11.
- Owner: Mike Fix (AT&T) - Verify Validation/Verification/Certification is consistent with CVC verbiage
- Owner: Murtuza Khan (AT&T) - Add additional test case descriptions
- Owner: Kyle Greenwell (Verizon) - generate a PR to merge w/ Master
- 8/28 Meeting
- Done! Add Labels to GitHub Issues → to help with Search (Owners: All, but primarily Mike, Kyle) (recommendation from Kelvin, Nokia)
- Done - but, added to 8.7.9! Add Murtuza Khan assessment of Test Cases/Harness (in relation to Functest) on Wiki page → under consideration (Owner: Murtuza K)
- Done - but, need contributor support to assess. Add {Name} XCI --> include to Etherpad installer project gap analysis → done (Owner: Mike Fix; will also inform CNTT internal Ch 8 team on 8/28 about the new Installer effort needing review)
- Owner: ALL → Requesting all team members to review/comment on next sections 8.4-8.6 (changed to 8.5) by 9/3 for discussion 9/4.
...