A Service Level Agreement (SLA) is a legal contract that ensures quality of service between parties. However, it can be difficult to guarantee levels of quality and detect SLA violations in cloud computing infrastructures. The document proposes using Model Driven Engineering (MDE) to formally define SLA contract requirements and integrate it with a multi-agent system to autonomously monitor for SLA violations in real-time. This combined approach of MDE and multi-agent systems aims to improve transparency and enforcement of SLA contracts for cloud services.

1. SLA Violation
www.iamrahuljain.in

2. Why SLA Violation… ???
www.iamrahuljain.in

3. What is SLA violation?
• Some businesses prefer or are obliged to have a
certain Service Level Agreement in place.
• The SLA sets a definite timeframe in which tickets
have to be answered or chats and calls have to be
picked up.
• If they are not answered or picked up within the
specified timeframe, SLA Violation occurs.
www.iamrahuljain.in

4. Why This Condition Arise…?
• The number of processors provided by the cloud providers
is less than the requested number of processor by the jobs
or cloudlet.
www.iamrahuljain.in

5. So…What companies normally do?
• If too many SLA Violation occur, a company should
reconsider their SLA setups and preferences or
should empower their workforce with more agents
or with better helpdesk tools.
www.iamrahuljain.in

6. Functionality
Customer SLA Violation Management functionality includes:
• Notifying appropriate people or systems to remedy the violation.
• Per the SLA contract, quantifying the violation in terms of an
adjustments or actions per the contract.
• Passing this adjustment or action on to billing or appropriate systems
for remedy.
• Tracking and management of open Customer SLA issues.
www.iamrahuljain.in

7. An Architecture for Detecting
SLA Violations in Cloud
Computing Infrastructures
www.iamrahuljain.in

8. FoSII Infra Overview
www.iamrahuljain.in

9. www.iamrahuljain.in

10. Each FoSII service implements three interfaces:
(i) negotiation interface
necessary for the
establishment of SLA
agreements.
www.iamrahuljain.in

11. (ii) application
management interface
necessary to start the
application, upload
data, and perform
similar management
actions.
www.iamrahuljain.in

12. (iii) self-
management
interface necessary
to devise actions in
order to prevent
SLA violations.
www.iamrahuljain.in

13. Working Of FoSII Infra
• The self-management
interface is implemented
by each Cloud service
and specifies operations
for sensing changes of
the desired state and for
reacting to those
changes.
www.iamrahuljain.in

14. Working Of FoSII Infra
• The host monitor sensors
continuously monitor the
infrastructure resource
metrics and provide the
autonomic manager with
the current resource
status.
www.iamrahuljain.in

15. Working Of FoSII Infra
• The runtime monitor
sensors sense future SLA
violation threats based
on resource usage
experiences and
predefined threat
thresholds.
www.iamrahuljain.in

16. Finally..
• Logically, FoSII infrastructure consists of multiple
components working together to achieve a common goal.
• In this architecture we focus on the knowledge management
component and the LoM2HiS framework since they are
responsible for system monitoring and detection of SLA
violations.
www.iamrahuljain.in

17. Combining multi-agent systems
and MDE approach for
monitoring SLA violations in the
Cloud Computing
www.iamrahuljain.in

18. Multi-agent systems (MASs) in order to
monitor SLA violations in real-time.
www.iamrahuljain.in

19. Multi Agent Systems
• MASs are suitable tools
for self-detection of
failures and self-
monitoring of cloud
operations and services,
QoS negotiation and SLA
management.
www.iamrahuljain.in

20. Multi Agent Systems
•They are designed to
operate in a
dynamically changing
environment.
www.iamrahuljain.in

21. Multi Agent Systems
• Our main motivation is
firstly to use MDE
technology for the creation
of the SLA contract and then
to integrate MASs in order
to control the quality of
service contract and
guarantee transparency and
symmetry with respect to
the SLA contract between
prospective signatories www.iamrahuljain.in

22. Proposed Architecture
www.iamrahuljain.in

23. Multi-agent systems and
MDE approach
www.iamrahuljain.in

24. Take A Easy Note:
• A Service Level Agreement (SLA) is a legal contract
between parties to ensure the Quality of Service
(QoS).
• A Service Level Agreement (SLA) is a legal contract
between parties to ensure the Quality of Service
(QoS).
www.iamrahuljain.in

25. Is There Any Guarantee..??
•However, It becomes hard to guarantee QoS
levels and detect SLA violations. Therefore,
we propose to use MDE (Model Driven
Engineering) to express the SLA contract
requirements.
www.iamrahuljain.in

26. • That MDE created with a specific modelling language
(DSML), will be used harmonically with a Multi-agent
systems (MASs) in order to monitor SLA violations in
real-time
www.iamrahuljain.in

27. Multi-agent systems and MDE approach for
monitoring SLA violations
www.iamrahuljain.in

28. Autonomous SLA violation
monitoring and filtering
www.iamrahuljain.in

29. Autonomous SLA violation monitoring and filtering
www.iamrahuljain.in

30. Thank You.!
www.iamrahuljain.in