• Date and Time: UTC 14:00, Thursday January 29, 2015
• Convenor: Bin Hu (AT&T)
• Participants:
  • Badrinarayanan B (CalSoft Labs)
  • Bryan Sullivan (AT&T)
  • Christopher Price (Ericsson)
  • Hai Liu (Huawei)
  • Juha Oravainen (NSN)
  • Linghui Zeng (Huawei)
  • Luke Hinds (NSN)
  • Manuel Rebellon (Sandvine)
  • Margaret Chiosi (AT&T)
  • Maria Toeroe (Ericsson)
  • Mike
  • Pasi
  • Patrice Buriez
  • Pradeep
  • Prasad Gorja (Freescale)
  • Praveen Kumar
  • Rajeev Seth (Sonus Networks)
  • Raymond Nugent (Huawei)
  • Ryota Mibu (NEC)
  • Stuart Mackie (Juniper)
  • Tapio Tallgren (NSN)
  • Tianran Zhou (Huawei)
  • Tim Rozet (RedHat)
  • Ulrich Kleber (Huawei)
  • Zhiqi Wang (Huawei)

• Discussion of Requirement project proposals
  • OpenStack Based VNF Forwarding Graph

The proposal author was not present. No information about the action of updating the proposal and clarifying the scope. Postponed to next meeting.

• Data Collection of Failure Prediction

Hai Liu presented it and introduced the update of the proposal. Uli also shared a diagram. The proposal is focusing on collecting data for failure prediction now. More specifically, it will work on the NB API of the prediction module.

The discussion focused on how it is differentiated from Policy, Doctor etc. other projects, and how to achieve synergy in terms of the mechanics of data collection in general.

All agreed that 4 actions are needed to further update the proposal:

• Update the repo name to be short and meaningful, all lower case without special chars
• Upload the diagram
• Clarify what is the difference from Pharos, Doctor and Copper projects
• Clarify how to achieve synergy in terms of the mechanics of data collection in general.

• Resource Scheduler

Zhiqi introduced the update of this proposal, and the diagram added in Dependencies section.

Ryota also clarified that it is different from Promise project.

The question focused on if this proposal introduced additional functions to support Promise, it would be good to add this feature into Promise project and combine those 2 projects together.

The meeting ended unexpectedly because another Test and Performance Meeting started 8 minutes before schedule. Starting another meeting automatically ended a previous meeting.

Further discussion was postponed to next meeting.

• VIM Northbound Model and Interface

Postponed to next meeting.

• Discussion of Collaborative Development project proposals
  • Rescuer

Postponed to next meeting.

• Service Function Chaining

Postponed to next meeting.

• Discussion of Integration and Testing project proposals:
  • Parser

Postponed to next meeting.

• Discussion of other projects

None.

Meeting adjourned