Community
Participate
Working Groups
All, Which is the right page to capture information that addresses the scenario painted below? Specifically, I assume we need to publish the following information for COSMOS 1.0: 1. Recommended hardware configuration(s) 2. Recommended non-COSMOS software configuration(s) 3. Recommended COSMOS software guidelines Should this info go on http://wiki.eclipse.org/COSMOS_M2_Dependencies? _____________________________________________ From: cosmos-dev-bounces@eclipse.org [mailto:cosmos-dev-bounces@eclipse.org] On Behalf Of Mohsin, Jimmy Sent: Monday, January 14, 2008 3:57 PM To: Cosmos Dev Subject: [cosmos-dev] COSMOS QA strategy - Operational criteria and theimpact Team, As you know, we have been talking about the QA Criteria and strategy for a while now… I had a question that came up internally in this regard… Please consider the following points: 1. We are yet to define / finalize our operational criteria for COSMOS 1.0. 2. We are also yet to specify any kind of bounds on COSMOS 1.0, e.g. .. consider the following possibility: a. An adopter takes the COSMOS 1.0 code and deploys a Domain and Broker b. She then ties in TEN or so MDRs each with GIGABYTES worth of data c. She then executes a plethora of queries, each of which returns MEGABYTES of data. I paint this worst case scenario as we all know that there is NO shortage of LARGE existing data sources… d. Everything comes crashing down, and the adopter gets the impression that COSMOS has issues… 3. In view of preventing the above from happening, let us say we have the operational criteria in place for i9; and then we discover that the code does not meet these criteria and has deficiencies that result in operational inefficiency 4. In this (hopefully unlikely ???) scenario, re-factoring work would need to be done, which will result in downstream implications for our release timeframes. How do we deal with this situation? What else can we do to mitigate this risk, other than defining Operational Criteria? Should we specify guidelines and operational best practices? Should we define hardware configurations? Anything else we should be thinking about? Is this purely an exercise in good documentation or do we need other checks and balances to ensure that the COSMOS "safe operation" constraints are not violated? Thanks, Jimmy Mohsin
This really belongs in cosmos.doc and perhaps in cosmos.build if we choose to go beyond documentation to address this ER. However, since cosmos.doc does not exist yet, I have put this in cosmos.web.
Please review the opertional critiria as defined in 214576. This ER will require significant input from Development.
We also need to define ALL platforms / OS's supported and not supported.
Rich, Can you please comment on which part of the User Guide (or any other document) addresses this question? Thanks, Jimmy
This question has come to me from numerous adopters... Some of the questions I have been asked: 1. How many MDRs can a single COSMOS Broker handle? 2. What are the recommended specs for the machine hosting the COSMOS codebase? 3. How many clients can talk to a COSMOS Broker at a time? 4. Assuming a multiple client situation, how many queries may be submitted to an MDR at a time?
This question has come up numerous times from several potential adopters. The transactionally intensicve / sensitive products are even more interested in the COSMOS footprint.
Reassigning to me as a placeholder.
Added Paul Stratton to the cc list.
Added Craig to the cc list and upped the time to 80 hours.
Jimmy will get this started.
This is now under review.
