Meeting Logistic:
Every Wed. at UTC 13:00-13:30
Attendee List:
- Qiao Fu (China Mobile)
- Michael Fix (AT&T)
- Jim Baker
- Mark Shostak (AT&T)
Goals of 11/13 Meeting:
- Prague F2F schedule planning
- General RI WS updates: fundamental concepts, major progress, roadmap, challenges, collaboration with OPNFV ...
- Installer description file updates and joint discussion with Pharos/Infra WG
- POD implementation updates, progress and challenges
- LAB updates, requirements, status and progress
- Format
- Short Description: One line description of topic
- Detailed Description: Detailed description of topic
- Topic Leader: name 1, name 2, ...
- Estimated Audience (Participant?) Size (1-15 / 15-30 / 30-50 / >50):
- Interested In Attending: If you are interested in this discussion and would like to participate in it, please add your name and email here (one name/email per line please). We'll use this information when building the schedule so that we minimize overbooking people where possible.
- Status of POD10
- Success
- Requirements extraction from RM/RA
- Use of PDF
- Plans/dates for POD15
- Approve PRs
- Assign open issues: 1 Lab, 3 Dev (see links below)
- Verify owners
*******************************************
Detailed Meeting Agenda:
- General Admin
- RI Documentation - https://github.com/cntt-n/CNTT/tree/master/doc/ref_impl/cntt-ri
- To be written (completed) with the Jan CNTT Release
- Run Book (GitHub - RI Ch07 - aka Cookbook for lab setup, deployment and validation)
- To be written (compiled, completed) with the Jan CNTT Release
- Will be part of RI Ch07 deliverable
- Consists of
- Pre-Requisite(s): Bare-metal validations confirming delivery, rack, stack, of env is "ready" for software deployments (e.g. BIOS, firmware, boot order, health, disk config, port / socket validations, MAC/NIC status, etc)
- a) RA Requirements Gathering process
- b) Infra Requirements and Selection Process
- c) Access & Connectivity
- d) Descriptor file &/or Manifest creation (data elements, use/implementation)
- e) Deployment Installer & Install Steps
- f) Deployment Validations
- ...others?
- RI Documentation - https://github.com/cntt-n/CNTT/tree/master/doc/ref_impl/cntt-ri
- Work-stream
- Core
- Lead: Fu Qiao
- Issues: six(6) → https://github.com/cntt-n/CNTT/issues?q=is%3Aopen+is%3Aissue+label%3A%22RI+1+Core%22
- PRs: five(5) → https://github.com/cntt-n/CNTT/pulls?q=is%3Apr+is%3Aopen+label%3A%22RI+1+Core%2
- Status
- Tasks (Work in progress)
- Creation of PDF/SDF Templates
- Hand-off to RC WS
- Lab Setup
- Lead: Rajesh Rajamani
- Issues: 1 unassigned, 4 total - https://github.com/cntt-n/CNTT/issues?q=is%3Aopen+is%3Aissue+label%3A%22RI+1+Labs%22
- PRs: zero(0) → https://github.com/cntt-n/CNTT/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+label%3A%22RI+1+Labs%22+
- Status
- POD10 (CNTT RI PoC) - will be used for initial install of OS via AirShip
- https://wiki.opnfv.org/display/pharos/Intel+POD10
- Status
- Manifest Validation(s) - Sridhar to provide status and its relation to OPNFV-AirShip status/discussion
- Jenkins setup? (Cedric) Jobs written. Waiting for slave from LF. Working with Jim to get traction. Support ticket opened. And, open GitHub issue.
- POD15 (CNTT RI target state) - end state lab for RI 1.0
- https://wiki.opnfv.org/display/pharos/Intel+POD15
- Status:
- Target date to start base install? (Rajesh) Provide date for install.
- What about the creation/use of PDF/SDF? (Fu Qiao) Take back to Core Team for how to incorporate/start these consumables.
- POD10 (CNTT RI PoC) - will be used for initial install of OS via AirShip
- Tasks (Work in progress)
- PoC on Trial Lab
- POD10
- Confirm availability (10/9)
- Confirm access (10/16)
- Perform AirShip installer (owner | date)
- Validate install status & env health (smoke test) (owner | date) → In progress (11/6)
- Confirm & correct deployment issues - tune manifest (10/16-EOM Oct) (owner | date)
- POD10
- Implementation on Target Lab
- POD15
- Confirm availability (10/9)
- Confirm access (10/16)
- Perform AirShip installer (owner | date)
- Validate install status & env health (smoke test) (owner | date)
- Confirm & correct deployment issues - tune manifest (10/16-EOM Oct) (owner | date)
- POD15
- PoC on Trial Lab
- Dev
- Leads: Cedric Ollivier, Rex Lee and Lei Huang
- Issues: 3 unassigned, 10 total → https://github.com/cntt-n/CNTT/issues?utf8=✓&q=is%3Aopen+is%3Aissue+label%3A"RI+1+Dev"+
- PRs: https://github.com/cntt-n/CNTT/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+label%3A%22RI+1+Dev%22+
- Status
- See above & below for POD10 and POD15 status, and action items below.
- Tasks (Work in progress)
- Item 1
- Item 2
- Item 3
- Core
AOB (Any other Business):
- Discussed the need to complete RI documentation by Jan F2F
- Also, discussed the need to complete the "Run Book" by Jan F2F - which will be Ch 7 of the RI documentation
- Bare metal validations (manifest checks w/ h/w or lab delivery) → needs to be added to the Run Book
- Gap? Pre-existing process/validations? → there are post software deployment validations, but no validations to date to confirm the bare metal delivered is ready for s/w deployments
- This will be included as a pre-req in the RI Ch07 documentation
- POD10 deployment - complete?
- POD10 software is deployed
- However.. the AirShip deployment installer and manifests were (are) specific to POD17
- There is AirShip project discussions underway to make the installer generic so it can be used across any POD; for now, it's been manually configured for POD10
- ETA is ~11/17-11/20 for the automated deployment change can be done and tested, and possibly implemente
- Functest API test - status? green light?
- Cedric received the green light today to run Functest, less the CICD scripts to perform the deployment
- The deployment+validation steps will not be run until the AirShip generic installer parameters have been created and tested
- ETA for Functest readout is by EOW (11/8)