T0 request status Tier0Feeder

[This wiki is a work in progress]

This wiki is meant to clarify how the T0 workflow request status transition happen and what is their meaning.

AnalyticsDataCollector

Here is the logic (part of it) deciding in which state workflows will show up in the T0 WMStats: https://github.com/dmwm/WMCore/blob/master/src/python/WMComponent/AnalyticsDataCollector/Plugins/Tier0Plugin.py#L23

so it's AnalyticsDataCollector component which does the transition of a workflow status from XXX to either [Merge, Processing Done, AlcaSkim, Harvesting].

Tier0Feeder

This component is actually creating T0 workflows, thus adding workflows with the status new in the system. It's also responsible for marking workflows as injected, such that fileset/subscriptions and the workflow can move all the way to archived, eventually. Here is a reference to that code markWorkflowsInjectedDAO

TaskArchiver

This component is responsible for marking subscriptions as done and then moving the workflow status to completed

CleanCouchPoller

And this works the same way as it does for central production, besides the request status which is looked up. In the T0 agent, this component looks for completed workflows and if possible, move them to normal-archived. For central production, it looks for workflows in the announced status and if possible, move the workflow to normal-archived.