JiaLiangC opened a new pull request, #3697: URL: https://github.com/apache/ambari/pull/3697
## What changes were proposed in this pull request? Main logic and changes of the commit: Desc: Ambari Ranger adaptation Ambari 2.8 uses bigtopstack 3.2.0, which corresponds to apache bigtop version 3.2.0 1.All components lack corresponding ranger property files. Therefore, all ranger-related configuration files for all components are added. 2.There is a lack of ranger integration, and here we integrate the ranger service. This ranger service is ported from hdp3.1.5's ranger service. The difference is that some initialization content in the install method is referenced to the /usr/bigtop/current directory, but this directory will only be linked with the "bigtop-select distro-select set component version" command in the post-hook after the install method is completed. Therefore, the initialization logic in the install method is moved to the configure method, and a mark file is set. Once the initialization is completed, a mark file is generated, and subsequent initialization will not be performed if the mark file exists. 3. Bug fix for ranger advisor not working After integrating Ranger, most of the component advisors were not functioning properly due to the presence of ambari/ambari-server/src/main/resources/stacks/BIGTOP/3.2.0/services/stack_advisor.py in the 2.8.0 branch. The working logic of stack_advisor is such that ambari/ambari-server/src/main/resources/scripts/stack_advisor.py, as the starting point, loads all advisors, including stack_advisor.py and service_advisor.py under ambari/ambari-server/src/main/resources/stacks directory. service_advisor.py loads all service_advisor.py under each component directory and retrieves the recommended configuration, such as ambari/ambari-server/src/main/resources/stacks/BIGTOP/3.2.0/services/HDFS/service_advisor.py, which contains all recommended HDFS configurations. However, in the 2.8.0 branch, ambari/ambari-server/src/main/resources/stacks/BIGTOP/3.2.0/services/stack_advisor.py hardcodes to only return a few service advisors, causing all other component service advisors to not work properly. Furthermore, ambari/ambari-server/src/main/resources/stacks/BIGTOP/3.2.0/services/stack_advisor.py is redundant, and the configurations are scattered in each service advisor. Therefore, removing this file fixed the issue. The fix can be found in this PR: https://github.com/apache/ambari/pull/3677. ## How was this patch tested? manual test before enable kerberos all compoent works smoonthly   after enable kerberos all compoent works smoonthly   Please review [Ambari Contributing Guide](https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute) before opening a pull request. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org For additional commands, e-mail: dev-h...@ambari.apache.org
