Good Day,   Effective January 31, 2021, all Cloudera software requires a valid subscription and is only accessible from behind the paywall. This includes all legacy versions for Cloudera Distribution including Apache Hadoop (CDH), Hortonworks Data Platform(HDP), Data Flow (HDF/CDF),and Cloudera Data Science Workbench (CDSW). Information regarding paywall access will be available in technical documentation by software type and version.   https://www.cloudera.com/downloads/paywall-expansion.html   If you have a valid Cloudera Subscription, you can obtain your credentials for downloads following directions outlined here: https://docs.cloudera.com/cdp-private-cloud-base/latest/installation/topics/cdpdc-cm-download-information.html      ... View more

Hello, thank you for your question:   1) Within Cloudera Navigator, you can apply metadata and tagging via the Navigator UI or the Navigator API.  Please see the below links for each: https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cn_iu_metadata_modify.html#xd_583c10bfdbd326ba--43d5fd93-1410993f8c2--7f69 https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cn_nav_hive-hdfs_api.html#tag_hive_hdfs_json_apis   2) Apache Sentry provides only Role Based Access Control (RBAC) policies.  Creating access policies based off of metadata and tags is more commonly referred to as Attribute Based Access Control (ABAC).  Navigator+Sentry in CDH6.3 does not provide ABAC functionality.  You will need Atlas and Ranger available in CDP which can support both RBAC and ABAC policies.  Please see an overview of ABAC in this Cloudera Youtube video on ABAC. ... View more

Check out our series of SDX videos on our youtube channel for some examples of Atlas + Ranger in action as part of the CDP Shared Data Experience (SDX):   https://www.youtube.com/playlist?list=PLe-h9HrA9qfCj2SI5BrvCdQOEOjHUWMBB ... View more

If Director is creating the database via templates it will append a randomly generated string to the scm prefix so that multiple deployments can use the same database server without naming conflicts.  The user you are using needs full administrative privileges to the entire database instance if going this route.     If you are wanting to specify a pre-created database name and user, and only provide the user access to that one database, you will need to make sure to use something like the example in the attached link and deploy your environments via a conf file.   https://www.cloudera.com/documentation/director/latest/topics/director_external_db_using.html   cloudera-manager { # ... databases { CLOUDERA_MANAGER { name: scm1 type: mysql host: 1.2.3.4 port: 3306 user: scmuser password: scmpassword } # ... } } type - The type of database, “MYSQL” or “POSTGRESQL.” hostname - The name of the server host. port - The listening port of the server. name - The name of the database on the server. username - The name of the user account having full access to the database. password - The password for the user account. Hope this helps! ... View more

Gateway roles have no specific hardware configuration requirements.  A gateway role simply copies the configuration files needed for a given role to be accessed from a host outside of the cluster. The hardware configuration will depend on what your team will be doing on the host.   Here is a link to the documentation on managing roles:   https://www.cloudera.com/documentation/enterprise/latest/topics/cm_mc_managing_roles.html   Gateway Roles A gateway is a special type of role whose sole purpose is to designate a host that should receive a client configuration for a specific service, when the host does not have any roles running on it. Gateway roles enable Cloudera Manager to install and manage client configurations on that host. There is no process associated with a gateway role, and its status will always be Stopped. You can configure gateway roles for HBase, HDFS, Hive, Kafka, MapReduce, Solr, Spark, Sqoop 1 Client, and YARN.   ... View more

  It looks like your scm user doesn't have proper privileges to access the database server. This could be a problem with the grants in your mysql instance.   [2019-03-14 23:36:19.504 +0500] INFO [io-thread-6] - - - - - ssh:10.142.0.54: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Access denied for user 'scm'@'%' to database 'scm_lsq85p3anqialkp12nogfhig3j' [2019-03-14 23:36:19.504 +0500] INFO [io-thread-6] - - - - - ssh:10.142.0.54: at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)[:1.8.0_181] Cloudera Altus Director requires a username with full access to the database.   https://www.cloudera.com/documentation/director/latest/topics/director_external_db_using.html   ... View more