You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by Sandeep More <mo...@gmail.com> on 2017/04/27 16:06:25 UTC
[FEATURE] Port Mapping for Topologies (Default Topologies per port)
As you might know, currently the default topology feature [1] is broken
[2], there were few attempts made to fix it but looks like the most recent
refactoring might have broken it again.
I would like to propose a feature (similar to Default Topology) where one
can specify port a topology can listen on. The requests to this topology do
not have to include the {gateway} and {topology} elements. So essentially
it will be Default Topology feature but now we can have support for
multiple topologies (listening on different ports).
Off-course the standard port configured through gateway config will work
just the way it always has, so all the existing features will not be
affected.
I am planning to start a new KIP and try to put more information there. I
think this will be an exciting new feature and a good value add.
Please let me know your thoughts !
Best,
Sandeep
[1]
http://knox.apache.org/books/knox-0-12-0/user-guide.html#Default+Topology+URLs
[2] https://issues.apache.org/jira/browse/KNOX-797
Re: [FEATURE] Port Mapping for Topologies (Default Topologies per port)
Posted by Sandeep More <mo...@gmail.com>.
Cool, glad you liked it ! I will start on the KIP and JIRA !
On Thu, Apr 27, 2017 at 12:28 PM, larry mccay <lm...@apache.org> wrote:
> Hi Sandeep -
>
> That sounds like a great improvement.
> Instead of having a single "default topology" we can map topologies to
> specific ports and have a dedicated URL without the gateway specific app
> context.
>
> This would provide interesting possibilities for existing hadoop cli's and
> possibly distcp.
> We will need to address the inabilitiy for the hadoop java client to deal
> with spnego challenges from the DN redirect next!
>
> Great idea - please write up the KIP and file a related JIRA.
>
> I will remove the default topology JIRAs from 0.13.0 for now in the
> interest of scope planning.
>
> thanks!
>
> --larry
>
> On Thu, Apr 27, 2017 at 12:06 PM, Sandeep More <mo...@gmail.com>
> wrote:
>
> > As you might know, currently the default topology feature [1] is broken
> > [2], there were few attempts made to fix it but looks like the most
> recent
> > refactoring might have broken it again.
> >
> > I would like to propose a feature (similar to Default Topology) where one
> > can specify port a topology can listen on. The requests to this topology
> do
> > not have to include the {gateway} and {topology} elements. So essentially
> > it will be Default Topology feature but now we can have support for
> > multiple topologies (listening on different ports).
> >
> > Off-course the standard port configured through gateway config will work
> > just the way it always has, so all the existing features will not be
> > affected.
> >
> > I am planning to start a new KIP and try to put more information there. I
> > think this will be an exciting new feature and a good value add.
> >
> > Please let me know your thoughts !
> >
> > Best,
> > Sandeep
> >
> >
> >
> > [1]
> > http://knox.apache.org/books/knox-0-12-0/user-guide.html#
> > Default+Topology+URLs
> > [2] https://issues.apache.org/jira/browse/KNOX-797
> >
>
Re: [FEATURE] Port Mapping for Topologies (Default Topologies per port)
Posted by Sandeep More <mo...@gmail.com>.
Created KIP-6 -
https://cwiki.apache.org/confluence/display/KNOX/KIP-6+Topology+Port+Mapping
and JIRA - https://issues.apache.org/jira/browse/KNOX-928
to track the progress !
Best,
Sandeep
On Thu, Apr 27, 2017 at 12:28 PM, larry mccay <lm...@apache.org> wrote:
> Hi Sandeep -
>
> That sounds like a great improvement.
> Instead of having a single "default topology" we can map topologies to
> specific ports and have a dedicated URL without the gateway specific app
> context.
>
> This would provide interesting possibilities for existing hadoop cli's and
> possibly distcp.
> We will need to address the inabilitiy for the hadoop java client to deal
> with spnego challenges from the DN redirect next!
>
> Great idea - please write up the KIP and file a related JIRA.
>
> I will remove the default topology JIRAs from 0.13.0 for now in the
> interest of scope planning.
>
> thanks!
>
> --larry
>
> On Thu, Apr 27, 2017 at 12:06 PM, Sandeep More <mo...@gmail.com>
> wrote:
>
> > As you might know, currently the default topology feature [1] is broken
> > [2], there were few attempts made to fix it but looks like the most
> recent
> > refactoring might have broken it again.
> >
> > I would like to propose a feature (similar to Default Topology) where one
> > can specify port a topology can listen on. The requests to this topology
> do
> > not have to include the {gateway} and {topology} elements. So essentially
> > it will be Default Topology feature but now we can have support for
> > multiple topologies (listening on different ports).
> >
> > Off-course the standard port configured through gateway config will work
> > just the way it always has, so all the existing features will not be
> > affected.
> >
> > I am planning to start a new KIP and try to put more information there. I
> > think this will be an exciting new feature and a good value add.
> >
> > Please let me know your thoughts !
> >
> > Best,
> > Sandeep
> >
> >
> >
> > [1]
> > http://knox.apache.org/books/knox-0-12-0/user-guide.html#
> > Default+Topology+URLs
> > [2] https://issues.apache.org/jira/browse/KNOX-797
> >
>
Re: [FEATURE] Port Mapping for Topologies (Default Topologies per port)
Posted by larry mccay <lm...@apache.org>.
Hi Sandeep -
That sounds like a great improvement.
Instead of having a single "default topology" we can map topologies to
specific ports and have a dedicated URL without the gateway specific app
context.
This would provide interesting possibilities for existing hadoop cli's and
possibly distcp.
We will need to address the inabilitiy for the hadoop java client to deal
with spnego challenges from the DN redirect next!
Great idea - please write up the KIP and file a related JIRA.
I will remove the default topology JIRAs from 0.13.0 for now in the
interest of scope planning.
thanks!
--larry
On Thu, Apr 27, 2017 at 12:06 PM, Sandeep More <mo...@gmail.com>
wrote:
> As you might know, currently the default topology feature [1] is broken
> [2], there were few attempts made to fix it but looks like the most recent
> refactoring might have broken it again.
>
> I would like to propose a feature (similar to Default Topology) where one
> can specify port a topology can listen on. The requests to this topology do
> not have to include the {gateway} and {topology} elements. So essentially
> it will be Default Topology feature but now we can have support for
> multiple topologies (listening on different ports).
>
> Off-course the standard port configured through gateway config will work
> just the way it always has, so all the existing features will not be
> affected.
>
> I am planning to start a new KIP and try to put more information there. I
> think this will be an exciting new feature and a good value add.
>
> Please let me know your thoughts !
>
> Best,
> Sandeep
>
>
>
> [1]
> http://knox.apache.org/books/knox-0-12-0/user-guide.html#
> Default+Topology+URLs
> [2] https://issues.apache.org/jira/browse/KNOX-797
>