[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Possible TC Actions to Consider
I agree with Dave - a Cloud profile helps us have an interesting scenario and to also piggyback in the Cloud "buzz", which could help disseminate our group. For this reason I would assign it a high priority in our list.
On the same train of thought we could think of a number of other interesting applications, such as Social Networking / Knowledge Management, SOA, Virtualization / Appliances, Grid, Green Computing, etc.
Other than that I think we should also pay attention soon to Systems Management despite being "bread and butter" - and at the same time address the differences between us and the CDM work from DMTF... which is a question that has already been brought up by others commenting on symptoms...
And there are many other interesting scenarios too which we have discussed in the past in our pre-standard meetings, and Industry-related scenarios would be good to have in our repertoire as well. We wouldn't be able to address all these with depth but the idea of having mini-scenarios for understanding and dissemination (and to maybe "seed" other sub-initiatives) is probably a good thing.
In connection with this expanded scenario list we should also discuss strategies for marketing and expansion to promote growth in our group. Our first mission I believe should be to make people notice this initiative and get them interested on possible applications and start forming a larger community. This agrees well with the concept of being a "broad" and generic specification.
Marcelo Perazolo
IBM Systems Director
IBM Corporation
phone: +1-919-5438491
email: mperazol@us.ibm.com
David Snelling ---10/29/2009 05:41:16 AM---Folks, I have commented of the naming issue, but not the Cloud Profile:
From: | David Snelling <David.Snelling@UK.Fujitsu.com> |
To: | "Lipton, Paul C" <Paul.Lipton@ca.com> |
Cc: | <saf@lists.oasis-open.org> |
Date: | 10/29/2009 05:41 AM |
Subject: | Re: [saf] Possible TC Actions to Consider |
I see the dilemma in either keeping the medical analogy or going full-IT or something else... the name of the specification is tied to this decision.
It depends a lot on what we want to be the focus. I believe we would want a very broad core specification and then do a deep-dive in each domain applications of the core spec, possibly in sub-groups under our TC or even totally different specifications spawned in OASIS after the core spec is ready. The IT Management space would be one, the Cloud space another, then others like Process Management, specific industries like Energy, Healthcare, etc. All these domains would have the option to extend the core spec to their own needs and to define authoritative classifications types for symptoms/syndromes/prescriptions/etc. (for better exchange of knowledge among intra-domain implementations).
A good non-biased replacement for "autonomic" has always been "self-management" but then again "management" has a bit more of an IT-specific connotation...
If we go with the IT-biased terminology my suggestion is this:
SMF - Self-Management Framework
AMF - Automated Management Framework
If we stick with Medical terminology:
SDF - Self-Diagnostic Framework
SDTF - Self-Diagnostic & Treatment Framework
If we abstract from everything and try to have a very broad terminology that can be applied to any multiple domains:
SRF - Self-Reasoning Framework
RAF - Reasoning & Automation Framework
SRKF - Self-Reasoning & Knowledge Framework
In my particular opinion I think we should eliminate the IT-biased option. I believe a medical analogy is something that everybody understands and despite what blog comments elsewhere may say it's something that differentiates this effort and gives it an interesting appeal... In a close second I also favor a broader generic terminology with the words "Reasoning", "Knowledge" and "Automation"... these are terms that - in my opinion - fit well in several different application domains - but are not as appealing I think.
I also disagree with having terms like Optimization and Remediation in the name associated to the core spec because I believe the uses will be broader than that - including prediction/avoidance and full root-cause resolution of problems (not only remediation), security issues identification and prevention, configuration and deployment issues, etc. In autonomic computing terminology we used to classify "Self-Management" in four different quadrants: Self-Healing, Self-Configuring, Self-Optimizing and Self-Protecting - symptoms were supposed to help in all quadrants, not being specific to one or two of them...
I'm also not too keen with "Framework" - I wish I had a better suggestion for that, but at the moment I haven't...
Marcelo Perazolo
IBM Systems Director
IBM Corporation
phone: +1-919-5438491
email: mperazol@us.ibm.com
<image002.gif>"Lipton, Paul C" ---10/26/2009 02:01:52 PM---Hi all,
<image004.png> From: | <image005.png> "Lipton, Paul C" <Paul.Lipton@ca.com> |
<image004.png> To: | <image005.png> <saf@lists.oasis-open.org> |
<image004.png> Date: | <image005.png> 10/26/2009 02:01 PM |
<image004.png> Subject: | <image005.png> [saf] Possible TC Actions to Consider |
______________________________________________________________________ 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. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]