Member since
07-25-2019
184
Posts
42
Kudos Received
39
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1012 | 03-25-2019 02:25 PM | |
547 | 01-22-2019 02:37 PM | |
492 | 01-16-2019 04:21 PM | |
1034 | 10-17-2018 12:22 PM | |
659 | 08-28-2018 08:31 AM |
08-17-2018
03:56 PM
@sunile.manjee That tutorial is not 100% correct, you can set fine grained RWX ACL permissions for your application to the files and folders of your ADLS account, as documented here and setting those properly should be enough to work with your ADLS account without granting the application any roles. Hope this helps!
... View more
08-15-2018
12:08 PM
@challa vinitha Could you please clarify your question in more detail?
... View more
08-15-2018
11:34 AM
@sunile.manjee In the Cloudbreak 2.x versions, there is no account management yet, so you cannot change the password of an already existing user You can create another admin user though following the steps: https://community.hortonworks.com/questions/178744/add-additional-users-to-cloudbreak-ui-24.html @Jonathan Sneep, you are referring to the Cloudbreak 1.16.x version. Hope this helps!
... View more
08-14-2018
09:08 AM
@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
08-14-2018
08:52 AM
@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
08-13-2018
09:30 PM
The open ports are determined by the network security group settings, which can be set in cluster creation wizard using Cloudbreak UI or cluster skeleton using Cloudbreak CLI.
... View more
08-13-2018
02:22 PM
@Jakub Igla I am not sure that I understood your question correctly, but you should definitely use the custom image facility of Cloudbreak and use your own base image with the pre-hardening and the pre-requisites of Cloudbreak will be burnt by our scripts. The remaining steps to utilize your custom image are documented here. Hope this helps!
... View more
08-13-2018
09:51 AM
1 Kudo
@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
08-13-2018
08:15 AM
@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
07-23-2018
02:21 PM
@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
07-20-2018
12:15 PM
@Vinay MP A couple of questions:
are you using your own custom-burnt image? if yes, then do you send the image id explicitly in the CLI in the cluster template request? if yes, then I am afraid that you should burn a new image as there was an incompatible change between 2.4 and 2.7 versions. We will indicate this in the documentation as well. Hope this helps!
... View more
07-19-2018
09:50 AM
@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
07-16-2018
01:50 PM
1 Kudo
@Tejaswi Chandra How have you deployed it? I have tried it following the official documentation, and it successfully launched a Cloudbreak with 2.7.0. Hope this helps!
... View more
07-09-2018
12:04 PM
@sunile.manjee As the problem was fixed, could you please retry and tell me how it went? Thanks!
... View more
05-16-2018
10:39 AM
2 Kudos
@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
05-10-2018
09:07 PM
@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
05-09-2018
09:33 PM
I am not sure what is a start/stop automation script, but maybe you should check if Cloudbreak is up and running. You can check it with the following commands: cd /var/lib/cloudbreak-deployment
cbd ps If it is not running, you should start it with "cbd start" as part of your script. Hope this helps!
... View more
05-09-2018
09:25 PM
@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
04-23-2018
07:59 PM
@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
04-21-2018
09:40 AM
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
04-15-2018
07:06 PM
@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
04-15-2018
06:54 PM
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
04-06-2018
12:59 PM
@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
04-05-2018
09:13 PM
@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
04-05-2018
10:56 AM
1 Kudo
@Leszek Leszczynski Have you managed to update and resolve your original issue?
... View more
04-05-2018
09:26 AM
@Folkert de Vries Unfortunately it turned out that all the resources are private by default, so they cannot be shared inside an account. The multi-user account mgmt. is on our roadmap. Sorry for the inconviniences caused!
... View more
03-29-2018
11:52 AM
1 Kudo
It should have been created as an admin user already with those capabilities. Such capabilities are mapped to so called UAA groups in Cloudbreak, which are shown in debug mode. Here is the relevant code snippet. Could you retry please, but with an "export DEBUG=1" as a first step and attach the output to this case?
... View more
03-28-2018
02:45 PM
@Brandon Gold The logs are by default under /var/lib/cloudbreak-deployment/logs/cbreak.log. If you are unable to figure out the error, please attach the log to this issue.
... View more
03-28-2018
02:41 PM
1 Kudo
@Folkert de Vries Multi-user management support is not part of Cloudbreak 2.4 version, it is on the roadmap. One option is to integrate your Cloudbreak deployment with your LDAP instance if you have one, it works the same way in 2.4. Another option, if you would like to just add another admin user, you can do the following:
add the following for the new user to a file called Profile.tmp inside cloudbreak deployment directory (/etc/lib/cloudbreak-deployment by default) export UAA_DEFAULT_USER_EMAIL='[default admin email address]'
export UAA_DEFAULT_USER_PW='[default admin password]'
export UAA_DEFAULT_USER_FIRSTNAME='[default admin first name]'
export UAA_DEFAULT_USER_LASTNAME='[default admin last name]'
run the following command from the existing Cloudbreak deployment directory CBD_DEFAULT_PROFILE=tmp cbd util add-default-user This will create a new admin user and leave the original user and profile untouched. Hope this helps!
... View more