GitHub user robertamarton opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/538

    TRAFODION [109] Instrument Trafodion to work with Secure Hadoop (Kerberos)

    The first phase of automation with Kerberos is ready.
    
    The following use cases are supported
    
    I.  New secure install: Customer installs Trafodion on a cluster with
     secure Hadoop. There is no existing Trafodion installation.
    
    II. Conversion from non-secure to secure: Customer has Trafodion installed
    on a non-secure Hadoop cluster. Customer enables Hadoop security on this 
    existing cluster. Customer runs a Trafodion script to enable Hadoop 
security 
    integration with Trafodion.
    
    See the JIRA for details on the changes.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/robertamarton/incubator-trafodion kerberos

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/538.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #538
    
----
commit 9673059cfb03abd8aabf37be1b4936ee520a4129
Author: Roberta Marton <[email protected]>
Date:   2016-06-10T14:50:06Z

    TRAFODION [109] Instrument Trafodion to work with Secure Hadoop (Kerberos)
    
    The first phase of automation with Kerberos is ready.
    
    The following use cases are supported
    
    I.  New secure install: Customer installs Trafodion on a cluster with
     secure Hadoop. There is no existing Trafodion installation.
    
    II. Conversion from non-secure to secure: Customer has Trafodion installed
    on a non-secure Hadoop cluster. Customer enables Hadoop security on this
    existing cluster. Customer runs a Trafodion script to enable Hadoop security
    integration with Trafodion.
    
    See the JIRA for details on the changes.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to