Community
Participate
Working Groups
See attachment for draft copy of the COSMOS 1.0 Project Release Plan.
Created attachment 63078 [details] COSMOS 1.0 Project Release Plan draft Draft of the COSMOS 1.0 Project Releaes plan (RTF filetype)
Created attachment 63100 [details] COSMOS 1.0 Project Release Plan draft
Created attachment 64095 [details] COSMOS 1.0 Project Release Plan - 4/17 draft I have attached the latest draft of the COSMOS 1.0 release plan. Please review and make comments.
I am guessing you want a defect for each major comment, so my first comment is about calling this 1.0. What does it mean to have SML based models in 1.0? Are these API and long lived. Being 1.0 implies a major commitment to long lived stable release. How does COSMOS go from an eclipsecon demo to 1.0 in a few months? I am not being critical of the function or the project, just questioning "1.0"
(In reply to comment #4) > I am guessing you want a defect for each major comment, so my first comment is > about calling this 1.0. > What does it mean to have SML based models in 1.0? Are these API and long > lived. > Being 1.0 implies a major commitment to long lived stable release. How does > COSMOS go from an eclipsecon demo to 1.0 in a few months? I am not being > critical of the function or the project, just questioning "1.0" Good point. Toni is working on determining the appropriate release number. This change will be made before this plan will be brought forward for approval. Thanks, Tania
Just some thoughts...: 1) Under "Project Designs" why don't we have a description for "Management Enablement"? I'm personally not clear on what will be included under this subproject. I first thought that Data Collection will provide the framework and the Management Enablement will provide the exemplary tooling that will demonstrate the framework but this doesn't seem to be the case. Can we include a short description of what will be included under this subproject in a future release? 2) Why are TPTP defects/enhancements listed under "COSMOS Data Collection Project Plan Items" table? The majority of the bugzilla entries listed belong to TPTP and probably shouldn't be included under the COSMOS release plan. 3) I was hoping the document would include a little more meat as to what should be delivered per iteration, the use cases of the release, how the plan items of each subproject will fit together, and etc... Maybe that falls outside the scope of this document.
Where can I find a summary of the requirements being considered?
I don't believe sharing word documents is appropriate. Projects are encouraged to publish with one of the web technologies and not assume reviewers have any proprietary software.
I believe the SML tooling is actually more correctly targeted at SML-IF documents in the use cases and not just random SML. Which version of SML will be supported in this 1.0 GA release? the draft currently supported, the submission to W3C or some other hybrid?
Regarding comment #9 Resource Modeling project supports the SML and SMLIF version spec submitted to w3c
Adding the validation support to the Project Design section Resource Modeling Project - Aims to provide support for validating and building a common model to represent the information being shared in a system management scenario. The Service Modeling Language Interchange Format (SML-IF) will be used to share model components between the tools involved in a system management activity. All Resource Modeling enhancements in plan for 1.0 are marked as P1. This is the complete list 179828 2007-03-28 enh P1 amehrega@ca.ibm.com NEW Resource 1.0 Wind 1.0i4 Provide the concept of a repository under the resource mo... 181594 2007-04-09 enh P1 amehrega@ca.ibm.com NEW Resource 1.0 Wind 1.0i4 SML validator should accept input other then File resources 178590 2007-03-21 enh P1 popescu@ca.ibm.com NEW Resource 1.0 All 1.0i3 Create SML descriptors for agents 180068 2007-03-29 enh P1 popescu@ca.ibm.com NEW Resource 1.0 Linu 1.0i4 Provide a Data Layer for Data Visualization access to Res... 172682 2007-02-02 enh P2 David_Whiteman@us.ibm.com NEW Resource 1.0 Wind 1.0i4 Create more test cases for the validation plug-in
I tried to follow some of the defect links in teh summary tables. Most have an extra _ on the end making them not work. The ones I followed only had one line descriptions of the item, so I am struggling to understand what is really in plan.
(In reply to comment #11) 178590 is listed in the plan as well. I understand the desire to create this, but I don't understand making it GA.
After trying to read the document and bugzilla, I think I can answer the question "what data sources will be provided and supported in June?" I think the intended answer is logs processed by a GLA, and an SML-IF based model. It would be good to really call this out specifically if this is the case. Yet I am still left with the question of what standards this GA function is actually supporting. GLA certainly is not, and WEF/C.B.E. may become such but are not really broadly adopted in the current form. Also the SML model is not standard. I am not suggesting this is wrong, it just needs to be communicated clearly.
In reply to comment #11 178590 is listed in plan since this is a line item that will be worked on and delivered in the June timeframe. The content is to be made available as an addition to the Data Center sample. The SML definitions and sample implementation have been checked in CVS under the Data Center sample plugin. We should take this off line and discuss any possible issues related to this work.
Created attachment 64334 [details] COSMOS 1.0 Project Release Plan - 4/19 Draft
The draft of the COSMOS Release Plan is now on the wiki for review. Please visit the wiki for the latest version: http://wiki.eclipse.org/index.php/Cosmos_Release_Plan#Community_Systems_Management_Open_Source_.28COSMOS.29_1.0_Project_Plan_.28Draft.29
(In reply to comment #17) > The draft of the COSMOS Release Plan is now on the wiki for review. Please > visit the wiki for the latest version: > So where are the issues now being tracked? I notice few people subscribed to this defect. btw the wiki #defects link is broken due to no target, and I believe based on your plan the target milestone for this defect is out of date ;-)
Created attachment 65050 [details] COSMOS 1.0 Project Release Plan - 4/26 Draft Added references to Data Reporting bugzilla entries.
The COSMOS 1.0 Project Release Plan is complete.
Verified and closed on January 2, 2007.
