samba.git/ctdb/tests/simple, branch master

ctdb-tests: Add new "ctdb setreclock" test

2015-02-04T04:40:55+00:00

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs 

Autobuild-User(master): Amitay Isaacs 
Autobuild-Date(master): Wed Feb  4 05:40:55 CET 2015 on sn-devel-104

ctdb-tests: Try to handle IPv6 addresses for local daemons

2014-12-05T20:02:40+00:00

If CTDB_USE_IPV6 is set then use IPv6 addresses for nodes and public
IPs.  This can be useful for some simple tests.  However, the node
address actually needs to be on lo so that ctdbd can bind to the port
on that address, so they actually need to be added as root before
running tests, like this:

  for i in $(seq 1 10) ; do ip addr add "fc00:10::${i}/64" dev lo ; done

IPv4 127.0.0.0/8 addresses are somehow magic and only one needs to be
on lo so that many can be bound to.

Also change the IPv4 node addresses to be (slightly) more exotic.

For both IPv4 and IPv6, choose addresses that are compatible with
socket wrapper.

Signed-off-by: Martin Schwenke 
Signed-off-by: Amitay Isaacs  (socket wrapper fixes)
Reviewed-by: Amitay Isaacs 
Reviewed-by: Martin Schwenke  (socket wrapper fixes)

ctdb-tests: Extend regexp to match IPv6 addresses

2014-12-05T20:02:40+00:00

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs

ctdb-tests: Update integration tests to use ctdb -X

2014-12-05T20:02:40+00:00

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs

ctdb-logging: New option CTDB_LOGGING, remove CTDB_LOGFILE, CTDB_SYSLOG

2014-10-28T04:42:04+00:00

Remove --logfile and --syslog daemon options and replace with
--logging.

Modularise and clean up logging initialisation code.  The
initialisation API includes an app_name argument that is currently
unused - this will be used in extensions to the syslog backend.

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs

ctdb-logging: Remove debug levels DEBUG_ALERT and DEBUG_CRIT

2014-10-28T04:42:04+00:00

Internally map them to DEBUG_ERR to limit code churn.

This reduces the unwieldy number of debug levels used by CTDB.  ALERT
and CRIT aren't of much use as separate errors, since everything from
ERR up should always be logged.  In future just ERR can be used.

This also improves compatibility with Samba's debug.c system priority
mapping.

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs

ctdb-logging: Remove DEBUG_EMERG

2014-10-28T04:42:04+00:00

It isn't used and shouldn't be.  CTDB can't make the system unusable.

Update associated test to ensure that EMERG isn't attempted.  Actually
test all remaining debug levels and modernise the test a bit.

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs

ctdb-logging: Remove log ringbuffer

2014-10-06T10:34:32+00:00

As far as we know, nobody uses this and it just complicates the
logging subsystem.

Remove all ringbuffer code and documentation.  Update the local
daemons startup code correspondingly.

Signed-off-by: Martin Schwenke 
Reviewed-by: Volker Lendecke

ctdb-tests: Clean up some tests where IP movement is checked

2014-09-23T06:06:12+00:00

Some of this implements logic that exists in functions.  Some of it is
overly complicated and potentially failure-prone.

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs

ctdb-tests: Remove dependency on log ringbuffer from missing IP test

2014-09-23T06:06:12+00:00

The log ringbuffer will probably be removed.  The test can be
implemented just as reliably by checking IP assignments using "ctdb
ip".

Update wait_until_ips_are_on_node() to print a more useful log
message.

Signed-off-by: Martin Schwenke 
Reviewed-by: Amitay Isaacs