If you want to install and test Cloudy, we strongly suggest you to take a look at the “Get started” section from the official web site. There you can find a lot of information from a basic installation to a LXC installation.
However if your computer's architecture is based on 64 bits or you have the UEFI system, you must follow some different steps. These steps are explained below in this FAQ, answering the question below “I'd like to use a 64 bit architecture version of Cloudy. How can I get it?” under the bold characters '“Cloudynize” your system'.
At this time we just have 32 bits ISO, however you can get the 64 bits version by one of these ways:
First, download the generation system:
apt-get install build-essential live-build imagemagick curl debootstrap git unzip git clone http://dev.cloudy.community/guifi.net/cloudy-image-builder.git
Now you must make a little modification to the Makefile file:
ARCH ?= amd64 FLAVOUR ?= amd64
Afterwards, you can build build the image like this:
Once the image has been created, you have Cloudy 64 bits in ./devel/binary.hybrid.iso
Another way to install Cloudy is modifying a current Debian OS by applying a script which turns this Debian into a Cloudy. This is also a good way to install Cloudy on a system with UEFI, since the Cloudy ISO doesn't support it yet but Debian Jessie's ISO does. To do this we can run the following commands over a basic Debian OS:
git clone https://github.com/Clommunity/cloudynitzar && cd cloudynitzar chmod +x cloudynitzar.sh sudo ./cloudynitzar
This simple steps will turn your Debian machine into a Cloudy distro, and assuming that your previous Debian was 64 bit, so will Cloudy. In order to get more information about the dependencies of this script please refer to the README file provided in the repository commented above.
In the first versions of Cloudy, in order to publish and look for services, we used Avahi1) over a layer 2 virtual network managed by GeTINConf2). However, after some tests were carried on, we noticed that this system requiered a huge amount of resources. Therefore we made some research in similar software that allowed us to, not only do the same, but also without such a ressource consumption.
For the time being however, it is important for the GeTINConf page to have the Guifi address device set; the rest remains unused.
In a short time though we expect to definitely remove GeTINConf from the Cloudy distro.
In any other system the installation would be very simple: just download the Cloudy ISO and install it. However the MINIX devices have one particular issue… they make use of UEFI in order to boot the system. For the time being, the Cloudy ISOs does not suppot UEFI, so we need another way to proceed. This alternative way is explained in this same web page, in the question above called “I'd like to use a 64 bit architecture version of Cloudy. How can I get it?” under the bold characters '“Cloudynize” your system'.
The easiest way to solve this is leaving the field tagged as “bootstrap node” blank. By doing this, you will be waiting for other nodes to connect to you.
This happens because Serf uses a gossip protocol: when it starts, it can be provided with another active node within the microcloud and then connect to it; once this is done they exchange a list of known-nodes and randomly connect to them. When no node is provided, it won't try to connect to any node, it will simply wait for others to connect to it. This is why if you leave the field blank it waits for connections.
If you have a question which is not answered in this FAQ, please subscribe to the cloudy-users mailing list and send a mail there, We'll be glad to solve your issue and add it in this FAQ.