cloudera-deploy
cloudera-deploy copied to clipboard
cloudera-labs
A general purpose framework for automating Cloudera Products
How to use tags like `infra` with the v2 (i.e. the `cloudera.exe` playbooks) -- the legacy `-t run` is no longer valid.
after deployment of the CDP private cluster and change of ```definition.yml``` for example hdfs failed volumes tolerated, like: ``` configs: HDFS: DATANODE: dfs_datanode_failed_volumes_tolerated: 3 ``` when running the playbook again,...
Listed below are the full sets of configurations that can be used in the DW playbook. ``` dw: overlay_network: {'yes' to enable overlay network} private_load_balancer: {'yes' to enable private load...
I was able to deploy the cdp private without any credentials, only cdp license has been used. I am trying to teardown our deployed cluster via tags ```-t teardown,all``` ....
I tried to run the playbook in DEBUG mode and found that a local ssh connection failed: `[email protected]: Permission denied (publickey,password)` Turned out that in cloudera-deploy ~/.ssh is mounted under...
Not sure I'm missing a simpler strategy, on howto prepare a new "cluster.yml" file required by this playbook (to be configured in the definition_path), from an exportable CDP (7.1.x /...
Print all `Cloudera Manager` nodes deployed to the log at the end of the run.
> a few notes on this example: > Can we avoid hardcoding instance type, instance counts, disk sizes/types and ami types inside the terraform config files? Would like to have...
> Would like to use a ElasticIP on the bastion, instead of transient public IP. ty _Originally posted by @clevesque in https://github.com/cloudera-labs/cloudera-deploy/issues/143#issuecomment-2150616941_
Metadata
Owner
Metadata
A general purpose framework for automating Cloudera Products