Member since
09-30-2015
15
Posts
22
Kudos Received
3
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1040 | 10-13-2017 01:49 PM | |
427 | 03-01-2017 05:30 PM | |
882 | 02-28-2017 03:45 PM |
03-06-2018
07:22 PM
@Benjamin Leroux This can happen if your company has restriceted security policy, which forbid to use self-signed certificates. In this case you have to change the self-signed certificates to a proper one on the ambari server host.
... View more
03-06-2018
02:01 PM
1 Kudo
@shweta singh You are right, that in case of HA clusters the HA nodes should be launched in different availabilty zones. Unfortunately Cloudbreak doesn't support clusters in multiple availability zones. if you have a contact to a Hortonworks Solution Engineer, please contact him, and we will be able to look into your issue more deeply.
... View more
03-06-2018
01:44 PM
1 Kudo
@shweta singh The pre-ambari-start recipes are running in the same salt state as the ambari-install, so they are running parallel. Salt is trying to run highstate more times, so after the pre-ambari-start recipes are finished with the proxy and repo settings the ambari-install phase should be successfull. The ambari repository settings can be set on the UI or from the CLI as well. Anyway in the next TP version of Cloudbreak (2.5) proxy setup for clusters will be in techpreview phase. You can try clusters behind proxy in that version.
... View more
03-05-2018
04:23 PM
If you remove the instance from the cloud provider and after this you sync the cluster in cloudbreak, the node will be removed automatically.
... View more
03-05-2018
02:00 PM
1 Kudo
@kishore cu to install solr using Cloudbreak and Ambari, the following steps are necessary:
Cloudbreak 2.4 is necessary, because pre-ambari-start recipe is need for solr mpack installation
You have to write a pre-ambari-start recipe based on the instructions here: https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.0/bk_solr-search-installation/content/ch_hdp-search-install-ambari.html After this you have to create your ambari blueprint which contains the components needed for SOLR: https://github.com/lucidworks/solr-stack/blob/master/src/main/mpack/common-services/SOLR/5.5.5/metainfo.xml It is not recommended to use prewarmed image with cloudbreak in this case, so you can use advanced cluster creation wizard and choose a base image instead of a prewarmed one. On the cluster creation wizard you have to use the created pre-ambari-start recipe and the created blueprint
... View more
03-05-2018
01:34 PM
@Purnima Kuchikulla As @Attila Kanto mentioned, Nifi is not supported in HDC, in HDC there are predefined HDP blueprints only. The cloudbreak team is working on HDF support in Cloudbreak: https://hortonworks.jira.com/browse/RMP-10082. It is planned to release in Cloudbreak 2.5 or later.
... View more
03-05-2018
01:25 PM
2 Kudos
Hi @MARTIN GATTO, cloudbreak 2.4 is the recommended version and hdcloud planned to be replaced with this version in the future. So the recommendation is to use Cloudbreak 2.4, because it is the long term supported one.
... View more
10-13-2017
01:49 PM
5 Kudos
@Anagha Khanolkar You can create your custom virtual network on the Azure Portal, where you can define your custom dns server. After this you can create a new network resource, where you can setup your exisiting virtual network and subnet settings. (http://hortonworks.github.io/cloudbreak-docs/latest/azure/#infrastructure-templates "Custom AZURE Network" paragraph) During Azure cluster creation you have to use this network with the custom DNS server
... View more
07-19-2017
12:43 PM
@Anandha L Ranganathan You can find the CF template on the Cloudformation view if you select a stack and choose the template tab.
Just to be sure: Did you try to launch instances in the same vpc / subnet as the instances launched by the cloudbreak? From these instances were you able to telnet to RDS instances? Were you able to ping external world and other aws instances in the same vpc / subnet?
... View more
05-24-2017
08:03 AM
2 Kudos
@kkanchu Why do you use the AMI ID - cloudbreak-deployer-130-2016-06-15(ami-019b5c6c) image? There are images with the new version of cloudbreak-deployer: http://sequenceiq.com/cloudbreak-docs/latest/aws/#cloudbreak-deployer-aws-image-details
... View more
03-01-2017
05:30 PM
2 Kudos
Hi @Davide Ferrari, you can define the hdp repository urls during cluster creation on the 'Configure HDP repository' tab if you enable the 'Advanced Options' on the UI.
... View more
02-28-2017
03:45 PM
6 Kudos
Hi @Atul Aggarwal, You have 2 options: using key-based or role-based credentials. Key-based credential: you can set your AWS keys of an IAM user with an "AssumeRole" policy in the Profile file. In this case you don't need the instance profile export AWS_ACCESS_KEY_ID=AKIA**************W7SA
export AWS_SECRET_ACCESS_KEY=RWCT4Cs8******************/*skiOkWD This iam user has the generate-role policy next to the assume-role policy. in this case you can use the following command to generate an iam role for cloudbreak with the following cbd commands: cbd aws generate-role - Generates an AWS IAM role for Cloudbreak provisioning on AWS
cbd aws show-role - Show assumers and policies for an AWS role
cbd aws delete-role - Deletes an AWS IAM role, removes all inline policies After the role generation you can use the generated role for the credential creation from cb shell: credential create --AWS --name cloudbreak --roleArn "arn:aws:iam::xxxx:role/cbreak-deployer" --sshKeyString "xxxxx" --publicInAccount true If you use the roleArn for credential creation, you don't need to use the accesskey and secretkey in the command. Role-based credential: You can create an IAM user with "AssumeRole" policy. The "generate-role" policy will be necessary here as well. To configure role-based credentials, start your instance with an "AssumeRole" policy. For more information, see Using Instance Profiles and Using an IAM Role to Grant Permissions to Applications Running on Amazon EC2 Instances. In this case you don't need to set the aws access and secret key in the Profile file. After this the 3-4 steps from the Key based credential have to be executed. You can find the details in the documentation here: http://sequenceiq.com/cloudbreak-docs/latest/aws/#configure-role-based-credentials
... View more