...
- RI Delivery Status
- RI Labs - Intel Lab
- Target Labs have been identified (Intel Labs POD10 and POD15)
- POD10 and POD15 were made available for access & installation on/by 10/9
- By EOD 10/15, access requests were being processed and initial connectivity attempts (by Mike Fix) were successful
- Additional details
- 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 confirmed Cedric can lead this area - Installers: Sridhar (confirm if he will work with AirShip OPNFV install process), Luc, Mike/Kyle/Mark → Lead Sridhar confirmed will lead this area
- Lab Support / Admin (SAs): Trevor - confirm SA role and responsibility (h/w) → Lead Trevor confirmed will lead, but caveat that this is limited support
- Test | Validation | Framework: Rajesh/Sridhar, Mehment/Kyle, Cedric, Pierre (placeholder)
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
- POD10 (CNTT RI PoC) - will be used for initial install of OS via AirShip
- RI Labs - Intel Lab
Meeting Minutes:
meeting update from now on
Fuqiao said 1. RI and RC calls are sharing the 1h for now, the situation will change from probably for next week, this meeting is dedicated for RI.
Mike will set up another meeting for RC.
Fuqiao:
Basic introduction about project CNTT-RI background.
this meeting is intended to work for RI stream.
discussion about the CNTT specific topic??
discussion about the wiki organization:
Fuqiao: LFN wiki created & shared and under LFN tree is quite well.
opfnv wiki: asked for creating the page, who is in charge that?
LFN wiki? opnfv wiki? link one with another?
document management:
Fuqiao:RI document will be in CNTT repository?
Fuqiao:expecting initial wiki page,in github?
Rabi: document propose better put into github directly.
testcase manangement:
Rabi:test case should map to requirement?
Ollivier: propose test case should be put inside the project? like ONAP
Cooper: test case and additional test case need a mapping considering the something like requirements?
opnfv-tsc and CNTT-RI relationship:
- Fuqiao: this weekly meeting mainly focus on CNTT-RI; opnfv-tsc is not related to CNTT-RI project.
- Jim: propose separate the opfnv-tsc meeting from CNTT-RI meeting too.
Others:
CNTT STREAM confluence page introduction, some rule introduction.
. Will send out email notice and calendar invite
2. This call is for the combined team for RI WS and OPNFV new project
3. Will use OPNFV wiki as main page to keep minutes, and will reference with each other from the LFN wiki
4. Document for RI will go to CNTT Github and will follow CNTT release cycle. Code for RI will probably go into installer projects and testing projects within OPNFV, and will follow OPNFV release cycle
5. OPNFV project is suggested to change a new name. After the name is determined, Jim Baker will help create official project page
6. Jim Baker asked about the weekly report at OPNFV TSC. Fu Qiao suggested it should be a report for the CNTT in general, not the responsibility for a single project
7. Mike lead the group to go through the github issues for RI and RC WS. Will proceed the WS work using github. Mike will update the useful link in the minutes page
8. Next meeting will be for the working items, and for specific people who will drive the itemsOlliver: mentioned there already been an exisiting CICD implementation for CNTT, can be copy&paste to use.