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

(London-R12) - Removal of AAF

    XMLWordPrintable

Details

    • Epic
    • Status: Done
    • Medium
    • Resolution: Done
    • None
    • London Release
    • None
    • Removal of AAF
    • Feature
    • GO

    Description

      Using ServiceMesh as default deployment option in London, we want

      • to remove AAF as component from the default installation stack
      • All components have to be able to provide unencrypted interfaces
      • Protocol encryption will be implemented by ServiceMesh Platform
      • AAF specific implementations can be removed from code and helmcharts

      SECCOM: https://wiki.onap.org/pages/viewpage.action?pageId=103417456

      OOM: https://wiki.onap.org/pages/viewpage.action?pageId=137199877

      API changes in components:

      • ONAP Component Services must offer "plain" non-TLS interfaces
      • ONAP Components must be able to use not-TLS interfaces of other components 

      Attachments

        Issue Links

          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. REQ-370 Components may use HTTP as server and client

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • To Do

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OOM-2975 Remove dependencies on AAF

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. REQ-368 Service mesh PoC

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Done
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

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

          Activity

            People

              andreasgeissler Andreas Geissler
              andreasgeissler Andreas Geissler
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: