Skip to main content

GGF18: Grid in the Enterprise?

This morning's sessions at GGF18 in Washington showed the interesting contrast between the academic and commercial ideas of what "Grid computing" means. The academic view came from Ian Foster's classic paper, The Anatomy of the Grid, which was referenced by Dan Atkins of the USA National Science Foundation in his keynote speech. This view stresses the importance of a Virtual Organisation - a group of people from different organisations working together on a project or task. The term "Virtual Organisation" comes from business economics, so is not unknown to the commercial world - classic examples are the supply chain of a manufacturing process or the various organisations working together on a civil engineering project - but in the Grid world, VOs are more commonly seen in science Grids.

The commercial view was presented during the session on Enterprise Grid Requirements. Paul Strong of Ebay put it clearly: the focus is on removing silos between sub-organisations and replacing dedicated servers with virtualised resources. The approach is the same as the science use case: virtualisation of resources, heterogeneity, dynamic mapping of application instances, hot deployment of services - all the technologies that form what I call Computing as commodity. The difference is that these might all be deployed within a single enterprise; virtual organisations are possible but not necessary.

I believe these differences arise from the contrasting natures of the communities. In the academic world it is now common to use Beowulf clusters as high-performance compute resources and these really don't bring much new to the IT world. They take "jobs" from a queue and run them on multiple processors in much the same way as "traditional" supercomputers. So Foster's definition stresses the difference from such systems, focusing on collaboration between different organisations. The commercial world often has multiple machines and servers running within a single organisation. Virtualising these is qualitatively different from running a Beowulf cluster and so the Grid metaphor is more appropriate.

Comments

Popular posts from this blog

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…

New staff for the EA team

I'm delighted to welcome Jason Murphy, who joins us as our CRM Architect, and Wilbert Kraan, our new Data Architect.  Both Jason and Wilbert have worked as consultants for several years and bring new skills and considerable experience to IS.  They both know more than I do about their respective fields, which is how I like to hire people.

So the Enterprise Architecture practice now comprises the three of us, instead of me working on my won, which means we have more capacty to guide the University's IT architecture.  We can offer a greater range of skills and can bring a wider range of experience to bear.  I'm really excited about the opportunities this presents.

As his job title implies, Jason will focus on contact relationship management, working to build a user community and to create a strategy for managing and improving the University's relationships with prospective students, research partners, community organisations, and other parties - to give them all a better …