Uploaded image for project: 'Active and Available Inventory'
  1. Active and Available Inventory
  2. AAI-175

aai core service of A&AI has it's Log Provider Configuration File configurable from startup.sh

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Medium
    • Resolution: Done
    • None
    • Beijing Release
    • None

    Description

      For A&AI "ajsc-aai" service has its logging provider configuration file location can be set to canonical location by changing "/startup.sh" script. 

      Currently the Log Provider Config File location as in "/startup.sh" is "/opt/app/aai/bundleconfig/etc/logback.xml". It should be inside a configurable location. This is to support logging provider configuration as described in ONAP application logging guidelines (https://wiki.onap.org/download/attachments/1015849/ONAP%20application%20logging%20guidelines.pdf?api=v2), which state that "[a]n application should provide the ability to change the logging level [...] with no/minimum impact to the running application" and that "[a] configuration file should be used by logging application to determine the actual directory specification where to write the log file", and is not consistent with standardized configuration locations suggested by the ONAP Logging Enhancements project (https://wiki.onap.org/display/DW/Logging+Enhancements+Project+Proposal#LoggingEnhancementsProjectProposal-Defaultproviderconfigurationlocations). 

      Fix suggested is as below: 

      1. Create the directory /etc/onap/aai/conf.d/ajsc-aai/ 
      2. Change the System parameter in "/startup.sh" file mentioned above as shown: 
      -Dlogback.configurationFile= /etc/onap/aai/conf.d/ajsc-aai/logback.xml 

      Attachments

        Issue Links

          duplicates

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AAI-95 AAI-Traversal ONAP docker container need to expose configuration to host

          • 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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AAI-96 AAI-Resources ONAP docker container need to expose configuration to host

          • 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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AAI-97 AAI HAPROXY ONAP docker container need to expose configuration to host

          • 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
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              vk250x Venkata Harish Kajur
              alkac Alka Choudhary
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: