Adapt DIRAC consumers to the binary status model(?)

[aldbr]

Description

Adapt the ResourceStatus and SiteStatus singletons, together with their callers, to work with the simplified binary status served by diracx (see phase 1, DIRACGrid/diracx#837).

Before starting, confirm that the richer "information layer" (Active, Probing, Degraded, …) used today is not actually relied upon by any consumer and can be safely collapsed into the binary allowed/banned model. Any place that genuinely needs more than binary information should be called out explicitly so we can decide whether to adapt the consumer or to extend the model.

Scope

• Singleton-level changes in ResourceStatus and SiteStatus so that their public API keeps working when the underlying data is binary.
• Adjustments in callers that currently display or filter by raw status strings (e.g. SiteStatus.getSites(siteState=...)).
• Keeping the singleton cache format compatible with the binary data.

Reference

• Phase 1 main issue: [RSS Phase 1] Read-only resource status via CacheableSource diracx#836
• Phase 1 data models: RSS data models (SQLAlchemy + Pydantic) diracx#837
• Phase 2 discussion: #790 comment

Acceptance criteria

• Confirmation (with examples) that the binary model is sufficient for all current consumers, or an explicit list of consumers that need more.
• ResourceStatus and SiteStatus singletons keep their public API while operating on binary data.
• Callers that filter/display raw status strings are updated.
• Existing DIRAC unit tests still pass; new tests cover the adapted behavior where relevant.
• No change to the legacy RPC service or its DB schema.

[aldbr]

@HeloiseJoffe, I ran a small analysis to guide you (also please double check just to make sure everything is fine):

It looks like most of the code can stay as is:

Consumer	File:line	Predicate
StorageElement.getStatus (real SE gate)	Resources/Storage/StorageElement.py:552-564	status not in ("Active","Degraded") → unusable
SiteDirector CE mask	WorkloadManagementSystem/Agent/SiteDirector.py:227	["all"] in ("Active","Degraded")
SiteStatus.getUsableSites	ResourceStatusSystem/Client/SiteStatus.py:149	status in ("Active","Degraded")
OperationHandlerBase.rssSEStatus	RequestManagementSystem/private/OperationHandlerBase.py:254	status != "Banned"

The "Degraded" branch simply goes dead (never emitted), which is harmless here. It can stay as is.

Then we have this in DataManagementSystem/private/FTS3Utilities.py:194: the only consumer whose behavior changes under binary:

if result[ftsServer]["all"] == "Active":
    return S_OK(True)
return S_OK(False)

Today a Degraded FTS server ("Degraded" == "Active" is False) is excluded. Under binary, it would be included. We should potentially accept it as we consider Degraded as Active but we can ask during ddev though.

A few more things to adjust:

• SiteStatus.getSites (ResourceStatusSystem/Client/SiteStatus.py:~197) should return Active if Degraded is passed and Banned if Probing is passed I think:

# before
allowedStateList = ["Active", "Banned", "Degraded", "Probing", "Error", "Unknown"]

# after: binary vocabulary + back-compat aliases so old callers don't silently get []
allowedStateList = ["Active", "Banned"]
_LEGACY_ALIASES = {"Degraded": "Active", "Probing": "Banned", "Error": "Banned", "Unknown": "Banned"}
siteState = _LEGACY_ALIASES.get(siteState, siteState)
if siteState not in allowedStateList:
    return S_ERROR(errno.EINVAL, "Not a valid status, parameter rejected")

• Same for DiracAdmin.getBannedSites (Interfaces/API/DiracAdmin.py:119-127) merges Banned+Probing; the Probing query is now always [] (Probing→Banned already covers it):

# before
bannedSites = self.sitestatus.getSites(siteState="Banned")
if not bannedSites["OK"]:
    return bannedSites
probingSites = self.sitestatus.getSites(siteState="Probing")
if not probingSites["OK"]:
    return probingSites
mergedList = sorted(bannedSites["Value"] + probingSites["Value"])

# after
bannedSites = self.sitestatus.getSites(siteState="Banned")
if not bannedSites["OK"]:
    return bannedSites
# Probing sites collapse into "Banned" under the binary model.
mergedList = sorted(bannedSites["Value"])

And finally there are a few display-only functions to change:

• dirac-dms-show-se-status — prints raw ReadAccess/WriteAccess strings; Degradedbecomes Active, Probing/Error becomes Banned.
• JobDB WebApp site-mask summary (WorkloadManagementSystem/DB/JobDB.py:1093-1103) Degraded sites could now be labeled Active instead of NoMask.