2:35 p.m.
New branch 'review' available with the following commits:
commit 1b772c431669971119f8fb7eb5e906fe8b0ece48
Author: David Teigland <teigland(a)redhat.com>
Date: Thu Jun 19 10:51:54 2014 -0500
sanlock: fix get_hosts off by one
When a host_id is specified, the information for
host_id+1 is returned.
Signed-off-by: David Teigland <teigland(a)redhat.com>
commit 153a0e2a0ba377f471455aad803f648556f8f06e
Author: David Teigland <teigland(a)redhat.com>
Date: Thu Jun 5 15:38:30 2014 -0500
sanlock: set an event for all hosts in the bitmap
Signed-off-by: David Teigland <teigland(a)redhat.com>
commit 32f22cf728955bf4101752b515f712615a79e267
Author: David Teigland <teigland(a)redhat.com>
Date: Fri May 30 15:06:00 2014 -0500
reset: daemon and program for resetting hosts
The sanlk_resetd daemon gets events from specified lockspaces.
Events are defined to cause the sanlk_resetd to:
- use wdmd/watchdog to reset the host (event 1)
- use /proc/sysrq-trigger to reboot the host (event 4)
The sanlk_resetd daemon can be used alone, and events passed
to it from another host by:
sanlock client set_event -s lockspace_name -i host_id -e 1
The sanlk_reset program can also be used to communicate with
sanlk_resetd on another host. It will set the event(s), then
monitor the host status until the target host is dead.
Signed-off-by: David Teigland <teigland(a)redhat.com>
commit 77c93f9ee653be0d6b9d2097ca34a4ecd2993911
Author: David Teigland <teigland(a)redhat.com>
Date: Tue May 27 15:16:00 2014 -0500
sanlock: lockspace host events
Hosts can set/get events between each other using a common lockspace.
. set_event takes two opaque 64 bit values ("event" and "data"),
and
a target host_id with optional host generation.
. reg_event creates an fd that a program can use in poll(2), and
. get_event on this fd returns the event values that have been set
along with the source host_id/generation.
. end_event releases the registered fd.
Each set_event call replaces generation/event/data values from the
previous set_event call, but host_id's from each are maintained.
set_event can be used to send the same event/data values to multiple
hosts at once using multiple set_event calls (generation is not
applicable in this case.)
set_event with different values within the same window of time can
result in the earlier target host(s) seeing later values not intended
for them, and missing the earlier values.
Event values are passed through fields in the lockspace delta leases.
Event notification is done via the host_id bitmaps in lockspace delta
leases. Setting an event (or making a resource request) for a target host
results in the target host's bit being set in the sending host's bitmap.
The bit remains set for set_bitmap_seconds (60 sec with 10 sec io
timeout.) After this, the bit is cleared and the target host will no
longer be notified. The target host will typically generate three events
for each set_event, once from each delta lease renewal (every 20 seconds)
over the course of the set_bitmap_seconds.
Signed-off-by: David Teigland <teigland(a)redhat.com>
commit 93885cbfc6271ecb5007601369ad29cee3df6b99
Author: David Teigland <teigland(a)redhat.com>
Date: Fri Apr 11 14:10:25 2014 -0500
sanlock: shutdown reply
A wait option (-w 1) can be added to sanlock shutdown.
The shutdown command will wait for a result from the
daemon indicating success (exiting), or failure (not
exiting because lockspaces exist).
Signed-off-by: David Teigland <teigland(a)redhat.com>