[ 
https://issues.apache.org/jira/browse/BIGTOP-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204244#comment-13204244
 ] 

Patrick Taylor Ramsey edited comment on BIGTOP-396 at 2/9/12 4:29 AM:
----------------------------------------------------------------------

* Removed hadoop-specific code from kerberos module (per Roman Shaposhnik's 
suggestion) and into "hadoop", "hadoop-hbase", and "hadoop-oozie". 
* Made kerberized hadoop services conditionally depend on the relevant keytabs
* Added a few dependencies that I missed in the last go 'round
* Pulled host_keytab and create_princ resource definitions out of 
kerberos::client:: up a level to kerberos::
* Simplified kerberos::host_keytab by removing princ_map (which made it 
slightly easier to define all the keytabs at once, which we don't do anymore)
                
      was (Author: ptr):
    * Removed hadoop-specific code from kerberos module (per Roman Shaposhnik's 
suggestion) and into "hadoop", "hadoop-hbase", and "hadoop-oozie". 
* Made kerberized hadoop services conditionally depend on the relevant keytabs
* Added a few dependencies that I missed in the last go 'round
* Pulled host_keytab and create_princ resource definitions out of 
kerberos::client:: up a level to kerberos::
                  
> Missing resource dependencies in puppet for secure clusters
> -----------------------------------------------------------
>
>                 Key: BIGTOP-396
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-396
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: 0.4.0
>            Reporter: Patrick Taylor Ramsey
>         Attachments: patch.20120208-04_20_37UTC.txt, patch.txt
>
>
> Currently, bigtop puppet will not run reliably for secure clusters, because 
> resources are likely to be executed in the wrong order.  I'm attaching a 
> patch that attempts to address this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to