Easing libremesh virtualization #938

irina556 · 2022-10-17T03:17:37Z

Remove the host interface
Removes an interface that was created on the host after having started a node with qemu_dev_start
Put the message in ansible for access to cloud nodes
By raising a cloud of nodes we could access each one by clusterssh. However, the output message was not entirely clear. For this reason, it is modified so that the user can directly copy it and thus build the cloud of nodes.
Add the "files" directory in ansible
Since the qemu_cloud_start.yml playbook uses this directory, it is left created to prevent the user from having to do so.
Port change
When you wanted to start a node giving it access to the internet using --enable-wan for qemu_dev_start, a collision with the port occurred since dnsmasq uses port 53 by default, which in general in the different Linux distributions is already occupied by the systemd-resolved service. To solve this, another port is assigned so that this collision does not occur.
It is worth noting that bind-dynamic was used because simply assigning another port on some PCs did not work and on others it did.
Change ifconfig to ip
In the linux_bridge.py and linux_bridge_port.py modules used by ansible, there were calls to ifconfig, and since modern Linux distributions do not have this command to view the TCP/IP configuration, it was not possible to run the node cloud (unless installing the net-tools package for ifconfig use). To avoid this inconvenience to any other user, the ifconfig calls are modified with the ip surrogate.
Added a playbook called "cloud_and_node_packages" in which the installation of some packages needed to run the qemu-dev-start file (iptables,dnsmasq) and others needed such as clusterssh and bridge-utils to run qemu_cloud_start.yml was automated, in case the user's host did not have them installed.
Creation of detailed documentation for virtualization: VIRTUALIZING.md
Although there was already some documentation in TESTING.md, a new file was created in which the fact of raising LibreMesh virtuals is explained in a more detailed and procedural way. In this way, more complete knowledge is given to any new user about what he can and must do to set up virtual nodes.

…ling the dependencies

ilario · 2022-11-06T14:21:26Z

README.md

@@ -83,3 +87,4 @@ Support this project by becoming a sponsor. Your logo will show up here with a l
 [10]: https://github.com/libremesh/network-profiles/
 [12]: https://opencollective.com/libremesh
 [13]: https://libremesh.org/development.html
+[14]: https://github.com/irina556/lime-packages/blob/easing-libremesh-virtualization/VIRTUALIZING.md


Hi! The link should point to the file that will be in the libremesh/lime-packages default branch repository.

ping @irina556

G10h4ck · 2022-11-28T16:43:46Z

tools/ansible/qemu_cloud_start.yml

-
-          clusterssh {{ linklocals | join(' ') }}
+          
+          clusterssh -o "-o 'StrictHostKeyChecking=no' -o 'HostKeyAlgorithms=+ssh-rsa'" {{ linklocals | join(' ') }}


I think it is more readable if you change the first -o with --options

G10h4ck · 2022-11-28T16:56:08Z

tools/qemu_dev_start

@@ -216,7 +216,7 @@ if [ -n "$_arg_enable_wan" ]; then
    fi

    # DHCP server for WAN ifc
-    dnsmasq -F 172.99.0.100,172.99.0.100 --dhcp-option=3,172.99.0.1 -i "$WAN_IFC" --dhcp-authoritative --log-dhcp
+    dnsmasq -F 172.99.0.100,172.99.0.100 --dhcp-option=3,172.99.0.1 -i "$WAN_IFC" --dhcp-authoritative --log-dhcp --port=5353 --bind-dynamic


Are you sure DNS server for virtual machines will work as is without any change if the dnsmasq is listening on port 5353 ?

ilario · 2022-12-27T13:38:24Z

@irina556 are you reading? Can you fix or should we just merge and then fix?

G10h4ck · 2023-01-27T14:33:10Z

@ilario would you volunteer to test and do the last polishing I have suggested, so we can merge it?
This work seems valuable to me but @irina556 is not responding since months so we should found another way to merge this before it rots in merge conflicts.

ilario · 2023-01-30T14:32:03Z

@ilario would you volunteer to test and do the last polishing I have suggested, so we can merge it?

I would gladly do that, but I have little space on my hard drive also due to the 24 GB of the buildroot.
In order to get rid of those, I would need another place where to compile.
repo.libremesh.org was an option but it requires some complicated maintenance and updating, if I understood correctly.

Have you tried asking her GSoC mentor(s)?
If I recall correctly there was some people between @germanferrero, @spiccinini and/or @Patacon13.

Patacon13 · 2023-01-30T15:02:09Z

@ilario would you volunteer to test and do the last polishing I have suggested, so we can merge it?

I would gladly do that, but I have little space on my hard drive also due to the 24 GB of the buildroot. In order to get rid of those, I would need another place where to compile. repo.libremesh.org was an option but it requires some complicated maintenance and updating, if I understood correctly.

Have you tried asking her GSoC mentor(s)? If I recall correctly there was some people between @germanferrero, @spiccinini and/or @Patacon13.

Hi! Irina didn't see the previous messages. I've messaged her about the fixes that @G10h4ck proposes, so she's going to make them. Thanks for notifying!

G10h4ck · 2023-03-17T09:42:36Z

Hi! Irina didn't see the previous messages. I've messaged her about the fixes that @G10h4ck proposes, so she's going to make them. Thanks for notifying!

@Patacon13 @irina556 any news? I am about to re-target libremesh, it would be good to be able to merge this PR before of that

irina556 · 2023-03-17T13:09:55Z

Hello! I apologize for the time I was not there. I haven't been able to review the changes because I had a problem with the computer I did the project on. It was burned, so I have lost all the information and the environment in which I have worked. In the same way, now I review the comments and I will do what I can. But currently I am without a computer so I can do tests

G10h4ck · 2023-05-04T09:18:08Z

@irina556 did you managed to get a computer ?

a-gave · 2023-08-09T15:32:56Z

Hi!
I add just small notes on this.
I've tried it and it seems to work normally also with firmware images based on openwrt-22.03.5 and with openwrt-23.05.0-rc2.
But for both versions I had to use the generic-kernel.bin instead of ramfs.bzImage [0]

cd lime-packages/tools;
./qemu_dev_start --node-id 1 --enable-wan wlo1 \
    libremesh-2023.1-rc1-ow22-default-x86-64-generic-rootfs.tar.gz \
    libremesh-2023.1-rc1-ow22-default-x86-64-generic-kernel.bin

A second note
This tool qemu_dev_start seems to work only with images built by buildroot and not ones built by the imagebuilder.
I tried to just see if the firmware images built with imagebuilder ever boot on qemu using instead the produced generic-ext4-combined.img images, for both openwrt versions 22.03.5 and 23.05.0-rc2, using this script below taken from the README of Temba [1] and the boot goes on without errors:

gunzip libremesh-2023.1-rc1-ow22-default-x86-64-generic-ext4-combined.img.gz
qemu-system-x86_64 -M q35 -drive file=libremesh-2023.1-rc1-ow22-default-x86-64-generic-ext4-combined.img,id=d0,if=none,bus=0,unit=0 -device ide-hd,drive=d0,bus=ide.0

[0] The ramfs.bzImage is not produced anymore since openwrt-21.02.7. It seems like the bzImage is now the default format for the kernel in x86.

cat target/linux/x86/Makefile | grep bzImage
KERNELNAME:=bzImage

[1] https://farga.exo.cat/exo/temba#run-x86_64-in-qemu

irina556 and others added 20 commits September 7, 2022 14:49

Change ifconfig to IP

5f7ae3f

Put the message in ansible to access the cloud nodes

3266db3

Port change

0a1c29f

Remove host interface

5ae447b

Remove brctl

c9646c9

Change brctl by ip

81f96c0

Modify message for node access

bb55a62

Install the packages needed to run a node and the cloud

07d7279

Creation of a playbook that allows running a LibreMesh node by instal…

a50ac31

…ling the dependencies

Remove only_one_node.yml

4a9bc44

added files directory

5600b05

Create .placeholder

7c3f941

Cloud node management message is modified

99a6d77

Virtualization guide for libremesh is created

2f46263

Update README.md

78235f0

Update README.md

56ec2f6

Update README.md

3a5448e

Update README.md

cfe428b

Update README.md

bf64260

Update README.md

d84bca8

ilario reviewed Nov 6, 2022

View reviewed changes

G10h4ck requested changes Nov 28, 2022

View reviewed changes

G10h4ck added the OpenWrt 19.07 compatible Mark pull requests compatible with OpenWrt 19.07, would be nice to merge those before re-targetting label Mar 17, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Easing libremesh virtualization #938

Easing libremesh virtualization #938

irina556 commented Oct 17, 2022

ilario Nov 6, 2022

G10h4ck Nov 28, 2022

G10h4ck Nov 28, 2022

G10h4ck Nov 28, 2022

ilario commented Dec 27, 2022

G10h4ck commented Jan 27, 2023 •

edited

Loading

ilario commented Jan 30, 2023

Patacon13 commented Jan 30, 2023

G10h4ck commented Mar 17, 2023

irina556 commented Mar 17, 2023

G10h4ck commented May 4, 2023

a-gave commented Aug 9, 2023


		clusterssh {{ linklocals \| join(' ') }}

		clusterssh -o "-o 'StrictHostKeyChecking=no' -o 'HostKeyAlgorithms=+ssh-rsa'" {{ linklocals \| join(' ') }}

Easing libremesh virtualization #938

Are you sure you want to change the base?

Easing libremesh virtualization #938

Conversation

irina556 commented Oct 17, 2022

ilario Nov 6, 2022

Choose a reason for hiding this comment

G10h4ck Nov 28, 2022

Choose a reason for hiding this comment

G10h4ck Nov 28, 2022

Choose a reason for hiding this comment

G10h4ck Nov 28, 2022

Choose a reason for hiding this comment

ilario commented Dec 27, 2022

G10h4ck commented Jan 27, 2023 • edited Loading

ilario commented Jan 30, 2023

Patacon13 commented Jan 30, 2023

G10h4ck commented Mar 17, 2023

irina556 commented Mar 17, 2023

G10h4ck commented May 4, 2023

a-gave commented Aug 9, 2023

G10h4ck commented Jan 27, 2023 •

edited

Loading