hi,
while doing some testing of scheduling (Matterhorn 1.3.1) we ended up
with a weird problem where recordings scheduled on one capture agent
ended up with media recorded from a different one. this had me puzzled
for a while ;)
it seems that because one of our agents was named 'matterhorn-ca' and
another was named 'matterhorn-ca4', the 'matterhorn-ca' agent picked up
'matterhorn-ca4' scheduled recordings.
this is because of the way the scheduler REST endpoint works.
/recordings/calendars?agentid=matterhorn-ca
returns any scheduled recording for agents that BEGIN with
'matterhorn-ca' instead of those that are EXACTLY 'matterhorn-ca' and
therefore will also get schedules for 'matterhorn-ca1', 'matterhorn-ca2'
etc.
this testing is with epiphan capture devices so it may be that other
agents check to make sure that schedules returned by the scheduler REST
endpoint are actually for them? i guess this is a reasonably
straightforward fix on the epiphan devices (i'll take a look when i get
back from the christmas break), but should the service itself be fixed
to only return upcoming recordings for the exact device specified or is
this intended to behave as it does?
many thanks,
paul.
--
Paul Pettit
Multimedia Development
University of Sussex
+44 (0) 1273 87 3223
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
