Member since
10-14-2015
65
Posts
57
Kudos Received
20
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
7660 | 04-20-2018 10:07 AM | |
2471 | 09-20-2017 12:31 PM | |
2280 | 05-04-2017 01:11 PM | |
1325 | 02-14-2017 07:36 AM | |
4677 | 02-03-2017 05:52 PM |
10-21-2016
04:24 PM
Thanks. The master.txt looks error free. I am trying to reproduce the issue with the attached blueprint. Attila
... View more
10-20-2016
09:07 PM
1 Kudo
Hi @Vadim Vaks, Is this error reproducible? Or was a single failure? If it is reproducible then could you send us the blueprint, please? The salt-api should use the port 3080, so that seems correct. Could you check that how many instances are running of the salt-api with: ps aux | grep salt-api You can try to kill it/them with kill -9. If you kill it with -9 then it won't be restarted. You can also try to stop it with service salt-api stop. After you have successfully stop the salt-api please move the /var/log/salt/master to e.g. /var/log/salt/master.bak and start the salt-api with service salt-api start and send us the content of the new /var/log/salt/master which will contain only the boot log of salt-api. Attila
... View more
10-20-2016
05:56 PM
1 Kudo
Hi @cduby, As requested: What do you do during manual registration? Do you install additional packages or just configure the data and namenode differently? In the latter case you can put those properties into the blueprint and you can do the installation and configuration in one step. If you are doing e.g. package installation and configuring things outside Hadoop config files the I see two options: Basic Option (with manual steps):
create a blueprint what is suitable for you needs just leave out the data a name node components. The blueprints are extremely flexible e.g for your reference I am attaching a very simple valid blueprint which contains only Zookeeper install the cluster and after installation just add services manually and configure Isilon Advanced Option:
You can write an Ambari Management Pack which contains the definition of EMC Isilon service:https://cwiki.apache.org/confluence/display/AMBARI/Management+Packs Install it with recipes: http://sequenceiq.com/cloudbreak-docs/latest/recipes/ You can use that new service from blueprint Thanks, Attila
... View more
10-19-2016
07:08 AM
What do you do during manual registration? Do you install additional packages or just configure the data and namenode differently? In the latter case you can put those properties into the blueprint and you can do the installation and configuration in one step. If you are doing e.g. package installation and configuring things outside Hadoop config files the I see two options: Basic Option (with manual steps):
create a blueprint what is suitable for you needs just leave out the data a name node components. The blueprints are extremely flexible e.g for your reference I am attaching a very simple valid blueprint which contains only Zookeeper install the cluster and after installation just add services manually and configure Isilon Advanced Option: You can write an Ambari Management Pack which contains the definition of EMC Isilon service: https://cwiki.apache.org/confluence/display/AMBARI/Management+Packs Install it with recipes: http://sequenceiq.com/cloudbreak-docs/latest/recipes/ You can use that new service from blueprint Attila
... View more
10-13-2016
07:11 PM
Hi @Gerald Lim, It has been fixed in rc-1.6, if you update now, then you will get the 1.6.1-rc.19 version where this issue and also the VPC issue) are fixed. Attila
... View more
10-12-2016
07:32 PM
Thanks. It seems that the issue was partially fixed. If you do it from shell it get's stored as string {"encrypted":"true"}, if you do it form UI it stored as boolean {"encrypted":true}. I will fix it in 1.6 line and let you know when it is available, as a temporary workaround could you create the new templates from UI, please? Thanks. Attila
... View more
10-12-2016
05:58 PM
Hi @Gerald Lim, The 1.6 is going to have a long term support. The mentioned default VPC issue was backported to 1.6 branch and will be on 1.6.1. You can update: cbd kill
cbd update rc-1.6
cbd regenerate
cbd start
This will update you to the 1.6.1 release candidate which is 1.6.1-rc.16 right now. Could you send me the shell command what you are using to create the template, please? Attila
... View more
10-12-2016
03:56 PM
Hi, Please update to 1.6, the 1.4 is not supported version. You can update it with: cbd kill
cbd update
cbd regenerate
cbd start In 1.6 release the error you are referring does not occur and the EBS encrytion is properly applied on attached disks. Attila
... View more
10-12-2016
03:03 PM
Hi, Cloudbreak uses Heat templates to set up networking, launch VMs and attach disks to them. The volume management is abstracted under Cinder on OpenStack, therefore it is not relevant for Cloudbreak that what storage backend is used under the hood. Although we have never tested EMC Isilon, but if it can be managed through Cinder then Cloudbreak can handle it. For your reference I copy here the Heat template fragment used by Cloudbreak, that is responsible to create the necessary cinder volume resources: type: OS::Cinder::Volume
properties:
name: hdfs-volume
size: ${volume.size} The complete template is here: https://github.com/sequenceiq/cloudbreak/blob/master/cloud-openstack/src/main/resources/templates/openstack-heat.ftl Attila
... View more
10-07-2016
04:48 PM
1 Kudo
Hi @Vitaliy Kotlyarenko, The doc has been fixed and public access to images have been granted: https://public-repo-1.hortonworks.com/HDP/cloudbreak/cloudbreak-deployer-160-2016-10-05.img https://public-repo-1.hortonworks.com/HDP/cloudbreak/cloudbreak-2016-08-26-07-56.img Please try them now. Thanks, Attila
... View more