Cluster : app settings, underscore in db and user name, dhcp scopes sync

[warlordattack]

I have a cluster with two nodes :

1/ sharing mysql

LAN : 192.168.50.x

192.168.50.118 (Mint VM ip)
Pc1 > Proxmox Mint VM > Docker > Technitium Node 1 # cluster : primary node, 192.168.50.219 (lan IP, mvlan net)
Pc1 > Proxmox Mint VM > Docker > MariaDB > mdb:3306 # inside docker (docker bridge net, mdb = 172.31.0.33)
Pc1 > Proxmox Mint VM > Docker > MariaDB > 192.168.50.118:3306 # lan (lan IP, mvlan net)

192.168.50.141 (docker container ip)
Pc2 > Proxmox Container > Docker > Technitium Node 2 # cluster : secondary node, 192.168.50.208 (lan IP, mvlan net)

Now we want use "Query Logs (MySQL)" and share a database for the two nodes.

Node 1 :

• sees mysql on internal docker bridge net as : mdb:3306
• can NOT see mysql on 192.168.50.118:3306 because 192.168.50.118 is Pc1 host IP (containers do not see the host IP)

Node 2 :

• sees mysql on LAN as : 192.168.50.118:3306
• can NOT see mysql on mdb:3306 because this node is on an other PC

The "Query Logs (MySQL) app" config is a unique file shared through the two nodes of the cluster
so we have one shared IP for mysql on two nodes :

{
  "enableLogging": false,
  "maxQueueSize": 1000000,
  "maxLogDays": 180,
  "maxLogRecords": 0,
  "databaseName": "technitium_db",
  "connectionString": "Server=192.168.50.118; Port=3306; Uid=u_technitium; Pwd=password;"
}

If server value is "192.168.50.118" then only Node 2 resolve it,
if server value is "mdb" then only Node 1 resolve it.

In this cluster situation, each cluster node needs it's own config, or we need multiple server values possible so each node will fail on one and resolve the second.

Please ADD possibility to have separate config for each node per app.

2/ underscore inside db and user name

I use user and db names with underscores for lisibility :

• "databaseName": "technitium_db",
• Uid=u_technitium;

This can cause problems (sql errors) in queries perhaps _ (underscode) must be escaped with \ (antislash) ?
Please test and correct this.
I had to create database manually with SQL queries, because cluster nodes could not connect or execute queries to create/update database objects.

3/
3.1/
In my cluster i ceated DHCP scopes on the main node,

• one for LAN
• other for proxmox internal NET for VMs in Proxmox 1,
  inside scopes i added many (99) reserved leases (so all devices take fixed IP from MAC adresses),
  the second node did not replicate the DHCP scopes,
  so if i reboot one node (or one node is down), the other will not assign leases to LAN network devices.

Entering 99 leases manually in the scope on each node and maintaining two lists on two nodes is painful (scope replication and sync could solve this).

3.2/
Also on the second node i do not need proxmox scope, i need only LAN scope (because the second node does not have access to proxmox 1).

So we need :

• replication of scopes between cluster nodes (for backup and survival purposes)
• be able to activate some scopes only on some nodes (one node does not need all same scopes active as other node)

LAN > Proxmox 1
Cluster > Node 1
Cluster > Node 1 > Scope LAN : active (gives leases to LAN devices when Node 2 is down)
Cluster > Node 1 > Scope Proxmox 1 : active (gives leases to proxmox 1 internal NET, VMs and CTs)
Cluster > Node 1 > Scope Proxmox 2 : unactive

LAN > Proxmox 2
Cluster > Node 2
Cluster > Node 2 > Scope LAN : active (gives leases to LAN devices when Node 1 is down)
Cluster > Node 2 > Scope Proxmox 1 : unactive
Cluster > Node 2 > Scope Proxmox 2 : active (gives leases to proxmox 2 internal NET, VMs and CTs)

Please add possibility to :

• sync DHCP scopes from master to slave nodes (so we maintain list of MAC-IP leases in one place)
• activate scopes per node (each node will have specific scopes active only)

Best regards :)

[ShreyasZare]

Thanks for the request.

• The query log app's are planned to support node specific config soon (see issue MySQL logging App and DNS cluster #1834).

• Will check the issue with _ char. For username part, you should be able to escape it since the connection string in the config is used directly.

• DHCP Server does not support Clustering yet and thus it works independently on each node. Clustering support for DHCP is planned. This will take some time though and timeline for it is not clear yet.

[ShreyasZare]

2/ underscore inside db and user name

I tried using underscore char with both db and username with mysql and it worked without any issues. What error are you seeing? Please share the complete error log that you can find in the Logs > View Logs section on the panel.

[srt4fun]

3/ 3.1/ In my cluster i ceated DHCP scopes on the main node,

• one for LAN
• other for proxmox internal NET for VMs in Proxmox 1,
  inside scopes i added many (99) reserved leases (so all devices take fixed IP from MAC adresses),
  the second node did not replicate the DHCP scopes,
  so if i reboot one node (or one node is down), the other will not assign leases to LAN network devices.

Entering 99 leases manually in the scope on each node and maintaining two lists on two nodes is painful (scope replication and sync could solve this).

There is an easy workaround for that... On your primary server take a settings backup with only the "DHCP Scope Files (.scope)" option checked. Then restore backup on your secondary servers with only the "DHCP Scope Files (.scope)" option checked. Only need to change server specific settings, if any.