Re: Prep for ranger-1.0.0 release

[Ramesh Mani]

+1 for the ranger 1.0.0 release.

Thanks,
Ramesh

On 2/22/18, 5:34 PM, "Sailaja Polavarapu" 
wrote:

>Rangers:
>As we are planning to do a release of ranger 1.0.0 soon (tentatively
>3/15/2018), I would like to create a branch ranger-1.0.0 for stabilizing
>the release. All of the fixes should go into the master which will track
>for our next major release and if needed will get cherry-picked into
>ranger-1.0.0 release.
>
>I am volunteering to be the release manager for ranger 1.0.0 release.
>Based on the discussion, current plan is to make the ranger 1.0.0 release
>with Hadoop 2.7.x (not Hadoop 3) and Atlas 0.8.2 as dependencies.
>
>Please let me know if any of you have any concerns and/or suggestions on
>the release process.
>
>Thanks,
>Sailaja.

Re: Prep for ranger-1.0.0 release

[Mehul Parikh]

+1 for Ranger 1.0.0 release.

On Fri, Feb 23, 2018 at 8:56 AM, Abhay Kulkarni 
wrote:

> +1 for Ranger 1.0.0 release.
>
> Thanks,
> -Abhay
>
> On 2/22/18, 7:15 PM, "Madhan Neethiraj"  wrote:
>
> >+1 for Ranger 1.0.0 release.
> >
> >Thanks,
> >Madhan
> >
> >
> >
> >
> >On 2/22/18, 5:54 PM, "Selvamohan Neethiraj"  wrote:
> >
> >Thanks Sailaja for driving this effort Š
> >
> >+1 for Ranger Release version 1.0.0
> >
> >Please let me know if you need any help on release related tasks ...
> >
> >Thanks,
> >Selva-
> >
> >> On Feb 22, 2018, at 8:34 PM, Sailaja Polavarapu
> > wrote:
> >>
> >> Rangers:
> >> As we are planning to do a release of ranger 1.0.0 soon
> >(tentatively 3/15/2018), I would like to create a branch ranger-1.0.0 for
> >stabilizing the release. All of the fixes should go into the master which
> >will track for our next major release and if needed will get
> >cherry-picked into ranger-1.0.0 release.
> >>
> >> I am volunteering to be the release manager for ranger 1.0.0
> >release. Based on the discussion, current plan is to make the ranger
> >1.0.0 release with Hadoop 2.7.x (not Hadoop 3) and Atlas 0.8.2 as
> >dependencies.
> >>
> >> Please let me know if any of you have any concerns and/or
> >suggestions on the release process.
> >>
> >> Thanks,
> >> Sailaja.
> >
> >
> >
> >
>
>


-- 

Thanks and regards,
Mehul Parikh

M: +91 98191 54446
E: xsme...@gmail.com

Re: Hadoop 3 support

[Ramesh Mani]

+1 for Ranger 1.0.0 release.

Thanks,
Ramesh

On 2/22/18, 3:17 PM, "Sailaja Polavarapu" 
wrote:

>Rangers:
> I am volunteering to be the release manager for ranger 1.0.0 release.
>Based on the below discussion I will start a new thread on kick of plan
>for the release soon. Please let me know if any of you have any concerns
>and/or suggestions.
>
>Thanks,
>Sailaja.
>
>On 1/22/18, 9:01 AM, "Colm O hEigeartaigh"  wrote:
>
>Sounds good, thanks!
>
>Colm.
>
>On Fri, Jan 19, 2018 at 10:59 PM, Madhan Neethiraj 
>wrote:
>
>> Colm,
>>
>> Atlas team is in the process of releasing 1.0.0-alpha, which should
>go out
>> next week. Once this release is out, Atlas team will get started on
>0.8.2
>> release; and this release should go out by end of the month.
>>
>> Thanks,
>> Madhan
>>
>>
>>
>>
>> On 1/19/18, 6:42 AM, "Colm O hEigeartaigh" 
>wrote:
>>
>> Are the Atlas team still planning on releasing 0.8.2 by the end
>of the
>> month? Are there features we need currently missing on the
>relevant
>> branch
>> in Atlas?
>>
>> Colm.
>>
>> On Wed, Jan 17, 2018 at 2:59 PM, Velmurugan Periasamy
>
>> wrote:
>>
>> > +1
>> >
>> > Another suggestion. Atlas is in the process
>> > 
>> 7d19573069eec90984d9d71277@%3Cdev.atlas.apache.org%3E>
>> > of releasing 1.0.0-alpha. Once this is complete, Ranger
>1.0.0-alpha
>> can be
>> > released based on that. Atlas team can be requested to back
>port any
>> > changes in Ranger/Atlas interface to 0.8.2, which can be used
>for
>> Ranger
>> > 1.0.0.
>> >
>> > From: Colm O hEigeartaigh 
>> > Reply-To: "dev@ranger.apache.org" , "
>> > cohei...@apache.org" 
>> > Date: Tuesday, January 9, 2018 at 10:40 AM
>> > To: Abhay Kulkarni 
>> > Cc: "dev@ranger.apache.org" , Ramesh
>Mani <
>> > rm...@hortonworks.com>
>> >
>> > Subject: Re: Hadoop 3 support
>> >
>> > +1 for this suggestion. Will there be any issue with
>downgrading
>> Atlas in
>> > Ranger from the current 1.0.0-SNAPSHOT version?
>> >
>> > Colm.
>> >
>> > On Mon, Jan 8, 2018 at 11:01 PM, Abhay Kulkarni <
>> akulka...@hortonworks.com
>> > >
>> > wrote:
>> >
>> > All,
>> >
>> > Here is another proposal for Ranger release 1.0.0.
>> >
>> > Atlas team is planning to make a Atlas-0.8.2 release towards
>the end
>> of
>> > this month. Once that is done, Ranger can do release 1.0.0
>with
>> dependency
>> > on Atlas 0.8.2 (without Hadoop 3.0.0).
>> >
>> > Thanks,
>> > -Abhay
>> >
>> > On 1/8/18, 12:23 PM, "Velmurugan Periasamy" <
>> vperias...@hortonworks.com on
>> > behalf of v...@apache.org> wrote:
>> >
>> > >+1 for getting the 1.0.0 release out soon.
>> > >
>> > >From:  Colm O hEigeartaigh 
>> > >Reply-To:  "dev@ranger.apache.org" ,
>> > >"cohei...@apache.org" 
>> > >Date:  Monday, January 8, 2018 at 12:37 PM
>> > >To:  Ramesh Mani 
>> > >Cc:  "dev@ranger.apache.org" 
>> > >Subject:  Re: Hadoop 3 support
>> > >
>> > >OK thanks. I will test the patch a bit more thoroughly before
>> submitting
>> > >for a RR.
>> > >
>> > >Just in regards as to whether to release 1.0.0 with or
>without
>> Hadoop
>> > >3.0.0...currently we have a dependency on Atlas
>1.0.0-SNAPSHOT.
>> What's the
>> > >timeline for releasing this? That would be the only thing
>blocking
>> getting
>> > >a 1.0.0 of Ranger out "quickly". If that's not imminent then
>I
>> guess that
>> > >gives us the time to get Ranger 1.0.0 out with Hadoop 3.0.0
>support.
>> > >
>> > >However, it's been ages since the last release so we should
>> probably not
>> > >wait too long before getting a release out.
>> > >
>> > >Colm.
>> > >
>> > >On Fri, Jan 5, 2018 at 6:39 PM, Ramesh Mani
>
>> > wrote:
>> > >
>> > >>  Thanks Colm,
>> > >>
>> > >>  I am fine with Option 1 or 3.  Do you want to create a RR
>for
>> this
>> > >>patch?
>> > >>
>> > >>  Thanks,
>> > >>  Ramesh
>> > >>
>> 

Re: Prep for ranger-1.0.0 release

[Abhay Kulkarni]

+1 for Ranger 1.0.0 release.

Thanks,
-Abhay

On 2/22/18, 7:15 PM, "Madhan Neethiraj"  wrote:

>+1 for Ranger 1.0.0 release.
>
>Thanks,
>Madhan
>
>
>
>
>On 2/22/18, 5:54 PM, "Selvamohan Neethiraj"  wrote:
>
>Thanks Sailaja for driving this effort Š
>
>+1 for Ranger Release version 1.0.0
>
>Please let me know if you need any help on release related tasks ...
>
>Thanks,
>Selva-
>
>> On Feb 22, 2018, at 8:34 PM, Sailaja Polavarapu
> wrote:
>> 
>> Rangers:
>> As we are planning to do a release of ranger 1.0.0 soon
>(tentatively 3/15/2018), I would like to create a branch ranger-1.0.0 for
>stabilizing the release. All of the fixes should go into the master which
>will track for our next major release and if needed will get
>cherry-picked into ranger-1.0.0 release.
>> 
>> I am volunteering to be the release manager for ranger 1.0.0
>release. Based on the discussion, current plan is to make the ranger
>1.0.0 release with Hadoop 2.7.x (not Hadoop 3) and Atlas 0.8.2 as
>dependencies.
>> 
>> Please let me know if any of you have any concerns and/or
>suggestions on the release process.
>> 
>> Thanks,
>> Sailaja.
>
>
>
>

Re: Prep for ranger-1.0.0 release

[Madhan Neethiraj]

+1 for Ranger 1.0.0 release.

Thanks,
Madhan




On 2/22/18, 5:54 PM, "Selvamohan Neethiraj"  wrote:

Thanks Sailaja for driving this effort …

+1 for Ranger Release version 1.0.0

Please let me know if you need any help on release related tasks ...

Thanks,
Selva-

> On Feb 22, 2018, at 8:34 PM, Sailaja Polavarapu 
 wrote:
> 
> Rangers:
> As we are planning to do a release of ranger 1.0.0 soon (tentatively 
3/15/2018), I would like to create a branch ranger-1.0.0 for stabilizing the 
release. All of the fixes should go into the master which will track for our 
next major release and if needed will get cherry-picked into ranger-1.0.0 
release.
> 
> I am volunteering to be the release manager for ranger 1.0.0 release. 
Based on the discussion, current plan is to make the ranger 1.0.0 release with 
Hadoop 2.7.x (not Hadoop 3) and Atlas 0.8.2 as dependencies.
> 
> Please let me know if any of you have any concerns and/or suggestions on 
the release process.
> 
> Thanks,
> Sailaja.

Re: Prep for ranger-1.0.0 release

[Selvamohan Neethiraj]

Thanks Sailaja for driving this effort …

+1 for Ranger Release version 1.0.0

Please let me know if you need any help on release related tasks ...

Thanks,
Selva-

> On Feb 22, 2018, at 8:34 PM, Sailaja Polavarapu  
> wrote:
> 
> Rangers:
> As we are planning to do a release of ranger 1.0.0 soon (tentatively 
> 3/15/2018), I would like to create a branch ranger-1.0.0 for stabilizing the 
> release. All of the fixes should go into the master which will track for our 
> next major release and if needed will get cherry-picked into ranger-1.0.0 
> release.
> 
> I am volunteering to be the release manager for ranger 1.0.0 release. Based 
> on the discussion, current plan is to make the ranger 1.0.0 release with 
> Hadoop 2.7.x (not Hadoop 3) and Atlas 0.8.2 as dependencies.
> 
> Please let me know if any of you have any concerns and/or suggestions on the 
> release process.
> 
> Thanks,
> Sailaja.



signature.asc
Description: Message signed with OpenPGP

Prep for ranger-1.0.0 release

[Sailaja Polavarapu]

Rangers:
As we are planning to do a release of ranger 1.0.0 soon (tentatively 
3/15/2018), I would like to create a branch ranger-1.0.0 for stabilizing the 
release. All of the fixes should go into the master which will track for our 
next major release and if needed will get cherry-picked into ranger-1.0.0 
release.

I am volunteering to be the release manager for ranger 1.0.0 release. Based on 
the discussion, current plan is to make the ranger 1.0.0 release with Hadoop 
2.7.x (not Hadoop 3) and Atlas 0.8.2 as dependencies.

Please let me know if any of you have any concerns and/or suggestions on the 
release process.

Thanks,
Sailaja.

Re: Hadoop 3 support

[Sailaja Polavarapu]

Rangers:
 I am volunteering to be the release manager for ranger 1.0.0 release. Based on 
the below discussion I will start a new thread on kick of plan for the release 
soon. Please let me know if any of you have any concerns and/or suggestions.

Thanks,
Sailaja.

On 1/22/18, 9:01 AM, "Colm O hEigeartaigh"  wrote:

Sounds good, thanks!

Colm.

On Fri, Jan 19, 2018 at 10:59 PM, Madhan Neethiraj 
wrote:

> Colm,
>
> Atlas team is in the process of releasing 1.0.0-alpha, which should go out
> next week. Once this release is out, Atlas team will get started on 0.8.2
> release; and this release should go out by end of the month.
>
> Thanks,
> Madhan
>
>
>
>
> On 1/19/18, 6:42 AM, "Colm O hEigeartaigh"  wrote:
>
> Are the Atlas team still planning on releasing 0.8.2 by the end of the
> month? Are there features we need currently missing on the relevant
> branch
> in Atlas?
>
> Colm.
>
> On Wed, Jan 17, 2018 at 2:59 PM, Velmurugan Periasamy 

> wrote:
>
> > +1
> >
> > Another suggestion. Atlas is in the process
> >  7d19573069eec90984d9d71277@%3Cdev.atlas.apache.org%3E>
> > of releasing 1.0.0-alpha. Once this is complete, Ranger 1.0.0-alpha
> can be
> > released based on that. Atlas team can be requested to back port any
> > changes in Ranger/Atlas interface to 0.8.2, which can be used for
> Ranger
> > 1.0.0.
> >
> > From: Colm O hEigeartaigh 
> > Reply-To: "dev@ranger.apache.org" , "
> > cohei...@apache.org" 
> > Date: Tuesday, January 9, 2018 at 10:40 AM
> > To: Abhay Kulkarni 
> > Cc: "dev@ranger.apache.org" , Ramesh Mani <
> > rm...@hortonworks.com>
> >
> > Subject: Re: Hadoop 3 support
> >
> > +1 for this suggestion. Will there be any issue with downgrading
> Atlas in
> > Ranger from the current 1.0.0-SNAPSHOT version?
> >
> > Colm.
> >
> > On Mon, Jan 8, 2018 at 11:01 PM, Abhay Kulkarni <
> akulka...@hortonworks.com
> > >
> > wrote:
> >
> > All,
> >
> > Here is another proposal for Ranger release 1.0.0.
> >
> > Atlas team is planning to make a Atlas-0.8.2 release towards the end
> of
> > this month. Once that is done, Ranger can do release 1.0.0 with
> dependency
> > on Atlas 0.8.2 (without Hadoop 3.0.0).
> >
> > Thanks,
> > -Abhay
> >
> > On 1/8/18, 12:23 PM, "Velmurugan Periasamy" <
> vperias...@hortonworks.com on
> > behalf of v...@apache.org> wrote:
> >
> > >+1 for getting the 1.0.0 release out soon.
> > >
> > >From:  Colm O hEigeartaigh 
> > >Reply-To:  "dev@ranger.apache.org" ,
> > >"cohei...@apache.org" 
> > >Date:  Monday, January 8, 2018 at 12:37 PM
> > >To:  Ramesh Mani 
> > >Cc:  "dev@ranger.apache.org" 
> > >Subject:  Re: Hadoop 3 support
> > >
> > >OK thanks. I will test the patch a bit more thoroughly before
> submitting
> > >for a RR.
> > >
> > >Just in regards as to whether to release 1.0.0 with or without
> Hadoop
> > >3.0.0...currently we have a dependency on Atlas 1.0.0-SNAPSHOT.
> What's the
> > >timeline for releasing this? That would be the only thing blocking
> getting
> > >a 1.0.0 of Ranger out "quickly". If that's not imminent then I
> guess that
> > >gives us the time to get Ranger 1.0.0 out with Hadoop 3.0.0 
support.
> > >
> > >However, it's been ages since the last release so we should
> probably not
> > >wait too long before getting a release out.
> > >
> > >Colm.
> > >
> > >On Fri, Jan 5, 2018 at 6:39 PM, Ramesh Mani 
> > wrote:
> > >
> > >>  Thanks Colm,
> > >>
> > >>  I am fine with Option 1 or 3.  Do you want to create a RR for
> this
> > >>patch?
> > >>
> > >>  Thanks,
> > >>  Ramesh
> > >>
> > >>  From: Colm O hEigeartaigh 
> > >>  Reply-To: "cohei...@apache.org" 
> > >>  Date: Friday, January 5, 2018 at 4:19 AM
> > >>  To: Ramesh Mani 
> > >>  Cc: 

[jira] [Commented] (RANGER-1981) Error in constructing base path for UI API when accessing Ranger via knox proxy without "/" at the end

[Nitin Galave (JIRA)]

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

Nitin Galave commented on RANGER-1981:
--

Committed to [apache 
master|https://github.com/apache/ranger/commit/605691882e08771c96371715f52bc34380dd4d27]
 branch.

> Error in constructing base path for UI API when accessing Ranger via knox 
> proxy without "/" at the end
> --
>
> Key: RANGER-1981
> URL: https://issues.apache.org/jira/browse/RANGER-1981
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: master, 0.7.2
>Reporter: Deepak Sharma
>Assignee: Nitin Galave
>Priority: Critical
> Fix For: 1.0.0
>
> Attachments: RANGER-1981.patch
>
>
> change similar to ATLAS-2171 has to be done in ranger also, it is happening 
> in ranger too.
> 1. Enabled knox proxy for ranger.
> 2.Accessed ranger UI via proxy using 
> [https://knox_gateway:8443/gateway/ui/r|https://knox_gateway:8443/gateway/ui/atlas]anger
> 3. Provided admin username and password and logged into ranger
> 4. Now, opened another tab in browser with URL
> UI is loaded without data because API path is not formed properly.
> If the URL is accessed with "/" at the end, logs in as admin user and all 
> operations work fine.



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

[jira] [Updated] (RANGER-1990) Add One-way SSL MySQL support in Ranger Admin

[Pradeep Agrawal (JIRA)]

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

Pradeep Agrawal updated RANGER-1990:

Attachment: RANGER-1990-1.patch

> Add One-way SSL MySQL support in Ranger Admin
> -
>
> Key: RANGER-1990
> URL: https://issues.apache.org/jira/browse/RANGER-1990
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 0.7.0
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: RANGER-1990-1.patch
>
>
> *Problem Statement:* Currently Ranger can communicate to SSL enabled MySQL 
> server but only if 2-way SSL config is provided, Ranger should support for 
> MySQL configured in Standard SSL(one-way) mode. 
> *Proposed Solution:* For mutual SSL (2-way) support keystore is required, 
> which is currently mandatory even if user want to connect to MySQL by using 
> Standard(1-way).  Proposed solution requires changes in install.properites to 
> have a property 'db_ssl_auth_type' which can have value '1-way' or '2-way'. 
> Default value shall be '2-way'. In case of '1-way', support keystore won't be 
> required however truststore is mandatory.



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

Review Request 65752: RANGER-1990: Add One-way SSL MySQL support in Ranger Admin

[Pradeep Agrawal]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65752/
---

Review request for ranger, bhavik patel, Gautam Borad, Abhay Kulkarni, Madhan 
Neethiraj, Mehul Parikh, Ramesh Mani, Sailaja Polavarapu, and Velmurugan 
Periasamy.


Bugs: RANGER-1990
https://issues.apache.org/jira/browse/RANGER-1990


Repository: ranger


Description
---

**Problem Statement:** Currently Ranger can communicate to SSL enabled MySQL 
server but only if 2-way SSL config is provided, Ranger should support for 
MySQL configured in Standard SSL(one-way) mode. 

**Proposed Solution:** For mutual SSL (2-way) support keystore is required, 
which is currently mandatory even if user want to connect to MySQL by using 
Standard(1-way).  Proposed solution requires changes in install.properites to 
have a property 'db_ssl_auth_type' which can have value '1-way' or '2-way'. 
Default value shall be '2-way'. In case of '1-way', support keystore won't be 
required however truststore is mandatory.


Diffs
-

  kms/config/kms-webapp/dbks-site.xml a098db1 
  kms/scripts/db_setup.py 663d60d 
  kms/scripts/dba_script.py c0dc7a4 
  kms/scripts/install.properties 5d4945e 
  kms/scripts/ranger-kms c279bc1 
  kms/scripts/setup.sh 2da1e96 
  kms/src/main/java/org/apache/hadoop/crypto/key/RangerKMSDB.java 87366b7 
  security-admin/scripts/db_setup.py 79d79d0 
  security-admin/scripts/dba_script.py c71ca42 
  security-admin/scripts/install.properties 268b8ac 
  security-admin/scripts/setup.sh 4d09bc2 
  security-admin/src/main/java/org/apache/ranger/common/PropertiesUtil.java 
1392421 
  security-admin/src/main/resources/conf.dist/ranger-admin-default-site.xml 
9dfc03d 


Diff: https://reviews.apache.org/r/65752/diff/1/


Testing
---

Tested Ranger admin and Ranger kms on SSL enabled MySQL with one-way and 
two-way ssl configurations.


Thanks,

Pradeep Agrawal

[jira] [Commented] (RANGER-1982) Error Improvement for Analytics Metric of Ranger Admin and Ranger Kms

[Fatima Amjad Khan (JIRA)]

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

Fatima Amjad Khan commented on RANGER-1982:
---

Committed on 
[Master|https://github.com/apache/ranger/commit/6239cb1a96b65f9d3cadbaeebab7e1aecd03343f]

> Error Improvement for Analytics Metric of Ranger Admin and Ranger Kms
> -
>
> Key: RANGER-1982
> URL: https://issues.apache.org/jira/browse/RANGER-1982
> Project: Ranger
>  Issue Type: Bug
>  Components: kms, Ranger
>Affects Versions: 1.0.0
>Reporter: Fatima Amjad Khan
>Assignee: Fatima Amjad Khan
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: RANGER-1982.patch
>
>
> Improve Error handling in analytical metrics of ranger admin and ranger kms



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

[jira] [Updated] (RANGER-1981) Error in constructing base path for UI API when accessing Ranger via knox proxy without "/" at the end

[Mehul Parikh (JIRA)]

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

Mehul Parikh updated RANGER-1981:
-
Summary: Error in constructing base path for UI API when accessing Ranger 
via knox proxy without "/" at the end  (was: Error in constructing base path 
for UI API when accessing Atlas via knox proxy without "/" at the end)

> Error in constructing base path for UI API when accessing Ranger via knox 
> proxy without "/" at the end
> --
>
> Key: RANGER-1981
> URL: https://issues.apache.org/jira/browse/RANGER-1981
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: master, 0.7.2
>Reporter: Deepak Sharma
>Assignee: Nitin Galave
>Priority: Critical
> Fix For: 1.0.0
>
> Attachments: RANGER-1981.patch
>
>
> change similar to ATLAS-2171 has to be done in ranger also, it is happening 
> in ranger too.
> 1. Enabled knox proxy for ranger.
> 2.Accessed ranger UI via proxy using 
> [https://knox_gateway:8443/gateway/ui/r|https://knox_gateway:8443/gateway/ui/atlas]anger
> 3. Provided admin username and password and logged into ranger
> 4. Now, opened another tab in browser with URL
> UI is loaded without data because API path is not formed properly.
> If the URL is accessed with "/" at the end, logs in as admin user and all 
> operations work fine.



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

Re: Review Request 65729: RANGER-1982 : Improve Error handling in analytical metrics of ranger admin and ranger kms

[Pradeep Agrawal]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65729/#review198103
---


Ship it!




Ship It!

- Pradeep Agrawal


On Feb. 21, 2018, 12:04 p.m., Fatima Khan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65729/
> ---
> 
> (Updated Feb. 21, 2018, 12:04 p.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, 
> Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, and 
> Sailaja Polavarapu.
> 
> 
> Bugs: RANGER-1982
> https://issues.apache.org/jira/browse/RANGER-1982
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Improve Error handling in analytical metrics of ranger admin and ranger kms
> 
> 
> Diffs
> -
> 
>   embeddedwebserver/scripts/ranger-admin-services.sh e902f73 
>   kms/scripts/ranger-kms c279bc1 
> 
> 
> Diff: https://reviews.apache.org/r/65729/diff/1/
> 
> 
> Testing
> ---
> 
> Tested with all the combination of commands possible for analytics metric.
> 
> 
> Thanks,
> 
> Fatima Khan
> 
>

[jira] [Updated] (RANGER-1990) Add One-way SSL MySQL support in Ranger Admin

[Pradeep Agrawal (JIRA)]

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

Pradeep Agrawal updated RANGER-1990:

Summary: Add One-way SSL MySQL support in Ranger Admin  (was: Add SSL 
enabled MySQL support in Ranger Admin)

> Add One-way SSL MySQL support in Ranger Admin
> -
>
> Key: RANGER-1990
> URL: https://issues.apache.org/jira/browse/RANGER-1990
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 0.7.0
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 1.0.0
>
>
> *Problem Statement:* Currently Ranger can communicate to SSL enabled MySQL 
> server but only if 2-way SSL config is provided, Ranger should support for 
> MySQL configured in Standard SSL(one-way) mode. 
> *Proposed Solution:* For mutual SSL (2-way) support keystore is required, 
> which is currently mandatory even if user want to connect to MySQL by using 
> Standard(1-way).  Proposed solution requires changes in install.properites to 
> have a property 'db_ssl_auth_type' which can have value '1-way' or '2-way'. 
> Default value shall be '2-way'. In case of '1-way', support keystore won't be 
> required however truststore is mandatory.



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

Re: Review Request 65747: RANGER-1981: Error in constructing base path for UI API when accessing Atlas via knox proxy without "/" at the end

[Mehul Parikh]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65747/#review198102
---


Ship it!




Ship It!

- Mehul Parikh


On Feb. 22, 2018, 5:44 a.m., Nitin Galave wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65747/
> ---
> 
> (Updated Feb. 22, 2018, 5:44 a.m.)
> 
> 
> Review request for ranger, Gautam Borad, Mehul Parikh, Pradeep Agrawal, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1981
> https://issues.apache.org/jira/browse/RANGER-1981
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> 1.Enabled knox proxy for ranger.
> 2.Accessed ranger UI via proxy using 
> https://knox_gateway:8443/gateway/ui/ranger
> 3.Provided admin username and password and logged into ranger
> 4.Now, opened another tab in browser with URL
> 
> UI is loaded without data because API path is not formed properly.
> 
> If the URL is accessed with "/" at the end, logs in as admin user and all 
> operations work fine.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/webapp/scripts/modules/RestCsrf.js c201c72 
> 
> 
> Diff: https://reviews.apache.org/r/65747/diff/1/
> 
> 
> Testing
> ---
> 
> Covered test cases :
> 1.By removing '/' in front of ranger 
> (https://:8443/gateway/ui/ranger)
> 2.By keeping '/' in front of ranger 
> (https://:8443/gateway/ui/ranger/)
> 3.Tested with KNOX SSO url.
> 4.Tested that when we hit KNOX proxy URL we get redirected to KNOX SSO.
> 5.By removing '/' in front of ranger after navigating to the different page.
> 
> 
> Thanks,
> 
> Nitin Galave
> 
>

[jira] [Updated] (RANGER-1990) Add SSL enabled MySQL support in Ranger Admin

[Pradeep Agrawal (JIRA)]

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

Pradeep Agrawal updated RANGER-1990:

Description: 
*Problem Statement:* Currently Ranger can communicate to SSL enabled MySQL 
server but only if 2-way SSL config is provided, Ranger should support for 
MySQL configured in Standard SSL(one-way) mode. 

*Proposed Solution:* For mutual SSL (2-way) support keystore is required, which 
is currently mandatory even if user want to connect to MySQL by using 
Standard(1-way).  Proposed solution requires changes in install.properites to 
have a property 'db_ssl_auth_type' which can have value '1-way' or '2-way'. 
Default value shall be '2-way'. In case of '1-way', support keystore won't be 
required however truststore is mandatory.

> Add SSL enabled MySQL support in Ranger Admin
> -
>
> Key: RANGER-1990
> URL: https://issues.apache.org/jira/browse/RANGER-1990
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 0.7.0
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 1.0.0
>
>
> *Problem Statement:* Currently Ranger can communicate to SSL enabled MySQL 
> server but only if 2-way SSL config is provided, Ranger should support for 
> MySQL configured in Standard SSL(one-way) mode. 
> *Proposed Solution:* For mutual SSL (2-way) support keystore is required, 
> which is currently mandatory even if user want to connect to MySQL by using 
> Standard(1-way).  Proposed solution requires changes in install.properites to 
> have a property 'db_ssl_auth_type' which can have value '1-way' or '2-way'. 
> Default value shall be '2-way'. In case of '1-way', support keystore won't be 
> required however truststore is mandatory.



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

Re: Review Request 65729: RANGER-1982 : Improve Error handling in analytical metrics of ranger admin and ranger kms

[Mehul Parikh]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65729/#review198101
---


Ship it!




Ship It!

- Mehul Parikh


On Feb. 21, 2018, 12:04 p.m., Fatima Khan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65729/
> ---
> 
> (Updated Feb. 21, 2018, 12:04 p.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, 
> Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, and 
> Sailaja Polavarapu.
> 
> 
> Bugs: RANGER-1982
> https://issues.apache.org/jira/browse/RANGER-1982
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Improve Error handling in analytical metrics of ranger admin and ranger kms
> 
> 
> Diffs
> -
> 
>   embeddedwebserver/scripts/ranger-admin-services.sh e902f73 
>   kms/scripts/ranger-kms c279bc1 
> 
> 
> Diff: https://reviews.apache.org/r/65729/diff/1/
> 
> 
> Testing
> ---
> 
> Tested with all the combination of commands possible for analytics metric.
> 
> 
> Thanks,
> 
> Fatima Khan
> 
>

[jira] [Created] (RANGER-1990) Add SSL enabled MySQL support in Ranger Admin

[Pradeep Agrawal (JIRA)]

Pradeep Agrawal created RANGER-1990:
---

 Summary: Add SSL enabled MySQL support in Ranger Admin
 Key: RANGER-1990
 URL: https://issues.apache.org/jira/browse/RANGER-1990
 Project: Ranger
  Issue Type: Improvement
  Components: Ranger
Affects Versions: 0.7.0
Reporter: Pradeep Agrawal
Assignee: Pradeep Agrawal
 Fix For: 1.0.0






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