|
|
|
Andreas Savva: 08/15/2007 5:28 PM EDT
|
| |
Action: |
Update
Category set to General
|
|
|
|
|
Hiro Kishimoto: 09/24/2003 5:43 AM EST
|
| |
Comment: |
Bill said;
I've set up an OGSA-WG Logging System subgroup conference call for Wednesday 9/24 5:00PM - 6:30PM EDT
Toll-free #: 888-566-5909
International #: 212 234 0034
Passcode #: 31589
Confirmation #: 7257574
Here is my best shot at the timezone details:
- 09/24 1400-1530 US Pacific (GMT-7)
- 09/24 1500-1630 US Mountain(GMT-6)
- 09/24 1600-1730 US Central (GMT-5)
- 09/24 1700-1830 US Eastern (GMT-4)
- 09/24 2100-2230 GMT
- 09/24 2200-2330 UK (GMT+1)
- 09/24 2300-0030 Central Europe (GMT+2)
- 09/25 0600-0730 Japan (GMT+9)
|
| |
Action: |
Update
|
|
|
Hiro Kishimoto: 09/24/2003 5:43 AM EST
|
| |
Action: |
Update
artifact_status changed from Assigned to Closed
close_date changed from - to 2003-09-24 19:43
|
|
|
Hiro Kishimoto: 09/22/2003 7:08 PM EST
|
| |
Action: |
Update
assigned_to changed from 100 to 621
|
|
|
|
|
Hiro Kishimoto: 09/21/2003 3:47 AM EST
|
| |
Comment: |
OGSA Logger System strawman document by Bill Horn.
|
| |
Action: |
Update
|
|
|
Hiro Kishimoto: 09/17/2003 4:12 AM EST
|
| |
Comment: |
From telecon minutes 2003/09/11
- Owner is Bill(no gridforge account yet)
- Bill (& Jim) planning an event/logging/metering... teleconf for the week of 9/21.
- Strawman up by then.
|
| |
Action: |
Update
|
|
|
Hiro Kishimoto: 09/17/2003 4:11 AM EST
|
| |
Action: |
Update
artifact_status changed from Open to Assigned
|
|
|
Andreas Savva: 09/11/2003 6:18 AM EST
|
| |
Comment: |
From F2F 2003/09/03-04 minutes:
Task: What is the set of services/mechanisms needed to address all [these] efficiently?
Presentation by JW.
- support for legacy logger: both for wrapping and for native
access.
- micro-second access to logs (if you directly coupled)
Do we really need logging at the Grid level? Several good answers
supporting a yes answer.
- E.g, wide area logging is important, debugging, etc.
Comments:
- Logging code points --- where you can plugin logs transparently to
the application/requestor.
- And an admin i/f to control how/when pick log events.
- Distinguish between static & dynamic logging events
- static: Subscribe to them explicitly
- dynamic: A call made into the service triggers logging events to
be sent to the caller.
- Might also want a combination of the two.
- Common set of mechanisms/events for a number of related services
(logging, metering/accounting, etc.)
Key Requirement Categories:
- Generation:
- Propagation:
- Collection (Virtualization):
- Processing:
Channels:
- Data/Event
- Control
|
| |
Action: |
Update
|
|
|
|
