User Tools

Site Tools


ipv6_opnfv_project:minutes_20151016

Minutes of IPv6 Project Meeting on October 16, 2015

  • Date and Time: PDT 8:00am / UTC 15:00, Friday October 16, 2015
  • Chair: Bin Hu (AT&T)
  • Participants:
    • Chris Valean (CloudBase Solutions)
    • Iben Rodriguez (Spirent)
    • Meenakshi Kaushik (Cisco)
    • Prakash Ramchandran (Huawei)
    • Sridhar Gaddam (RedHat)
    • Wei Han (Huawei)

We focused on discussing current steps and instructions of setting up Service VM as IPv6 vRouter in native OpenStack environment (with ML2 OVS) and in OpenStack+ODL environment. In summary:

  • Current setup is based on environment of OS+ODL. This is documented in wiki.
    • There are many gaps in ODL Lithium SR1, such as:
      • ODL-L3 doesn't support IPv6
      • ODL doesn't support Shared Tenant Networks
      • Security groups for IPv6 is not supported
      • net-virt provider doesn't support IPv6. This prevents us from using Neutron REST API to create subnets because exceptions are thrown.
        • There will be a workaround in SR2 to avoid Java exception. But full feature support will be in later ODL releases.
    • Thus the role of ODL is to provide L2 connectivity. No other features of ODL can be used in case of IPv6.
      • In this case, we still need to use neutron-l3-agent for IPv6 router namespace, and other Neutron features as well when needed
      • When OpenStack is upgraded to Liberty, one additional benefit in IPv6 is its Prefix Delegation support in Neutron.
      • However, PD doesn't add significant value to our IPv6 PoC
      • Thus upgrading OpenStack to Liberty is the same as using Kilo effectively
    • When ODL gets perfect and fully supports IPv6, we will use ODL-L3 instead of neutron-l3-agent.
      • Neutron becomes pass-through agent effectively
      • Thus the version of OpenStack doesn't make any difference
    • We need to install ODL Lithium SR2 to very several bug fixes in order to be able to use Neutron REST APIs to create subnets.
      • Sridhar will work on this
  • Previously, we experimented the setup in native OS environment with ML2 OVS. This is also documented in wiki.\
    • Sridhar will verify the documentation, and revise it accordingly.
  • For B Release deliverables, we assume that installer will take care of Step 1 through 3 to create OS+ODL environment. We only need to provide Step 4 and Step 5 documentation and instruction for B release.
    • One issue is that our current setting is to use neutron-l3-agent instead of odl-l3. We need to verify the end state after installation, i.e. neutron-l3-agent disabled or not, odl-l3 enabled or not.
      • We may need additional instructions before Step 4, and after installation.
    • Bin will communicate with Tim and Jonas to confirm the end state.
  • We talked about future roadmap including:
    • Phase 2: more environments with other SDN controllers, such as OpenContrail, ONOS, Midonet, etc.
    • Phase 3: full-blown, bare metal environment
    • Both Phase 2 and Phase 3 will be beyond B release, and we need more resources to support Phase 2 and Phase 3, including:
      • Infrastructure resources, e.g. more bare metal machines in Spirent's VCT Lab
      • Developer resources in community to repeat the setup in various enviroments.
    • Bin will create roadmap in wiki
    • Bin will encourage community resources to repeat PoC setup in various environments

Actions include:

  • Sridhar to revise instructions of Steps 1 through 5 for shared tenant networks and using Neutron REST API to create networks
  • Sridhar to verify wiki documentation for accuracy and up-to-date
  • Sridhar to install SR2 and verify bug fixes
  • Bin to add roadmap in wiki documentation
  • Bin to work with Installers to confirm the end state of installation, i.e. neutron-l3-agent disabled or not, odl-l3 enabled or not
  • Bin to encourage community resources to repeat PoC setup in various environments

<Standing agenda and project plan is as follows>

  • Roll call
  • Admin Update
    • B Release Planning Update
      • Requirement on Genesis, CI, FuncTest or anything else?
      • 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
    • 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.

ipv6_opnfv_project/minutes_20151016.txt · Last modified: 2015/10/17 06:28 by Bin Hu