[ https://issues.apache.org/jira/browse/AMBARI-22945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swapan Shridhar updated AMBARI-22945: ------------------------------------- Description: *BACKGROUND:* In order to support multi-instance for components of a given service, we need to enhance the Host Components API so that they can distinguish one component instance of a service from another component instance of a service with the same Name. Given that, we refer components of a services in 2 ways: - One from the Service component APIs : *http://<AmbariServerHost>:8080/api/v1/clusters/<clusterName>/services/<ServiceName>/components/<componentName>* - Other from the host component APIs (which tell us the host on which the current component is resides) *http://<AmbariServerHost>:8080/api/v1/clusters/<clusterName>/hosts/<hostName>/host_components/<hostComponentName>* For example, : - if *core* _Service Group_ has its *HDFS_CLIENT* type component named as *HDFS_CLIENT* Core -> HDFS -> HDFS_CLIENT, and at the same time - we have *edw* _Service Group_ having its *HDFS_CLIENT* type component named as *HDFS_CLIENT* : edw -> HDFS -> HDFS_CLIENT There is a way to distinguish a given Thus, following changes are required: - Notion of component type - A way to identify the HOST component uniquely was: *BACKGROUND:* In order to support multi-instance for components of a given service, we need to enhance the Host Components API so that they can distinguish one component instance of a service from another component instance of a service with the same Name. Given that, we refer components of a services in 2 ways: - One from the Service component APIs : *http://<AmbariServerHost>:8080/api/v1/clusters/<clusterName>/services/<ServiceName>/components/<componentName>* - Other from the host component APIs (which tell us the host on which the current component is resides) http://<AmbariServerHost>:8080/api/v1/clusters/<clusterName>/hosts/<hostName>/host_components/<hostComponentName> For example, : - if *core* _Service Group_ has its *HDFS_CLIENT* type component named as *HDFS_CLIENT* Core -> HDFS -> HDFS_CLIENT, and at the same time - we have *edw* _Service Group_ having its *HDFS_CLIENT* type component named as *HDFS_CLIENT* : edw -> HDFS -> HDFS_CLIENT There is a way to distinguish a given Thus, following changes are required: - Notion of component type - A way to identify the HOST component uniquely > Enhance host components API to support multiple host component instances. > ------------------------------------------------------------------------- > > Key: AMBARI-22945 > URL: https://issues.apache.org/jira/browse/AMBARI-22945 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Reporter: Swapan Shridhar > Assignee: Swapan Shridhar > Priority: Critical > Fix For: 3.0.0 > > > *BACKGROUND:* > In order to support multi-instance for components of a given service, we need > to enhance the Host Components API so that they can distinguish one component > instance of a service from another component instance of a service with the > same Name. > Given that, we refer components of a services in 2 ways: > - One from the Service component APIs : > > *http://<AmbariServerHost>:8080/api/v1/clusters/<clusterName>/services/<ServiceName>/components/<componentName>* > - Other from the host component APIs (which tell us the host on which the > current component is resides) > > *http://<AmbariServerHost>:8080/api/v1/clusters/<clusterName>/hosts/<hostName>/host_components/<hostComponentName>* > For example, : > - if *core* _Service Group_ has its *HDFS_CLIENT* type component named as > *HDFS_CLIENT* > Core -> HDFS -> HDFS_CLIENT, and at the same time > - we have *edw* _Service Group_ having its *HDFS_CLIENT* type component > named as *HDFS_CLIENT* : > edw -> HDFS -> HDFS_CLIENT > There is > a way to distinguish a given > Thus, following changes are required: > - Notion of component type > - A way to identify the HOST component uniquely -- This message was sent by Atlassian JIRA (v7.6.3#76005)