About rdoktorics

rdoktorics · ‎02-13-2017

@rahul gulati Unfortunately cloudbreak currently does not support deploying the cluster on existing machines. The only way is to provision clusters if you deploy the whole cluster end to end.

rdoktorics · ‎01-24-2017

https://github.com/sequenceiq/cloudbreak/pull/2183/files added to master

rdoktorics · ‎12-27-2016

@Santhosh B Gowda echo "credential list " | java -jar cloudbreak-shell.jar --sequenceiq.user=${cloudbreak-user} --sequenceiq.password=${cloudbreak-passwrod} --identity.address=https://${cloudbreak-ip}/identity --cloudbreak.address=https://${cloudbreak-ip} --cert.validation=false >> /tmp/output.log Br, R

rdoktorics · ‎12-20-2016

Hi @Kenneth Graves Sure thing that we can add those instance types. I just created a Jira and the next release will include those instance types. Thanks for reporting this 🙂 Br, Richard

rdoktorics · ‎11-14-2016

Hi @hello hadoop You have right the documentation is missing, but here is the related source code https://github.com/sequenceiq/cloudbreak/blob/rc-1.6/shell/src/main/java/com/sequenceiq/cloudbreak/shell/commands/common/ClusterCommands.java#L79 which can help you to deploy kerberized clusters. These are the related config parameters: --enableSecurity --kerberosMasterKey --kerberosAdmin --kerberosPassword Br, Richard

rdoktorics · ‎10-02-2016

@Chris Gambino Currently you can not create autoscaling policies with CLI but here is the link for the rest api on the hosted Cloudbreak: https://cloudbreak.sequenceiq.com/as/api/index.html Br, Richard

rdoktorics · ‎07-29-2016

@Sunile Manjee https://github.com/sequenceiq/cloudbreak/blob/master/CHANGELOG.md

rdoktorics · ‎07-29-2016

hi @Sunile Manjee Openstack is officially in GA with higher than 1.2.0 Cloudbreak. We supporting Kilo and Juno. Br, Richard

rdoktorics · ‎07-28-2016

You should contact with the Hortonworks support and they will help you to create the custom AMI's. Br, Richard

rdoktorics · ‎07-26-2016

Could you please add this line to your Profile: export CBD_FORCE_START=true and also please write this into the compose file where the cloudbreak container is declared under the volume definition: - ./etc/:/etc/cloudbreak after the modification the volume section will seems like this: volumes: - "/Users/rdoktorics/Projects/cloudbreak-deployer/certs:/certs" - /dev/urandom:/dev/random - ./etc/:/etc/cloudbreak after that please do not regenerate the compose file. This is just a patch because cbd 1.3.0 does not implement this feature. The future releases will contains this fix. If you have any problem applying the patch then I am happy to help on webex. Br, Richard

Online	Offline
Last Visited	‎08-10-2023 04:53 AM

Member Since	‎09-25-2015 09:20 PM
Last Visited	‎08-10-2023 04:53 AM
Posts	142
Kudos received	56

Cloudera Community

Re: Cloudbreak Workspace: doing things for other u...

Re: Is it possible to add a new instance group to ...

Re: Cloudbreak downscale fails when no Datanodes i...

Re: Cloudbreak Azure, Can't create stack via CLI f...

Re: Change Default HDP Repositories during UI clus...

Re: Cloudbreak stuck at creating Azure Cluster

Re: AWS r4 Instance type support in Cloudbreak

Re: cloudbreak shell process cmdfile output

Re: AWS r4 Instance type support in Cloudbreak

Re: Does Cloudbreak 1.6 Shell support Kerberos?

Re: Create Autoscaling Policies in CLI or REST

Re: Where can I find list of enhancements (Release...

Re: Is Openstack support with cloudbreak officiall...

Re: Can Cloudbreak deploy HDP on custom AMI's?

Re: Can Cloudbreak deploy HDP on custom AMI's?