Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...



Agenda and Minutes

  • Agenda Bashing
  • Antitrust Policy: https://r.lfnetworking.org/Antitrust%20Slide.pdf
  • Status Overview
    • Reviewed Issues and PRs – need reviews
  • RA-1 Chapters 1 - 4 Status Report  Ian Gardner
    • Open Issues & Status
    • Request to make Horizon an optional service Issue #1417
    • Request to make Swift (container_sync) optional (PR #1440)
    • – for discussion April 13
  • RA-1 Chapters 5 - 7 Status Report Karine Sevilla

    • Open Issues & Status
  • RA-1 Chapters 8 Status Report Sukhdev Kapur
    • Open Issues & Status
  • Action Item Review
  • AOB
    • Ahmed El Sawaf to share DPDK performance data and guidelines – for presentation April 13 (first topic on agenda)


Action Items

At the RA-1 meeting on March 30th decided to remove Cyborg

Need Issue/PR to change Cyborg API to v1 from v2.

Also, suggest that the following comment be added, "Operators are advised not to implement Cyborg (including support for API v1) because of its limited capabilities but more importantly that starting with OpenStack Stein release the data model, including exposed objects, has changed necessitating changes in API where backward compatibility is not possible. Reference: Cyborg API Version 2(https://specs.openstack.org/openstack/cyborg-specs/specs/train/approved/cyborg-api.html)."

DescriptionDue DateAssigneeStatusTask In
1Topology contentby April 10Need PR.  Will wait until Thursday (April 2nd) and issue PR.  Nokia will provide feedback if possible within current COVID-19 rebalancing challengesIssue #638
2Update 4.2.2.3/4.2.2.5

Number of suggestions for improvements and convergence on language.

Samuel to add "Network Node" write-up in the same PR (Pankaj sent email to Samuel) – not done so created Issue #1390 and PR# 1391

Issue #1153

PR #1310

PR's Requiring Review
as per PR
PR # 1387, 1391, 1408, 1440 and 1444

3Flow Table
Ian Gardner

Raise issue for defining flows as per Ian Gardner PR #1391:

a network flow diagram or table covering how traffic is managed depending on network type:

(we need a network guru to add the correct flows if I get any of this wrong)
Tenant. Traffic uses gre/vxlan and flows from compute to compute and compute to controller
Provider VLAN. Traffic flows directly to/from the compute node hosting the VM via OVS
Provider VLAN DPDK. Traffic flows directly to/from the compute node hosting the VM via OVS-DPDK
Provider VLAN SRIOV. ...
Neutron NAT. Traffic flows from the compute node to the controller and is NAT'd
CVR / DVR???

3PR's Requiring Reviewas per PR
PR # 1387, 1391 and 1408


4PR's Requiring fixes
Petar Torre

PR # 1389

Ahmed El Sawaf to provide a reference to RedHat et al performance sources/sizing guidelines and these can be included in the write-up.


5OpenStack Mandatory Features
Manik SidanaIssue #1156 – no PRIssue #1156
6Security: Image Security
Yeeling LamIssue #1395 – no PR
7Security: Hardening
Yeeling LamTo open Issue and PR
8Security: Confidentiality & Integrity
Karine SevillaIssue #1217 – no PR;Issue #1217
9Cyborg API correctionKarine Sevilla10Barbican write-up in RA-1 Ch03/Ch04
Karine Sevilla

To raise Issue and Content

Already exists in RA-1 Ch05


1011Review SDN in RA-1 Ch 3.2.5Content Created

PR #1391 add a subsection on SDN and reference to Ch 3.2.5

Issue and PR for RA-1 Ch 3.2.5 upgrade

Issue #1443

PR #1444

11SDN - Tungsten Fabric

Testing when using monolithic plugin.  Phase I: use Neutron APIs.

For Phase II, Q: how to handle custom APIs? Get upstream (OSTK)/another project to define SDN API extensions.  What should be the CNTT position?  Wait for CNTT Network FG to define position.