Re: Ambari Tracking configuration changes

2014-11-07 Thread Siddharth Wagle
Hi Iva, Correctly specifying type and tag will get you the key values that you are looking for. You might find it useful to download a JsonViewer app (if using Chrome/Firefox) and effectively just click on the config hrefs to navigate to the key/value properties. -Sid On Fri, Nov 7, 2014 at 12:

Re: Ambari Tracking configuration changes

2014-11-07 Thread P lva
Myroslav, Thanks for your prompt response. I tried this GET /api/v1/clusters/c1/configurations and its lists all the available configurations { "href" : "", "tag" : "", "type" : "core-site", "Config" : { "cluster_name" : "c1" } However when i add the type

Re: Ambari Tracking configuration changes

2014-11-07 Thread Myroslav Papyrkovskyy
Hello, I'm pretty sure you can. Sample request: GET /api/v1/clusters/c1/configurations?type=yarn-site&tag=version13456 You can find more details here: https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/configuration.md Regards, Myroslav On Fri, Nov 7, 2014 at 6:53 PM, P lva wr

Ambari Tracking configuration changes

2014-11-07 Thread P lva
Is there any way to track configuration changes in ambari 1.6. The change log has version information. Can we make a call to the api with this version number and get the configs ? Thanks Ral

Re: Stop all components API call no longer seems to work

2014-11-07 Thread Greg Hill
The host is in maintenance mode, but the components are not stopped. I'm setting maintenance mode prior to stopping services because otherwise you get nagios notifications when the components are stopped (or this used to be the case anyway). Adding the operation_level made everything work correct

Re: Stop all components API call no longer seems to work

2014-11-07 Thread Yusaku Sako
Hi Greg, The API call you mentioned to stop all components on a host still works in 1.7.0 (I just verified on my recent 1.7.0 cluster). Operation_level is not mandatory and the WARN can be ignored. Operation_level drives the behavior of operations when services/hosts/host_components are in mainten

Re: Stop all components API call no longer seems to work

2014-11-07 Thread Dmitry Sen
Hi, Greg! I think you should specify operation level in the body, like 1. {"RequestInfo":{"context":"Stop Services","operation_level":{"level":"CLUSTER","cluster_name":"testcluster"}},"Body":{"ServiceInfo":{"state":"INSTALLED"}}}: BR, Dmytro On Fri, Nov 7, 2014 at 3:55 PM, Greg Hill w

Stop all components API call no longer seems to work

2014-11-07 Thread Greg Hill
This used to work in earlier 1.7.0 builds, but doesn't seem to any longer: PUT /api/v1/clusters/testcluster/hosts/c6404.ambari.apache.org/host_components {"RequestInfo": {"context": "Stop All Components"}, "Body": {"HostRoles": {"state": "INSTALLED"}}} Seeing this in the server logs: 13:05:42,08