About hensilva

hensilva · ‎09-29-2017

It seems that editing the Profile, replacing URL parameters and regenerating files did the trick. But I'd like to be sure there are no unintendend consequences later on, since I'll be disabling this Internet endpoint.

hensilva · ‎09-29-2017

What do I need to change to be able to access Cloudbreak Portal using its internal IP address? I used the Marketplace deployment from Azure and the output is a public address https://xxxx.eastus.cloudapp.azure.com. I want to remove this public IP address and only access the Portal from my VNET. If I navigate to https://10.191.232.132 (internal IP address): 404 not found If I navigate to https://10.191.232.132/sl: CloudBreak Login Portal. If I insert username + password, the Dashboard is displayed with a link to the Cloudbreak UI (picture). Clicking this, I'm redirected to the external address again https://xxxx.eastus.cloudapp.azure.com/sl. Playing around config files, I noticed this external URL is configured. What do I need to change in this config files (and additional steps) to avoid this redirection and allow users?? I just want internal VNET access. Thanks

hensilva · ‎09-05-2017

I'm trying to deploy a 6-node cluster using the Azure Availability Sets option. AvSet itself is successfully created in Azure. Problem is that the generated template does not have the dependsOn parameter added to the VMs meaning it only waits for the NIC object. So if randomly a VM deployment starts before the AvSet is created, it fails with AvSet not found error.

hensilva · ‎09-05-2017

Thanks! I'm a beginner using this tool, so just a couple of questions to clarify what I need to do: What about the Dcb.hdp.entries.2.6.repo.redhat? In my case it would be CentOS 7 + HDP 2.4. Does it mean my config would be something like this? CB_JAVA_OPT="-Dcb.hdp.entries.2.4.version=2.4.2.0 -Dcb.hdp.entries.2.4.repo.redhat6=http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.4.2.0 -Dcb.hdp.entries.2.4.repo.redhat7=http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.4.2.0" Utils version is also different in my scenario (1.1.0.20 instead of 1.1.0.21). Do this config change needs to reflect that? How the deployment will use the information? Based on the Stack version from the Blueprint and everything else is automatic?

hensilva · ‎09-05-2017

Hi all! For a very specific scenario, all clusters created by Cloudbreak should have HDP-2.4 stack (specifically 2.4.2). To accomplish that using the Cloudbreak UI, it's necessary to open advanced options during cluster creation and copying 2.42 repositories manually. I understand it's possible to provide this info via command line, but I'd like to know if it's possible to change the defaults (picture attached) or at least pre-fill the 2.4.2 information. Is it?

Online	Offline
Last Visited	‎09-29-2017 10:40 PM

Date Registered	‎09-01-2017 09:23 PM
Last Visited	‎09-29-2017 10:40 PM
Total Messages Posted	5

Re: Internal IP for Cloudbreak UI (Azure)

Internal IP for Cloudbreak UI (Azure)

Bug with Cloudbreak + Azure availability sets?

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

Change Default HDP Repositories during UI cluster ...