Skip to main content

Storage meets the Grid

I'm just back from OGF19, which was very productive in a number of ways. One strand of interest is the continuing dialogue between the storage industry (represented by SNIA) and the grid world. This conversation has been developing slowly over the last year. I was on a panel at MSST 2006 that explored some aspects of this. SNIA were also present at GGF18 to explore where the two concerns meet. Both sides are still learning about each other, as they are both complex and changing technologies.

One obvious area of overlap is that of data replication. Many grid projects maintain replicas of data, to improve access times and/or to guard against loss. The classic example is the LHC Grid, but there are many other examples, particularly in the world of data librarines. Meanwhile, the storage industry supply replication systems for commerical data, specialising in backups and disaster recovery.

The two technologies work at different levels. Storage systems copy data from one disk block to another, with no knowledge about the data being copied. Grid systems copy files or database tables (in fact these two are themselves very different technologies), while maintaining application-specific metadata. Storage systems are usually deployed over LANs while grids are deployed over WANs, but this is not a hard and fast rule.

It remains to be seen which approach is best in which circumstances. Certainly there seem to be standards and tools from the storage industry that might be useful in the grid world, and vice versa. This will be an interesting conversation for some time.


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…