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

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

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…