You can set configurations at the blueprint level (to apply to all
host_groups) and you can also set configurations in the host_groups element
to set configurations for that host_group.
Will that help? Or will it just mean you will have to have a host_group
that you have to apply per host?
Can you provide some details on what type of check you want to do?
You can use custom actions support for that. You will need to define a
custom action first. There is API only support for issuing custom action on
all hosts and then the action can perform the test and then report back
results.
https://cwiki.apache.org/confluence/display/AMBARI/Stacks+and+Services
On Wed, Jun 4, 2014 at 10:35 PM, ÐΞ€ρ@Ҝ (๏̯͡๏) deepuj...@gmail.com wrote:
Custom stack ? Is this new feature with 1.6.0 ?
Is this exposed from Web UI ? Or i this only REST interface ?
On Wed, Jun 4, 2014 at 10:00 PM,
hello
So I’m looking at the code in 1.6.0 and I see that dependencies seem to have
moved out into a ‘role_command_order.json’ file …. on a per-stack basis … but
then I spotted one of these files up in ambari-server/main/resources … is that
one used for anything? Can it be ignored? Is there
Hi Qing Chi,
You can have 2 host_groups with exactly same components say salve_type_1,
slave_type_2 with different configs for each host group.
-Sid
On Thu, Jun 5, 2014 at 6:52 PM, Qing Chi 79624 c...@vmware.com wrote:
Hi Jeff,
Thanks a lot for your help.
I think the host_group is the
It would be best to not have 100 different configs for 100 different hosts.
Is there anyway you can use the same mount points for these hosts?
Typically, you may have several classes of machines (say, different number
of disks). But having
On Thu, Jun 5, 2014 at 8:25 PM, Siddharth Wagle
unique mount points for each and every host doesn't sound like a good way
to set it up...
On Thu, Jun 5, 2014 at 8:43 PM, Yusaku Sako yus...@hortonworks.com wrote:
It would be best to not have 100 different configs for 100 different hosts.
Is there anyway you can use the same mount points for
Hi Yusaku,
There is a different number of VMDK in the different virtual machine. So mount
points are different in these virtual machines.
Thanks,
-qing
From: Yusaku Sako yus...@hortonworks.commailto:yus...@hortonworks.com
Reply-To: user@ambari.apache.orgmailto:user@ambari.apache.org
Date:
I can understand that there could be a different number of disks on
different VMs, but isn't there some logical grouping?
Something like...
Group 1. VM001-VM100 with 2 disks: /mnt/disks/0, /mnt/disks/1
Group 2. VM101-VM200 with 4 disks: /mnt/disks/0, /mnt/disks/1,
/mnt/disks/2, /mnt/disks/3
and so
