[INSTRM-593] Run STS service logger at non-Subaru sites Created: 11/Jan/19  Updated: 25/Feb/22  Resolved: 25/Feb/22

Status: Done
Project: Instrument control development
Component/s: ics_alertsActor
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: cloomis Assignee: arnaud.lefur
Resolution: Done Votes: 0
Labels: SPS
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to INSTRM-698 Run STS server at LAM Done
relates to INSTRM-621 Run real STS server at JHU Won't Fix
Story Points: 2
Sprint: 2019 B, 2019 C, SM1-2019 K

 Description   

Yoshida, Hiroshige has provided a simple STS server program, which simply receives and parses the traffic from the STS client part of the alertsActor. We should run that when not at Subaru, and have it log the traffic from the alertsActor. [Stretch goal: act on the alerts/glue this to the LAM jabberBot. Other ticket.]



 Comments   
Comment by hassan [ 15/Feb/19 ]

Craig expects to start work on this on the 3rd week of Feb.

Comment by hassan [ 28/Feb/19 ]

This is an H4RG related ticket. Delayed until ADC work is finished.

Comment by hassan [ 16/Jul/19 ]

Covered completely by INSTRM-621 and INSTRM-698?

Comment by hassan [ 18/Jul/19 ]

cloomis added simple STS server STSboard.py to ics_alertsActor (commit 0f112b6b).

Comment by hassan [ 18/Jul/19 ]

arnaud.lefur to verify that implementation is acceptable before closing.

Comment by hassan [ 25/Jul/19 ]

Yoshida, Hiroshige: no need to implement this to validate whole system.

Comment by arnaud.lefur [ 25/Feb/22 ]

JHU and LAM has their own mechanism.

Generated at Sat Feb 10 16:26:38 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.