Skip to main content

OGSA + EGA = ?

What does the merger of the Global Grid Forum and the Enterprise Grid Alliance mean for the people actually developing Grid standards? This has been addressed in a couple of sessions here at GGF18. The first indications is that their efforts mesh quite well - or at least they avoid much conflict.

The EGA have produced a reference model, a security model and use cases, concentrating on the management of data centres. Their focus on the provisioning of data servers should nicely complement the existing OGSA work, which addresses provisioning of compute servers rather than data and considers only higher-level data services. Similarly the EGA reference model describes the components of a data centre at a higher level than current CIM work, which is where OGSA is currently concentrating its efforts. And of course the Enterprise requirements have a major focus on SLAs, QoS, policy management, billing and chargeback - long recognised by OGSA but not something they've got around to addressing. Even the glossaries produced by the two bodies hardly clash - so we can't use the excuse that we don't understand each other!

One area where the two approaches currently differ is in the area of management. In OGSA, each service is typically self-managed, whereas the EGA typically has one service managing multiple others. This will require some work to reconcile. In the meantime, the two groups have agreed to compare their provisioning models to see whether they can produce a common solution.

So the initial prognosis is hopeful. As always, the devil will be in the detail. It will be interesting to see what comes out of the detailed discussions.

Comments

Popular posts from this blog

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…

A brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation.  Compared to the Core Diagrams that I described in an earlier post, the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers).  It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs.  I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web.

We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh.  Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR:
This is only intended to be suggestive: the real canvas would need to result from in-depth discussions about th…