This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/artf5637?nav=1 at Sun, 06 Nov 2022 04:43:50 GMT SourceForge : artf5637: Some comments from Paul

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Tracker
Project: TSC     Trackers > Tasks for our Technical Strategy Document > View Artifact
Artifact artf5637 : Some comments from Paul
Tracker: Tasks for our Technical Strategy Document
Title: Some comments from Paul
Description:
Following the request for commenst from the BoD, Paul Strong provided these, whcih sparked a discussion thread:

Dave,
 
Firstly – this is a great start.
 
Specific comments on the slides –
 
Scope Of OGF
 
It may be useful to separate this slide into 2 slides, one with a broad scope and one with the examples or focus areas 
as is the current case.
 
Perhaps the broad scope should include something about –
Enabling Grid Computing via working together, sharing experiences and developing standards that enable…
o        Treating the [Inter?]network (or subsets thereof) as a shared, integrated platform
o        The development of applications and services that leverage this platform, ranging from the computationally 
intensive to the transactional  
o        Heterogeneous (homogeneous assumed) implementations of that platform and applications/services with 
interoperable components
o        The management of the applications/services and the platform (Grid) they run on
o        Within And Between Enterprises/Organizations, inc Data Center and Collaboration
 
I may be slightly off base but I see the core of Grid being the view of the network of computers, or a sub set of it, as
 a pervasive, shared, integrated platform.  All of the rest are perspectives on that platform.  How do I share within an
 enterprise/organization?  How do I share across organizations?  How do I make my applications scale to take advantage 
of this platform?  What are the system calls that my applications/services have to make to that platform?   How do I 
manage the platform and the hosted applications?  Etc. etc.   At least for me, this vague view helps provide a context 
for everything else.
 
Goals
 
Perhaps we could again break this down into what and how. For example…
 
What
Identify Requirements
Use cases, scenarios – for
The application of grid technologies
Managing grid implementations
Core technical requirements
Enable Implementation
Develop standards – Architectural etc.
Open Source implementations
Drive/Encourage Adoption
Highlight successful implementations
Provide points of reference – patterns, reference implementations
 
How
Through a community –
Regular meetings (telecom)
Regular summits (F2F)
eMail
…
 
Comments with respect to the document –
 
Clearly the slides comments apply equally well to the doc.
 
First a general comment - I notice that the reference model/OGSA reconciliation effort is not identified as a high 
priority. This may merely be because it is not a use case per se, but rather something that most of the use cases depend
 upon in order to address their requirements.  I do believe that addressing this is a key to making all of the rest 
successful and as such it needs to be specifically addressed in the strategy document.
 
Whilst I appreciate the JFK-esque thrust, I have a minor issue with statement on page 3 –
 
The Open Grid Forum should commit all its available resources to the goal that before this decade is out, commercial and
 academic organizations will build real operational grids using OGF defined components.
 
I would replace “…components” with “standards”.  Clearly our role is to enable the building of operational grids 
using interoperable, standards based components.  However I think that our role is to define sets of logical components 
and interfaces, but not necessarily the realized components – these will probably be implementation specific.
 
Cheers
Paul
Submitted By: David Snelling
Submitted On: 11/20/2006 10:35 AM EST
Last Modified: 11/20/2006 10:51 AM EST

Status / Comments Change Log Associations Attachments  
Status  
Group: *
Status:* Open
Category: *
Customer: *
Priority: * 1
Assigned To: * None
Reported in Release: *
Fixed in Release: *
Estimated Hours: * 0
Actual Hours: * 0
Comments
David Snelling: 11/20/2006 10:51 AM EST
  Comment:
nd then some more from Charlie, where he quotes himself from another thread:

(yes, I am glad we are having this discussion too!)

Paul, I agree- both of these customer sets - the direct and the indirect- are needed for OGF to be worth doing.  I think you have captured these two 
distinct groups just right.

I also resonate with your point that some organizations roll their own, and in fact 4 of the software components in my TeraGrid "provider" list (in my
 previous message "OGF's primary customers) were developed by, or adapted by, providers I funded.  I had not through of it that way, but I agree and 
it's great to be able to be a card carrying member of two stakeholder camps! :-)

In my earlier note I said the board would hear about some plans from the eScience ghetto between now and the board meeting.  Those plans are moving 
pretty fast so let me go ahead and outline them as they are part of this same discussion having gotten feedback from Geoffrey and others that this is 
a reasonable summary.

Here is how I have described this plan to the Globus and Condor guys this week (and, as luck would have it, I ran into Rich Wolski - UCSB/
NetworkWeatherService - at the airport and got his take as well):

<Interanal Quote from another thread>

After a very productive discussion about this within the eScience pocket of the GFSG on Monday this week some of us believe that we have begun to 
hatch a plan to try to get these software providers re-engaged with OGF (or engaged for the first time).  In a nutshell it is as follows:

---   Create a "software forum" at OGF meetings, starting in North Carolina, where any software
---   provider can schedule a room and a chunk of time to meet with the people who use their
---   software.  Some groups may want an hour; others may want half a day.  The meetings
---   would attempt to get dialog going between providers and their customers, and among
---   their customers.  These would take place over 1.5 to 2 days.  Organizers of OGF-19 will
---   need to tell us whether to do this on separate days or not so as not to interfere with the
---   standards working sessions.

To design such a forum, we plan to:

a) talk to the major players (Globus Alliance, Condor, Unicore, etc.) to see if they would work with us to create a structure at the OGF meeting in 
North Carolina that would enable them to meet with their customers and facilitate their customers meeting with one another.  Catlett agreed to talk to
 Globus and Condor; Gentsch agreed to talk to Unicore.  Anyone who wants to help is free to talk to other providers.

b) make that structure open to *ANY* software provider group who wishes to participate (indeed we want to recruit and advertise- there are lots of 
important software providers to this community).

Part (a) is important, because we need some "anchor" tenants to attract critical mass.

OGF, and particularly the standards activities, would benefit from the second-order effects of such a forum.  Some of the second-order effects of such
 a cluster of "software provider forums," happening in the same venue over ~2 days, would include:
	- cross-fertilization between the software providers (the bees being the common users and
	the spies sent to see what the other guy's users are saying)
	- sharing problems/solutions between users of these packages
	- requirements gathering for software providers (while standards work prioritizers listen in)


I also believe that we need to have a discussion between a set of key software provider leaders and TCS to have the following exchange:
	a) brief them on the draft roadmap
	b) ask them what they believe OGF should focus on in order to help them deliver better
	software to help organizations build and operate grids.

I heard three flavors of "questions" about this idea on Monday:

	Q1: why would the providers do this? what is in it for them? they have their own meetings
	already (globusworld, condor week, etc.).
	A1: because putting on a big meeting is a lot of work, and you only get the faithful to attend.
	Participating in an OGF cluster of "mini-forums" would let you do it more often, with less
	work on your part, and potentially get more exposure (to not just the faithful)

	Q2: why would people using this software want to come to such an OGF forum when they
	can just go to the software provider meetings (globusworld, condor week, etc.)
	A2: because none of us paying people to build and operate grids want to invest in sending
	them to five or six software-provider events every year, and having the providers (including
	the ones who are not, but want to be, your provider) in one place facilitates speed-dating.

	Q3: won't this make OGF appear to be pushing certain providers, potentially the wrong
	ones?
	Q3: yes, if we were talking about restricting providers.  But we're not.

</Interanal Quote from another thread>

In talking to Ian Foster (Globus), Miron Livny (Condor), and Rich Wolski (UCSB- Network Weather Service and batch queue prediction tools) I have 
already gotten their take on Q1.  They all basically view this as a refreshing approach and one they would like to participate in.

As for Q2 - Speaking with my software consumer hat on, I already average 20 TeraGrid people at OGF and I would send 15-20 more if we had this kind of 
forum (I can picture their faces; I am not talking in the abstract).  [note- I am not viewing this as a scheme to get more attendees - the point I am 
making is that OGF would be more valuable to me, a stakeholder]


CeC

  Action: Update
David Snelling: 11/20/2006 10:44 AM EST
  Comment:
Paul, responded to Charlie:

This is an important discussion.

Some thoughts below...

I think *both* sets of "customers" need to be engaged -

i)	Direct consumers of OGF standards - software developers and
roll-your-own shops like us (eBay).

ii)	Indirect consumers - users who build grids using software that
incorporates OGF standards or is OGF compliant in some sense.

In theory it should be much easier to engage the software developers as
the OGF work should be directly applicable to their product development.
If they do not see it this way then we should seek to understand why.

From an enterprise grid perspective we care about the following software
developers -
o	Enterprise software, framework, middleware and packaged
applications vendors, e.g. SAP, BEA, Oracle, Sybase and Tibco, for our
transactional and batch enterprise applications.
o	Traditional Grid software vendors, for our market simulations,
genome processing, pharma, car crash simulations and so forth.
o	Enterprise management vendors, i.e. IBM, BMC, CA and HP, as well
as a raft of smaller and niche players.  As I have mentioned before, the
really big challenge for enterprises is really around managing the vast
number of things you end up with in your datacenters once you have lots
of scale-out, grid applications/services, of whatever ilk.  I think that
getting the systems management vendors engaged is key to getting
enterprise end users engaged.

As per my comments yesterday, I believe we should explore a different
route for end users of Grids, especially enterprises.  Firstly we (OGF)
need their requirements as context for the software vendors and for our
own standards.  It's their problems that we are ultimately solving.  I
have discussed the following with a number of other end users, and all
were very positive -
o	Create one or more customer advisory councils such as those
traditionally used by vendors.
o 	Have a broad set of high level technologists from non-competing
companies so that they can be more open.
o	Hold one or more 1 or 2 day sessions focused solely on specific
requirements areas.
o	Publish requirements to be shared by community and vendors.

From an end user perspective this may have high value in that it stops
us having to answer the same set of questions from 20 vendors that we
get every year :o)  Of course vendors can individually ask more detailed
questions at other times, but we can get a shared notion of the broad
requirements without the end users among us losing patience.  It also
requires less engagement from the end users.  Once the dialog is started
we can revisit a year later and show progress (standards, products, case
studies) in the directions they indicated.  This method may not be cheap
and I expect that vendors would have to "nudge" their customers to
participate initially, but I know for sure that I'd rather have one
broad engagement for a short period of time to get my needs across to a
large number of vendors, than to have to continually engage in somewhat
arcane working/research groups or in a large number of separate
conversations.

Regards
Paul
  Action: Update
David Snelling: 11/20/2006 10:39 AM EST
  Comment:
Charlie added these comments to the thread:

I agree and had a similar thought on this.  I would have written this "using software that employs OGF standards" or something along those lines.

The subtle issue is I think deeper than just wording, in that we have to be clear that the primary "customers" of OGF really are not the "
organizations [who] build operational grids."  Those organizations use software solutions, thus only indirectly use standards other than when they 
develop their own software, which of course some organizations do.  OGF's goal is that the groups developing those software solutions will use OGF 
standards.

If we do not get this point clearly then we will gather requirements not from our real customers (the software developers) but from *their* customers,
 bypassing our real customers (and alienating them along the way).

I will write a separate email about this so as not to sidetrack the document feedback thread.

CeC

  Action: Update
David Snelling: 11/20/2006 10:35 AM EST
  Action: Create


 
 


The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/artf5637?nav=1 at Sun, 06 Nov 2022 04:43:57 GMT