[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GCE: March Meeting Task List



I would add the following


3A6C8742.F62BECEF@lbl.gov">


1. Overview
2. Architecture
A. Define Grid software/services that the GCE currently depends upon
           B. Define Grid software/services that the GCE plans to make use of
           C. Define Grid software/services that are needed by the GCE but are not supported by the
                Grid
           D. Define software/services used/needed by the GCE  that are outside the scope the Grid

   3. Implementation
          A. Commodity technologies/software used (e.g., EJB, JMS, JINI,...)
          B.  Proprietary technologies/software developed that can be shared with others
 
3A6C8742.F62BECEF@lbl.gov">


A diagram is highly recommended

3. Supported Grid Services
A. Security
B. Information services
C. Scheduling
D. Data transfer
E. Additional Grid services

There's much more to be added I'm sure- please continue to iterate and refine
and hopefully we'll have something by the end of the week, we can use as a
template.

Jason


Tomasz

3A6C8742.F62BECEF@lbl.gov">


Tomasz Haupt wrote:

I like the plan, and I would be glad to help with creating the list of
issues and creating the template.
I will work on the web form for the BP. I guess, we need the template first.

What about announcing the request for papers? Who will do that?
Tomasz

Mary Thomas wrote:

All -

Time to get organized for the March meeting. Geoffrey Fox was
here in San Diego, and we came up with some thoughts, the
raw notes I have included below.

We discussed the history of DATOOR and ComputingPortals, what
was good & useful, and what was not. As a result, we decided that
a good focus and deliverable for our working group would be a special issue
of Concurrency, Practice and Experience focussed on current best
practices in Grid Computing.

Here is the basic Process, with some due dates
1. Find BP Candidates (have some, but need more ! European input)
2. Get a list of issues with elaborations (END of JAN BY ITERATING LIST
BELOW)
3. Ask BP Candidates to talk and write about issues at GGF1 with a
template doc (END JAN to END FEB)
4. Refine annotated issues list and produce call for papers
work on this at GGF1, complet by (END of MARCH)
5. Papers ---> publish
End June SUBMIT DATE
End August REVIEW PROCESS
End October Final
Feb 2002 Publish
6. Redo new list start End of June, finish for October Meeting
"list" becomes cosmic overview to be published next year
papers published in (5) become October presentations (Or, we
get a session at HPDC, but that is out of synch).

This is pretty exciting, since it gives us all a venue to publish,
and that will drive interest and _participation_. This will be a
valuable benefit to the GCE community. Should this task be added
to the charter?

For March, we ha! ve the following KEY tasks:
Task 1. GCE charter (NEARLY DONE)
Task 2. Drive GCE mailing list discussion of ISSUES
subtask: take issues list and create the Best Prac template
Task 3: Organize BP papers, and presentations for GGF1
subtask: submit as official WG docs
subtask: organize GGF1 presentations
Task 4. Organize CPE special issue
subtask: call for papers, etc.

I will be starting separate threads on some of these
(like the issues). We don't have much time for any of
these, but I think that we can get this done for GGF1.

Mary
---------------------------------------------------------------------
Mary Thomas Email: mthomas@sdsc.edu
Manager, Computational Sciences Portals Group Ph: 858.534.5061
Scientific Computing Department Fax: 858.534.5117
San Diego S! upercomputer Center www.sdsc.edu/~mthomas

=================================================================
RAW NOTES:

* Special Issue on Architecture and Applications of Portals
* special focus on portal architecture and implications for
Computational Grids
* Papers can contain:

Overview
Capabilities
Experience
Status
Futures
Architecture
What works CS and Application
Futures What will work in CS and Applications

Papers can address the following Issues:
Metaschedulers
(XML) object specifications for computers, users, programs, data streams
......
Security
Tools e.g. scientific whiteboard
Implementation
Architecture, Java EJB JMS SOAP Perl ...
Scalability
Fault Tolerance
Complexity (real people can't install Complex Codes)
! Others TBD

need to elaborate each item in issues list

Process
1. Find BP Candidates DONE
2. Get a list of issues with elaborations END JAN BY ITERATING LIST ABOVE
3. Ask BP Candidates to talk and write about issues at GGF1 with
template END JAN to END FEB
4. Refine annotated list and produce call for papers END MARCH
5. Papers ---> publish
End June SUBMIT
End August REVIEW
End October Final
Feb 2002 Publish
6. Redo new list start End June finish for October Meeting
7. Present mini-papers at October Meeting
8. March "list" becomes cosmic overview to be published.




--
Jason Novotny novotny@george.lbl.gov
Home: (510) 704-9917 Work: (510) 486-8662
NERSC Distributed Computing http://www-didc.lbl.gov