[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: TC Liaison with DMTF CMWG [PLEASE RESPOND BY 9/17]
Hi all, In reference to the Work Register document we are developing, I've taken a OASIS liaison policy (1) and I believe we need to bring our request to liaison to the President (If your reading of the policy is different please let me know.). I'd like to suggest the follow answers to the questions we are supposed to answer. Please respond with your feedback before 9/17. If there is no objection, around the 18th or so, I will send it off to the President along with a copy of the latest Work Register draft cc to the chairs or the entire TC, whatever folks suggest. Please respond with your suggestions by 9/17. I cannot attend the next SAF call. Please contact me if there are any concerns or whatever that come out of that call. REQUEST TO OASIS PRESIDENT: * Who is the other organization, what do they do, and what is the nature of the relationship suggested? (e.g. is it suggested that OASIS join the other organization and at what level, or vice versa.) [Paul} This would be a liaison relationship between the OASIS SAF TC and the DMTF Cloud Management WG (CMWG). * What are the benefits to OASIS of this relationship? What are the goals of OASIS in the relationship? [Paul] The SAF TC is developing a Cloud-Specific Profile that will reference the interfaces and model being developed by the CMWG as predefined Actions within the SAF catalog. The DMTF may be willing to promote this joint work in a press release and elsewhere. * Which particular activities (technical committees, member sections, etc.) at OASIS would be affected by the relationship? What effect will it have on them, and what level of involvement should be expected from them? [Paul] At a high level, in addition to the identification of additional use cases that support both our models, the SAF TC hopes to obtain valuable guidance and feedback from the CMWG on the proper definitions needed for SAF Catalog Actions to align with CMWG interfaces as well as potential Symptom definitions for Cloud Providers. Additionally, we'd like to jointly produce a white paper that defines the SAF Profile and how it works with CMWG interfaces. Additional details are provided in the DMTF Work Register document draft provided. * What are the benefits to the other organization of this relationship? What are the goals of the other organization in the relationship? [Paul] SAF provides a collaborative, automation knowledge framework to the lower-level granularity of CMWG interfaces that would potentially enable SAF-aware DMTF-enabled clouds to better serve their customers, providing greater agility and business/IaaS alignment. * What is the risk of negative impact on OASIS? [Paul] Other than the usual risks of failure associated with any such technical collaboration, none are apparent. * What liaison representation would OASIS be expected to send? [Paul] The SAF TC already has several members from multiple companies that also serve in the CMWG. Liaison between the groups would be natural and easy. No additional participation from OASIS staff is required. * What are the costs, obligations, and responsibilities to OASIS and/or its TCs? [Paul] Outside of the deliverables and potentially providing a press quote, we don't see any. (1) http://www.oasis-open.org/committees/liaison_policy.php Thanks, Paul Paul Lipton CA Technologies VP, Industry Standards and Open Source Member, CA Council for Technical Excellence Phone (new preferred number!): +1 215 539-2731 Mobile: +1 267 987-6887 Email: firstname.lastname@example.org 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.