Usage Collector Usage collector consists of a scheduler that triggers the collection of – information from the different resource providers in a circular fashion. It interacts with each resource provider one by one, if the provider returns with an empty response it moves to the next provider in the cycle. Usage (REST API) The Usage REST API exposes a REST endpoint for data access. This – is used to allow access to the content in the usage database. Usage Database Data from the usage collector stored in the central data repository – The following illustration represents how the Service Provider Foundation usage endpoint communicates with the Usage Service in Windows Azure Pack. This is how the communication flows between the different components: The Usage Collector, a component of the Usage Service, collects usage data from every resource provider. For VM Clouds, Usage Collector interacts with the usage endpoint of Service Provider Foundation to collect usage data such as CPU, memory, or disk usage. Service Provider Foundation usage endpoint retrieves data from the VMM and the Operations Manager Data Warehouse and returns the data to the Usage Collector service. Usage Collector stores the data in a Usage Database. Usage REST API can be used to access the usage data from the database for billing. To associate the Service Provider Foundation usage endpoint with the Windows Azure Pack Usage Service, you must register the Service Provider Foundation usage endpoint from the VM Clouds QuickStart tab. For more information, see . See Also How is Service Provider Foundation associated with Service Management Automation? Service Provider Foundation integrates with the management portal for administrators and Microsoft System Center Virtual Machine Manager to provide capabilities to administer and provision virtual machines on the go. Service Provider Foundation can also be extended to integrate with other business operations and tool using Service Management Automation (a variant of System Center Orchestrator for management portal for administrators), to provide capabilities to service providers and organizations to extend their offerings. For example, you could think of a scenario where every time a service administrator changes an existing plan, you want to run an automated task that propagates that change across all pre-existing subscriptions
Usage Collector – Usage collector consists of a scheduler that triggers the collection of information from the different resource providers in a circular fashion. It interacts with each resource provider one by one, if the provider returns with an empty response it moves to the next provider in the cycle. Usage (REST API) – The Usage REST API exposes a REST endpoint for data access. This is used to allow access to the content in the usage database. Usage Database – Data from the usage collector stored in the central data repository The following illustration represents how the Service Provider Foundation usage endpoint communicates with the Usage Service in Windows Azure Pack. This is how the communication flows between the different components: The Usage Collector, a component of the Usage Service, collects usage data from every resource provider. For VM Clouds, Usage Collector interacts with the usage endpoint of Service Provider Foundation to collect usage data such as CPU, memory, or disk usage. Service Provider Foundation usage endpoint retrieves data from the VMM and the Operations Manager Data Warehouse and returns the data to the Usage Collector service. Usage Collector stores the data in a Usage Database. Usage REST API can be used to access the usage data from the database for billing. To associate the Service Provider Foundation usage endpoint with the Windows Azure Pack Usage Service, you must register the Service Provider Foundation usage endpoint from the VM Clouds QuickStart tab. For more information, see . See Also How is Service Provider Foundation associated with Service Management Automation? Service Provider Foundation integrates with the management portal for administrators and Microsoft System Center Virtual Machine Manager to provide capabilities to administer and provision virtual machines on the go. Service Provider Foundation can also be extended to integrate with other business operations and tool using Service Management Automation (a variant of System Center Orchestrator for management portal for administrators), to provide capabilities to service providers and organizations to extend their offerings. For example, you could think of a scenario where every time a service administrator changes an existing plan, you want to run an automated task that propagates that change across all pre-existing subscriptions
WAPv1_Administration.docx