Several stakeholders should become users of Clouds in Community Networks.
The following scenarios are to going to be developed:
The value of the Community Cloud comes from its usage.
All contributions that lead to usage by stakeholders are significant.
Typical cloud architecture. Three layers: Infrastructure, Platform, Services
Old stuff ====== research_approach ====== Original file
====== RESEARCH APPROACH ====== ====== Overview ====== Clommunity consortium is composed by academic/research institutions and community networks. Despite this cross-fertilization is expected to very productive, coping with such different skills, organization systems, etc. is an additional challenge for the project. This document is a working tool (so it is expected to change over the time) that is aimed at facilitate this cooperation. Following sections are project phases ===== Consortium partners ===== * Academic/research institutions (AIs) * Universitat Politècnica de Cataluna (UPC) [project leader] * Swedish Institute of Computer Science (SICS) * Royal Institute of Technology (KTH) * International Centre for Theoretical Physics (ICTP) * Community networks (CNs) * Fundació Privada per a la Xarxa Oberta, Lliure i Neutral guifi.net (guifi.net) ====== Knowledge transfer (KT) ====== Partners: UPC, SICS, KTH, guifi Duration: ???
===== Rationale ===== AIs have good knowledge of standard cloud SoA ⇒ AIs teach main cloud aspects to CNs CNs have a good knowledge of CNs SoA ⇒ CNs teach CNs main aspects to AIs ===== Tasks ===== * AIs → CNs : Cloud * CNs -AIs : CNs ===== Further information ===== ==== CNs inputs (/requirements) ====
=== guifi.net === * the best strategy to introduce a new product into (software or hardware or both) the community is offering and easier solution than the existing one (other aspects such being technically better, etc. are irrelevant) * e.g. offer a platform including the current guifi.net distro's services easier (as a whole) to install and/or with better upgrades, etc. ====== Problem definition ====== Partners: UPC, SICS, KTH, guifi Duration: ???
===== Rationale ===== CNs do no fulfill standard cloud assumptions: * weak links (unstable, small bandwidth) * small individual computing capacity (not always available, small CPU, small RAM, small storage) * very spread (many small devices). General approach: * step 1: design (architecture), develop, and implement(prototype) a CNs cloud platform * step 2: port some of (better all) the current CNs applications to the platform * step 3: deploy few clommunity boxes and test for a long period (2 weeks?). Iterate to step 1/2 if necessary * step 4: deploy clommunity boxes to the community (can be done in three iterations: it1, boxes are 100% funded, it2, boxes are funded 50%, it3, no funding any more) * Success indicator: number of it1/2/3 boxes deployed, number of ISO downloads ===== Tasks ===== * Identify CNs cloud characteristics vs. standard cloud * How does the previous differences effect standard cloud * Identify CNs current applications * Adaptation to the could approach * Changes to the applications needed * Expected benefits * Can the cloud approach equals at least the current performance? * Changes needed for standard cloud → community cloud * Identify potential new applications (just possible thx to CNs cloud) ===== Further information =====
==== CNs cloud vs. standard cloud ==== Cloud logical diagram: 3-. Application 2-. Platform → key layer; User and services localization and identification → key features 1-. Infrastructure
==== CNs current applications ==== === guifi.net === * “standard”: proxy (with LDAP and federation system), DNS, monitoring (graphs) * guifi.net server ISO: http://es.wiki.guifi.net/wiki/Distribuci%C3%B3n_guinux ====== Testbed deployment ====== Partners: guifi Duration: ??? ====== Software devolpment ====== Partners: UPC, SICS, KTH Duration: ??? ===== Platform develoment ===== ===== Existing applications port ===== ===== New applications =====
====== Experimentation and Evalutaion ====== ====== Dissemination ======