You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Kevin Minder <ke...@hortonworks.com> on 2013/02/11 15:55:27 UTC
[PROPOSAL] Knox Hadoop Gateway Project
Knox Gateway Proposal
== Abstract ==
Knox Gateway is a system that provides a single point of secure access
for Apache Hadoop clusters.
== Proposal ==
The Knox Gateway (“Gateway” or “Knox”) is a system that provides a
single point of authentication and access for Apache Hadoop services in
a cluster. The goal is to simplify Hadoop security for both users (i.e.
who access the cluster data and execute jobs) and operators (i.e. who
control access and manage the cluster). The Gateway runs as a server (or
cluster of servers) that serve one or more Hadoop clusters.
Provide perimeter security to make Hadoop security setup easier
Support authentication and token verification security scenarios
Deliver users a single cluster end-point that aggregates capabilities
for data and jobs
Enable integration with enterprise and cloud identity management
environments
== Background ==
An Apache Hadoop cluster is presented to consumers as a loose collection
of independent services. This makes it difficult for users to interact
with Hadoop since each service maintains it’s own method of access and
security. As well, for operators, configuration and administration of a
secure Hadoop cluster is a complex and many Hadoop clusters are insecure
as a result.
== Rationale ==
Organizations that are struggling with Hadoop cluster security result in
a) running Hadoop without security or b) slowing adoption of Hadoop. The
Gateway aims to provide perimeter security that integrates more easily
into existing organizations’ security infrastructure. Doing so will
simplify security for these organizations and benefit all Hadoop
stakeholders (i.e. users and operators). Additionally, making a
dedicated perimeter security project part of the Apache Hadoop ecosystem
will prevent fragmentation in this area and further increase the value
of Hadoop as a data platform.
== Current Status ==
Prototype available, developed by the list of initial committers.
=== Meritocracy ===
We desire to build a diverse developer community around Gateway
following the Apache Way. We want to make the project open source and
will encourage contributors from multiple organizations following the
Apache meritocracy model.
=== Community ===
We hope to extend the user and developer base in the future and build a
solid open source community around Gateway. Apache Hadoop has a large
ecosystem of open source projects, each with a strong community of
contributors. All project communities in this ecosystem have an
opportunity to participate in the advancement of the Gateway project
because ultimately, Gateway will enable the security capabilities of
their project to be more enterprise friendly.
=== Core Developers ===
Gateway is currently being developed by several engineers from
Hortonworks - Kevin Minder, Larry McCay, John Speidel, Tom Beerbower and
Sumit Mohanty. All the engineers have deep expertise in middleware,
security & identity systems and are quite familiar with the Hadoop
ecosystem.
=== Alignment ===
The ASF is a natural host for Gateway given that it is already the home
of Hadoop, Hive, Pig, HBase, Oozie and other emerging big data software
projects. Gateway is designed to solve the security challenges familiar
to the Hadoop ecosystem family of projects.
== Known Risks ==
=== Orphaned products & Reliance on Salaried Developers ===
The core developers plan to work full time on the project. We believe
that this project will be of general interest to many Hadoop users and
will attract a diverse set of contributors. We intend to demonstrate
this by having contributors from several organizations recognized as
committers by the time Knox graduates from incubation.
=== Inexperience with Open Source ===
All of the core developers are active users and followers of open
source. As well, Hortonworks has a strong heritage of success with
contributions to Apache Hadoop Projects.
=== Homogeneous Developers ===
The current core developers are from Hortonworks, however, we hope to
establish a developer community that includes contributors from several
corporations.
=== Reliance on Salaried Developers ===
Currently, the developers are paid to do work on Gateway. However, once
the project has a community built around it, we expect to get committers
and developers from outside the current core developers.
=== Relationships with Other Apache Products ===
Gateway is going to be used by the users and operators of Hadoop, and
the Hadoop ecosystem in general.
=== A Excessive Fascination with the Apache Brand ===
Our interest in developing Gateway in Apache project is to follow an
established development model, as well since many of the Hadoop
ecosystem projects also are part of Apache, Gateway will complement
those projects by following the same development and contribution model.
== Documentation ==
There is documentation in Hortonworks’ internal repositories. These can
be shared upon request and will be transferred into the Apache CM system
if this proposal is accepted.
== Initial Source ==
The source is currently in Hortonworks’ internal repositories. The
process of making this GitHub repository public has been started and the
URL will be provided once available.
== Source and Intellectual Property Submission Plan ==
The complete Gateway code is under Apache Software License 2.
== External Dependencies ==
The Gateway dependencies are listed below, separated by Category A and
Category B as defined in the Apache Third-Party Licensing Policy. Note:
These are the direct dependencies. Indirect dependencies are not included.
=== Category A Dependencies ===
Apache Commons - ASLv2.0
commons-io:commons-io#2.4
commons-cli:commons-cli#1.2
commons-codec:commons-codec#1.7
org.apache.commons:commons-digester3#3.2
org.apache.commons:commons-vfs2#2.0
Apache Hadoop - ASLv2.0
org.apache.hadoop:hadoop-auth#0.23.3
org.apache.hadoop:hadoop-core#1.0.3
Apache Geronimo - ASLv2.0
org.apache.geronimo.components:geronimo-jaspi#2.0.0
org.apache.geronimo.specs:geronimo-osgi-locator#1.1
Apache Shiro - ASLv2.0
org.apache.shiro:shiro-web#1.2.1
ApacheDS - ASLv2.0
org.apache.directory.server:apacheds-all#1.5.5
Log4J - ASLv2.0
log4j:log4j#1.2.17
SL4J - MIT
org.slf4j:slf4j-api#1.6.6
org.slf4j:slf4j-log4j12#1.6.6
Guava - ASLv2.0
com.google.guava:guava#14.0-rc1
HttpClient - ASLv2.0
org.apache.httpcomponents:httpclient#4.2.1
Jetty - ASLv2.0
org.eclipse.jetty:jetty-server#8.1.7.v20120910
org.eclipse.jetty:jetty-servlet#8.1.7.v20120910
org.eclipse.jetty:jetty-webapp#8.1.7.v20120910
org.eclipse.jetty:jetty-jaspi#8.1.7.v20120910
org.eclipse.jetty.aggregate:jetty-all#8.1.7.v20120910
org.eclipse.jetty:test-jetty-servlet#8.1.7.v20120910
Spring Security - ASLv2.0
org.springframework:spring-core#3.1.3.RELEASE
org.springframework:spring-context#3.1.3.RELEASE
org.springframework:spring-web#3.1.3.RELEASE
org.springframework.security:spring-security-core#3.1.3.RELEASE
org.springframework.security:spring-security-web#3.1.3.RELEASE
org.springframework.security:spring-security-config#3.1.3.RELEASE
org.springframework.security:spring-security-ldap#3.1.2.RELEASE
org.springframework.ldap:spring-ldap-core#1.3.1.RELEASE
org.springframework.ldap:spring-ldap-core-tiger#1.3.1.RELEASE
org.springframework.ldap:spring-ldap-odm#1.3.1.RELEASE
org.springframework.ldap:spring-ldap-ldif-core#1.3.1.RELEASE
org.springframework.ldap:spring-ldap-ldif-batch#1.3.1.RELEASE
JBoss ShrinkWrap - ASLv2.0
org.jboss.shrinkwrap:shrinkwrap-api#1.0.1
org.jboss.shrinkwrap:shrinkwrap-impl-base#1.0.1
org.jboss.shrinkwrap.descriptors:shrinkwrap-descriptors-api-javaee#2.0.0-alpha-4
org.jboss.shrinkwrap.descriptors:shrinkwrap-descriptors-impl-javaee#2.0.0-alpha-4
=== Category A Dependencies (Test) ===
EasyMock - ASLv2.0
org.easymock:easymock#3.0
XML Matchers - ASLv2.0
org.xmlmatchers:xml-matchers#0.10
Hamcrest - BSDv3
org.hamcrest:hamcrest-api#1.0
org.hamcrest:hamcrest-core#1.2.1
org.hamcrest:hamcrest-library#1.2.1
JsonPath - ASLv2.0
com.jayway.jsonpath:json-path#0.8.1
com.jayway.jsonpath:json-path-assert#0.8.1
XMLTool - ASLv2.0
com.mycila.xmltool:xmltool#3.3
REST-assured - ASLv2.0
com.jayway.restassured:rest-assured#1.6.2
=== Category B Dependencies ===
Jersey - CDDLv1.1 or GPL2wCPE
com.sun.jersey:jersey-server#1.14
com.sun.jersey:jersey-servlet#1.14
Jerico - EPLv1.0
net.htmlparser.jericho:jericho-html#3.2
Servlet - CDDLv1.0 or GPLv2
javax.servlet:javax.servlet-api#3.0.1
JUnit - CPLv1.0
junit:junit#4.11
== Cryptography ==
The Gateway uses cryptographic software indirectly as a result of having
two dependencies: ApacheDS and Apache Shiro. Gateway does not include
any special or custom cryptographic technologies.
ApacheDS is an ASF project and has been classified Export Commodity
Control Number (ECCN) 5D002.C.1 due to it’s dependency on Bouncy Castle.
More information on the ApacheDS classification can be found at
http://svn.apache.org/repos/asf/directory/apacheds/trunk/installers/README
Apache Shiro is an ASF project and has been classified Export Commodity
Control Number (ECCN) 5D002.C.1. More information on the Apache Shiro
classification can be found at
http://svn.apache.org/repos/asf/shiro/trunk/README
== Required Resources ==
=== Mailing lists ===
knox-dev AT incubator DOT apache DOT org
knox-commits AT incubator DOT apache DOT org
knox-user AT hms incubator apache DOT org
knox-private AT incubator DOT apache DOT org
=== Subversion Directory ===
https://svn.apache.org/repos/asf/incubator/knox
=== Issue Tracking ===
JIRA Knox (KNOX)
== Initial Committers ==
Kevin Minder (kevin DOT minder AT hortonworks DOT com)
Larry McCay (lmccay AT hortonworks DOT com)
John Speidel (jspeidel AT hortonworks DOT com)
Tom Beerbower (tbeerbower AT hortonworks DOT com)
Sumit Mohanty (smohanty AT hortonworks DOT com)
== Affiliations ==
Kevin Minder (Hortonworks)
Larry McCay (Hortonworks)
John Speidel (Hortonworks)
Tom Beerbower (Hortonworks)
Sumit Mohanty (Hortonworks)
== Sponsors ==
=== Champion ===
Devaraj Das (ddas AT apache DOT org)
=== Nominated Mentors ===
Owen O’Malley (omalley AT apache DOT org)
Mahadev Konar (mahadev AT apache DOT org)
Alan Gates (gates AT apache DOT org)
Devaraj Das (ddas AT apache DOT org)
=== Sponsoring Entity ===
Incubator PMC
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Tom White <to...@gmail.com>.
This looks like an interesting and useful project. I'd like to volunteer as
a mentor on it.
Thanks,
Tom
On 11 Feb 2013 14:56, "Kevin Minder" <ke...@hortonworks.com> wrote:
> Knox Gateway Proposal
>
> == Abstract ==
>
> Knox Gateway is a system that provides a single point of secure access for
> Apache Hadoop clusters.
>
> == Proposal ==
>
> The Knox Gateway (“Gateway” or “Knox”) is a system that provides a single
> point of authentication and access for Apache Hadoop services in a cluster.
> The goal is to simplify Hadoop security for both users (i.e. who access the
> cluster data and execute jobs) and operators (i.e. who control access and
> manage the cluster). The Gateway runs as a server (or cluster of servers)
> that serve one or more Hadoop clusters.
>
> Provide perimeter security to make Hadoop security setup easier
> Support authentication and token verification security scenarios
> Deliver users a single cluster end-point that aggregates capabilities for
> data and jobs
> Enable integration with enterprise and cloud identity management
> environments
>
> == Background ==
>
> An Apache Hadoop cluster is presented to consumers as a loose collection
> of independent services. This makes it difficult for users to interact with
> Hadoop since each service maintains it’s own method of access and security.
> As well, for operators, configuration and administration of a secure Hadoop
> cluster is a complex and many Hadoop clusters are insecure as a result.
>
> == Rationale ==
>
> Organizations that are struggling with Hadoop cluster security result in
> a) running Hadoop without security or b) slowing adoption of Hadoop. The
> Gateway aims to provide perimeter security that integrates more easily into
> existing organizations’ security infrastructure. Doing so will simplify
> security for these organizations and benefit all Hadoop stakeholders (i.e.
> users and operators). Additionally, making a dedicated perimeter security
> project part of the Apache Hadoop ecosystem will prevent fragmentation in
> this area and further increase the value of Hadoop as a data platform.
>
> == Current Status ==
>
> Prototype available, developed by the list of initial committers.
>
> === Meritocracy ===
>
> We desire to build a diverse developer community around Gateway following
> the Apache Way. We want to make the project open source and will encourage
> contributors from multiple organizations following the Apache meritocracy
> model.
>
> === Community ===
>
> We hope to extend the user and developer base in the future and build a
> solid open source community around Gateway. Apache Hadoop has a large
> ecosystem of open source projects, each with a strong community of
> contributors. All project communities in this ecosystem have an opportunity
> to participate in the advancement of the Gateway project because
> ultimately, Gateway will enable the security capabilities of their project
> to be more enterprise friendly.
>
> === Core Developers ===
>
> Gateway is currently being developed by several engineers from Hortonworks
> - Kevin Minder, Larry McCay, John Speidel, Tom Beerbower and Sumit Mohanty.
> All the engineers have deep expertise in middleware, security & identity
> systems and are quite familiar with the Hadoop ecosystem.
>
> === Alignment ===
>
> The ASF is a natural host for Gateway given that it is already the home of
> Hadoop, Hive, Pig, HBase, Oozie and other emerging big data software
> projects. Gateway is designed to solve the security challenges familiar to
> the Hadoop ecosystem family of projects.
>
> == Known Risks ==
>
> === Orphaned products & Reliance on Salaried Developers ===
>
> The core developers plan to work full time on the project. We believe that
> this project will be of general interest to many Hadoop users and will
> attract a diverse set of contributors. We intend to demonstrate this by
> having contributors from several organizations recognized as committers by
> the time Knox graduates from incubation.
>
> === Inexperience with Open Source ===
>
> All of the core developers are active users and followers of open source.
> As well, Hortonworks has a strong heritage of success with contributions to
> Apache Hadoop Projects.
>
> === Homogeneous Developers ===
>
> The current core developers are from Hortonworks, however, we hope to
> establish a developer community that includes contributors from several
> corporations.
>
> === Reliance on Salaried Developers ===
>
> Currently, the developers are paid to do work on Gateway. However, once
> the project has a community built around it, we expect to get committers
> and developers from outside the current core developers.
>
> === Relationships with Other Apache Products ===
>
> Gateway is going to be used by the users and operators of Hadoop, and the
> Hadoop ecosystem in general.
>
> === A Excessive Fascination with the Apache Brand ===
>
> Our interest in developing Gateway in Apache project is to follow an
> established development model, as well since many of the Hadoop ecosystem
> projects also are part of Apache, Gateway will complement those projects by
> following the same development and contribution model.
>
> == Documentation ==
>
> There is documentation in Hortonworks’ internal repositories. These can be
> shared upon request and will be transferred into the Apache CM system if
> this proposal is accepted.
>
> == Initial Source ==
>
> The source is currently in Hortonworks’ internal repositories. The process
> of making this GitHub repository public has been started and the URL will
> be provided once available.
>
> == Source and Intellectual Property Submission Plan ==
>
> The complete Gateway code is under Apache Software License 2.
>
> == External Dependencies ==
>
> The Gateway dependencies are listed below, separated by Category A and
> Category B as defined in the Apache Third-Party Licensing Policy. Note:
> These are the direct dependencies. Indirect dependencies are not included.
>
> === Category A Dependencies ===
>
> Apache Commons - ASLv2.0
> commons-io:commons-io#2.4
> commons-cli:commons-cli#1.2
> commons-codec:commons-codec#1.**7
> org.apache.commons:commons-**digester3#3.2
> org.apache.commons:commons-**vfs2#2.0
> Apache Hadoop - ASLv2.0
> org.apache.hadoop:hadoop-auth#**0.23.3
> org.apache.hadoop:hadoop-core#**1.0.3
> Apache Geronimo - ASLv2.0
> org.apache.geronimo.**components:geronimo-jaspi#2.0.**0
> org.apache.geronimo.specs:**geronimo-osgi-locator#1.1
> Apache Shiro - ASLv2.0
> org.apache.shiro:shiro-web#1.**2.1
> ApacheDS - ASLv2.0
> org.apache.directory.server:**apacheds-all#1.5.5
> Log4J - ASLv2.0
> log4j:log4j#1.2.17
> SL4J - MIT
> org.slf4j:slf4j-api#1.6.6
> org.slf4j:slf4j-log4j12#1.6.6
> Guava - ASLv2.0
> com.google.guava:guava#14.0-**rc1
> HttpClient - ASLv2.0
> org.apache.httpcomponents:**httpclient#4.2.1
> Jetty - ASLv2.0
> org.eclipse.jetty:jetty-**server#8.1.7.v20120910
> org.eclipse.jetty:jetty-**servlet#8.1.7.v20120910
> org.eclipse.jetty:jetty-**webapp#8.1.7.v20120910
> org.eclipse.jetty:jetty-jaspi#**8.1.7.v20120910
> org.eclipse.jetty.aggregate:**jetty-all#8.1.7.v20120910
> org.eclipse.jetty:test-jetty-**servlet#8.1.7.v20120910
> Spring Security - ASLv2.0
> org.springframework:spring-**core#3.1.3.RELEASE
> org.springframework:spring-**context#3.1.3.RELEASE
> org.springframework:spring-**web#3.1.3.RELEASE
> org.springframework.security:**spring-security-core#3.1.3.**RELEASE
> org.springframework.security:**spring-security-web#3.1.3.**RELEASE
> org.springframework.security:**spring-security-config#3.1.3.**RELEASE
> org.springframework.security:**spring-security-ldap#3.1.2.**RELEASE
> org.springframework.ldap:**spring-ldap-core#1.3.1.RELEASE
> org.springframework.ldap:**spring-ldap-core-tiger#1.3.1.**RELEASE
> org.springframework.ldap:**spring-ldap-odm#1.3.1.RELEASE
> org.springframework.ldap:**spring-ldap-ldif-core#1.3.1.**RELEASE
> org.springframework.ldap:**spring-ldap-ldif-batch#1.3.1.**RELEASE
> JBoss ShrinkWrap - ASLv2.0
> org.jboss.shrinkwrap:**shrinkwrap-api#1.0.1
> org.jboss.shrinkwrap:**shrinkwrap-impl-base#1.0.1
> org.jboss.shrinkwrap.**descriptors:shrinkwrap-**
> descriptors-api-javaee#2.0.0-**alpha-4
> org.jboss.shrinkwrap.**descriptors:shrinkwrap-**
> descriptors-impl-javaee#2.0.0-**alpha-4
>
> === Category A Dependencies (Test) ===
>
> EasyMock - ASLv2.0
> org.easymock:easymock#3.0
> XML Matchers - ASLv2.0
> org.xmlmatchers:xml-matchers#**0.10
> Hamcrest - BSDv3
> org.hamcrest:hamcrest-api#1.0
> org.hamcrest:hamcrest-core#1.**2.1
> org.hamcrest:hamcrest-library#**1.2.1
> JsonPath - ASLv2.0
> com.jayway.jsonpath:json-path#**0.8.1
> com.jayway.jsonpath:json-path-**assert#0.8.1
> XMLTool - ASLv2.0
> com.mycila.xmltool:xmltool#3.3
> REST-assured - ASLv2.0
> com.jayway.restassured:rest-**assured#1.6.2
>
> === Category B Dependencies ===
>
> Jersey - CDDLv1.1 or GPL2wCPE
> com.sun.jersey:jersey-server#**1.14
> com.sun.jersey:jersey-servlet#**1.14
> Jerico - EPLv1.0
> net.htmlparser.jericho:**jericho-html#3.2
> Servlet - CDDLv1.0 or GPLv2
> javax.servlet:javax.servlet-**api#3.0.1
> JUnit - CPLv1.0
> junit:junit#4.11
>
> == Cryptography ==
>
> The Gateway uses cryptographic software indirectly as a result of having
> two dependencies: ApacheDS and Apache Shiro. Gateway does not include any
> special or custom cryptographic technologies.
>
> ApacheDS is an ASF project and has been classified Export Commodity
> Control Number (ECCN) 5D002.C.1 due to it’s dependency on Bouncy Castle.
> More information on the ApacheDS classification can be found at
> http://svn.apache.org/repos/**asf/directory/apacheds/trunk/**
> installers/README<http://svn.apache.org/repos/asf/directory/apacheds/trunk/installers/README>
>
> Apache Shiro is an ASF project and has been classified Export Commodity
> Control Number (ECCN) 5D002.C.1. More information on the Apache Shiro
> classification can be found at http://svn.apache.org/repos/**
> asf/shiro/trunk/README<http://svn.apache.org/repos/asf/shiro/trunk/README>
>
> == Required Resources ==
>
> === Mailing lists ===
>
> knox-dev AT incubator DOT apache DOT org
> knox-commits AT incubator DOT apache DOT org
> knox-user AT hms incubator apache DOT org
> knox-private AT incubator DOT apache DOT org
>
> === Subversion Directory ===
>
> https://svn.apache.org/repos/**asf/incubator/knox<https://svn.apache.org/repos/asf/incubator/knox>
>
> === Issue Tracking ===
>
> JIRA Knox (KNOX)
>
> == Initial Committers ==
>
> Kevin Minder (kevin DOT minder AT hortonworks DOT com)
> Larry McCay (lmccay AT hortonworks DOT com)
> John Speidel (jspeidel AT hortonworks DOT com)
> Tom Beerbower (tbeerbower AT hortonworks DOT com)
> Sumit Mohanty (smohanty AT hortonworks DOT com)
>
> == Affiliations ==
>
> Kevin Minder (Hortonworks)
> Larry McCay (Hortonworks)
> John Speidel (Hortonworks)
> Tom Beerbower (Hortonworks)
> Sumit Mohanty (Hortonworks)
>
> == Sponsors ==
>
> === Champion ===
>
> Devaraj Das (ddas AT apache DOT org)
>
> === Nominated Mentors ===
>
> Owen O’Malley (omalley AT apache DOT org)
> Mahadev Konar (mahadev AT apache DOT org)
> Alan Gates (gates AT apache DOT org)
> Devaraj Das (ddas AT apache DOT org)
>
> === Sponsoring Entity ===
>
> Incubator PMC
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org<ge...@incubator.apache.org>
> For additional commands, e-mail: general-help@incubator.apache.**org<ge...@incubator.apache.org>
>
>
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Kevin Minder <ke...@hortonworks.com>.
Hi Hadrian,
Currently I would like to keep the focus on Hadoop services to make sure
that we can produce a useful product in a reasonable time frame. We
have been careful with the initial code however to treat all Hadoop
integrations as modular plugins. So we have and will consider
increasing the scope to other apache projects at the right time.
Also, the code is currently available at https://github.com/hortonworks/knox
Kevin.
On 2/11/13 10:54 PM, Hadrian Zbarcea wrote:
> +1 on the idea.
> +1 (strong) on the need to increase diversity.
>
> I would suggest to open a bit the scope of the project to target other
> apache projects that act as services. I know it was mentioned, but it
> sounded to me more like a possibility than a focus.
>
> I would also volunteer as a committer and, if you prefer, mentor. I
> assume it would be possible to take a peek at the code grant in the
> coming days.
>
> Cheers,
> Hadrian
>
> On 02/11/2013 10:10 AM, Bertrand Delacretaz wrote:
>> On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
>> <ke...@hortonworks.com> wrote:
>> ...
>>> === Nominated Mentors ===
>>>
>>> Owen O’Malley (omalley AT apache DOT org)
>>> Mahadev Konar (mahadev AT apache DOT org)
>>> Alan Gates (gates AT apache DOT org)
>>> Devaraj Das (ddas AT apache DOT org)
>> ...
>>
>> Considering all initial committers are from hortonworks, I'd like to
>> see affiliations for mentors as well - or at least indicate which
>> mentors are *not* affiliated with hortonworks.
>>
>> -Bertrand
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Hadrian Zbarcea <hz...@gmail.com>.
+1 on the idea.
+1 (strong) on the need to increase diversity.
I would suggest to open a bit the scope of the project to target other
apache projects that act as services. I know it was mentioned, but it
sounded to me more like a possibility than a focus.
I would also volunteer as a committer and, if you prefer, mentor. I
assume it would be possible to take a peek at the code grant in the
coming days.
Cheers,
Hadrian
On 02/11/2013 10:10 AM, Bertrand Delacretaz wrote:
> On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
> <ke...@hortonworks.com> wrote:
> ...
>> === Nominated Mentors ===
>>
>> Owen O’Malley (omalley AT apache DOT org)
>> Mahadev Konar (mahadev AT apache DOT org)
>> Alan Gates (gates AT apache DOT org)
>> Devaraj Das (ddas AT apache DOT org)
> ...
>
> Considering all initial committers are from hortonworks, I'd like to
> see affiliations for mentors as well - or at least indicate which
> mentors are *not* affiliated with hortonworks.
>
> -Bertrand
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Upayavira <uv...@odoko.co.uk>.
Diversity as has been discussed has generally been about contributors
not mentors, but while we should be able to expect mentors to act
primarily in the best interests of the ASF not their employer, having
some diversity of mentors is going to be a good thing.
The flaws in the initial landgrab over committership at the beginning of
a podling's life have been demonstrated. I believe it is best to start
with a known set of contributors (from one org is fine) and watch them
demonstrate their ability to open up their project quickly by setting a
low bar to committership.
It does seem like this project now has a wealth of mentor options. I've
seen projects with six mentors, five of which were quickly inactive. It
makes sense I'd say to start a discussion amongst those who have
volunteered to see who is best placed to be an active mentor. A project
choosing their own mentors also makes sense, as these are people they
are going to be working with.
Just some reflections.
Upayavira
On Wed, Feb 13, 2013, at 12:27 AM, Josh Wills wrote:
> I thought that the need for diversity referred to the community, not to
> the
> mentors.
>
> I strongly advocate for newly incubating projects choosing their own
> initial members (you need only search for the epic thread that resulted
> from the Crunch Proposal circa May 2012), but it seems like recent data
> suggests that starting out with a small set of committers from a single
> organization working on a large and complex codebase is a recipe for
> diversity issues and a difficult path out of the incubator.
>
> Kevin et al., please choose whomever you want, but do consider getting
> some
> folks from other organizations to seed the community. It does so much
> good
> for the project over the long term.
>
>
> On Tue, Feb 12, 2013 at 3:31 PM, Devaraj Das <dd...@hortonworks.com>
> wrote:
>
> > Hi folks,
> > Happy to see such a hugely positive response on the proposal. I'll put
> > up a vote tomorrow.
> >
> > Now, on the mentors, I think we have enough at this point and we have
> > also addressed the diversity concern. I had got the confirmation from
> > Chris Douglas and Chris Mattmann yesterday afternoon that they would
> > participate as mentors in the project. On the nominations for getting
> > involved in the project, you are welcome to come in as contributors.
> > Individuals in the initial list of committers all have a view point
> > that the committers list be kept as such and the standard practice
> > (based on contributions, after the project is accepted for incubation)
> > for accepting new committers be followed here.
> >
> > Thanks
> > Devaraj.
> >
> > On Mon, Feb 11, 2013 at 8:07 AM, Kevin Minder
> > <ke...@hortonworks.com> wrote:
> > > Hi Bertrand,
> > > Currently all of the mentors are affiliated with Hortonworks as well. We
> > > can reach out to a number of other people and organizations that are
> > > interested in the project to diversify if this is an important
> > consideration
> > > at this stage.
> > >
> > > One other question I have is about creating a wiki to host the proposal.
> > I
> > > don't seem to have privs to create http://wiki.apache.org/incubator/knox
> > .
> > > Would that be the correct place to evolve the proposal? If so, how do I
> > go
> > > about creating in?
> > > Kevin.
> > >
> > >
> > > On 2/11/13 10:10 AM, Bertrand Delacretaz wrote:
> > >>
> > >> On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
> > >> <ke...@hortonworks.com> wrote:
> > >> ...
> > >>>
> > >>> === Nominated Mentors ===
> > >>>
> > >>> Owen O’Malley (omalley AT apache DOT org)
> > >>> Mahadev Konar (mahadev AT apache DOT org)
> > >>> Alan Gates (gates AT apache DOT org)
> > >>> Devaraj Das (ddas AT apache DOT org)
> > >>
> > >> ...
> > >>
> > >> Considering all initial committers are from hortonworks, I'd like to
> > >> see affiliations for mentors as well - or at least indicate which
> > >> mentors are *not* affiliated with hortonworks.
> > >>
> > >> -Bertrand
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > >> For additional commands, e-mail: general-help@incubator.apache.org
> > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> >
> >
> > On Mon, Feb 11, 2013 at 8:07 AM, Kevin Minder
> > <ke...@hortonworks.com> wrote:
> > > Hi Bertrand,
> > > Currently all of the mentors are affiliated with Hortonworks as well. We
> > > can reach out to a number of other people and organizations that are
> > > interested in the project to diversify if this is an important
> > consideration
> > > at this stage.
> > >
> > > One other question I have is about creating a wiki to host the proposal.
> > I
> > > don't seem to have privs to create http://wiki.apache.org/incubator/knox
> > .
> > > Would that be the correct place to evolve the proposal? If so, how do I
> > go
> > > about creating in?
> > > Kevin.
> > >
> > >
> > > On 2/11/13 10:10 AM, Bertrand Delacretaz wrote:
> > >>
> > >> On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
> > >> <ke...@hortonworks.com> wrote:
> > >> ...
> > >>>
> > >>> === Nominated Mentors ===
> > >>>
> > >>> Owen O’Malley (omalley AT apache DOT org)
> > >>> Mahadev Konar (mahadev AT apache DOT org)
> > >>> Alan Gates (gates AT apache DOT org)
> > >>> Devaraj Das (ddas AT apache DOT org)
> > >>
> > >> ...
> > >>
> > >> Considering all initial committers are from hortonworks, I'd like to
> > >> see affiliations for mentors as well - or at least indicate which
> > >> mentors are *not* affiliated with hortonworks.
> > >>
> > >> -Bertrand
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > >> For additional commands, e-mail: general-help@incubator.apache.org
> > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> >
> >
> > On Mon, Feb 11, 2013 at 8:07 AM, Kevin Minder
> > <ke...@hortonworks.com> wrote:
> > > Hi Bertrand,
> > > Currently all of the mentors are affiliated with Hortonworks as well. We
> > > can reach out to a number of other people and organizations that are
> > > interested in the project to diversify if this is an important
> > consideration
> > > at this stage.
> > >
> > > One other question I have is about creating a wiki to host the proposal.
> > I
> > > don't seem to have privs to create http://wiki.apache.org/incubator/knox
> > .
> > > Would that be the correct place to evolve the proposal? If so, how do I
> > go
> > > about creating in?
> > > Kevin.
> > >
> > >
> > > On 2/11/13 10:10 AM, Bertrand Delacretaz wrote:
> > >>
> > >> On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
> > >> <ke...@hortonworks.com> wrote:
> > >> ...
> > >>>
> > >>> === Nominated Mentors ===
> > >>>
> > >>> Owen O’Malley (omalley AT apache DOT org)
> > >>> Mahadev Konar (mahadev AT apache DOT org)
> > >>> Alan Gates (gates AT apache DOT org)
> > >>> Devaraj Das (ddas AT apache DOT org)
> > >>
> > >> ...
> > >>
> > >> Considering all initial committers are from hortonworks, I'd like to
> > >> see affiliations for mentors as well - or at least indicate which
> > >> mentors are *not* affiliated with hortonworks.
> > >>
> > >> -Bertrand
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > >> For additional commands, e-mail: general-help@incubator.apache.org
> > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
>
> --
> Director of Data Science
> Cloudera <http://www.cloudera.com>
> Twitter: @josh_wills <http://twitter.com/josh_wills>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Josh Wills <jw...@cloudera.com>.
I thought that the need for diversity referred to the community, not to the
mentors.
I strongly advocate for newly incubating projects choosing their own
initial members (you need only search for the epic thread that resulted
from the Crunch Proposal circa May 2012), but it seems like recent data
suggests that starting out with a small set of committers from a single
organization working on a large and complex codebase is a recipe for
diversity issues and a difficult path out of the incubator.
Kevin et al., please choose whomever you want, but do consider getting some
folks from other organizations to seed the community. It does so much good
for the project over the long term.
On Tue, Feb 12, 2013 at 3:31 PM, Devaraj Das <dd...@hortonworks.com> wrote:
> Hi folks,
> Happy to see such a hugely positive response on the proposal. I'll put
> up a vote tomorrow.
>
> Now, on the mentors, I think we have enough at this point and we have
> also addressed the diversity concern. I had got the confirmation from
> Chris Douglas and Chris Mattmann yesterday afternoon that they would
> participate as mentors in the project. On the nominations for getting
> involved in the project, you are welcome to come in as contributors.
> Individuals in the initial list of committers all have a view point
> that the committers list be kept as such and the standard practice
> (based on contributions, after the project is accepted for incubation)
> for accepting new committers be followed here.
>
> Thanks
> Devaraj.
>
> On Mon, Feb 11, 2013 at 8:07 AM, Kevin Minder
> <ke...@hortonworks.com> wrote:
> > Hi Bertrand,
> > Currently all of the mentors are affiliated with Hortonworks as well. We
> > can reach out to a number of other people and organizations that are
> > interested in the project to diversify if this is an important
> consideration
> > at this stage.
> >
> > One other question I have is about creating a wiki to host the proposal.
> I
> > don't seem to have privs to create http://wiki.apache.org/incubator/knox
> .
> > Would that be the correct place to evolve the proposal? If so, how do I
> go
> > about creating in?
> > Kevin.
> >
> >
> > On 2/11/13 10:10 AM, Bertrand Delacretaz wrote:
> >>
> >> On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
> >> <ke...@hortonworks.com> wrote:
> >> ...
> >>>
> >>> === Nominated Mentors ===
> >>>
> >>> Owen O’Malley (omalley AT apache DOT org)
> >>> Mahadev Konar (mahadev AT apache DOT org)
> >>> Alan Gates (gates AT apache DOT org)
> >>> Devaraj Das (ddas AT apache DOT org)
> >>
> >> ...
> >>
> >> Considering all initial committers are from hortonworks, I'd like to
> >> see affiliations for mentors as well - or at least indicate which
> >> mentors are *not* affiliated with hortonworks.
> >>
> >> -Bertrand
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
>
> On Mon, Feb 11, 2013 at 8:07 AM, Kevin Minder
> <ke...@hortonworks.com> wrote:
> > Hi Bertrand,
> > Currently all of the mentors are affiliated with Hortonworks as well. We
> > can reach out to a number of other people and organizations that are
> > interested in the project to diversify if this is an important
> consideration
> > at this stage.
> >
> > One other question I have is about creating a wiki to host the proposal.
> I
> > don't seem to have privs to create http://wiki.apache.org/incubator/knox
> .
> > Would that be the correct place to evolve the proposal? If so, how do I
> go
> > about creating in?
> > Kevin.
> >
> >
> > On 2/11/13 10:10 AM, Bertrand Delacretaz wrote:
> >>
> >> On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
> >> <ke...@hortonworks.com> wrote:
> >> ...
> >>>
> >>> === Nominated Mentors ===
> >>>
> >>> Owen O’Malley (omalley AT apache DOT org)
> >>> Mahadev Konar (mahadev AT apache DOT org)
> >>> Alan Gates (gates AT apache DOT org)
> >>> Devaraj Das (ddas AT apache DOT org)
> >>
> >> ...
> >>
> >> Considering all initial committers are from hortonworks, I'd like to
> >> see affiliations for mentors as well - or at least indicate which
> >> mentors are *not* affiliated with hortonworks.
> >>
> >> -Bertrand
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
>
> On Mon, Feb 11, 2013 at 8:07 AM, Kevin Minder
> <ke...@hortonworks.com> wrote:
> > Hi Bertrand,
> > Currently all of the mentors are affiliated with Hortonworks as well. We
> > can reach out to a number of other people and organizations that are
> > interested in the project to diversify if this is an important
> consideration
> > at this stage.
> >
> > One other question I have is about creating a wiki to host the proposal.
> I
> > don't seem to have privs to create http://wiki.apache.org/incubator/knox
> .
> > Would that be the correct place to evolve the proposal? If so, how do I
> go
> > about creating in?
> > Kevin.
> >
> >
> > On 2/11/13 10:10 AM, Bertrand Delacretaz wrote:
> >>
> >> On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
> >> <ke...@hortonworks.com> wrote:
> >> ...
> >>>
> >>> === Nominated Mentors ===
> >>>
> >>> Owen O’Malley (omalley AT apache DOT org)
> >>> Mahadev Konar (mahadev AT apache DOT org)
> >>> Alan Gates (gates AT apache DOT org)
> >>> Devaraj Das (ddas AT apache DOT org)
> >>
> >> ...
> >>
> >> Considering all initial committers are from hortonworks, I'd like to
> >> see affiliations for mentors as well - or at least indicate which
> >> mentors are *not* affiliated with hortonworks.
> >>
> >> -Bertrand
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Director of Data Science
Cloudera <http://www.cloudera.com>
Twitter: @josh_wills <http://twitter.com/josh_wills>
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Devaraj Das <dd...@hortonworks.com>.
Hi folks,
Happy to see such a hugely positive response on the proposal. I'll put
up a vote tomorrow.
Now, on the mentors, I think we have enough at this point and we have
also addressed the diversity concern. I had got the confirmation from
Chris Douglas and Chris Mattmann yesterday afternoon that they would
participate as mentors in the project. On the nominations for getting
involved in the project, you are welcome to come in as contributors.
Individuals in the initial list of committers all have a view point
that the committers list be kept as such and the standard practice
(based on contributions, after the project is accepted for incubation)
for accepting new committers be followed here.
Thanks
Devaraj.
On Mon, Feb 11, 2013 at 8:07 AM, Kevin Minder
<ke...@hortonworks.com> wrote:
> Hi Bertrand,
> Currently all of the mentors are affiliated with Hortonworks as well. We
> can reach out to a number of other people and organizations that are
> interested in the project to diversify if this is an important consideration
> at this stage.
>
> One other question I have is about creating a wiki to host the proposal. I
> don't seem to have privs to create http://wiki.apache.org/incubator/knox.
> Would that be the correct place to evolve the proposal? If so, how do I go
> about creating in?
> Kevin.
>
>
> On 2/11/13 10:10 AM, Bertrand Delacretaz wrote:
>>
>> On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
>> <ke...@hortonworks.com> wrote:
>> ...
>>>
>>> === Nominated Mentors ===
>>>
>>> Owen O’Malley (omalley AT apache DOT org)
>>> Mahadev Konar (mahadev AT apache DOT org)
>>> Alan Gates (gates AT apache DOT org)
>>> Devaraj Das (ddas AT apache DOT org)
>>
>> ...
>>
>> Considering all initial committers are from hortonworks, I'd like to
>> see affiliations for mentors as well - or at least indicate which
>> mentors are *not* affiliated with hortonworks.
>>
>> -Bertrand
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
On Mon, Feb 11, 2013 at 8:07 AM, Kevin Minder
<ke...@hortonworks.com> wrote:
> Hi Bertrand,
> Currently all of the mentors are affiliated with Hortonworks as well. We
> can reach out to a number of other people and organizations that are
> interested in the project to diversify if this is an important consideration
> at this stage.
>
> One other question I have is about creating a wiki to host the proposal. I
> don't seem to have privs to create http://wiki.apache.org/incubator/knox.
> Would that be the correct place to evolve the proposal? If so, how do I go
> about creating in?
> Kevin.
>
>
> On 2/11/13 10:10 AM, Bertrand Delacretaz wrote:
>>
>> On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
>> <ke...@hortonworks.com> wrote:
>> ...
>>>
>>> === Nominated Mentors ===
>>>
>>> Owen O’Malley (omalley AT apache DOT org)
>>> Mahadev Konar (mahadev AT apache DOT org)
>>> Alan Gates (gates AT apache DOT org)
>>> Devaraj Das (ddas AT apache DOT org)
>>
>> ...
>>
>> Considering all initial committers are from hortonworks, I'd like to
>> see affiliations for mentors as well - or at least indicate which
>> mentors are *not* affiliated with hortonworks.
>>
>> -Bertrand
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
On Mon, Feb 11, 2013 at 8:07 AM, Kevin Minder
<ke...@hortonworks.com> wrote:
> Hi Bertrand,
> Currently all of the mentors are affiliated with Hortonworks as well. We
> can reach out to a number of other people and organizations that are
> interested in the project to diversify if this is an important consideration
> at this stage.
>
> One other question I have is about creating a wiki to host the proposal. I
> don't seem to have privs to create http://wiki.apache.org/incubator/knox.
> Would that be the correct place to evolve the proposal? If so, how do I go
> about creating in?
> Kevin.
>
>
> On 2/11/13 10:10 AM, Bertrand Delacretaz wrote:
>>
>> On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
>> <ke...@hortonworks.com> wrote:
>> ...
>>>
>>> === Nominated Mentors ===
>>>
>>> Owen O’Malley (omalley AT apache DOT org)
>>> Mahadev Konar (mahadev AT apache DOT org)
>>> Alan Gates (gates AT apache DOT org)
>>> Devaraj Das (ddas AT apache DOT org)
>>
>> ...
>>
>> Considering all initial committers are from hortonworks, I'd like to
>> see affiliations for mentors as well - or at least indicate which
>> mentors are *not* affiliated with hortonworks.
>>
>> -Bertrand
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Alejandro Abdelnur <tu...@cloudera.com>.
Hi Kevin,
I'd like to offer joining the project if accepted for incubation.
I'm actively working in Hadoop (PMC member) and Oozie (PMC member), helped
driving Oozie through incubation and graduation. I'm also the initial
developer of hadoop-auth and httpfs (standalone WebHDFS gateway). In, Oozie
provides REST APIs for jobs submission (workflows, coordinators, bundles,
mapreduce, streaming, pig). In addition I've been involved in efforts for
providing HTTP access to Hadoop stack.
Thanks.
On Mon, Feb 11, 2013 at 11:54 AM, Kevin Minder <kevin.minder@hortonworks.com
> wrote:
> The proposal is now hosted on the wiki.
> http://wiki.apache.org/**incubator/knox<http://wiki.apache.org/incubator/knox>
> Currently just the initial proposal. I'll be incorporating
> feedback/clarifications shortly.
>
>
> On 2/11/13 11:35 AM, Bertrand Delacretaz wrote:
>
>> Hi,
>>
>> On Mon, Feb 11, 2013 at 5:07 PM, Kevin Minder
>> <ke...@hortonworks.com> wrote:
>>
>>> ...Currently all of the mentors are affiliated with Hortonworks as well.
>>> We
>>> can reach out to a number of other people and organizations that are
>>> interested in the project to diversify if this is an important
>>> consideration
>>> at this stage....
>>>
>> I think that would be good - just ask for more mentors on this list.
>> Without such diversity this is basically an all-hortonworks podling,
>> which is not good IMO.
>>
>> ....I
>>> don't seem to have privs to create http://wiki.apache.org/**
>>> incubator/knox <http://wiki.apache.org/incubator/knox>.
>>> Would that be the correct place to evolve the proposal? If so, how do I
>>> go
>>> about creating in?...
>>>
>> Yes, http://wiki.apache.org/**incubator/is<http://wiki.apache.org/incubator/is>the right place - just ask
>> for write access on this list, a [wiki] marker in the subject line
>> will probably help. I don't think I have the rights to grant that
>> access myself.
>>
>> -Bertrand
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org<ge...@incubator.apache.org>
>> For additional commands, e-mail: general-help@incubator.apache.**org<ge...@incubator.apache.org>
>>
>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org<ge...@incubator.apache.org>
> For additional commands, e-mail: general-help@incubator.apache.**org<ge...@incubator.apache.org>
>
>
--
Alejandro
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Kevin Minder <ke...@hortonworks.com>.
The proposal is now hosted on the wiki.
http://wiki.apache.org/incubator/knox
Currently just the initial proposal. I'll be incorporating
feedback/clarifications shortly.
On 2/11/13 11:35 AM, Bertrand Delacretaz wrote:
> Hi,
>
> On Mon, Feb 11, 2013 at 5:07 PM, Kevin Minder
> <ke...@hortonworks.com> wrote:
>> ...Currently all of the mentors are affiliated with Hortonworks as well. We
>> can reach out to a number of other people and organizations that are
>> interested in the project to diversify if this is an important consideration
>> at this stage....
> I think that would be good - just ask for more mentors on this list.
> Without such diversity this is basically an all-hortonworks podling,
> which is not good IMO.
>
>> ....I
>> don't seem to have privs to create http://wiki.apache.org/incubator/knox.
>> Would that be the correct place to evolve the proposal? If so, how do I go
>> about creating in?...
> Yes, http://wiki.apache.org/incubator/is the right place - just ask
> for write access on this list, a [wiki] marker in the subject line
> will probably help. I don't think I have the rights to grant that
> access myself.
>
> -Bertrand
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [WIKI] Permissions to create new wiki page for Knox proposal
Posted by Kevin Minder <ke...@hortonworks.com>.
Thanks you! I've created the page.
On 2/11/13 2:22 PM, Marvin Humphrey wrote:
> On Mon, Feb 11, 2013 at 8:43 AM, Kevin Minder
> <ke...@hortonworks.com> wrote:
>> Can someone please grant me (kminder) the premissions required to create a
>> wiki page to host the Knox proposal (http://wiki.apache.org/incubator/knox).
> Done.
>
> The wiki username "kminder" now has permission to edit most pages under
> wiki.apache.org/incubator.
>
> Marvin Humphrey
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [WIKI] Permissions to create new wiki page for Knox proposal
Posted by Marvin Humphrey <ma...@rectangular.com>.
On Mon, Feb 11, 2013 at 8:43 AM, Kevin Minder
<ke...@hortonworks.com> wrote:
> Can someone please grant me (kminder) the premissions required to create a
> wiki page to host the Knox proposal (http://wiki.apache.org/incubator/knox).
Done.
The wiki username "kminder" now has permission to edit most pages under
wiki.apache.org/incubator.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
[WIKI] Permissions to create new wiki page for Knox proposal
Posted by Kevin Minder <ke...@hortonworks.com>.
Hi Everyone,
Can someone please grant me (kminder) the premissions required to create
a wiki page to host the Knox proposal
(http://wiki.apache.org/incubator/knox).
Kevin.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Mon, Feb 11, 2013 at 5:07 PM, Kevin Minder
<ke...@hortonworks.com> wrote:
> ...Currently all of the mentors are affiliated with Hortonworks as well. We
> can reach out to a number of other people and organizations that are
> interested in the project to diversify if this is an important consideration
> at this stage....
I think that would be good - just ask for more mentors on this list.
Without such diversity this is basically an all-hortonworks podling,
which is not good IMO.
>
> ....I
> don't seem to have privs to create http://wiki.apache.org/incubator/knox.
> Would that be the correct place to evolve the proposal? If so, how do I go
> about creating in?...
Yes, http://wiki.apache.org/incubator/is the right place - just ask
for write access on this list, a [wiki] marker in the subject line
will probably help. I don't think I have the rights to grant that
access myself.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Kevin Minder <ke...@hortonworks.com>.
Hi Bertrand,
Currently all of the mentors are affiliated with Hortonworks as well.
We can reach out to a number of other people and organizations that are
interested in the project to diversify if this is an important
consideration at this stage.
One other question I have is about creating a wiki to host the
proposal. I don't seem to have privs to create
http://wiki.apache.org/incubator/knox. Would that be the correct place
to evolve the proposal? If so, how do I go about creating in?
Kevin.
On 2/11/13 10:10 AM, Bertrand Delacretaz wrote:
> On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
> <ke...@hortonworks.com> wrote:
> ...
>> === Nominated Mentors ===
>>
>> Owen O’Malley (omalley AT apache DOT org)
>> Mahadev Konar (mahadev AT apache DOT org)
>> Alan Gates (gates AT apache DOT org)
>> Devaraj Das (ddas AT apache DOT org)
> ...
>
> Considering all initial committers are from hortonworks, I'd like to
> see affiliations for mentors as well - or at least indicate which
> mentors are *not* affiliated with hortonworks.
>
> -Bertrand
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Mon, Feb 11, 2013 at 3:55 PM, Kevin Minder
<ke...@hortonworks.com> wrote:
...
> === Nominated Mentors ===
>
> Owen O’Malley (omalley AT apache DOT org)
> Mahadev Konar (mahadev AT apache DOT org)
> Alan Gates (gates AT apache DOT org)
> Devaraj Das (ddas AT apache DOT org)
...
Considering all initial committers are from hortonworks, I'd like to
see affiliations for mentors as well - or at least indicate which
mentors are *not* affiliated with hortonworks.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Kevin Minder <ke...@hortonworks.com>.
The current Knox source is now publicly readable.
https://github.com/hortonworks/knox.git
On 2/11/13 1:44 PM, Jakob Homan wrote:
> When do you expect the github to be made available?
> -Jakob
>
>
>
> On Mon, Feb 11, 2013 at 10:21 AM, Alex Karasulu <ak...@apache.org>wrote:
>
>> Hi Kevin,
>>
>> This sounds like a much needed project. I endorse the concept but as
>> Bertrand pointed out you need a bit more diversity. Otherwise I see no
>> problem with moving forward.
>>
>> Good luck!
>>
>>
>> On Mon, Feb 11, 2013 at 4:55 PM, Kevin Minder
>> <ke...@hortonworks.com>wrote:
>>
>>> Knox Gateway Proposal
>>>
>>> == Abstract ==
>>>
>>> Knox Gateway is a system that provides a single point of secure access
>> for
>>> Apache Hadoop clusters.
>>>
>>> == Proposal ==
>>>
>>> The Knox Gateway (“Gateway” or “Knox”) is a system that provides a single
>>> point of authentication and access for Apache Hadoop services in a
>> cluster.
>>> The goal is to simplify Hadoop security for both users (i.e. who access
>> the
>>> cluster data and execute jobs) and operators (i.e. who control access and
>>> manage the cluster). The Gateway runs as a server (or cluster of servers)
>>> that serve one or more Hadoop clusters.
>>>
>>> Provide perimeter security to make Hadoop security setup easier
>>> Support authentication and token verification security scenarios
>>> Deliver users a single cluster end-point that aggregates capabilities for
>>> data and jobs
>>> Enable integration with enterprise and cloud identity management
>>> environments
>>>
>>> == Background ==
>>>
>>> An Apache Hadoop cluster is presented to consumers as a loose collection
>>> of independent services. This makes it difficult for users to interact
>> with
>>> Hadoop since each service maintains it’s own method of access and
>> security.
>>> As well, for operators, configuration and administration of a secure
>> Hadoop
>>> cluster is a complex and many Hadoop clusters are insecure as a result.
>>>
>>> == Rationale ==
>>>
>>> Organizations that are struggling with Hadoop cluster security result in
>>> a) running Hadoop without security or b) slowing adoption of Hadoop. The
>>> Gateway aims to provide perimeter security that integrates more easily
>> into
>>> existing organizations’ security infrastructure. Doing so will simplify
>>> security for these organizations and benefit all Hadoop stakeholders
>> (i.e.
>>> users and operators). Additionally, making a dedicated perimeter security
>>> project part of the Apache Hadoop ecosystem will prevent fragmentation in
>>> this area and further increase the value of Hadoop as a data platform.
>>>
>>> == Current Status ==
>>>
>>> Prototype available, developed by the list of initial committers.
>>>
>>> === Meritocracy ===
>>>
>>> We desire to build a diverse developer community around Gateway following
>>> the Apache Way. We want to make the project open source and will
>> encourage
>>> contributors from multiple organizations following the Apache meritocracy
>>> model.
>>>
>>> === Community ===
>>>
>>> We hope to extend the user and developer base in the future and build a
>>> solid open source community around Gateway. Apache Hadoop has a large
>>> ecosystem of open source projects, each with a strong community of
>>> contributors. All project communities in this ecosystem have an
>> opportunity
>>> to participate in the advancement of the Gateway project because
>>> ultimately, Gateway will enable the security capabilities of their
>> project
>>> to be more enterprise friendly.
>>>
>>> === Core Developers ===
>>>
>>> Gateway is currently being developed by several engineers from
>> Hortonworks
>>> - Kevin Minder, Larry McCay, John Speidel, Tom Beerbower and Sumit
>> Mohanty.
>>> All the engineers have deep expertise in middleware, security & identity
>>> systems and are quite familiar with the Hadoop ecosystem.
>>>
>>> === Alignment ===
>>>
>>> The ASF is a natural host for Gateway given that it is already the home
>> of
>>> Hadoop, Hive, Pig, HBase, Oozie and other emerging big data software
>>> projects. Gateway is designed to solve the security challenges familiar
>> to
>>> the Hadoop ecosystem family of projects.
>>>
>>> == Known Risks ==
>>>
>>> === Orphaned products & Reliance on Salaried Developers ===
>>>
>>> The core developers plan to work full time on the project. We believe
>> that
>>> this project will be of general interest to many Hadoop users and will
>>> attract a diverse set of contributors. We intend to demonstrate this by
>>> having contributors from several organizations recognized as committers
>> by
>>> the time Knox graduates from incubation.
>>>
>>> === Inexperience with Open Source ===
>>>
>>> All of the core developers are active users and followers of open source.
>>> As well, Hortonworks has a strong heritage of success with contributions
>> to
>>> Apache Hadoop Projects.
>>>
>>> === Homogeneous Developers ===
>>>
>>> The current core developers are from Hortonworks, however, we hope to
>>> establish a developer community that includes contributors from several
>>> corporations.
>>>
>>> === Reliance on Salaried Developers ===
>>>
>>> Currently, the developers are paid to do work on Gateway. However, once
>>> the project has a community built around it, we expect to get committers
>>> and developers from outside the current core developers.
>>>
>>> === Relationships with Other Apache Products ===
>>>
>>> Gateway is going to be used by the users and operators of Hadoop, and the
>>> Hadoop ecosystem in general.
>>>
>>> === A Excessive Fascination with the Apache Brand ===
>>>
>>> Our interest in developing Gateway in Apache project is to follow an
>>> established development model, as well since many of the Hadoop ecosystem
>>> projects also are part of Apache, Gateway will complement those projects
>> by
>>> following the same development and contribution model.
>>>
>>> == Documentation ==
>>>
>>> There is documentation in Hortonworks’ internal repositories. These can
>> be
>>> shared upon request and will be transferred into the Apache CM system if
>>> this proposal is accepted.
>>>
>>> == Initial Source ==
>>>
>>> The source is currently in Hortonworks’ internal repositories. The
>> process
>>> of making this GitHub repository public has been started and the URL will
>>> be provided once available.
>>>
>>> == Source and Intellectual Property Submission Plan ==
>>>
>>> The complete Gateway code is under Apache Software License 2.
>>>
>>> == External Dependencies ==
>>>
>>> The Gateway dependencies are listed below, separated by Category A and
>>> Category B as defined in the Apache Third-Party Licensing Policy. Note:
>>> These are the direct dependencies. Indirect dependencies are not
>> included.
>>> === Category A Dependencies ===
>>>
>>> Apache Commons - ASLv2.0
>>> commons-io:commons-io#2.4
>>> commons-cli:commons-cli#1.2
>>> commons-codec:commons-codec#1.**7
>>> org.apache.commons:commons-**digester3#3.2
>>> org.apache.commons:commons-**vfs2#2.0
>>> Apache Hadoop - ASLv2.0
>>> org.apache.hadoop:hadoop-auth#**0.23.3
>>> org.apache.hadoop:hadoop-core#**1.0.3
>>> Apache Geronimo - ASLv2.0
>>> org.apache.geronimo.**components:geronimo-jaspi#2.0.**0
>>> org.apache.geronimo.specs:**geronimo-osgi-locator#1.1
>>> Apache Shiro - ASLv2.0
>>> org.apache.shiro:shiro-web#1.**2.1
>>> ApacheDS - ASLv2.0
>>> org.apache.directory.server:**apacheds-all#1.5.5
>>> Log4J - ASLv2.0
>>> log4j:log4j#1.2.17
>>> SL4J - MIT
>>> org.slf4j:slf4j-api#1.6.6
>>> org.slf4j:slf4j-log4j12#1.6.6
>>> Guava - ASLv2.0
>>> com.google.guava:guava#14.0-**rc1
>>> HttpClient - ASLv2.0
>>> org.apache.httpcomponents:**httpclient#4.2.1
>>> Jetty - ASLv2.0
>>> org.eclipse.jetty:jetty-**server#8.1.7.v20120910
>>> org.eclipse.jetty:jetty-**servlet#8.1.7.v20120910
>>> org.eclipse.jetty:jetty-**webapp#8.1.7.v20120910
>>> org.eclipse.jetty:jetty-jaspi#**8.1.7.v20120910
>>> org.eclipse.jetty.aggregate:**jetty-all#8.1.7.v20120910
>>> org.eclipse.jetty:test-jetty-**servlet#8.1.7.v20120910
>>> Spring Security - ASLv2.0
>>> org.springframework:spring-**core#3.1.3.RELEASE
>>> org.springframework:spring-**context#3.1.3.RELEASE
>>> org.springframework:spring-**web#3.1.3.RELEASE
>>> org.springframework.security:**spring-security-core#3.1.3.**RELEASE
>>> org.springframework.security:**spring-security-web#3.1.3.**RELEASE
>>> org.springframework.security:**spring-security-config#3.1.3.**RELEASE
>>> org.springframework.security:**spring-security-ldap#3.1.2.**RELEASE
>>> org.springframework.ldap:**spring-ldap-core#1.3.1.RELEASE
>>> org.springframework.ldap:**spring-ldap-core-tiger#1.3.1.**RELEASE
>>> org.springframework.ldap:**spring-ldap-odm#1.3.1.RELEASE
>>> org.springframework.ldap:**spring-ldap-ldif-core#1.3.1.**RELEASE
>>> org.springframework.ldap:**spring-ldap-ldif-batch#1.3.1.**RELEASE
>>> JBoss ShrinkWrap - ASLv2.0
>>> org.jboss.shrinkwrap:**shrinkwrap-api#1.0.1
>>> org.jboss.shrinkwrap:**shrinkwrap-impl-base#1.0.1
>>> org.jboss.shrinkwrap.**descriptors:shrinkwrap-**
>>> descriptors-api-javaee#2.0.0-**alpha-4
>>> org.jboss.shrinkwrap.**descriptors:shrinkwrap-**
>>> descriptors-impl-javaee#2.0.0-**alpha-4
>>>
>>> === Category A Dependencies (Test) ===
>>>
>>> EasyMock - ASLv2.0
>>> org.easymock:easymock#3.0
>>> XML Matchers - ASLv2.0
>>> org.xmlmatchers:xml-matchers#**0.10
>>> Hamcrest - BSDv3
>>> org.hamcrest:hamcrest-api#1.0
>>> org.hamcrest:hamcrest-core#1.**2.1
>>> org.hamcrest:hamcrest-library#**1.2.1
>>> JsonPath - ASLv2.0
>>> com.jayway.jsonpath:json-path#**0.8.1
>>> com.jayway.jsonpath:json-path-**assert#0.8.1
>>> XMLTool - ASLv2.0
>>> com.mycila.xmltool:xmltool#3.3
>>> REST-assured - ASLv2.0
>>> com.jayway.restassured:rest-**assured#1.6.2
>>>
>>> === Category B Dependencies ===
>>>
>>> Jersey - CDDLv1.1 or GPL2wCPE
>>> com.sun.jersey:jersey-server#**1.14
>>> com.sun.jersey:jersey-servlet#**1.14
>>> Jerico - EPLv1.0
>>> net.htmlparser.jericho:**jericho-html#3.2
>>> Servlet - CDDLv1.0 or GPLv2
>>> javax.servlet:javax.servlet-**api#3.0.1
>>> JUnit - CPLv1.0
>>> junit:junit#4.11
>>>
>>> == Cryptography ==
>>>
>>> The Gateway uses cryptographic software indirectly as a result of having
>>> two dependencies: ApacheDS and Apache Shiro. Gateway does not include any
>>> special or custom cryptographic technologies.
>>>
>>> ApacheDS is an ASF project and has been classified Export Commodity
>>> Control Number (ECCN) 5D002.C.1 due to it’s dependency on Bouncy Castle.
>>> More information on the ApacheDS classification can be found at
>>> http://svn.apache.org/repos/**asf/directory/apacheds/trunk/**
>>> installers/README<
>> http://svn.apache.org/repos/asf/directory/apacheds/trunk/installers/README
>>>
>>> Apache Shiro is an ASF project and has been classified Export Commodity
>>> Control Number (ECCN) 5D002.C.1. More information on the Apache Shiro
>>> classification can be found at http://svn.apache.org/repos/**
>>> asf/shiro/trunk/README<
>> http://svn.apache.org/repos/asf/shiro/trunk/README>
>>> == Required Resources ==
>>>
>>> === Mailing lists ===
>>>
>>> knox-dev AT incubator DOT apache DOT org
>>> knox-commits AT incubator DOT apache DOT org
>>> knox-user AT hms incubator apache DOT org
>>> knox-private AT incubator DOT apache DOT org
>>>
>>> === Subversion Directory ===
>>>
>>> https://svn.apache.org/repos/**asf/incubator/knox<
>> https://svn.apache.org/repos/asf/incubator/knox>
>>> === Issue Tracking ===
>>>
>>> JIRA Knox (KNOX)
>>>
>>> == Initial Committers ==
>>>
>>> Kevin Minder (kevin DOT minder AT hortonworks DOT com)
>>> Larry McCay (lmccay AT hortonworks DOT com)
>>> John Speidel (jspeidel AT hortonworks DOT com)
>>> Tom Beerbower (tbeerbower AT hortonworks DOT com)
>>> Sumit Mohanty (smohanty AT hortonworks DOT com)
>>>
>>> == Affiliations ==
>>>
>>> Kevin Minder (Hortonworks)
>>> Larry McCay (Hortonworks)
>>> John Speidel (Hortonworks)
>>> Tom Beerbower (Hortonworks)
>>> Sumit Mohanty (Hortonworks)
>>>
>>> == Sponsors ==
>>>
>>> === Champion ===
>>>
>>> Devaraj Das (ddas AT apache DOT org)
>>>
>>> === Nominated Mentors ===
>>>
>>> Owen O’Malley (omalley AT apache DOT org)
>>> Mahadev Konar (mahadev AT apache DOT org)
>>> Alan Gates (gates AT apache DOT org)
>>> Devaraj Das (ddas AT apache DOT org)
>>>
>>> === Sponsoring Entity ===
>>>
>>> Incubator PMC
>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org<
>> general-unsubscribe@incubator.apache.org>
>>> For additional commands, e-mail: general-help@incubator.apache.**org<
>> general-help@incubator.apache.org>
>>>
>>
>> --
>> Best Regards,
>> -- Alex
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Kevin Minder <ke...@hortonworks.com>.
I hope to have the repo converted from private to public today (2/11).
On 2/11/13 1:44 PM, Jakob Homan wrote:
> When do you expect the github to be made available?
> -Jakob
>
>
>
> On Mon, Feb 11, 2013 at 10:21 AM, Alex Karasulu <ak...@apache.org>wrote:
>
>> Hi Kevin,
>>
>> This sounds like a much needed project. I endorse the concept but as
>> Bertrand pointed out you need a bit more diversity. Otherwise I see no
>> problem with moving forward.
>>
>> Good luck!
>>
>>
>> On Mon, Feb 11, 2013 at 4:55 PM, Kevin Minder
>> <ke...@hortonworks.com>wrote:
>>
>>> Knox Gateway Proposal
>>>
>>> == Abstract ==
>>>
>>> Knox Gateway is a system that provides a single point of secure access
>> for
>>> Apache Hadoop clusters.
>>>
>>> == Proposal ==
>>>
>>> The Knox Gateway (“Gateway” or “Knox”) is a system that provides a single
>>> point of authentication and access for Apache Hadoop services in a
>> cluster.
>>> The goal is to simplify Hadoop security for both users (i.e. who access
>> the
>>> cluster data and execute jobs) and operators (i.e. who control access and
>>> manage the cluster). The Gateway runs as a server (or cluster of servers)
>>> that serve one or more Hadoop clusters.
>>>
>>> Provide perimeter security to make Hadoop security setup easier
>>> Support authentication and token verification security scenarios
>>> Deliver users a single cluster end-point that aggregates capabilities for
>>> data and jobs
>>> Enable integration with enterprise and cloud identity management
>>> environments
>>>
>>> == Background ==
>>>
>>> An Apache Hadoop cluster is presented to consumers as a loose collection
>>> of independent services. This makes it difficult for users to interact
>> with
>>> Hadoop since each service maintains it’s own method of access and
>> security.
>>> As well, for operators, configuration and administration of a secure
>> Hadoop
>>> cluster is a complex and many Hadoop clusters are insecure as a result.
>>>
>>> == Rationale ==
>>>
>>> Organizations that are struggling with Hadoop cluster security result in
>>> a) running Hadoop without security or b) slowing adoption of Hadoop. The
>>> Gateway aims to provide perimeter security that integrates more easily
>> into
>>> existing organizations’ security infrastructure. Doing so will simplify
>>> security for these organizations and benefit all Hadoop stakeholders
>> (i.e.
>>> users and operators). Additionally, making a dedicated perimeter security
>>> project part of the Apache Hadoop ecosystem will prevent fragmentation in
>>> this area and further increase the value of Hadoop as a data platform.
>>>
>>> == Current Status ==
>>>
>>> Prototype available, developed by the list of initial committers.
>>>
>>> === Meritocracy ===
>>>
>>> We desire to build a diverse developer community around Gateway following
>>> the Apache Way. We want to make the project open source and will
>> encourage
>>> contributors from multiple organizations following the Apache meritocracy
>>> model.
>>>
>>> === Community ===
>>>
>>> We hope to extend the user and developer base in the future and build a
>>> solid open source community around Gateway. Apache Hadoop has a large
>>> ecosystem of open source projects, each with a strong community of
>>> contributors. All project communities in this ecosystem have an
>> opportunity
>>> to participate in the advancement of the Gateway project because
>>> ultimately, Gateway will enable the security capabilities of their
>> project
>>> to be more enterprise friendly.
>>>
>>> === Core Developers ===
>>>
>>> Gateway is currently being developed by several engineers from
>> Hortonworks
>>> - Kevin Minder, Larry McCay, John Speidel, Tom Beerbower and Sumit
>> Mohanty.
>>> All the engineers have deep expertise in middleware, security & identity
>>> systems and are quite familiar with the Hadoop ecosystem.
>>>
>>> === Alignment ===
>>>
>>> The ASF is a natural host for Gateway given that it is already the home
>> of
>>> Hadoop, Hive, Pig, HBase, Oozie and other emerging big data software
>>> projects. Gateway is designed to solve the security challenges familiar
>> to
>>> the Hadoop ecosystem family of projects.
>>>
>>> == Known Risks ==
>>>
>>> === Orphaned products & Reliance on Salaried Developers ===
>>>
>>> The core developers plan to work full time on the project. We believe
>> that
>>> this project will be of general interest to many Hadoop users and will
>>> attract a diverse set of contributors. We intend to demonstrate this by
>>> having contributors from several organizations recognized as committers
>> by
>>> the time Knox graduates from incubation.
>>>
>>> === Inexperience with Open Source ===
>>>
>>> All of the core developers are active users and followers of open source.
>>> As well, Hortonworks has a strong heritage of success with contributions
>> to
>>> Apache Hadoop Projects.
>>>
>>> === Homogeneous Developers ===
>>>
>>> The current core developers are from Hortonworks, however, we hope to
>>> establish a developer community that includes contributors from several
>>> corporations.
>>>
>>> === Reliance on Salaried Developers ===
>>>
>>> Currently, the developers are paid to do work on Gateway. However, once
>>> the project has a community built around it, we expect to get committers
>>> and developers from outside the current core developers.
>>>
>>> === Relationships with Other Apache Products ===
>>>
>>> Gateway is going to be used by the users and operators of Hadoop, and the
>>> Hadoop ecosystem in general.
>>>
>>> === A Excessive Fascination with the Apache Brand ===
>>>
>>> Our interest in developing Gateway in Apache project is to follow an
>>> established development model, as well since many of the Hadoop ecosystem
>>> projects also are part of Apache, Gateway will complement those projects
>> by
>>> following the same development and contribution model.
>>>
>>> == Documentation ==
>>>
>>> There is documentation in Hortonworks’ internal repositories. These can
>> be
>>> shared upon request and will be transferred into the Apache CM system if
>>> this proposal is accepted.
>>>
>>> == Initial Source ==
>>>
>>> The source is currently in Hortonworks’ internal repositories. The
>> process
>>> of making this GitHub repository public has been started and the URL will
>>> be provided once available.
>>>
>>> == Source and Intellectual Property Submission Plan ==
>>>
>>> The complete Gateway code is under Apache Software License 2.
>>>
>>> == External Dependencies ==
>>>
>>> The Gateway dependencies are listed below, separated by Category A and
>>> Category B as defined in the Apache Third-Party Licensing Policy. Note:
>>> These are the direct dependencies. Indirect dependencies are not
>> included.
>>> === Category A Dependencies ===
>>>
>>> Apache Commons - ASLv2.0
>>> commons-io:commons-io#2.4
>>> commons-cli:commons-cli#1.2
>>> commons-codec:commons-codec#1.**7
>>> org.apache.commons:commons-**digester3#3.2
>>> org.apache.commons:commons-**vfs2#2.0
>>> Apache Hadoop - ASLv2.0
>>> org.apache.hadoop:hadoop-auth#**0.23.3
>>> org.apache.hadoop:hadoop-core#**1.0.3
>>> Apache Geronimo - ASLv2.0
>>> org.apache.geronimo.**components:geronimo-jaspi#2.0.**0
>>> org.apache.geronimo.specs:**geronimo-osgi-locator#1.1
>>> Apache Shiro - ASLv2.0
>>> org.apache.shiro:shiro-web#1.**2.1
>>> ApacheDS - ASLv2.0
>>> org.apache.directory.server:**apacheds-all#1.5.5
>>> Log4J - ASLv2.0
>>> log4j:log4j#1.2.17
>>> SL4J - MIT
>>> org.slf4j:slf4j-api#1.6.6
>>> org.slf4j:slf4j-log4j12#1.6.6
>>> Guava - ASLv2.0
>>> com.google.guava:guava#14.0-**rc1
>>> HttpClient - ASLv2.0
>>> org.apache.httpcomponents:**httpclient#4.2.1
>>> Jetty - ASLv2.0
>>> org.eclipse.jetty:jetty-**server#8.1.7.v20120910
>>> org.eclipse.jetty:jetty-**servlet#8.1.7.v20120910
>>> org.eclipse.jetty:jetty-**webapp#8.1.7.v20120910
>>> org.eclipse.jetty:jetty-jaspi#**8.1.7.v20120910
>>> org.eclipse.jetty.aggregate:**jetty-all#8.1.7.v20120910
>>> org.eclipse.jetty:test-jetty-**servlet#8.1.7.v20120910
>>> Spring Security - ASLv2.0
>>> org.springframework:spring-**core#3.1.3.RELEASE
>>> org.springframework:spring-**context#3.1.3.RELEASE
>>> org.springframework:spring-**web#3.1.3.RELEASE
>>> org.springframework.security:**spring-security-core#3.1.3.**RELEASE
>>> org.springframework.security:**spring-security-web#3.1.3.**RELEASE
>>> org.springframework.security:**spring-security-config#3.1.3.**RELEASE
>>> org.springframework.security:**spring-security-ldap#3.1.2.**RELEASE
>>> org.springframework.ldap:**spring-ldap-core#1.3.1.RELEASE
>>> org.springframework.ldap:**spring-ldap-core-tiger#1.3.1.**RELEASE
>>> org.springframework.ldap:**spring-ldap-odm#1.3.1.RELEASE
>>> org.springframework.ldap:**spring-ldap-ldif-core#1.3.1.**RELEASE
>>> org.springframework.ldap:**spring-ldap-ldif-batch#1.3.1.**RELEASE
>>> JBoss ShrinkWrap - ASLv2.0
>>> org.jboss.shrinkwrap:**shrinkwrap-api#1.0.1
>>> org.jboss.shrinkwrap:**shrinkwrap-impl-base#1.0.1
>>> org.jboss.shrinkwrap.**descriptors:shrinkwrap-**
>>> descriptors-api-javaee#2.0.0-**alpha-4
>>> org.jboss.shrinkwrap.**descriptors:shrinkwrap-**
>>> descriptors-impl-javaee#2.0.0-**alpha-4
>>>
>>> === Category A Dependencies (Test) ===
>>>
>>> EasyMock - ASLv2.0
>>> org.easymock:easymock#3.0
>>> XML Matchers - ASLv2.0
>>> org.xmlmatchers:xml-matchers#**0.10
>>> Hamcrest - BSDv3
>>> org.hamcrest:hamcrest-api#1.0
>>> org.hamcrest:hamcrest-core#1.**2.1
>>> org.hamcrest:hamcrest-library#**1.2.1
>>> JsonPath - ASLv2.0
>>> com.jayway.jsonpath:json-path#**0.8.1
>>> com.jayway.jsonpath:json-path-**assert#0.8.1
>>> XMLTool - ASLv2.0
>>> com.mycila.xmltool:xmltool#3.3
>>> REST-assured - ASLv2.0
>>> com.jayway.restassured:rest-**assured#1.6.2
>>>
>>> === Category B Dependencies ===
>>>
>>> Jersey - CDDLv1.1 or GPL2wCPE
>>> com.sun.jersey:jersey-server#**1.14
>>> com.sun.jersey:jersey-servlet#**1.14
>>> Jerico - EPLv1.0
>>> net.htmlparser.jericho:**jericho-html#3.2
>>> Servlet - CDDLv1.0 or GPLv2
>>> javax.servlet:javax.servlet-**api#3.0.1
>>> JUnit - CPLv1.0
>>> junit:junit#4.11
>>>
>>> == Cryptography ==
>>>
>>> The Gateway uses cryptographic software indirectly as a result of having
>>> two dependencies: ApacheDS and Apache Shiro. Gateway does not include any
>>> special or custom cryptographic technologies.
>>>
>>> ApacheDS is an ASF project and has been classified Export Commodity
>>> Control Number (ECCN) 5D002.C.1 due to it’s dependency on Bouncy Castle.
>>> More information on the ApacheDS classification can be found at
>>> http://svn.apache.org/repos/**asf/directory/apacheds/trunk/**
>>> installers/README<
>> http://svn.apache.org/repos/asf/directory/apacheds/trunk/installers/README
>>>
>>> Apache Shiro is an ASF project and has been classified Export Commodity
>>> Control Number (ECCN) 5D002.C.1. More information on the Apache Shiro
>>> classification can be found at http://svn.apache.org/repos/**
>>> asf/shiro/trunk/README<
>> http://svn.apache.org/repos/asf/shiro/trunk/README>
>>> == Required Resources ==
>>>
>>> === Mailing lists ===
>>>
>>> knox-dev AT incubator DOT apache DOT org
>>> knox-commits AT incubator DOT apache DOT org
>>> knox-user AT hms incubator apache DOT org
>>> knox-private AT incubator DOT apache DOT org
>>>
>>> === Subversion Directory ===
>>>
>>> https://svn.apache.org/repos/**asf/incubator/knox<
>> https://svn.apache.org/repos/asf/incubator/knox>
>>> === Issue Tracking ===
>>>
>>> JIRA Knox (KNOX)
>>>
>>> == Initial Committers ==
>>>
>>> Kevin Minder (kevin DOT minder AT hortonworks DOT com)
>>> Larry McCay (lmccay AT hortonworks DOT com)
>>> John Speidel (jspeidel AT hortonworks DOT com)
>>> Tom Beerbower (tbeerbower AT hortonworks DOT com)
>>> Sumit Mohanty (smohanty AT hortonworks DOT com)
>>>
>>> == Affiliations ==
>>>
>>> Kevin Minder (Hortonworks)
>>> Larry McCay (Hortonworks)
>>> John Speidel (Hortonworks)
>>> Tom Beerbower (Hortonworks)
>>> Sumit Mohanty (Hortonworks)
>>>
>>> == Sponsors ==
>>>
>>> === Champion ===
>>>
>>> Devaraj Das (ddas AT apache DOT org)
>>>
>>> === Nominated Mentors ===
>>>
>>> Owen O’Malley (omalley AT apache DOT org)
>>> Mahadev Konar (mahadev AT apache DOT org)
>>> Alan Gates (gates AT apache DOT org)
>>> Devaraj Das (ddas AT apache DOT org)
>>>
>>> === Sponsoring Entity ===
>>>
>>> Incubator PMC
>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org<
>> general-unsubscribe@incubator.apache.org>
>>> For additional commands, e-mail: general-help@incubator.apache.**org<
>> general-help@incubator.apache.org>
>>>
>>
>> --
>> Best Regards,
>> -- Alex
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Jakob Homan <jg...@gmail.com>.
When do you expect the github to be made available?
-Jakob
On Mon, Feb 11, 2013 at 10:21 AM, Alex Karasulu <ak...@apache.org>wrote:
> Hi Kevin,
>
> This sounds like a much needed project. I endorse the concept but as
> Bertrand pointed out you need a bit more diversity. Otherwise I see no
> problem with moving forward.
>
> Good luck!
>
>
> On Mon, Feb 11, 2013 at 4:55 PM, Kevin Minder
> <ke...@hortonworks.com>wrote:
>
> > Knox Gateway Proposal
> >
> > == Abstract ==
> >
> > Knox Gateway is a system that provides a single point of secure access
> for
> > Apache Hadoop clusters.
> >
> > == Proposal ==
> >
> > The Knox Gateway (“Gateway” or “Knox”) is a system that provides a single
> > point of authentication and access for Apache Hadoop services in a
> cluster.
> > The goal is to simplify Hadoop security for both users (i.e. who access
> the
> > cluster data and execute jobs) and operators (i.e. who control access and
> > manage the cluster). The Gateway runs as a server (or cluster of servers)
> > that serve one or more Hadoop clusters.
> >
> > Provide perimeter security to make Hadoop security setup easier
> > Support authentication and token verification security scenarios
> > Deliver users a single cluster end-point that aggregates capabilities for
> > data and jobs
> > Enable integration with enterprise and cloud identity management
> > environments
> >
> > == Background ==
> >
> > An Apache Hadoop cluster is presented to consumers as a loose collection
> > of independent services. This makes it difficult for users to interact
> with
> > Hadoop since each service maintains it’s own method of access and
> security.
> > As well, for operators, configuration and administration of a secure
> Hadoop
> > cluster is a complex and many Hadoop clusters are insecure as a result.
> >
> > == Rationale ==
> >
> > Organizations that are struggling with Hadoop cluster security result in
> > a) running Hadoop without security or b) slowing adoption of Hadoop. The
> > Gateway aims to provide perimeter security that integrates more easily
> into
> > existing organizations’ security infrastructure. Doing so will simplify
> > security for these organizations and benefit all Hadoop stakeholders
> (i.e.
> > users and operators). Additionally, making a dedicated perimeter security
> > project part of the Apache Hadoop ecosystem will prevent fragmentation in
> > this area and further increase the value of Hadoop as a data platform.
> >
> > == Current Status ==
> >
> > Prototype available, developed by the list of initial committers.
> >
> > === Meritocracy ===
> >
> > We desire to build a diverse developer community around Gateway following
> > the Apache Way. We want to make the project open source and will
> encourage
> > contributors from multiple organizations following the Apache meritocracy
> > model.
> >
> > === Community ===
> >
> > We hope to extend the user and developer base in the future and build a
> > solid open source community around Gateway. Apache Hadoop has a large
> > ecosystem of open source projects, each with a strong community of
> > contributors. All project communities in this ecosystem have an
> opportunity
> > to participate in the advancement of the Gateway project because
> > ultimately, Gateway will enable the security capabilities of their
> project
> > to be more enterprise friendly.
> >
> > === Core Developers ===
> >
> > Gateway is currently being developed by several engineers from
> Hortonworks
> > - Kevin Minder, Larry McCay, John Speidel, Tom Beerbower and Sumit
> Mohanty.
> > All the engineers have deep expertise in middleware, security & identity
> > systems and are quite familiar with the Hadoop ecosystem.
> >
> > === Alignment ===
> >
> > The ASF is a natural host for Gateway given that it is already the home
> of
> > Hadoop, Hive, Pig, HBase, Oozie and other emerging big data software
> > projects. Gateway is designed to solve the security challenges familiar
> to
> > the Hadoop ecosystem family of projects.
> >
> > == Known Risks ==
> >
> > === Orphaned products & Reliance on Salaried Developers ===
> >
> > The core developers plan to work full time on the project. We believe
> that
> > this project will be of general interest to many Hadoop users and will
> > attract a diverse set of contributors. We intend to demonstrate this by
> > having contributors from several organizations recognized as committers
> by
> > the time Knox graduates from incubation.
> >
> > === Inexperience with Open Source ===
> >
> > All of the core developers are active users and followers of open source.
> > As well, Hortonworks has a strong heritage of success with contributions
> to
> > Apache Hadoop Projects.
> >
> > === Homogeneous Developers ===
> >
> > The current core developers are from Hortonworks, however, we hope to
> > establish a developer community that includes contributors from several
> > corporations.
> >
> > === Reliance on Salaried Developers ===
> >
> > Currently, the developers are paid to do work on Gateway. However, once
> > the project has a community built around it, we expect to get committers
> > and developers from outside the current core developers.
> >
> > === Relationships with Other Apache Products ===
> >
> > Gateway is going to be used by the users and operators of Hadoop, and the
> > Hadoop ecosystem in general.
> >
> > === A Excessive Fascination with the Apache Brand ===
> >
> > Our interest in developing Gateway in Apache project is to follow an
> > established development model, as well since many of the Hadoop ecosystem
> > projects also are part of Apache, Gateway will complement those projects
> by
> > following the same development and contribution model.
> >
> > == Documentation ==
> >
> > There is documentation in Hortonworks’ internal repositories. These can
> be
> > shared upon request and will be transferred into the Apache CM system if
> > this proposal is accepted.
> >
> > == Initial Source ==
> >
> > The source is currently in Hortonworks’ internal repositories. The
> process
> > of making this GitHub repository public has been started and the URL will
> > be provided once available.
> >
> > == Source and Intellectual Property Submission Plan ==
> >
> > The complete Gateway code is under Apache Software License 2.
> >
> > == External Dependencies ==
> >
> > The Gateway dependencies are listed below, separated by Category A and
> > Category B as defined in the Apache Third-Party Licensing Policy. Note:
> > These are the direct dependencies. Indirect dependencies are not
> included.
> >
> > === Category A Dependencies ===
> >
> > Apache Commons - ASLv2.0
> > commons-io:commons-io#2.4
> > commons-cli:commons-cli#1.2
> > commons-codec:commons-codec#1.**7
> > org.apache.commons:commons-**digester3#3.2
> > org.apache.commons:commons-**vfs2#2.0
> > Apache Hadoop - ASLv2.0
> > org.apache.hadoop:hadoop-auth#**0.23.3
> > org.apache.hadoop:hadoop-core#**1.0.3
> > Apache Geronimo - ASLv2.0
> > org.apache.geronimo.**components:geronimo-jaspi#2.0.**0
> > org.apache.geronimo.specs:**geronimo-osgi-locator#1.1
> > Apache Shiro - ASLv2.0
> > org.apache.shiro:shiro-web#1.**2.1
> > ApacheDS - ASLv2.0
> > org.apache.directory.server:**apacheds-all#1.5.5
> > Log4J - ASLv2.0
> > log4j:log4j#1.2.17
> > SL4J - MIT
> > org.slf4j:slf4j-api#1.6.6
> > org.slf4j:slf4j-log4j12#1.6.6
> > Guava - ASLv2.0
> > com.google.guava:guava#14.0-**rc1
> > HttpClient - ASLv2.0
> > org.apache.httpcomponents:**httpclient#4.2.1
> > Jetty - ASLv2.0
> > org.eclipse.jetty:jetty-**server#8.1.7.v20120910
> > org.eclipse.jetty:jetty-**servlet#8.1.7.v20120910
> > org.eclipse.jetty:jetty-**webapp#8.1.7.v20120910
> > org.eclipse.jetty:jetty-jaspi#**8.1.7.v20120910
> > org.eclipse.jetty.aggregate:**jetty-all#8.1.7.v20120910
> > org.eclipse.jetty:test-jetty-**servlet#8.1.7.v20120910
> > Spring Security - ASLv2.0
> > org.springframework:spring-**core#3.1.3.RELEASE
> > org.springframework:spring-**context#3.1.3.RELEASE
> > org.springframework:spring-**web#3.1.3.RELEASE
> > org.springframework.security:**spring-security-core#3.1.3.**RELEASE
> > org.springframework.security:**spring-security-web#3.1.3.**RELEASE
> > org.springframework.security:**spring-security-config#3.1.3.**RELEASE
> > org.springframework.security:**spring-security-ldap#3.1.2.**RELEASE
> > org.springframework.ldap:**spring-ldap-core#1.3.1.RELEASE
> > org.springframework.ldap:**spring-ldap-core-tiger#1.3.1.**RELEASE
> > org.springframework.ldap:**spring-ldap-odm#1.3.1.RELEASE
> > org.springframework.ldap:**spring-ldap-ldif-core#1.3.1.**RELEASE
> > org.springframework.ldap:**spring-ldap-ldif-batch#1.3.1.**RELEASE
> > JBoss ShrinkWrap - ASLv2.0
> > org.jboss.shrinkwrap:**shrinkwrap-api#1.0.1
> > org.jboss.shrinkwrap:**shrinkwrap-impl-base#1.0.1
> > org.jboss.shrinkwrap.**descriptors:shrinkwrap-**
> > descriptors-api-javaee#2.0.0-**alpha-4
> > org.jboss.shrinkwrap.**descriptors:shrinkwrap-**
> > descriptors-impl-javaee#2.0.0-**alpha-4
> >
> > === Category A Dependencies (Test) ===
> >
> > EasyMock - ASLv2.0
> > org.easymock:easymock#3.0
> > XML Matchers - ASLv2.0
> > org.xmlmatchers:xml-matchers#**0.10
> > Hamcrest - BSDv3
> > org.hamcrest:hamcrest-api#1.0
> > org.hamcrest:hamcrest-core#1.**2.1
> > org.hamcrest:hamcrest-library#**1.2.1
> > JsonPath - ASLv2.0
> > com.jayway.jsonpath:json-path#**0.8.1
> > com.jayway.jsonpath:json-path-**assert#0.8.1
> > XMLTool - ASLv2.0
> > com.mycila.xmltool:xmltool#3.3
> > REST-assured - ASLv2.0
> > com.jayway.restassured:rest-**assured#1.6.2
> >
> > === Category B Dependencies ===
> >
> > Jersey - CDDLv1.1 or GPL2wCPE
> > com.sun.jersey:jersey-server#**1.14
> > com.sun.jersey:jersey-servlet#**1.14
> > Jerico - EPLv1.0
> > net.htmlparser.jericho:**jericho-html#3.2
> > Servlet - CDDLv1.0 or GPLv2
> > javax.servlet:javax.servlet-**api#3.0.1
> > JUnit - CPLv1.0
> > junit:junit#4.11
> >
> > == Cryptography ==
> >
> > The Gateway uses cryptographic software indirectly as a result of having
> > two dependencies: ApacheDS and Apache Shiro. Gateway does not include any
> > special or custom cryptographic technologies.
> >
> > ApacheDS is an ASF project and has been classified Export Commodity
> > Control Number (ECCN) 5D002.C.1 due to it’s dependency on Bouncy Castle.
> > More information on the ApacheDS classification can be found at
> > http://svn.apache.org/repos/**asf/directory/apacheds/trunk/**
> > installers/README<
> http://svn.apache.org/repos/asf/directory/apacheds/trunk/installers/README
> >
> >
> > Apache Shiro is an ASF project and has been classified Export Commodity
> > Control Number (ECCN) 5D002.C.1. More information on the Apache Shiro
> > classification can be found at http://svn.apache.org/repos/**
> > asf/shiro/trunk/README<
> http://svn.apache.org/repos/asf/shiro/trunk/README>
> >
> > == Required Resources ==
> >
> > === Mailing lists ===
> >
> > knox-dev AT incubator DOT apache DOT org
> > knox-commits AT incubator DOT apache DOT org
> > knox-user AT hms incubator apache DOT org
> > knox-private AT incubator DOT apache DOT org
> >
> > === Subversion Directory ===
> >
> > https://svn.apache.org/repos/**asf/incubator/knox<
> https://svn.apache.org/repos/asf/incubator/knox>
> >
> > === Issue Tracking ===
> >
> > JIRA Knox (KNOX)
> >
> > == Initial Committers ==
> >
> > Kevin Minder (kevin DOT minder AT hortonworks DOT com)
> > Larry McCay (lmccay AT hortonworks DOT com)
> > John Speidel (jspeidel AT hortonworks DOT com)
> > Tom Beerbower (tbeerbower AT hortonworks DOT com)
> > Sumit Mohanty (smohanty AT hortonworks DOT com)
> >
> > == Affiliations ==
> >
> > Kevin Minder (Hortonworks)
> > Larry McCay (Hortonworks)
> > John Speidel (Hortonworks)
> > Tom Beerbower (Hortonworks)
> > Sumit Mohanty (Hortonworks)
> >
> > == Sponsors ==
> >
> > === Champion ===
> >
> > Devaraj Das (ddas AT apache DOT org)
> >
> > === Nominated Mentors ===
> >
> > Owen O’Malley (omalley AT apache DOT org)
> > Mahadev Konar (mahadev AT apache DOT org)
> > Alan Gates (gates AT apache DOT org)
> > Devaraj Das (ddas AT apache DOT org)
> >
> > === Sponsoring Entity ===
> >
> > Incubator PMC
> >
> > ------------------------------**------------------------------**---------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org<
> general-unsubscribe@incubator.apache.org>
> > For additional commands, e-mail: general-help@incubator.apache.**org<
> general-help@incubator.apache.org>
> >
> >
>
>
> --
> Best Regards,
> -- Alex
>
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Alex Karasulu <ak...@apache.org>.
Hi Kevin,
This sounds like a much needed project. I endorse the concept but as
Bertrand pointed out you need a bit more diversity. Otherwise I see no
problem with moving forward.
Good luck!
On Mon, Feb 11, 2013 at 4:55 PM, Kevin Minder
<ke...@hortonworks.com>wrote:
> Knox Gateway Proposal
>
> == Abstract ==
>
> Knox Gateway is a system that provides a single point of secure access for
> Apache Hadoop clusters.
>
> == Proposal ==
>
> The Knox Gateway (“Gateway” or “Knox”) is a system that provides a single
> point of authentication and access for Apache Hadoop services in a cluster.
> The goal is to simplify Hadoop security for both users (i.e. who access the
> cluster data and execute jobs) and operators (i.e. who control access and
> manage the cluster). The Gateway runs as a server (or cluster of servers)
> that serve one or more Hadoop clusters.
>
> Provide perimeter security to make Hadoop security setup easier
> Support authentication and token verification security scenarios
> Deliver users a single cluster end-point that aggregates capabilities for
> data and jobs
> Enable integration with enterprise and cloud identity management
> environments
>
> == Background ==
>
> An Apache Hadoop cluster is presented to consumers as a loose collection
> of independent services. This makes it difficult for users to interact with
> Hadoop since each service maintains it’s own method of access and security.
> As well, for operators, configuration and administration of a secure Hadoop
> cluster is a complex and many Hadoop clusters are insecure as a result.
>
> == Rationale ==
>
> Organizations that are struggling with Hadoop cluster security result in
> a) running Hadoop without security or b) slowing adoption of Hadoop. The
> Gateway aims to provide perimeter security that integrates more easily into
> existing organizations’ security infrastructure. Doing so will simplify
> security for these organizations and benefit all Hadoop stakeholders (i.e.
> users and operators). Additionally, making a dedicated perimeter security
> project part of the Apache Hadoop ecosystem will prevent fragmentation in
> this area and further increase the value of Hadoop as a data platform.
>
> == Current Status ==
>
> Prototype available, developed by the list of initial committers.
>
> === Meritocracy ===
>
> We desire to build a diverse developer community around Gateway following
> the Apache Way. We want to make the project open source and will encourage
> contributors from multiple organizations following the Apache meritocracy
> model.
>
> === Community ===
>
> We hope to extend the user and developer base in the future and build a
> solid open source community around Gateway. Apache Hadoop has a large
> ecosystem of open source projects, each with a strong community of
> contributors. All project communities in this ecosystem have an opportunity
> to participate in the advancement of the Gateway project because
> ultimately, Gateway will enable the security capabilities of their project
> to be more enterprise friendly.
>
> === Core Developers ===
>
> Gateway is currently being developed by several engineers from Hortonworks
> - Kevin Minder, Larry McCay, John Speidel, Tom Beerbower and Sumit Mohanty.
> All the engineers have deep expertise in middleware, security & identity
> systems and are quite familiar with the Hadoop ecosystem.
>
> === Alignment ===
>
> The ASF is a natural host for Gateway given that it is already the home of
> Hadoop, Hive, Pig, HBase, Oozie and other emerging big data software
> projects. Gateway is designed to solve the security challenges familiar to
> the Hadoop ecosystem family of projects.
>
> == Known Risks ==
>
> === Orphaned products & Reliance on Salaried Developers ===
>
> The core developers plan to work full time on the project. We believe that
> this project will be of general interest to many Hadoop users and will
> attract a diverse set of contributors. We intend to demonstrate this by
> having contributors from several organizations recognized as committers by
> the time Knox graduates from incubation.
>
> === Inexperience with Open Source ===
>
> All of the core developers are active users and followers of open source.
> As well, Hortonworks has a strong heritage of success with contributions to
> Apache Hadoop Projects.
>
> === Homogeneous Developers ===
>
> The current core developers are from Hortonworks, however, we hope to
> establish a developer community that includes contributors from several
> corporations.
>
> === Reliance on Salaried Developers ===
>
> Currently, the developers are paid to do work on Gateway. However, once
> the project has a community built around it, we expect to get committers
> and developers from outside the current core developers.
>
> === Relationships with Other Apache Products ===
>
> Gateway is going to be used by the users and operators of Hadoop, and the
> Hadoop ecosystem in general.
>
> === A Excessive Fascination with the Apache Brand ===
>
> Our interest in developing Gateway in Apache project is to follow an
> established development model, as well since many of the Hadoop ecosystem
> projects also are part of Apache, Gateway will complement those projects by
> following the same development and contribution model.
>
> == Documentation ==
>
> There is documentation in Hortonworks’ internal repositories. These can be
> shared upon request and will be transferred into the Apache CM system if
> this proposal is accepted.
>
> == Initial Source ==
>
> The source is currently in Hortonworks’ internal repositories. The process
> of making this GitHub repository public has been started and the URL will
> be provided once available.
>
> == Source and Intellectual Property Submission Plan ==
>
> The complete Gateway code is under Apache Software License 2.
>
> == External Dependencies ==
>
> The Gateway dependencies are listed below, separated by Category A and
> Category B as defined in the Apache Third-Party Licensing Policy. Note:
> These are the direct dependencies. Indirect dependencies are not included.
>
> === Category A Dependencies ===
>
> Apache Commons - ASLv2.0
> commons-io:commons-io#2.4
> commons-cli:commons-cli#1.2
> commons-codec:commons-codec#1.**7
> org.apache.commons:commons-**digester3#3.2
> org.apache.commons:commons-**vfs2#2.0
> Apache Hadoop - ASLv2.0
> org.apache.hadoop:hadoop-auth#**0.23.3
> org.apache.hadoop:hadoop-core#**1.0.3
> Apache Geronimo - ASLv2.0
> org.apache.geronimo.**components:geronimo-jaspi#2.0.**0
> org.apache.geronimo.specs:**geronimo-osgi-locator#1.1
> Apache Shiro - ASLv2.0
> org.apache.shiro:shiro-web#1.**2.1
> ApacheDS - ASLv2.0
> org.apache.directory.server:**apacheds-all#1.5.5
> Log4J - ASLv2.0
> log4j:log4j#1.2.17
> SL4J - MIT
> org.slf4j:slf4j-api#1.6.6
> org.slf4j:slf4j-log4j12#1.6.6
> Guava - ASLv2.0
> com.google.guava:guava#14.0-**rc1
> HttpClient - ASLv2.0
> org.apache.httpcomponents:**httpclient#4.2.1
> Jetty - ASLv2.0
> org.eclipse.jetty:jetty-**server#8.1.7.v20120910
> org.eclipse.jetty:jetty-**servlet#8.1.7.v20120910
> org.eclipse.jetty:jetty-**webapp#8.1.7.v20120910
> org.eclipse.jetty:jetty-jaspi#**8.1.7.v20120910
> org.eclipse.jetty.aggregate:**jetty-all#8.1.7.v20120910
> org.eclipse.jetty:test-jetty-**servlet#8.1.7.v20120910
> Spring Security - ASLv2.0
> org.springframework:spring-**core#3.1.3.RELEASE
> org.springframework:spring-**context#3.1.3.RELEASE
> org.springframework:spring-**web#3.1.3.RELEASE
> org.springframework.security:**spring-security-core#3.1.3.**RELEASE
> org.springframework.security:**spring-security-web#3.1.3.**RELEASE
> org.springframework.security:**spring-security-config#3.1.3.**RELEASE
> org.springframework.security:**spring-security-ldap#3.1.2.**RELEASE
> org.springframework.ldap:**spring-ldap-core#1.3.1.RELEASE
> org.springframework.ldap:**spring-ldap-core-tiger#1.3.1.**RELEASE
> org.springframework.ldap:**spring-ldap-odm#1.3.1.RELEASE
> org.springframework.ldap:**spring-ldap-ldif-core#1.3.1.**RELEASE
> org.springframework.ldap:**spring-ldap-ldif-batch#1.3.1.**RELEASE
> JBoss ShrinkWrap - ASLv2.0
> org.jboss.shrinkwrap:**shrinkwrap-api#1.0.1
> org.jboss.shrinkwrap:**shrinkwrap-impl-base#1.0.1
> org.jboss.shrinkwrap.**descriptors:shrinkwrap-**
> descriptors-api-javaee#2.0.0-**alpha-4
> org.jboss.shrinkwrap.**descriptors:shrinkwrap-**
> descriptors-impl-javaee#2.0.0-**alpha-4
>
> === Category A Dependencies (Test) ===
>
> EasyMock - ASLv2.0
> org.easymock:easymock#3.0
> XML Matchers - ASLv2.0
> org.xmlmatchers:xml-matchers#**0.10
> Hamcrest - BSDv3
> org.hamcrest:hamcrest-api#1.0
> org.hamcrest:hamcrest-core#1.**2.1
> org.hamcrest:hamcrest-library#**1.2.1
> JsonPath - ASLv2.0
> com.jayway.jsonpath:json-path#**0.8.1
> com.jayway.jsonpath:json-path-**assert#0.8.1
> XMLTool - ASLv2.0
> com.mycila.xmltool:xmltool#3.3
> REST-assured - ASLv2.0
> com.jayway.restassured:rest-**assured#1.6.2
>
> === Category B Dependencies ===
>
> Jersey - CDDLv1.1 or GPL2wCPE
> com.sun.jersey:jersey-server#**1.14
> com.sun.jersey:jersey-servlet#**1.14
> Jerico - EPLv1.0
> net.htmlparser.jericho:**jericho-html#3.2
> Servlet - CDDLv1.0 or GPLv2
> javax.servlet:javax.servlet-**api#3.0.1
> JUnit - CPLv1.0
> junit:junit#4.11
>
> == Cryptography ==
>
> The Gateway uses cryptographic software indirectly as a result of having
> two dependencies: ApacheDS and Apache Shiro. Gateway does not include any
> special or custom cryptographic technologies.
>
> ApacheDS is an ASF project and has been classified Export Commodity
> Control Number (ECCN) 5D002.C.1 due to it’s dependency on Bouncy Castle.
> More information on the ApacheDS classification can be found at
> http://svn.apache.org/repos/**asf/directory/apacheds/trunk/**
> installers/README<http://svn.apache.org/repos/asf/directory/apacheds/trunk/installers/README>
>
> Apache Shiro is an ASF project and has been classified Export Commodity
> Control Number (ECCN) 5D002.C.1. More information on the Apache Shiro
> classification can be found at http://svn.apache.org/repos/**
> asf/shiro/trunk/README<http://svn.apache.org/repos/asf/shiro/trunk/README>
>
> == Required Resources ==
>
> === Mailing lists ===
>
> knox-dev AT incubator DOT apache DOT org
> knox-commits AT incubator DOT apache DOT org
> knox-user AT hms incubator apache DOT org
> knox-private AT incubator DOT apache DOT org
>
> === Subversion Directory ===
>
> https://svn.apache.org/repos/**asf/incubator/knox<https://svn.apache.org/repos/asf/incubator/knox>
>
> === Issue Tracking ===
>
> JIRA Knox (KNOX)
>
> == Initial Committers ==
>
> Kevin Minder (kevin DOT minder AT hortonworks DOT com)
> Larry McCay (lmccay AT hortonworks DOT com)
> John Speidel (jspeidel AT hortonworks DOT com)
> Tom Beerbower (tbeerbower AT hortonworks DOT com)
> Sumit Mohanty (smohanty AT hortonworks DOT com)
>
> == Affiliations ==
>
> Kevin Minder (Hortonworks)
> Larry McCay (Hortonworks)
> John Speidel (Hortonworks)
> Tom Beerbower (Hortonworks)
> Sumit Mohanty (Hortonworks)
>
> == Sponsors ==
>
> === Champion ===
>
> Devaraj Das (ddas AT apache DOT org)
>
> === Nominated Mentors ===
>
> Owen O’Malley (omalley AT apache DOT org)
> Mahadev Konar (mahadev AT apache DOT org)
> Alan Gates (gates AT apache DOT org)
> Devaraj Das (ddas AT apache DOT org)
>
> === Sponsoring Entity ===
>
> Incubator PMC
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org<ge...@incubator.apache.org>
> For additional commands, e-mail: general-help@incubator.apache.**org<ge...@incubator.apache.org>
>
>
--
Best Regards,
-- Alex
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Alex Karasulu <ak...@apache.org>.
I thought about this a bit last night. If y'all are interested I too could
also mentor the project. That should add some diversity to the mentors
list. I see value in it and would like to see this community succeed.
I'm not affiliated with any company.
On Mon, Feb 11, 2013 at 9:23 PM, Eric Sammer <es...@cloudera.com> wrote:
> Kevin:
>
> Makes complete sense.
>
> I'd like to offer to join the project, if it's accepted for incubation. I'm
> a committer on MRUnit and Flume, and on the PMC for both. I've helped both
> projects through the incubation phase, and I also know a little bit about
> this Hadoop thing. ;)
>
> Thanks!
>
>
> On Mon, Feb 11, 2013 at 9:28 AM, Kevin Minder
> <ke...@hortonworks.com>wrote:
>
> > Hi Eric,
> > Let me answer your second question first.
> >
> > Q: Is it your intention to provide job submissions and data ingestion
> APIs
> > for MR and HDFS, respectively?
> > A: Yes we plan to progress the project to cover all existing ecosystem
> > projects. In addition the project is based on a modular framework that
> > allows for each extension to cover services that are either new or
> > proprietary. Certainly there exist very high volume data ingest use
> cases
> > for which using a gateway may be impractical but in general the idea is
> to
> > support all required client interaction with Hadoop via the gateway.
> >
> > Now for your first question...
> >
> > Q: Can you explain a bit more about what the target use case is?
> > A: One typical use case will be that the gateway will run in a DMW. It
> > will as you say be integrations with various directory services and is
> > extensible to cover those not included. The gateway will then propagate
> > the identity into the Hadoop cluster using Hadoop specific mechanisms.
> The
> > key point is that there will typically be a single port open on the
> client
> > side to the gateway. The Hadoop cluster is firewalled, only providing
> > access to the Hadoop services to the gateway instances.
> > A: Another use case is that an organization is already using some SSO
> > solution and the gateway would be integrated with that to verify any SSO
> > token and then propagate the identity to the Hadoop services.
> >
> > I will collect this and add it to the proposal wiki once I have privs to
> > create the page.
> >
> > Thanks!
> > Kevin.
> >
> >
> > On 2/11/13 12:03 PM, Eric Sammer wrote:
> >
> >> Kevin:
> >>
> >> Interesting proposal. Can you explain a bit more about what the target
> use
> >> case is? It sounds like there's SSO-ish functionality (presumably a
> doAs()
> >> machine) with integration with directory services, but the proposal also
> >> mentions a single point for "data and jobs." Is it your intention to
> >> provide job submissions and data ingestion APIs for MR and HDFS,
> >> respectively? Do you plan to target other ecosystem projects such as
> >> HBase?
> >> Sorry if I missed this in the proposal.
> >>
> >> Thanks!
> >>
> >>
> >> On Mon, Feb 11, 2013 at 6:55 AM, Kevin Minder
> >> <ke...@hortonworks.com>**wrote:
> >>
> >> Knox Gateway Proposal
> >>>
> >>> == Abstract ==
> >>>
> >>> Knox Gateway is a system that provides a single point of secure access
> >>> for
> >>> Apache Hadoop clusters.
> >>>
> >>> == Proposal ==
> >>>
> >>> The Knox Gateway (“Gateway” or “Knox”) is a system that provides a
> single
> >>> point of authentication and access for Apache Hadoop services in a
> >>> cluster.
> >>> The goal is to simplify Hadoop security for both users (i.e. who access
> >>> the
> >>> cluster data and execute jobs) and operators (i.e. who control access
> and
> >>> manage the cluster). The Gateway runs as a server (or cluster of
> servers)
> >>> that serve one or more Hadoop clusters.
> >>>
> >>> Provide perimeter security to make Hadoop security setup easier
> >>> Support authentication and token verification security scenarios
> >>> Deliver users a single cluster end-point that aggregates capabilities
> for
> >>> data and jobs
> >>> Enable integration with enterprise and cloud identity management
> >>> environments
> >>>
> >>> == Background ==
> >>>
> >>> An Apache Hadoop cluster is presented to consumers as a loose
> collection
> >>> of independent services. This makes it difficult for users to interact
> >>> with
> >>> Hadoop since each service maintains it’s own method of access and
> >>> security.
> >>> As well, for operators, configuration and administration of a secure
> >>> Hadoop
> >>> cluster is a complex and many Hadoop clusters are insecure as a result.
> >>>
> >>> == Rationale ==
> >>>
> >>> Organizations that are struggling with Hadoop cluster security result
> in
> >>> a) running Hadoop without security or b) slowing adoption of Hadoop.
> The
> >>> Gateway aims to provide perimeter security that integrates more easily
> >>> into
> >>> existing organizations’ security infrastructure. Doing so will simplify
> >>> security for these organizations and benefit all Hadoop stakeholders
> >>> (i.e.
> >>> users and operators). Additionally, making a dedicated perimeter
> security
> >>> project part of the Apache Hadoop ecosystem will prevent fragmentation
> in
> >>> this area and further increase the value of Hadoop as a data platform.
> >>>
> >>> == Current Status ==
> >>>
> >>> Prototype available, developed by the list of initial committers.
> >>>
> >>> === Meritocracy ===
> >>>
> >>> We desire to build a diverse developer community around Gateway
> following
> >>> the Apache Way. We want to make the project open source and will
> >>> encourage
> >>> contributors from multiple organizations following the Apache
> meritocracy
> >>> model.
> >>>
> >>> === Community ===
> >>>
> >>> We hope to extend the user and developer base in the future and build a
> >>> solid open source community around Gateway. Apache Hadoop has a large
> >>> ecosystem of open source projects, each with a strong community of
> >>> contributors. All project communities in this ecosystem have an
> >>> opportunity
> >>> to participate in the advancement of the Gateway project because
> >>> ultimately, Gateway will enable the security capabilities of their
> >>> project
> >>> to be more enterprise friendly.
> >>>
> >>> === Core Developers ===
> >>>
> >>> Gateway is currently being developed by several engineers from
> >>> Hortonworks
> >>> - Kevin Minder, Larry McCay, John Speidel, Tom Beerbower and Sumit
> >>> Mohanty.
> >>> All the engineers have deep expertise in middleware, security &
> identity
> >>> systems and are quite familiar with the Hadoop ecosystem.
> >>>
> >>> === Alignment ===
> >>>
> >>> The ASF is a natural host for Gateway given that it is already the home
> >>> of
> >>> Hadoop, Hive, Pig, HBase, Oozie and other emerging big data software
> >>> projects. Gateway is designed to solve the security challenges familiar
> >>> to
> >>> the Hadoop ecosystem family of projects.
> >>>
> >>> == Known Risks ==
> >>>
> >>> === Orphaned products & Reliance on Salaried Developers ===
> >>>
> >>> The core developers plan to work full time on the project. We believe
> >>> that
> >>> this project will be of general interest to many Hadoop users and will
> >>> attract a diverse set of contributors. We intend to demonstrate this by
> >>> having contributors from several organizations recognized as committers
> >>> by
> >>> the time Knox graduates from incubation.
> >>>
> >>> === Inexperience with Open Source ===
> >>>
> >>> All of the core developers are active users and followers of open
> source.
> >>> As well, Hortonworks has a strong heritage of success with
> contributions
> >>> to
> >>> Apache Hadoop Projects.
> >>>
> >>> === Homogeneous Developers ===
> >>>
> >>> The current core developers are from Hortonworks, however, we hope to
> >>> establish a developer community that includes contributors from several
> >>> corporations.
> >>>
> >>> === Reliance on Salaried Developers ===
> >>>
> >>> Currently, the developers are paid to do work on Gateway. However, once
> >>> the project has a community built around it, we expect to get
> committers
> >>> and developers from outside the current core developers.
> >>>
> >>> === Relationships with Other Apache Products ===
> >>>
> >>> Gateway is going to be used by the users and operators of Hadoop, and
> the
> >>> Hadoop ecosystem in general.
> >>>
> >>> === A Excessive Fascination with the Apache Brand ===
> >>>
> >>> Our interest in developing Gateway in Apache project is to follow an
> >>> established development model, as well since many of the Hadoop
> ecosystem
> >>> projects also are part of Apache, Gateway will complement those
> projects
> >>> by
> >>> following the same development and contribution model.
> >>>
> >>> == Documentation ==
> >>>
> >>> There is documentation in Hortonworks’ internal repositories. These can
> >>> be
> >>> shared upon request and will be transferred into the Apache CM system
> if
> >>> this proposal is accepted.
> >>>
> >>> == Initial Source ==
> >>>
> >>> The source is currently in Hortonworks’ internal repositories. The
> >>> process
> >>> of making this GitHub repository public has been started and the URL
> will
> >>> be provided once available.
> >>>
> >>> == Source and Intellectual Property Submission Plan ==
> >>>
> >>> The complete Gateway code is under Apache Software License 2.
> >>>
> >>> == External Dependencies ==
> >>>
> >>> The Gateway dependencies are listed below, separated by Category A and
> >>> Category B as defined in the Apache Third-Party Licensing Policy. Note:
> >>> These are the direct dependencies. Indirect dependencies are not
> >>> included.
> >>>
> >>> === Category A Dependencies ===
> >>>
> >>> Apache Commons - ASLv2.0
> >>> commons-io:commons-io#2.4
> >>> commons-cli:commons-cli#1.2
> >>> commons-codec:commons-codec#1.****7
> >>> org.apache.commons:commons-****digester3#3.2
> >>> org.apache.commons:commons-****vfs2#2.0
> >>> Apache Hadoop - ASLv2.0
> >>> org.apache.hadoop:hadoop-auth#****0.23.3
> >>> org.apache.hadoop:hadoop-core#****1.0.3
> >>> Apache Geronimo - ASLv2.0
> >>> org.apache.geronimo.****components:geronimo-jaspi#2.0.****0
> >>> org.apache.geronimo.specs:****geronimo-osgi-locator#1.1
> >>> Apache Shiro - ASLv2.0
> >>> org.apache.shiro:shiro-web#1.****2.1
> >>> ApacheDS - ASLv2.0
> >>> org.apache.directory.server:****apacheds-all#1.5.5
> >>>
> >>> Log4J - ASLv2.0
> >>> log4j:log4j#1.2.17
> >>> SL4J - MIT
> >>> org.slf4j:slf4j-api#1.6.6
> >>> org.slf4j:slf4j-log4j12#1.6.6
> >>> Guava - ASLv2.0
> >>> com.google.guava:guava#14.0-****rc1
> >>> HttpClient - ASLv2.0
> >>> org.apache.httpcomponents:****httpclient#4.2.1
> >>> Jetty - ASLv2.0
> >>> org.eclipse.jetty:jetty-****server#8.1.7.v20120910
> >>> org.eclipse.jetty:jetty-****servlet#8.1.7.v20120910
> >>> org.eclipse.jetty:jetty-****webapp#8.1.7.v20120910
> >>> org.eclipse.jetty:jetty-jaspi#****8.1.7.v20120910
> >>> org.eclipse.jetty.aggregate:****jetty-all#8.1.7.v20120910
> >>> org.eclipse.jetty:test-jetty-****servlet#8.1.7.v20120910
> >>> Spring Security - ASLv2.0
> >>> org.springframework:spring-****core#3.1.3.RELEASE
> >>> org.springframework:spring-****context#3.1.3.RELEASE
> >>> org.springframework:spring-****web#3.1.3.RELEASE
> >>> org.springframework.security:****spring-security-core#3.1.3.****RELEASE
> >>> org.springframework.security:****spring-security-web#3.1.3.****RELEASE
> >>> org.springframework.security:****spring-security-config#3.1.3.**
> >>> **RELEASE
> >>> org.springframework.security:****spring-security-ldap#3.1.2.****RELEASE
> >>> org.springframework.ldap:****spring-ldap-core#1.3.1.RELEASE
> >>> org.springframework.ldap:****spring-ldap-core-tiger#1.3.1.****RELEASE
> >>> org.springframework.ldap:****spring-ldap-odm#1.3.1.RELEASE
> >>> org.springframework.ldap:****spring-ldap-ldif-core#1.3.1.****RELEASE
> >>> org.springframework.ldap:****spring-ldap-ldif-batch#1.3.1.****RELEASE
> >>> JBoss ShrinkWrap - ASLv2.0
> >>> org.jboss.shrinkwrap:****shrinkwrap-api#1.0.1
> >>> org.jboss.shrinkwrap:****shrinkwrap-impl-base#1.0.1
> >>> org.jboss.shrinkwrap.****descriptors:shrinkwrap-**
> >>> descriptors-api-javaee#2.0.0-****alpha-4
> >>> org.jboss.shrinkwrap.****descriptors:shrinkwrap-**
> >>> descriptors-impl-javaee#2.0.0-****alpha-4
> >>>
> >>>
> >>> === Category A Dependencies (Test) ===
> >>>
> >>> EasyMock - ASLv2.0
> >>> org.easymock:easymock#3.0
> >>> XML Matchers - ASLv2.0
> >>> org.xmlmatchers:xml-matchers#****0.10
> >>>
> >>> Hamcrest - BSDv3
> >>> org.hamcrest:hamcrest-api#1.0
> >>> org.hamcrest:hamcrest-core#1.****2.1
> >>> org.hamcrest:hamcrest-library#****1.2.1
> >>> JsonPath - ASLv2.0
> >>> com.jayway.jsonpath:json-path#****0.8.1
> >>> com.jayway.jsonpath:json-path-****assert#0.8.1
> >>>
> >>> XMLTool - ASLv2.0
> >>> com.mycila.xmltool:xmltool#3.3
> >>> REST-assured - ASLv2.0
> >>> com.jayway.restassured:rest-****assured#1.6.2
> >>>
> >>>
> >>> === Category B Dependencies ===
> >>>
> >>> Jersey - CDDLv1.1 or GPL2wCPE
> >>> com.sun.jersey:jersey-server#****1.14
> >>> com.sun.jersey:jersey-servlet#****1.14
> >>> Jerico - EPLv1.0
> >>> net.htmlparser.jericho:****jericho-html#3.2
> >>>
> >>> Servlet - CDDLv1.0 or GPLv2
> >>> javax.servlet:javax.servlet-****api#3.0.1
> >>>
> >>> JUnit - CPLv1.0
> >>> junit:junit#4.11
> >>>
> >>> == Cryptography ==
> >>>
> >>> The Gateway uses cryptographic software indirectly as a result of
> having
> >>> two dependencies: ApacheDS and Apache Shiro. Gateway does not include
> any
> >>> special or custom cryptographic technologies.
> >>>
> >>> ApacheDS is an ASF project and has been classified Export Commodity
> >>> Control Number (ECCN) 5D002.C.1 due to it’s dependency on Bouncy
> Castle.
> >>> More information on the ApacheDS classification can be found at
> >>> http://svn.apache.org/repos/****asf/directory/apacheds/trunk/****<
> http://svn.apache.org/repos/**asf/directory/apacheds/trunk/**>
> >>> installers/README<http://svn.**apache.org/repos/asf/**
> >>> directory/apacheds/trunk/**installers/README<
> http://svn.apache.org/repos/asf/directory/apacheds/trunk/installers/README
> >
> >>> >
> >>>
> >>>
> >>> Apache Shiro is an ASF project and has been classified Export Commodity
> >>> Control Number (ECCN) 5D002.C.1. More information on the Apache Shiro
> >>> classification can be found at http://svn.apache.org/repos/**
> >>> asf/shiro/trunk/README<http://**svn.apache.org/repos/asf/**
> >>> shiro/trunk/README <http://svn.apache.org/repos/asf/shiro/trunk/README
> >>
> >>>
> >>>
> >>> == Required Resources ==
> >>>
> >>> === Mailing lists ===
> >>>
> >>> knox-dev AT incubator DOT apache DOT org
> >>> knox-commits AT incubator DOT apache DOT org
> >>> knox-user AT hms incubator apache DOT org
> >>> knox-private AT incubator DOT apache DOT org
> >>>
> >>> === Subversion Directory ===
> >>>
> >>> https://svn.apache.org/repos/****asf/incubator/knox<
> https://svn.apache.org/repos/**asf/incubator/knox>
> >>> <https://**svn.apache.org/repos/asf/**incubator/knox<
> https://svn.apache.org/repos/asf/incubator/knox>
> >>> >
> >>>
> >>>
> >>> === Issue Tracking ===
> >>>
> >>> JIRA Knox (KNOX)
> >>>
> >>> == Initial Committers ==
> >>>
> >>> Kevin Minder (kevin DOT minder AT hortonworks DOT com)
> >>> Larry McCay (lmccay AT hortonworks DOT com)
> >>> John Speidel (jspeidel AT hortonworks DOT com)
> >>> Tom Beerbower (tbeerbower AT hortonworks DOT com)
> >>> Sumit Mohanty (smohanty AT hortonworks DOT com)
> >>>
> >>> == Affiliations ==
> >>>
> >>> Kevin Minder (Hortonworks)
> >>> Larry McCay (Hortonworks)
> >>> John Speidel (Hortonworks)
> >>> Tom Beerbower (Hortonworks)
> >>> Sumit Mohanty (Hortonworks)
> >>>
> >>> == Sponsors ==
> >>>
> >>> === Champion ===
> >>>
> >>> Devaraj Das (ddas AT apache DOT org)
> >>>
> >>> === Nominated Mentors ===
> >>>
> >>> Owen O’Malley (omalley AT apache DOT org)
> >>> Mahadev Konar (mahadev AT apache DOT org)
> >>> Alan Gates (gates AT apache DOT org)
> >>> Devaraj Das (ddas AT apache DOT org)
> >>>
> >>> === Sponsoring Entity ===
> >>>
> >>> Incubator PMC
> >>>
> >>> ------------------------------****----------------------------**
> >>> --**---------
> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.****apache.org<
> >>> general-**unsubscribe@incubator.apache.**org<
> general-unsubscribe@incubator.apache.org>
> >>> >
> >>> For additional commands, e-mail: general-help@incubator.apache.
> ****org<
> >>> general-help@incubator.**apache.org <general-help@incubator.apache.org
> >>
> >>>
> >>>
> >>>
> >>
> >
> > ------------------------------**------------------------------**---------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org<
> general-unsubscribe@incubator.apache.org>
> > For additional commands, e-mail: general-help@incubator.apache.**org<
> general-help@incubator.apache.org>
> >
> >
>
>
> --
> Eric Sammer
> twitter: esammer
> data: www.cloudera.com
>
--
Best Regards,
-- Alex
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Eric Sammer <es...@cloudera.com>.
Kevin:
Makes complete sense.
I'd like to offer to join the project, if it's accepted for incubation. I'm
a committer on MRUnit and Flume, and on the PMC for both. I've helped both
projects through the incubation phase, and I also know a little bit about
this Hadoop thing. ;)
Thanks!
On Mon, Feb 11, 2013 at 9:28 AM, Kevin Minder
<ke...@hortonworks.com>wrote:
> Hi Eric,
> Let me answer your second question first.
>
> Q: Is it your intention to provide job submissions and data ingestion APIs
> for MR and HDFS, respectively?
> A: Yes we plan to progress the project to cover all existing ecosystem
> projects. In addition the project is based on a modular framework that
> allows for each extension to cover services that are either new or
> proprietary. Certainly there exist very high volume data ingest use cases
> for which using a gateway may be impractical but in general the idea is to
> support all required client interaction with Hadoop via the gateway.
>
> Now for your first question...
>
> Q: Can you explain a bit more about what the target use case is?
> A: One typical use case will be that the gateway will run in a DMW. It
> will as you say be integrations with various directory services and is
> extensible to cover those not included. The gateway will then propagate
> the identity into the Hadoop cluster using Hadoop specific mechanisms. The
> key point is that there will typically be a single port open on the client
> side to the gateway. The Hadoop cluster is firewalled, only providing
> access to the Hadoop services to the gateway instances.
> A: Another use case is that an organization is already using some SSO
> solution and the gateway would be integrated with that to verify any SSO
> token and then propagate the identity to the Hadoop services.
>
> I will collect this and add it to the proposal wiki once I have privs to
> create the page.
>
> Thanks!
> Kevin.
>
>
> On 2/11/13 12:03 PM, Eric Sammer wrote:
>
>> Kevin:
>>
>> Interesting proposal. Can you explain a bit more about what the target use
>> case is? It sounds like there's SSO-ish functionality (presumably a doAs()
>> machine) with integration with directory services, but the proposal also
>> mentions a single point for "data and jobs." Is it your intention to
>> provide job submissions and data ingestion APIs for MR and HDFS,
>> respectively? Do you plan to target other ecosystem projects such as
>> HBase?
>> Sorry if I missed this in the proposal.
>>
>> Thanks!
>>
>>
>> On Mon, Feb 11, 2013 at 6:55 AM, Kevin Minder
>> <ke...@hortonworks.com>**wrote:
>>
>> Knox Gateway Proposal
>>>
>>> == Abstract ==
>>>
>>> Knox Gateway is a system that provides a single point of secure access
>>> for
>>> Apache Hadoop clusters.
>>>
>>> == Proposal ==
>>>
>>> The Knox Gateway (“Gateway” or “Knox”) is a system that provides a single
>>> point of authentication and access for Apache Hadoop services in a
>>> cluster.
>>> The goal is to simplify Hadoop security for both users (i.e. who access
>>> the
>>> cluster data and execute jobs) and operators (i.e. who control access and
>>> manage the cluster). The Gateway runs as a server (or cluster of servers)
>>> that serve one or more Hadoop clusters.
>>>
>>> Provide perimeter security to make Hadoop security setup easier
>>> Support authentication and token verification security scenarios
>>> Deliver users a single cluster end-point that aggregates capabilities for
>>> data and jobs
>>> Enable integration with enterprise and cloud identity management
>>> environments
>>>
>>> == Background ==
>>>
>>> An Apache Hadoop cluster is presented to consumers as a loose collection
>>> of independent services. This makes it difficult for users to interact
>>> with
>>> Hadoop since each service maintains it’s own method of access and
>>> security.
>>> As well, for operators, configuration and administration of a secure
>>> Hadoop
>>> cluster is a complex and many Hadoop clusters are insecure as a result.
>>>
>>> == Rationale ==
>>>
>>> Organizations that are struggling with Hadoop cluster security result in
>>> a) running Hadoop without security or b) slowing adoption of Hadoop. The
>>> Gateway aims to provide perimeter security that integrates more easily
>>> into
>>> existing organizations’ security infrastructure. Doing so will simplify
>>> security for these organizations and benefit all Hadoop stakeholders
>>> (i.e.
>>> users and operators). Additionally, making a dedicated perimeter security
>>> project part of the Apache Hadoop ecosystem will prevent fragmentation in
>>> this area and further increase the value of Hadoop as a data platform.
>>>
>>> == Current Status ==
>>>
>>> Prototype available, developed by the list of initial committers.
>>>
>>> === Meritocracy ===
>>>
>>> We desire to build a diverse developer community around Gateway following
>>> the Apache Way. We want to make the project open source and will
>>> encourage
>>> contributors from multiple organizations following the Apache meritocracy
>>> model.
>>>
>>> === Community ===
>>>
>>> We hope to extend the user and developer base in the future and build a
>>> solid open source community around Gateway. Apache Hadoop has a large
>>> ecosystem of open source projects, each with a strong community of
>>> contributors. All project communities in this ecosystem have an
>>> opportunity
>>> to participate in the advancement of the Gateway project because
>>> ultimately, Gateway will enable the security capabilities of their
>>> project
>>> to be more enterprise friendly.
>>>
>>> === Core Developers ===
>>>
>>> Gateway is currently being developed by several engineers from
>>> Hortonworks
>>> - Kevin Minder, Larry McCay, John Speidel, Tom Beerbower and Sumit
>>> Mohanty.
>>> All the engineers have deep expertise in middleware, security & identity
>>> systems and are quite familiar with the Hadoop ecosystem.
>>>
>>> === Alignment ===
>>>
>>> The ASF is a natural host for Gateway given that it is already the home
>>> of
>>> Hadoop, Hive, Pig, HBase, Oozie and other emerging big data software
>>> projects. Gateway is designed to solve the security challenges familiar
>>> to
>>> the Hadoop ecosystem family of projects.
>>>
>>> == Known Risks ==
>>>
>>> === Orphaned products & Reliance on Salaried Developers ===
>>>
>>> The core developers plan to work full time on the project. We believe
>>> that
>>> this project will be of general interest to many Hadoop users and will
>>> attract a diverse set of contributors. We intend to demonstrate this by
>>> having contributors from several organizations recognized as committers
>>> by
>>> the time Knox graduates from incubation.
>>>
>>> === Inexperience with Open Source ===
>>>
>>> All of the core developers are active users and followers of open source.
>>> As well, Hortonworks has a strong heritage of success with contributions
>>> to
>>> Apache Hadoop Projects.
>>>
>>> === Homogeneous Developers ===
>>>
>>> The current core developers are from Hortonworks, however, we hope to
>>> establish a developer community that includes contributors from several
>>> corporations.
>>>
>>> === Reliance on Salaried Developers ===
>>>
>>> Currently, the developers are paid to do work on Gateway. However, once
>>> the project has a community built around it, we expect to get committers
>>> and developers from outside the current core developers.
>>>
>>> === Relationships with Other Apache Products ===
>>>
>>> Gateway is going to be used by the users and operators of Hadoop, and the
>>> Hadoop ecosystem in general.
>>>
>>> === A Excessive Fascination with the Apache Brand ===
>>>
>>> Our interest in developing Gateway in Apache project is to follow an
>>> established development model, as well since many of the Hadoop ecosystem
>>> projects also are part of Apache, Gateway will complement those projects
>>> by
>>> following the same development and contribution model.
>>>
>>> == Documentation ==
>>>
>>> There is documentation in Hortonworks’ internal repositories. These can
>>> be
>>> shared upon request and will be transferred into the Apache CM system if
>>> this proposal is accepted.
>>>
>>> == Initial Source ==
>>>
>>> The source is currently in Hortonworks’ internal repositories. The
>>> process
>>> of making this GitHub repository public has been started and the URL will
>>> be provided once available.
>>>
>>> == Source and Intellectual Property Submission Plan ==
>>>
>>> The complete Gateway code is under Apache Software License 2.
>>>
>>> == External Dependencies ==
>>>
>>> The Gateway dependencies are listed below, separated by Category A and
>>> Category B as defined in the Apache Third-Party Licensing Policy. Note:
>>> These are the direct dependencies. Indirect dependencies are not
>>> included.
>>>
>>> === Category A Dependencies ===
>>>
>>> Apache Commons - ASLv2.0
>>> commons-io:commons-io#2.4
>>> commons-cli:commons-cli#1.2
>>> commons-codec:commons-codec#1.****7
>>> org.apache.commons:commons-****digester3#3.2
>>> org.apache.commons:commons-****vfs2#2.0
>>> Apache Hadoop - ASLv2.0
>>> org.apache.hadoop:hadoop-auth#****0.23.3
>>> org.apache.hadoop:hadoop-core#****1.0.3
>>> Apache Geronimo - ASLv2.0
>>> org.apache.geronimo.****components:geronimo-jaspi#2.0.****0
>>> org.apache.geronimo.specs:****geronimo-osgi-locator#1.1
>>> Apache Shiro - ASLv2.0
>>> org.apache.shiro:shiro-web#1.****2.1
>>> ApacheDS - ASLv2.0
>>> org.apache.directory.server:****apacheds-all#1.5.5
>>>
>>> Log4J - ASLv2.0
>>> log4j:log4j#1.2.17
>>> SL4J - MIT
>>> org.slf4j:slf4j-api#1.6.6
>>> org.slf4j:slf4j-log4j12#1.6.6
>>> Guava - ASLv2.0
>>> com.google.guava:guava#14.0-****rc1
>>> HttpClient - ASLv2.0
>>> org.apache.httpcomponents:****httpclient#4.2.1
>>> Jetty - ASLv2.0
>>> org.eclipse.jetty:jetty-****server#8.1.7.v20120910
>>> org.eclipse.jetty:jetty-****servlet#8.1.7.v20120910
>>> org.eclipse.jetty:jetty-****webapp#8.1.7.v20120910
>>> org.eclipse.jetty:jetty-jaspi#****8.1.7.v20120910
>>> org.eclipse.jetty.aggregate:****jetty-all#8.1.7.v20120910
>>> org.eclipse.jetty:test-jetty-****servlet#8.1.7.v20120910
>>> Spring Security - ASLv2.0
>>> org.springframework:spring-****core#3.1.3.RELEASE
>>> org.springframework:spring-****context#3.1.3.RELEASE
>>> org.springframework:spring-****web#3.1.3.RELEASE
>>> org.springframework.security:****spring-security-core#3.1.3.****RELEASE
>>> org.springframework.security:****spring-security-web#3.1.3.****RELEASE
>>> org.springframework.security:****spring-security-config#3.1.3.**
>>> **RELEASE
>>> org.springframework.security:****spring-security-ldap#3.1.2.****RELEASE
>>> org.springframework.ldap:****spring-ldap-core#1.3.1.RELEASE
>>> org.springframework.ldap:****spring-ldap-core-tiger#1.3.1.****RELEASE
>>> org.springframework.ldap:****spring-ldap-odm#1.3.1.RELEASE
>>> org.springframework.ldap:****spring-ldap-ldif-core#1.3.1.****RELEASE
>>> org.springframework.ldap:****spring-ldap-ldif-batch#1.3.1.****RELEASE
>>> JBoss ShrinkWrap - ASLv2.0
>>> org.jboss.shrinkwrap:****shrinkwrap-api#1.0.1
>>> org.jboss.shrinkwrap:****shrinkwrap-impl-base#1.0.1
>>> org.jboss.shrinkwrap.****descriptors:shrinkwrap-**
>>> descriptors-api-javaee#2.0.0-****alpha-4
>>> org.jboss.shrinkwrap.****descriptors:shrinkwrap-**
>>> descriptors-impl-javaee#2.0.0-****alpha-4
>>>
>>>
>>> === Category A Dependencies (Test) ===
>>>
>>> EasyMock - ASLv2.0
>>> org.easymock:easymock#3.0
>>> XML Matchers - ASLv2.0
>>> org.xmlmatchers:xml-matchers#****0.10
>>>
>>> Hamcrest - BSDv3
>>> org.hamcrest:hamcrest-api#1.0
>>> org.hamcrest:hamcrest-core#1.****2.1
>>> org.hamcrest:hamcrest-library#****1.2.1
>>> JsonPath - ASLv2.0
>>> com.jayway.jsonpath:json-path#****0.8.1
>>> com.jayway.jsonpath:json-path-****assert#0.8.1
>>>
>>> XMLTool - ASLv2.0
>>> com.mycila.xmltool:xmltool#3.3
>>> REST-assured - ASLv2.0
>>> com.jayway.restassured:rest-****assured#1.6.2
>>>
>>>
>>> === Category B Dependencies ===
>>>
>>> Jersey - CDDLv1.1 or GPL2wCPE
>>> com.sun.jersey:jersey-server#****1.14
>>> com.sun.jersey:jersey-servlet#****1.14
>>> Jerico - EPLv1.0
>>> net.htmlparser.jericho:****jericho-html#3.2
>>>
>>> Servlet - CDDLv1.0 or GPLv2
>>> javax.servlet:javax.servlet-****api#3.0.1
>>>
>>> JUnit - CPLv1.0
>>> junit:junit#4.11
>>>
>>> == Cryptography ==
>>>
>>> The Gateway uses cryptographic software indirectly as a result of having
>>> two dependencies: ApacheDS and Apache Shiro. Gateway does not include any
>>> special or custom cryptographic technologies.
>>>
>>> ApacheDS is an ASF project and has been classified Export Commodity
>>> Control Number (ECCN) 5D002.C.1 due to it’s dependency on Bouncy Castle.
>>> More information on the ApacheDS classification can be found at
>>> http://svn.apache.org/repos/****asf/directory/apacheds/trunk/****<http://svn.apache.org/repos/**asf/directory/apacheds/trunk/**>
>>> installers/README<http://svn.**apache.org/repos/asf/**
>>> directory/apacheds/trunk/**installers/README<http://svn.apache.org/repos/asf/directory/apacheds/trunk/installers/README>
>>> >
>>>
>>>
>>> Apache Shiro is an ASF project and has been classified Export Commodity
>>> Control Number (ECCN) 5D002.C.1. More information on the Apache Shiro
>>> classification can be found at http://svn.apache.org/repos/**
>>> asf/shiro/trunk/README<http://**svn.apache.org/repos/asf/**
>>> shiro/trunk/README <http://svn.apache.org/repos/asf/shiro/trunk/README>>
>>>
>>>
>>> == Required Resources ==
>>>
>>> === Mailing lists ===
>>>
>>> knox-dev AT incubator DOT apache DOT org
>>> knox-commits AT incubator DOT apache DOT org
>>> knox-user AT hms incubator apache DOT org
>>> knox-private AT incubator DOT apache DOT org
>>>
>>> === Subversion Directory ===
>>>
>>> https://svn.apache.org/repos/****asf/incubator/knox<https://svn.apache.org/repos/**asf/incubator/knox>
>>> <https://**svn.apache.org/repos/asf/**incubator/knox<https://svn.apache.org/repos/asf/incubator/knox>
>>> >
>>>
>>>
>>> === Issue Tracking ===
>>>
>>> JIRA Knox (KNOX)
>>>
>>> == Initial Committers ==
>>>
>>> Kevin Minder (kevin DOT minder AT hortonworks DOT com)
>>> Larry McCay (lmccay AT hortonworks DOT com)
>>> John Speidel (jspeidel AT hortonworks DOT com)
>>> Tom Beerbower (tbeerbower AT hortonworks DOT com)
>>> Sumit Mohanty (smohanty AT hortonworks DOT com)
>>>
>>> == Affiliations ==
>>>
>>> Kevin Minder (Hortonworks)
>>> Larry McCay (Hortonworks)
>>> John Speidel (Hortonworks)
>>> Tom Beerbower (Hortonworks)
>>> Sumit Mohanty (Hortonworks)
>>>
>>> == Sponsors ==
>>>
>>> === Champion ===
>>>
>>> Devaraj Das (ddas AT apache DOT org)
>>>
>>> === Nominated Mentors ===
>>>
>>> Owen O’Malley (omalley AT apache DOT org)
>>> Mahadev Konar (mahadev AT apache DOT org)
>>> Alan Gates (gates AT apache DOT org)
>>> Devaraj Das (ddas AT apache DOT org)
>>>
>>> === Sponsoring Entity ===
>>>
>>> Incubator PMC
>>>
>>> ------------------------------****----------------------------**
>>> --**---------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.****apache.org<
>>> general-**unsubscribe@incubator.apache.**org<ge...@incubator.apache.org>
>>> >
>>> For additional commands, e-mail: general-help@incubator.apache.****org<
>>> general-help@incubator.**apache.org <ge...@incubator.apache.org>>
>>>
>>>
>>>
>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org<ge...@incubator.apache.org>
> For additional commands, e-mail: general-help@incubator.apache.**org<ge...@incubator.apache.org>
>
>
--
Eric Sammer
twitter: esammer
data: www.cloudera.com
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Kevin Minder <ke...@hortonworks.com>.
Hi Eric,
Let me answer your second question first.
Q: Is it your intention to provide job submissions and data ingestion APIs for MR and HDFS, respectively?
A: Yes we plan to progress the project to cover all existing ecosystem projects. In addition the project is based on a modular framework that allows for each extension to cover services that are either new or proprietary. Certainly there exist very high volume data ingest use cases for which using a gateway may be impractical but in general the idea is to support all required client interaction with Hadoop via the gateway.
Now for your first question...
Q: Can you explain a bit more about what the target use case is?
A: One typical use case will be that the gateway will run in a DMW. It will as you say be integrations with various directory services and is extensible to cover those not included. The gateway will then propagate the identity into the Hadoop cluster using Hadoop specific mechanisms. The key point is that there will typically be a single port open on the client side to the gateway. The Hadoop cluster is firewalled, only providing access to the Hadoop services to the gateway instances.
A: Another use case is that an organization is already using some SSO solution and the gateway would be integrated with that to verify any SSO token and then propagate the identity to the Hadoop services.
I will collect this and add it to the proposal wiki once I have privs to
create the page.
Thanks!
Kevin.
On 2/11/13 12:03 PM, Eric Sammer wrote:
> Kevin:
>
> Interesting proposal. Can you explain a bit more about what the target use
> case is? It sounds like there's SSO-ish functionality (presumably a doAs()
> machine) with integration with directory services, but the proposal also
> mentions a single point for "data and jobs." Is it your intention to
> provide job submissions and data ingestion APIs for MR and HDFS,
> respectively? Do you plan to target other ecosystem projects such as HBase?
> Sorry if I missed this in the proposal.
>
> Thanks!
>
>
> On Mon, Feb 11, 2013 at 6:55 AM, Kevin Minder
> <ke...@hortonworks.com>wrote:
>
>> Knox Gateway Proposal
>>
>> == Abstract ==
>>
>> Knox Gateway is a system that provides a single point of secure access for
>> Apache Hadoop clusters.
>>
>> == Proposal ==
>>
>> The Knox Gateway (“Gateway” or “Knox”) is a system that provides a single
>> point of authentication and access for Apache Hadoop services in a cluster.
>> The goal is to simplify Hadoop security for both users (i.e. who access the
>> cluster data and execute jobs) and operators (i.e. who control access and
>> manage the cluster). The Gateway runs as a server (or cluster of servers)
>> that serve one or more Hadoop clusters.
>>
>> Provide perimeter security to make Hadoop security setup easier
>> Support authentication and token verification security scenarios
>> Deliver users a single cluster end-point that aggregates capabilities for
>> data and jobs
>> Enable integration with enterprise and cloud identity management
>> environments
>>
>> == Background ==
>>
>> An Apache Hadoop cluster is presented to consumers as a loose collection
>> of independent services. This makes it difficult for users to interact with
>> Hadoop since each service maintains it’s own method of access and security.
>> As well, for operators, configuration and administration of a secure Hadoop
>> cluster is a complex and many Hadoop clusters are insecure as a result.
>>
>> == Rationale ==
>>
>> Organizations that are struggling with Hadoop cluster security result in
>> a) running Hadoop without security or b) slowing adoption of Hadoop. The
>> Gateway aims to provide perimeter security that integrates more easily into
>> existing organizations’ security infrastructure. Doing so will simplify
>> security for these organizations and benefit all Hadoop stakeholders (i.e.
>> users and operators). Additionally, making a dedicated perimeter security
>> project part of the Apache Hadoop ecosystem will prevent fragmentation in
>> this area and further increase the value of Hadoop as a data platform.
>>
>> == Current Status ==
>>
>> Prototype available, developed by the list of initial committers.
>>
>> === Meritocracy ===
>>
>> We desire to build a diverse developer community around Gateway following
>> the Apache Way. We want to make the project open source and will encourage
>> contributors from multiple organizations following the Apache meritocracy
>> model.
>>
>> === Community ===
>>
>> We hope to extend the user and developer base in the future and build a
>> solid open source community around Gateway. Apache Hadoop has a large
>> ecosystem of open source projects, each with a strong community of
>> contributors. All project communities in this ecosystem have an opportunity
>> to participate in the advancement of the Gateway project because
>> ultimately, Gateway will enable the security capabilities of their project
>> to be more enterprise friendly.
>>
>> === Core Developers ===
>>
>> Gateway is currently being developed by several engineers from Hortonworks
>> - Kevin Minder, Larry McCay, John Speidel, Tom Beerbower and Sumit Mohanty.
>> All the engineers have deep expertise in middleware, security & identity
>> systems and are quite familiar with the Hadoop ecosystem.
>>
>> === Alignment ===
>>
>> The ASF is a natural host for Gateway given that it is already the home of
>> Hadoop, Hive, Pig, HBase, Oozie and other emerging big data software
>> projects. Gateway is designed to solve the security challenges familiar to
>> the Hadoop ecosystem family of projects.
>>
>> == Known Risks ==
>>
>> === Orphaned products & Reliance on Salaried Developers ===
>>
>> The core developers plan to work full time on the project. We believe that
>> this project will be of general interest to many Hadoop users and will
>> attract a diverse set of contributors. We intend to demonstrate this by
>> having contributors from several organizations recognized as committers by
>> the time Knox graduates from incubation.
>>
>> === Inexperience with Open Source ===
>>
>> All of the core developers are active users and followers of open source.
>> As well, Hortonworks has a strong heritage of success with contributions to
>> Apache Hadoop Projects.
>>
>> === Homogeneous Developers ===
>>
>> The current core developers are from Hortonworks, however, we hope to
>> establish a developer community that includes contributors from several
>> corporations.
>>
>> === Reliance on Salaried Developers ===
>>
>> Currently, the developers are paid to do work on Gateway. However, once
>> the project has a community built around it, we expect to get committers
>> and developers from outside the current core developers.
>>
>> === Relationships with Other Apache Products ===
>>
>> Gateway is going to be used by the users and operators of Hadoop, and the
>> Hadoop ecosystem in general.
>>
>> === A Excessive Fascination with the Apache Brand ===
>>
>> Our interest in developing Gateway in Apache project is to follow an
>> established development model, as well since many of the Hadoop ecosystem
>> projects also are part of Apache, Gateway will complement those projects by
>> following the same development and contribution model.
>>
>> == Documentation ==
>>
>> There is documentation in Hortonworks’ internal repositories. These can be
>> shared upon request and will be transferred into the Apache CM system if
>> this proposal is accepted.
>>
>> == Initial Source ==
>>
>> The source is currently in Hortonworks’ internal repositories. The process
>> of making this GitHub repository public has been started and the URL will
>> be provided once available.
>>
>> == Source and Intellectual Property Submission Plan ==
>>
>> The complete Gateway code is under Apache Software License 2.
>>
>> == External Dependencies ==
>>
>> The Gateway dependencies are listed below, separated by Category A and
>> Category B as defined in the Apache Third-Party Licensing Policy. Note:
>> These are the direct dependencies. Indirect dependencies are not included.
>>
>> === Category A Dependencies ===
>>
>> Apache Commons - ASLv2.0
>> commons-io:commons-io#2.4
>> commons-cli:commons-cli#1.2
>> commons-codec:commons-codec#1.**7
>> org.apache.commons:commons-**digester3#3.2
>> org.apache.commons:commons-**vfs2#2.0
>> Apache Hadoop - ASLv2.0
>> org.apache.hadoop:hadoop-auth#**0.23.3
>> org.apache.hadoop:hadoop-core#**1.0.3
>> Apache Geronimo - ASLv2.0
>> org.apache.geronimo.**components:geronimo-jaspi#2.0.**0
>> org.apache.geronimo.specs:**geronimo-osgi-locator#1.1
>> Apache Shiro - ASLv2.0
>> org.apache.shiro:shiro-web#1.**2.1
>> ApacheDS - ASLv2.0
>> org.apache.directory.server:**apacheds-all#1.5.5
>> Log4J - ASLv2.0
>> log4j:log4j#1.2.17
>> SL4J - MIT
>> org.slf4j:slf4j-api#1.6.6
>> org.slf4j:slf4j-log4j12#1.6.6
>> Guava - ASLv2.0
>> com.google.guava:guava#14.0-**rc1
>> HttpClient - ASLv2.0
>> org.apache.httpcomponents:**httpclient#4.2.1
>> Jetty - ASLv2.0
>> org.eclipse.jetty:jetty-**server#8.1.7.v20120910
>> org.eclipse.jetty:jetty-**servlet#8.1.7.v20120910
>> org.eclipse.jetty:jetty-**webapp#8.1.7.v20120910
>> org.eclipse.jetty:jetty-jaspi#**8.1.7.v20120910
>> org.eclipse.jetty.aggregate:**jetty-all#8.1.7.v20120910
>> org.eclipse.jetty:test-jetty-**servlet#8.1.7.v20120910
>> Spring Security - ASLv2.0
>> org.springframework:spring-**core#3.1.3.RELEASE
>> org.springframework:spring-**context#3.1.3.RELEASE
>> org.springframework:spring-**web#3.1.3.RELEASE
>> org.springframework.security:**spring-security-core#3.1.3.**RELEASE
>> org.springframework.security:**spring-security-web#3.1.3.**RELEASE
>> org.springframework.security:**spring-security-config#3.1.3.**RELEASE
>> org.springframework.security:**spring-security-ldap#3.1.2.**RELEASE
>> org.springframework.ldap:**spring-ldap-core#1.3.1.RELEASE
>> org.springframework.ldap:**spring-ldap-core-tiger#1.3.1.**RELEASE
>> org.springframework.ldap:**spring-ldap-odm#1.3.1.RELEASE
>> org.springframework.ldap:**spring-ldap-ldif-core#1.3.1.**RELEASE
>> org.springframework.ldap:**spring-ldap-ldif-batch#1.3.1.**RELEASE
>> JBoss ShrinkWrap - ASLv2.0
>> org.jboss.shrinkwrap:**shrinkwrap-api#1.0.1
>> org.jboss.shrinkwrap:**shrinkwrap-impl-base#1.0.1
>> org.jboss.shrinkwrap.**descriptors:shrinkwrap-**
>> descriptors-api-javaee#2.0.0-**alpha-4
>> org.jboss.shrinkwrap.**descriptors:shrinkwrap-**
>> descriptors-impl-javaee#2.0.0-**alpha-4
>>
>> === Category A Dependencies (Test) ===
>>
>> EasyMock - ASLv2.0
>> org.easymock:easymock#3.0
>> XML Matchers - ASLv2.0
>> org.xmlmatchers:xml-matchers#**0.10
>> Hamcrest - BSDv3
>> org.hamcrest:hamcrest-api#1.0
>> org.hamcrest:hamcrest-core#1.**2.1
>> org.hamcrest:hamcrest-library#**1.2.1
>> JsonPath - ASLv2.0
>> com.jayway.jsonpath:json-path#**0.8.1
>> com.jayway.jsonpath:json-path-**assert#0.8.1
>> XMLTool - ASLv2.0
>> com.mycila.xmltool:xmltool#3.3
>> REST-assured - ASLv2.0
>> com.jayway.restassured:rest-**assured#1.6.2
>>
>> === Category B Dependencies ===
>>
>> Jersey - CDDLv1.1 or GPL2wCPE
>> com.sun.jersey:jersey-server#**1.14
>> com.sun.jersey:jersey-servlet#**1.14
>> Jerico - EPLv1.0
>> net.htmlparser.jericho:**jericho-html#3.2
>> Servlet - CDDLv1.0 or GPLv2
>> javax.servlet:javax.servlet-**api#3.0.1
>> JUnit - CPLv1.0
>> junit:junit#4.11
>>
>> == Cryptography ==
>>
>> The Gateway uses cryptographic software indirectly as a result of having
>> two dependencies: ApacheDS and Apache Shiro. Gateway does not include any
>> special or custom cryptographic technologies.
>>
>> ApacheDS is an ASF project and has been classified Export Commodity
>> Control Number (ECCN) 5D002.C.1 due to it’s dependency on Bouncy Castle.
>> More information on the ApacheDS classification can be found at
>> http://svn.apache.org/repos/**asf/directory/apacheds/trunk/**
>> installers/README<http://svn.apache.org/repos/asf/directory/apacheds/trunk/installers/README>
>>
>> Apache Shiro is an ASF project and has been classified Export Commodity
>> Control Number (ECCN) 5D002.C.1. More information on the Apache Shiro
>> classification can be found at http://svn.apache.org/repos/**
>> asf/shiro/trunk/README<http://svn.apache.org/repos/asf/shiro/trunk/README>
>>
>> == Required Resources ==
>>
>> === Mailing lists ===
>>
>> knox-dev AT incubator DOT apache DOT org
>> knox-commits AT incubator DOT apache DOT org
>> knox-user AT hms incubator apache DOT org
>> knox-private AT incubator DOT apache DOT org
>>
>> === Subversion Directory ===
>>
>> https://svn.apache.org/repos/**asf/incubator/knox<https://svn.apache.org/repos/asf/incubator/knox>
>>
>> === Issue Tracking ===
>>
>> JIRA Knox (KNOX)
>>
>> == Initial Committers ==
>>
>> Kevin Minder (kevin DOT minder AT hortonworks DOT com)
>> Larry McCay (lmccay AT hortonworks DOT com)
>> John Speidel (jspeidel AT hortonworks DOT com)
>> Tom Beerbower (tbeerbower AT hortonworks DOT com)
>> Sumit Mohanty (smohanty AT hortonworks DOT com)
>>
>> == Affiliations ==
>>
>> Kevin Minder (Hortonworks)
>> Larry McCay (Hortonworks)
>> John Speidel (Hortonworks)
>> Tom Beerbower (Hortonworks)
>> Sumit Mohanty (Hortonworks)
>>
>> == Sponsors ==
>>
>> === Champion ===
>>
>> Devaraj Das (ddas AT apache DOT org)
>>
>> === Nominated Mentors ===
>>
>> Owen O’Malley (omalley AT apache DOT org)
>> Mahadev Konar (mahadev AT apache DOT org)
>> Alan Gates (gates AT apache DOT org)
>> Devaraj Das (ddas AT apache DOT org)
>>
>> === Sponsoring Entity ===
>>
>> Incubator PMC
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org<ge...@incubator.apache.org>
>> For additional commands, e-mail: general-help@incubator.apache.**org<ge...@incubator.apache.org>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [PROPOSAL] Knox Hadoop Gateway Project
Posted by Eric Sammer <es...@cloudera.com>.
Kevin:
Interesting proposal. Can you explain a bit more about what the target use
case is? It sounds like there's SSO-ish functionality (presumably a doAs()
machine) with integration with directory services, but the proposal also
mentions a single point for "data and jobs." Is it your intention to
provide job submissions and data ingestion APIs for MR and HDFS,
respectively? Do you plan to target other ecosystem projects such as HBase?
Sorry if I missed this in the proposal.
Thanks!
On Mon, Feb 11, 2013 at 6:55 AM, Kevin Minder
<ke...@hortonworks.com>wrote:
> Knox Gateway Proposal
>
> == Abstract ==
>
> Knox Gateway is a system that provides a single point of secure access for
> Apache Hadoop clusters.
>
> == Proposal ==
>
> The Knox Gateway (“Gateway” or “Knox”) is a system that provides a single
> point of authentication and access for Apache Hadoop services in a cluster.
> The goal is to simplify Hadoop security for both users (i.e. who access the
> cluster data and execute jobs) and operators (i.e. who control access and
> manage the cluster). The Gateway runs as a server (or cluster of servers)
> that serve one or more Hadoop clusters.
>
> Provide perimeter security to make Hadoop security setup easier
> Support authentication and token verification security scenarios
> Deliver users a single cluster end-point that aggregates capabilities for
> data and jobs
> Enable integration with enterprise and cloud identity management
> environments
>
> == Background ==
>
> An Apache Hadoop cluster is presented to consumers as a loose collection
> of independent services. This makes it difficult for users to interact with
> Hadoop since each service maintains it’s own method of access and security.
> As well, for operators, configuration and administration of a secure Hadoop
> cluster is a complex and many Hadoop clusters are insecure as a result.
>
> == Rationale ==
>
> Organizations that are struggling with Hadoop cluster security result in
> a) running Hadoop without security or b) slowing adoption of Hadoop. The
> Gateway aims to provide perimeter security that integrates more easily into
> existing organizations’ security infrastructure. Doing so will simplify
> security for these organizations and benefit all Hadoop stakeholders (i.e.
> users and operators). Additionally, making a dedicated perimeter security
> project part of the Apache Hadoop ecosystem will prevent fragmentation in
> this area and further increase the value of Hadoop as a data platform.
>
> == Current Status ==
>
> Prototype available, developed by the list of initial committers.
>
> === Meritocracy ===
>
> We desire to build a diverse developer community around Gateway following
> the Apache Way. We want to make the project open source and will encourage
> contributors from multiple organizations following the Apache meritocracy
> model.
>
> === Community ===
>
> We hope to extend the user and developer base in the future and build a
> solid open source community around Gateway. Apache Hadoop has a large
> ecosystem of open source projects, each with a strong community of
> contributors. All project communities in this ecosystem have an opportunity
> to participate in the advancement of the Gateway project because
> ultimately, Gateway will enable the security capabilities of their project
> to be more enterprise friendly.
>
> === Core Developers ===
>
> Gateway is currently being developed by several engineers from Hortonworks
> - Kevin Minder, Larry McCay, John Speidel, Tom Beerbower and Sumit Mohanty.
> All the engineers have deep expertise in middleware, security & identity
> systems and are quite familiar with the Hadoop ecosystem.
>
> === Alignment ===
>
> The ASF is a natural host for Gateway given that it is already the home of
> Hadoop, Hive, Pig, HBase, Oozie and other emerging big data software
> projects. Gateway is designed to solve the security challenges familiar to
> the Hadoop ecosystem family of projects.
>
> == Known Risks ==
>
> === Orphaned products & Reliance on Salaried Developers ===
>
> The core developers plan to work full time on the project. We believe that
> this project will be of general interest to many Hadoop users and will
> attract a diverse set of contributors. We intend to demonstrate this by
> having contributors from several organizations recognized as committers by
> the time Knox graduates from incubation.
>
> === Inexperience with Open Source ===
>
> All of the core developers are active users and followers of open source.
> As well, Hortonworks has a strong heritage of success with contributions to
> Apache Hadoop Projects.
>
> === Homogeneous Developers ===
>
> The current core developers are from Hortonworks, however, we hope to
> establish a developer community that includes contributors from several
> corporations.
>
> === Reliance on Salaried Developers ===
>
> Currently, the developers are paid to do work on Gateway. However, once
> the project has a community built around it, we expect to get committers
> and developers from outside the current core developers.
>
> === Relationships with Other Apache Products ===
>
> Gateway is going to be used by the users and operators of Hadoop, and the
> Hadoop ecosystem in general.
>
> === A Excessive Fascination with the Apache Brand ===
>
> Our interest in developing Gateway in Apache project is to follow an
> established development model, as well since many of the Hadoop ecosystem
> projects also are part of Apache, Gateway will complement those projects by
> following the same development and contribution model.
>
> == Documentation ==
>
> There is documentation in Hortonworks’ internal repositories. These can be
> shared upon request and will be transferred into the Apache CM system if
> this proposal is accepted.
>
> == Initial Source ==
>
> The source is currently in Hortonworks’ internal repositories. The process
> of making this GitHub repository public has been started and the URL will
> be provided once available.
>
> == Source and Intellectual Property Submission Plan ==
>
> The complete Gateway code is under Apache Software License 2.
>
> == External Dependencies ==
>
> The Gateway dependencies are listed below, separated by Category A and
> Category B as defined in the Apache Third-Party Licensing Policy. Note:
> These are the direct dependencies. Indirect dependencies are not included.
>
> === Category A Dependencies ===
>
> Apache Commons - ASLv2.0
> commons-io:commons-io#2.4
> commons-cli:commons-cli#1.2
> commons-codec:commons-codec#1.**7
> org.apache.commons:commons-**digester3#3.2
> org.apache.commons:commons-**vfs2#2.0
> Apache Hadoop - ASLv2.0
> org.apache.hadoop:hadoop-auth#**0.23.3
> org.apache.hadoop:hadoop-core#**1.0.3
> Apache Geronimo - ASLv2.0
> org.apache.geronimo.**components:geronimo-jaspi#2.0.**0
> org.apache.geronimo.specs:**geronimo-osgi-locator#1.1
> Apache Shiro - ASLv2.0
> org.apache.shiro:shiro-web#1.**2.1
> ApacheDS - ASLv2.0
> org.apache.directory.server:**apacheds-all#1.5.5
> Log4J - ASLv2.0
> log4j:log4j#1.2.17
> SL4J - MIT
> org.slf4j:slf4j-api#1.6.6
> org.slf4j:slf4j-log4j12#1.6.6
> Guava - ASLv2.0
> com.google.guava:guava#14.0-**rc1
> HttpClient - ASLv2.0
> org.apache.httpcomponents:**httpclient#4.2.1
> Jetty - ASLv2.0
> org.eclipse.jetty:jetty-**server#8.1.7.v20120910
> org.eclipse.jetty:jetty-**servlet#8.1.7.v20120910
> org.eclipse.jetty:jetty-**webapp#8.1.7.v20120910
> org.eclipse.jetty:jetty-jaspi#**8.1.7.v20120910
> org.eclipse.jetty.aggregate:**jetty-all#8.1.7.v20120910
> org.eclipse.jetty:test-jetty-**servlet#8.1.7.v20120910
> Spring Security - ASLv2.0
> org.springframework:spring-**core#3.1.3.RELEASE
> org.springframework:spring-**context#3.1.3.RELEASE
> org.springframework:spring-**web#3.1.3.RELEASE
> org.springframework.security:**spring-security-core#3.1.3.**RELEASE
> org.springframework.security:**spring-security-web#3.1.3.**RELEASE
> org.springframework.security:**spring-security-config#3.1.3.**RELEASE
> org.springframework.security:**spring-security-ldap#3.1.2.**RELEASE
> org.springframework.ldap:**spring-ldap-core#1.3.1.RELEASE
> org.springframework.ldap:**spring-ldap-core-tiger#1.3.1.**RELEASE
> org.springframework.ldap:**spring-ldap-odm#1.3.1.RELEASE
> org.springframework.ldap:**spring-ldap-ldif-core#1.3.1.**RELEASE
> org.springframework.ldap:**spring-ldap-ldif-batch#1.3.1.**RELEASE
> JBoss ShrinkWrap - ASLv2.0
> org.jboss.shrinkwrap:**shrinkwrap-api#1.0.1
> org.jboss.shrinkwrap:**shrinkwrap-impl-base#1.0.1
> org.jboss.shrinkwrap.**descriptors:shrinkwrap-**
> descriptors-api-javaee#2.0.0-**alpha-4
> org.jboss.shrinkwrap.**descriptors:shrinkwrap-**
> descriptors-impl-javaee#2.0.0-**alpha-4
>
> === Category A Dependencies (Test) ===
>
> EasyMock - ASLv2.0
> org.easymock:easymock#3.0
> XML Matchers - ASLv2.0
> org.xmlmatchers:xml-matchers#**0.10
> Hamcrest - BSDv3
> org.hamcrest:hamcrest-api#1.0
> org.hamcrest:hamcrest-core#1.**2.1
> org.hamcrest:hamcrest-library#**1.2.1
> JsonPath - ASLv2.0
> com.jayway.jsonpath:json-path#**0.8.1
> com.jayway.jsonpath:json-path-**assert#0.8.1
> XMLTool - ASLv2.0
> com.mycila.xmltool:xmltool#3.3
> REST-assured - ASLv2.0
> com.jayway.restassured:rest-**assured#1.6.2
>
> === Category B Dependencies ===
>
> Jersey - CDDLv1.1 or GPL2wCPE
> com.sun.jersey:jersey-server#**1.14
> com.sun.jersey:jersey-servlet#**1.14
> Jerico - EPLv1.0
> net.htmlparser.jericho:**jericho-html#3.2
> Servlet - CDDLv1.0 or GPLv2
> javax.servlet:javax.servlet-**api#3.0.1
> JUnit - CPLv1.0
> junit:junit#4.11
>
> == Cryptography ==
>
> The Gateway uses cryptographic software indirectly as a result of having
> two dependencies: ApacheDS and Apache Shiro. Gateway does not include any
> special or custom cryptographic technologies.
>
> ApacheDS is an ASF project and has been classified Export Commodity
> Control Number (ECCN) 5D002.C.1 due to it’s dependency on Bouncy Castle.
> More information on the ApacheDS classification can be found at
> http://svn.apache.org/repos/**asf/directory/apacheds/trunk/**
> installers/README<http://svn.apache.org/repos/asf/directory/apacheds/trunk/installers/README>
>
> Apache Shiro is an ASF project and has been classified Export Commodity
> Control Number (ECCN) 5D002.C.1. More information on the Apache Shiro
> classification can be found at http://svn.apache.org/repos/**
> asf/shiro/trunk/README<http://svn.apache.org/repos/asf/shiro/trunk/README>
>
> == Required Resources ==
>
> === Mailing lists ===
>
> knox-dev AT incubator DOT apache DOT org
> knox-commits AT incubator DOT apache DOT org
> knox-user AT hms incubator apache DOT org
> knox-private AT incubator DOT apache DOT org
>
> === Subversion Directory ===
>
> https://svn.apache.org/repos/**asf/incubator/knox<https://svn.apache.org/repos/asf/incubator/knox>
>
> === Issue Tracking ===
>
> JIRA Knox (KNOX)
>
> == Initial Committers ==
>
> Kevin Minder (kevin DOT minder AT hortonworks DOT com)
> Larry McCay (lmccay AT hortonworks DOT com)
> John Speidel (jspeidel AT hortonworks DOT com)
> Tom Beerbower (tbeerbower AT hortonworks DOT com)
> Sumit Mohanty (smohanty AT hortonworks DOT com)
>
> == Affiliations ==
>
> Kevin Minder (Hortonworks)
> Larry McCay (Hortonworks)
> John Speidel (Hortonworks)
> Tom Beerbower (Hortonworks)
> Sumit Mohanty (Hortonworks)
>
> == Sponsors ==
>
> === Champion ===
>
> Devaraj Das (ddas AT apache DOT org)
>
> === Nominated Mentors ===
>
> Owen O’Malley (omalley AT apache DOT org)
> Mahadev Konar (mahadev AT apache DOT org)
> Alan Gates (gates AT apache DOT org)
> Devaraj Das (ddas AT apache DOT org)
>
> === Sponsoring Entity ===
>
> Incubator PMC
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org<ge...@incubator.apache.org>
> For additional commands, e-mail: general-help@incubator.apache.**org<ge...@incubator.apache.org>
>
>
--
Eric Sammer
twitter: esammer
data: www.cloudera.com