From OpenFlow Wiki

Meeting Minutes for SWAI, 27 May 2010

Present

Agenda

• Test framework and test development continued
• HAL update
• Netgear update

Meeting Minutes

Test framework

• What do we need to do to get to release?
  • Get as many of the Perl blackbox tests integrated into OFTest as possible
    • What is strategy here? Need to review coverage of BB tests to generate a list of tests to implement in OFTest.
  • Clarify and clean up documentation
    • Extract auto gen doc
    • Provide API overview and "how to use"
    • High level overview of components (controller, dataplane, messages and other objects)
• General question: What is test granularity approach.
• Action: Implement and run the following test
  • Match on .... VLAN = X
  • Action list: Output A, VLAN set to Y, Output B
  • Expected result: Packet with VLAN X on A, packet with VLAN Y on B

HAL

• Baseline description of HW abstractions
• Need to provide a clear argument as to why the HAL API should be represented/implemented in C and not eating into the OpenFlow protocol.
• Stakes in ground:
  • No new high level abstractions that are not in the OF protocol or configuration protocol should be introduced into the HAL.
  • Should clarify what are core OF abstractions.
  • Should not modify core OF abstractions.
• Want to be portable across different HAL implementations
• Does there need to be an OS abstraction layer as well? What OS abstractions need to be represented in this? Best example is native network interface support.