Open bb233 opened 5 years ago
I think it is a good idea. The queue names, however, I think we can leave them as is. At some point, we will need to remove the "development" in the queue names and we should do that together.
OK. I'll add a JIRA ticket for this.
New proposed queue names (may have to put production after cular if Greg's team needs it)
QUEUE_INGEST = 'cular_ingest' QUEUE_INGEST_IN_PROGRESS = 'cular_ingest_in_progress'
QUEUE_TRANSFER_S3 = 'cular_transfer_s3' QUEUE_TRANSFER_S3_IN_PROGRESS = 'cular_transfer_s3_in_progress' QUEUE_TRANSFER_SFS = 'cular_transfer_sfs' QUEUE_TRANSFER_SFS_IN_PROGRESS = 'cular_transfer_sfs_in_progress'
QUEUE_INGEST_FIXITY_S3 = 'cular_ingest_fixity_s3' QUEUE_INGEST_FIXITY_S3_IN_PROGRESS = 'cular_ingest_fixity_s3_in_progress' QUEUE_INGEST_FIXITY_SFS = 'cular_ingest_fixity_sfs' QUEUE_INGEST_FIXITY_SFS_IN_PROGRESS = 'cular_ingest_fixity_sfs_in_progress' QUEUE_INGEST_FIXITY_COMPARE = 'cular_ingest_fixity_comparison' QUEUE_INGEST_FIXITY_COMPARE_IN_PROGRESS = 'cular_ingest_fixity_comparison_in_progress'
QUEUE_PERIODIC_FIXITY_S3 = 'cular_periodic_fixity_s3' QUEUE_PERIODIC_FIXITY_S3_IN_PROGRESS = 'cular_periodic_fixity_s3_in_progress' QUEUE_PERIODIC_FIXITY_SFS = 'cular_periodic_fixity_sfs' QUEUE_PERIODIC_FIXITY_SFS_IN_PROGRESS = 'cular_periodic_fixity_sfs_in_progress' QUEUE_PERIODIC_FIXITY_COMPARE = 'cular_periodic_fixity_comparison' QUEUE_PERIODIC_FIXITY_COMPARE_IN_PROGRESS = 'cular_periodic_fixity_comparison_in_progress'
QUEUE_ERROR = 'cular_error' QUEUE_COMPLETE = 'cular_done'
For each service, there are a series of files, workers, environment variables, queues, and executables associated with them. For instance, for the service to calculate SFS fixity, we have:
SFSFixityGenerator
fixity_sfs.log
asi_sfs_fixity_*
cular_development_fixity_sfs*
and the associated ruby constantsQueues::QUEUE_FIXITY_SFS*
fixity_check_sfs.service
and associated scriptfixity_check_sfs.script
While there appears to be a preference in this case (and with the other services) to refer to it as "sfs_fixity", this is mostly internal; the externally-facing usages use a mix of
sfs_fixity_check
,fixity_sfs
,sfs_fixity
, andfixity_check_sfs
instead.This same pattern of inconsistent names exists across 5 of the 6 services, the single-word named "ingest" server excepted.
I propose that one name for each service be chosen, and the code modified to be consistent with that.
In this example, by choosing
sfs_fixity
as the name for this service, we would rename the log file tosfs_fixity.log
, the SQS queues tocular_development_sqs_fixity*
andQueues::QUEUE_SFS_FIXITY*
, and the systemd service tosfs_fixity.service
(or perhapsasi_sfs_fixity.service
so the services are grouped together insystemctl status
).