Note: another interesting service for declaring and sharing data… through the cloud. Possibly the most simple we went through. Dweet.io.
Also to be mentioned with a similar goal but more complete/complex, OpenRemote.
I&IC Workshop #2 with James Auger at HEAD: Design Implications
Based on the concepts and scenarios produced in our second workshop, we decided to work on the design implications of such projects. More specifically, we realized the set of contexts (religion, music, etc.) the workshop participants worked on share common traits: the needs for a cloud infrastructure was fairly similar and let to the idea of a basic “data unit”. Such a mobile system would act as a mini-data center.
I&IC Workshop #2 with James Auger at HEAD: output > “Cloudified” Scenarios
Note: the post I&IC Workshop #2 with James Auger at HEAD, brief: “Cloudy” presents the objectives and brief for this workshop.
After last week’s workshop at HEAD – Genève, we learnt that addressing Cloud Computing from a design perspective requires to take a detour. Instead of looking at data centers and cloud computing directly, we asked students to choose a domain of everyday life (religion, cooking, communication, etc.) and work on how this technology may influence it, the kinds of practices that may emerge and what kind of implications would surface. The projects reflect this diversity and we also push the student to adopt both a critical and speculative angle. Such requirements mean that the output of the workshop largely consists in a set of short scenarios/usage strategies exemplified by sketches and pictures. Each of them provides a subtle perspective on cloud computing by showing that the limits and the opportunities of these technologies are entangled.
Cloudified Scenarios – a workshop with James Auger at HEAD – Genève on Vimeo.
Two posts have been added later as follow-ups to this one that propose an update to the direct results of the workshop:
- http://www.iiclouds.org/20141112/iic-workshop-2-at-head-design-implications/
- http://www.iiclouds.org/20141112/iic-workshop-2-at-head-ui-proposals/
Setting up our own (small size) personal cloud infrastructure. Part #2, components
While setting up our own small size data center and cloud infrastructure, we’ve tried to exemplify the key constitutive ingredients of this type of computing infrastructure, as of November 2014. But we’ve also tried to maintain them as much open as we could, for further questioning, developments and transformations.
The first key ingredients are software parts and we’ve described them in the previous post about the same topic.
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.
Setting up our own (small size) personal cloud infrastructure. Part #1, components
On the way to the development of different artifacts for the design research (Inhabiting & Interfacing the Cloud(s)), we’ll need to work with our own “personal cloud”. The first obvious reason is that we’ll need a common personal platform to exchange research documents, thoughts and work together between the different (geographically distributed) partners involved in the project. We are thus our own first case study. The second one is to exemplify the key components about how a small data center / cloud infrastructure might be assembled today and learn from it.
But then, more importantly, this will become necessary for two other main objectives: first one is that we would like to give access to “cloud” tools to the design, architecture and makers communities, so that they can start play and transform a dedicated infrastructure (and this won’t of course be possible with all type of systems); second one will possibly be for the “hands on” and “prototyping” parts of our research, for which we’ll need an accessible cloud based architecture to modify or customize (this includes both the software and hardware), around which some open developments, networked objects, new interfaces, apps, etc. could be developed.
From Bergcloud to ?
Even if unfortunately Bergcloud is a dead project now (and that it sadly brought down the design collective Berg too), I mention it here on our research blog as it probably has some connections with our own research project and what we might try to develop later as tools. The unsuccessful commercial approach of Bergcloud to connected objects should also be taken as a question toward this big “buzz” though.
