Member since
07-25-2019
184
Posts
42
Kudos Received
39
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2253 | 03-25-2019 02:25 PM | |
1132 | 01-22-2019 02:37 PM | |
1268 | 01-16-2019 04:21 PM | |
2680 | 10-17-2018 12:22 PM | |
1341 | 08-28-2018 08:31 AM |
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
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-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-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
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: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