Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created on 02-05-2019 01:27 AM - edited 09-16-2022 07:07 AM
Hi,
is it supported to submit a new cluster template to Cloudera Altus Director and use an existing Cloudera Manager installation?
I had a Director template for Cluster A and CM A and it was deployed sucessfully. As the Director server was not needed any more, it was deleted (so the operations is managed by CM, but no changes were made in cluster config).
Now I would like to create Cluster B also with Director, but to point to an existing Cloudera Manager A (and thus using the same KDC)
Is this supported?
Thanks
Created 02-05-2019 08:35 AM
Altus Director does have some limited ability to use an existing CM server (see the notes in https://github.com/cloudera/director-scripts/blob/master/configs/aws.reference.conf#L487-L490). There are gaps in what CM related features will work, especially around TLS/SSL and external databases.
Do you happen to have a backup of the old Director's database? If so, you could use that to restore the state on a new Director server.
For either of the above paths, I would recommend opening a support case with Cloudera if you need to pursue this for a production cluster.
Created 02-05-2019 07:51 AM
Unfortunately Altus Director is not able to use an existing CM deployment to create a new deployment. If you used a configuration file for the original deployment, then that configuration file could be used for a new deployment via a new Altus Director. See this documentation for information on how to use configuration files, which is the recommended method for repeatable templated deployments.
Created 02-05-2019 08:05 AM
Created 02-05-2019 08:35 AM
Altus Director does have some limited ability to use an existing CM server (see the notes in https://github.com/cloudera/director-scripts/blob/master/configs/aws.reference.conf#L487-L490). There are gaps in what CM related features will work, especially around TLS/SSL and external databases.
Do you happen to have a backup of the old Director's database? If so, you could use that to restore the state on a new Director server.
For either of the above paths, I would recommend opening a support case with Cloudera if you need to pursue this for a production cluster.