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 "EGI Core activities:2015-bidding Collaboration tools"

From EGIWiki
Jump to navigation Jump to search
Line 23: Line 23:
*Main DNS for egi.eu domain  
*Main DNS for egi.eu domain  
*Provisioning of few VM to allow EGI.eu team to test services and workflows (max. 6cores/6GB RAM total)
*Provisioning of few VM to allow EGI.eu team to test services and workflows (max. 6cores/6GB RAM total)
== Coordination==


== Operations ==
== Operations ==

Revision as of 14:38, 1 July 2015

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.eu Web site hosting and CMS maintenance
  • EGI main events dedicated webspace
  • EGI SSO
  • Including shibboleth access for third party services using SSO as ID provider
  • Wiki
  • Mailman
  • DocumentDB
  • Survey tool
  • Eduroam for Egi.eu
  • Indico
  • RT
  • RT must interface with the UMD software provisioning system. Tight cooperation with the provider of the UMD infrastructure is expected
  • Other collaboration platforms as needed
  • Main DNS for egi.eu domain
  • Provisioning of few VM to allow EGI.eu team to test services and workflows (max. 6cores/6GB RAM total)

Operations

  • Host and run the services
  • Create new SSO groups, mailing lists and Wiki namespaces
  • Provide usage statistics upon request
  • Create dedicated web spaces for the main EGI events
  • Deploy regularly relevant software patches and new releases in order to keep the services up to date
  • Adapt RT Scrips, dashboards upon request

Maintenance

  • Extend SSO to be ID provider for new services, upon request
  • Creation of new queues in RT and new metadata
  • More in general adding new use cases for the functionalities of the deployed tools, e.g. creating a new SSO group with mailing list.
  • Update of all tools at least once every 6 months to newest available version

Support

Support is provided through the it-support mailing list and the dedicated ggus support unit.

Service level targets

EGI collaboration services must have 90% availability over the month

If provided the DNS service must have Availability > 99% on a monthly basis.

Effort

The estimated effort to efficiently provide this service is between: 10-12 PM/year�