Test all Supernodes with testsnXX nodes

freifunkh / ansible

Here we store all Ansible roles and configs used for Freifunk Hannover.

MIT License

7 stars 3 forks source link

Test all Supernodes with testsnXX nodes #166

Open lemoer opened 3 years ago

lemoer commented 3 years ago

[ ] Automate the creation of testsnXX nodes
[ ] Deploy testsnXX for fastd for every supernode
[ ] Deploy testsnXX for wireguard for every supernode

I started to implement the creation of testsnXX nodes here: https://github.com/freifunkh/ansible-deploy-gluon-to-proxmox .

lemoer commented 3 years ago

I added the milestone "Beginn der stabilen Phase", as this contains useful monitoring and should therefore implemented before the "stabile Phase".

AiyionPrime commented 3 years ago

This contains monitoring? :)

1977er commented 3 years ago

Yes. We already had some testsnXX nodes, which were set up manually and probably did not survive an autoupdate.

The former testsn nodes included a zabbix-client on the gluon node.

lemoer commented 3 years ago

I made some progress today:

A proxmox bridge for the client interface of the router is created.
The bridge is used to configure the node via ssh.
Currently the following things are done in config mode:
- The hostname are configured correctly.
- The node is marked as "configured".
- Afterwards the node is rebooted.

lemoer commented 3 years ago

I again made some progress today:

Multiple gluon nodes can now be created.
The fastd/wireguard keys are downloaded to the ansible control host, so they can be added to a peers git later.

@1977er After the current playbook is executed, the nodes are rebooted into normal running mode. Therefore if their keys are submitted into our peers directory, they should already be fully functional. Other tasks/playbooks could then install zabix, ... stuff.

Next steps:

[ ] Maybe use add_host and delegate_to to run stuff on the newly created hosts.

lemoer commented 3 years ago

This will be normal gluon nodes, which are added to the peers repo. Therefore this can be done without touching any core infrastructure. Therefore it's not a blocker for the milestone.