Difference between revisions of "E-GRANT"
Jump to navigation
Jump to search
(12 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{Template:Op menubar}} {{Template:Tools menubar}} {{TOC_right}}<br> | {{Template:Op menubar}} {{Template:Tools menubar}} {{TOC_right}}<br> | ||
{{Template:Deprecated}} | |||
{| class="wikitable" | {| class="wikitable" | ||
Line 6: | Line 8: | ||
| ''e-GRANT'' | | ''e-GRANT'' | ||
|- | |- | ||
| '''Tool description''' | | '''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''' | | '''Tool url''' | ||
| | | http://e-grant.egi.eu/<br> | ||
|- | |- | ||
| '''Email''' | | '''Email''' | ||
| | | Egrant-support@mailman.egi.eu | ||
|- | |- | ||
| '''GGUS Support unit''' | | '''GGUS Support unit''' | ||
| ''e-GRANT RA | | ''e-GRANT RA Tool'' | ||
|- | |||
| '''GOC DB entry''' | |||
| https://goc.egi.eu/portal/index.php?Page_Type=Site&id=1325 | |||
|- | |- | ||
| '''Requirements tracking - EGI tracker''' | | '''Requirements tracking - EGI tracker''' | ||
Line 22: | Line 31: | ||
|- | |- | ||
| '''Issue tracking - Developers tracker''' | | '''Issue tracking - Developers tracker''' | ||
| | | n/a | ||
|- | |- | ||
| '''Release schedule''' | | '''Release schedule''' | ||
| | | https://wiki.egi.eu/wiki/E-GRANT_Release_Schedule | ||
|- | |- | ||
| '''Release notes''' | | '''Release notes''' | ||
| | | https://wiki.egi.eu/wiki/E-GRANT_Release_Notes | ||
|- | |- | ||
| '''Roadmap''' | | '''Roadmap''' | ||
| | | https://wiki.egi.eu/wiki/TASK_JRA1.5_Resource_Allocation_%E2%80%93_e-GRANT | ||
|- | |- | ||
| '''Related OLA''' | | '''Related OLA''' | ||
| ' | | 'TBD | ||
|- | |- | ||
| '''Test instance url''' | | '''Test instance url''' | ||
| | | https://149.156.9.43/slaneg/auth/login | ||
|- | |||
| '''Documentation''' | |||
| [https://wiki.egi.eu/wiki/Resource_Allocation RA Process Main Page] | |||
|- | |||
| '''License''' | |||
| Apache2.0 | |||
|- | |||
| '''Provider''' | |||
| ACC Cyfronet AGH | |||
|- | |||
| '''Source code''' | |||
| [https://git.plgrid.pl/projects/EED/repos/egrantrepo/browse https://git.plgrid.pl/projects/EED/repos/egrantrepo/browse] | |||
|} | |} | ||
= | <br> | ||
= 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]] | |||
e-GRANT is | #All requirements are gathered in EGI RT instance.<br> | ||
#Prioritization and testing is done by dedicated [[Operations Tools Advisory Groups#e-GRANT_Advisory_and_Testing_Board|e-GRANT OTAG]] coordinated by EGI Operations team | |||
#EGI RT statuses of requests are as follow | |||
#*New | |||
#*Accepted - accepted by OTAG<br> | |||
#*Rejected - rejected by OTAG | |||
#*Open - (In progress) development team is work on the request<br> | |||
#*Resolved - released | |||
#Forge priority of requests are as follow | |||
#*None - 0 | |||
#*Low - 1<br> | |||
#*Normal - 2 | |||
#*High - 3<br> | |||
#*Immediate (i.e. emergency) - 4<br> | |||
#Standard changes (routine actions, no need for approval) | |||
#*changes related to database information update | |||
#*bug fixing - restoring service to expected functionality | |||
#Emergency changes (implemented without approval but subject of post-review) | |||
#*Security incidents | |||
#Releases | |||
#*Frequency: every 3 months | |||
= Documentation = | |||
[https://wiki.egi.eu/wiki/Resource_Allocation RA Process Main Page] | |||
<br> | |||
== Instances == | == Instances == | ||
=== Production === | |||
URL: [https://e-grant.egi.eu e-GRANT] | |||
=== Testing === | |||
URL: [https://149.156.9.43/slaneg/auth/login e-GRANT test] | |||
'''As Customer:''' | |||
login: vo1@email.com | login: vo1@email.com | ||
Line 69: | Line 115: | ||
login: vo2@email.com<br> | login: vo2@email.com<br> | ||
password: vo | password: vo | ||
<br> | <br> '''As Provider:'''<br> | ||
login: provider1@email.com<br> | login: provider1@email.com<br> | ||
Line 87: | Line 129: | ||
password: provider | password: provider | ||
[[Category:Tools]] | |||
[[Category: |
Latest revision as of 12:41, 5 June 2018
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 |
This article is Deprecated and should no longer be used, but is still available for reasons of reference. |
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/ |
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
- All requirements are gathered in EGI RT instance.
- Prioritization and testing is done by dedicated e-GRANT OTAG coordinated by EGI Operations team
- 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
- Forge priority of requests are as follow
- None - 0
- Low - 1
- Normal - 2
- High - 3
- Immediate (i.e. emergency) - 4
- Standard changes (routine actions, no need for approval)
- changes related to database information update
- bug fixing - restoring service to expected functionality
- Emergency changes (implemented without approval but subject of post-review)
- Security incidents
- Releases
- Frequency: every 3 months
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