Hi, You asked multiple question, I'll try to make a list out of it and answer them in order Where I can find updated information upon how to install a small cluster in Azure? This would consist of 2 steps. First you need to deploy your own Cloudbreak Installation. We have a tool for that called cbd. I would advise to follow one of our quick start guides: https://github.com/hortonworks/azure-cbd-quickstart The second step is once you have Cloudbreak running, you can start creating your clusters. Is it possible to store the parameters and be able to launch the cluster on Azure at will without having to spend a lot of time configuring the same things? You can easily reproduce an HDP cluster once you did the initial configuration. You just need to save the cluster descriptor json and feed that to one of our APIs. Do you know if there is a way to launch already preconfigured clusters from a blueprint? Yes, Cloudbreak comes with Default Ambari blueprints built in. These blueprint define what services should be installed on the Cluster. You can also specify custom blueprints if you are not satisfied with the built in ones. Say for example that I have a script which automatically provides 5 or 6 VMs on Azure and then launce HDP automatically? You don't need to fiddle with custom scripts, cloudbreak can provision machines, networks,disk, anything that is needed for a cluster. ... View more

Hi, @automating cluster creation Using the CLI for automated cluster setup is a valid approach. @security Storing secure data in git repository is not a good idea. I would assume that you have Cloudbreak deployed and a CI job would have a configured cli to use it. I would also assume that this machine is secured as if you have access to this machine, you basically have access to everything cloudbreak stores. The configuration for CLI is located usually in ~/cb/config, and has the following testenv1: username: user1 password: user1pw server: 10.0.10.12 I'm not sure what kind of CI framework you plan to use (jenkins, teamcity, spinnaker), but basically you could have a CLI installed on an agent or a docker container having the cli and an example configuration file injected from the context of the CI build agent. Another idea is to have the encrypted cli config stored in github, and have the agent the decryption key, and apply the correct config. ... View more