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

Project Leadership

When I look back over recent projects that I've been involved in, it seems that one key to making a project successful is having someone on the team who really drives it forward: someone who is invested in the project as a whole and not just their own part in it. We (by which I mean the University's Applications division) have a well-defined project process, with defined roles, required milestones, deployment standards, and so forth.    All these are useful, but if the team doesn't have a leader, it seems a project can lose its way, perhaps not responding to changing circumstances, getting stuck on a technical problem, or not securing a needed resource in time to meet some external constraint. The leader can be any member of the team - it could be a developer, a project manager, or the sponsor, or someone in another role.  A team can include several people who are this committed to the project; it doesn't have to be a single person.   As an example, one of...

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

"That's not Grid!" - A cautionary tale

I don't usually attempt humour here, but see if you like this... Once upon a time, in the far-off world of Computerland, a great guru arose and declared a vision. "I see a future when all computers will be linked together and people will run their programs without knowing which computers are running them. People do not need to know where their jobs run; they just need the results. I call this Grid Computing!" The people of Computerland were excited by the guru's vision. They went away and worked to make it happen. When they were ready, they returned to the guru and said: "Oh great guru! We have implemented your vision. We can run our programs on whichever processor is free at the time, making sure that all programs can run and making best use of all our processors. No longer does one computer sit idle while another one is overloaded. Your vision is a great success!" "No, no, no!", said the guru, "That's not Grid!" The guru exp...