@challa vinitha Could you please clarify your question in more detail? ... View more

@Jakub Igla This means that the members of this groups should receive implicit admin permissions when logged in to Ambari. It is just a simple group name, e.g. "cloudbreak" Hope this helps! ... View more

@Wei Law It seems like the stack was in "STOP_IN_PROGRESS" state, meaning that it could not be stopped again. It can take some time for the cloud provider to delete all the resources, you can check the progress in the Azure portal. Here is the relevant code. Hope this helps! ... View more

@Matt Cable This feature is being implemented, and will be part of the upcoming Cloudbreak 2.8 version in the near future. Hope this helps! ... View more

@Tejaswi Chandra May I ask why you are implementing this manually? With Cloudbreak, it can be configured automatically: https://docs.hortonworks.com/HDPDocuments/Cloudbreak/Cloudbreak-2.7.1/content/external-ldap/index.html Hope this helps! ... View more

@Matt Cable If you are willing to complete some very easy manual steps, there is another way to go, as Cloudbreak uses separate autoscaling groups for each hostgroup: You should: notice the AMI is of your custom, updated AMI and the original AMI for each region you use, search the available LaunchConfigurations in the given region created with the original AMI create a copy based on each found such LaunchConfiguration, with two differences: The name should be renames The ImageId should be set to the id of your new AMI Search for all the AutoScalingGroups created with the previously found LaunchConfiguration Update the found AutoScalingGroup by replacing the original LaunchConfiguration to the newly created one with the migrated AMI-id Deletes the original LaunchConfiguration After these steps, all your subsequent upscales will use your new AMI. Hope this helps! ... View more

@Kevin B I am not sure I get your point. The original question has been answered in my first answer, everything can be automated fully with the CB CLI and you don't need to use a recipe for that. You don't need to use ansible scripts either as the whole process can be implemented with a handful of Cloudbreak CLI calls. Please comment if I misunderstood your question. Hope this helps! ... View more

@Kevin B You have the option in Cloudbreak 2.7.1 to register the Management Pack with the URL described in the official docs, and assign the registered MPack to the cluster in the cluster creation wizard (CB docs here). You can automate it with the CB CLI, too. Hope this helps! ... View more

@Venkat ramanann There are no generally applicable guidelines, it depends on the type of your workloads. There is a good analysis in case you are on AWS here, though. Hope this helps! ... View more

@JJ Recipes are attached to the cluster in the cluster creation wizard. The exact method depends on your CB version, but for 2.x versions, you should switch on "Advanced" options. You can assign the recipes per host groups. For the new nodes added, recipes will run automatically. Pls. find more info here and here. Hope this helps! ... View more

@Marshal Tito Unfortunately, the user and account management feature is yet to implemented in the new CB 2.x version line, it is on our roadmap to support it. The referred docs were applicable for only CB 1.x versions. Sorry about the inconvenience caused. ... View more

@Marshal Tito You can use ADLS via a connector which is to help you connect to, access, and work with data the cloud storage services. These connectors are not a replacement for HDFS and cannot be used as a replacement for HDFS defaultFS . You can read more here: https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.1/bk_cloud-data-access/content/intro.html Hope this helps! ... View more

@Jody H It is not a problem to have all the services in a single container, it might be a Docker anti-pattern, but it should work, you can go that way. Cloudbreak has not been creating HDP clusters in Docker containers for ~2 years now, before then CB deployed into containers, but there were some stability and enterprise supportability issues with that approach back then, which might have been resolved since then. Hope this helps! ... View more

Hi @Jeff Jennings 1. Right now, there is no default blueprint containing Ranger. Here is my previous answer for more details on this topic. 2. Yes, if CB and the on-prem AD Server can communicate, then yes. Hope this helps! ... View more

@Anurag Mishra I know it is a very old thread but in case it is still actual, Cloudbreak can help launching HDP or HDF in Google Cloud. Please see here: https://docs.hortonworks.com/HDPDocuments/Cloudbreak/Cloudbreak-2.5.0/content/gcp-launch/index.html Hope this helps! ... View more

It depends on your setup, but maybe Ambari is not necessary at all. You can find more information about the typical problems to solve here and some working docker containers here and here. Hope this helps! ... View more

@prarthana basgod I agree, this part of the logging is not verbose enough to find out the root cause. What is your CB version? If you have a support subscription, feel free to open a ticket and we will happy to assist you in the further investigation, if not could you attach the whole cbreak.log, ambari-server.log and ambari-agent.log? ... View more

@Tok Luo If you do not stick to this two-phased solution, another approach you can take is to install HDF with Cloudbreak 2.5 itself. Here is a tutorial as well: https://community.hortonworks.com/articles/182221/create-a-nifi-cluster-on-aws-azure-google-or-opens.html Hope this helps! ... View more

@prarthana basgod Do you have any updates on this issue? ... View more