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 "E-GRANT"

From EGIWiki
Jump to navigation Jump to search
 
(19 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}}


== e-GRANT ==


e-GRANT is a tool supporting Resource Allocation process. It allows researchers to request:<br>
{| class="wikitable"
|-
| '''Tool name'''
| ''e-GRANT''
|-
| '''Tool Category and description'''
|
'''EGI-Engage:TASK JRA1.5 Resource Allocation'''


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


for a given amount of time. e-GRANT handles all activities involved in RA Process which leads to SLA signing.  
|-
| '''Tool url'''
| http://e-grant.egi.eu/<br>
|-
| '''Email'''
| Egrant-support@mailman.egi.eu
|-
| '''GGUS Support unit'''
| ''e-GRANT RA Tool''
|-
| '''GOC&nbsp;DB&nbsp;entry'''
| https://goc.egi.eu/portal/index.php?Page_Type=Site&amp;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'''
| [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]
|}


== <span id="Instances" class="mw-headline">Instances </span> ==
<br>  


[https://e-grant.egi.eu <span class="mw-headline">e-GRANT</span>]
= Change, Release and Deployment  =


production
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 test (TD)<br>devel instance
#All requirements are gathered in EGI&nbsp;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&nbsp;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


== Release Notes ==
= Documentation  =


== Documentation ==
[https://wiki.egi.eu/wiki/Resource_Allocation RA Process Main Page]


[https://wiki.egi.eu/wiki/Resource_Allocation RA Process Main Page]
<br>


[https://wiki.egi.eu/wiki/Resource_Allocation_Provider_Activities e-GRANT for Provider]
== Instances  ==


e-GRANT for Broker
=== Production  ===


e-GRANT for Customer
URL: [https://e-grant.egi.eu e-GRANT]


[https://wiki.egi.eu/wiki/Resource_Allocation_Procedure_and_Work_Instruction Work instructions (Customer, Broker, Provider) and RA&nbsp;Procedure]
=== Testing  ===


[https://wiki.egi.eu/wiki/Resource_Allocation_Terminology RA terminology]
URL: [https://149.156.9.43/slaneg/auth/login e-GRANT test]  


== Other ==
'''As Customer:'''


[[Category:E-GRANT]]
login: vo1@email.com
 
password: vo
 
or
 
login: vo2@email.com<br>
 
password: vo
 
<br> '''As Provider:'''<br>
 
login: provider1@email.com<br>
 
password: provider
 
or<br>
 
login: provider2@email.com<br>
 
password: provider
 
[[Category:Tools]]

Latest revision as of 11: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



Alert.png 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/
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