Folks, FYI, Perhaps you may have noticed, there is an announcement for GGF15 on the GGF Web site. Among them is a deadlines for sessions for GGF15. From http://www.ggf.org/ggf_events_chairinfo_ggf15.htm ... DOCUMENTS (for GGF15 CG/WG/RG Sessions) DEADLINE for submitting working drafts for GGF15 is Friday, 26 August 2005. SESSION SCHEDULING The DEADLINE for scheduling requests for WG/RGs is Friday, 2 September 2005. Also, there is an slot allocation policy explained. At this moment among the discussion of the drafting the spec, it sounds a bit too early what we can do in the GGF15 sessions, but here are some ideas for topics. - Introduction of the ACS (call for adoption of ACS.) - Spec. review sessions to cover, data handling or security, possibly with attendances from ogsa-data or ogsa-authz people. - Advanced use case discussion related to ACS, such as data replication, global-wide interactions, bare metal installation, etc... - Relationship to other standards. - Next step of ACS-WG. - Final draft spec review First three would be open audience session. Latter ones tend to internal discussions. One of my concern is how much we can prepare for these, especially if it is the presentation such as outreach or educational. I'd like to hear who are interested in leading the session for each. So depending on that we may end up with few sessions for internal discussion. Also, it is advised that each WG has two sessions at most in the new policy announced. We have two more calls to discuss about the GGF sessions. In the next and following calls, we would cover this. This is a reminder for the topic to be covered.
We agreed that we will skip the call for next week. Date: Aug 24 Wed 20:00 EDT/Aug 25 Thu 9:00 JST Calling #: will be announced later
-Keisuke
We had a good meeting today with the CDDLM team during the OGSA F2F. The minutes from today will contain details, however I wanted to capture some additional points specific to ACS: 1. A need for an integration point between ACS and CSG (Candidate Set Generator) was raised today, by Andrew I believe. This means that the CSG would need to be able to get the application metadata in order to make an appropriate decision on where a particular job can execute. I propose therefore that this be considered to ensure that either the entire property set be defined in our spec or that the spec allow for dynamic properties which could be provided by the client when constructing the archive (admin data?). These would be accessible by the CSG via WS-ResourceProperties, as stated in the strawman. Is there a standardized namespace to cover such things that would be required (memory utilization, disk space, time, speed, bandwidth, OS, containers, etc)? 2. Andrew also raised a use-case which involves making a copy of an AA and creating a new AA from it by extending it and overwriting some of the contents with perhaps different DD information which might have some particulars for a different organization. This would mean that the new AA would have a new EPR. We may want to consider this and whether or not our current set of portypes is sufficient. 3. Work shall proceed to design a more complete abstract interaction diagram which captures all the moving parts: EMS: BES, EPS, CSG, JSDL, CDDLM, WS-Agreement, WS-Naming, etc. This would build on the EMS box slide and would contain boxes representing all the parts to represent more of the ideal goal. It will most likely be presented at the next GGF. 4. We should also probably use WS-Names instead of EPRs. WS-Naming will be discussed tomorrow. 5. Idea of using NFS or CIFS as a protocol/means to read/write was mentioned. -- -- Michael Behrens R2AD, LLC Cell: 571-594-3008 ___________________________________________________________ $0 Web Hosting with up to 200MB web space, 1000 MB Transfer 10 Personalized POP and Web E-mail Accounts, and much more. Signup at www.doteasy.com
Mike and Pete, Thank you very much for reporting the OGSA F2F. I also read the minutes and content materials on the GridForge. It sounds great that there was great progress in the relationship between ACS and other EMS activities! I have some questions.
We had a good meeting today with the CDDLM team during the OGSA F2F. The minutes from today will contain details, however I wanted to capture some additional points specific to ACS:
1. A need for an integration point between ACS and CSG (Candidate Set Generator) was raised today, by Andrew I believe. This means that the CSG would need to be able to get the application metadata in order to make an appropriate decision on where a particular job can execute. I propose therefore that this be considered to ensure that either the entire property set be defined in our spec or that the spec allow for dynamic properties which could be provided by the client when constructing the archive (admin data?). These would be accessible by the CSG via WS-ResourceProperties, as stated in the strawman. Is there a standardized namespace to cover such things that would be required (memory utilization, disk space, time, speed, bandwidth, OS, containers, etc)?
I remember that JSDL defines resource requirement terms such as memory, disk space, OS, etc. Was there any mention of JSDL regarding this topic?
2. Andrew also raised a use-case which involves making a copy of an AA and creating a new AA from it by extending it and overwriting some of the contents with perhaps different DD information which might have some particulars for a different organization. This would mean that the new AA would have a new EPR. We may want to consider this and whether or not our current set of portypes is sufficient.
I think this may be done by retrieving entire archive by "GetArchive" then creating new AA with local modification.
3. Work shall proceed to design a more complete abstract interaction diagram which captures all the moving parts: EMS: BES, EPS, CSG, JSDL, CDDLM, WS-Agreement, WS-Naming, etc. This would build on the EMS box slide and would contain boxes representing all the parts to represent more of the ideal goal. It will most likely be presented at the next GGF.
Sounds good.
4. We should also probably use WS-Names instead of EPRs. WS-Naming will be discussed tomorrow.
What is WS-Names? Is it the name of XML types? or name of specification? What is the difference between WS-Names and WS-Naming?
5. Idea of using NFS or CIFS as a protocol/means to read/write was mentioned.
See you on the call! Sachiko
participants (3)
-
Keisuke Fukui -
Michael Behrens -
Sachiko Wada