Difference between revisions of "EGI gateway primer ToC"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
= Current ToC = | = Current ToC = | ||
#Introduction | #Introduction | ||
#*Some background and summary of current status | |||
*Some background and summary of current status | #*Mandate | ||
*Mandate | #*Target audience | ||
*Target audience | #Definitions | ||
#*Terms that are necessary to understand what we call a "Science Gateway” | |||
#Definitions | #*Distinction between an "enabling technology", a "SG framework", and "SG instance" | ||
*Terms that are necessary to understand what we call a "Science Gateway” | #For SG (framework) developers and maintainers | ||
*Distinction between an "enabling technology", a "SG framework", and "SG instance" | #*What it is their role | ||
#For SG (framework) developers and maintainers | #*What it is expected from them | ||
*What it is their role | #*Who are these players in Europe and what are their production and in which maturity level (it could be just a list of pointers to the EGI App Database that is the result of the other Task in our VT) | ||
*What it is expected from them | #For SG (instance) developers and operators | ||
*Who are these players in Europe and what are their production and in which maturity level (it could be just a list of pointers to the EGI App Database that is the result of the other Task in our VT) | #*What it is their role | ||
#For SG (instance) developers and operators | #*What it is expected from them | ||
*What it is their role | #*Who are these players in Europe and what are their production and in which maturity level (it could be just a list of pointers to the EGI App Database that is the result of the other Task in our VT) | ||
*What it is expected from them | |||
*Who are these players in Europe and what are their production and in which maturity level (it could be just a list of pointers to the EGI App Database that is the result of the other Task in our VT) | |||
Other topics agreed to be included: | Other topics agreed to be included: | ||
Line 25: | Line 23: | ||
*EGI.eu policies | *EGI.eu policies | ||
= Past ToCs = | |||
These are just some ideas for the primer structure (to be refined later by the VT project): | |||
*Building the gateway | *Building the gateway |
Revision as of 16:41, 4 July 2012
Current ToC
- Introduction
- Some background and summary of current status
- Mandate
- Target audience
- Definitions
- Terms that are necessary to understand what we call a "Science Gateway”
- Distinction between an "enabling technology", a "SG framework", and "SG instance"
- For SG (framework) developers and maintainers
- What it is their role
- What it is expected from them
- Who are these players in Europe and what are their production and in which maturity level (it could be just a list of pointers to the EGI App Database that is the result of the other Task in our VT)
- For SG (instance) developers and operators
- What it is their role
- What it is expected from them
- Who are these players in Europe and what are their production and in which maturity level (it could be just a list of pointers to the EGI App Database that is the result of the other Task in our VT)
Other topics agreed to be included:
- Monitoring of portals/gateways
- Comparison of Science Gateway enabling technologies
- EGI.eu policies
Past ToCs
These are just some ideas for the primer structure (to be refined later by the VT project):
- Building the gateway
- Planning and design of gateways
- Gateways characteristics
- Enabling technologies
- Connecting to EGI resources
- VO Portal Policy
- Job Submission mechanisms (robots, ...)
- Data storage and file management
- Operations and maintenance practices
- Integration of web-based gateways in EGI SAM central instance
- Security and accounting
- Sustainability
A list of established EGI policies is available in the EGI.eu Policies and procedures webpage. All relevant policies to the primer should be incorporated.