Transitioning the cluster

Transition the HDP cluster managed by Ambari to CDP Private Cloud Base cluster managed by Cloudera Manager using the AM2CM tool.

Take a copy of your blueprint before transitioning your cluster. It helps you to understand the changes and differences between HDP 2.6.5 versus HDP 7.1.x versus Cloudera Manager. Use this to take the blueprint: http://<ambari_ip>:<port>/api/v1/clusters/<cluster-name>?format=blueprint. You cannot to take the blueprint after transitioning the cluster.
Perform the following steps:
  1. Login to Ambari server.
  2. In the new tab, enter the URL: http://<ambari_ip>:<port>/api/v1/clusters/<cluster-name>?format=blueprint_with_hosts
  3. Download the Ambari blueprint and save it in JSON format.
  4. Download the AM2CM tool from: http://archive.cloudera.com/am2cm/1.x/am2cm-1.0.0.0-58.tar.gz

    To find all the download links in a centralised location, see Software download matrix

  5. Extract the am2cm-1.0.0.0-xx.tar file to am2cm-1.0.0.0-xx folder.
  6. Set the JAVA_HOME variable.
  7. Navigate to the am2cm-1.0.0.0-xx/conf/user-settings.ini file and update Parcels, Cluster name, passwords, and JDBC URL information.
    
    # Cluster details 
    cluster.name=<Cluster-Name> 
    cluster.displayname=<Cluster-Name>
    cluster.fullversion=7.1.1
    
    # Hive JDBC settings
    SERVICE_HIVE_hive_metastore_database_password=<DB-Password>
    SERVICE_HIVE_hive_jdbc_url_override=<JDBC_URL>
    
    # Oozie JDBC settings
    SERVICE_OOZIE_oozie_database_password=<DB-Password>
    SERVICE_OOZIE_oozie_service_JPAService_jdbc_url=<JDBC_URL>
  8. Run the command to generate the Cloudera Manager Deployment template.
    # cd am2cm-1.0.0.0-xx
    #chmod +x ./am2cm.sh
    # ./am2cm.sh  -bp PATH/TO/Amb_blueprint.json  -dt /PATH/TO/cm_deployment_template.json
  9. You can check for errors in the console or in the am2cm-1.0.0.0-xx/cm_migration.log logs. For example, sh am2cm.sh.
  10. Go to the Parcels/Parcel Repository & Network Settings page on Cloudera Manager user interface and add Remote Parcel Repository URLs.
    For more information configuring the repository URLs see, Configure a Repository for Cloudera Manager.
  11. LZO package configuration: If HDP is configured with LZO packages then follow below steps.
    1. In Cloudera Manager , go to Parcels / Parcel Repository & Network Settings under Remote Parcel Repository URLs add https://archive.cloudera.com/p/gplextras7/7.1.1.0/parcels/ URL
    2. In Parcels screen - Download, Distribute and Activate “GPLEXTRAS” If the HDP intermediate bits or Ambari 7.1.x.x has LZO packages used, then enable or add the packages to Cloudera Manager. For more information, see Configuring Data Compression documentation.
  12. Stop HDP services from Ambari.
  13. Import the template using the API through browser or CLI.
    • Using browser:
      1. Copy the URL in the browser and enter. http://<CM_HOST>:7180/static/apidocs/ui/index.html#!/ClouderaManagerResource/updateDeployment2
      2. Navigate to Cloudera ManagerResource
      3. Copy the template in body.
      4. Click Tryit out!
    • Using CLI:
      curl --user admin:admin -k -X PUT -H "Content-Type: application/json" -d @cm_deployment_template.json 'http://<CM_HOST>:7180/api/v41/cm/deployment?deleteCurrentDeployment=false'
  14. In Cloudera Manager Parcel screen, download Cloudera Runtime and distribute the parcel. Cloudera Manager deploys the parcel to the cluster hosts. The default is 10 concurrent hosts. You can adjuste this to a maximum of 50, but must be configured before the template is applied.
  15. After the parcels are deployed on Cloudera Manager, activate the Cloudera Runtime 7.1.x parcels.