Page History

enhancedClusterCapabilities:
    version: 0.1
    derived_from: tosca.datatypes.Root 
    description: "Describes the datatype for parameter mapping"
    properties:
      minKernelVersion:
        description: "Describes the minimal required Kernel version, e.g. 4.15.0. Coded as displayed by linux command uname –r"
        required: true
        type: string  
      requiredKernelModules:
        description: > 
             Required kernel modules are coded as listed by linux lsmod command, e.g. ip6_tables, cryptd, nf_nat etc.​ 
        required: false
        type: list
        entry_schema:
              type: string 
      conflictingKernelModules:
        description: > 
             Kernel modules, which must not be present in the target environment. 
             The kernel modules are coded as listed by linux lsmod command, e.g. ip6_tables, cryptd, nf_nat etc. 
             Example: Linux kernel SCTP module, which would conflict with use of proprietary user space 
             SCTP stack provided by the application.​ 
        required: false
        type: list
        entry_schema:
              type: string   
      requiredCustomResources:
        description: >               
            List the custom resource kinds required to be supported in the target environment. 
            The list shall include those custom resource kinds which are not delivered with the application.			 
        required: false
        type: list
        entry_schema:
              type: tosca.datatypes.asd.customResourceRequirement
      clusterLabels:
        description: > 
             This attribute allows to associate arbitrary labels to clusters.
             These can indicate special infrastructure capabilities (e.g., NW acceleration, GPGPUGPU compute, etc.). 
             The intent of these labels is to serve as a set of values that can help in application placement decisions. 
             clusterLabels follow the Kubernetes label  This can be specified with the attribute 
key-value-nomenclature (https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/). 
             It is recommended that labels follow a -m: Mandatory, means deployment is not attempted if such support is not available in the target system
              -p: As preference - it means orchestrator will try to select a system with specific requirements,standardized meaning e.g. for node features (https://kubernetes-sigs.github.io/node-feature-discovery/v0.9/get-started/features.html#table-of-contents)
             or are mutually agreed between ASD supplier and operators.
             Example: 
             ClusterLabels
     but if not found it will attempt deployment in a system not having such HW.  
 - feature.node.kubernetes.io/cpu-cpuid.AESNI: true                
        required: false
        type: list
        entry_schema:
              type: string  
      requiredPodAnnotations:
        description: > 
             Annotations required to be supported.
             Example that list requirement for Kubernetes cluster infrastructure support for the Multus network attachment annotations:
             requiredPodAnnotations: {"k8s.v1.cncf.io/networks", ... } 
        required: false
        type: list
        entry_schema:
              type: string