[jira] [Created] (KNOX-1064) Externalize Hadoop Service Configuration Details and Service URL Creation
Phil Zampino created KNOX-1064: -- Summary: Externalize Hadoop Service Configuration Details and Service URL Creation Key: KNOX-1064 URL: https://issues.apache.org/jira/browse/KNOX-1064 Project: Apache Knox Issue Type: Bug Components: Server Affects Versions: 0.14.0 Reporter: Phil Zampino Assignee: Phil Zampino For the sake of flexibility in terms of the services supported by service discovery and topology generation, the following should be externalized from the code: # The set and mapping of service components and their respective configuration details. # The service URL generation details. The goal is to be able to add/modify these details without having to modify source code. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KNOX-1062) Service-Level Parameter Support in Service Discovery and Topology Generation
Phil Zampino created KNOX-1062: -- Summary: Service-Level Parameter Support in Service Discovery and Topology Generation Key: KNOX-1062 URL: https://issues.apache.org/jira/browse/KNOX-1062 Project: Apache Knox Issue Type: Bug Components: Server Affects Versions: 0.14.0 Reporter: Phil Zampino Assignee: Phil Zampino Per the comments about KNOX-1014, simple descriptors and topology generation must support service-level params as they are supported in topology XML files. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (KNOX-1014) Service Discovery and Topology Generation Framework
[
https://issues.apache.org/jira/browse/KNOX-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178456#comment-16178456
]
Phil Zampino edited comment on KNOX-1014 at 9/25/17 2:28 AM:
-
[~lmccay]
{quote}
1. hive protocol scheme
2. deployment fail for missing services or no?
3. .yaml extension in addition to .yml
4. service level params
{quote}
# It was unclear to me whether hive proxying through Knox is supported if the
transport mode is NOT http. If it is unsupported, then the resolution of the
second item in your list comes into play...
# Prior to supporting service discovery, a topology would deploy just fine with
incorrect/invalid service URLs. However, I could be persuaded that failure to
dynamically determine a URL for a service declared in a descriptor should cause
topology generation to fail (since discovery knows it would be generating an
incorrect topology whereas a human does not necessarily know this). I don't
know if we want to generate/deploy something that the descriptor author did not
intend.
# This is literally a one-line change; Consider it done.
# I'll need to learn about these service params in order to add support for
them.
was (Author: pzampino):
[~lmccay]
{quote}
1. hive protocol scheme
2. deployment fail for missing services or no?
3. .yaml extension in addition to .yml
4. service level params
{quote}
# It was unclear to me whether hive proxying through Knox is supported if the
transport mode is NOT http. If it is unsupported, then the resolution of the
second item in your list comes into play...
# Prior to supporting service discovery, a topology would deploy just fine with
incorrect/invalid service URLs. However, I could be persuaded that failure to
dynamically determine a URL for a service declared in a descriptor should cause
topology generation to fail (since discovery knows it would be generating an
incorrect topology whereas a human does not necessarily know this).
# This is literally a one-line change; Consider it done.
# I'll need to learn about these service params in order to add support for
them.
> Service Discovery and Topology Generation Framework
> ---
>
> Key: KNOX-1014
> URL: https://issues.apache.org/jira/browse/KNOX-1014
> Project: Apache Knox
> Issue Type: Sub-task
> Components: Server
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Labels: kip-8
> Fix For: 0.14.0
>
> Attachments: KNOX-1014-002.patch, KNOX-1014.patch
>
>
> Implement the foundation for Service Discovery and Topology Generation.
> * Define simple descriptor format (YAML, JSON, etc...)
> * Local simple descriptor and shared provider configuration discovery
> ** Monitor conf/shared-providers, conf/descriptors similar to the way
> conf/topologies is currently monitored.
> * Ambari service discovery (REST API interactions and model construction)
> ** Configuration
> *** How to plug-in discovery implementations
> *** How to configure authentication (credentials/trust) with the service
> registries
> * Topology assembly from simple descriptor and discovery details
> * Topology deployment
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KNOX-1014) Service Discovery and Topology Generation Framework
[
https://issues.apache.org/jira/browse/KNOX-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178456#comment-16178456
]
Phil Zampino commented on KNOX-1014:
[~lmccay]
{quote}
1. hive protocol scheme
2. deployment fail for missing services or no?
3. .yaml extension in addition to .yml
4. service level params
{quote}
# It was unclear to me whether hive proxying through Knox is supported if the
transport mode is NOT http. If it is unsupported, then the resolution of the
second item in your list comes into play...
# Prior to supporting service discovery, a topology would deploy just fine with
incorrect/invalid service URLs. However, I could be persuaded that failure to
dynamically determine a URL for a service declared in a descriptor should cause
topology generation to fail (since discovery knows it would be generating an
incorrect topology whereas a human does not necessarily know this).
# This is literally a one-line change; Consider it done.
# I'll need to learn about these service params in order to add support for
them.
> Service Discovery and Topology Generation Framework
> ---
>
> Key: KNOX-1014
> URL: https://issues.apache.org/jira/browse/KNOX-1014
> Project: Apache Knox
> Issue Type: Sub-task
> Components: Server
>Reporter: Phil Zampino
>Assignee: Phil Zampino
> Labels: kip-8
> Fix For: 0.14.0
>
> Attachments: KNOX-1014-002.patch, KNOX-1014.patch
>
>
> Implement the foundation for Service Discovery and Topology Generation.
> * Define simple descriptor format (YAML, JSON, etc...)
> * Local simple descriptor and shared provider configuration discovery
> ** Monitor conf/shared-providers, conf/descriptors similar to the way
> conf/topologies is currently monitored.
> * Ambari service discovery (REST API interactions and model construction)
> ** Configuration
> *** How to plug-in discovery implementations
> *** How to configure authentication (credentials/trust) with the service
> registries
> * Topology assembly from simple descriptor and discovery details
> * Topology deployment
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
