|
| 1 | +--- |
| 2 | +title: Deploying |
| 3 | +nav_order: 91 |
| 4 | +has_children: true |
| 5 | +--- |
| 6 | + |
| 7 | +# Deploying the (12)urenloop stack |
| 8 | + |
| 9 | +# Requirements |
| 10 | + |
| 11 | +## Inventory |
| 12 | + |
| 13 | +Gather the following: |
| 14 | + |
| 15 | +- [ ] 1 Flight case with router/switch: |
| 16 | + - See the [Network documentation](./NETWORK) |
| 17 | + |
| 18 | +- [ ] 2 clients: |
| 19 | + - Dell thin clients |
| 20 | + - `snowball` & `meeseeks` from Zeus |
| 21 | + - These will be wiped! |
| 22 | + |
| 23 | +- [ ] 8 ronnys: |
| 24 | + - Also known as stations |
| 25 | + - Raspberry Pi 4's |
| 26 | + - These will be wiped! |
| 27 | + |
| 28 | +- [ ] 1 laptop with `uv` installed |
| 29 | + |
| 30 | +Make everything is labelled: |
| 31 | + - [ ] `client1-2` |
| 32 | + - [ ] `ronny01-08` |
| 33 | + - [ ] What ports on the switch are to be used for the `telnet` (tel-network). |
| 34 | + |
| 35 | +## Static DHCP leases |
| 36 | + |
| 37 | +The router should automatically assign IP addresses based on MAC address via DHCP as follows: |
| 38 | + |
| 39 | +| Host | IP | MAC | |
| 40 | +|---------|---------------|-------------------| |
| 41 | +| client1 | 172.12.50.21 | 90:8D:6E:8C:8A:01 | |
| 42 | +| client2 | 172.12.50.22 | 90:8D:6E:8C:8A:9B | |
| 43 | +| ronny01 | 172.12.50.101 | DC:A6:32:49:97:00 | |
| 44 | +| ronny02 | 172.12.50.102 | DC:A6:32:49:9A:90 | |
| 45 | +| ronny03 | 172.12.50.103 | E4:5F:01:4A:42:DE | |
| 46 | +| ronny04 | 172.12.50.104 | DC:A6:32:49:62:B4 | |
| 47 | +| ronny05 | 172.12.50.105 | DC:A6:32:49:65:33 | |
| 48 | +| ronny06 | 172.12.50.106 | E4:5F:01:4A:40:E2 | |
| 49 | +| ronny07 | 172.12.50.107 | DC:A6:32:49:97:E7 | |
| 50 | +| ronny08 | 172.12.50.108 | DC:A6:32:49:98:CD | |
| 51 | + |
| 52 | +> If you replace any hardware, make sure to update the MAC in the router config, this table and the [Network documentation](./NETWORK) |
| 53 | +
|
| 54 | +## Preparing devices for ansible |
| 55 | + |
| 56 | +### Clients |
| 57 | + |
| 58 | +Wipe and install Debian on the clients as described in [Preparing a client for the ansible-config](deploying/prepare_a_client): |
| 59 | + - [ ] `client1` |
| 60 | + - [ ] `client2` |
| 61 | + |
| 62 | +### Ronnys |
| 63 | + |
| 64 | +Flash the ronnys and set a password as described in [Preparing a ronny for the ansible-config](deploying/prepare_a_ronny): |
| 65 | + - [ ] `ronny01` |
| 66 | + - [ ] `ronny02` |
| 67 | + - [ ] `ronny03` |
| 68 | + - [ ] `ronny04` |
| 69 | + - [ ] `ronny05` |
| 70 | + - [ ] `ronny06` |
| 71 | + - [ ] `ronny07` |
| 72 | + - [ ] `ronny08` |
| 73 | + |
| 74 | +### Laptop |
| 75 | + |
| 76 | +- [ ] Clone the [ansible-config](https://github.com/12urenloop/ansible-config/) repository on the laptop and follow the install instructions for dependencies in the `README.md`. |
| 77 | + |
| 78 | +## Deploying |
| 79 | + |
| 80 | +Ensure your `hosts.yml` is accurate. |
| 81 | + |
| 82 | +Then, execute all relevant ansible playbooks: |
| 83 | + |
| 84 | +```sh |
| 85 | +ansible-playbook -kK playbook-01-common-init.yml |
| 86 | +ansible-playbook -kK playbook-02-clients-init.yml |
| 87 | +ansible-playbook -kK playbook-03-stations-init.yml |
| 88 | +``` |
| 89 | + |
| 90 | +```sh |
| 91 | +ansible-playbook -kK playbook-10-stations-ronny.yml |
| 92 | +# ansible-playbook -kK playbook-11-stations-uwb.yml # prototype |
| 93 | +``` |
| 94 | + |
| 95 | +```sh |
| 96 | +ansible-playbook -kK playbook-20-client1-telraam.yml |
| 97 | +... |
| 98 | +``` |
| 99 | + |
| 100 | +```sh |
| 101 | +ansible-playbook -kK playbook-30-client2-monitoring.yml |
| 102 | +... |
| 103 | +``` |
0 commit comments