Download Educational-SAF_for_Cloud_Business_Alignment-WD

Symptoms Automation
Framework (SAF)
for Cloud Business Alignment
OASIS SAF TC
Working Draft 03
29 April 2010
What is SAF?

An information model



Describing, recognizing, and reacting to multi-domain
problems/opportunities
Enabling vendors, integrators, and organizations to codify
their best practices
And SHARE them in a machine readable and interoperable
way
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
What is SAF?

Symptom


Syndrome


a rule envelope identifying meaningful pattern of Symptoms
Protocol


an event envelope indicating that a situation is present in the system
an action envelope defining treatment template necessary to create a
Prescription
Prescription

a concrete instance of a Protocol. Used to provide remediation,
diagnostics, preventative measures, or optimizations
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
SAF for Cloud Business
Alignment

The problem scenario


A cloud consumer: an online sales company
Subtle warnings of a potential peak in sales




Strong indications of sudden surge in sales




More web site browsing (operations department)
A call from a regional sales manager
A small increase in online sales system
Media endorsement (marketing department)
Lots of buzz in blogs (RSS Feeds)
All this info cannot be combined and analyzed
properly
Result: cloud capacity is not ready to handle the
sudden rise! Lost profit...
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
SAF for Cloud Business
Alignment

How do we merge info/content from all
aspects of the business?



internal departments
external sources
How do we connect the high level
business conditions to appropriate and
automated actions in the Cloud?
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
consumer
provider
A Cloud consumer wants to do business
with a Cloud provider. They willcatalogue
use SAF
to bridge their knowledge domains.
Consumer will also use SAF to merge
data from the many different business
aspects.
* These are roles in the framework, not necessarily people! They will usually be software entities.
** The Catalogue, Diagnostician, and Practitioner(s) could be implemented in various ways,
e.g. Provider provides the Catalogue and Practitioner, and the Consumer the Diagnostician.
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
Let’s collaborate to understand each
other better!
consumer
Cool! I’ll provide a catalogue where we can
link your business concepts to my cloud
operations
provider
catalogue
* These are roles in the framework, not necessarily people! They will usually be software entities.
** The Catalogue, Diagnostician, and Practitioner(s) could be implemented in various ways,
e.g. Provider provides the Catalogue and Practitioner, and the Consumer the Diagnostician.
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
consumer
I will provide a Protocol template that
modifies server capacity –since I know
how to do this.
provider
catalogue
* These are roles in the framework, not necessarily people! They will usually be software entities.
** The Catalogue, Diagnostician, and Practitioner(s) could be implemented in various ways,
e.g. Provider provides the Catalogue and Practitioner, and the Consumer the Diagnostician.
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
consumer
I also have the ability to emit Symptoms
about server outages. I’ll add Syndromes
to the catalogue to detect these
Symptoms.
provider
catalogue
* These are roles in the framework, not necessarily people! They will usually be software entities.
** The Catalogue, Diagnostician, and Practitioner(s) could be implemented in various ways,
e.g. Provider provides the Catalogue and Practitioner, and the Consumer the Diagnostician.
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
And since I know my business, I will provide a Syndrome
to identify important business conditions
consumer
provider
For example, I will merge data from all my
departments and external sources pertaining to
my sales...
catalogue
...so that I can identify potential sudden
increase in my sales!
* These are roles in the framework, not necessarily people! They will usually be software entities.
** The Catalogue, Diagnostician, and Practitioner(s) could be implemented in various ways,
e.g. Provider provides the Catalogue and Practitioner, and the Consumer the Diagnostician.
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
Finally, I will associate Syndromes to Protocols. In other
words, map business decisions to desired responses.
consumer
provider
For example, if my sales increase Syndrome is
triggered, I’ll invoke your Protocol to increase
my server capacity!
catalogue
* These are roles in the framework, not necessarily people! They will usually be software entities.
** The Catalogue, Diagnostician, and Practitioner(s) could be implemented in various ways,
e.g. Provider provides the Catalogue and Practitioner, and the Consumer the Diagnostician.
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
consumer
provider
catalogue
I work for the consumer, and I’ll be
constantly and iteratively checking
incoming data (Symptoms) to see if I
identify some important business
condition (Syndrome)!
*Although the Diagnostician is
supplied by the Consumer in this
example to show the flexibility of
SAF, it will typically be supplied
by the Provider along with
Catalogue authoring tools, so as
to increase the service value
provided to the customers
I work for the provider, and I will be
“implementing” Prescriptions
relevant to him.
practitioner
diagnostician
For example, I will be arranging to
increase server capacity whenever
needed.
* These are roles in the framework, not necessarily people! They will usually be software entities.
** The Catalogue, Diagnostician, and Practitioner(s) could be implemented in various ways,
e.g. Provider provides the Catalogue and Practitioner, and the Consumer the Diagnostician.
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
consumer
provider
This is the operations department. We
will automatically be emitting low level
Symptoms with web site browsing rates
This is the sales department. We will
operations periodically emit Symptoms with the rate
of shop sales
sales
marketing
3rd part
news analysis
This is marketing. I will manually emit
Symptoms over email or phone
whenever something significant
happens. diagnostician
catalogue
practitioner
*Some Symptoms will be low level
mechanically produced (web site
hits) while other high level ones can
be derived or be manually emitted
(marketing calls). Some emitters
may not even know they participate
in SAF –merely sending data or
notifications around!
I am a contractor service provider. I
analyze news and RSS feeds and send
statistics on the ‘buzz’/hype about the
company * These are roles in the framework, not necessarily people! They will usually be software entities.
** The Catalogue, Diagnostician, and Practitioner(s) could be implemented in various ways,
e.g. Provider provides the Catalogue and Practitioner, and the Consumer the Diagnostician.
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
consumer
operations
provider
with all the roles introduced,
and the
catalogue
Catalogue filled in by Consumer and
Provider, this merged environment
begins to operate iteratively under
normal business conditions, when at
some point an interesting situation
appears...
practitioner
sales
diagnostician
marketing
3rd part
news analysis
* These are roles in the framework, not necessarily people! They will usually be software entities.
** The Catalogue, Diagnostician, and Practitioner(s) could be implemented in various ways,
e.g. Provider provides the Catalogue and Practitioner, and the Consumer the Diagnostician.
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
consumer
provider
Web site browsing has
gone up!
catalogue
operations
sales
practitioner
Call: CEO interviewed
and endorsed on CNN!
diagnostician
marketing
3rd part
news analysis
* These are roles in the framework, not necessarily people! They will usually be software entities.
** The Catalogue, Diagnostician, and Practitioner(s) could be implemented in various ways,
e.g. Provider provides the Catalogue and Practitioner, and the Consumer the Diagnostician.
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
consumer
provider
catalogue
operations
Store sales have
upward trend
practitioner
sales
diagnostician
marketing
There is lots of talk/buzz/hype about the
* These are roles in the framework, not necessarily people! They will usually be software entities.
part
company in the blogosphere!
** The Catalogue, Diagnostician, and Practitioner(s) could be implemented in various ways,
news analysis
e.g. Provider provides the Catalogue and Practitioner, and the Consumer the Diagnostician.
3rd
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
consumer
provider
catalogue
operations
Combining all this info (Symptoms), I found
the business condition (Syndrome) of
potential sudden increase in sales!
practitioner
sales
diagnostician
marketing
3rd part
news analysis
I’ll send the relevant Prescription to
the practitioner to increase server
capacity!
* These are roles in the framework, not necessarily people! They will usually be software entities.
** The Catalogue, Diagnostician, and Practitioner(s) could be implemented in various ways,
e.g. Provider provides the Catalogue and Practitioner, and the Consumer the Diagnostician.
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
consumer
provider
catalogue
operations
practitioner
I know how to do this cause I speak
this Cloud Provider’s language (e.g.
Fujitsu SOP API)
sales
diagnostician
marketing
3rd part
news analysis
* These are roles in the framework, not necessarily people! They will usually be software entities.
** The Catalogue, Diagnostician, and Practitioner(s) could be implemented in various ways,
e.g. Provider provides the Catalogue and Practitioner, and the Consumer the Diagnostician.
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
consumer
provider
Here you are, get some more servers
proactively so you can accommodate
the anticipated growth!
catalogue
operations
practitioner
sales
diagnostician
marketing
3rd part
news analysis
* These are roles in the framework, not necessarily people! They will usually be software entities.
** The Catalogue, Diagnostician, and Practitioner(s) could be implemented in various ways,
e.g. Provider provides the Catalogue and Practitioner, and the Consumer the Diagnostician.
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
SAF for Cloud Business
Alignment

With Symptoms


Consumers can map their business
conditions to Cloud operations
It becomes possible to blend information
from many domains
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
SAF for Cloud Business
Alignment

Benefits for consumer




Improved operations and understanding by merging
info from different business aspects
Better positioned to accommodate sudden business
changes
Cloud provisioning maps naturally to business
requirements
Benefits for provider


Significant differentiator and value added capabilities
Automated and improved responses to meet
changing customer needs
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
Participate

What we need

Real cloud consumer requirements



Around business functions in the cloud,
such as energy, identity, contract, policy
management, QoS, etc.
Validation of our Cloud use cases
Direct communication and/or potential
for participation in the OASIS
Technical Committee
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS
More Info and Contact

Contact



Stavros Isaiadis, Fujitsu (SAF TC Co-chair)
[email protected]
Jeff Vaught, CA (SAF TC Co-chair)
[email protected]
OASIS SAF Technical Committee

http://www.oasis-open.org/committees/saf/

Current Working Documents


http://www.oasisopen.org/committees/documents.php?wg_abbrev=saf
Example Use Case Working Draft

http://www.oasisopen.org/committees/download.php/36886/UseCaseAutomated_Provisioning-WD.doc
This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS