Chapter 1. Deployment Scenarios
Your deployment scenario for installing, configuring, or upgrading your Hortonworks DataFlow (HDF) components depends on your particular use case.
![[Note]](../common/images/admon/note.png) | Note |
|---|---|
This document describes how to install Ambari and HDF on IBM Power Systems. To install Ambari and HDF on Intel x86 hardware, review your deployment options using Planning Your Deployment. |
Table 1.1. Installation Scenarios
| Scenario | Installation Scenario | Steps | ||||||
|---|---|---|---|---|---|---|---|---|
|
This scenario applies if you want to install the entire HDF platform, consisting of all flow management and stream processing components on a new cluster. The stream processing components include the new Streaming Analytics Manager (SAM) modules that are in GA (General Availability). This includes the SAM Stream Builder and Stream Operations modules but does not include installing the technical preview version of SAM Stream Insight, which is powered by Druid and Superset. This scenario requires that you install an HDF cluster. |
| |||||||
|
This scenario applies to you if you are both an Hortonworks Data Platform (HDP) and HDF customer and you want to install a fresh cluster of HDP and add HDF services. The stream processing components include the new (SAM) and all of its modules. This includes installing the technical preview version of the SAM Stream Insight module, which is powered by Druid and Apache Superset. This scenario requires that you install both an HDF cluster and an HDP cluster.
|
| |||||||
|
You have an existing HDP cluster with Apache Storm and or Apache Kafka services and want to install Apache NiFi or NiFi Registry modules on that cluster. This requires that you upgrade to the latest version of Apache Ambari and HDP, and then use Ambari to add HDF services to the upgraded HDP cluster.
|
| |||||||
|
Performing any of the previous deployments by using a local repository See Using Local Repositories in the instructions appropriate for your scenario. |
Local repositories are frequently used in enterprise clusters that have limited outbound internet access. In these scenarios, having packages available locally provides more governance and better installation performance. This requires that you perform several steps to create a local repository and update the Ambari repository configuration file. |
|
![[Important]](../common/images/admon/important.png)
Table 1.2. Upgrade Scenarios
| Scenario | Upgrade Scenario | Steps | |||
|---|---|---|---|---|---|
|
You have an existing Ambari-managed HDF cluster and want to upgrade it using either Rolling or Express upgrade.
|
| ||||
| You have an existing Ambari-managed HDP cluster with NiFi installed. You want to upgrade the NiFi service installed on your HDP cluster. |
| ||||
| You have an existing Ambari-managed HDF cluster with all your HDF services installed and you want to upgrade the NiFi service, and migrate SAM and Schema Registry to an HDF cluster. |
|