Frequently Asked Questions
What workloads can I run on the different hardware devices?
Depending on the device you have is recommended to run a specific number of services together. In the hardware page in the workloads section you can find some recommendations based on our tests installing Cloudy in different hardware.
I’d like to install Cloudy and/or to know more about it.
If you want to install and to test Cloudy, we suggest you to take a look at the Get started. There you will find a lot of information from a basic installation to a installation the system in a virtual machine.
However if your computer’s architecture is based on 64 bit or you have the UEFI system, you must follow some different steps. These steps are explained in this FAQ below, answering the question “I’d like to use a 64 bit architecture version of Cloudy. How can I get it?”.
I’d like to use a 64 bit architecture version of Cloudy. How can I get it?
For the moment we just have a 32 bit ISO image, however you can get the 64 bit version by one of these ways:
I’ve just configured GeTINConf but it doesn’t start. What’s going on?
In the first versions of Cloudy, in order to publish and to look for services, we used Avahi over a layer 2 virtual network managed by GeTINConf sources. 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 the same, but also without such a ressources consumption.
For the time being, 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.
I’m in an isolated island and therefore I can’t start Serf’s bootstrap among other things. What can I do?
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, Serf 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.
I’ve just received a MINIX device to test Cloudy but it is not installed. How do I install Cloudy?
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 do not suppot UEFI, so we need another way to proceed.
This alternative way is explained in this FAQ above, in the question “I’d like to use a 64 bit architecture version of Cloudy. How can I get it?”, concretely in the point “Cloudynize”.
How can I configure Cloudy in a client node (Guifi.net)?
In order to allow a Cloudy installed in a client node to interact to other Cloudys, is needed to do the following:
1. Know the node’s public IP address (10.x.x.x); not the one assigned to Cloudy but the IP assigned to the client node.
2. Edit a couple of files and declare the public IP of the node.
3. To do port forwarding for the port 5000 (serf). And if you want more services you will have to redirect (forward) the port of each service.
I have a Raspberry Pi. Can I install Cloudy on it?
Yes, you can install Cloudy because it is based in Debian which has support for ARM architecture.
However, currently we only have pre-built images for x86 architecture, but you can install Cloudy over a Debian based system with the alternative method commented above; “clouydinize”.
You can read how to do it in the Cloudy Raspberry Pi article in the Guifi.net wiki.
I have a question and I could not find it in this FAQ. What can I do?
If you have a question which is not answered in this FAQ, please subscribe to the cloudy-users mailing list and send an e-mail there, we will be glad to help you and to add your question in this FAQ.