X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/c110a9aeed738f1b2dd456950a8ee3018cd97fed..fb27923f7ce22eddde0852d24d6c94323de41330:/sdk/cwl/arvados_cwl/arv-cwl-schema-v1.2.yml?ds=sidebyside diff --git a/sdk/cwl/arvados_cwl/arv-cwl-schema-v1.2.yml b/sdk/cwl/arvados_cwl/arv-cwl-schema-v1.2.yml index e9f70bf1cf..86cd06effe 100644 --- a/sdk/cwl/arvados_cwl/arv-cwl-schema-v1.2.yml +++ b/sdk/cwl/arvados_cwl/arv-cwl-schema-v1.2.yml @@ -330,3 +330,74 @@ $graph: doc: | Maximum number of GPU devices to request. If not specified, same as `cudaDeviceCountMin`. + +- name: UsePreemptible + type: record + extends: cwl:ProcessRequirement + inVocab: false + doc: | + Specify a workflow step should opt-in or opt-out of using preemptible (spot) instances. + fields: + class: + type: string + doc: "Always 'arv:UsePreemptible" + jsonldPredicate: + _id: "@type" + _type: "@vocab" + usePreemptible: boolean + +- name: OutputCollectionProperties + type: record + extends: cwl:ProcessRequirement + inVocab: false + doc: | + Specify metadata properties that will be set on the output + collection associated with this workflow or step. + fields: + class: + type: string + doc: "Always 'arv:OutputCollectionProperties" + jsonldPredicate: + _id: "@type" + _type: "@vocab" + outputProperties: + type: PropertyDef[] + jsonldPredicate: + mapSubject: propertyName + mapPredicate: propertyValue + + +- name: KeepCacheType + type: enum + symbols: + - ram_cache + - disk_cache + doc: + - | + ram_cache: Keep blocks will be cached in RAM only. + - | + disk_cache: Keep blocks will be cached to disk and + memory-mapped. The disk cache leverages the kernel's virtual + memory system so "hot" data will generally still be kept in + RAM. + +- name: KeepCacheTypeRequirement + type: record + extends: cwl:ProcessRequirement + inVocab: false + doc: | + Choose keep cache strategy. + fields: + - name: class + type: string + doc: "'arv:KeepCacheTypeRequirement'" + jsonldPredicate: + _id: "@type" + _type: "@vocab" + - name: keepCacheType + type: KeepCacheType? + doc: | + Whether Keep blocks loaded by arv-mount should be kept in RAM + only or written to disk and memory-mapped. The disk cache + leverages the kernel's virtual memory system so "hot" data will + generally still be kept in RAM.