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

Webinar: Powering your business with Cloud Computing

On October 14th, I will be hosting a Grid Computing Now! web seminar on the topic of Cloud Computing. We have lined up two very interesting speakers who are using Cloud now to make businesses work. Ross Cooney had a good technological solution to sell but couldn't make it economic until Cloud Computing allowed him to pay for his computation only when he needed it. He will discuss the instant benefits and long term impact of cloud computing to the development, competitiveness and scalability of your application. Alan Williamson created the BlueDragon Java CFML runtime engine that powers MySpace.com. He advises several businesses and will give an overview of the different types of services available and how to avoid being locked-in to a single supplier. You can register for this event here .

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-de...

"Just enough" Enterprise Architecture

I spent an informative and enjoyable day with a proto-community of people pursuing Enterprise Architecture in UK Higher Education.  Many of the participants had been previously involved in JISC projects and have enjoyed similar events in the past, so I began the day as a bit of an outsider.  In the University of Edinburgh, our progress in adopting "architectures" is mainly on the IT side, via our Applications Architecture and our use of Service-Oriented Architecture .  Enterprise Architecture would integrate all this IT activity with the business processes and goals of the University (or what I sometimes call the administrative processes, for those readers who are unhappy with calling a university a "business"). I've tended to be a little sceptical of fully-fledged enterprise architecture (EA) because it sounds like a mammoth undertaking and the organisations doing it have often been very large corporations.  The two main outcomes of the JISC experiences ar...