Adding a flow to an existing deployment

Follow these instructions to deploy your new flow into an existing cluster.

In the Add Flow to Existing Deployment modal, select the deployment where you want to add the new flow and click Continue

Name your flow

When you add a flow to an existing deployment you must provide a flow name that is unique within that deployment. You can import an existing flow configuration to speed up flow deployment.

warning

When you add a flow version that requires custom NARs or custom Python processors to an existing deployment which does not already have those resources in place, Cloudera Data Flow gives you a warning instructing you to add the missing resource before proceeding.

Failing to add a custom NAR to your deployment before deploying the flow version results in erroneous operation until you add the NAR and Cloudera Data Flow recognizes the change. This may not be an issue in testbed use, but you should avoid it in production use.

Adding a custom Python processor to a deployment after you deployed a flow version has absolutely no effect on the operation of the already deployed flow. You can only fix that issue by opening the flow description in Flow Designer for editing, removing and then re-adding the custom Python processor, publishing your changes as a new flow version, and performing a flow version change on your flow. This sequence of actions changes the ID of the component and causes Cloudera Data Flow to pick up the custom Python processor that you have added post-deployment.

Provide a unique Flow Name.
This name helps you distinguish between individual instances of a flow within a deployment.
note

Flow name must be unique within a deployment. The deployment wizard marks a name valid by displaying a green checkmark below the Flow Name text box.
Optional: If you have previously exported a configuration that closely aligns with the one you are deploying now, you can import it under Import Configuration to auto-fill as much of the wizard as possible.
You can overwrite imported configuration values in the deployment wizard.
Optional: If you do not want the flow to start running after deployment, unselect the Automatically start flow upon successful deployment checkbox.
If the flow version you are deploying requires an inbound connection and the target deployment does not have one, you see a warning. You cannot proceed until you either add an inbound conection configuration to the deployment in the Deployment Manager, or you select the I understand and choose to proceed with the configuration as is. option.

If you click To set a Custom Inbound Connections Configuration open the Deployment Manager option, Deployment Manager opens in a new window where you can configure an inbound connection before proceeding with adding the flow.

If you select the I understand and choose to proceed with the configuration as is. option, the Next button becomes active and you can proceed with adding the flow without configuring the inbound connection at this time.

tip
If you do not configure an inbound connection now, unselect the Automatically start flow upon successful deployment option and configure the inbound connection before starting the flow in Deployment Manager.
Click Next .

Provide parameter values

Depending on the flow you deploy, you may need to specify parameter values like connection strings or credentials, and upload files like truststores or JARs.

Provide values to parameters required for your flow deployment.
You have to provide values for all parameters. Filter for empty fields by selecting the No value checkbox.

tip
If you are deploying a ReadyFlow, you can learn about required parameters and instructions on how to obtain parameter values by checking Prerequisites and Required parameters in the documentation of the respective ReadyFlow.
When you finish setting configuration parameters, click Next .
You may edit parameters individually by clicking the edit icon next to them or you may edit entire parameter groups by selecting the Edit Group option.

In either case, you have the option to define a custom parameter value that is specific to this deployment or, if available, select the value from a shared parameter group.
You may import a set of shared parameters from a parameter group to fill in values and facilitate flow deployment. To do so, select the Import Shared Parameters option.
- Parameters in the shared group that match a deployment parameter are preselected, unless you have already modified that parameter in the deployment wizard. In that case that particular parameter is left unselected to protect any changes you have already made and you need to manually select that parameter.

Set Key performance indicators

Optionally add key performance indicators to help you track the performance of your flow deployment then review your settings and launch the deployment process.

From KPIs, you may choose to identify key performance indicators (KPIs), the metrics to track those KPIs, and when and how to receive alerts about the KPI metrics tracking.

tip

You can reorder the KPIs by dragging them up or down the list. The order you configure here will be reflected in the detailed monitoring view of the resulting deployment.

See Working with KPIs for complete information about the KPIs available to you and how to monitor them.

note
If you deploy a flow to an exsting deployment, you can only define KPIs for the new flow, you cannot add or change deployment-related KPIs.
Click Next .

Verify your settings and initiate deployment

Review deployment settings, make any necessary changes, and start deployment.

Review a summary of the information provided and make any necessary edits by clicking Previous.
When you are finished, complete your flow deployment by clicking Deploy.

tip

Click View CLI Command to see the equivalent Cloudera CLI syntax in a help pane.

After you click Deploy, you are redirected to the Alerts tab in the Flow Details where you can track how the deployment progresses.