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 "VT VAPOR:VAPOR OpsPortal Engage"

From EGIWiki
Jump to navigation Jump to search
Line 19: Line 19:
Collaborations may be considered with the
Collaborations may be considered with the
[http://perun.metacentrum.cz/web/ Perun] user management system for the user life-cycle workflow management, and the [https://wiki.egi.eu/wiki/VT_Scientific_Publications_Repository_Implementation_Resources VT Scientific Publications Repository Implementation Resources] and OpenAIRE project to collect scientific publications based on resource usage acknowledgement.
[http://perun.metacentrum.cz/web/ Perun] user management system for the user life-cycle workflow management, and the [https://wiki.egi.eu/wiki/VT_Scientific_Publications_Repository_Implementation_Resources VT Scientific Publications Repository Implementation Resources] and OpenAIRE project to collect scientific publications based on resource usage acknowledgement.
== Infrastructure resources  ==
Extends the resource distribution browser:
* To cloud resources
* To give more details (OS , number of cores , capacity)
* To replace some Gstat feature
* Provide API
Extend the dashboard
* To monitor cloud infrastructures

Revision as of 19:12, 17 July 2014

User community management

The User Database implemented in the Operations Portal retrieves user information from the VOMS servers. It is proposed to extend this database to be a one-stop repository for (i) information about grid and cloud users including users behind a robot certificate, and (ii) the management of user registration life-cycle. This user community management solution is dedicated primarily to VO managers.

The User Database is intended to store user information besides the administrative data available in the VOMS. The following information is envisaged:

  • Administrative data (DN, email, affiliation, VO membership, group membership) in sync with the VOMS database.
  • Research discipline classification referring to the VT Scientific Discipline Classification.
  • Scientific publications: keep track of published works using the infrastructure and encourage users to acknowledge the usage of EGI resources.
  • Robot certificate DN (if any) in order to have a realistic idea of the number of actual users in a VO (may users have their own personal grid certificate or not).
  • Scientific applications used linking to the EGI Applications Database.
  • User File Catalog instance (if any) and base directory.

As much as possible, the life cycle workflow automates interactions with third party services such as the VOMS, file catalog, EGI Applications Database, mailing list system. At registration time, the user is automatically requested to provide details about their activity, affiliation and the applications they use (link to the EGI Applications Database). A VO administrator approves or reject pending requests. On approval, the user's root directory is created in the file catalog. After membership expiration, files of expired users are cleaned up after a grace period.

Collaborations may be considered with the Perun user management system for the user life-cycle workflow management, and the VT Scientific Publications Repository Implementation Resources and OpenAIRE project to collect scientific publications based on resource usage acknowledgement.

Infrastructure resources

Extends the resource distribution browser:

  • To cloud resources
  • To give more details (OS , number of cores , capacity)
  • To replace some Gstat feature
  • Provide API

Extend the dashboard

  • To monitor cloud infrastructures