Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @

EGI Core activities:2013-bidding Accounting Portal

From EGIWiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Main operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

EGI Core services menu: Services PHASE I Services PHASE II Services PHASE III Bids Payments Travel procedure Performance

Go back to the EGI Core Activities Bidding page.

Go back to the Core EGI activity list.

  • Service name: Accounting Portal
  • Service category: Operations
  • Service type: Coordination, operation and maintenance

The Accounting Portal is part of the EGI Core Infrastructure Platform which supports the daily operations of EGI.


The EGI Accounting Infrastructure is distributed. At a central level it includes the repositories for the persistent storage of usage records. The central databases are populated through individual usage records published by the Resource Centres, or through the publication of summarised usage records. The Accounting Infrastructure is essential in a service-oriented business model to record usage information. The Accounting Portal provides data accounting views for users, VO Managers, NGI operations and the general public.

Technical description

The Accounting Portal receives and stores the site, user, and VO level summaries generated by the Accounting Repository and allows visualisation and manipulation via a web portal. For example, by aggregating sites in a country, or varying the time period viewed.

The system is expected to evolve to provide storage, cloud and parallel job views. The portal has a frontend that renders HTML pages, and a Python backend to update the DBs. The frontend is coded on PHP 5 running under Apache, with a MySQL relational database on a SL6 distro. It uses plain PHP and pChart 2.0 for the graphs. The databases are separated into a CPU record database, a User record database, and a topology database.

This service includes the following components.


This activity is responsible for the coordination of the system operation and upgrade activities with those partners that are in charge of operating other systems that depend on it.


Support through the EGI helpdesk is provided

  • to users of the portal about the data displayed and the views provided.
  • to the operators of other depending systems.

Support hours: eight hours a day (for example 9-17 CE(S)T), Monday to Friday – excluding public holidays of the hosting organization.


  • Daily running of the system
  • Provisioning of a high availability configuration
  • A test infrastructure to verify interoperability and the impact of software upgrades on depending systems


This activity includes:

  • core refactoring, bug fixing, proactive maintenance, improvement of the system
  • coordination of software maintenance activities with other technology providers that provide software for the EGI Core Infrastructure or remote systems deployed by integrated and peer infrastructures that interoperate with the central EGI components of the system.
  • Maintenance of probes to test the functionality of the service
  • Requirements gathering
  • Documentation

Service level targets