Difference between revisions of "2016-bidding/collaboration tools"
Jump to navigation
Jump to search
(→Effort) |
|||
(4 intermediate revisions by 2 users not shown) | |||
Line 11: | Line 11: | ||
*EGI Web site hosting and other web servers related to EGI activities | *EGI Web site hosting and other web servers related to EGI activities | ||
*EGI SSO, including shibboleth access for third party services using SSO as ID provider | *EGI SSO, including shibboleth access for third party services using SSO as ID provider | ||
*Wiki | *Wiki (MediaWiki, Confluence) | ||
*Mailing list management | *Mailing list management | ||
*Document Repository | *Document Repository | ||
*Eduroam for EGI.eu | *Eduroam for EGI.eu | ||
*IdP federated in SURFConext and eduGAIN | |||
*Agenda management via Indico | *Agenda management via Indico | ||
*Actions and requirements tracking (RT). RT must interface with the UMD software provisioning system. Tight cooperation with the provider of the UMD infrastructure is expected | *Actions and requirements tracking (RT). RT must interface with the UMD software provisioning system. Tight cooperation with the provider of the UMD infrastructure is expected | ||
Line 36: | Line 36: | ||
*Extension of the SSO to be ID provider for new services, upon request | *Extension of the SSO to be ID provider for new services, upon request | ||
*Creation of new queues in RT and new metadata | *Creation of new queues in RT and new metadata | ||
*Support of new use cases for the capabilities of the collaboration tools, e.g. by creating a new SSO group with mailing list. | *Support of new use cases for the capabilities of the collaboration tools, e.g. by creating a new SSO group with mailing list. | ||
= Support = | = Support = | ||
Line 44: | Line 44: | ||
= Service level targets = | = Service level targets = | ||
EGI collaboration services must have | EGI collaboration services must have 95% availability over the month | ||
If provided the DNS service must have Availability > 99% on a monthly basis. | If provided the DNS service must have Availability > 99% on a monthly basis. | ||
Line 50: | Line 50: | ||
= Effort = | = Effort = | ||
Bids planning a total effort of 12 Person Months/year would allow these services and activities to be addressed appropriately. | Bids planning a total effort of about 12 Person Months/year would allow these services and activities to be addressed appropriately. |
Latest revision as of 18:39, 26 October 2016
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
EGI Core services menu: | Services PHASE I • | Services PHASE II • | Services PHASE III • | Bids • | Payments • | Travel procedure • | Performance |
Go back to the EGI Core Activities Bidding page.
- Service name: collaboration tools (IT Support)
Technical description
The task provides the following services for the EGI collaboration, all the services requiring authentication must interface with SSO:
- EGI Web site hosting and other web servers related to EGI activities
- EGI SSO, including shibboleth access for third party services using SSO as ID provider
- Wiki (MediaWiki, Confluence)
- Mailing list management
- Document Repository
- Eduroam for EGI.eu
- IdP federated in SURFConext and eduGAIN
- Agenda management via Indico
- Actions and requirements tracking (RT). RT must interface with the UMD software provisioning system. Tight cooperation with the provider of the UMD infrastructure is expected
- Main DNS for egi.eu domain
- Provisioning of a few VM to allow EGI.eu team to test services and workflows (max. 6cores/6GB RAM total)
- Other collaboration platforms on a need be basis
Operations
- Hosting and daily operations the services
- Creation of new SSO groups, mailing lists, and Wiki namespaces
- Provisioning of usage statistics upon request
- Creation of dedicated web spaces for the main EGI events
- Regular deployment of relevant software patches and new releases in order to keep the services up to date to the newest available version
- Adapt RT Scrips and dashboards upon request
Maintenance
- Extension of the SSO to be ID provider for new services, upon request
- Creation of new queues in RT and new metadata
- Support of new use cases for the capabilities of the collaboration tools, e.g. by creating a new SSO group with mailing list.
Support
Support is provided through the it-support mailing list and the dedicated ggus support unit.
Service level targets
EGI collaboration services must have 95% availability over the month
If provided the DNS service must have Availability > 99% on a monthly basis.
Effort
Bids planning a total effort of about 12 Person Months/year would allow these services and activities to be addressed appropriately.