OpenCloud (Academic Research) Mesh

Note: When we had to pick an open source cloud computing platform at the start of our research, we dug for some time to pick the one that would better match with our planned activities. We chose ownCloud and explained our choice in a previous post, so as some identified limitations linked to it. Early this year came this announcement by ownCloud that it will initiate “Global Interconnected Private Clouds for Universities and Researchers” (with early participants such has the CERN, ETHZ, SWITCH, TU-Berlin, University of Florida, University of Vienna, etc.) So it looks like we’ve picked the right open platform! Especially also because they are announcing a mesh layer on top of different clouds to provide common access across globally interconnected organizations.

This comforts us in our initial choice and the need to bridge it with the design community, especially as this new “mesh layer” is added to ownCloud, which was something missing when we started this project (from ownCloud version 7.0, this scalability became available though). It now certainly allows what we were looking for: a network of small and personal data centers. Now the question comes back to design: if personal data centers are not big undisclosed or distant facilities anymore, how could they look like? For what type of uses? If the personal applications are not “file sharing only” oriented, what could they become? For what kind of scenarios?

 

OpenCloudMesh_4.0_150dpi

Cloud Computing design exhibit in Saint Etienne

The Cité du Design in Saint Etienne (France) had an exhibit about cloud computing few months ago. It was part of an initiative by Orange, the French telco, that asked design students to speculate about “the personal digital space of tomorrow.” The question they addressed are the following:

What new uses? How to organize this space for storing personal data? How to avoid being overwhelmed by all the content that we unwinttingly store in it on a daily basis? How to make the memories that we capture on video and in photos more accessible? How can we easily send all or part of this special prvate space to the people we love? Can we find a new material or emotional value for this data?

(The reasons why an I&IC’s) OwnCloud Core Processing Library

Beside the reflection produced by the overall Inhabiting & Interfacing the Cloud(s) project and the related necessity to provide “access to tools” to a larger community (largely described in the founding document of the project and in a former post about the setting up of this library), new paradigms may arise in the global organization of servers farms. These new paradigms may in return generate new ways to organize files on cloud servers (by a different control of the redundancy principle for example, or a different use of file’s duplication, etc.), allowing for new projects.

In order to answer the stakes of the I&IC design research and to prepare such output/proposals, we have developed the OwnCloud Core Processing Library that will allow to setup a software layer on top of the hardware layer.

 

To download and learn how to use the OwnCloud Core Processing Library, we’ve prepared a post in the Cook Books section of this site.

 

owncloud_logo    processing2-logo

Reblog > Decentralizing the Cloud: How Can Small Data Centers Cooperate?

Note: while reading last Autumn newsletter from our scientific committee partner Ecocloud (EPFL), among the many interesting papers the center is publishing, I stumbled upon this one written by researchers Hao Zhuang, Rameez Rahman, and Prof. Karl Aberer. It surprised me how their technological goals linked to decentralization seem to question similar issues as our design ones (decentralization, small and networked data centers, privacy, peer to peer models, etc.)! Yet not in such a small size as ours, which rather look toward the “personal/small” and  “maker community” size. They are rather investigating “regional” data centers, which is considered small when you start talking about data centers.

Inhabiting and Interfacing the Cloud(s) – Talk & workshop at LIFT 15

Note: Nicolas Nova and I will be present during next Lift Conference in Geneva (Feb. 4-6 2015) for a talk combined with a workshop and a skype session with EPFL (a workshop related with the I&IC research project will be finishing at EPFL –Prof. Dieter Dietz’s ALICE Laboratory at EPFL-ECAL Lab– the day we’ll present in Geneva). All persons who follow the research on this blog and that would be present during Lift 15, please come see us and exchange ideas!

 

Via the Lift Conference

—–

Inhabiting and Interfacing the Cloud(s)

Workshop
Curated by Lift
Fri, Feb. 06 2015 – 10:30 to 12:30
Room 7+8 (Level 2)
-
Architect (EPFL), founding member of fabric | ch and Professor at ECAL
-
Principal at Near Future Laboratory and Professor at HEAD Geneva
-

Workshop description : Since the end of the 20th century, we have been seeing the rapid emergence of “Cloud Computing”, a new constructed entity that combines extensively information technologies, massive storage of individual or collective data, distributed computational power, distributed access interfaces, security and functionalism.

In a joint design research that connects the works of interaction designers from ECAL & HEAD with the spatial and territorial approaches of architects from EPFL, we’re interested in exploring the creation of alternatives to the current expression of “Cloud Computing”, particularly in its forms intended for private individuals and end users (“Personal Cloud”). It is to offer a critical appraisal of this “iconic” infrastructure of our modern age and its user interfaces, because to date their implementation has followed a logic chiefly of technical development, governed by the commercial interests of large corporations, and continues to be seen partly as a purely functional,centralized setup. However, the Personal Cloud holds a potential that is largely untapped in terms of design, novel uses and territorial strategies.

The workshop will be an opportunity to discuss these alternatives and work on potential scenarios for the near future. More specifically, we will address the following topics:

  • How to combine the material part with the immaterial, mediatized part? Can we imagine the geographical fragmentation of these setups?
  • Might new interfaces with access to ubiquitous data be envisioned that take nomadic lifestyles into account and let us offer alternatives to approaches based on a “universal” design? Might these interfaces also partake of some kind of repossession of the data by the end users?
  • What setups and new combinations of functions need devising for a partly nomadic lifestyle? Can the Cloud/Data Center itself be mobile?
  • Might symbioses also be developed at the energy and climate levels (e.g. using the need to cool the machines, which themselves produce heat, in order to develop living strategies there)? If so, with what users (humans, animals, plants)?

The joint design research Inhabiting & Interfacing the Cloud(s) is supported by HES-SO, ECAL & HEAD.

Interactivity : The workshop will start with a general introduction about the project, and moves to a discussion of its implications, opportunities and limits. Then a series of activities will enable break-out groups to sketch potential solutions.

Cookbook > Setting up your personal Linux & OwnCloud server

Note: would you like to install your personal open source cloud infrastructure, maintain it, manage your data by yourself and possibly develop artifacts upon it, like we needed to do in the frame of this project? If the answer is yes, then here comes below the step by step recipe on how to do it. The proposed software for Cloud-like operations, ownCloud, has been chosen among different ones. We explained our (interdisciplinary) choice in this post, commented here. It is an open source system with a wide community of developers (but no designers yet).

We plan to publish later some additional Processing libraries — in connection with this open source software — that will follow one of our research project’s objectives to help gain access to (cloud based) tools.

Would you then also like to “hide” your server in a traditional 19″ Cabinet (in your everyday physical or networked vicinity)? Here is a post that details this operation and what to possibly “learn” from it –”lessons” that will become useful when it will come to possible cabinet alternatives–.

Data Hotel

By Wednesday, November 26, 2014 Tags: 0075, Clouds, Infrastructure, Internet, observation Permalink 0

15678040278_09b341e0c2_o

(Reblogged from Pasta and Vinegar)

A billboard encountered at Haneda Airport in Tokyo this week. I find it interesting to observe the criteria chosen by the cloud company: we understand here that the service should be easy and that a reliable support might exist (24 hours). This looks quite common in the tech industry. However, I find the two others characteristics quite intriguing: “public cloud” and “system architect” sounds a bit abstract and strange. Perhaps the latter corresponds to the idea of a well-designed system, but I wonder about the notion of “public cloud” itself: what does that mean? Although it might suggest a public access to data, it may consist in something else (perhaps there’s a Japanese thing I’m missing here) as it’s difficult to sell people a service where all your data are made public.