Member since
10-01-2018
5
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2121 | 02-05-2019 08:35 AM |
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.
... View more
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.
... View more
10-03-2018
10:00 AM
1 Kudo
I tried the same on a vm provisioned from a similar AMI in a US region and I'm not seeing any errors. Is this happening consistently, even on new VMs?
... View more
10-01-2018
10:42 AM
Was this a local install of CentOS 7.5 from source media, or a VM running in a public cloud? If it's a cloud VM, can you point to the specific AMI or VM Image that was used?
... View more