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

No root (superuser) access to database from application container

    XMLWordPrintable

Details

    • Epic
    • Status: Done
    • High
    • Resolution: Done
    • None
    • Guilin Release
    • None
    • No root (superuser) access to database from application container
    • Non-Functional Requirement (DEPRECATED)
    • 2
    • Not yet performed
    • Reduced Scope
    • M
    • GO
    • Green
    • GO
    • Yellow
    • GO
    • Yellow
    • GO

    Description

       Description of Use Case / Requirement:

       ONAP application container should not access database using root account and should not ask for escalation (sudo). If application requires root access to bootstrap the database an init container or separate kubernetes job should be used.

       

      Owners (one of these should be the Assignee - use @ notation): kopasiak sdesbure

       

      Link to HLD/LLD (if any):

       

      Dependency Relationships with Other Projects:

       

      Project Impact (Test Only (TO), Code (C)): C

       

      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.

       

      Integration Leads (use @ notation): 

       

      Company Engagement: Samsung, Orange

       

      Attachments

        Issue Links

          clones

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. REQ-1 ONAP Requirement Template

          • 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. REQ-537 Long-term IPv4/IPv6 dual stack networking support

          • 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
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SO-3044 No root (superuser) access to database from application container

          • 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.
          • Open

          Task - A task that needs to be done. OPTFRA-800 REQ-358 No root access to database from application container

          • 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.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DCAEGEN2-2329 REQ-358 No root (superuser) access to database from application container

          • 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
          mentioned in

          Page Loading...

          Page Loading...

          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

              kopasiak Krzysztof Opasiak
              sdesbure Sylvain Desbureaux
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: