Skip to end of metadata
Go to start of metadata


August 30-31, 2016

Address: Double Tree by Hilton, 889 Yang Gao Nan Road, Pudong, Shanghai

Venue: Golden Spring Hall, West Wing, Floor 4

Tel: 021-50504888


August 30

  • 8:30 Arrive
  • 8:45 Welcome [Chris]
  • 9:00 - 9:30 Open Source Community Principles [Chris]
  • 9:30 - 10:00 Developer Success Guide [Gildas]
    • How to work in Open-O
    • Tools
    • Development Guidelines
    • Best practices
  • 10:00 - 10:15 Break
  • 10:15 - 11:00 Pre-release API and Integration Goals & Principles [Uri]
  • 11:00 - 12:00 Project Reviews (should address M3 milestone template, sequence/"swim lane" diagram, functional block diagram, APIs)
  • 12:00 - 1:00 Lunch
  • 1:00 - 6:15 Project Reviews
    • 1:30 - 2:30 GS-O [Brendan]
    • 2:30 - 3:00 Common TOSCA [Arthur]
    • 3:00 - 3:15 Break
    • 3:15 - 4:15 Common Services [Huabing]
    • 4:15 - 5:15 SDN-O [Olga]
    • 5:15 - 6:15 NFV-O [Lingli]

August 31

  • 8:30 Arrive
  • 8:45 - 9:15 Integration [Helen]
  • 9:15 - 10:15 VNF models [Chengli]
  • 10:15 - 10:30 Break
  • 10:30 - 11:30 VNF SDK Proposal [Alex]
  • 11:30 - 12:00 discussion
  • 12:00 - 1:00 Lunch
  • 1:00 - 5:00 Cross-Project Discussion
    • use-case walk-through
    • IPR
    • collaboration tools (slack, IRC, Confluence, etc.)
    • security
    • SFC
  • 3:00 - 3:15 Break
  • 5:00 - 5:15 Wrap-up discussion [Chris/Uri]

Slide Deck

OPEN-O Community by Chris

OPEN-O Architecture Comments by Uri

OnBoarding New Developers presentation by Gildas

Integration Workshop Presentation-Common Service by Huabing Zhao

[[GSO-ReleaseArchitecture | GSO Release Architecture by Brendan]]

[[Common_TOSCA:Release_1:Release_Plan | Common_TOSCA by Arthur]]

[[Common Service:Release 1:Architecture| Common-Services by Huabing]]

[[SDN-O_Release_Architecture | SDN-O by Olga]]

[[NFV-O:Release_1:Release_Plan| NFVO Plan]] and [[ NFV-O:Release_Architecture | NFVO by Lingli]]


Meeting minutes Day 1: Tuesday, August 30


Presenter: Chris
Goals of the hackfest:

  1. Review Architecture and ensure alignment among all projects
  2. Review API
  3. Ensure we are on track to meet our release date. (M3 this week and Sun Release in November)

Source Community Principles

Presenter: Chris
OPEN-O Community by Chris

Key talking Points:

  1. Reference to” A word about shoes and socks” … ”the sandbox that is the best I sth eone with the most kids in”
  2. 14 company as members, 100+ members: Share our toys, and keep growing (membership and developers)
  3. How to build trust: 13 specific behaviors:
    1. Talk Straight
    2. Demonstrate respect
    3. Create transparency
    4. Right Wrongs
    5. Show Loyalty
    6. Deliver results (hit milstone dates)
    7. Get Better (continuous improvement)
    8. Confront Reality
    9. Clarify Expectation
    10. Listen first (read minutes)
    11. Culture: GuanXi (consensus building)
    12. Developers are more like artists than factory workers
    13. Use common tools (wiki, Slack, iRC, Email) it provides transprency. Words do not scale.
  4. Approval
  5. Cadence-Synchronization
  6. Batch Size: open source is on the speed. Goal to reach Minumum Viable Product
  7. Rapid feedback. Regerence to lottery ticket
  8. Law of diminishing Results (commercial target vs open source market)
  9. Opening to discussion:
    1. Kumar: Tools: communications. Trouble with firewall issue. Discussion planned for Wednesday.
    2. Chris: Disciple to use the tool (to follow the sun)
    3. Alex: Currently issues: archives do not exist, not sure how decision are made
    4. Uri:List of good of principles (lead criteria: committed diversity. Metrics for community performance) to work as a community.
    5. Marc: Continue to grow the community

Developer Success Guide: Onboarding new Developer

Presenter: Gildas
Onboarding New Developers presentation

Further details on onboarding is also available in the Onboarding wiki.

Notes: Gildas to request LF to create mailings specific for each project. Status: Done

OPEN-O Architecture Comments

Presenter: Uri
OPEN-O Architecture Comments by Uri
To support our goal to reach M3 on Thursday, Sept 1

  1. Key talking Points:
    1. Keys structural issues
    2. Key functionality
    3. The values of Architectural review
    4. Suggestion for Architecture (Technical Debt recognition)
    5. Required decision
      1. Remove the Architecture review from Release1 M3 milestone?: Request for TSC approval.
      2. Agreement for R 1: API, block diagram, swimmlane as we defined during last week ARC meeting. Proposal to have Uri leading offside discussion later during this hackfest, wth the goal to conduct Gap Analysis and prioritize items for later releases.
      3. Officially agree on canonized TOSCA YAML over YANG model
      4. API external, internal
      5. Ability to add a new project/micro service later.

Microservice Bus Architecture

Presenter: Huabing
Integration Workshop Presentation-Common Service by Huabing Zhao
Talking points:

  1. High level architecture
  2. Auth Architecture
  3. API Specification
    1. Version issue
    2. Inner versus Outer APIs

Session to be organized with Huabing, Alex, Brendan.


Presenter: Brendan

Talking points:

  1. GSO is an abstraction layer labove technologies such as SDN and NFV.: [[GSO-ReleaseArchitectureScope | Scope]]
  2. Capture of relationship between components: Uri
  3. The Service Model (customer friendly) is not part of Sun Release.
  4. Functionality: [[GSO-ReleaseArchitectureFunctionalities]]
    1. GS-O assurance is now Out of scope for Sun Release.
  5. Release delivrable: no change.
    1. User documentation: minimum doc on how to write a template.
  6. High level architecture diagram [[GSO-ReleaseArchitectureHigh_level_architecture_diagram | architecture diagram]]. Fo rel 1 big GSO box is a single machine
  7. Use Case [[GSO-ReleaseArchitectureUse_cases]] and [[GSO-ReleaseArchitectureExternal_interactions]]
  8. API Incoming dependencies [[GSO-ReleaseArchitectureAPI_Incoming_Dependencies]]

Common Tosca

Presenter: Arthur

Talking Points:

  1. [[Common_TOSCA:Release_1:Release_PlanArchitecture | Architecture]]
  2. [[Common_TOSCA:Release_1:Release_PlanFunctionalities | Functionalities]]
  3. Uri’s request: format between on common-tosca and GSO to be clarified (CSAR file,???) (Arthur, Brendan). To be discussed tomorrow.
  4. [[Common_TOSCA:Release_1:Release_PlanRelease_Deliverables | Deliverable]]
  5. [[Common_TOSCA:Release_1:Release_PlanAPI_Incoming_Dependencies | API]]
  6. Test plan: currently a gap.
  7. [[Common_TOSCA:Release_1:Release_PlanGaps | GAPS]]:
  8. [[Common_TOSCA:Release_1:Release_PlanKnown_Issues | Knowm Issue:]]
  9. [[Common_TOSCA:Release_1:Release_PlanDocumentation.2C_Training.2C_Tutorial | Documentation]]

Common Services

Presenter: Huabing
[[Common Service:Release 1:Architecture| Common-Services]]

Talking Points:

  1. [[ Common_Service:Release_1:ArchitectureScope | Scope]]
  2. Common-Utilities not presented on purposes on diagram
  3. no Change on functionality
  4. [[ Common_Service:Release_1:ArchitectureSub-Components | add sub-cpts: common utility]]
  5. [[Common_Service:Release_1:ArchitectureArchitecture_Alignment | Archiecture Alignment]]
  6. [[Common_Service:Release_1:ArchitectureInteractions| Interaction]]
  7. [[Common_Service:Release_1:ArchitectureAPI_Outgoing_Dependencies | Outgoing API]]
  8. [[ Common_Service:Release_1:ArchitectureFree_and_Open_Source_Software |FOSS]]
  9. Model designer Demo
  10. [[Common_TOSCA:Catalog_API_Documentation |Common Tosca Catalog API]]
  11. [[:File:OPEN-O API Portal Proposal.pdf|OPEN-O API Portal Proposal]]


Presenter: Olga

Talking Points:

  1. [[SDN-O_Release_ArchitectureScope |Scope]] Arthur (common-tosca) to review SDNO proposal
  2. [[SDN-O_Release_ArchitectureSDN-O_Features | Functionalities: no change]]
  3. [[SDN-O_Release_ArchitectureSub-Projects | Sub project]] Added LCM: To clarify LCM naming (which is not really a LCM)
  4. [[SDN-O_Release_ArchitectureHigh_level_architecture_diagram | High level architecture diagram]]
  5. [[ SDN-O_Release_ArchitectureUse_cases | use case enhanced]]
  6. [[SDN-O_Release_ArchitectureExternal_interactions | External Interactions]]
  7. [[SDN-O_Release_ArchitectureInternal_interactions | Internal Interactions]]
  8. [[ SDN-O_Release_ArchitectureError_Handling |Error handling]]
  9. [[SDN-O_Release_ArchitectureAPI_Outgoing_Dependencies | API Outgoing Dependencies]] Follow up with ZTE on controller.
  10. [[SDN-O_Release_ArchitectureThird_Party_Dependencies |Dependencies]]
  11. [[SDN-O_Release_ArchitectureTesting_and_Integration_Plans| Test plan]] Continue discussion on Wednesday on inter project meeting


Presenter: Lingli

Talking Points:

  1. [[NFV-O:Release_1:Release_PlanWhat_is_this_release_trying_to_address.3F | What is this release addressing]]
  2. Question on how SFC is managed: plan to cover during Wednesday inter project meeting
  3. [[ NFV-O:Release_1:Release_PlanUse_Cases | Use Case]]
  4. [[ NFV-O:Release_1:Release_PlanFunctionalities | No change in functionality]]
  5. [[ NFV-O:Release_ArchitectureRelease_Deliverables | Release Deliverable]] No changes since M1
  6. [[NFV-O:Release_ArchitectureArchitecture_Alignment | Architecture Alignment]]
  7. [[NFV-O:Release_ArchitectureInteractions| Interactions]]


Meeting minutes Day 2: Wednesday, August 31


Presenter: HelenOpen-O Integration F2F Shanghai Summary by Helen Chen and more


  1. Integrate everything all together
  2. Responsible for lab setup

Talking Points:

  1. Committers
  2. Logistics
  3. project Description
  4. Sun Release deliverable
  5. Tool Infrastructure: Installation-Delivery of Sun Release (VMs,…) to be brought to TSC for further discussions.
  6. O-Parent: coding style, license header.
  7. CI-Management (CI) and JJB
  8. Unit Test: test framework
  9. System Test
  10. General Principle: Cas talk on how to organize the integration testing
  11. OPEN-O Test Scenarios (pre and post conditions). All testing won’t be performed for Sun Release. Team will be leveraging some OPNVF tools.
  12. Lab Demo availability will come after Sun Release.
  13. Discussion on Plugfest in December


Participants: All
Service request Sequence Diagram

Cas to summarize outcome.

VNF Supplier APIs and SDK

Presenter: Alex
New project proposal
VNF Supplier APIs and SDK Project page

  1. Problem to solve:
    1. Streamline the process to onboard.
    2. Standardize the dependencies on VNF products.
  2. Features:
    1. Deliver some extension to tosca.
    2. Deliver extension to data model using vnfd and vdus.
    3. Provide DevOps tooling
    4. Lifecycle
  3. Resources

Awareness that this VNF project is coming late. Micro service architecture allows for patch and deliver asynchronously to OPEN-O releases.

'''Call for vote''':
OPEN-O has 8 TSC voting members. At the time of the TSC Chair (Chris) calling for the vote 6 out of 8 voting members were present if the room thus quorum was reached.
Vote results:
1. Intel- Uri:+1
2. China Mobile-Lingli: +1
3. Huawei-Chris:+1
4. ZTE-Huabing: -1
5. Gigaspaces-Arthur: +1
6. Ericson-Qing:+1
7. China Telecom: TSC Voting member Chen was not present and no delegation for voting for attributed.
8. HKT-Frankie: absent

Gildas made a summary of the vote outcome and Marc Cohn (Linux Foundation) called the vote as '''Pass'''.

OPEN-O M3 milestone

Based on the artifacts (Architecture template, API in Swagger, swim lane, entity relation diagram) presented at Shanghai on Tuesday, August 30, by PTLs and in accordance with the deliverable plan agreed on last ARC meeting, there was a consensus to qualify OPEN-O Release M3 passed. The expected MVP was reached.

M3 Artifacts:

  1. [[August_2016_HackfestGSO |GSO]]
  2. [[August_2016_HackfestSDNO |SDNO]]
  3. [[August_2016_HackfestNFVO |NFVO]]
  4. [[August_2016_HackfestCommon_Tosca | Common Tosca ]]
  5. [[August_2016_HackfestCommon_Services | Common_Services]]

Doc Project Proposal

Presenter: Chengli Wang.

Project named: OPEN-O Modeling