date:20180709

[jira] [Commented] (RANGER-2112) Ranger KMS broken with JDK 8 update 171

2018-07-09 Thread Pradeep Agrawal (JIRA)



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

Pradeep Agrawal commented on RANGER-2112:
-

The issue can be resolved by updating the value of *jceks.key.serialFilter* 
property in /jre/lib/security/java.security file.
Usually the default value of jceks.key.serialFilter property is:
{code:java}
jceks.key.serialFilter = 
java.lang.Enum;java.security.KeyRep;java.security.KeyRep$Type;javax.crypto.spec.SecretKeySpec;!*
{code}
we need to add one more entry(*org.apache.hadoop.crypto.key.***) in it to make 
Ranger KMS working. Please note that the entries are separated by semicolon( ; 
). After adding the entry in jceks.key.serialFilter property it will look like:
{code:java}
jceks.key.serialFilter = 
java.lang.Enum;java.security.KeyRep;java.security.KeyRep$Type;javax.crypto.spec.SecretKeySpec;org.apache.hadoop.crypto.key.**;!*
{code}

Restart the Ranger-KMS service.

> Ranger KMS broken with JDK 8 update 171
> ---
>
> Key: RANGER-2112
> URL: https://issues.apache.org/jira/browse/RANGER-2112
> Project: Ranger
>  Issue Type: Bug
>  Components: kms
>Affects Versions: 0.7.0
>Reporter: Hernan Fernandez
>Assignee: Pradeep Agrawal
>Priority: Major
>
> After update to JDK 8 update 171 Ranger KMS UI
> 1) Ranger KMS UI > Encryption: will show the key list as the following.
> keyname (empty)
> Cipher (empty)
> Version 0
> Attributes (empty)
> Create (empty)
>  
> !image-2018-05-22-10-19-13-599.png!
>  
> 2) hadoop key -list -metadata
> Listing keys for KeyProvider: 
> org.apache.hadoop.crypto.key.kms.LoadBalancingKMSClientProvider@7d322cad
> testkey1 : null 
>  
>  *ROOT CAUSE*
>  This may be related to
> {code:java}
> New Features 
> security-libs/javax.crypto  
> Enhanced KeyStore Mechanisms
> A new security property named jceks.key.serialFilter has been introduced. If 
> this filter is configured, the JCEKS KeyStore uses it during the 
> deserialization of the encrypted Key object stored inside a SecretKeyEntry. 
> If it is not configured or if the filter result is UNDECIDED (for example, 
> none of the patterns match), then the filter configured by jdk.serialFilter 
> is consulted. If the system property jceks.key.serialFilter is also supplied, 
> it supersedes the security property value defined here. The filter pattern 
> uses the same format as jdk.serialFilter. The default pattern allows 
> java.lang.Enum, java.security.KeyRep, java.security.KeyRep$Type, and 
> javax.crypto.spec.SecretKeySpec but rejects all the others. Customers storing 
> a SecretKey that does not serialize to the above types must modify the filter 
> to make the key extractable.
> {code}
> http://www.oracle.com/technetwork/java/javase/8u171-relnotes-430.html
>  b) second option this is related to 3DES disabled on java.security (to be 
> tested)
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Ranger not executing policies...

2018-07-09 Thread Don Bosco Durai

I think I know the issue. My plugin code is the latest 1.x, while the Ranger 
Admin is 0.7. So even though the server is sending the correct data, the 1.x 
plugin code is not able to convert it to proper object (ServicePolicies).

Let me try after downgrading my plugin version.

Bosco


On 7/9/18, 4:52 PM, "Don Bosco Durai"  wrote:

Hi Abhay

Thanks for looking into it so quickly.

Good catch on the issue. I have given public access to *,*,*. However, when 
the policies are pulled from Spark, the resources are not coming properly. I 
think, none of the resources are coming. I might have to dig deeper to see the 
root cause.

I have attached 2 files. hiveServer2_brown_hive.json is downloaded by 
HiveServer2 and hiveCLI_brown_hive.json is downloaded by SparkSQL Thrift Server.

hiveServer2_brown_hive.json
  "resources": {
"database": {
  "values": [
"*"
  ],
  "isExcludes": false,
  "isRecursive": false
},

hiveCLI_brown_hive.json
  "resources": {},

Thanks

Bosco


On 7/9/18, 4:34 PM, "Abhay Kulkarni"  wrote:

Bosco,

It appears from the log (lines 6, 7)  that the Trie search for resource 
(database=default) did not find any policies. Per lines 3 and 5, it looks like 
the name of the policy resource is set to 'database' instead of 'default'. 
Could you please check if the policies are correctly downloaded to the 
component?

Thanks,
-Abhay


From: Don Bosco Durai mailto:bo...@apache.org>>
Reply-To: "dev@ranger.apache.org" 
mailto:dev@ranger.apache.org>>
Date: Monday, July 9, 2018 at 3:51 PM
To: ranger mailto:dev@ranger.apache.org>>
Subject: Ranger not executing policies...

Hi Abhay

I have extended the work done by Kent Yao for supporting Ranger with 
SparkSQL ThriftServer. I managed to integrate with the Ranger master branch and 
also the Ranger authorizer code is called, but I always get denied by Ranger 
authorizer.

Earlier in the logs, I can see the policies getting downloaded and also 
the local .json file is getting created. However, when the check privileges 
call is called, it seems it is not able to get it. I am not sure if custom 
class loaders are interfering. Is it possible to dump the policies when the 
authorization code is called?

I have attached part of the logs. Let me know if you can guide me in 
the right direction?

Thanks

Bosco

[jira] [Resolved] (RANGER-2147) Release Ranger 1.1.0

2018-07-09 Thread Velmurugan Periasamy (JIRA)



 [ 
https://issues.apache.org/jira/browse/RANGER-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Velmurugan Periasamy resolved RANGER-2147.
--
Resolution: Fixed

> Release Ranger 1.1.0
> 
>
> Key: RANGER-2147
> URL: https://issues.apache.org/jira/browse/RANGER-2147
> Project: Ranger
>  Issue Type: Task
>  Components: Ranger
>Reporter: Velmurugan Periasamy
>Assignee: Velmurugan Periasamy
>Priority: Major
> Fix For: 1.1.0
>
>
> Track release activities for Ranger 1.1.0



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (RANGER-2147) Release Ranger 1.1.0

2018-07-09 Thread Velmurugan Periasamy (JIRA)



 [ 
https://issues.apache.org/jira/browse/RANGER-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Velmurugan Periasamy updated RANGER-2147:
-
Issue Type: Task  (was: Bug)

> Release Ranger 1.1.0
> 
>
> Key: RANGER-2147
> URL: https://issues.apache.org/jira/browse/RANGER-2147
> Project: Ranger
>  Issue Type: Task
>  Components: Ranger
>Reporter: Velmurugan Periasamy
>Assignee: Velmurugan Periasamy
>Priority: Major
> Fix For: 1.1.0
>
>
> Track release activities for Ranger 1.1.0



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Ranger not executing policies...

2018-07-09 Thread Abhay Kulkarni

Bosco,

It appears from the log (lines 6, 7)  that the Trie search for resource 
(database=default) did not find any policies. Per lines 3 and 5, it looks like 
the name of the policy resource is set to 'database' instead of 'default'. 
Could you please check if the policies are correctly downloaded to the 
component?

Thanks,
-Abhay


From: Don Bosco Durai mailto:bo...@apache.org>>
Reply-To: "dev@ranger.apache.org" 
mailto:dev@ranger.apache.org>>
Date: Monday, July 9, 2018 at 3:51 PM
To: ranger mailto:dev@ranger.apache.org>>
Subject: Ranger not executing policies...

Hi Abhay

I have extended the work done by Kent Yao for supporting Ranger with SparkSQL 
ThriftServer. I managed to integrate with the Ranger master branch and also the 
Ranger authorizer code is called, but I always get denied by Ranger authorizer.

Earlier in the logs, I can see the policies getting downloaded and also the 
local .json file is getting created. However, when the check privileges call is 
called, it seems it is not able to get it. I am not sure if custom class 
loaders are interfering. Is it possible to dump the policies when the 
authorization code is called?

I have attached part of the logs. Let me know if you can guide me in the right 
direction?

Thanks

Bosco

Ranger not executing policies...

2018-07-09 Thread Don Bosco Durai

Hi Abhay

 

I have extended the work done by Kent Yao for supporting Ranger with SparkSQL 
ThriftServer. I managed to integrate with the Ranger master branch and also the 
Ranger authorizer code is called, but I always get denied by Ranger authorizer.

 

Earlier in the logs, I can see the policies getting downloaded and also the 
local .json file is getting created. However, when the check privileges call is 
called, it seems it is not able to get it. I am not sure if custom class 
loaders are interfering. Is it possible to dump the policies when the 
authorization code is called?

 

I have attached part of the logs. Let me know if you can guide me in the right 
direction?

 

Thanks

 

Bosco

 

18/07/09 21:58:21 DEBUG RangerPolicyRepository: ==> 
RangerPolicyRepository.setAuditEnabledFromCache()
18/07/09 21:58:21 DEBUG RangerPolicyRepository: <== 
RangerPolicyRepository.setAuditEnabledFromCache():false
18/07/09 21:58:21 INFO RangerPolicyRepository: DELETE ME: 
policyResourceTrie={database=resourceName=database; optIgnoreCase=true; 
optWildcard=true; wildcardChars=*?{}\; nodeCount=1; leafNodeCount=1; 
singleChildNodeCount=0; maxDepth=1; evaluatorListCount=0; 
wildcardEvaluatorListCount=0; evaluatorListRefCount=0; 
wildcardEvaluatorListRefCount=0, udf=resourceName=udf; optIgnoreCase=true; 
optWildcard=true; wildcardChars=*?{}\; nodeCount=1; leafNodeCount=1; 
singleChildNodeCount=0; maxDepth=1; evaluatorListCount=0; 
wildcardEvaluatorListCount=0; evaluatorListRefCount=0; 
wildcardEvaluatorListRefCount=0, hiveservice=resourceName=hiveservice; 
optIgnoreCase=true; optWildcard=true; wildcardChars=*?{}\; nodeCount=1; 
leafNodeCount=1; singleChildNodeCount=0; maxDepth=1; evaluatorListCount=0; 
wildcardEvaluatorListCount=0; evaluatorListRefCount=0; 
wildcardEvaluatorListRefCount=0, column=resourceName=column; 
optIgnoreCase=true; optWildcard=true; wildcardChars=*?{}\; nodeCount=1; 
leafNodeCount=1; singleChildNodeCount=0; maxDepth=1; evaluatorListCount=0; 
wildcardEvaluatorListCount=0; evaluatorListRefCount=0; 
wildcardEvaluatorListRefCount=0, url=resourceName=url; optIgnoreCase=true; 
optWildcard=true; wildcardChars=*?{}\; nodeCount=1; leafNodeCount=1; 
singleChildNodeCount=0; maxDepth=1; evaluatorListCount=0; 
wildcardEvaluatorListCount=0; evaluatorListRefCount=0; 
wildcardEvaluatorListRefCount=0, table=resourceName=table; optIgnoreCase=true; 
optWildcard=true; wildcardChars=*?{}\; nodeCount=1; leafNodeCount=1; 
singleChildNodeCount=0; maxDepth=1; evaluatorListCount=0; 
wildcardEvaluatorListCount=0; evaluatorListRefCount=0; 
wildcardEvaluatorListRefCount=0}
18/07/09 21:58:21 INFO RangerPolicyRepository: DELETE ME: 
resourceKeys=[database]
18/07/09 21:58:21 INFO RangerPolicyRepository: DELETE ME: 
resourceName=database, trie=resourceName=database; optIgnoreCase=true; 
optWildcard=true; wildcardChars=*?{}\; nodeCount=1; leafNodeCount=1; 
singleChildNodeCount=0; maxDepth=1; evaluatorListCount=0; 
wildcardEvaluatorListCount=0; evaluatorListRefCount=0; 
wildcardEvaluatorListRefCount=0
18/07/09 21:58:21 DEBUG RangerResourceTrie: ==> 
RangerResourceTrie.getEvaluatorsForResource(default)
18/07/09 21:58:21 DEBUG RangerResourceTrie: <== 
RangerResourceTrie.getEvaluatorsForResource(default): evaluatorCount=0
18/07/09 21:58:21 DEBUG RangerPolicyRepository: <== 
RangerPolicyRepository.getLikelyMatchPolicyEvaluators(default): evaluatorCount=0
18/07/09 21:58:21 INFO RangerPolicyEngineImpl: DELETE ME: evaluators.size=0, 
request.getResource()=RangerResourceImpl={ownerUser={null} 
elements={database=default; } }, policyType=0, resource.getAsString()=default
18/07/09 21:58:21 DEBUG RangerPolicyRepository: ==> 
RangerPolicyRepository.storeAuditEnabledInCache()
18/07/09 21:58:21 DEBUG RangerPolicyRepository: <== 
RangerPolicyRepository.storeAuditEnabledInCache()
18/07/09 21:58:21 DEBUG RangerPolicyEngineImpl: <== 
RangerPolicyEngineImpl.evaluatePoliciesNoAudit(RangerAccessRequestImpl={resource={RangerResourceImpl={ownerUser={null}
 elements={database=default; } }} accessType={_any} user={hive} 
userGroups={hadoop } accessTime={Mon Jul 09 21:58:21 UTC 2018} 
clientIPAddress={null} forwardedAddresses={} remoteIPAddress={null} 
clientType={HIVECLI} action={METADATA OPERATION} requestData={null} 
sessionId={d69a2cc0-7654-4dcd-8aaa-6f81b9c9026f} resourceMatchingScope={SELF} 
clusterName={brown} context={token:USER={hive} } }, policyType =0): 
RangerAccessResult={isAccessDetermined={false} isAllowed={false} 
isAuditedDetermined={false} isAudited={false} policyType={0} policyId={-1} 
auditPolicyId={-1} evaluatedPoliciesCount={0} reason={null} additionalInfo={}}
18/07/09 21:58:21 DEBUG usage: [PERF] 
RangerPolicyEngine.usage(accessingUser=hive,accessedResource=default,accessType=_any,evaluatedPoliciesCount=0):
 0
18/07/09 21:58:21 DEBUG request: [PERF] 
RangerPolicyEngine.evaluatePolicies(requestHashCode=a3f1f32_0): 3
18/07/09 21:58:21 DEBUG RangerPolicyEngineImpl: <== 
RangerPolicyEngineImpl.evaluatePolicies(RangerAccessRequestImpl={

[RESULT] [VOTE] Apache Ranger Release 1.1.0-rc2

2018-07-09 Thread Velmurugan Periasamy

Hello Rangers:

Thank you so much for your efforts to validate Apache Ranger 1.1.0 release 
candidate #2 and your feedback/vote.

More than 72 hours have passed and the current vote thread is considered 
concluded and passes with the following resolution:

Six +1 votes from the following PPMC member(s):

+1 Abhay Kulkarni
+1 Colm O hEigeartaigh
+1 Don Bosco Durai
+1 Madhanmohan Neethiraj
+1 Ramesh Mani
+1 Velmurugan Periasamy

Eight +1 votes from the following non-PPMC member(s):

+1 Bhavik Patel
+1 Mehul Parikh
+1 Nitin Galave
+1 Peng Jianhua
+1 Pradeep Agrawal
+1 Srikanth Venkat
+1 Vipin Rathor
+1 Vishal Suvagia


Zero -1 votes:


I will start the process of moving the release artifacts to the mirrors and 
other release activities. 


Voting thread for reference - 
https://lists.apache.org/thread.html/c5a80745b890f03de25590aab67c8a2e634dedd58270bc3d13055c79@%3Cdev.ranger.apache.org%3E
 


Issues fixed in this release - 
https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+1.1.0+-+Release+Notes

Thank you,
Vel



On 7/5/18, 12:56 PM, "Velmurugan Periasamy" mailto:v...@apache.org>> wrote:

Hello Rangers:

Thank you for your contribution to Apache Ranger community. Apache Ranger
1.1.0 release candidate #2 is now available for a vote within dev
community. Note: RC1
(https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc1/ 
) is canceled
due to https://issues.apache.org/jira/browse/RANGER-1951 
.

Links to RC2 release artifacts are given below. Kindly request all
Rangers (Dev's & PMC members) to review and vote on this release.

Git tag for the release:
https://github.com/apache/ranger/tree/ranger-1.1.0-rc2 
 (last commit id:
1732536f1de4ac3f1699f660e089385487004261)


Sources for the release:
https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/apache-ranger-1.1 
.
0.tar.gz

Source release verification:
PGP Signature:
https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/apache-ranger-1.1 
.
0.tar.gz.asc
  
MD5/SHA Hashes:
https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/apache-ranger-1.1 
.
0.tar.gz.mds
https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/apache-ranger-1.1 
.
0.tar.gz.sha1
https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/apache-ranger-1.1 
.
0.tar.gz.sha256
https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/apache-ranger-1.1 
.
0.tar.gz.sha512


Keys to verify the signature of the release artifact are available at:
https://dist.apache.org/repos/dist/release/ranger/KEYS 


Release Notes:
https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+1.1.0+-+R 

elease+Notes

Build verification steps can be found at:
   http://ranger.apache.org/quick_start_guide.html 


The vote will be open for at least 72 hours or until necessary number of
votes are reached.
[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)
Here is my +1

Thank you,
Vel

Re: [VOTE] Apache Ranger Release 1.1.0-rc2

2018-07-09 Thread Jianhua Peng

+1

On 2018/07/05 19:56:31, Velmurugan Periasamy  wrote: 
> Hello Rangers:
> 
> Thank you for your contribution to Apache Ranger community. Apache Ranger 
> 1.1.0 release candidate #2 is now available for a vote within dev community. 
> Note: RC1 (https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc1/) is 
> canceled due to https://issues.apache.org/jira/browse/RANGER-1951. 
> 
> Links to RC2 release artifacts are given below. Kindly request all Rangers 
> (Dev's & PMC members) to review and vote on this release.
> 
>  
> Git tag for the release:
> https://github.com/apache/ranger/tree/ranger-1.1.0-rc2 (last commit id:  
> 1732536f1de4ac3f1699f660e089385487004261)
> 
> 
> Sources for the release:
> https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/apache-ranger-1.1.0.tar.gz
> 
>  
> Source release verification:
>  
> PGP Signature:
> https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/apache-ranger-1.1.0.tar.gz.asc
>   
> MD5/SHA Hashes:
> https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/apache-ranger-1.1.0.tar.gz.mds
> https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/apache-ranger-1.1.0.tar.gz.sha1
> https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/apache-ranger-1.1.0.tar.gz.sha256
> https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/apache-ranger-1.1.0.tar.gz.sha512
> 
> 
> Keys to verify the signature of the release artifact are available at: 
> https://dist.apache.org/repos/dist/release/ranger/KEYS
>  
> 
> Release Notes:
> https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+1.1.0+-+Release+Notes
>  
> 
> Build verification steps can be found at:
>http://ranger.apache.org/quick_start_guide.html
> 
>  
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>  
> Here is my +1
> 
> Thank you,
> Vel

Re: [VOTE] Apache Ranger Release 1.1.0-rc2

2018-07-09 Thread Colm O hEigeartaigh

+1. (Minor thing - the NOTICE year needs to be updated).

Colm.

On Mon, Jul 9, 2018 at 3:16 PM, Nitin Galave  wrote:

> 1. Successfully extracted tar file.
> 2. Clean, build and test ran successfully.
>
> +1
>
> Thanks,
>
> Nitin Galave.
>
> On Mon, Jul 9, 2018 at 10:29 AM Bhavik Patel 
> wrote:
>
> > +1 for Apache Ranger 1.1.0 rc2.
> >
> > Regard,
> > Bhavik Patel
> >
> > On Sun, Jul 8, 2018 at 1:55 PM, Madhan Neethiraj 
> > wrote:
> >
> > > +1 for Apache Ranger 1.1.0 rc2.
> > >
> > > Thanks,
> > > Madhan
> > >
> > >
> > >
> > > On 7/5/18, 12:56 PM, "Velmurugan Periasamy"  wrote:
> > >
> > > Hello Rangers:
> > >
> > > Thank you for your contribution to Apache Ranger community. Apache
> > > Ranger 1.1.0 release candidate #2 is now available for a vote within
> dev
> > > community. Note: RC1 (
> > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-
> > > rc1/) is canceled due to
> > https://issues.apache.org/jira/browse/RANGER-1951.
> > >
> > >
> > > Links to RC2 release artifacts are given below. Kindly request all
> > > Rangers (Dev's & PMC members) to review and vote on this release.
> > >
> > >
> > > Git tag for the release:
> > > https://github.com/apache/ranger/tree/ranger-1.1.0-rc2 (last
> commit
> > > id:  1732536f1de4ac3f1699f660e089385487004261)
> > >
> > >
> > > Sources for the release:
> > > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > > apache-ranger-1.1.0.tar.gz
> > >
> > >
> > > Source release verification:
> > >
> > > PGP Signature:
> > > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > > apache-ranger-1.1.0.tar.gz.asc
> > >
> > > MD5/SHA Hashes:
> > > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > > apache-ranger-1.1.0.tar.gz.mds
> > > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > > apache-ranger-1.1.0.tar.gz.sha1
> > > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > > apache-ranger-1.1.0.tar.gz.sha256
> > > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > > apache-ranger-1.1.0.tar.gz.sha512
> > >
> > >
> > > Keys to verify the signature of the release artifact are available
> > at:
> > > https://dist.apache.org/repos/dist/release/ranger/KEYS
> > >
> > >
> > > Release Notes:
> > > https://cwiki.apache.org/confluence/display/RANGER/
> > > Apache+Ranger+1.1.0+-+Release+Notes
> > >
> > >
> > > Build verification steps can be found at:
> > >http://ranger.apache.org/quick_start_guide.html
> > >
> > >
> > > The vote will be open for at least 72 hours or until necessary
> number
> > > of votes are reached.
> > > [ ] +1  approve
> > > [ ] +0  no opinion
> > > [ ] -1  disapprove (and reason why)
> > >
> > > Here is my +1
> > >
> > > Thank you,
> > > Vel
> > >
> > >
> > >
> > >
> > >
> >
>
>
> --
>
>
> *Thanks,Nitin Galave.*
>



-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Register now for ApacheCon and save $250

2018-07-09 Thread Rich Bowen


Greetings, Apache software enthusiasts!

(You’re getting this because you’re on one or more dev@ or users@ lists 
for some Apache Software Foundation project.)


ApacheCon North America, in Montreal, is now just 80 days away, and 
early bird prices end in just two weeks - on July 21. Prices will be 
going up from $550 to $800 so register NOW to save $250, at 
http://apachecon.com/acna18


And don’t forget to reserve your hotel room. We have negotiated a 
special rate and the room block closes August 24. 
http://www.apachecon.com/acna18/venue.html


Our schedule includes over 100 talks and we’ll be featuring talks from 
dozens of ASF projects.,  We have inspiring keynotes from some of the 
brilliant members of our community and the wider tech space, including:


 * Myrle Krantz, PMC chair for Apache Fineract, and leader in the open 
source financing space
 * Cliff Schmidt, founder of Literacy Bridge (now Amplio) and creator 
of the Talking Book project

 * Bridget Kromhout, principal cloud developer advocate at Microsoft
 * Euan McLeod, Comcast engineer, and pioneer in streaming video

We’ll also be featuring tracks for Geospatial science, Tomcat, 
Cloudstack, and Big Data, as well as numerous other fields where Apache 
software is leading the way. See the full schedule at 
http://apachecon.com/acna18/schedule.html


As usual we’ll be running our Apache BarCamp, the traditional ApacheCon 
Hackathon, and the Wednesday evening Lighting Talks, too, so you’ll want 
to be there.


Register today at http://apachecon.com/acna18 and we’ll see you in Montreal!

--
Rich Bowen
VP, Conferences, The Apache Software Foundation
h...@apachecon.com
@ApacheCon

Re: [VOTE] Apache Ranger Release 1.1.0-rc2

2018-07-09 Thread Nitin Galave

1. Successfully extracted tar file.
2. Clean, build and test ran successfully.

+1

Thanks,

Nitin Galave.

On Mon, Jul 9, 2018 at 10:29 AM Bhavik Patel 
wrote:

> +1 for Apache Ranger 1.1.0 rc2.
>
> Regard,
> Bhavik Patel
>
> On Sun, Jul 8, 2018 at 1:55 PM, Madhan Neethiraj 
> wrote:
>
> > +1 for Apache Ranger 1.1.0 rc2.
> >
> > Thanks,
> > Madhan
> >
> >
> >
> > On 7/5/18, 12:56 PM, "Velmurugan Periasamy"  wrote:
> >
> > Hello Rangers:
> >
> > Thank you for your contribution to Apache Ranger community. Apache
> > Ranger 1.1.0 release candidate #2 is now available for a vote within dev
> > community. Note: RC1 (
> https://dist.apache.org/repos/dist/dev/ranger/1.1.0-
> > rc1/) is canceled due to
> https://issues.apache.org/jira/browse/RANGER-1951.
> >
> >
> > Links to RC2 release artifacts are given below. Kindly request all
> > Rangers (Dev's & PMC members) to review and vote on this release.
> >
> >
> > Git tag for the release:
> > https://github.com/apache/ranger/tree/ranger-1.1.0-rc2 (last commit
> > id:  1732536f1de4ac3f1699f660e089385487004261)
> >
> >
> > Sources for the release:
> > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > apache-ranger-1.1.0.tar.gz
> >
> >
> > Source release verification:
> >
> > PGP Signature:
> > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > apache-ranger-1.1.0.tar.gz.asc
> >
> > MD5/SHA Hashes:
> > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > apache-ranger-1.1.0.tar.gz.mds
> > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > apache-ranger-1.1.0.tar.gz.sha1
> > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > apache-ranger-1.1.0.tar.gz.sha256
> > https://dist.apache.org/repos/dist/dev/ranger/1.1.0-rc2/
> > apache-ranger-1.1.0.tar.gz.sha512
> >
> >
> > Keys to verify the signature of the release artifact are available
> at:
> > https://dist.apache.org/repos/dist/release/ranger/KEYS
> >
> >
> > Release Notes:
> > https://cwiki.apache.org/confluence/display/RANGER/
> > Apache+Ranger+1.1.0+-+Release+Notes
> >
> >
> > Build verification steps can be found at:
> >http://ranger.apache.org/quick_start_guide.html
> >
> >
> > The vote will be open for at least 72 hours or until necessary number
> > of votes are reached.
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Here is my +1
> >
> > Thank you,
> > Vel
> >
> >
> >
> >
> >
>


-- 


*Thanks,Nitin Galave.*

[jira] [Commented] (RANGER-2112) Ranger KMS broken with JDK 8 update 171

Re: Ranger not executing policies...

[jira] [Resolved] (RANGER-2147) Release Ranger 1.1.0

[jira] [Updated] (RANGER-2147) Release Ranger 1.1.0

Re: Ranger not executing policies...

Ranger not executing policies...

[RESULT] [VOTE] Apache Ranger Release 1.1.0-rc2

Re: [VOTE] Apache Ranger Release 1.1.0-rc2

Re: [VOTE] Apache Ranger Release 1.1.0-rc2

Register now for ApacheCon and save $250

Re: [VOTE] Apache Ranger Release 1.1.0-rc2

11 matches

Site Navigation

Mail list logo

Footer information