Wiki

• Date and Time: PDT 9:00am / UTC 16:00, Friday October 02, 2015
• Chair: Bin Hu (AT&T)
• Participants:
  • Hannes Frederic Sowa (Redhat)
  • Iben Rodriguez (Spirent)
  • Jonne Soininen (Nokia)
  • Mark Medina (ClearPath)
  • Meenakshi Kaushik (Cisco)
  • Prakash Ramchandran (Huawei)
  • Sridhar Gaddam (RedHat)
  • Vikram Dham (Dell)

We focused on Sprint-1 ODL Gap Analysis and related issues. In summary:

• Sridhar described current ODL issues:
  • ODL Lithium SR1 only supports Floating IP addresses for VMs. It currently does not support L3 IPv6 Router.
  • We cannot create IPv6 subnet using Neutron REST API in ODL. Although subnet creation appears successful but the necessary OVS flows are not applied on the br-int bridge because there is a Java exception. This is because in ODL, OVSDB NET-VIRT doesn't support IPv6 yet. There is a bug report and workaround of ignoring subnet of IPv6 in external arp resolver (https://git.opendaylight.org/gerrit/#/c/25635/1) to avoid Java exception. But the problem is not solved.
  • No support for shared tenant networks. So, each tenant needs to have their own vRouter.
  • Mutli-node setup in Spirent Lab is configured with ODL for L2 support and Neutron L3 agent for Routing.

• Sridhar gave an update of Neutron:
  • In Neutron + OVS setup, each L3 agent runs and manages the router in a separate namespace
  • IPv4/IPv6 Routing uses iptables and not ovsflows. With connection tracking support in OVS, in future this can be enhanced to use the OVS flows instead of IPtables.
  • Neutron Rest API only supports /64 IPv6 subnets.

• Hannes talked about Connection Tracking feature added in Kernel, and it needs new BP for Neutron.
  • The idea is to get rid of the qrouter, as those currently slow down performance a lot (the current setup traverses two ovs dataplanes and one namespace performing the NAT, masquerading, enforcing security policies and such). The new code can do this directly in openvswitch, thus giving huge performance improvements.
  • We need to check what we need to do inside ovs for ipv6, then.

• Hannes also talked about Link local address with MAC address, and enhancement in kernel for us to verify.
  • Basically Fedora Kernel does have this feature already. The RFC7217 is available here <https://tools.ietf.org/html/rfc7217>
  • It is implemented in the kernel via the sysctls in /proc/sys/net/ipv6/conf/*/stable_secret

# stable_secret - IPv6 address
This IPv6 address will be used as a secret to generate IPv6
addresses for link-local addresses and autoconfigured
ones. All addresses generated after setting this secret will
be stable privacy ones by default. This can be changed via the
addrgenmode ip-link. conf/default/stable_secret is used as the
secret for the namespace, the interface specific ones can
overwrite that. Writes to conf/all/stable_secret are refused.

It is recommended to generate this secret during installation
of a system and keep it stable after that.

By default the stable secret is unset.

• Currently it is not integrated into NetworkManager etc. in current distributions, but as soon as a new version will be released, it should include stable privacy support:
  • https://fedoraproject.org/wiki/Tools/NetworkManager/IPv6#IPv6_Privacy_Extensions
  • http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=lr/stable-privacy-rfc7217
• A specific build with new NetworkManager can be generated for the test lab to test this before a new release.

• We discussed PoC design. It is good for long term, because it should work in this way
  • Any feature that is required for OPNFV IPv6 use-cases if found missing in Neutron/ODL, the idea is to propose it upstream in the respective component and track/implement it so that it becomes part of the upstream feature.

• Iben and Jonne work offline on allocating /48 address block and configuring physical IPv6 router

• Iben and Sridhar work offline to address several access issue, such as MTU size, OVS setting, ESXi security setting etc.

<Standing agenda and project plan is as follows>

• Roll call
• Admin Update
  • B Release Planning Update
    • Requirement on Genesis, CI, FuncTest or anything else?
      • Testing Requirement for B Release
    • JIRA: IPVSIX-10 Create timeline of milestones of IPv6, and aligned with B release
      • 08/18/2015: B Release Milestone A
      • 08/18/2015: B Release Milestone B
      • 09/25/2015: B Release Milestone C
      • 09/25: Revised PoC 1 Diagram completion
      • 10/09: Sprint C-1: Gap analysis with ODL completion (IPVSIX-18)
      • 10/15: Sprint C-2: Test Plan completion (IPVSIX-14)
      • 10/30: Decision on Snapshot image or Metadata (latency issue)
      • 11/15: Sprint C-3: Jenkins integration completion (IPVSIX-7)
      • 11/30: Sprint C-4: Test completion (IPVSIX-27)
      • 12/01/2015: B Release Milestone D
      • 01/05/2016: B Release Milestone E
      • 02/02/2016: B Release Target Date
    • Other update of B Release
      • B Release Weekly Project Status
  • Jira issue status
  • Gerrit repo status
• B Release Tasks Update
  • Epic: JIRA IPVSIX-12 IPv6 Support / Gap Analysis with ODL
    • Story: JIRA IPVSIX-19 Revision of PoC 1 Diagram
      • Task: JIRA IPVSIX-20: Sridhar adds how IPv4 routing happens for VMs (Tenant B) in the diagram
      • Task: JIRA IPVSIX-21: Sridhar reviews the setup instructions, and see if any change is needed to support dual-stack Service VM vRouter.
      • Task: JIRA IPVSIX-22: Sridhar modifies diagram to use external IPv6 router for the setup of OS+ODL
    • Story: JIRA IPVSIX-18 Gap Analysis Wiki of IPv6 on ODL (Sprint C-1)
      • Task: JIRA IPVSIX-23: Iben creates Spirent VCTLab accounts for Sridhar, Meenakshi, and Prakash
      • Task: JIRA IPVSIX-24: Sridhar and Meenakshi set up Lithium SR1 integration
      • Task: JIRA IPVSIX-25: Sridhar and Meenakshi continue ODL gap analysis based on this setup.
  • Epic: JIRA IPVSIX-13 Metadata Methodology / cloud.init()
    • Sridhar has done it. Update of further experiment from all
  • Epic: JIRA IPVSIX-14 Test methodoloy, test case development and testing related tasks (Sprint C-2)
  • Multisite IPv6 Community Lab and CI Integration Update (Iben)
    • Epic: JIRA: IPVSIX-7 Experiment and document instructions on Jenkins integration (Sprint C-3)
      • Dependent on JIRA OCTO-135
    • Epic: JIRA: IPVSIX-9 Setup IPv6 in OPNFV Community Test Labs
  • Epic: JIRA: IPVSIX-27 Test Completion using FuncTest or other test tools integration (Sprint C-4)
  • Epic:JIRA: IPVSIX-6 Propose Metadata structure of IPv6 ISO
    • Progress update from Prakash and Iben in terms of brown field experience, and vPING and vLOOP.
  • Story: JIRA IPVSIX-29 Create an IPv6 chapter for the configuration guide
    • Required by DOCS-40
  • Story: JIRA IPVSIX-30 Create an IPv6 user guide chapter for the Brahmaputra user guide
    • Required by DOCS-41
• Next Step
• AOB

Meeting adjourned.