Launch Cloudbreak on Azure

Before launching the Cloudbreak, make sure that you've met the prerequisites and have read and agree to the Cloudbreak on Azure Marketplace Terms.

Launch the Cloudbreak VM

  1. Log in to your Azure Portal.

  2. From the services menu, select .

  3. In the search box, enter "Cloudbreak":

  4. Select .
    The information about the Cloudbreak for Hortonworks Data Platform will be displayed. In the bottom of the page, you will see a dropdown for selecting a deployment model, with the Resource Manager deployment model pre-selected. This is the only deployment model available for this offering.

  5. Click Create.

  6. The template for installing Cloudbreak will appear. On the Basics page, provide the following basic parameters:

    Parameter Description
    Administrator email address Create an admin login that you will use to log in to the Cloudbreak UI. Must be a valid email address.
    Administrator user password Password for the admin login. Must be at least 8 characters containing letters, numbers, and symbols.
    Confirm password Confirm the password for the admin login.
    VM Username Enter an admin username for the virtual machine. You will use it to SSH to the VM.
    VM SSH public key

    Paste your SSH public key.

    You can use pbcopy to quickly copy it. For example: pbcopy < /Users/homedir/.ssh/id_rsa.pub

    Subscription Select which existing subscription you want to use.
    Resource group Only Create new is supported. Select Create new to create a new resource group and enter a name for your new resource group. Cloudbreak resources will later be accessible in that chosen resource group.
    Location Select an Azure region in which you want to deploy Cloudbreak.
  7. Once done, click OK.

  8. On the Advanced Settings page, provide the following advanced parameters:

    Parameter Description
    Controller Instance Type Select virtual machine instance type to use for the Cloudbreak. The minimum instance type suitable for Cloudbreak is D2.
    Allow connections to the cloud controller from this address range or default tag

    Enter a valid CIDR IP or use one of the default tags such as Internet. For example:

    • 10.0.0.0/24 will allow access from 10.0.0.0 through 10.0.0.255
    • 'Internet' will allow access from all. This is not a secure option but you can use it it you are just getting started and are not planning to have the instance on for a longer period.
    • (Advanced) 'VirtualNetwork' will allow access from the address space of the Virtual Network.
    • (Advanced) 'AzureLoadBalancer' will allow access from the address space of the load balancer.

    For more information, refer to the Azure documentation.

    Enable SmartSense (Optional) Select whether to enable SmartSense telemetry. Default is I have read and opt-in to SmartSense telemetry. SmartSense provides product telemetry and usage information to Hortonworks. For more information, refer to the SmartSense terms.
    Virtual network Create a new Vnet (default) or select an existing Vnet.
    Subnets If you created a new Vnet, create subnets within it. If selected an existing Vnet, select exiting subnets.
  9. Once done, click OK.

  10. On the Summary page, validate the information that you provided. Before proceeding to the next page, you have an option to Download template and parameters. You can use them to launch Cloudbreak via CLI. Once done, click OK.

  11. Review terms of use and click Purchase.

  12. Proceed to the next step: Explore Newly Created Resources

Explore Newly Created Resources

This step is optional.

While the deployment is in progress, you can optionally navigate to the newly created resource group and see what Azure resources are being created.

  1. From the left pane, select .

  2. Find the the resource group that you just created and select it to view details.

  3. The following resources should have been created in your resource group:

  4. You can click on each entry to view details of the resource. For example, click on to view details, including Cloudbreak IP address.

  5. Once your deployment is ready, the status will change from "Deploying" to "Success".

Access Cloudbreak UI

  1. When your deployment succeeds, you will receive a notification in the top-right corner. You can click on the link provided to navigate to the resource group created earlier.

    This only works right after deployment. At other times, you can find your resource group by selecting Resource Groups from the service menu and then finding your resource group by name.

  2. Once you've navigated to your resource group, click on Deployments and then click on hortonworks.cloudbreal-for-hortonworks-data-platf-...:

  3. From Outputs, you can copy the link by clicking on the icon:

  4. Paste the link in your browser's address bar.

    The first time you access Cloudbreak UI, Cloudbreak will automatically generate a self-signed certificate, due to which your browser will warn you about an untrusted connection and will ask you to confirm a security exception. You can safely proceed to the website.

    Browser Steps
    Firefox Click Advanced > Click Add Exception... > Click Confirm Security Exception
    Safari Click Continue
    Chrome Click Advanced > Click Proceed...
  5. Now you should be able to access Cloudbreak UI and log in with the Admin email address and Admin password that you created when launching Cloudbreak:

  6. Upon a successful login, you are redirected to the dashboard:

The last task that you need to perform before you can use Cloudbreak is to create a cloudbreak credential.

Create Cloudbreak Credential

Before you can start creating clusters, you must first create a Cloudbreak credential. Without this credential, you will not be able to create clusters via Cloudbreak. Cloudbreak works by connecting your Azure account through this credential, and then uses it to create resources on your behalf.

There are two methods for creating a Cloudbreak credential:

Method Description Prerequisite Steps
Interactive The advantage of using this method is that the app and service principal creation and role assignment are fully automated, so the only input that you need to provide is the Subscription ID and Directory ID. During the interactive credential creation, you are required to log in to your Azure account. (1) Your account must have the "Owner" role (or its equivalent) in the subscription. (2) You must be able log in to your Azure account. To configure an interactive credential, refer to Create an Interactive Credential.
App-based The advantage of the app-based credential creation is that it allows you to create a credential without logging in to the Azure account, as long as you have been given all the information. In addition to providing your Subscription ID and Directory ID, you must provide information for your previously created Azure AD application (its ID and key which allows access to it). (1) Your account must have the "Contributor" role (or equivalent) in the subscription. (2) You or your Azure administrator must perform prerequisite steps of registering an Azure application and assigning the "Contributor" role to it. This step typically requires admin permissions so you may have to contact your Azure administrator. To configure an app based credential, refer to Create an App Based Credential.

Create an Interactive Credential

Follow these steps to create an interactive Cloudbreak credential.

Steps

  1. In the Cloudbreak web UI, select Credentials from the navigation pane.

  2. Click Create Credential.

  3. Under Cloud provider, select "Microsoft Azure".

  4. Select Interactive Login:

  5. Provide the following information:

    Parameter Description
    Name Enter a name for your credential.
    Description (Optional) Enter a description.
    Subscription Id Copy and paste the Subscription ID from your Subscriptions.
    Tenant Id Copy and paste your Directory ID from your Active Directory > Properties.
    Azure role type

    You have the following options:

    • "Use existing Contributor role" (default): If you select this option, Cloudbreak will use the "Contributor" role to create resources. This requires no further input.
    • "Reuse existing custom role": If you select this option and enter the name of an existing role, Cloudbreak will use this role to create resources.
    • "Let Cloudbreak create a custom role": If you select this option and enter a name for the new role, the role will be created. When choosing role name, make sure that there is no existing role with the name chosen. For information on creating custom roles, refer to Azure documentation.

    If using a custom role, make sure that it includes the necessary Action set for Cloudbreak to be able to manage clusters: Microsoft.Compute/*, Microsoft.Network/*, Microsoft.Storage/*, Microsoft.Resources/*.

    To obtain the Subscription Id:

    To obtain the Tenant ID (actually Directory Id):

  6. After providing the parameters, click Interactive Login.

  7. Copy the code provided in the UI:

  8. Click Azure login and a new Device login page will open in a new browser tab:

  9. Next, paste the code in field on the Device login page and click Continue.

  10. Confirm your account by selecting it:

  11. A confirmation page will appear, confirming that you have signed in to the Microsoft Azure Cross-platform Command Line Interface application on your device. You may now close this window.

    Congratulations! You've successfully launched and configured Cloudbreak. Now you can use Cloudbreak to create clusters.

Create an App Based Credential

Follow these steps to create an app based Cloudbreak credential.

Prerequisites

  1. On Azure Portal, navigate to the Active Directory > App Registrations and register a new application. For more information, refer to Create an Azure AD Application.

    Aa an alternative to the steps listed below for creating an application registration, you use a utility called azure-cli-tools. The utility supports app creation and role assignment. It is available at https://github.com/sequenceiq/azure-cli-tools/blob/master/cli_tools.

  2. Navigate to the Subscriptions, choose Access control (IAM). Click Add and then assign the "Contributor" role to your newly created application by selecting "Contributor" under Role and your app name under Select:

    This step typically requires admin permissions so you may have to contact your Azure administrator.

Steps

  1. In the Cloudbreak web UI, select Credentials from the navigation pane.

  2. Click Create Credential.

  3. Under Cloud provider, select "Microsoft Azure".

  4. Select App based Login:

  5. On the Configure credential page, provide the following parameters:

    Parameter Description
    Select Credential Type Select App based.
    Name Enter a name for your credential.
    Description (Optional) Enter a description.
    Subscription Id Copy and paste the Subscription ID from your Subscriptions.
    Tenant Id Copy and paste your Directory ID from your Active Directory > Properties.
    App Id Copy and paste the Application ID from your Azure Active Directory > App Registrations > your app registration's Settings > Properties.
    Password This is your application key. You can generate it from your Azure Active Directory app registration's Settings > Keys.

    To obtain the Subscription Id from Subscriptions:

    To obtain the App ID (actually Application ID) and an application key from Azure Active Directory:

    To obtain the Tenant ID (actually Directory Id) from Azure Active Directory:

  6. Click Create.

    Congratulations! You have successfully launched Cloudbreak and created a Cloudbreak credential. Now you can use Cloudbreak to create clusters.

Related Links
CLI Tools (Hortonworks)
Use Portal to Create an Azure Active Directory Application (External)