FW: cloud profile

["Vaught, Jeffrey A" <Jeffrey.Vaught@ca.com>]

I was thinking about the different SAF roles and "where in the cloud" they would be situated.
Below is a grid of some possibilities, along with a simple use case.
Paul's Scenario #1 & #2 fit into my use case #5 (CC is emitter, CP is diagnostician and practitioner).
Paul's Scenario #3 is a combination use case where both CC & CP are using SAF.

CC=cloud consumer
CP=cloud provider

Emitter	Diagnostician	Practitioner	Use Case
CP	CP	CP	Standard DataCenter use cases
CC	CC	CC	Standard DataCenter use cases
CP	CP	CC	A marketing firm CC uses a CP email service to generate leads for their product (also known as Spam).  CP rates vary based on the number of mails sent in a batch.  10K mails in a batch costs $5.00, whereas 20K mails in a batch is only $7.00. The CP SAF diagnostician recognizes a historical pattern of repeated small batches (<10K) within a few hours of each other.  The CP suggests combining the batches for rate optimization via a SAF "combine mail batch" prescription. The CC practitioner executes the prescription and combines batches for rate optimization.
CP	CC	CP	Marketing firm CC uses a CP email service (as above). CP emits a Symptom that says "Rates have changed.  Batches less 20K mails cost $10.00".  This means no price break until you reach 20K mails. The CC diagnostician considers the new price break with pending batch submissions and generates a "combine mail batch" prescription to be executed by the CP practitioner.
CC	CP	CP	CC emits a "SLA breach" symptom with regards to the CP database query performance.  CP diagnostician detects these symptoms from several of its consumers and generates a "DB optimization" prescription that remediates the problem.
CC	CC	CP	CC detects an increasing usage trend with respect to its Online application, and will need to provision additional storage from the CP.  A prescription is generated to the CP to provision additional storage.
CC	CP	CC	CC is using storage service from CP according to api "X".  CC emits a symptom saying "Can't connect to storage service using api 'X'".  CP diagnostician detects this symptom and runs investigative prescriptions to determine if CC has upgraded to the new api "Y".  The diagnosis is that CC has not upgraded, and a prescription is generated to "upgrade to api Y".  The CC pracititioner automatically downloads and installs new api Y.
CP	CC	CC	Marketing firm CC uses a CP email service (as above). CP emits a Symptom that says "Rates have changed.  Batches less 20K mails cost $10.00".  This means no price break until you reach 20K mails. The CC diagnostician considers the new price break with pending batch submissions and generates a "combine mail batch" prescription to be executed by the CC practitioner.