1. Cloud Automation and Business Alignment using OASIS SAF Speaker Name Venue Date

2. Agenda n Surviving the Perfect Storm n Symptoms n Plans

3. Anatomy of a Perfect Storm n Subtle warnings that a sales storm is coming… l More web site browsing (operations) l A call from a regional sales manager l A small increase in online sales system

4. Anatomy of a Perfect Storm n The sales storm hits… l Oprah endorsement (celebrity!) n Media follow-ups (RSS feeds) l A surge of online sales!!! n Cloud provider not ready! l All executives abandon ship! n How could this have been prevented?

5. Surviving the “Perfect Storm”

7. Symptoms Automation Framework 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

8. Solution: SAF Model n Symptom - A Symptom is the indicator that a situation is present in the system. Symptoms represent the dynamic state of the system. n Syndrome - A Syndrome is an identifiable collection of zero or more related Symptoms (as identified by a signature). n Protocol - A Protocol is the treatment-regimen, providing the template necessary to create a Prescription. n Prescription - A Prescription is an instance corresponding to a Protocol. It is used to provide remediation, diagnostics, preventative measures, or optimization to be performed.

9. Solution: SAF Roles

10. XXXX Prescription http://saf.org/XXXX/prescriptions/001 http://saf.org/XXXX/custom_compute_create 2010-03-25_13:45 client.id=1234-5678-9 change.percentage=20 POST /compute HTTP/1.1 Host: example.com Authorization: Basic xxxxxxxxxxxxxxxxxxx User-Agent: XXXX-client/1.0 (linux) libcurl/7.19.4 XXXX/1.0 Category: compute; scheme="http://purl.org/XXXX/kind#"; label="Compute Resource" Category: ubuntu-9.10; scheme="http://purl.org/XXXX/category#template"; label="Ubuntu Linux 9.10" XXXX.compute.cores: %X% XXXX.compute.memory: %Y% Accept: */*

11. Integrating XXXX and Symptoms n Prescriptions from XXXX l n Symptoms from XXXX l

12. Planning n Devise a scenario n Paper Design n Develop Live Demo n Select a Venue

13. Summary n Where is the bridge? l Connecting customer business conditions to cloud provider responses n Sales fluctuations to resource provisioning n Carbon emission compliance to energy management n Promotion l Demo?

14. Contact Information n SAF TC home page: l http://www.oasis-open.org/committees/saf/ http://www.oasis-open.org/committees/saf/ n Join SAF TC: l http://www.oasis-open.org/join/ http://www.oasis-open.org/join/ l join@oasis-open.org join@oasis-open.org n Prospective documents at: l http://xml.coverpages.org/SAF/ http://xml.coverpages.org/SAF/ This document is an OASIS SAF TC Working Draft. It does not reflect the views of the OASIS SAF TC or of OASIS.

15. Discussion

16. The Sting n Impact: Bull with two Horns l Lack of uptake in many potential Cloud sectors due to Business/Cloud barrier l Obscurity for XXXX n Aim: l We have strong synergy between Symptoms and XXXX. Let’s exploit it l We have a cunning plan