Differences between revisions 4 and 6 (spanning 2 versions)
Revision 4 as of 2006-06-26 17:20:11
Size: 6442
Editor: MarkNorman
Comment:
Revision 6 as of 2013-05-17 16:26:48
Size: 6412
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
See ["JISC Proposal for Phase 2"] draft text, for the detailed proposal. This needs to go to JISC as soon as I (MN) return on 10 July 06. See [[JISC_Proposal_for_Phase_2]] draft text, for the detailed proposal. This needs to go to JISC as soon as I (MN) return on 10 July 06.

See Phase2Notes for information about ongoing work from Mustie and Alun. (-- AlunEdwards <<DateTime(2006-11-16T17:05:43Z)>>)
Line 4: Line 6:
Line 5: Line 8:
 This page is (a bit better than) a dump of ideas for the Phase two work that Mustie and Alun may lead on.
Line 6: Line 10:
This page is (a bit better than) a dump of ideas for the Phase two work that Mustie and Alun may lead on. Currently (-- MarkNorman <<DateTime(2006-05-11T15:11:24Z)>>) I have two main ideas:
Line 8: Line 12:
Currently (-- MarkNorman [[DateTime(2006-05-11T15:11:24Z)]]) I have two main ideas:
Line 11: Line 14:
Initial steps:
Line 12: Line 16:
Initial steps:
Line 16: Line 19:
Line 26: Line 28:
Line 28: Line 29:

This is quite hard, but I thought I should try to get something to you 
 This is quite hard, but I thought I should try to get something to you
Line 31: Line 31:

 This is incredibly rough - but should give some hints. Please let me
 know if it is way down on the uncooked end of half-baked. i.e. if it
 triggers off possibilities in your mind - excellent: if it sounds mad or
 This is incredibly rough - but should give some hints. Please let me
 know if it is way down on the uncooked end of half-baked. i.e. if it
 triggers off possibilities in your mind - excellent: if it sounds mad or
Line 36: Line 35:
Line 39: Line 37:
 Alun and I could work with you on something from September onwards. 
 (Actually, I may not be able to do much before October). You said that 
 you would have to start in August at the latest. (That might be OK if 
 Alun and I could work with you on something from September onwards.
 (Actually, I may not be able to do much before October). You said that
 you would have to start in August at the latest. (That might be OK if
Line 43: Line 41:
Line 46: Line 43:
 Hopefully, you at least 0.5 FTE, Alun 0.5 FTE from Sept onwards - maybe   Hopefully, you at least 0.5 FTE, Alun 0.5 FTE from Sept onwards - maybe
Line 48: Line 45:
Line 51: Line 47:
 It would be good to find some proof that there are people out there 
 whose research would benefit from 'the power of the grid'. However, 
 these people are non-computer-technical and so would not even consider 
 using the grid as it is now. In fact, it may be so far out of their 
 reach that they may never have heard of grid computing (and probably 
 It would be good to find some proof that there are people out there
 whose research would benefit from 'the power of the grid'. However,
 these people are non-computer-technical and so would not even consider
 using the grid as it is now. In fact, it may be so far out of their
 reach that they may never have heard of grid computing (and probably
Line 57: Line 53:
Line 60: Line 55:
 Formulate a study (and hopefully carry out a pilot) to observe or 
 capture the work or desired work of a research 'community' or group. We 
 may then postulate that 'the grid could help you with this' (and 
 therefore outline a grid-based application or service) and see what they 
 Formulate a study (and hopefully carry out a pilot) to observe or
 capture the work or desired work of a research 'community' or group. We
 may then postulate that 'the grid could help you with this' (and
 therefore outline a grid-based application or service) and see what they
Line 65: Line 60:
 [What we *DON'T* want to do is to go straight to part 2 of the above   [What we *DON'T* want to do is to go straight to part 2 of the above
Line 67: Line 62:
Line 70: Line 64:
 (e.g. common searches, common types of data to submit for transformation 
 etc. Therefore, perfect for building a secure, predictable application 
 (e.g. common searches, common types of data to submit for transformation
 etc. Therefore, perfect for building a secure, predictable application
Line 73: Line 67:
 - given a simple interface with something that they want, the   - given a simple interface with something that they want, the
Line 75: Line 69:
 - there is no need for researchers in academic disciplines to be 
 knowledgeable about the technology underlying the delivery of these 
 - there is no need for researchers in academic disciplines to be
 knowledgeable about the technology underlying the delivery of these
Line 78: Line 72:
Line 85: Line 78:
 Participants should be chosen orthogonally to their knowledge of or 
 interest in grid computing. We don't want the study to be skewed by 
 Participants should be chosen orthogonally to their knowledge of or
 interest in grid computing. We don't want the study to be skewed by
Line 88: Line 81:
Line 91: Line 83:
 We'll probably (I'll know soon!) have at least £20K underspend on the 
 ESP-GRID project, so finances shouldn't be a problem. The main thing 
 We'll probably (I'll know soon!) have at least £20K underspend on the
 ESP-GRID project, so finances shouldn't be a problem. The main thing
Line 94: Line 86:

Line 97: Line 87:
Line 100: Line 89:
= Categorisation of users =
This should be fairly easy to do, but we might have a problem in that our set of users chosen for #1 (above) may be quite skewed. In the first of my two (hopeful) [[attachment:AllHandsPapers2006/AllHands06TypesUsers.pdf|All Hands Paper]]s (PDF), we suggest the following users:
Line 101: Line 92:
= Categorisation of users =
This should be fairly easy to do, but we might have a problem in that our set of users chosen for #1 (above) may be quite skewed. In the first of my two (hopeful) [attachment:AllHandsPapers2006/AllHands06TypesUsers.pdf All Hands Paper]s (PDF), we suggest the following users:
Line 111: Line 100:
Line 116: Line 104:
Line 119: Line 106:
|| '''Person''' || '''When available''' || '''Comment''' ||
|| Mark || May: 15-17, 19 (am), 22-25, 31st || Looks flexible, but I've got to do lots of scheduling soon! ||
|| Alun || May: 23 (am) June: 1 || I'm available on a couple of other days - but only via telephone or JiscMail chatroom or whatever, I won't be in Oxford ||
|| Mustie || || ||
|| Marina || || ||
Line 120: Line 112:
|| '''Person''' || '''When available''' || '''Comment''' ||
|| Mark || May: 15-17, 19 (am), 22-25, 31st || Looks flexible, but I've got to do lots of scheduling soon!||
|| Alun || May: 23 (am) June: 1 || I'm available on a couple of other days - but only via telephone or JiscMail chatroom or whatever, I won't be in Oxford ||
|| Mustie || || ||
|| Marina || || ||
Line 131: Line 118:
 * maybe me 0.2 FTE in October-November?   * maybe me 0.2 FTE in October-November?

See JISC_Proposal_for_Phase_2 draft text, for the detailed proposal. This needs to go to JISC as soon as I (MN) return on 10 July 06.

See Phase2Notes for information about ongoing work from Mustie and Alun. (-- AlunEdwards 2006-11-16 17:05:43)

The following (on this page) is our early rough notes for such work.


  • This page is (a bit better than) a dump of ideas for the Phase two work that Mustie and Alun may lead on.

Currently (-- MarkNorman 2006-05-11 15:11:24) I have two main ideas:

  1. Get grid requirements from non-grid-users (users who don't care about the technology)
  2. Provide evidence for the categorisation of users that we suggested in our earlier findings

Initial steps:

  • we need a short document (2-3 pages) with aims and vague methodologies
  • I need to send a proposal to JISC (they should say yes, as we've heavily underspent)
  • Plan the time scales (again)

Requirements

After speaking before, I sent the following in an email (to Mustie) to see if it triggered off thoughts. It kind of sums up where I'm at, but obviously needs tightening up.

 Subject: Idea for requirements/competency work
 Date: Wed, 05 Apr 2006 18:44:24 +0100
 From: Mark Norman <mark.norman@computing-services.oxford.ac.uk>
 To: Mustafizur Rahman <mustafizur.rahman@exeter.oxford.ac.uk>
 CC: 'Alun Edwards' <alun.edwards@computing-services.oxford.ac.uk>
 Mustie,
 This is quite hard, but I thought I should try to get something to you
 before going on holiday.
 This is incredibly rough - but should give some hints.  Please let me
 know if it is way down on the uncooked end of half-baked.  i.e. if it
 triggers off possibilities in your mind - excellent: if it sounds mad or
 v. badly formed - please say so!
 Time-scale
 ==========
 Alun and I could work with you on something from September onwards.
 (Actually, I may not be able to do much before October).  You said that
 you would have to start in August at the latest.  (That might be OK if
 you could work on the design etc. and start without us).
 Resources/FTE
 =============
 Hopefully, you at least 0.5 FTE, Alun 0.5 FTE from Sept onwards - maybe
 me 0.2 FTE in October-November?
 Justification
 =============
 It would be good to find some proof that there are people out there
 whose research would benefit from 'the power of the grid'.  However,
 these people are non-computer-technical and so would not even consider
 using the grid as it is now. In fact, it may be so far out of their
 reach that they may never have heard of grid computing (and probably
 assume that it is something supercomputer geeks do).
 Idea for work
 =============
 Formulate a study (and hopefully carry out a pilot) to observe or
 capture the work or desired work of a research 'community' or group.  We
 may then postulate that 'the grid could help you with this' (and
 therefore outline a grid-based application or service) and see what they
 think (without seeing any interface).
 [What we *DON'T* want to do is to go straight to part 2 of the above
 paragraph - that's what most people have done].
 It would also be good to establish:
 - that much of this researchers' work has common parameters
 (e.g. common searches, common types of data to submit for transformation
 etc.  Therefore, perfect for building a secure, predictable application
 for).
 - given a simple interface with something that they want, the
 researchers will come
 - there is no need for researchers in academic disciplines to be
 knowledgeable about the technology underlying the delivery of these
 applications/services
 Method?
 =======
 A questionnaire?!? Hmm. :-p
 Watching users.
 Interviewing users.
 [users = researchers, not actual users of grid technology]
 Participants should be chosen orthogonally to their knowledge of or
 interest in grid computing.  We don't want the study to be skewed by
 people with an interest.
 Costs/Resources
 ===============
 We'll probably (I'll know soon!) have at least £20K underspend on the
 ESP-GRID project, so finances shouldn't be a problem.  The main thing
 availability of people (you, me Alun).
 It all seems so very vague...
 See you on or after the 18th!

Categorisation of users

This should be fairly easy to do, but we might have a problem in that our set of users chosen for #1 (above) may be quite skewed. In the first of my two (hopeful) All Hands Papers (PDF), we suggest the following users:

  • SEU - Service End User (like a user of an app. in a portal), divided into
    • SEUD - pretty standard SEU, running queries on databases, text searches etc.
    • SEUX - special case of SEU (slightly higher risk). Actually runs executable code through an application interface (e.g. Matlab code).
  • PUA - Power User Agnostic of which grid resource node his/her job/code runs on.
  • PUS - Power User requiring Specific grid resource nodes (most common user at present).
  • PUDS - Power user Developing a Service. (As PUA/PUS but developing expertise like SP.)
  • SP - Service Provider.
  • Grid-Sys - Infrastructure sysadmin. (System administration of grid nodes, possibly with infrastructure delivery and security expertise.)

It's easy to predict that in a mature and popular (with researchers) grid, the SEUs will be dominant in terms of numbers, dwarfing the Power Users (who are really the main security threats).

We can't look into the future, but it would be good to do some kind of work (hopefully alongside the requirements stuff) that helped to justify these labels. Any ideas?

Dates for a brainstorm session

1-2 hours at OUCS? (Or we could come to Begbroke?)

Person

When available

Comment

Mark

May: 15-17, 19 (am), 22-25, 31st

Looks flexible, but I've got to do lots of scheduling soon!

Alun

May: 23 (am) June: 1

I'm available on a couple of other days - but only via telephone or JiscMail chatroom or whatever, I won't be in Oxford

Mustie

Marina

I shall really have to submit this proposal in early June, but we wouldn't have to work on it until later.

Resources/FTE/Time scales

  • Mustie 0.5 FTE Aug-Sept, then ???
  • Alun 0.5 FTE from Sept onwards
  • maybe me 0.2 FTE in October-November?

ESPGRIDwiki: PhaseTwoWork (last edited 2013-05-17 16:26:48 by localhost)