Recent Posts by Christian Babski

I&IC’s OwnCloud Core Processing Library (evolution)

Note: “I&IC OwnCloud Core Processing Library” (working title) is part of a home cloud kit, which was described in a previous post and that will be composed by four various artifacts, both physical and digital.

The kit will be distributed freely at the end of the project.



One processing project with one cloud, while the server (OwnCloud) can still be accessed by a regular interface (OwnCloud client). The upper part (white) is the “network/server side” of the project (OwnCloud), hosted on a Linux server, while the bottom (grey dots) is user or “client side”. It can consists in connected objects or environments, interfaces, visualizations of different sorts.


The I&IC’s Owncloud Core Processing Library is now composed of a “client side” component and “server side” component (IICloud’s Addon).

The “client side” part of the library (“user side” vs. “network/server side” in the illustrations above and below) can be used from Processing, in order to get access to OwnCloud server(s) and manipulate files. The benefit of the core library resides in the fact that it mashups all together a set of heterogeneous functionalities in one single library (it has been therefore renamed I&IC OwnCloud Core Processing Library as it is more closely related to our research).

(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

Cookbook > How to set up Processing to use the OwnCloud Core Processing Library

We will describe how to use the OwnCloud Core Processing Library within the Processing framework, starting from a blank sketch. Library’s functions will be refined and new ones may be developped, some additional libraries will be added as well in order to propose high level functions deeper linked to the IICloud(s) project.



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–.

Toward OwnCloud Core Processing Library

The purpose of the OwnCloud Core Processing Library is to give the possibility to program “cloud functionalities” within a well known and simplified designer oriented programming language (and community): Processing.


Therefore, the OwnCloud Core Processing Library linked with our personal cloud merges the Open Collaboration Service (OCS) Share API with higher level functions in order to implement seamlessly “search&share files” applications written in the well known designers oriented Processing programming language. This will soon become available to everyone on the I&IC website. The workshops we are currently running / will run during the coming weeks are helping/will help us fine tune its functionalities.


The OwnCloud Core Processing Library allows the automation of the action of sharing files and the action of file tagging within an open source OwnCloud environment. Search&Sharing tasks can be threaded and/or interdependent, everything depending on the kind of results expected from one application to another. Thus, these actions can be driven by unmanned processes, decision-making (copy, delete, share one or several files) based on related metadata (i.e. metadata relation/link) or based on external data, dug from the Internet or networked/connected items/things.

Comments on: Setting up our own (small size) personal cloud infrastructure. Part #1, components

Following Patrick’s post about our different options for choosing a “Cloud” software and the one that we finally made by choosing ownCloud. Here are a few related comments that develop our point of view and technical choices.

ArkOs, Openstack and RiakCS all take the hand over an entire server/system/computer, offering a kind of embedded linux system within a human-friendly interface, the kind of mechanism one can find on ready-to-use NAS (Network Attached Storage) hardware.

Basically, it transforms any regular computer into a NAS device. One of the key points about the structure we are trying to setup is to be able to host anything we would like/need or may appear interesting to probe. That includes our own website(s), web services in order to feed projects with data and any kind of applications that may be useful to try and develop within the frame of this research.

We do need therefore to keep the research server as generic as possible by using a normal linux distribution, which we can then enhance by any set of additional services. While ArkOS, Openstack and RiakCS are of course interesting projects, at some point, it may become already too specific for our goals.




Owncloud appears to be a simple web site structure dedicated to file sharing. As mentioned in my previous post, Owncloud proposes a set of APIs that allow the access to Owncloud features while being able to develop our own applications. Thus, these applications can rely on Owncloud while being hosted on a heterogeneous set of devices, network connected.

Recent Comments by Christian Babski

    No comments by Christian Babski yet.