2019-bidding/collaboration-tools
Jump to navigation
Jump to search
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 Core Activities Bidding page.
(to add requirements on software licenses and FitSM Training & certification)
Service name: collaboration tools (IT Support)
Technical description
The task provides the following services for the EGI collaboration, all the services' authentication must integrate with EGI Check-in:
- 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).
- Jira ticketing system.
- Mailing list management.
- Document Repository.
- eduROAM for EGI Foundation employees.
- IdP federated in SURFConext and eduGAIN.
- Agenda management via Indico.
- Community forum using discourse deployed in a VM (operated by Operations team?)
- 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). This service is provided ad-hoc, and therefore it is not subject to monitoring and availability and reliability reporting. Only responses to support requests will be monitored.
- 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
- The services must run on separate machines (or VMs) in order to minimise the risk of incidents affecting multiple services at the same time
- Creating an Availability and Continuity Plan and implementing countermeasures to mitigate the risks defined in the related risk assessment
Maintenance
- Extension of the SSO to be ID provider for new services, upon request (Being deprecated with migration to check-in and usage of federated authentication via EGI Check-in)
- 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 99% availability over the month
If provided the DNS service must have Availability > 99.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.