Maniphest T192032

Enable `scap log` on deployment-* servers
Open, LowestPublic
Actions

Assigned To

None

Authored By

	MarcoAurelio
	Apr 11 2018, 9:49 PM

Description

If I understand correctly there's a scap log functionality so you can send messages to the SAL directly through the bash window without the need to go to the IRC channel and !log them. I find this does not work for the deployment-* servers though. Is is possible to enable it? It should log to the RelEng-SAL page on Wikitech. Thanks!

Sample
(maybe I am not doing it right)

maurelio@deployment-tin:~$ scap log -v test
21:55:03 test

but no !log message was triggered - there's no logmsgbot on -releng

Event Timeline

MarcoAurelio created this task.Apr 11 2018, 9:49 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 11 2018, 9:49 PM

MarcoAurelio updated the task description. (Show Details)Apr 11 2018, 9:56 PM

Yeah, we could do that, by setting up an instance (or just applying the relevant class to deployment-tin). But then we probably want to make the scap-scripts (those run every ten minutes) not trigger the usual "scap started" and "scap ended"/"scap aborted"/... messages. There's a full scap on beta every 10 minutes - we don't want an extra message in -releng every five minutes. If we can convince scap to not log stuff for the auto update, no objections.

EddieGP moved this task from To Triage to Backlog on the Beta-Cluster-Infrastructure board.Apr 13 2018, 8:01 AM

EddieGP triaged this task as Lowest priority.May 10 2018, 11:21 AM

thcipriani moved this task from Needs triage to Services improvements on the Scap board.Jul 11 2018, 12:23 AM

Enable `scap log` on deployment-* serversOpen, LowestPublicActions

Description

Event Timeline

Enable `scap log` on deployment-* servers
Open, LowestPublic
Actions