samba.git/ctdb/server, branch talloc-2.4.2

ctdb: send a CTDB_SRVID_IPREALLOCATED message after CTDB_EVENT_IPREALLOCATED

2024-01-04T11:39:36+00:00

Event scripts run the "ipreallocated" hook in order to notice that some ip addresses
in the cluster potentially changed.

CTDB_SRVID_IPREALLOCATED gives C code a chance to get notified as well once the event
scripts are finished.

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Martin Schwenke

ctdb-server: Drop unnecessary copy of destination address

2023-12-15T12:09:21+00:00

Modernise debug while touching the code.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=15523

Signed-off-by: Martin Schwenke 
Reviewed-by: Stefan Metzmacher 

Autobuild-User(master): Stefan Metzmacher 
Autobuild-Date(master): Fri Dec 15 12:09:21 UTC 2023 on atb-devel-224

ctdb-daemon: Use ctdb_connection_to_buf() to simplify

2023-12-15T11:06:34+00:00

The one case that is no longer handled specially is when the
destination address is IPv4 loopback.  This may previously have been
used to avoid flooding the logs when testing.  However, that seems
unnecessary - if testing with 127.0.0.1 then make it a public address.

Modernise debug while touching the code.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=15523

Signed-off-by: Martin Schwenke 
Reviewed-by: Stefan Metzmacher

ctdb: add/implement CTDB_CONTROL_TCP_CLIENT_PASSED

2023-12-15T11:06:34+00:00

With multichannel a tcp connection is registered first with
a temporary smbd process, that calls CTDB_CONTROL_TCP_CLIENT
first and then passes the tcp connection to the longterm smbd
that already handles all connections belonging to the specific
client_guid. That smbd process calls CTDB_CONTROL_TCP_CLIENT
again, but the 'tickle' information is already there.
When the temporary smbd process exists/disconnects from ctdb
or calls CTDB_CONTROL_TCP_CLIENT_DISCONNECTED, the 'tickle'
information is removed, while the longterm smbd process
still serves the tcp connection.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=15523

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Martin Schwenke

ctdb: add/implement CTDB_CONTROL_TCP_CLIENT_DISCONNECTED

2023-12-15T11:06:34+00:00

With multichannel a ctdb connection from smbd may hold multiple
tcp connections, which can be disconnected before the smbd
process terminates the whole ctdb connection, so we a
way to remove undo 'CTDB_CONTROL_TCP_CLIENT' again.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=15523

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Martin Schwenke

ctdb: make use of ctdb_canonicalize_ip_inplace() in ctdb_control_tcp_client()

2023-12-15T11:06:34+00:00

We could also remove the src_addr and dest_addr helper variables
completely, but that would be too much for this commit.

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Martin Schwenke

ctdb: remove unused ctdb->client_ip_list and print debug on ctdb_tcp_list instead

2023-12-15T11:06:34+00:00

BUG: https://bugzilla.samba.org/show_bug.cgi?id=15523

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Martin Schwenke

ctdb: Fix code spelling

2023-12-08T02:28:33+00:00

Signed-off-by: Joseph Sutton 
Reviewed-by: Andrew Bartlett

ctdb: Remove trailing whitespace

2023-12-08T02:28:33+00:00

Signed-off-by: Joseph Sutton 
Reviewed-by: Andrew Bartlett

ctdb: Add "home_nodes" file to deterministic IP allocation

2023-10-10T14:17:19+00:00

With a file "home_nodes" next to "public_addresses" you can assign
public IPs to specific nodes when using the deterministic allocation
algorithm. Whenever the "home node" is up, the IP address will be
assigned to that node, independent of any other deterministic
calculation. The line

192.168.21.254 2

in the file "home_nodes" assigns the IP address to node 2. Only when
node 2 is not able to host IP addresses, 192.168.21.254 undergoes the
normal deterministic IP allocation algorithm.

Signed-off-by: Volker Lendecke 

add home_nodes
Reviewed-by: Ralph Boehme 

Autobuild-User(master): Volker Lendecke 
Autobuild-Date(master): Tue Oct 10 14:17:19 UTC 2023 on atb-devel-224