Skip to main content
Version: 3.1.0 (Preview)

Blueprint Support For Ranger

Stack Advisor Workflow

Use the installed BIGTOP Ranger Stack and Stack Advisor to fill derived Ranger and plugin settings. The Blueprint or cluster template must still provide required values that cannot be inferred, especially database connectivity and administrator credentials. Do not copy credentials into documentation or source-controlled Blueprint examples.

For Ranger Admin, review admin-properties: DB_FLAVOR, db_host, db_root_user, db_root_password, db_password, and audit_db_password. The selected database requires the matching JDBC driver on Ambari Server.

For Ranger plugins, review ranger-env, including ranger_admin_password and the plugin enablement properties such as ranger-yarn-plugin-enabled, ranger-hdfs-plugin-enabled, and ranger-hbase-plugin-enabled. Enable only plugins required by the deployed services.

For Ranger KMS, review kms-properties and the KMS service configuration. Required fields include the database flavor, connector JAR, master-key password, database host, and database credentials. Use the corresponding RANGER_KMS Stack service available in the selected BIGTOP Stack.

Required Configuration And Order

  1. Confirm the selected Stack provides Ranger, Ranger KMS, and the required plugin configuration types.
  2. Provide database host/port, database names/users, and required password properties through protected Ambari configuration input.
  3. Install the JDBC driver on Ambari Server before Stack Advisor evaluates the database choice.
  4. Set plugin enablement deliberately, then allow Stack Advisor to generate dependent properties.
  5. Review the recommended configuration and create the cluster only after unresolved required properties are fixed.

Without Stack Advisor, every Ranger, Ranger KMS, and enabled-plugin property without a valid default must be supplied explicitly in the Blueprint or cluster template. This is more fragile across Stack versions; prefer advisor-backed configuration and verify the generated result.

Source References

The current service implementation is in the pinned BIGTOP Ranger Stack and Ranger service advisor. Select the service path matching the installed BIGTOP version (3.2.0, 3.3.0, or 3.4.0).