1. Symptoms Automation Framework (SAF) for Cloud Business Alignment OASIS SAF TC Working Draft 01 8 April 2010

2. 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 Symptoms? n An information model l Describing, recognizing, and reacting to multi-domain problems/opportunities l Enabling vendors, integrators, and organizations to codify their best practices l And SHARE them in a machine readable and interoperable way

3. 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 Symptoms? n Symptom l an indicator that a situation is present in the system l e.g. “server XYZ ping failed”, “server application ABC unresponsive” n Syndrome l an identifiable meaningful pattern of Symptoms l e.g. if “server XYZ ping failed” && “server application ABC unresponsive” then server XYZ is probably down n Protocol l a treatment template necessary to create a Prescription l e.g. “reboot server” n Prescription l a concrete instance of a Protocol. Used to provide remediation, diagnostics, preventative measures, or optimizations l e.g. “reboot server XYZ”

4. This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS How does Symptoms work? n Domain experts fill in a Catalogue with Syndromes and Protocols l i.e. what to keep an eye on in their system, and how to react if it appears. n Symptoms are emitted from various sources (within or external to the system) n A Diagnostician matches the incoming Symptoms against Syndromes from the Catalogue n If it matches a Syndrome, it creates a Prescription and sends it to a designated Practitioner n The Practitioner “implements” the Prescription

5. This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS symptom emitter How does Symptoms work? Diagnostician Practitioner Catalogue any complex system symptom emitter Symptom emitter symptoms prescriptions syndromes protocols

6. This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS A simple example n Symptom A: “Ping to Application Server A (192.168.1.2) failed” n Symptom B: “Application ‘EXCEL’ unresponsive” n Symptom C: “Ping to Router failed” n Syndrome ‘Server Down’: “Symptom A && Symptom B” l Associated Protocol ‘Reboot Server’: “Reboot server at IP address X” n Syndrome ‘Network Card Down’: “Symptom A && Symptom C” l Associated Protocol ‘Reset Network Card’: “Reset network interface X” n If Symptoms A and B appear in the system, the Syndrome ‘Server Down’ will be recognized and a Prescription will be generated from the associated Protocol l ‘Reboot server at IP address 192.168.1.2’

7. This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS Symptoms for Cloud Business Alignment n The problem scenario l A cloud consumer: an online sales company l Subtle warnings of a potential peak in sales n More web site browsing (operations department) n A call from a regional sales manager n A small increase in online sales system l Strong indications of sudden surge in sales n Media endorsement (marketing department) n Lots of buzz in blogs (RSS Feeds) l All this info cannot be combined and analyzed properly l Result: cloud capacity is not ready to handle the sudden rise! Lost profit...

8. This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS Symptoms for Cloud Business Alignment n How do we merge info/content from all aspects of the business? l Internal departments l external sources n How do we connect the high level business conditions to appropriate and automated actions in the Cloud?

9. 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 diagnostician operations marketing catalogue sales 3 rd part news analysis Let’s collaborate to understand each other better! Cool! I’ll provide a catalogue where we can link your business concepts to my cloud operations I will provide a Protocol template that modifies server capacity –since I know how to do this. And since I know my business, I will provide a Syndrome to identify important business conditions For example, I will merge data from all my departments and external sources pertaining to my sales......so that I can identify potential sudden increase in my sales! And if my sales are to go up suddenly, I’ll use your Protocol to increase my server capacity! Web site browsing has gone up! Store sales have upward trend Call: CEO interviewed and endorsed in CNN! There is lots of talk/buzz about the company in the blogosphere! Combining all this info, I found the business condition of potential sudden increase in sales! I’ll inform the practitioner to enact the relevant Protocol to increase server capacity! I know how to do this cause I speak this Cloud’s language (e.g. Fujitsu SOP API) * 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. I work for the consumer, and I’ll be checking incoming data to see if I identify some important business condition! I work for the provider, and I will be “implementing” Prescriptions relevant to him. practitioner For example, I will be arranging to increase server capacity whenever needed. This is the operations department. We will be emitting Symptoms to denote web site browsing rates This is the sales department. We will emit Symptoms with the rate of shop sales This is marketing. I will emit Symptoms whenever something significant happens. I am a contractor service provider. I parse news and RSS feeds and emit Symptoms to denote ‘buzz’ about the company with all the roles introduced, and the Catalogue filled in by Consumer and Provider, this merged environment begins to operate under normal business conditions, when at some point... Here you are, get some more servers proactively so you can accommodate the anticipated growth!

10. This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS Symptoms for Cloud Business Alignment n With Symptoms l Consumers can map their business conditions to Cloud operations l Becomes possible to blend information from many domains

11. This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS Symptoms for Cloud Business Alignment n Benefits for consumer l Improved operations and understanding by merging info from different business aspects l Better positioned to accommodate sudden business changes l Cloud provisioning maps naturally to business requirements n Benefits for provider l Significant differentiator and value added capabilities l Automated and improved responses to meet changing customer needs

12. This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS Collaborations n What we need l Real cloud consumer requirements n Around business functions in the cloud, such as energy, ID, contract, policy management, QoS, etc. l Validation of our Cloud use cases l Direct communication and/or potential for participation in the OASIS Technical Committee

13. This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS n Contact l Stavros Isaiadis, Fujitsu (SAF TC Co-chair) Stavros.Isaiadis@uk.fujitsu.com l Jeff Vaught CA (SAF TC Co-chair) vauje01@ca.com n OASIS SAF Technical Committee l http://www.oasis-open.org/committees/saf/ http://www.oasis-open.org/committees/saf/ l Current Working Documents n http://www.oasis- open.org/committees/documents.php?wg_abbrev=saf http://www.oasis- open.org/committees/documents.php?wg_abbrev=saf l Example Use Case Working Draft n http://www.oasis- open.org/committees/download.php/36886/UseCase- Automated_Provisioning-WD.doc http://www.oasis- open.org/committees/download.php/36886/UseCase- Automated_Provisioning-WD.doc More Info and Contact