150 likes | 271 Vues
Cloud Automation and Business Alignment using OASIS SAF. Speaker Name Venue Date. Agenda. Surviving the Perfect Storm Symptoms Plans. Anatomy of a Perfect Storm. Subtle warnings that a sales storm is coming… More web site browsing ( operations ) A call from a regional sales manager
E N D
Cloud Automation and Business Alignment using OASIS SAF Speaker Name Venue Date
Agenda • Surviving the Perfect Storm • Symptoms • Plans
Anatomy of a Perfect Storm • Subtle warnings that a sales storm is coming… • More web site browsing (operations) • A call from a regional sales manager • A small increase in online sales system
Anatomy of a Perfect Storm • The sales storm hits… • Oprah endorsement (celebrity!) • Media follow-ups (RSS feeds) • A surge of online sales!!! • Cloud provider not ready! • All executives abandon ship! • How could this have been prevented?
Symptoms Automation Framework • 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
Solution: SAF Model • Symptom - A Symptom is the indicator that a situation is present in the system. Symptoms represent the dynamic state of the system. • Syndrome - A Syndrome is an identifiable collection of zero or more related Symptoms (as identified by a signature). • Protocol - A Protocol is the treatment-regimen, providing the template necessary to create a Prescription. • Prescription - A Prescription is an instance corresponding to a Protocol. It is used to provide remediation, diagnostics, preventative measures, or optimization to be performed.
XXXX Prescription <Prescription> <PrescriptionId>http://saf.org/XXXX/prescriptions/001</PrescriptionId> <PrescriptionType>http://saf.org/XXXX/custom_compute_create</PrescriptionType> <ExpirationDate>2010-03-25_13:45</ExpirationDate> <Arguments> client.id=1234-5678-9 change.percentage=20 </Arguments> <Process> 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: */* </Process> </Prescription>
Integrating XXXX and Symptoms • Prescriptions from XXXX • Symptoms from XXXX
Planning • Devise a scenario • Paper Design • Develop Live Demo • Select a Venue
Summary • Where is the bridge? • Connecting customer business conditions to cloud provider responses • Sales fluctuations to resource provisioning • Carbon emission compliance to energy management • • • • Promotion • Demo?
Contact Information • SAF TC home page: • http://www.oasis-open.org/committees/saf/ • Join SAF TC: • http://www.oasis-open.org/join/ • join@oasis-open.org • Prospective documents at: • 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.