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

Difference between revisions of "2019-bidding/accounting"

From EGIWiki
Jump to navigation Jump to search
Line 80: Line 80:
== Effort (EGI-related activities) ==
== Effort (EGI-related activities) ==


Bids planning a total effort between 2 and 3 Person Months/year would allow these services and activities to be addressed appropriately.  Effort may be provided as part of either the INFRAEOSC-07 and INFRAEOSC-03 projects.  
Bids planning a total effort between 3 and 4 Person Months/year would allow these services and activities to be addressed appropriately.  Effort may be provided as part of either the INFRAEOSC-07 and INFRAEOSC-03 projects.


== Effort (EOSC-related activities) ==
== Effort (EOSC-related activities) ==


Partners are encouraged to submit details of activities and proposed costing of effort for EOSC Hub related activities.  This may include activities related to development of new functionality required by EOSC communities (e.g. in the case of accounting, a separate accounting portal view for EOSC Hub) in addition to activities delivering services to these communities.
Partners are encouraged to submit details of activities and proposed costing of effort for EOSC Hub related activities.  This may include activities related to development of new functionality required by EOSC communities (e.g. in the case of accounting, a separate accounting portal view for EOSC Hub) in addition to activities delivering services to these communities.

Revision as of 09:04, 13 November 2019

Main EGI.eu 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 Core Activities Bidding page.

Service name: Accounting repositories and portal

Introduction

The Accounting Infrastructure provides storage and access to usage information across the EGI Federation. At a central level, it includes the repositories for the persistent storage of usage records and a visualization portal for users and resource providers. The central databases are populated through individual usage records published by the Resource Centres, or through the publication of summarised usage records.

Technical description

The Accounting repositories store compute (serial and parallel jobs), storage, and cloud resource accounting data collected from Resource Centres of the EGI Federation. Accounting information is gathered from distributed sensors into a central accounting repository where it is processed to generate summaries that are available through the EGI Accounting Portal. The Accounting Repository, based on the APEL software, has a MySQL database backend, and needs to ensure the exchange of accounting information with peer e-Infrastructures.

The Accounting Portal receives and stores the site, user, and VO level aggregated summaries generated by the Accounting Repository, and provides views via a web portal, for example, by grouping sites in a country on custom time intervals. The databases are organized into a CPU record database, a User record database, and a topology database.

Coordination

This activity is responsible for:

  • The coordination of the APEL database operations and upgrade activities with those partners that are in charge of operating systems that depend on the central APEL accounting databases and portal or on which the accounting infrastructures depends.
  • The Coordination with the EGI Operations to support accounting clients' upgrade campaigns and other operational activities aiming at improving the accuracy and completeness of the accounting information gathered.
  • Requirements gathering from service providers and end-users.

Operations

  • Daily running of the system including the repositories and the portal for computing and storage accounting
  • Provisioning of a high availability configuration
  • A testing infrastructure to verify interoperability and the impact of software upgrades on depending systems
  • Creating an Availability and Continuity Plan and implementing countermeasures to mitigate the risks defined in the related risk assessment
  • Deployment of new releases in production

Maintenance

This activity includes:

  • 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

Software Compliance

  • Unless explicitly agreed, software being used and developed to provide the service should:
    • Be licensed under an open source and permissive license (like MIT, BSD, Apache 2.0,...).
      • The license should provide unlimited access rights to the EGI community.
    • Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the EGI organisation in GitHub.) All releases should be appropriately tagged.
    • Adopt best practices:
      • Defining and enforcing code style guidelines.
      • Using Semantic Versioning.
      • Using a Configuration Management frameworks such as Ansible.
      • Taking security aspects into consideration through at every point in time.
      • Having automated testing in place.
      • Using code reviewing.
      • Treating documentation as code.
        • Documentation should be available for Developers, administrators and end users.

IT Service Management compliance

  • Key staff who deliver services should have foundation or basic level ITSM training and certification.
    • ITSM training and certification could include FitSM, ITIL, ISO 20000 etc.
  • Key staff and service owners should have advanced/professional training and certification covering the key processes for their services.
  • Providers should have mature and well maintained ITSM process that are key to support the services they provide.

Support

Support through the EGI helpdesk is provided

  • to the operators of those infrastructures that publish or need to publish usage records into the EGI central accounting databases (Resource Centres, Operations Centres/NGIs and other integrated and peer infrastructures)
  • to the operators of other depending systems
  • to users of the portal about the data displayed and the views provided.

Support hours: eight hours a day , Monday to Friday – excluding public holidays of the hosting organization.

Service level targets

Effort (EGI-related activities)

Bids planning a total effort between 3 and 4 Person Months/year would allow these services and activities to be addressed appropriately. Effort may be provided as part of either the INFRAEOSC-07 and INFRAEOSC-03 projects.

Effort (EOSC-related activities)

Partners are encouraged to submit details of activities and proposed costing of effort for EOSC Hub related activities. This may include activities related to development of new functionality required by EOSC communities (e.g. in the case of accounting, a separate accounting portal view for EOSC Hub) in addition to activities delivering services to these communities.