nearxos/Rina-deployment
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update VM deployment script and documentation to reflect new default VM name 'CUBE' and IP configuration. Adjusted cloud-init settings for static IP and network details. Enhanced README and related scripts for clarity on VLAN and bridge usage.

Browse Source
This commit is contained in:
nearxos
2026-02-17 15:22:05 +02:00
parent 9b1b4cef44
commit 307a34a2a5
7 changed files with 42 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/vlan40-bridge-systemd-networkd.md
View File

@@ -158,13 +158,13 @@ This ties the VLAN to eth1 so it is created when eth1 is configured. eth1 stays
## 8. Deploy the VM on br1.40
After `br1.40` is up and has `eth1.40` as a port, deploy the Rina VM onto it:
After `br1.40` is up and has `eth1.40` as a port, deploy the VM onto it:
```bash
BRIDGE=br1.40 ./deploy-rina-vm.sh
```
The VM will get an IP in your VLAN 40 subnet via cloud-init (e.g. 192.168.40.225); adjust cloud-init if your subnet or gateway differ.
By default the VM is named **CUBE**. It will get the IP configured in `cloud-init/user-data` (e.g. 192.168.0.225/24); adjust that file if your subnet or gateway differ. Console: `virsh console CUBE`.
---