This is an old revision of the document!
Please help move this page
Doctor Team Meetings
Info
Past meetings
Weekly project meetings
Dec 22, 2014
Agenda
work item updates
Fault table
GAP analysis template
Wiki pages
Minutes
Dec 8, 2014
Agenda
How we shape requirements
Day of the week and time of weekly meeting
Tools: etherpad, ML,
IRC?
Project schedule, visualiztion of deliverables
Minutes
How we shape requirements
Use case study first
Gap Analysis should be included existing monitoring tools like Nagios etc.
How we format fault message and VNFD elements for alarms?
Fault detection should be designed within a common/standard manner
Those could be implement in existing monitoring tools separated from OpenStack
What is "common" monitoring tools, there are different tools and configurations
Focus on H/W faults
Do we really need that kind of notification mechanism? Can we use error from
API polling, just get error detected by application or auto-healing by VIM?
Real vEPC needs to know fault that cannot be found by application like abnormal temperature.
VIM should not run auto-healing for some VNF.
There are two cases/sequences defined in ESTI NFV MANO that fault notification are send from VIM to VNFM and to Orchestrator.
Alarming mechanism is good to reduce the number of request from user who pooling virtual resource status.
We shall categorize requirements and create new table on wiki page. (layer?)
→ A general view of the participants is to have the 'HW monitoring module' outside of OpenStack
TODOs
Open etherpad page for collaborative working (Ryota)
Collect use cases for different fault management scenarios (Ryota)
-
Provide Gap Analysis (Dinesh, Everyone)
Provide fault management scenario based on ETSI NFV Architecture (Ashiq)
List fault items to be detected (Ashiq, Everyone)
Day of the week and time of weekly meeting
Tools: etherpad, ML,
IRC?
Project schedule, visualiztion of deliverables
Dec 1, 2014
Logistics
Agenda
Minutes
Project proposal
There were two comments at project review in TSC meeting (Nov 26)
Large scope: TSC asked to narrow project scope, creating as requirement projects seems reasonable
Overlap with HA project, so collaborate in project activity
-
Ashiq and Qiao had talked before this meeting, and agreed that we would not eliminate duplication at proposal phase
Project proposal was fixed by some members
-
The project categories was changed to requirement only
In new revision of project proposal, we removed detailed descriptions which don't suit requirement project
Links to original project proposal are replaced to point the new page, and the link to the old page that described further details can be found at the bottom of the new proposal page
We should not edit the proposal page after TSC approval to keep evidence what we planed at the beginning of the project
"Auto recovery" is missing, will continue discussion in mail with clarification by Tomi
Nov 17, 2014
Agenda
Scoping and Scheduling (what feature to be realized in what time frame)
Resources available and necessary for this project
Technical aspects and relevance to upstream projects
How to socialize with upstream projects
Logistics
-
Feb 6, 2015
Implementation Planning
Topic and agreement can be found in
Slides.