Using Kudu with CDH 5.12 or Earlier

For Kudu 1.4 and earlier with CDH 5.12 and earlier, the Kudu service is distributed in its own parcel and is not part of CDH. To add Kudu to a CDH 5.12 or earlier cluster, bootstrapped by Altus Director, perform the following steps.
  1. List "KUDU" as a product in the cluster template, providing its version number.
  2. Include the URL for a Kudu parcel repository in the list of parcel repositories for the cluster template. Be sure to also include the URL for the CDH parcel repository, even if it is the default repository that Altus Director uses when no parcel repositories are listed.
  3. Manually assign roles for Kudu, as well as other products, to instances in the cluster template.
  4. Provide required Kudu configuration properties, such as the paths for the data and write-ahead log files.
```
cluster {
  products {
    CDH: 5.11.0,
    KUDU: 1.2.0
  }
 
  parcelRepositories: ["https://archive.cloudera.com/cdh5/parcels/5.11.0/",
                      "https://archive.cloudera.com/kudu/parcels/5.11.0/"]
 
  services: [HDFS, YARN, KUDU]
 
  masters {
    count: 1
    instance: {
      type: m4.xlarge
      image: ami-12345678
    }

    roles {
      HDFS: [NAMENODE, SECONDARYNAMENODE]
      YARN: [RESOURCEMANAGER, JOBHISTORY]
      KUDU: [KUDU_MASTER]
    }

    configs {
      KUDU {
        KUDU_MASTER {
          fs_wal_dir: "/data0/kudu/masterwal"
          fs_data_dirs: "/data1/kudu/master"
        }
      }
    }
 }
  workers {
    count: 3
    minCount: 3
    instance: {
      type: m4.xlarge
      image: ami-12345678
    }

    roles {
      HDFS: [DATANODE]
      YARN: [NODEMANAGER]
      KUDU: [KUDU_TSERVER]
    }

    configs {
      KUDU {
        KUDU_TSERVER {
          fs_wal_dir: "/data0/kudu/tabletwal"
          fs_data_dirs: "/data1/kudu/tablet"
        }
      }
    }
  }
}
```

The Kudu configurations above are examples only. Check the Kudu documentation for the complete set of required configurations. Also note that valid paths for files depend on the file systems that are established in cluster instances, which depend on the underlying operating system images.

The CSD for Kudu is included with Cloudera Manager starting with version 5.11. If you are using that version or later of Cloudera Manager, you do not need to list the Kudu CSD in the csds section of the deployment template. Otherwise, do include the CSD.
```
cloudera-manager {
  ...
  # Kudu CSD is not included with Cloudera Manager 5.10
  csds: [
     "https://archive.cloudera.com/kudu/csd/KUDU-5.10.0.jar"
   ]
}
```

To learn more about using Kudu alongside CDH, see Installing Kudu in the Cloudera Enterprise documentation.