User Tools

Site Tools


Minutes of Technical Community Discussion on February 12, 2015

  • Date and Time: UTC 14:00, Thursday Febuary 12, 2015
  • Convenor: Bin Hu (AT&T)
  • Participants:
    • Brian Smith (Bell Canada)
    • Carlos Goncalves (NEC)
    • Christopher Price (Ericsson)
    • Dave Neary (RedHat)
    • Iben Rodriguez (Spirent)
    • Juha Oravainen (NSN)
    • Julien Zhang (ZTE)
    • Kansheng Dong (China Mobile)
    • Manuel Rebellon (Sandvine)
    • Mario Torrecillas Rodriguez (ARM)
    • Michael Godley (Intel)
    • Patrice Buriez (Intel)
    • Prasad Gorja (Freescale)
    • Praveen Kumar
    • Rajeev Seth (Sonus Networks)
    • Raymond Nugent (Huawei)
    • Stuart Mackie (Juniper)
    • Tianran Zhou (Huawei)

Bin introduced the technical discussion and review history of this proposal. The original author has sent an email to the mailing list about the update of this proposal.

Carlos remembered that on Jan 15, based on the discussion, Dave Lenrow had an action item to communicate with wider stakeholders including the proposal of Service Function Chaining, clarify the scope, and see if it is possible to consolidate those 2 similar proposals that have the similar scope.

There has been no update on this aspect.

Bin will take an action item to follow up with Cathy / Dave in the mailing list.

Tianran Zhou introduced this proposal. The proposal brings a new abstraction layer between application and cloud platform (e.g. OpenStack). The abstraction layer provides a simplified NB API for application to interact with cloud platform. Then the abstraction layer converts to platform-specific API calls such as those APIs in Nova, Neutron etc.

The first type of questions asked about what type of problem it would solve. Tianran explained that current platform-specific APIs in OpenStack are not intuitive and complicated. It requires deep domain knowledge of OpenStack for an app developer to understand and use those APIs. This proposal provides a simplified set of API so that app developers can use without deep domain knowledge of specific cloud platforms. It provides a way that can work with any cloud platform thus more scalable, and ensures app portability over different cloud platforms.

The second type of questions asked about what this project would deliver. Will it deliver the abstraction layer (API and code) in OPNFV (thus a differentiated value of OPNFV)? Or will it deliver the requirement and work with upstream community to implement the abstraction layer? Tianran clarified that they are open to those approaches. It would be good for OPNFV to develop the abstraction layer (API and code) so that OPNFV will add our unique vale in industry. On other hand, it is also ok to get the work done in upstream. For example, Huawei has brought this to OpenStack. So far no luck for OpenStack to recognize the issue and intend to solve it.

The third type of questions asked about collaboration with other entities. For example, ETSI MANO. Tianran clarified that they are happy to work with other entities. In fact, the deliverables of this project can also contribute to other entities, such as ETSI. They already introduced it to IETF 91.

Tianran will revise this proposal to emphasize on the difference with other similar activities in ETSI etc., and outline how it will work together with other entities to achieve collaboration and synergy,

  • Discussion of Collaborative Development project proposals

Postponed to next meeting.

Postponed to next meeting.

Postponed to next meeting.

  • Discussion of Integration and Testing project proposals:


  • Discussion of other projects


At last, Bin mentioned that Huawei (Uli) indicated the Chinese New Year Holiday Week in China thus Huawei would be unable to participate in the discussion next week considering most of proposals were from Huawei. Bin also observed the meetup in Santa Rosa next week. Bin will poll the mailing list whether or not to cancel the meeting next week.

Meeting adjourned

wiki/tc_minutes_20150212.txt · Last modified: 2015/05/06 20:05 by Daniel Farrell