Workloads can consist of multiple running instances.

[fandreas]

draft-ietf-wimse-arch/draft-ietf-wimse-arch.md

Line 40 in 8234b6d

The increasing prevalence of cloud computing and micro service architectures has led to the rise of complex software functions being built and deployed as workloads, where a workload is defined as a running instance of software executing for a specific purpose. This document discusses an architecture for designing and standardizing protocols and payloads for conveying workload identity and security context information.

The current workload definition says it is defined as "a running instance of software....". I think this is overly restrictive - workloads can consist of one or more running instances of software.

[jsalowey]

I think this is accurate, but I'm not sure the difference would be meaningful. Is there are particular scenario that makes you want this clarification?

[fandreas]

The basic question is whether we always want to identify (and authorize) individual/specific workload instances, or whether there can be a set of workloads that have the same identity and associated authorizations. I believe the latter is important since we often run multiple instances of the same workload (and the specific instances come and go).

[jricher]

Perhaps we should be specific and pedantic about a workload software vs a workload instance