CVRG Infrastructure Uses
From CVRG Wiki
Use of the CVRG Infrastructure maintained by the CVRG team
An advantage of deploying an instance of the CVRG at JHU for use as a project data repository is that this requires minimal local software engineering expertise. However, there will be maintenance and support costs that must be factored into this use of the CVRG Infrastructure. The CVRG team’s storage and computational resources require maintenance and upkeep. Personnel are required to maintain the hardware and support the use of the Infrastructure by the cardiovascular community. This requires a service-level agreement between the users of the CVRG Infrastructure and the CVRG team.
In addition, there is an end user data agreement between the users of the CVRG Infrastructure and the CVRG team. It is understood that all data within the CVRG Infrastructure maintained by the CVRG team is the property of the user(s) who submit the data. It is also understood that these data may be shared with other users/groups in the CVRG Infrastructure at the discretion of the data owners. The CVRG team will maintain user ids, groups and other security-related items within the CVRG Infrastructure. The CVRG team will access user-owned data to resolve issues when requested by the user.
Use of the CVRG Infrastructure when managed locally
Local use of the CVRG infrastructure requires that users provide their own computing and storage resources and local software engineering expertise. The CVRG team will be available to answer questions and assist in the resolution of problems with an externally deployed infrastructure. Data integration internal to the local infrastructure will be possible. This locally managed instance of the CVRG infrastructure can be integrated with other instances, at the decision of the local management team, with assistance from the CVRG team.