|
Hi
Paul,
Good
idea to try and grind out the value of SAF in concrete terms. My two
cents along the lines
Hi
all,
Not
really liking my previous missive regarding the Cloud Profile too much (it
goes too deep too quickly), please allow me to “pop the stack” with a
higher-level perspective, if I may. Forgive oversimplifications and
generalizations, but I am just trying to open up a brainstorming dialog.
One
might also note that since without SAF it is hard to do some things it might
be hard to find cloud use cases evolved and sophisticated enough in the real
world to be useful at this time in the industry. Just a thought.
I guess
without SAF it would be a combination of rules based systems and a complex event
processing system. One would also have to glue everything together with some
cross-domain integration "middleware" or similar... Nasty
stuff...
Existing
and emerging management and security standards will do things like the below
(basically everything done for SOA, but more RESTful and with a cloud provider
and virtualization slant):
*
Complain about misbehaving manageable resources (cloud entities, perhaps, like
virtual networks and CPUs) and provide metrics
*
Provide protocols and schema to manage your cloud resources (ask for a
template, establish a contract, provision a VM, whatever). In short, a sort of
standardized equivalent to EC2 APIs and protocols, if you
sould.
*
Identity, autht, authz in the cloud (and federation
stuff)
*
Privacy and location stuff (ie: “don’t host my data outside the country,
etc.”)
*
And so on…
So
we shouldn’t do that stuff.
What
is unique about SAF (some assertions)
*
It’s not the Symptoms, it’s the catalog. What is cool about the
catalog?
A.
TRANSLATION: You can “translate” a meaningful pattern (Syndrome) to a
meaningful action (Prescription).
B.
CROSS-DOMAIN: This translation can be from one domain to another domain or at
a higher-level within the same domain. These domains can be IT/cloud domains
and/or business/application/service domains.
C.
ITERATION: You can keep doing translations adding value over and over
again
D.
EXPERTISE/KNOWLEDGE: The catalog can encapsulate the expertise of human
experts, which is often most valuable when it is doing (guess) translation, is
cross-domain, and is iterative.
I usually also
emphasize the framework and the clear (?) definition of the architectural roles
one has to realize and their flexibility, e.g. multiple practitioners coming
from different users, multiple symptom emitters, multiple catalogue sources (to
combine domain specific knowledge?) etc.
Further, it is
the possibility of sharing this knowledge in standard means, that also attaches
value to SAF.
Finally, we could
mention the possibility for runtime adaptations to the catalogue, the ability to
have the system evolve in response to the environmental changes, e.g. add a new
syndrome after data mining over historical records and identify a new,
previously unknown pattern (as Dave has mentioned in the past). This might be
implied in Paul's "iteration" but not sure.
Cheers,
Stavros
______________________________________________________________________
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 and McAfee Groupshield does
not guarantee that it has not been intercepted or amended nor that it is
virus-free.
|
|