Details

    • Type: Epic
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Casablanca Release
    • Labels:
    • Epic Name:
      Standardized ONAP deployment
    • Epic Status:
      Done

      Description

      As an ONAP operator, I want to have a consistent mechanism for Deploying/Operating the platform components across multiple technologies (K8S, Ansible, HEAT, Ckloudify) so that I operate the platform with the best technologies suited for my environment. 

      Currently, HEAT, K8S and Cloudify deployment options are very different in nature and deployment options can not easily be combined together in order to provide the best approach.

      Acceptance Criteria

      • HEAT deployment mechanism is merged under the OOM umbrella so that more consistency is achieved
      • Potentially add more deployment options such as the support for Ansible.

       

      Update: June 25th 2018

      During the Casablanca face-to-face meeting in Beijing support of Heat was discussed with the following proposal/TSC recommendation:

      HEAT-based ONAP deployment support should be dropped once OOM-based ONAP deployment's issues are fully identified and resolved.

      Recommendation from TSC: keep supporting HEAT in Casablanca for testing and integration purposes. However, HEAT won't be a gating item at Release Sign-Off.

       

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              david.sauvageau David Sauvageau
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: