Page tree
Skip to end of metadata
Go to start of metadata

D Release Planning

According to our roadmap, we have successfully accomplished our Phase 1 Work in Brahmaputra Release covering the design and implementation of IPv6 vRouter using service VM in native OpenStack environment and ODL-integrated environment.

We also successfully accomplished our Phase 2 work in Colorado Release covering IPv6-only infrastructure deployment by Apex installers, and IPv6 gap analysis with OpenStack Mitaka Release and ODL Boron Release.

Now we are planning our Phase 3 work in Danube Release.

  • IPv6-only infrastructure deployment by installers
  • IPv6 Gap Analysis with Official Components of OpenStack and ODL in D Release
    • OpenStack Newton Release
    • ODL Carbon Release (or still Boron Release)
  • Documentation / Install Guide / User Guide
    • A note indicating tunnel endpoint is still IPv4 when OVS version is earlier than 2.6.
  • Multisite IPv6 - may postpone to E Release or later because of unavailable infrastructure

    • JIRA IPVSIX-38 (Epic) which depends on PHAROS-181
    • Areas of interest:
      1. At underlay level, multiple instances of OpenStack can be deployed at multisites, one at each site, and use IPv6 for normal Neutron Router

      2. Extend IPv6 vRouter Connectivity to External IPv6 Networks (North-South connectivity) and Deployed on Multisite Pharos Labs
        • At overlay level, the simplest case is that vRouter is deployed at multisites, each vRouter at each site, and connects to ext-net that has physical IPv6 router. Then vRouters at multisites can communicate with each other (North-South). Thus VM on each subnet can communicate with IPv6 packets via North-South connectivity.

        • Note: achievable if we have appropriate lab infrastructure. It depends on PHAROS-181
    • Testing: YARDSTICK-249
      • Note: Subject to infrastructure availability.
    • Additional Areas:
      • At overlay level, what is role of L3VPN plays to connect those vRouters that connect to ext-net?
        • Note: It may need Tricircle. L2 networking across OpenStack instances (East-West) will not be available until Newton as the earliest, and L3 networking will be even later.
        • This scenario is planned for D Release or later
      • At overlay level, since those VMs in different subnets can communicate with IPv6 traffic, how does it affect SFC if L3VPN is used to construct SFC?
        • Note: Experimental. It may be in D Release or postponed to E Release or later
      • Then there are HA related issues, including both multisite and standalone deployment.

        • Note: Experimental. It may be in D Release or postpone to E Release or later

Service VM as IPv6 vRouter in ONOS-integrated environment

  • JIRA IPVSIX-39 (Epic)
  • Note: subject to expertise and resource availability, it may be in D Release or postpone to E Release or later

Service VM as IPv6 vRouter in OpenContrail-integrated environment

No resource available. Postponed to E Release or later

Project plan per the milestones described at Danube

(MS0) Open Intent to Participate9/27/16Completed
(MS1) Planning complete (scenarios or deliverables defined)10/25/16Completed
(MS2) Detailed test case descriptions communicated to test project teams11/22/16Completed
(MS3) Installer integration with OpenStack completed11/30/16N/A
(MS4) Infrastructure updates completed12/6/16N/A
(MS5) Scenario integration and Feature Freeze completed1/27/17Completed
(MS6) Test cases implemented, preliminary documentation completed, and stable branch open2/17/17Completed
(MS7) Stable branch window close3/10/17Completed
(MS8) Formal test execution completed3/20/17Completed
(MS9) JIRA issues assigned to release closed or deferred3/22/17Completed
(MS10) Documentation completed3/24/17Completed
(MS11) Release Danube 1.0
(MS12) Release Danube 2.0
(MS13) Release Danube 3.06/8/17 


  • No labels