[
https://issues.apache.org/jira/browse/KNOX-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Larry McCay updated KNOX-1247:
------------------------------
Fix Version/s: (was: 1.1.0)
1.2.0
> Knox Cloud Federation
> ---------------------
>
> Key: KNOX-1247
> URL: https://issues.apache.org/jira/browse/KNOX-1247
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Sandeep More
> Assignee: Sandeep More
> Priority: Major
> Fix For: 1.2.0
>
>
> This use-case is part of [KIP-11
> |https://cwiki.apache.org/confluence/display/KNOX/KIP-11+Cloud+Usecases](UC-1)
> This should allow topology based federation from one knox instance to
> another. This would be particularly useful for federating on-prem instances
> with cloud based ones.
> Excerpt from UC-1
> bq. The key improvement needed for this usecase is the ability to override
> the dispatch mechanism for each service configured within a topology such
> that a single normalized dispatch is used across all services exposed by the
> topology. This single dispatch would probably just need to implement an
> outgoing version of our Header based Preauth SSO Provider with Client Cert
> over TLS.
> bq. The cloud Knox instance/s will need a topology that is configured with
> the Header based Preauth Provider and have the public key of the on-prem
> instance in its truststore.
> bq. This will enable things like:
> * WebHDFS calls to an on-prem Knox actually redispatches the calls the cloud
> instance/s and results in files being put to or read from HDFS in the cloud.
> * Spark jobs submitted to Livy through on-prem instances actually redispatch
> and are submitted as cloud workloads
> * MapReduce jobs submitted to YARN RM through Knox will be submitted as
> workloads to the cloud
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
