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:
April 2012 - May 2012
June 2012 - April 2013
15 October 2012 - TERENA Trusted Cloud Drive pilot invites phase II participation
23 April 2012 - New pilot project to extend TERENA's cloud activities
|Cloud Broker Platform||The Cloud Broker Platform is a flexible open-source software tool developed by UNINETT Sigma in 2010 as part of the NEON project.The platform is the basis of the TERENA Trusted Cloud Drive pilot service.|
|Trusted Cloud Drive||Trusted Cloud Drive is a pilot service made available by TERENA for evolutionary prototyping, testing and service development purposes.|
|Pilot||A pilot experiment, also called a pilot study, is a small scale preliminary study conducted in order to evaluate feasibility, time, cost, adverse events, and effect size (statistical variability) in an attempt to predict an appropriate sample size and improve upon the study design prior to performance of a full-scale research project . Pilot studies, therefore, may not be appropriate for case studies.|
A prototype is an early sample or model built to test a concept or process or to act as a thing to be replicated or learned from. A prototype is designed to test and trial a new design to enhance precision by system analysts and users. Prototyping serves to provide specifications for a real, working system rather than a theoretical one.
Prototype software is often referred to as alpha grade, meaning it is the first version to run. Often only a few functions are implemented, the primary focus of the alpha is to have a functional base code on to which features may be added. Once alpha grade software has most of the required features integrated into it, it becomes beta software for testing of the entire software and to adjust the program to respond correctly during situations unforeseen during development.
Evolutionary Prototyping (also known as breadboard prototyping) is quite different from Throwaway Prototyping. The main goal when using Evolutionary Prototyping is to build a very robust prototype in a structured manner and constantly refine it. "The reason for this is that the Evolutionary prototype, when built, forms the heart of the new system, and the improvements and further requirements will be built. When developing a system using Evolutionary Prototyping, the system is continually refined and rebuilt. "…evolutionary prototyping acknowledges that we do not understand all the requirements and builds only those that are well understood."
Grey-box testing involves having knowledge of internal data structures and algorithms for purposes of designing tests, while executing those tests at the user, or black-box level.The testing procedure will include:
|Service Delivery Framework||A service delivery framework is a set of principles, standards, policies and constraints used to guide the design, development, deployment, operation and retirement of services delivered by a service provider with a view to offering a consistent service experience to a specific user community in a specific business context. An SDF is the context in which a service provider's capabilities are arranged into services.|
The aim of this pilot is to explore possible deployment scenarios for a trusted personal storage service for academia. The pilot will be built upon a federated software platform (i.e. the Cloud Broker Platform) that offers the ability to easily connect different storage back-end (both private and public cloud storage back-end are supported) and store users data in a secure and privacy preserving way (thanks to the separation of storage data and metadata as well as the built-in encryption functionality) in the cloud.
The following aspects will also be explored as part of the pilot:
(i) Longer term sustainability for a potential service (i.e. the community);
(ii) Legal aspects and perceived trust issues related to the storage and management of the encryption keys and metadata (i.e. the service model);
(iii) Software scalability and performance (i.e. the code);
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.
The pilot will be prototyping and operating the Cloud Broker Platform, the open software developed by UNINETT Sigma in 2010 as part of the NEON project, at TERENA and some selected NRENs, Universities, and other institutes.This prototype software has been built with the basic idea of separating the storage data (i.e. encrypted content) from the metadata (i.e. encryption keys, filenames, size, date, etc). By keeping the metadata store “on premises” data confidentiality is guaranteed under the assumption that the premises are inside a “trusted domain” – e.g. TERENA.
The technical part of the pilot will consist of installing all the components depicted in the picture above: namely a centralized cloud broker for the TERENA’s community (the green box depicted in the picture above), the web portal to access the system (front-end) and the storage back-end. The pilot will be carried out in two phases:
The pilot Phase ii will be operated for a 9-month period after which an evaluation will follow to assess the success of the pilot and to agree on the following steps.
There will be three deliverables produced as part of the pilot:
Latest version of the full project description.
Go and visit Phase i and Phase ii
Explore possible deployment scenarios for a trusted personal storage service for academia.
Longer term sustainability for a potential service
Knowledgeable and reliable software development community around the open-source code.
Significant number of user communities, 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.
One single service model does not fit to all organisations.
Software scalability and performance
|Platform code is robust, secure, and scalable.||Platform code is weak, insecure, and rigid.|