Uploaded image for project: 'Release Requirements'
  1. Release Requirements
  2. REQ-432

IPv4/IPv6 dual stack support in ONAP (Honolulu)

XMLWordPrintable

    • IPv4/IPv6 dual stack support in ONAP (Honolulu)
    • Feature
    • GO
    • Original Scope
    • M
    • GO
    • Green
    • Green
    • GO
    • GO
    • Green

      Description of Use Case / Requirement:

      Majority of LTE and 5G RAN networks today are running exclusively on IPv6. IPv4/IPv6 dual stack solution for ONAP is needed to enable integration.
      Continuation of https://jira.onap.org/browse/REQ-385

      It is mainly about a Kubernetes platform, hosting ONAP application containers.
      An enabler for IPv4/IPv6 networking would be an upgrade of ONAP OOM Helm charts to K8S 1.16+ APIs (Done in Guilin)

      Honolulu scope
      The target for Honolulu is to update all ONAP components, which do not install/execute properly in IPv4/IPv6 dual stack environment.
      As of today (B10/2020), the following components are affected:

      • SDN-R Elastic Search module
      • Portal Cassandra DB image
      • DCAE - CFY Plugin - support exposing services using IPv6
      • At this moment, this is a full list.

      Beyond Honolulu
      A migration to an alternative platform supporting dual stack K8S networking will be a matter in a future release.

      Owners (one of these should be the Assignee - use @ notation): deen1985 demx8as6 kopasiak sdesbure dmilaszkiewicz Grzegorz-Lis

      Link to HLD/LLD (if any):
      None

      Dependency Relationships with Other Projects:

      1. DCAE --> We need to extend the CFY Plugin to support IPv6 service exposure
      2. SDN-R --> Elasticsearch update needed
      3. Portal --> Cassandra startup scripts to be updated

      Proposed proceeding related to this requirement (in context of dependencies):

      1. Update the Helm charts to support K8S 1.17+ API (DONE)
      2. Update the set-up scripts for all relevant components, mentioned before

      Project Impact (Test Only (TO), Code (C)):
      DCAE (C)
      SDN-R (C)
      Portal (C)
      Integration (TO)

      NFR Support: (support for non-functional requirement)

      1. Its is an NFR itself

      Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):
      Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.

      • OOM: P (Partially supported)
      • DCAE (C)
      • SDN-R (P)
      • Portal (P)
      • Integration (C)

      Integration Leads (use @ notation): dmilaszkiewicz

      Company Engagement:

      • Nokia
      • Orange
      • Samsung
      • highstreet

            deen1985 deen1985
            deen1985 deen1985
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: