date:20171212

[jira] [Created] (KNOX-1145) Upgrade Jackson due to CVE-2017-7525

2017-12-12 Thread Colm O hEigeartaigh (JIRA)

Colm O hEigeartaigh created KNOX-1145:
-

 Summary: Upgrade Jackson due to CVE-2017-7525
 Key: KNOX-1145
 URL: https://issues.apache.org/jira/browse/KNOX-1145
 Project: Apache Knox
  Issue Type: Improvement
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
 Fix For: 1.0.0


Apache Knox currently ships the Jackson databind jar version 2.2.2. However, 
there is a security advisory CVE-2017-7525 released for this component:

https://github.com/FasterXML/jackson-databind/issues/1599

We should upgrade Jackson to pick this fix up.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1145) Upgrade Jackson due to CVE-2017-7525

2017-12-12 Thread Colm O hEigeartaigh (JIRA)


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

Colm O hEigeartaigh updated KNOX-1145:
--
Status: Patch Available  (was: Open)

> Upgrade Jackson due to CVE-2017-7525
> 
>
> Key: KNOX-1145
> URL: https://issues.apache.org/jira/browse/KNOX-1145
> Project: Apache Knox
>  Issue Type: Improvement
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
> Fix For: 1.0.0
>
> Attachments: KNOX-1145.patch
>
>
> Apache Knox currently ships the Jackson databind jar version 2.2.2. However, 
> there is a security advisory CVE-2017-7525 released for this component:
> https://github.com/FasterXML/jackson-databind/issues/1599
> We should upgrade Jackson to pick this fix up.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1145) Upgrade Jackson due to CVE-2017-7525

2017-12-12 Thread Colm O hEigeartaigh (JIRA)


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

Colm O hEigeartaigh updated KNOX-1145:
--
Attachment: KNOX-1145.patch

A patch to upgrade to Jackson 2.8.10. I also removed a duplicate test 
dependency that I noticed.

> Upgrade Jackson due to CVE-2017-7525
> 
>
> Key: KNOX-1145
> URL: https://issues.apache.org/jira/browse/KNOX-1145
> Project: Apache Knox
>  Issue Type: Improvement
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
> Fix For: 1.0.0
>
> Attachments: KNOX-1145.patch
>
>
> Apache Knox currently ships the Jackson databind jar version 2.2.2. However, 
> there is a security advisory CVE-2017-7525 released for this component:
> https://github.com/FasterXML/jackson-databind/issues/1599
> We should upgrade Jackson to pick this fix up.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

2017-12-12 Thread Phil Zampino (JIRA)


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

Phil Zampino updated KNOX-1144:
---
Description: 
Changes to existing provider configurations don't result in updates to the 
existing descriptors which reference them.

This is a consequence of changing the startup behavior wrt simple descriptors. 
Now that existing simple descriptors no longer trigger topology regeneration at 
startup (unless they've changed since shutdown), the relationships between 
simple descriptors and the provider configurations they reference are not being 
established.

These relationships need to be established when the TopologyService is 
initialized.


  was:
Changes to existing provider configurations don't result in updates to the 
existing descriptors which reference them.

This is a consequence of changing the startup behavior wrt simple descriptors. 
Now that existing simple descriptors no longer trigger topology regeneration at 
startup (unless they've changed since shutdown), the relationships between 
simple descriptors and the provider configurations they reference are not being 
established.

These relationships need to established when the TopologyService is initialized.



> Provider Configuration Reference Relationships Aren't Established For 
> Existing Descriptors at Gateway Startup
> -
>
> Key: KNOX-1144
> URL: https://issues.apache.org/jira/browse/KNOX-1144
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
>
> Changes to existing provider configurations don't result in updates to the 
> existing descriptors which reference them.
> This is a consequence of changing the startup behavior wrt simple 
> descriptors. Now that existing simple descriptors no longer trigger topology 
> regeneration at startup (unless they've changed since shutdown), the 
> relationships between simple descriptors and the provider configurations they 
> reference are not being established.
> These relationships need to be established when the TopologyService is 
> initialized.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

2017-12-12 Thread Phil Zampino (JIRA)


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

Phil Zampino updated KNOX-1144:
---
Attachment: KNOX-1144.patch

> Provider Configuration Reference Relationships Aren't Established For 
> Existing Descriptors at Gateway Startup
> -
>
> Key: KNOX-1144
> URL: https://issues.apache.org/jira/browse/KNOX-1144
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
> Attachments: KNOX-1144.patch
>
>
> Changes to existing provider configurations don't result in updates to the 
> existing descriptors which reference them.
> This is a consequence of changing the startup behavior wrt simple 
> descriptors. Now that existing simple descriptors no longer trigger topology 
> regeneration at startup (unless they've changed since shutdown), the 
> relationships between simple descriptors and the provider configurations they 
> reference are not being established.
> These relationships need to be established when the TopologyService is 
> initialized.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

2017-12-12 Thread Phil Zampino (JIRA)


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

Phil Zampino updated KNOX-1144:
---
Status: Patch Available  (was: In Progress)

Attached KNOX-1144.patch

The TopologyService now determines provider configuration reference 
relationships for any existing simple descriptors at gateway startup time. This 
should address the issue.

Furthermore, the remote configuration monitor immediately downloads any 
existing provider configurations (which either do not exist locally, or are 
different from the local contents), to avoid any inconsistent behavior due to 
downloading a remote descriptor before its referenced provider config; I've not 
ever seen this happen yet, but this change should prevent any potential for 
inconsistent behavior wrt updating descriptors when their referenced provider 
configs change.


> Provider Configuration Reference Relationships Aren't Established For 
> Existing Descriptors at Gateway Startup
> -
>
> Key: KNOX-1144
> URL: https://issues.apache.org/jira/browse/KNOX-1144
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
> Attachments: KNOX-1144.patch
>
>
> Changes to existing provider configurations don't result in updates to the 
> existing descriptors which reference them.
> This is a consequence of changing the startup behavior wrt simple 
> descriptors. Now that existing simple descriptors no longer trigger topology 
> regeneration at startup (unless they've changed since shutdown), the 
> relationships between simple descriptors and the provider configurations they 
> reference are not being established.
> These relationships need to be established when the TopologyService is 
> initialized.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Release Apache Knox 0.14.0 rc 2

2017-12-12 Thread Philip Zampino

>
> 1. it can get confusing trying to keep track of where topologies are coming
> from - I believe we have a JIRA for CLI listing of remote descriptors and
> provider configs already - that will help


KNOX-1137  is the JIRA
which addresses this.


2. it seems that you can get into a state where if you have an XML issue in
> a provider config that just fixing the provider config in ZK doesn't result
> in the topology getting repulled - needs a JIRA and additional
> investigation


KNOX-1144  addresses this;
I believe it involves provider configurations and descriptors that exist
prior to gateway start-up.



On Mon, Dec 11, 2017 at 4:45 PM, larry mccay  wrote:

> * built from source and ran unit tests
> * verified signatures
> * ran knox samples for webhdfs, hive, hbase
> * used nodejs client to interact with webhdfs and webhcat
>
> * ran knoxshell samples noted:
> 1. logging seems broken and is printing to console - at least with default
> config - will need to file a JIRA
> 2. hive samples are difficult to run through executable jar due to needing
> to add hive jars to classpath - will file JIRA and write article to share a
> workaround
> 3. wrote a handy sample for testing that will make a nice feature in the
> next release - a simple hive shell called knoxline :)
>
> * Tested service discovery with and without remote config monitoring and
> with ambari service monitoring - this is amazing work and was fun to test -
> couple things noted:
> 1. it can get confusing trying to keep track of where topologies are coming
> from - I believe we have a JIRA for CLI listing of remote descriptors and
> provider configs already - that will help
> 2. it seems that you can get into a state where if you have an XML issue in
> a provider config that just fixing the provider config in ZK doesn't result
> in the topology getting repulled - needs a JIRA and additional
> investigation
>
> * Tested UI improvements to protect against changing generated topologies -
> very nice!
> * Tested Okta with KnoxSSO for SAML
> * Tested Form based provider with KnoxSSO
>
> I don't find any of the above to be blockers and am very happy to give my:
>
> +1
>
> On Thu, Dec 7, 2017 at 4:51 PM, Sandeep More 
> wrote:
>
> > Great, thanks Larry and Phil the release looks great !
> >
> > +1 (binding)
> > * Downloaded and built from source (with Java 1.8.0_101)
> > * Checked LICENSE and NOTICE files
> > * Verified GPG/MD5/SHA signatures for Knox source, Knox and Knoxshell
> > release packages
> > * Installed pseudo-distributed instance (Mac OS X )
> > * Ran through knox tests
> > * Checked websocket functionality
> > * Checked java script compression (Ambari UI)
> > * Checked Topology Port Mapping feature
> > * Checked KnoxShell samples
> >
> > * ZooKeeper Configuration deployment and monitoring
> > * Checked the UI (read only for generated topologies)
> >
> > Best,
> > Sandeep
> >
> >
> > On Wed, Dec 6, 2017 at 9:07 PM, larry mccay  wrote:
> >
> > > All -
> > >
> > > A new candidate for the Apache Knox 0.14.0 release is available at:
> > >
> > > https://dist.apache.org/repos/dist/dev/knox/knox-0.14.0/
> > >
> > > The release candidate is a zip archive of the sources in:
> > >
> > > https://git-wip-us.apache.org/repos/asf/knox.git
> > > Branch v0.14.0 (git checkout -b v{gateway-version})
> > >
> > > The KEYS file for signature validation is available at:
> > > https://dist.apache.org/repos/dist/release/knox/KEYS
> > >
> > > On of the main features of this release is the Service Discovery
> > > and autosync of remote config and service information from Apache
> Ambari.
> > >
> > > There is a wiki available to help test this new set of features [1].
> > Please
> > > consider testing this out with your test environments.
> > >
> > > Please vote on releasing this package as Apache Knox 0.14.0.
> > > The vote is open for the next 72 hours and passes if a majority of at
> > > least three +1 Apache Knox PMC votes are cast.
> > >
> > > [ ] +1 Release this package as Apache Knox 0.14.0
> > > [ ] -1 Do not release this package because...
> > >
> > > thanks!
> > >
> > > --larry
> > >
> > > 1.
> > > https://cwiki.apache.org/confluence/display/KNOX/Apache+Knox+Dynamic+
> > > Configuration+End-to-End
> > >
> >
>

[jira] [Assigned] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

2017-12-12 Thread Phil Zampino (JIRA)


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

Phil Zampino reassigned KNOX-1137:
--

Assignee: Phil Zampino

> KnoxCLI For Listing Provider Configurations and Descriptors in a Remote 
> Configuration Registry
> --
>
> Key: KNOX-1137
> URL: https://issues.apache.org/jira/browse/KNOX-1137
> Project: Apache Knox
>  Issue Type: Bug
>  Components: KnoxCLI
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
>
> KNOX-1125 introduced Knox CLI commands for adding and removing provider 
> configurations and simple descriptors to a remote configuration registry 
> (e.g., ZooKeeper). It would be helpful to also have the ability to list the 
> provider configurations and descriptors that are in the registry.
> list-provider-configs --registry-client name
> list-descriptors --registry-client name



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

2017-12-12 Thread Phil Zampino (JIRA)


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

Work on KNOX-1137 started by Phil Zampino.
--
> KnoxCLI For Listing Provider Configurations and Descriptors in a Remote 
> Configuration Registry
> --
>
> Key: KNOX-1137
> URL: https://issues.apache.org/jira/browse/KNOX-1137
> Project: Apache Knox
>  Issue Type: Bug
>  Components: KnoxCLI
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
>
> KNOX-1125 introduced Knox CLI commands for adding and removing provider 
> configurations and simple descriptors to a remote configuration registry 
> (e.g., ZooKeeper). It would be helpful to also have the ability to list the 
> provider configurations and descriptors that are in the registry.
> list-provider-configs --registry-client name
> list-descriptors --registry-client name



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Test failures in master

2017-12-12 Thread Philip Zampino

I've started encountering some test failures on the master branch, without
any local changes. They both involve the DefaultDispatch NOT throwing
exceptions for invalid hosts.


testJiraKnox58(org.apache.hadoop.gateway.dispatch.DefaultDispatchTest)
Time elapsed: 0.835 sec  <<< FAILURE!
java.lang.AssertionError:
Expected: not a string containing "unreachable-host"
 but: was "unreachable-host"
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at
org.apache.hadoop.gateway.dispatch.DefaultDispatchTest.testJiraKnox58(DefaultDispatchTest.java:103)


This one is due to an attempt to write the outbound respond where the
response output stream has not been setup. The problem is that the test
never expects it to get that far:

testHttpClientOutboundException(org.apache.hadoop.gateway.AuditLoggingTest)
Time elapsed: 4.036 sec  <<< ERROR!
java.lang.NullPointerException: null
at org.apache.hadoop.io.IOUtils.copyBytes(IOUtils.java:87)
at
org.apache.hadoop.gateway.dispatch.AbstractGatewayDispatch.writeResponse(AbstractGatewayDispatch.java:65)
at
org.apache.hadoop.gateway.dispatch.DefaultDispatch.writeOutboundResponse(DefaultDispatch.java:183)
at
org.apache.hadoop.gateway.dispatch.DefaultDispatch.executeRequest(DefaultDispatch.java:117)
at
org.apache.hadoop.gateway.dispatch.DefaultDispatch.doGet(DefaultDispatch.java:278)
at
org.apache.hadoop.gateway.AuditLoggingTest.testHttpClientOutboundException(AuditLoggingTest.java:202)


Is anyone else seeing this? Could it be my environment?
Are you aware of anything that changed recently which would cause this?

  -- Phil

[jira] [Updated] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

2017-12-12 Thread Phil Zampino (JIRA)


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

Phil Zampino updated KNOX-1137:
---
Attachment: KNOX-1137.patch

> KnoxCLI For Listing Provider Configurations and Descriptors in a Remote 
> Configuration Registry
> --
>
> Key: KNOX-1137
> URL: https://issues.apache.org/jira/browse/KNOX-1137
> Project: Apache Knox
>  Issue Type: Bug
>  Components: KnoxCLI
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
> Attachments: KNOX-1137.patch
>
>
> KNOX-1125 introduced Knox CLI commands for adding and removing provider 
> configurations and simple descriptors to a remote configuration registry 
> (e.g., ZooKeeper). It would be helpful to also have the ability to list the 
> provider configurations and descriptors that are in the registry.
> list-provider-configs --registry-client name
> list-descriptors --registry-client name



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

2017-12-12 Thread Phil Zampino (JIRA)


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

Phil Zampino updated KNOX-1137:
---
Status: Patch Available  (was: In Progress)

Attached KNOX-1137.patch, which adds:

list-provider-configs --registry-client CLIENT_NAME
list-descriptors --registry-client CLIENT_NAME

Examples:
{GATEWAY_HOME}/bin/knoxcli.sh list-provider-configs --registry-name 
sandbox-zookeeper-client
Provider Configurations (@localhost:2181)
sandbox-providers.xml

{GATEWAY_HOME}/bin/knoxcli.sh list-descriptors --registry-name 
sandbox-zookeeper-client
Descriptors (@localhost:2181)
docker-sandbox.json

> KnoxCLI For Listing Provider Configurations and Descriptors in a Remote 
> Configuration Registry
> --
>
> Key: KNOX-1137
> URL: https://issues.apache.org/jira/browse/KNOX-1137
> Project: Apache Knox
>  Issue Type: Bug
>  Components: KnoxCLI
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
> Attachments: KNOX-1137.patch
>
>
> KNOX-1125 introduced Knox CLI commands for adding and removing provider 
> configurations and simple descriptors to a remote configuration registry 
> (e.g., ZooKeeper). It would be helpful to also have the ability to list the 
> provider configurations and descriptors that are in the registry.
> list-provider-configs --registry-client name
> list-descriptors --registry-client name



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Test failures in master

2017-12-12 Thread Philip Zampino

It looks to have been a DNS issue. It's resolved for me now.

On Tue, Dec 12, 2017 at 12:35 PM, Philip Zampino  wrote:

> I've started encountering some test failures on the master branch, without
> any local changes. They both involve the DefaultDispatch NOT throwing
> exceptions for invalid hosts.
>
>
> testJiraKnox58(org.apache.hadoop.gateway.dispatch.DefaultDispatchTest)
> Time elapsed: 0.835 sec  <<< FAILURE!
> java.lang.AssertionError:
> Expected: not a string containing "unreachable-host"
>  but: was "unreachable-host"
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:956)
> at org.junit.Assert.assertThat(Assert.java:923)
> at org.apache.hadoop.gateway.dispatch.DefaultDispatchTest.testJiraKnox58(
> DefaultDispatchTest.java:103)
>
>
> This one is due to an attempt to write the outbound respond where the
> response output stream has not been setup. The problem is that the test
> never expects it to get that far:
>
> testHttpClientOutboundException(org.apache.hadoop.gateway.AuditLoggingTest)
> Time elapsed: 4.036 sec  <<< ERROR!
> java.lang.NullPointerException: null
> at org.apache.hadoop.io.IOUtils.copyBytes(IOUtils.java:87)
> at org.apache.hadoop.gateway.dispatch.AbstractGatewayDispatch.
> writeResponse(AbstractGatewayDispatch.java:65)
> at org.apache.hadoop.gateway.dispatch.DefaultDispatch.
> writeOutboundResponse(DefaultDispatch.java:183)
> at org.apache.hadoop.gateway.dispatch.DefaultDispatch.executeRequest(
> DefaultDispatch.java:117)
> at org.apache.hadoop.gateway.dispatch.DefaultDispatch.
> doGet(DefaultDispatch.java:278)
> at org.apache.hadoop.gateway.AuditLoggingTest.
> testHttpClientOutboundException(AuditLoggingTest.java:202)
>
>
> Is anyone else seeing this? Could it be my environment?
> Are you aware of anything that changed recently which would cause this?
>
>   -- Phil
>
>

[jira] [Comment Edited] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

2017-12-12 Thread Phil Zampino (JIRA)


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

Phil Zampino edited comment on KNOX-1137 at 12/12/17 7:20 PM:
--

Attached KNOX-1137.patch, which adds:

list-provider-configs --registry-client CLIENT_NAME
list-descriptors --registry-client CLIENT_NAME

Examples:

{noformat}
{GATEWAY_HOME}/bin/knoxcli.sh list-provider-configs --registry-name 
sandbox-zookeeper-client
Provider Configurations (@localhost:2181)
sandbox-providers.xml

{noformat}

{noformat}
{GATEWAY_HOME}/bin/knoxcli.sh list-descriptors --registry-name 
sandbox-zookeeper-client
Descriptors (@localhost:2181)
docker-sandbox.json

{noformat}



was (Author: pzampino):
Attached KNOX-1137.patch, which adds:

list-provider-configs --registry-client CLIENT_NAME
list-descriptors --registry-client CLIENT_NAME

Examples:
{GATEWAY_HOME}/bin/knoxcli.sh list-provider-configs --registry-name 
sandbox-zookeeper-client
Provider Configurations (@localhost:2181)
sandbox-providers.xml

{GATEWAY_HOME}/bin/knoxcli.sh list-descriptors --registry-name 
sandbox-zookeeper-client
Descriptors (@localhost:2181)
docker-sandbox.json

> KnoxCLI For Listing Provider Configurations and Descriptors in a Remote 
> Configuration Registry
> --
>
> Key: KNOX-1137
> URL: https://issues.apache.org/jira/browse/KNOX-1137
> Project: Apache Knox
>  Issue Type: Bug
>  Components: KnoxCLI
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
> Attachments: KNOX-1137.patch
>
>
> KNOX-1125 introduced Knox CLI commands for adding and removing provider 
> configurations and simple descriptors to a remote configuration registry 
> (e.g., ZooKeeper). It would be helpful to also have the ability to list the 
> provider configurations and descriptors that are in the registry.
> list-provider-configs --registry-client name
> list-descriptors --registry-client name



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

2017-12-12 Thread Phil Zampino (JIRA)


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

Phil Zampino edited comment on KNOX-1137 at 12/12/17 7:20 PM:
--

Attached KNOX-1137.patch, which adds:

* list-provider-configs --registry-client CLIENT_NAME
* list-descriptors --registry-client CLIENT_NAME

Examples:

{noformat}
{GATEWAY_HOME}/bin/knoxcli.sh list-provider-configs --registry-name 
sandbox-zookeeper-client
Provider Configurations (@localhost:2181)
sandbox-providers.xml

{noformat}

{noformat}
{GATEWAY_HOME}/bin/knoxcli.sh list-descriptors --registry-name 
sandbox-zookeeper-client
Descriptors (@localhost:2181)
docker-sandbox.json

{noformat}



was (Author: pzampino):
Attached KNOX-1137.patch, which adds:

list-provider-configs --registry-client CLIENT_NAME
list-descriptors --registry-client CLIENT_NAME

Examples:

{noformat}
{GATEWAY_HOME}/bin/knoxcli.sh list-provider-configs --registry-name 
sandbox-zookeeper-client
Provider Configurations (@localhost:2181)
sandbox-providers.xml

{noformat}

{noformat}
{GATEWAY_HOME}/bin/knoxcli.sh list-descriptors --registry-name 
sandbox-zookeeper-client
Descriptors (@localhost:2181)
docker-sandbox.json

{noformat}


> KnoxCLI For Listing Provider Configurations and Descriptors in a Remote 
> Configuration Registry
> --
>
> Key: KNOX-1137
> URL: https://issues.apache.org/jira/browse/KNOX-1137
> Project: Apache Knox
>  Issue Type: Bug
>  Components: KnoxCLI
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
> Attachments: KNOX-1137.patch
>
>
> KNOX-1125 introduced Knox CLI commands for adding and removing provider 
> configurations and simple descriptors to a remote configuration registry 
> (e.g., ZooKeeper). It would be helpful to also have the ability to list the 
> provider configurations and descriptors that are in the registry.
> list-provider-configs --registry-client name
> list-descriptors --registry-client name



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

2017-12-12 Thread Phil Zampino (JIRA)


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

Phil Zampino edited comment on KNOX-1144 at 12/12/17 7:25 PM:
--

Attached KNOX-1144.patch

The TopologyService now determines provider configuration reference 
relationships for any existing simple descriptors at gateway startup time. This 
should address the issue.

Furthermore, the remote configuration monitor immediately downloads any 
existing provider configurations (which either do not exist locally, or are 
different from the local contents), to avoid any inconsistent behavior due to 
downloading a remote descriptor before its referenced provider config; I've not 
ever seen this happen yet, but this change should prevent any potential for 
inconsistent behavior wrt updating descriptors when their referenced provider 
configs change.

To test this patch:
# Start the gateway
# Add one or more provider configurations to conf/shared-providers/
# Add one or more descriptors, which reference those provider configs, to 
conf/descriptors
# Stop the gateway
# Modify one or more provider configurations
# Start the gateway
# Verify that topologies for the affected descriptors were regenerated with the 
new provider configs.
# Stop the gateway
# Start the gateway
# Modify one or more provider configurations
# Verify that topologies for the affected descriptors were regenerated with the 
new provider configs.



was (Author: pzampino):
Attached KNOX-1144.patch

The TopologyService now determines provider configuration reference 
relationships for any existing simple descriptors at gateway startup time. This 
should address the issue.

Furthermore, the remote configuration monitor immediately downloads any 
existing provider configurations (which either do not exist locally, or are 
different from the local contents), to avoid any inconsistent behavior due to 
downloading a remote descriptor before its referenced provider config; I've not 
ever seen this happen yet, but this change should prevent any potential for 
inconsistent behavior wrt updating descriptors when their referenced provider 
configs change.


> Provider Configuration Reference Relationships Aren't Established For 
> Existing Descriptors at Gateway Startup
> -
>
> Key: KNOX-1144
> URL: https://issues.apache.org/jira/browse/KNOX-1144
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
> Attachments: KNOX-1144.patch
>
>
> Changes to existing provider configurations don't result in updates to the 
> existing descriptors which reference them.
> This is a consequence of changing the startup behavior wrt simple 
> descriptors. Now that existing simple descriptors no longer trigger topology 
> regeneration at startup (unless they've changed since shutdown), the 
> relationships between simple descriptors and the provider configurations they 
> reference are not being established.
> These relationships need to be established when the TopologyService is 
> initialized.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

2017-12-12 Thread Phil Zampino (JIRA)


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

Phil Zampino updated KNOX-1144:
---
Attachment: simple-sandbox.json
sandbox-providers.xml

> Provider Configuration Reference Relationships Aren't Established For 
> Existing Descriptors at Gateway Startup
> -
>
> Key: KNOX-1144
> URL: https://issues.apache.org/jira/browse/KNOX-1144
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
> Attachments: KNOX-1144.patch, sandbox-providers.xml, 
> simple-sandbox.json
>
>
> Changes to existing provider configurations don't result in updates to the 
> existing descriptors which reference them.
> This is a consequence of changing the startup behavior wrt simple 
> descriptors. Now that existing simple descriptors no longer trigger topology 
> regeneration at startup (unless they've changed since shutdown), the 
> relationships between simple descriptors and the provider configurations they 
> reference are not being established.
> These relationships need to be established when the TopologyService is 
> initialized.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

2017-12-12 Thread Phil Zampino (JIRA)


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

Phil Zampino edited comment on KNOX-1144 at 12/12/17 7:28 PM:
--

Attached KNOX-1144.patch

The TopologyService now determines provider configuration reference 
relationships for any existing simple descriptors at gateway startup time. This 
should address the issue.

Furthermore, the remote configuration monitor immediately downloads any 
existing provider configurations (which either do not exist locally, or are 
different from the local contents), to avoid any inconsistent behavior due to 
downloading a remote descriptor before its referenced provider config; I've not 
ever seen this happen yet, but this change should prevent any potential for 
inconsistent behavior wrt updating descriptors when their referenced provider 
configs change.

To test this patch:
# Start the gateway
# Add one or more provider configurations (e.g., sandbox-providers.xml) to 
conf/shared-providers/
# Add one or more descriptors, which reference those provider configs, (e.g., 
simple-sandbox.json) to conf/descriptors
# Stop the gateway
# Modify one or more provider configurations
# Start the gateway
# Verify that topologies for the affected descriptors were regenerated with the 
new provider configs.
# Stop the gateway
# Start the gateway
# Modify one or more provider configurations
# Verify that topologies for the affected descriptors were regenerated with the 
new provider configs.



was (Author: pzampino):
Attached KNOX-1144.patch

The TopologyService now determines provider configuration reference 
relationships for any existing simple descriptors at gateway startup time. This 
should address the issue.

Furthermore, the remote configuration monitor immediately downloads any 
existing provider configurations (which either do not exist locally, or are 
different from the local contents), to avoid any inconsistent behavior due to 
downloading a remote descriptor before its referenced provider config; I've not 
ever seen this happen yet, but this change should prevent any potential for 
inconsistent behavior wrt updating descriptors when their referenced provider 
configs change.

To test this patch:
# Start the gateway
# Add one or more provider configurations to conf/shared-providers/
# Add one or more descriptors, which reference those provider configs, to 
conf/descriptors
# Stop the gateway
# Modify one or more provider configurations
# Start the gateway
# Verify that topologies for the affected descriptors were regenerated with the 
new provider configs.
# Stop the gateway
# Start the gateway
# Modify one or more provider configurations
# Verify that topologies for the affected descriptors were regenerated with the 
new provider configs.


> Provider Configuration Reference Relationships Aren't Established For 
> Existing Descriptors at Gateway Startup
> -
>
> Key: KNOX-1144
> URL: https://issues.apache.org/jira/browse/KNOX-1144
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Server
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
> Attachments: KNOX-1144.patch, sandbox-providers.xml, 
> simple-sandbox.json
>
>
> Changes to existing provider configurations don't result in updates to the 
> existing descriptors which reference them.
> This is a consequence of changing the startup behavior wrt simple 
> descriptors. Now that existing simple descriptors no longer trigger topology 
> regeneration at startup (unless they've changed since shutdown), the 
> relationships between simple descriptors and the provider configurations they 
> reference are not being established.
> These relationships need to be established when the TopologyService is 
> initialized.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KNOX-1099) document Livy Knox service (Spark Rest Service)

2017-12-12 Thread Rick Kellogg (JIRA)


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

Rick Kellogg commented on KNOX-1099:


See the following for details:

https://community.hortonworks.com/articles/70499/adding-livy-server-as-service-to-apache-knox.html

> document Livy Knox service (Spark Rest Service)
> ---
>
> Key: KNOX-1099
> URL: https://issues.apache.org/jira/browse/KNOX-1099
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Site
>Affects Versions: 0.11.0
>Reporter: Jeffrey Rodriguez
>Assignee: Jeffrey E  Rodriguez
> Fix For: 0.14.0
>
>
> Add user documentation for Livy Service - KNOX-842



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (KNOX-1146) Document KNOX CLI Commands For Listing Provider Configs and Descriptors in Remote Registries

2017-12-12 Thread Phil Zampino (JIRA)

Phil Zampino created KNOX-1146:
--

 Summary: Document KNOX CLI Commands For Listing Provider Configs 
and Descriptors in Remote Registries
 Key: KNOX-1146
 URL: https://issues.apache.org/jira/browse/KNOX-1146
 Project: Apache Knox
  Issue Type: Bug
  Components: Site
Affects Versions: 0.14.0
Reporter: Phil Zampino
Assignee: Phil Zampino
 Fix For: 0.15.0


KNOX-1137 adds commands for listing provider configurations and simple 
descriptors in remote registries



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1146) Document KNOX CLI Commands For Listing Provider Configs and Descriptors in Remote Registries

2017-12-12 Thread Phil Zampino (JIRA)


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

Phil Zampino updated KNOX-1146:
---
Attachment: KNOX-1146.patch

> Document KNOX CLI Commands For Listing Provider Configs and Descriptors in 
> Remote Registries
> 
>
> Key: KNOX-1146
> URL: https://issues.apache.org/jira/browse/KNOX-1146
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Site
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
> Attachments: KNOX-1146.patch
>
>
> KNOX-1137 adds commands for listing provider configurations and simple 
> descriptors in remote registries



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (KNOX-1146) Document KNOX CLI Commands For Listing Provider Configs and Descriptors in Remote Registries

2017-12-12 Thread Phil Zampino (JIRA)


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

Work on KNOX-1146 started by Phil Zampino.
--
> Document KNOX CLI Commands For Listing Provider Configs and Descriptors in 
> Remote Registries
> 
>
> Key: KNOX-1146
> URL: https://issues.apache.org/jira/browse/KNOX-1146
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Site
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
> Attachments: KNOX-1146.patch
>
>
> KNOX-1137 adds commands for listing provider configurations and simple 
> descriptors in remote registries



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1146) Document KNOX CLI Commands For Listing Provider Configs and Descriptors in Remote Registries

2017-12-12 Thread Phil Zampino (JIRA)


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

Phil Zampino updated KNOX-1146:
---
Status: Patch Available  (was: In Progress)

> Document KNOX CLI Commands For Listing Provider Configs and Descriptors in 
> Remote Registries
> 
>
> Key: KNOX-1146
> URL: https://issues.apache.org/jira/browse/KNOX-1146
> Project: Apache Knox
>  Issue Type: Bug
>  Components: Site
>Affects Versions: 0.14.0
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Fix For: 0.15.0
>
> Attachments: KNOX-1146.patch
>
>
> KNOX-1137 adds commands for listing provider configurations and simple 
> descriptors in remote registries



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[RESULT] [VOTE] Release Apache Knox 0.14.0 rc 2

2017-12-12 Thread larry mccay

The VOTE for 0.14.0 rc2 passes with:

3 binding +1's
2 non-binding +'1
0 -1's

I will be working on promoting the RC2 to an official release shortly.

Thank you for taking the time to test this release and contributing to the
Apache Knox community!

On Tue, Dec 12, 2017 at 10:29 AM, Philip Zampino  wrote:

> >
> > 1. it can get confusing trying to keep track of where topologies are
> coming
> > from - I believe we have a JIRA for CLI listing of remote descriptors and
> > provider configs already - that will help
>
>
> KNOX-1137  is the JIRA
> which addresses this.
>
>
> 2. it seems that you can get into a state where if you have an XML issue in
> > a provider config that just fixing the provider config in ZK doesn't
> result
> > in the topology getting repulled - needs a JIRA and additional
> > investigation
>
>
> KNOX-1144  addresses
> this;
> I believe it involves provider configurations and descriptors that exist
> prior to gateway start-up.
>
> 
>
> On Mon, Dec 11, 2017 at 4:45 PM, larry mccay  wrote:
>
> > * built from source and ran unit tests
> > * verified signatures
> > * ran knox samples for webhdfs, hive, hbase
> > * used nodejs client to interact with webhdfs and webhcat
> >
> > * ran knoxshell samples noted:
> > 1. logging seems broken and is printing to console - at least with
> default
> > config - will need to file a JIRA
> > 2. hive samples are difficult to run through executable jar due to
> needing
> > to add hive jars to classpath - will file JIRA and write article to
> share a
> > workaround
> > 3. wrote a handy sample for testing that will make a nice feature in the
> > next release - a simple hive shell called knoxline :)
> >
> > * Tested service discovery with and without remote config monitoring and
> > with ambari service monitoring - this is amazing work and was fun to
> test -
> > couple things noted:
> > 1. it can get confusing trying to keep track of where topologies are
> coming
> > from - I believe we have a JIRA for CLI listing of remote descriptors and
> > provider configs already - that will help
> > 2. it seems that you can get into a state where if you have an XML issue
> in
> > a provider config that just fixing the provider config in ZK doesn't
> result
> > in the topology getting repulled - needs a JIRA and additional
> > investigation
> >
> > * Tested UI improvements to protect against changing generated
> topologies -
> > very nice!
> > * Tested Okta with KnoxSSO for SAML
> > * Tested Form based provider with KnoxSSO
> >
> > I don't find any of the above to be blockers and am very happy to give
> my:
> >
> > +1
> >
> > On Thu, Dec 7, 2017 at 4:51 PM, Sandeep More 
> > wrote:
> >
> > > Great, thanks Larry and Phil the release looks great !
> > >
> > > +1 (binding)
> > > * Downloaded and built from source (with Java 1.8.0_101)
> > > * Checked LICENSE and NOTICE files
> > > * Verified GPG/MD5/SHA signatures for Knox source, Knox and Knoxshell
> > > release packages
> > > * Installed pseudo-distributed instance (Mac OS X )
> > > * Ran through knox tests
> > > * Checked websocket functionality
> > > * Checked java script compression (Ambari UI)
> > > * Checked Topology Port Mapping feature
> > > * Checked KnoxShell samples
> > >
> > > * ZooKeeper Configuration deployment and monitoring
> > > * Checked the UI (read only for generated topologies)
> > >
> > > Best,
> > > Sandeep
> > >
> > >
> > > On Wed, Dec 6, 2017 at 9:07 PM, larry mccay  wrote:
> > >
> > > > All -
> > > >
> > > > A new candidate for the Apache Knox 0.14.0 release is available at:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/knox/knox-0.14.0/
> > > >
> > > > The release candidate is a zip archive of the sources in:
> > > >
> > > > https://git-wip-us.apache.org/repos/asf/knox.git
> > > > Branch v0.14.0 (git checkout -b v{gateway-version})
> > > >
> > > > The KEYS file for signature validation is available at:
> > > > https://dist.apache.org/repos/dist/release/knox/KEYS
> > > >
> > > > On of the main features of this release is the Service Discovery
> > > > and autosync of remote config and service information from Apache
> > Ambari.
> > > >
> > > > There is a wiki available to help test this new set of features [1].
> > > Please
> > > > consider testing this out with your test environments.
> > > >
> > > > Please vote on releasing this package as Apache Knox 0.14.0.
> > > > The vote is open for the next 72 hours and passes if a majority of at
> > > > least three +1 Apache Knox PMC votes are cast.
> > > >
> > > > [ ] +1 Release this package as Apache Knox 0.14.0
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > thanks!
> > > >
> > > > --larry
> > > >
> > > > 1.
> > > > https://cwiki.apache.org/confluence/display/KNOX/
> Apache+Knox+Dynamic+
> > > > Configuration+End-to-End
> > > >
> > >
> >
>

Re: [RESULT] [VOTE] Release Apache Knox 0.14.0 rc 2

2017-12-12 Thread Philip Zampino

Great news! Thanks Larry.

On Tue, Dec 12, 2017 at 8:22 PM larry mccay  wrote:

> The VOTE for 0.14.0 rc2 passes with:
>
> 3 binding +1's
> 2 non-binding +'1
> 0 -1's
>
> I will be working on promoting the RC2 to an official release shortly.
>
> Thank you for taking the time to test this release and contributing to the
> Apache Knox community!
>
> On Tue, Dec 12, 2017 at 10:29 AM, Philip Zampino 
> wrote:
>
> > >
> > > 1. it can get confusing trying to keep track of where topologies are
> > coming
> > > from - I believe we have a JIRA for CLI listing of remote descriptors
> and
> > > provider configs already - that will help
> >
> >
> > KNOX-1137  is the JIRA
> > which addresses this.
> >
> >
> > 2. it seems that you can get into a state where if you have an XML issue
> in
> > > a provider config that just fixing the provider config in ZK doesn't
> > result
> > > in the topology getting repulled - needs a JIRA and additional
> > > investigation
> >
> >
> > KNOX-1144  addresses
> > this;
> > I believe it involves provider configurations and descriptors that exist
> > prior to gateway start-up.
> >
> > 
> >
> > On Mon, Dec 11, 2017 at 4:45 PM, larry mccay  wrote:
> >
> > > * built from source and ran unit tests
> > > * verified signatures
> > > * ran knox samples for webhdfs, hive, hbase
> > > * used nodejs client to interact with webhdfs and webhcat
> > >
> > > * ran knoxshell samples noted:
> > > 1. logging seems broken and is printing to console - at least with
> > default
> > > config - will need to file a JIRA
> > > 2. hive samples are difficult to run through executable jar due to
> > needing
> > > to add hive jars to classpath - will file JIRA and write article to
> > share a
> > > workaround
> > > 3. wrote a handy sample for testing that will make a nice feature in
> the
> > > next release - a simple hive shell called knoxline :)
> > >
> > > * Tested service discovery with and without remote config monitoring
> and
> > > with ambari service monitoring - this is amazing work and was fun to
> > test -
> > > couple things noted:
> > > 1. it can get confusing trying to keep track of where topologies are
> > coming
> > > from - I believe we have a JIRA for CLI listing of remote descriptors
> and
> > > provider configs already - that will help
> > > 2. it seems that you can get into a state where if you have an XML
> issue
> > in
> > > a provider config that just fixing the provider config in ZK doesn't
> > result
> > > in the topology getting repulled - needs a JIRA and additional
> > > investigation
> > >
> > > * Tested UI improvements to protect against changing generated
> > topologies -
> > > very nice!
> > > * Tested Okta with KnoxSSO for SAML
> > > * Tested Form based provider with KnoxSSO
> > >
> > > I don't find any of the above to be blockers and am very happy to give
> > my:
> > >
> > > +1
> > >
> > > On Thu, Dec 7, 2017 at 4:51 PM, Sandeep More 
> > > wrote:
> > >
> > > > Great, thanks Larry and Phil the release looks great !
> > > >
> > > > +1 (binding)
> > > > * Downloaded and built from source (with Java 1.8.0_101)
> > > > * Checked LICENSE and NOTICE files
> > > > * Verified GPG/MD5/SHA signatures for Knox source, Knox and Knoxshell
> > > > release packages
> > > > * Installed pseudo-distributed instance (Mac OS X )
> > > > * Ran through knox tests
> > > > * Checked websocket functionality
> > > > * Checked java script compression (Ambari UI)
> > > > * Checked Topology Port Mapping feature
> > > > * Checked KnoxShell samples
> > > >
> > > > * ZooKeeper Configuration deployment and monitoring
> > > > * Checked the UI (read only for generated topologies)
> > > >
> > > > Best,
> > > > Sandeep
> > > >
> > > >
> > > > On Wed, Dec 6, 2017 at 9:07 PM, larry mccay 
> wrote:
> > > >
> > > > > All -
> > > > >
> > > > > A new candidate for the Apache Knox 0.14.0 release is available at:
> > > > >
> > > > > https://dist.apache.org/repos/dist/dev/knox/knox-0.14.0/
> > > > >
> > > > > The release candidate is a zip archive of the sources in:
> > > > >
> > > > > https://git-wip-us.apache.org/repos/asf/knox.git
> > > > > Branch v0.14.0 (git checkout -b v{gateway-version})
> > > > >
> > > > > The KEYS file for signature validation is available at:
> > > > > https://dist.apache.org/repos/dist/release/knox/KEYS
> > > > >
> > > > > On of the main features of this release is the Service Discovery
> > > > > and autosync of remote config and service information from Apache
> > > Ambari.
> > > > >
> > > > > There is a wiki available to help test this new set of features
> [1].
> > > > Please
> > > > > consider testing this out with your test environments.
> > > > >
> > > > > Please vote on releasing this package as Apache Knox 0.14.0.
> > > > > The vote is open for the next 72 hours and passes if a majority of
> at
> > > > > least three +1 Apache Knox PMC votes are cast

[jira] [Created] (KNOX-1147) KNOX Audit Log time not configurable or not supporting TZ

2017-12-12 Thread Rajesh Chandramohan (JIRA)

Rajesh Chandramohan created KNOX-1147:
-

 Summary: KNOX Audit Log time not configurable or not supporting TZ
 Key: KNOX-1147
 URL: https://issues.apache.org/jira/browse/KNOX-1147
 Project: Apache Knox
  Issue Type: Improvement
Affects Versions: 0.10.0, 0.13.0, 0.14.0
Reporter: Rajesh Chandramohan


 The KNOX Log4J configuration for Knoxaudit log uses  
or.hadoop.gateway.audit.log4j.layout.AuditLayout , so when the system is using 
PST tz , The auditLog is logging with 1hr ahead of current PST time. Is there a 
way to log audit event matching with current time in system and not break with 
DST change?

Even in latest version it is having hardcoded time pattern , not able to add 
Time zone. Was thinking of adding  
setDateFormat(DATE_FORMAT, TimeZone.getTimeZone(TZ));  But is there any other 
better way to get around this issue?

+
public class AuditLayout extends DateLayout {
  
  private static final String DATE_FORMAT = "yy/MM/dd HH:mm:ss";
  private static final String SEPARATOR = "|";
  private StringBuffer sb = new StringBuffer();
Override
public void activateOptions() {
  setDateFormat( DATE_FORMAT );
}


+


Thanks



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KNOX-1147) KNOX Audit Log time not configurable or not supporting TZ

2017-12-12 Thread Larry McCay (JIRA)


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

Larry McCay updated KNOX-1147:
--
Fix Version/s: 0.15.0

> KNOX Audit Log time not configurable or not supporting TZ
> -
>
> Key: KNOX-1147
> URL: https://issues.apache.org/jira/browse/KNOX-1147
> Project: Apache Knox
>  Issue Type: Improvement
>Affects Versions: 0.10.0, 0.13.0, 0.14.0
>Reporter: Rajesh Chandramohan
> Fix For: 0.15.0
>
>
>  The KNOX Log4J configuration for Knoxaudit log uses  
> or.hadoop.gateway.audit.log4j.layout.AuditLayout , so when the system is 
> using PST tz , The auditLog is logging with 1hr ahead of current PST time. Is 
> there a way to log audit event matching with current time in system and not 
> break with DST change?
> Even in latest version it is having hardcoded time pattern , not able to add 
> Time zone. Was thinking of adding  
> setDateFormat(DATE_FORMAT, TimeZone.getTimeZone(TZ));  But is there any other 
> better way to get around this issue?
> +
> public class AuditLayout extends DateLayout {
>   
>   private static final String DATE_FORMAT = "yy/MM/dd HH:mm:ss";
>   private static final String SEPARATOR = "|";
>   private StringBuffer sb = new StringBuffer();
> Override
> public void activateOptions() {
>   setDateFormat( DATE_FORMAT );
> }
> +
> Thanks



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KNOX-1147) KNOX Audit Log time not configurable or not supporting TZ

2017-12-12 Thread Larry McCay (JIRA)


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

Larry McCay commented on KNOX-1147:
---

Hi [~rajeshc] - I don't know of any other way around this.
Thank you for pointing it out.

I have either never noticed that - I think I am always just making sure the 
mins are reasonable when I am looking at the audit. :)

> KNOX Audit Log time not configurable or not supporting TZ
> -
>
> Key: KNOX-1147
> URL: https://issues.apache.org/jira/browse/KNOX-1147
> Project: Apache Knox
>  Issue Type: Improvement
>Affects Versions: 0.10.0, 0.13.0, 0.14.0
>Reporter: Rajesh Chandramohan
> Fix For: 0.15.0
>
>
>  The KNOX Log4J configuration for Knoxaudit log uses  
> or.hadoop.gateway.audit.log4j.layout.AuditLayout , so when the system is 
> using PST tz , The auditLog is logging with 1hr ahead of current PST time. Is 
> there a way to log audit event matching with current time in system and not 
> break with DST change?
> Even in latest version it is having hardcoded time pattern , not able to add 
> Time zone. Was thinking of adding  
> setDateFormat(DATE_FORMAT, TimeZone.getTimeZone(TZ));  But is there any other 
> better way to get around this issue?
> +
> public class AuditLayout extends DateLayout {
>   
>   private static final String DATE_FORMAT = "yy/MM/dd HH:mm:ss";
>   private static final String SEPARATOR = "|";
>   private StringBuffer sb = new StringBuffer();
> Override
> public void activateOptions() {
>   setDateFormat( DATE_FORMAT );
> }
> +
> Thanks



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

KNOX Audit Log time not configurable or not supporting PST

2017-12-12 Thread Rajesh Chandramohan

Hi KNOX-Team
 The KNOX Log4J configuration for Knoxaudit log uses  
or.hadoop.gateway.audit.log4j.layout.AuditLayout , so when the system is using 
PST tz , The auditLog is logging with 1hr ahead of current PST time. Is there a 
way to log audit event matching with current time in system and not break with 
DST change?
Even in latest version it is having hardcoded time pattern , not able to add 
Time zone. Was thinking of adding  setDateFormat(DATE_FORMAT, 
TimeZone.getTimeZone(TZ));  But is there any other better way to get around 
this issue?
+public class AuditLayout extends DateLayout {
  
  private static final String DATE_FORMAT = "yy/MM/dd HH:mm:ss";
  private static final String SEPARATOR = "|";
  private StringBuffer sb = new StringBuffer();Override
public void activateOptions() {
  setDateFormat( DATE_FORMAT );
}

+

Thanks\Rajesh

Re: KNOX Audit Log time not configurable or not supporting PST

2017-12-12 Thread Rajesh Chandramohan

Tracking Jira in KNOX Project https://issues.apache.org/jira/browse/KNOX-1147
Thanks\Rajesh
 

On Tuesday 12 December 2017, 6:06:16 PM GMT-8, Rajesh Chandramohan 
 wrote:  
 
 Hi KNOX-Team
 The KNOX Log4J configuration for Knoxaudit log uses  
or.hadoop.gateway.audit.log4j.layout.AuditLayout , so when the system is using 
PST tz , The auditLog is logging with 1hr ahead of current PST time. Is there a 
way to log audit event matching with current time in system and not break with 
DST change?
Even in latest version it is having hardcoded time pattern , not able to add 
Time zone. Was thinking of adding  setDateFormat(DATE_FORMAT, 
TimeZone.getTimeZone(TZ));  But is there any other better way to get around 
this issue?
+public class AuditLayout extends DateLayout {
  
  private static final String DATE_FORMAT = "yy/MM/dd HH:mm:ss";
  private static final String SEPARATOR = "|";
  private StringBuffer sb = new StringBuffer();Override
public void activateOptions() {
  setDateFormat( DATE_FORMAT );
}

+

Thanks\Rajesh

[jira] [Created] (KNOX-1145) Upgrade Jackson due to CVE-2017-7525

[jira] [Updated] (KNOX-1145) Upgrade Jackson due to CVE-2017-7525

[jira] [Updated] (KNOX-1145) Upgrade Jackson due to CVE-2017-7525

[jira] [Updated] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

[jira] [Updated] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

[jira] [Updated] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

Re: [VOTE] Release Apache Knox 0.14.0 rc 2

[jira] [Assigned] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

[jira] [Work started] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

Test failures in master

[jira] [Updated] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

[jira] [Updated] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

Re: Test failures in master

[jira] [Comment Edited] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

[jira] [Comment Edited] (KNOX-1137) KnoxCLI For Listing Provider Configurations and Descriptors in a Remote Configuration Registry

[jira] [Comment Edited] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

[jira] [Updated] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

[jira] [Comment Edited] (KNOX-1144) Provider Configuration Reference Relationships Aren't Established For Existing Descriptors at Gateway Startup

[jira] [Commented] (KNOX-1099) document Livy Knox service (Spark Rest Service)

[jira] [Created] (KNOX-1146) Document KNOX CLI Commands For Listing Provider Configs and Descriptors in Remote Registries

[jira] [Updated] (KNOX-1146) Document KNOX CLI Commands For Listing Provider Configs and Descriptors in Remote Registries

[jira] [Work started] (KNOX-1146) Document KNOX CLI Commands For Listing Provider Configs and Descriptors in Remote Registries

[jira] [Updated] (KNOX-1146) Document KNOX CLI Commands For Listing Provider Configs and Descriptors in Remote Registries

[RESULT] [VOTE] Release Apache Knox 0.14.0 rc 2

Re: [RESULT] [VOTE] Release Apache Knox 0.14.0 rc 2

[jira] [Created] (KNOX-1147) KNOX Audit Log time not configurable or not supporting TZ

[jira] [Updated] (KNOX-1147) KNOX Audit Log time not configurable or not supporting TZ

[jira] [Commented] (KNOX-1147) KNOX Audit Log time not configurable or not supporting TZ

KNOX Audit Log time not configurable or not supporting PST

Re: KNOX Audit Log time not configurable or not supporting PST

30 matches

Site Navigation

Mail list logo

Footer information