View
214
Download
0
Category
Preview:
Citation preview
17 October 2006Cracow Grid Workshop ‘06
Execution Management and SLA Enforcement in Akogrimo
Antonios LitkeAntonios Litke, Kleopatra Konstanteli, Vassiliki Andronikou, Sotirios Chatzis, and Theodora
Varvarigou
e-mail:e-mail: ali@telecom.ntua.gr ali@telecom.ntua.gr
17 October 2006Cracow Grid Workshop ‘06
Presentation Outline
Architectural overview of Akogrimo
The need for SLAs
Component descriptions and interactions
Implementation issues
Related work
Conclusions
Questions/answers
17 October 2006Cracow Grid Workshop ‘06
OGSA-based Layered Architecture
An OGSA compliant architecture aims to
Manage resources across distributed heterogeneous platforms
Deliver seamless access control and quality of service
Provide a common base for autonomic management solutions
Define open, published interfaces
17 October 2006Cracow Grid Workshop ‘06
Akogrimo Architecture
Equipment
(Grid resources)
AkogrimoApplications / Scenarios
OGSA
Web Services
OGSA specific services
Service Level Agreement Enforcement
Execution Management Services
InformationServices
Data Management Services
Security Services
Physical Resources
WSRFWSRF – Based services
WSRF – Enabled Resources
WS – Resource LifeTime Management
WS – Resource Properties Management
WS – BaseNotifications WS – Addressing
Logical Resources
Communications
L2
IP Transport – Mobile IP
802.11Ethernet UMTS
QoS adaptation
17 October 2006Cracow Grid Workshop ‘06
Akogrimo Architecture
•Physical and logical resources layer
Resources comprise each and every capability of the Grid
•Physical resources, which include servers, storage, and network and Logical resources.
•Logical resources are above the physical and provide additional functionality by virtualizing and aggregating the resources in the physical layer.
•In Akogrimo communication resources are also incorporated in logical resources
17 October 2006Cracow Grid Workshop ‘06
The need for management of SLA
Grids and mobile Grids are dynamic environments subject to unpredictable changes:
system or network failures, system performance degradation, removal of machines, variations in the cost of resources,
Execution Management components should take care of conformance to the contractual terms of SLAs
EMS system monitors and manages the execution of the job until its completion
In case of violations, it takes actions to dynamically rectify them in such a way as to meet the terms defined in the related SLA
17 October 2006Cracow Grid Workshop ‘06
Grid Infrastructure Services
•Addresses the performance issues while conforming to the determined Service Level Agreement (SLA).
•Execution Management Services:
Instantiating and managing tasks
•SLA Enforcement:
SLA contractual terms that especially influence the execution of jobs
•Monitoring:
status of the execution, availability of services, and of gathering the relevant information
EMS
Monitoring
SLA-Decisor
SLA Access
SLA-Controller
Re
giste
r
Re
trie
ve Q
oS
p
ara
me
ters
Start/Stop monitoring
Create resourceActivate/Destroy
Cre
ate
busi
ness
reso
urce
Business Application
Service
Mo
nito
ring
n
otifica
tion
Viola
tion
d
ete
cted
Subs
crib
e
Stat
us n
otifi
catio
n
Su
bscrib
e
17 October 2006Cracow Grid Workshop ‘06
Example of QoS Parameters in SLAs
<QoSParams> <QoSItems> <QoSItem> <param>cpuSpeed</param> <paramValue>3.5</paramValue> <paramType>MHz</paramType> <threshold>40%</threshold> </QoSItem> <QoSItem> <param>diskSpace</param> <paramValue>1</paramValue> <paramType>GB</paramType> <threshold>20%</threshold> </QoSItem> <QoSItem> <param>memory</param> <paramValue>1</paramValue> <paramType>GB</paramType> <threshold>50%</threshold> </QoSItem> <QoSItem> <param>networkBandwidth</param> <paramValue>GOLD</paramValue> <paramType></paramType> <threshold></paramValue> </QoSItem> </QoSItems>
</QoSParams>
17 October 2006Cracow Grid Workshop ‘06
Discovery and Reservation phase
Service Interaction Interface
SLA-Access Step 2 ObjQoS getQoSParameters(String slaID)
SLA-Discovery Step 3 ArrayList findSuitableResources(objQoS objQoSData)
Business service Step 5 EndpointReferenceType create()
QoS Broker Step 6 Boolean setQoS(EndpointReferenceType serviceEPR, integer networkBundleType)
Step 8 EndpointReferenceType create() SLA-Controller
Step 9 Boolean registerToServiceDecisor(EndpointReferenceType slaControllerEPR, EndpointReferenceType serviceEPR)
17 October 2006Cracow Grid Workshop ‘06
Discovery and Reservation MSC
Client
EMS
1: Specify slaID and userID, submit request
for discovery and reservation of resources
SLA-Access
2: Retrieve QoS parameters from SLA
SLA-Discovery
3: Look for resources
4: Match? Create a service reservation
resource and add related info (slaID, userID, QoS)
RReservationResource
Business service
5: Create an business service
resource and manage its lifecycle
6: Add the EPR of the e-Health resource
to the reservation
11: Return the EPR of the reservation resource
SLA-ControllerQoS Broker
7: Perform network resources reservation
8: Create a SLA-Controller resource
10: Add the EPR of the SLA-Controller resource to the
reservation resource
SLA-Decisor
9: Register to the SLA-Decisor
17 October 2006Cracow Grid Workshop ‘06
Execution and Monitoring phase
Service Interaction Interface
Step 4 Boolean activateServiceController(EndpointReferenceType serviceEPR, objQoS objQoSData, String slaID)
Step 11 Boolean receiveInformationByMonitoring(EndpointReferenceType serviceEPR, objQoS objQoSData)
SLA-Controller
Step 17, 24 Void destroy()
SLA-Decisor Step 12 Boolean setViolation( EndpointReferenceType serviceEPR, Violation violation)
Step 5 Boolean startMonitoring( EndpointReferenceType serviceEPR, objQoS objQoSData, String slaID )
Monitoring
Step 14, 21 Boolean stopMonitoring( EndpointReferenceType serviceEPR)
Step 6 org.oasis.wsn.SubscribeResponse subscribe(org.oasis.wsn.Subscribe subscribeRequest)
Step 7 Boolean startMetering( EndpointReferenceType serviceEPR)
Metering
Step 16, 23 Boolean stopMetering( EndpointReferenceType serviceEPR)
Business Step 8 Not standard (depends on the e-Health service)
17 October 2006Cracow Grid Workshop ‘06
Execution and Monitoring MSC Client
EMS
1: Specify EPR of reservation resource, input for the service and submit request
RSLA-Controller
4: Activate SLA-Controller resource
SLA-Monitoring
5: Invoke Monitoring Service
7: Invoke Metering Service
SLA-Metering
8: Start execution of Business Resource
27: Return the output of the business service
execution
RBusinessResource
15: Stop Monitoring service
2. Find reservation resource
16: Stop Metering Service
24: Destroy SLA-Controller resource
RReservationResource
3. Retrieve info
26: Destroy Reservation Resource
25: Destroy Business Resource
SLA-Desicor
10: Significant change? Notify SLA-Monitoring11: Notify SLA-
Controller about the change
12: Violation? Notify SLA-Desicor13: Decide on
appropriate action
14: Reallocation needed? Notify EMS
19: Find new resources
18: Destroy Business Resource
20: Update Reservation Resource
21: Go back to step 3
and repeat sequence
17: Destroy SLA-Controller resource
22:Done? Stop Monitoring service
23: Stop Metering Service
6: Subscribe for notifications
9: Loop (Monitor execution)
17 October 2006Cracow Grid Workshop ‘06
Implementation issues
Globus Toolkit 4, and especially WS-GRAM and MDS4
SLA contracts management are developed using the WSRF.NET platform
Compelling implementation and technological challenge to see whether:
•The 2 main grid services development tools, implement the WS-related specifications in a transparent and interoperable way
17 October 2006Cracow Grid Workshop ‘06
Related work
GRIA (Grid Resources for Industrial Applications)• designed and developed the GRIA middleware based on Web Services
• supports the confirmation of a service offer through establishment of SLA and extensions of existing SLAs
GRASP (Grid-based Application Service Provision)• SLA management subsystem including the service provision negotiation based on QoS criteria and monitoring of the feasibility of the contract
Unigrids (Uniform Interface to Grid Services)• SLA framework and cross-Grid brokering services in order to support Grid economics
• integrating a Web Services Agreement-based resource management framework into the Unicore Grid middleware
17 October 2006Cracow Grid Workshop ‘06
...and what is special in Akogrimo?
1) SLA parameters do include network QoS parameters
2) Negotiation, reservation and execution are made on this basis also
3) Utilization of both toolkits: GT4 and WSRF.NET
4) Decision on appropriate action when violation and estimation of the significance of the violation through a dedicated component
17 October 2006Cracow Grid Workshop ‘06
Conclusion
•We presented an architecture to manage execution and enforce SLA in OGSA based grids and mobile Grids
Discovery and reservation phase
Execution and monitoring phase
•The proposed design has been implemented in GT4 and WSRF.NET
•Advancing attributes of SLA mangement with use of network resources
•For future research: To define an economic model based on how these violations affect the efficiency of Grids
17 October 2006Cracow Grid Workshop ‘06
Thank you!
Questions?
17 October 2006Cracow Grid Workshop ‘06
Backup slides
17 October 2006Cracow Grid Workshop ‘06
Akogrimo Architecture
•Web services layer
All Grid resources are modelled as services
Web Services Resource Framework (WSRF) defines a family of specifications for accessing stateful resources using Web services
•OGSA architected grid services layer
Overall grid management functionality
•Grid applications layer
High – level applications a client might require
For Akogrimo we have deployed an E – Health application offering a suite of E – Health services.
17 October 2006Cracow Grid Workshop ‘06
Grid Infrastructure Services Layer
SOAP
SOAP
SOAP
Mobile Network
Grid Infrastructure Services Layer
Data Management
EMS Metering SLA Enforcement
Monitoring Policy Manager
Application Services Layer
Mobile Network Middleware Service
Discovery AAA
Service Provisioning
Network Management
Application Service X
OpVO Manager
BP Enactment
Application Service N
OpVO Manager
BP Enactment
etc etc
etc
IPv6/MIPv6 Networks
QoS Broker Mobile Terminal
etc
17 October 2006Cracow Grid Workshop ‘06
Network QoS
•The Mobile Network Layer implements end-to-end Quality of Service, for all types of mobility
Make an effective use of network resources
Assure that a user can utilize the services he is entitled to without disruptions
•The QoS implementation
Allows fine-grained QoS control at the access networks
Aggregates different flows with the same QoS requirements in the core network
•
The network supports
well defined QoS bundles
Bundle 1 Bundle 2 Bundle 3 Mix audio + data High data + video Mostly voice 10 – Interactive 20 – Interactive 10 – Interactive 100 – Data 1000 – Data 1 – Priority 1 – Priority 200 – Priority 1 – Signalling 1 – Signalling 1 – Signalling 250 – Best Effort 250 – Best Effort
17 October 2006Cracow Grid Workshop ‘06
Application Services Layer
•Each application service requested by a client is modeled as a business process
•Workflows represent the automation of the business process
Each workflow coordinates and manages component services or entities involved into the automation of business process
•A Virtual Organization (VO) provides services and the means to manage and coordinate Business Processes
•Implementation of a Business Process implies
Creation of an Operational Virtual Organisation (OpVO) out of a base VO.
17 October 2006Cracow Grid Workshop ‘06
MDVO example focused on AAA
Recommended