Difference between revisions of "E-GRANT"
Jump to navigation
Jump to search
Line 58: | Line 58: | ||
= Change, Release and Deployment = | = 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|Instructions for Operations Tools teams]] | |||
= Documentation= | = Documentation= |
Revision as of 14:01, 27 February 2015
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Tools menu: | • Main page | • Instructions for developers | • AAI Proxy | • Accounting Portal | • Accounting Repository | • AppDB | • ARGO | • GGUS | • GOCDB |
• Message brokers | • Licenses | • OTAGs | • Operations Portal | • Perun | • EGI Collaboration tools | • LToS | • EGI Workload Manager |
Tool name | e-GRANT |
Tool Category and description | TBD
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/ |
Egrant-support@mailman.egi.eu | |
GGUS Support unit | e-GRANT RA Tool |
GOC DB entry | TBD |
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 | TBD |
Related OLA | 'TBD |
Test instance url | https://149.156.9.43/slaneg/auth/login |
Documentation | TBD |
License | Apache2.0 |
Provider | ACC Cyfronet AGH |
Source code | TBD |
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
Documentation
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