E-GRANT

From EGIWiki
Jump to: navigation, search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Tools menu: Main page Instructions for developers Accounting Repository AppDB GGUS Message brokers ARGO Operations Portal GOCDB
AAI Proxy Metric Portal Licenses OTAGs Accounting Portal e-GRANT Perun Gstat LToS


Contents


Tool name e-GRANT
Tool Category and description

EGI-Engage:TASK JRA1.5 Resource Allocation

e-GRANT supporting Resource Allocation Process by allowing researchers to request an amount of compute and storage resources, for a given amount of time.

Tool url http://e-grant.egi.eu/
Email Egrant-support@mailman.egi.eu
GGUS Support unit e-GRANT RA Tool
GOC DB entry https://goc.egi.eu/portal/index.php?Page_Type=Site&id=1325
Requirements tracking - EGI tracker https://rt.egi.eu/rt/Dashboards/5540/e-Grant-Requirements
Issue tracking - Developers tracker n/a
Release schedule https://wiki.egi.eu/wiki/E-GRANT_Release_Schedule
Release notes https://wiki.egi.eu/wiki/E-GRANT_Release_Notes
Roadmap https://wiki.egi.eu/wiki/TASK_JRA1.5_Resource_Allocation_%E2%80%93_e-GRANT
Related OLA 'TBD
Test instance url https://149.156.9.43/slaneg/auth/login
Documentation RA Process Main Page
License Apache2.0
Provider ACC Cyfronet AGH
Source code https://git.plgrid.pl/projects/EED/repos/egrantrepo/browse


Change, Release and Deployment

This sections are providing detailed agreement in terms of requirements gathering, release and deployment of Operations Portal which extend Instructions for Operations Tools teams

  1. All requirements are gathered in EGI RT instance.
  2. Prioritization and testing is done by dedicated e-GRANT OTAG coordinated by EGI Operations team
  3. EGI RT statuses of requests are as follow
    • New
    • Accepted - accepted by OTAG
    • Rejected - rejected by OTAG
    • Open - (In progress) development team is work on the request
    • Resolved - released
  4. Forge priority of requests are as follow
    • None - 0
    • Low - 1
    • Normal - 2
    • High - 3
    • Immediate (i.e. emergency) - 4
  5. Standard changes (routine actions, no need for approval)
    • changes related to database information update
    • bug fixing - restoring service to expected functionality
  6. Emergency changes (implemented without approval but subject of post-review)
    • Security incidents
  7. Releases
    • Frequency: every 3 months

Documentation

RA Process Main Page


Instances

Production

URL: e-GRANT

Testing

URL: e-GRANT test

As Customer:

login: vo1@email.com

password: vo

or

login: vo2@email.com

password: vo


As Provider:

login: provider1@email.com

password: provider

or

login: provider2@email.com

password: provider

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export