1. Symptoms Automation Framework (SAF) for Cloud Business Alignment OASIS SAF TC Working Draft 06 06 August 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 Cloud Management Challenge Human experts in specific IT infrastructure and business domains possess substantial knowledge about prevention, remediation, and optimization of systems based on business conditions. The Cloud breaks down opportunities for these experts (often residing in multiple cloud consumers and providers) to collaborate in order to effectively capture, combine, and leverage this silo-ed knowledge across their various multiple domains in an automated fashion. Thus, while cloud providers will be able to provide standardized management interfaces to control their services, business consumers will be unable to adequately automate and obtain value for their business using these management interfaces. The SAF is a catalog-based XML collaborative knowledge framework that is designed to address these challenges by automating appropriate responses to changing business conditions and integrating contributions from diverse domains. SAF has applicability to cloud computing (using the SAF Cloud Profile) as well as many other architectures and disciplines.

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 SAF? n An information model and set of architectural roles l Describing, recognizing, and reacting to multi- domain problems/opportunities l Enabling vendors, integrators, and organizations to codify their best practices l And share/automate them in a machine readable, interoperable way

4. 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? n Information Model l Symptom n An event indicating that a business condition is present l Syndrome n A rule identifying meaningful pattern of Symptoms l Protocol n An action defining a template to create a Prescription l Prescription n a concrete instance of a Protocol Typically used for remediation, diagnostics, prevention, or optimization

5. 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? n Architectural Roles (slightly simplified) l Syndrome and Protocol Catalog (a.k.a. SAF catalog) n Domains collaborate by contributing to this repository l Diagnostician n Recognizes conditions by matching Symptoms to Syndromes in the SAF catalog. Identifies related Protocols. l Practitioner n Uses Protocols to take actions by creating Prescriptions l Case Manager n Acts as the coordinator of the framework. Directs the actions of the above-mentioned roles as it keeps track of the of Symptoms and the diagnose-prescribe cycle.

6. This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS Cloud/Business Alignment Scenario n Online sales company (and Cloud Consumer) l Multi-domain conditions indicate upcoming sales surge n More web site browsing (operations) n A call from a regional sales manager (field organization) n A small increase in online sales system (accounting) n Media endorsement (marketing) n Lots of buzz in blogs (RSS feeds – independent service) l Problem (business perspective) n Scattered, un-integrated, unleveraged knowledge What business conditions are relevant and when? How do we integrate diverse knowledge? How do we rapidly respond to changing conditions?

7. This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS Business/Cloud Alignment Scenario n Business/IT alignment... How did that work out in the past? Not well! l Problem (general IT perspective) n Widely distributed business/IT knowledge n How can business/IT collaborate, analyze & respond quickly? l It’s much more difficult in the cloud! n Simple challenge in this scenario: adjust cloud capacity across multiple systems and providers as needed by each provider... quickly, automatically, appropriately n We can’t meet this challenge! Cloud capacity is not ready to handle the sudden rise! Business unresponsive... Lost profit... n Let’s revisit the scenario with SAF...

8. 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 * 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. A Cloud consumer wants to do business with a Cloud provider. They will use SAF to bridge their knowledge domains. Consumer will also use SAF to merge data from the many different business aspects.

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 catalogue Let’s collaborate to understand each other better! Cool! I’ll provide a SAF catalogue where we can link your business concepts to my cloud operations * 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.

10. 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 will provide an action (Protocol) template that modifies server capacity –since I know how to do this. * 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.

11. 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 also have the ability to emit Symptoms about server outages. I’ll add patterns (Syndromes) to the catalogue to match these types of Symptoms (similar to events). * 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.

12. 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 And since I know my business, I will provide a Syndrome to identify important business conditions For example, I will merge descriptions (Syndromes) from all my departments and external sources pertaining to my sales......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.

13. 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 Finally, I will associate Syndromes to the actions (Protocols) that you have provided. In other words, map business decisions to desired responses. For example, if my “Sales Increase Syndrome” is triggered, I’ll invoke your Protocol to increase my 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.

14. 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 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. 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)! 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. *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

15. 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 * 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. practitioner 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 periodically emit Symptoms with the rate of shop sales This is marketing. I will manually emit Symptoms over email or phone whenever near-term our forecasts change. I am a contractor service provider. I analyze news and RSS feeds and send statistics on the ‘buzz’/hype about the company *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!

16. 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 * 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. practitioner with all the roles introduced, and the Catalogue collaboratively 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...

17. 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 Web site browsing has gone up! Call: CEO interviewed and endorsed on CNN! * 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. practitioner

18. 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 Store sales have upward trend * 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. practitioner There is lots of talk/buzz/hype about the company in the blogosphere!

19. 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 Combining all this info (Symptoms), I found the business condition (Syndrome) of potential sudden, large increase in sales! I’ll use the relevant Protocol to create and send a 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. practitioner

20. 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 I know how to increase capacity cause I run in the Cloud Provider’s infrastructure. I can be anything from a script to a BPEL process. It doesn’t matter. * 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. practitioner

21. 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 * 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. practitioner Here you are, I’ve provided some more servers proactively so you can accommodate the anticipated growth!

22. 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 n With SAF l Consumers can map their business conditions to Cloud management operations l It becomes possible to blend information from many domains and for automation to act on that information

23. 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 n Benefits for cloud consumer l Improved operations and understanding by merging info from different business aspects l Better positioned to accommodate sudden business changes (also threats, etc.) l Cloud provider actions maps naturally to business requirements of consumer n Benefits for cloud provider l Significant differentiator and value added capabilities l Automated and improved responses to meet changing customer needs

24. This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS Invitation n More use cases for SAF Cloud Profiles l Cloud business conditions (for Syndromes) l Cloud provider interfaces (for Protocols) n So we can map to diverse provider capabilities n Validation of our Cloud use cases n Use cases for other SAF profiles l e.g., identity, policy management, QoS, financial, etc. n Join the OASIS SAF Technical Committee

25. This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS n TC Chairs (contacts) 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 Information and Contacts