hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sandy Ryza <sandy.r...@cloudera.com>
Subject Re: Thinking ahead
Date Mon, 14 Apr 2014 03:47:13 GMT
Reference:
http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201401.mbox/%3CCAJS6+b4TKuPVqfaoRf_314XvEiVrYQy-VtRYD8+36Tu_Bc51fw@mail.gmail.com%3E

This is of course open source, and I have neither the ability nor the
desire to compel or pressure anybody to work on anything, but I wanted to
point out that the proposal to merge AHS into trunk stated an intent to tie
ends up on security.


On Sun, Apr 13, 2014 at 7:50 PM, Sandy Ryza <sandy.ryza@cloudera.com> wrote:

> Unfortunately I don't have the bandwidth to take on ATS security at this
> time.  My (I now understand mistaken) impression that it was being worked
> on, as we had discussed it under the initial criteria for including the AHS
> in a release.  I brought it up as a feature I felt worth waiting for if it
> meant extending the target release date a couple weeks - I of course had no
> intention to volunteer anybody for it.
>
>
> On Sun, Apr 13, 2014 at 5:50 PM, Arun C Murthy <acm@hortonworks.com>wrote:
>
>> Sandy,
>>
>> On Apr 12, 2014, at 10:09 AM, Sandy Ryza <sandy.ryza@cloudera.com> wrote:
>>
>> I'm having trouble editing the wiki, but I think Timeline Server stability
>> (e.g. security and locking down APIs) should go on that list.
>>
>>
>> I'm very glad to see you are very passionate about security for ATS since
>> you've asked about it a few times around here.
>>
>> I just opened https://issues.apache.org/jira/browse/YARN-1935.
>>
>> Would you be willing to volunteer to take this on? Much appreciated.
>>
>> thanks,
>> Arun
>>
>>
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity
>> to which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message