Just some clarifications to the instructions provided in this article. Hopefully, it will save you time to get you up and running faster. 1) Nifi 401:Unauthorized Error If you see a similar error message in the Nifi console: ERROR [Timer-Driven Process Thread-6] o.a.nifi.processors.standard.PostHTTP PostHTTP[id=834bb9f9-a15d-42bd-8d7a-3f00c810d729] Failed to Post StandardFlowFileRecord[uuid=bc74e1c5-12e7-4da2-93b4-a3dc624218ac,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1471370511531-1, container=default, section=1], offset=11780, length=407],offset=0,name=12406098021784,size=407] to http://gcm-http.googleapis.com/gcm/send: response code was 401:Unauthorized and when you click "Notify Customer" in the Analyst's console and no event is updated on the Android emulator in Android Studio. Resolution 401:Unauthorized Error Open open the UpdateAttribute processor and add a new property called Authorization and set its value to key=your google browser key 2) Wrong Google API number The API project number is 12 digits. Do not use the number at the end of the Google API Project ID. For example, ID: api-project-555555555 Resolution Google API number Use the number given in the Google API console at Project Number (see screenshot below). This will to successfully link from the Sandbox to the mobile emulator; otherwise, you'll click "Notify Customer" in the Analyst's console and no event is updated on the Android emulator in Android Studio. 3) Mobile Application Compilation FYI I thought it helps to provide and example to this section of the Readme because it severely edits the XML syntax. Under the res folder, browse to: app-->res-->values-->google_maps_api.xml (debug): string name="google_maps_key" templateMergeStrategy="preserve" translatable="false" ENTER YOUR GOOGLE BROWSER KEY CREDENTIAL HERE /string Here's what it looks like in Android Studio with xml syntax preserved shown in green box below between "><" identifying the string. Hope this helps! ... View more

I've received a couple of "how to" questions after folks successfully deploy the Hortonworks Data Platform Standard on Microsoft's Azure. I've collected my responses here as a reference to others: What is Hortonworks Data Platform (HDP) Standard? It is a muti-node HDP 2.4/Ambari 2.2.1 cluster on Microsoft’s Azure Cloud launched in a few mouse clicks. Hortonworks aims to match this service with the latest version of HDP. You provide: your name email passwords or ssh key the number of nodes the VM types for your masters and workers should your cluster be HA or not as shown in this screenshot: Where's Ambari? Once the cluster is successfully deployed, the Azure Dashboard will go from something like: to the Ambari service is located on the first master server. In the Azure portal goto Resource group, <your resource group name which was selected at first "Basics" step>, master1, settings and look for Public IP address. Use a web browser to access Ambari with: <master1 Public IP address>:8080 What's the Ambari username? The default username is "admin". The password was set under "Ambari password" in the screenshot above. What are my ssh parameters? The HDP service ports are enabled by default during the cluster installation. The master nodes allow external ssh access so use the cluster creation fields in the screenshot above in a terminal: ssh <cluster admin username>@<your cluster name>-master-01.cloudapp.net Worker nodes are only accessible via ssh from any of the master nodes. Why am I receiving "Operation result in exceeding quota limits on Core"? The default Azure Resource Manager (ARM) cores is 20 and not enough to deploy an HDP Standard cluster. Prior to deploying the cluster, request a ARM core quota increase to at least 120. Details to request a quota increase are here and remember ARM core resources are Azure region specific. ... View more

Here are some lessons learned while trying to deploy the latest version of Cloudbreak (1.1.0) on Azure. Please refer to the latest Hortonworks Cloudbreak documentation for the detailed steps and use this article as a supplement until the documents are updated. Logging into the Deployer VM There is a prebuilt image for Azure Cloudbreak deployer. This image does not require a ssh key; however, record the username and password you've specified at setup in the Azure portal (see the section in green highlight below). Those are your credentials to login to the deployer VM and setup Cloudbreak services later. Once the VM deploys (refer to the Azure portal for status), grab the the Public IP specified in the Azure portal and ssh into the VM. Ssh into the Deployer VM by, ssh <your specified username>@<public IP specified in Azure portal> password: <enter you specified password> Deployer VM run initiation steps Once you've logged into the Deployer VM, run these initiation steps which are currently missing from the document: Create a file called Profile cd ~ vi ./Profile Add the following, export PUBLIC_IP=<the public IP address of the Deployer VM> You can always find the Deployer VM's public IP address in the Azure portal. And do not leave a space between the equals and IP e.g. PUBLIC_IP=12.34.245 rather than PUBLIC_IP= 12.34.245 Now run the following, cbd init The output looks something like, Profile already exists, now you are ready to run: cbd generate ===> Deployer doctor: Checks your environment, and reports a diagnose. local version:1.1.0 latest release:1.1.0 docker command: OK docker client version: OK docker server version: OK Now run cbd generate and enter the VM’s password you specified at setup when prompted. The output looks something like: generating docker-compose.yml generating uaa.yml At this point you can run the 'cbd' commands for the Azure application setup with Cloudbreak Deployer and deployment of a DASH service in Cloudbreak Deployer as shown in the document. Displaying your Cloudbreak UI credentials Run the following command to output your Cloudbreak UI credentials (Note: you don't use your Azure AD user for this login), cbd login It will output something like, Uluwatu (Cloudbreak UI) url: http://<Deployer VM's public IP>:3000 login email: ***@******.com password: ********* Request an Azure quota increase Lastly, Azure has a default limit of 20 cores in a region. Follow these steps to request a quota increase because the Deployer VM together with a deployment of the hdp-small-default Ambari blueprint will exceed the default core limit resources. Happy Cloudbreak deploying!! ... View more