#260 Closed-loop control flag

[Björn Andersen]

Introduce a closed-loop flag that has a relation to a (set of) Metrics to convey the information that these are under some kind of automated control (local or remote) and may therefore change frequently.

This does not imply any locking mechanism for related operations! See also: [p11073-10703:#2]

[Martin]

FWIW: take 10101 nomencalture code 3::6286 into account.

[Björn Andersen]

@d-gregorczyk and @b-andersen: We could just add an extension to the Abstract(Metric)State that has a coded value with this code. That would be much less overhead than a second related metric.

@martinuro: Do we need this in MPKP?

[Stefan Schlichting]

Please check how this ticket relates to the DerivationMethod attribute of metrics.

[Björn Andersen]

They are probably related, but our suggestion pertains to the state rather than to the descriptor.

[Björn Andersen]

An extension with the coded value still seems to be our best idea. Should we include that in the MPKP?

[Björn Andersen]

Ticket moved from /p/opensdc/p11073-10701/5/

Can't be converted:

• _draft:
• _requirement:
• _clause:
• _milestone:

[Björn Andersen]

Needs to be solved in BICEPS due to the problem described in [#212]. Possible solutions include an "ActualDerivationMethod" in the state, because the descriptor attribute is insufficient to address the issue.