[ https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swapan Shridhar updated AMBARI-21824: ------------------------------------- Description: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- *Service:* http://<hostname>:<port>/api/v1/clusters/<clusterName>/*servicegroups/<ServiceGroupName>*/services http://<hostname>:<port>/api/v1/clusters/<clusterName>/*servicegroups/<ServiceGroupName>*/services/<ServiceName> *ServiceComponent:* http://<hostname>:<port>/api/v1/clusters/<clusterName>/*servicegroups/<ServiceGroupName>*/services/<ServiceName>/components/ http://<hostname>:<port>/api/v1/clusters/<clusterName>/*servicegroups/<ServiceGroupName>*/services/<ServiceName>/components/ZOOKEEPER_SERVER --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- *HostComponent:* (API remains same, but has notion of servicegroup in Ambari backend) http://<hostname>:<port>/api/v1/clusters/c1/hosts/<HostName>/host_components/ http://<hostname>:<port>/api/v1/clusters/c1/hosts/<HostName>/host_components/<HostComponentName> - The change also includes UI changes as well, which create a *default ServiceGroup named 'core'*, and all services created goes under it. was: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- *Service:* http://<hostname>:<port>/api/v1/clusters/<clusterName>/*servicegroups/<ServiceGroupName>*/services http://<hostname>:<port>/api/v1/clusters/<clusterName>/*servicegroups/<ServiceGroupName>*/services/<ServiceName> *ServiceComponent:* http://<hostname>:<port>/api/v1/clusters/<clusterName>/*servicegroups/<ServiceGroupName>*/services/<ServiceName>/components/ http://<hostname>:<port>/api/v1/clusters/<clusterName>/*servicegroups/<ServiceGroupName>*/services/<ServiceName>/components/ZOOKEEPER_SERVER --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- *HostComponent:* (API remains same, but has notion of servicegroup in Ambari backend) http://<hostname>:<port>/api/v1/clusters/c1/hosts/<HostName>/host_components/ http://<hostname>:<port>/api/v1/clusters/c1/hosts/<HostName>/host_components/<HostComponentName> The change also includes UI changes as well, which create a *default ServiceGroup named 'core'*, and all services created goes under it. > Make services as sub-resource of ServiceGroups and use Servicegroup while > doing Creation, Update and retrieval of HostComponents and ServiceComponents. > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: AMBARI-21824 > URL: https://issues.apache.org/jira/browse/AMBARI-21824 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web > Affects Versions: 2.5.1 > Reporter: Swapan Shridhar > Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. > This Task involves : > - moving *Services* which was earlier a sub-resource of *Cluster* under > *ServiceGroup* now, and > - using *Servicegroup* while doing Creation, Update and retrieval of > *HostComponents* and *ServiceComponents*. > The new API calls will be the following: > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > *Service:* > http://<hostname>:<port>/api/v1/clusters/<clusterName>/*servicegroups/<ServiceGroupName>*/services > http://<hostname>:<port>/api/v1/clusters/<clusterName>/*servicegroups/<ServiceGroupName>*/services/<ServiceName> > *ServiceComponent:* > http://<hostname>:<port>/api/v1/clusters/<clusterName>/*servicegroups/<ServiceGroupName>*/services/<ServiceName>/components/ > http://<hostname>:<port>/api/v1/clusters/<clusterName>/*servicegroups/<ServiceGroupName>*/services/<ServiceName>/components/ZOOKEEPER_SERVER > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > *HostComponent:* (API remains same, but has notion of servicegroup in Ambari > backend) > http://<hostname>:<port>/api/v1/clusters/c1/hosts/<HostName>/host_components/ > http://<hostname>:<port>/api/v1/clusters/c1/hosts/<HostName>/host_components/<HostComponentName> > - The change also includes UI changes as well, which create a *default > ServiceGroup named 'core'*, and all services created goes under it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)