[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cosmos-dev] End-to-End Scenario Definition - Meeting Notice
|
unfortunately, i've got a standing 10-11
on fridays
Mark Weitzel | STSM | IBM Software Group | Tivoli | Autonomic Computing
| (919) 543 0625 | weitzelm@xxxxxxxxxx
"Ebright, Don"
<Don.Ebright@xxxxxxxxxxxxx>
Sent by: cosmos-dev-bounces@xxxxxxxxxxx
06/07/2007 08:58 AM
Please respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx> |
|
To
| "Cosmos Dev" <cosmos-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [cosmos-dev] End-to-End Scenario
Definition - Meeting Notice |
|
9:00 isn't great for me. Could
we do it just before the 11:00AM Friday COSMOS status call?
Don
From: cosmos-dev-bounces@xxxxxxxxxxx
[mailto:cosmos-dev-bounces@xxxxxxxxxxx]
On Behalf Of Hawkins, Joel
Sent: Thursday, June 07, 2007 8:42 AM
To: Cosmos Dev
Subject: RE: [cosmos-dev] End-to-End Scenario Definition - Meeting
Notice
Friday morning at 9:00 would
be fine.
What’s the WSDM call?
-----Original Message-----
From: cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx]
On Behalf Of Mark D Weitzel
Sent: Wednesday, June 06, 2007 5:25 PM
To: Cosmos Dev
Cc: Cosmos Dev; cosmos-dev-bounces@xxxxxxxxxxx
Subject: RE: [cosmos-dev] End-to-End Scenario Definition - Meeting
Notice
Joel,
Is there a time that is better for you?
Friday morning at 9?
-mw
Mark Weitzel | STSM | IBM Software Group | Tivoli | Autonomic Computing
| (919) 543 0625 | weitzelm@xxxxxxxxxx
"Ebright, Don"
<Don.Ebright@xxxxxxxxxxxxx>
Sent by: cosmos-dev-bounces@xxxxxxxxxxx
06/06/2007 05:11 PM
Please respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx> |
|
To
| "Cosmos Dev" <cosmos-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [cosmos-dev] End-to-End Scenario
Definition - Meeting Notice |
|
Sheldon,
Joel and I have a conflict with this time slot. I am also scheduled
for the call to discuss moving WSDM components into COSMOS at 12:30 and
the COSMOS community call at 3:00.
BTW, as mentioned on the architecture call, we expect to populate the database
with live data instead of using a static set of historical data, although
there is no reason why we couldn't preload some "historical"
information as well.
Don
From: cosmos-dev-bounces@xxxxxxxxxxx
[mailto:cosmos-dev-bounces@xxxxxxxxxxx]
On Behalf Of Sheldon Lee-Loy
Sent: Wednesday, June 06, 2007 4:57 PM
To: cosmos-dev@xxxxxxxxxxx
Subject: [cosmos-dev] End-to-End Scenario Definition - Meeting
Notice
I opened bug https://www.eclipse.org/bugs/show_bug.cgi?id=191360
to track the creation of the end-to-end application data for the resource
model, statistical and logging data.
Jimmy, I couldn't add you to this bug since I don't know your bugzilla
id. You will have to add this yourself.
I set up a meeting to discuss the end to end model that we want to show
and the statistical and logging data we want to have in the databases.
This meeting is to flush out the details so that the resource model
team knows what should be modelled in SML and the data collection team
knows what they should capture.
Time: Thursday June 7, 2-3 PM EST
Toll Free Dial in: 1-866-254-5059
Local Dial In: 416-343-2607
Global Tool Free: 800-4444-1010
Conference ID: 2771920
The resource model team and data collection team should attend this call.
Thanks,
Sheldon
______________________________________
Sheldon Lee-Loy
Tivoli Autonomic Computing, IBM Toronto Lab
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it._______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev
=00
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.The contents of this e-mail are intended for the named
addressee only. It contains information that may be confidential. Unless
you are the named addressee or an authorized designee, you may not copy
or use it, or disclose it to anyone else. If you received it in error please
notify us immediately and then destroy it._______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev