First node deployment¶
This guide intends to describe the process of deploying your first node. We will call it “box0”. This node is nothing else than a basic compute node plus an LXD container running OpenNebula. A ready to be deployed image have been created, check First node deployment.
You will need a microSD card with at least 4GB and preferably class 10 or better.
- Read Notes sections attached to some steps, before using the shell
- Commands prefixed by “#” are meant to be run as root. Commands prefixed by “$” must be run as a normal user.
(...)in code snippets means that could be code before/after the modified lines. That portion of code need to stay unmodified.
1. Get and install your first node¶
Please, download the image and follow this short guide.
1.2. Dump image on a microSD card¶
1.2.1. If you use Linux¶
I will assume /dev/mmcblk0 is your microSD card. Please check and be sure. If you make a mistake and erase all of your girlfriend’s pictures you are on your own so good luck.
dd if=./image_name.img of=/dev/mmcblk0 && sync
1.3. Turn it on¶
Connect the microSD to your Raspberry Pi 3 and turn it on.
1.4. Expand filesystem¶
Now you should expand the filesystem so it will use all the space from your microSD card. Log in the new node either through ssh or directly with a keyboard and a monitor. Default user and password is “cloud”. Enter the “Raspberry Pi Software Configuration Tool”:
Go to “Advanced Options” and hit “Expand Filesystem”
“READY”, that is all. Easy, right?
Now you have your first node ready. As explained before on the overview we recommend at least two nodes and a NFS drive for production, but if you just want to try “Clox” you can use this Raspberry Pi 3. Everything is already configured. Open the following URL: http://192.168.0.9:9869/. The default user is “oneadmin” and default password “oneadmin” also.
If the session closes unexpectedly, the time and date must be wrong. The problem is that, in order to cut costs, the Real Time Clock (RTC) was left out from this SBC, so every time you reboot date and time will be lost. You can add an RTC, use an NTP server or simply update manually the date. Containers can’t modify the system’s clock for security issues, so just update the time and date on box0 and the OpenNebula’s container will automatically update it. Log in to box0 and, as root, check and update the time if necessary:
date date -s "2 OCT 2006 18:00:00"
The default OpenNebula’s datastore has been maintained, with the default configuration. This datastore uses the ssh drivers, which means the image will be copied before deploying the container. Because of this the container will start slowly and will not run as smoothly as it should. That is why we recommend an NFS datastore. Still, you can now go to the frontend with this URL: http://192.168.0.9:9869/ but only with testing purposes. The default user is “oneadmin” and default password “oneadmin” also.
Now, you should create the NFS datastore and add new compute nodes. Please, go to the next guide.