RE: [saf] Simple Cloud Usecases

["Lipton, Paul C" <Paul.Lipton@ca.com>]

Dave,

Thinking cap responses below. Generally, I am +1 on all your excellent (as usual) ideas! 

Thanks,
Paul 
 
Paul Lipton
VP, Industry Standards and Open Source 
Member, CA Council for Technical Excellence 
Phone (preferred number!): +1 215 539-2731
Mobile: +1 267 987-6887
Email: paul.lipton@ca.com

THIS MESSAGE MAY CONTAIN CONFIDENTIAL, PRIVILEGED OR OTHER LEGALLY PROTECTED INFORMATION. IT IS INTENDED FOR THE ADDRESSEE ONLY. IF YOU ARE NOT THE ADDRESSEE (OR SOMEONE THE ADDRESSEE AUTHORIZED TO RECEIVE THIS MESSAGE), YOU ARE PROHIBITED FROM COPYING, DISTRIBUTING OR OTHERWISE USING IT. PLEASE NOTIFY THE SENDER AND RETURN IT AT OUR COST. THANK YOU.


-----Original Message-----
From: David Snelling [mailto:David.Snelling@UK.Fujitsu.com] 
Sent: Friday, February 12, 2010 6:11 AM
To: saf@lists.oasis-open.org
Subject: [saf] Simple Cloud Usecases


Folks,

As promised here is the start of a thread on use cases for Cloud  
interactions moderated (in any way) by Symptoms. I suggest we limit  
this thread to the use cases themselves and discuss them in a separate  
thread to avoid confusion (Jeff thanks for the notes) NB: I merged 2  
and 3 from the call and number 3 is a new one.

Use Case 1: Automation of Increased Provisioning

- Provider contributes (and publishes) a Protocol to add additional  
resources (VM, etc).
- Consumer contributes Syndromes (including signature based on the  
Symptoms he will emit) for detecting poor customer response time;
- The provider knows nothing of the consumer semantics and vica versa.
[[Paul]] Just a thought. Who hooks them together? Does it matter? 

Use Case 2: Automation of Decreased Provisioning

- Provider publishes a Syndrome (including signature based on Symptoms  
he will emit) for detecting multiple Idle VMs allocated to a given  
consumer.
- This Syndrome also includes a Protocol for decommissioning the VM  
within the environment.
- Consumer takes the published Syndrome and Protocol (possibly  
modifies parameters specific to her needs, such as VM shutdown  
process) and adds this to the catalogue.
[[Paul]] Wouldn't be more useful if the consumer could add *business-relevant* aspects to the pattern instead of a VM shutdown process? The provider is far more expert than the consumer in that area. Also, standards like DMTf cloud incubator (and most other cloud APIs) will allow you to shut down a VM and enhancements to standards like CIM might allow the detection of an idle VM.  I would suggest that the Consumer add something like a pattern that detects when a "sale" is about to be launched. When that sale flag is set, idle VMs are NOT decommissioned because we will be needing to respond to a wave of sales soon and don't want to have slow response times discourage sales. Try to do that with a conventional spec! :-) 

Use Case 3: Green Policy Management

- The Provider publishes a Symptom relating to the current CO2 burn of  
the customer's current computational estate.
- The consumer can then simple run a Symptoms diagnostician  
(internally or hosted/provided by the provider) to modify her QoS to  
keep CO2 below some policy determined level.
[[Paul]] I like this a lot. We should talk to the OASIS Emix TC about this. Emix feeds the money and carbon cost as Symptoms to a framework that reflects corporate *business and regulatory policy!* Try to encapsulate that with a simple management spec! This is multi-faceted with real business value. 

More later. Keep your thinking caps on over the weekend.




Take care:

     Dr. David Snelling < David . Snelling . UK . Fujitsu . com >
     Fujitsu Laboratories of Europe Limited
     Hayes Park Central
     Hayes End Road
     Hayes, Middlesex  UB4 8FE
     Reg. No. 4153469

     +44-7590-293439 (Mobile)





______________________________________________________________________
                                        
 Fujitsu Laboratories of Europe Limited
 Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE
 Registered No. 4153469
 
 This e-mail and any attachments are for the sole use of addressee(s) and
 may contain information which is privileged and confidential. Unauthorised
 use or copying for disclosure is strictly prohibited. The fact that this
 e-mail has been scanned by Trendmicro Interscan does not guarantee that 
 it has not been intercepted or amended nor that it is virus-free. 

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php