Page History

paramMappings:tosca.datatypes.asd.paramMappings:
    version: 0.1
    derived_from: tosca.datatypes.Root  
    description: "Describes the datatype for parameter mapping"
    properties:
      loadbalancerIPloadbalancer_IP:
        description: >
              When present, this attribute specifies the name of the deployment 
              artifact input parameter through which the orchestrator can 
              configure the loadbalancerIP parameter of the K8s service 
              or ingress controller that the ExtCpdextCpdData represents.
        required: false
        typeNote: string
The format of the Content strings externalIPs:
is specific for each different 
   description: >
          orchestration templating technology used When(Helm, presentTeraform, this attribute specifies the name of the deployment 
etc.). 
              Currently only a format for use with artifactHelm input parameter through which the orchestrator cancharts is suggested:
              "<helmchartname>:[<subchartname>.]^(0..N)[<parentparamname>.]^(0..N)<paramname>".  
              configureWhether the extermalIPsoptional parameterparts of the K8sformat serviceare orpresent ingressdepends 
on how the 
           controller, or the podparameter networkis interface annotation, that thedeclared in the helm chart. An example is: 
              ExtCpd represents."chartName:subChart1.subChart2.subChart3.Parent1.Parent2.Parent3.LBIP". 
        required: false
        type: liststring
        entryexternal_schemaIPs:
           typedescription: string>
       nadName: 
        description: >
              Specifies, for an ExtCpd respesenting a secondary network interface,
When present, this attribute specifies the name of the deployment 
              artifact input parameter through which  the name(s) of the NetworkAttachmentDefinitions the orchestrator has
              created as base for the network interface the ExtCpd represents. 
        required: false
        type: list
orchestrator can 
              configure the extermalIPs parameter of the K8s service or ingress 
              controller, or  entry_schema:
  the pod network interface annotation, that the 
         type: string
      nadNamespace:extCpdData represents.
        description:  >
       Note:  The  format  of Specifies,the forContent anstrings asdExtCpdis respesentingspecific afor secondaryeach networkdifferent interface,
              theorchestration namespacetemplating wheretechnology theused NetworkAttachmentDefinitions (NADs) are located.Helm, Teraform, etc.). 
              AttributeCurrently mayonly bea omittedformat iffor theuse namespacewith isHelm samecharts as the application is suggested:
              "<helmchartname>:[<subchartname>.]^(0..N)[<parentparamname>.]^(0..N)<paramname>".  
        namespace.
        required: Whether false
the optional  parts  of  the type:format string 

enhancedClusterCapabilities:
    version: 0.1are present depends on how the 
    derived_from: tosca.datatypes.Root 
    description: "Describes the datatype for parameter mapping"
is declared in the properties:
helm chart.  An   minKernelVersion:
        descriptionexample is: >
               Describes the minimal required Kernel version, e.g. 4.15.0"chartName:subChart1.subChart2.subChart3.Parent1.Parent2.Parent3.extIP". 
        required: false
      Coded as displayed by linux command uname –rtype: list
        requiredentry_schema:
 true
          type: string  
      requiredKernelModulesnad_names: 
        description: >
 
             RequiredSpecifies, kernelfor modulesan areextCpdData codedrespesenting asa listedsecondary by linux lsmod command, network interface,
             e.g. ip6_tables, cryptd, nf_nat etc.​ 
        required: false the name(s) of the deployment artifact input parameter(s) through which 
        type: list
     the orchestrator can provide  entry_schema:
    the names of the network attachment 
          type: string 
      conflictingKernelModules:
        description: > 
             Kernel modules, which must not be present in the target environmentdefinitions (NADs) the orchestrator has created as base for the network 
              interface the extCpdData represents. 
             The kernelNote modules1: areWhen codedthe asextCpdData listedrepresent by linux lsmod command, a networkRedundant/mated-pair of 
             e.g., ip6_tables, cryptd, nf_nat etc. 
         sriov interfaces, there are references to 2 or 3 related NADs needed 
     Example: Linux kernel SCTP module, which would conflict with useto ofbe 
passed, while for other interface types only one NAD reference 
   proprietary user space SCTP stack provided by the application.​ 
   is  needed  to required:be falsepassed.
        type: list
     Note   entry_schema2:
 The format of the Content strings is specific for each different 
  type: string   
      requiredCustomResources:
     orchestration templating technology description: >               
used (Helm, Teraform, etc.). 
              Currently only a Listformat thefor customuse resourcewith kindsHelm requiredcharts tois besuggested:
 supported  in  the  target  
     "<helmchartname>:[<subchartname>.]^(0..N)[<parentparamname>.]^(0..N)<paramname>".  
              Whether environment.the Theoptional listparts shallof include those custom resource kinds whichthe format are present depends on how the 
            are not deliveredparameter withis the application.			 
        required: falsedeclared in the helm chart. An example is: 
        type: list
     chartName:"subChart1.subChart2.subChart3.Parent1.Parent2.Parent3.nadName".
   entry_schema:
           Note 3: A type: tosca.datatypes.asd.customResourceRequirement
      clusterLabels:
        description: > 
             This attribute allows to associate arbitrary labels to clusters.
      direct attached (passthrough) network interface, such as an sriov 
              interface, attaches to a network via only one of the two switch planes 
       These can indicate special infrastructure capabilities (e.g., NW acceleration,  in the infrastructure.
             GPU compute, etc.). The intent of these labels is to serve as a set of When using a direct attached network interface one therefore commonly in a 
             values thatpod canuses helpa inmated applicationpair placementof decisions.sriov 
network  attachments,  where  each  interface  
   clusterLabels follow the Kubernetes label key-value-nomenclature 
      attaches same network but via   (https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/). 
different switchplane.
              ItThe isapplication recommendeduses thatthe labelsmated followpair aof standardizednetwork meaning e.g. for node 
interfaces as a single 
              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.logical “swith-path-redundant” network interface – and this is represented 
              by a single extCpdData. 
              Also there is a case where a third “bond” attachment interface is used in 
              the pod, bonding the two direct interfaces so that the application do not 
              need to handle the redundancy issues – application just uses the bond interface.
              In this case, all three attachments are together making up a logical 
              “switch-path-redundant” network interface represented by a single extCpdData. 
              When three NADs are used in the extCpdData the NAD implementing the bond attachment 
              interface is provided through the parameter indicated in the third place in 
              the nadNames attribute.
        required: false
        type: list
        entry_schema:
           type: string
      nad_namespace: 
        description: >
              Specifies, for an extCpdData respesenting a secondary network interface,
              the name of the deployment artifact input parameter through which the orchestrator 
              can provide the namespace where the NetworkAttachmentDefinitions (NADs) are located.
              Attribute may be omitted if the namespace is same as the application 
              namespace.
              Note: The format of the Content strings is specific for each different 
              orchestration templating technology used (Helm, Teraform, etc.). 
              Currently only a format for use with Helm charts is suggested:
              "<helmchartname>:[<subchartname>.]^(0..N)[<parentparamname>.]^(0..N)<paramname>".  
              Whether the optional parts of the format are present depends on how the 
              parameter is declared in the helm chart. An example is: 
              "chartName:subChart1.subChart2.subChart3.Parent1.Parent2.Parent3.NameSpace". 
        required: false
        type: string