Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "COSMOS data collection"

(→‎Agenda)
Line 32: Line 32:
 
* Review action items
 
* Review action items
 
* i7 scope
 
* i7 scope
 +
* Firm up timeframes for the CA PoC demo (Jimmy Mohsin and Jack Devine)
 +
* We need a dedicated design session for the i7 / i8 Broker and Management Domain in the first week of Oct.  Can we focus the next Arch meeting on this? (Jimmy Mohsin)
 
* Cosmos DC framework technology stack and support matrix
 
* Cosmos DC framework technology stack and support matrix
 
** Redistributable Components (logging, reporting, web server, etc)
 
** Redistributable Components (logging, reporting, web server, etc)

Revision as of 10:48, 27 September 2007

COSMOS Main Page

Data Collection

Meeting Title: Conference Call on COSMOS Data Collection
Link to information on Wiki: CosmosDataCollectionComponent
Date & Time: Tuesday October 2, 2007 at 11AM EDT
Toll-free Dial-in number: +1 (866) 213.1962
Primary International Dial-in: +1.609.454.9912
Passcode: 2025533#

Contact

Email [Don Ebright] Phone +1 (313) 227.6734

Agenda

  • Status updates and agenda changes
  • Review action items
  • i7 scope
  • Firm up timeframes for the CA PoC demo (Jimmy Mohsin and Jack Devine)
  • We need a dedicated design session for the i7 / i8 Broker and Management Domain in the first week of Oct. Can we focus the next Arch meeting on this? (Jimmy Mohsin)
  • Cosmos DC framework technology stack and support matrix
    • Redistributable Components (logging, reporting, web server, etc)
    • Operating System
    • Languages
    • Certifications
    • Production environment considerations

Topic suggestions for future meetings

  • Use Cases - 45 minutes - Jimmy Mohsin
  • Requirements for Security in the COSMOS DC and which iteration should / will contain Security - 30 minutes - Jimmy Mohsin
  • Leveraging CMDBf Use Case
    • What value will an adopter derive by utilizing this use-case? (Jimmy Mohsin)
    • What is the definition of exact deliverable, i.e what is in the final relase package for this use case? (Jimmy Mohsin)
    • What are the design / implementation pre-requisites for implementation of the CMDBf use case (Jimmy Mohsin)
    • Will this use case result in one ER or multiple, i.e. how will the work be divided? I hope MULIPLE! (Jimmy Mohsin)
    • How many resources are envisioned to be utilized and from which companies? (Jimmy Mohsin)
    • What is the estimated time scope in weeks AND iterations (i7? i7 & i8?) (Jimmy Mohsin)
    • Who will define the quality metrics and by when? (Jimmy Mohsin)
    • We need clear (and timely) timeframes for design completions. (Jimmy Mohsin)
  • "Facilitation of Adoption for the COSMOS DC" or "Adoptability of the COSMOS DC" (Jimmy Mohsin)
    • Now that we are headed toward implementing a fairly heavy duty use case, we also need to think about making the COSMOS DC easy to use by our future adopters.
    • What comprises a COSMOS DC GA release package?
    • Who is the target of the COSMOS DC GA release? Is it developers? Business users? Architects? ALL of these audiences?
    • What sort of sample implementations should be included so that ALL audiences are able to see value in the COSMOS DC?
    • What sort of documentation should be included?
    • Do we list the hardware / software pre-requisites for the COSMOS DC?
    • What is our install and software upgrade approach?
    • Is there ANY linkage of all these to the SDD initiatives?
    • Will there be any sort of support?

Minutes of prior meetings

Retrieved from "https://wiki.eclipse.org/index.php?title=COSMOS_data_collection&oldid=52160"

Back to the top