Apologies for not reviewing my podlings. I was relocating my family across
the globe during this reporting cycle.
I have now reviews the reports from each podling as follows (not added to
report in board agenda or wiki since there is a great big "do not edit" on
the wiki doc):
Ross Gardler
-- Forwarded message --
From: Yusaku Sako
Date: Tue, Jul 16, 2013 at 6:19 PM
Subject: [VOTE] Apache Ambari 1.2.4-incubating RC0
To: ambari-...@incubator.apache.org
Hi all,
ambari-1.2.4-incubating-rc0 release candidate is now available.
Here's a summary of what's new in Ambari 1
On Tue, Jul 16, 2013 at 1:13 PM, Doug Cutting wrote:
> On Tue, Jul 16, 2013 at 10:13 AM, sebb wrote:
>> So why not pre-allow all automated senders when creating the podling list?
>
> Why not pre-allow *@apache.org?
That sounds great.
The proposal to pre-allow no-re...@apache.org at list creatio
On Tue, Jul 16, 2013 at 06:13:28PM +0100, sebb wrote:
> On 13 July 2013 19:28, Daniel Shahaf wrote:
> > On Sat, Jul 13, 2013 at 10:57:33AM -0700, Marvin Humphrey wrote:
> >> A second possibility might be to consolidate `-allow` lists. (I'm not sure
> >> whether this is technically feasible -- it
On Tue, Jul 16, 2013 at 06:13:28PM +0100, sebb wrote:
> On 13 July 2013 19:28, Daniel Shahaf wrote:
> > On Sat, Jul 13, 2013 at 10:57:33AM -0700, Marvin Humphrey wrote:
> >> A second possibility might be to consolidate `-allow` lists. (I'm not sure
> >> whether this is technically feasible -- it
On Tue, Jul 16, 2013 at 10:13 AM, sebb wrote:
> So why not pre-allow all automated senders when creating the podling list?
Why not pre-allow *@apache.org?
Doug
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
On 13 July 2013 19:28, Daniel Shahaf wrote:
> On Sat, Jul 13, 2013 at 10:57:33AM -0700, Marvin Humphrey wrote:
>> A second possibility might be to consolidate `-allow` lists. (I'm not sure
>> whether this is technically feasible -- it came up yesterday on the infra
>> list, but the discussion was
On Sat, Jul 13, 2013 at 10:57:33AM -0700, Marvin Humphrey wrote:
> A second possibility might be to consolidate `-allow` lists. (I'm not sure
> whether this is technically feasible -- it came up yesterday on the infra
> list, but the discussion was not conclusive. Perhaps one of the
> Infrastruct
Hi Alex,
Currently there is no way to get a single attribute of a node, as it
is not supported neither in the Chef Server Search API [1] nor in the
Node API [2]. You will need to get the list of the nodes, and find the
desired attribute in the returned attribute map.
You can also search nodes bas
