HP Cloud OS for Moonshot Podręcznik Użytkownika Pobierz pdf (Strona 60)

HP Cloud OS for Moonshot Administration Dashboard Help Version 1.0

Page | 60

Understanding Workload Entities

Some of the important entities that help to make up Workloads based provisioning are:

Workloads Service

Facilitates automated deployment of a workload based service realization.

Workload

A composite entity comprising Application Image, Infrastructure Design, Infrastructure hints for

specific resource requirement.

Workload Topology

An infrastructure blueprint defining infrastructure topology.

Deployment Profile

A cloud specific workload binding document which references cloud resources and can be

provisioned (or deployed) as is to create a deployed workload. It references specific cloud

resources.

Deployed Workload

A realized service after the deployment profile has been successfully launched by the end user

Relationship between Workload Entities

A workload entity is an abstract representation of a service which maps to a given infrastructure blue-print

(technically termed as topology). The same workload can be realized by different cloud resources present

in the system which can be uniquely represented as deployment profiles.

For Example: Let us assume that a single server group based workload requirement is, to serve static

web hosting. As we know that both Scott_1 and Borman can serve static web hosting, it is thus possible

to have two different deployment profiles; where one maps to nova flavor compute resource of Borman

while the other maps to Scott_1. Also, a given deployment profile can be launched multiple times for

same or different user. Considering this, there is an inherent relationship amongst workloads, topology,

deployment profiles and deployed workloads which has been illustrated below:

Figure 43: Relationship between Workload Entities

1 2 ... 55 56 57 58 59 60 61 62 63 64 65 ... 125 126

Brak uwag

HP Cloud OS for Moonshot Podręcznik Użytkownika Strona 60