The pilot has been completed!
About
TERENA Trusted Cloud Drive is a pilot experiment developing a personal data storage service that builds on a flexible Cloud Broker Platform. The unique features of the platform are:
- Federated access to the service
- Metadata and storage data are kept separate
- Storage data is encrypted and stored in the cloud
- Metadata stored in a trusted place.
- Various cloud storage back-ends can be brokered
- Flexible WebDAV front-end and web app.
- Different user platforms (Windows, MacOS, iOS, Android) are supported
- Code and documentation is fully open-source
Phase IApril 2012 - May 2012Completed | Phase IIJune 2012 - April 2013Completed | Pilot RecommendationsMay, 2013Completed |
---|
News
15 October 2012 - TERENA Trusted Cloud Drive pilot invites phase II participation
...
Although the software already offers capabilities to test different front-end applications too, this aspect will not be fully explored during the pilot. However, requirements will be collected during the pilot lifetime and recommendations on how to further improve the front-end (end-users) functionalities will be provided.
Take a look at the pilot's success measures.
Main technical characteristics of the pilot
...
- Phase i - Local installation of the platform at the TERENA office. During this phase the cloud broker (the elements in the green box above) will be installed and connected to a limited storage back-end offered by TERENA. A simple web portal and the necessary support for the federated access will also be developed. For this phase TERENA will sub-contract the software developer, Maarten Koopmans who will provide the necessary support for the installation. The platform will be evaluated and tested by a limited number of NRENs’ experts coordinated by TERENA.
- Phase ii - Upon successful test of Phase i, NRENs will be invited to participate in the pilot (NRENs that have already expressed their interest in participating are HEAnet, NIIF, BELNET, PSNC, and CARNet/Srce) either adding their own cloud storage back-end and/or developing new front-end applications to the cloud broker. An additional public storage back-end will also be added. During this phase it is envisage that NRENs will offer a limited number of end-users to provide feedback on the usability of the system. Although most of the user requirements will not implemented during the pilot phase, they will help shape and understand the type of service users would be looking for.
...
Latest version of the full project description.
Go and visit Phase i and Phase ii
Anchor | ||||
---|---|---|---|---|
|
Explore possible deployment scenarios for a trusted personal storage service for academia.
Objectives | Measures | Opportunity | Thread |
---|---|---|---|
Longer term sustainability for a potential service The community |
| Knowledgeable and reliable software development community around the open-source code. Significant number of user communities, targeted specific use cases. | Platform developer as single point of failure. Lack of development and support efforts. No significant take up of the service platform. |
Legal aspects and perceived trust issues related to the storage and management of the encryption keys and metadata The service model |
| Cloud platform is widely used to clearly separate the Personal Data Controller role from the Storage Data Manager role. Organizations can pick the service model and delivery scenario that better fits to their environment and use cases. | (Legal) benefits of the platform is not understood. Perceived as yet an other personal cloud storage service. Service One single service model does not fit to all organisations. |
Software scalability and performance The code |
| Platform core code is robust, secure, and scalable. | Platform code is weak, insecure, and rigid. |