- ogsa-rss-bof - lists.ogf.org

[wg-all] Mailing List Changes
by Andre Merzky 03 Sep '06

03 Sep '06

Sorry for duplicates ------------------------------------------------------------ As of yesterday, all GGF/OGF mailing lists are migrated to the ogf domain. They are now managed by mailman, the web interface is available at http://www.ogf.org/mailman/listinfo With that migration, all list can be now reached via <list>@ogf.org The old @ggf.org addresses will be available for some time, but are bound to disappear eventually - please start using the ogf addresses! A number of lists have changed their names: ggf-it --> ogf-it ggf-office --> ogf-office ggf-proc-wg --> ogf-proc-wg ggf-sponsors --> ogf-sponsors ggf-tutorials --> ogf-tutorials ggf-compute --> ogf-compute ggflistowners --> ogflistowners ggfstudentmembers --> ogfstudentmembers Postings to the old list names get forwarded to the new ones. With the migration we have also been able to fix the archives - you may have noticed that list archiving stopped sometime in mid June. Well, now its working again, and all mails from June to now have been added to the archive. The list archives can be found at: http://www.ogf.org/archives/<list> If you are an list administrator, and would like to receive the list admin password, please contact postmaster(a)ogf.org. In general, however, we tried to map the old majordomo settings to the mailman settings, in terms of privacy etc, so no or little changes should be required from your side. The spam avoidance policy has been changed to some extent, and is somewhat stricter than before. Please let us know if you experience any trouble with that. On all questions in respect to mailing lists, or mails in general, please contact postmaster(a)ogf.org. Best regards, Andre. -- "So much time, so little to do..." -- Garfield -- wg-all mailing list wg-all(a)ogf.org http://www.ogf.org/mailman/listinfo/wg-all

1 0

GSA Use-Case Document in Public Comment
by Philipp Wieder 13 Sep '05

13 Sep '05

Dear All, the Grid Scheduling Architecture use case document has finally been submitted for public comment. You can get the current version at https://forge.gridforum.org/tracker/?aid=1611, the public comment will start once it is announced via the common GGF channels. Please read the document and comment on it since it is also input to the OGSA-RSS work. Best regards, Philipp. -------- Original Message -------- Subject: [gsa-rg] Use-Case Document in Public Comment Date: Tue, 13 Sep 2005 10:59:05 +0200 From: Ramin Yahyapour <Ramin.Yahyapour(a)udo.edu> Reply-To: Ramin.Yahyapour(a)udo.edu To: gsa-rg(a)ggf.org Dear all, I submitted last week our Use-case document to Greg Newby who is our GGF editor. He was so kind to upload the document to GridForge for public comment You can find the document tracker here: https://forge.gridforum.org/tracker/?aid=1611 Please use the public comment period to take a read of the doc and to provide some comments. As you may know, these comments are important for the GGF process. Therefore, also if you have no specific comments but find the document somehow useful, helpful etc: please tell so via the GridForge interface! Positive comments are also helpful comments... Best regards, Ramin -------- Original Message -------- Subject: Re: Document Submission from GSA-RG Date: Sun, 11 Sep 2005 22:13:17 -0800 From: Gregory Newby <newby(a)arsc.edu> To: Ramin Yahyapour <ramin.yahyapour(a)udo.edu> CC: Stephen Pickles <stephen.pickles(a)manchester.ac.uk>, Joel Replogle <replogle(a)ggf.org> References: <431ECD42.2060605(a)udo.edu> On Wed, Sep 07, 2005 at 01:21:38PM +0200, Ramin Yahyapour wrote: > Dear Greg, > > we from GSA-RG would like to submit our current GGF document draft about > "Grid Scheduling Use Cases". > > The doc is attached and can also be found at GridForge: > https://forge.gridforum.org/projects/gsa-rg/document/GridSchedulingUseCases… > > Unfortunately, I am not so skilled with GridForge and I could also not > find some kind of guidelines on how to formally submit a doc. > Therefore, I am not sure whether there is a formal electronic way in GridForge > to submit a document to the GGF editor. Let me know if I need to do something > somehow to create somekind of a GridForge "Tracker" to start the > document pipeline process for this doc. Thanks, Ramin. I've uploaded this & created a tracker item under the Editor project for you. Login to GridForge, then use this link to find the document: https://forge.gridforum.org/tracker/?aid=1611 You'll want to turn on "monitoring" via GridForge, so you can see as the document goes through changes. Joel will add it to the Public Comment screen over the next day or so, and I'll announce it to wg-all: this starts the 30-day public comment period countdown. You're urged to solicit comments, to get readers' responses. I made some formatting changes & formatting suggestions - see the tracker for details. Thanks for your efforts on this document. It looks like it will be a useful addition to the GGF document series. -- Greg Dr. Gregory Newby, Chief Scientist (Acting), Arctic Region Supercomputing Ctr Univ of Alaska Fairbanks-909 Koyukuk Dr-PO Box 756020-Fairbanks-AK 99775-6020 e: newby AT arsc.edu v: 907-450-8663 f: 907-450-8601 w: www.arsc.edu/~newby -- Dr.-Ing. Ramin Yahyapour | mailto:Ramin.Yahyapour@uni-dortmund.de Computer Engineering Institute | phone: +49 (231) 755-2735 University of Dortmund | mobil: +49 (179) 5261973 44221 Dortmund / Germany | fax: +49 (231) 755-3251

1 0

OGSA RSS (Resource Selection Services) WG
by Soonwook Hwang 23 Aug '05

23 Aug '05

Dear all, For those of you who have yet to be informed, I am pleased to let you know that the OGSA-RSS-WG was approved by the GGF Steering Group early this month. The focus of this OGSA-RSS-WG is on defining protocols and interfaces for the Resource Selection Services (RSS) portion of the OGSA EMS (Execution Management Services). The RSS consists of the Candidate Set Generator (CSG) and Execution Planning Services (EPS). The CSG is all about finding execution candidate locations and the EPS all about selecting the best execution location according to a given objective function. Please refer to https://forge.gridforum.org/projects/ogsa-rss-wg/ for more information about this working group. If you are interested in the group's ongoing activities, please subscribe its mailing list by sending an email with the body "subscribe ogsa-rss <email-address>" to majordomo(a)ggf.org. Best regards, Soonwook

1 0

Re: [ogsa-rss-bof] Strawmen...
by Mathias Dalheimer 03 Aug '05

03 Aug '05

Hi! (For the people on the OGSA-RSS-Bof mailing list: We had a short discussion on how to start the work on the service description...) Soonwook Hwang wrote: > Let me give it a thought on a simple usecase. > Hope to come up with at least a very simple one. Great! You'll find my current comments of the GSA-Usecase document attached. Basically, I extracted the section on how the various schedulers do their work (their internal workflow). Unfortunately, the use cases do not state for all use cases which data is needed, but I think this can be approximated by looking at their internal workflows. I also included a use case for calana currently submitted to the GSA, but not included in their documents so far. I would like to invite anyone to edit the document directly and send it back to me - I volunteer to synchronize the changes. In addition, I hope to identify some common properties we need to consider. This should be the basis of our interface design (for which Donal made a proposal, I would be happy to reuse it...) > Mathias, are you ever trying to map the > usecases that you are looking at onto > the OGSA-EMS Architecture? Would it work > out? This is a very interesting question. At the moment, I am rather optimistic that this can be done. The GSA also identified some common functionality in their GSA Requirement document (which is currently under development, but contains some points we might need to consider). It's here: https://forge.gridforum.org/docman2/ViewCategory.php?group_id=133&category_… Basically, all schedulers follow the procedure of collecting potential resources before actually selecting the right resource. This fits nicely in the scheme defined by OGSA-EMS. Comments welcome, Mathias

2 1

[Fwd: OGSA-RSS-WG approved]
by Mathias Dalheimer 02 Aug '05

02 Aug '05

Hi! Stephen Pickles just sent me an email: [snip] OGSA-RSS-WG has now been approved by the GGF Steering Group. Congratulations! [snap] Wahooo! Mathias

2 1

Strawmen...
by Donal K. Fellows 01 Aug '05

01 Aug '05

Hi all... Thinking about the upcoming F2F meeting, we're going to need some strawmen for people to poke fun at. Here's my first go (everything will need XML serialization, of course): CSG has one official operation: GetCandidates(JobDefinition[] atomicJobs) -> Candidate[] Each Candidate is a structure containing: EndpointReference eprOfBESToSubmitThisJobTo JobDefinition configuredAtomicJob ValuationTerm[] descriptionsOfQoSPriceEtc We permit multiple jobs in the request because this is useful in a setting where a CSG is defined hierarchically in terms of other CSGs (a good way of building a wider Grid in my experience). Any scheduling or reservation terms are done by writing extra things into the JobDefinition elements. JSDL is flexible enough for this. EPS needs at least this operation: PlanExecution(JobDefinition atomicJob, SelectionPolicy selector) -> ExecutionPlan I don't know what the SelectionPolicy will look like, but basing it off of Condor ClassAd selection rules might be a good start. The ExecutionPlan is a structure containing at least: EndpointReference eprOfBESToSubmitThisJobTo JobDefinition actualAtomicJobToSubmit ValuationTerm[] descriptionOfQoSPriceEtc (i.e. the contents of the Candidate) but I know more things will be needed to make this really work. The EPS will ask relevant CSG(s) for the candidates for the job submitted, and will then evaluate the policy to pick the best place to submit the job to. The EPS will not submit the job. The EPS *will* secure any reservations/holds required to carry out the selected candidate. However, an EPS really only becomes interesting when we move away from looking at single jobs; it's within the context of a workflow that having a service instead of doing it all by hand makes real sense. At least in my opinion. And I don't think we want to develop a workflow in this group! OK, that's my thoughts for now. Any opinions? Donal.

2 1

Regrets -- week of July 25-29
by Fred Maciel 23 Jul '05

23 Jul '05

Hi, On the week of July 25-29 I'll be in the SNIA/DMTF Technical Symposium. Regards, Fred Maciel Hitachi America R&D

1 0

Charter submitted
by Mathias Dalheimer 21 Jul '05

21 Jul '05

Hi! I just send our charter draft to Bill and Stephen, asking for GFSG approval. Thank you for all your input. Cheers, Mathias

2 1

Charter BoF report
by Mathias Dalheimer 20 Jul '05

20 Jul '05

Hi all, I just created the charter BoF report and would like to ask you to have a look at it. In addition, I edited the charter according to the comments we received. You find both files attached. Thanks, Mathias

4 14

OGSA RM teleconference -- where does resource modeling fits in?
by Fred Maciel 18 Jul '05

18 Jul '05

Hi, First of all, sorry for the cross-posting -- this subject involves all three WGs. Since GGF14 there have been a lot of discussions on where resource modeling fits -- BES considered it out of scope but Andrew thinks it's not totally out; RSS is discussing whether it's in scope; and this was discussed in the OGSA-WG also. So, let's discuss this in the Resource Modeling design team teleconference (which is, in fact, the place to discuss this). Oh, yes, part of this was supposed to be discussed in the RM teleconference this week, but only I and Ellen could come... Here are the details: Date: Tuesday, July 19th, at the following times: - 11:00-12:00 US Pacific (GMT - 7) - 12:00-13:00 US Mountain (GMT - 6) - 13:00-14:00 US Central (GMT - 5) - 14:00-15:00 US Eastern (GMT - 4) - 18:00-19:00 GMT - 19:00-20:00 UK (GMT + 1) - 20:00-21:00 Central Europe (GMT + 2) - 03:00-04:00 Japan (GMT + 9, following day) -- sorry. Dial-in: Toll Free: (888) 422-7120 Int'l Access: (608) 250-0194 Participant code: 693305 If screen sharing is needed, let's use Glance: URL: http://ogsa.glance.net Session key: 0719 Explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html See you there, Fred Maciel Hitachi America R&D

3 2