Page History

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
     Note: The format type:of string
the Content strings is specific for externalIPs:
each different 
      description: >
        orchestration templating technology used   When present, this attribute specifies the name of the deployment 
(Helm, Teraform, etc.). 
              Currently only a format for use with artifactHelm inputcharts parameter through which the orchestrator can is suggested:
                   configure the extermalIPs parameter of the K8s service or ingress 
              controller, or the pod network interface annotation, that the 
   "<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 ExtCpd represents.
   chart. An example is: 
     required: false
        type: list"chartName:subChart1.subChart2.subChart3.Parent1.Parent2.Parent3.LBIP". 
        entry_schemarequired: false
           type: string
        nadNameexternal_IPs: 
        description: >
              Specifies, for an ExtCpd respesenting a secondary networkWhen interfacepresent,
 this attribute specifies the name of the deployment 
     the name(s) of the NetworkAttachmentDefinitions the orchestrator has
    artifact  input  parameter  through  which  createdthe asorchestrator basecan for
 the network interface the ExtCpd represents. 
        required: false
   configure  the  extermalIPs type:parameter list
of the K8s service or ingress   entry_schema:
           type: string
   controller,  or nadNamespace:the 
pod network interface annotation, that the 
  description: >
              Specifies, for an asdExtCpdextCpdData respesentingrepresents.
 a secondary network interface,
          Note: The format of the namespaceContent strings whereis thespecific NetworkAttachmentDefinitionsfor (NADs)each aredifferent located.
              Attributeorchestration maytemplating betechnology omittedused if the namespace is same as the application 
(Helm, Teraform, etc.). 
              Currently only a format for use namespace.
with  Helm  charts  is  requiredsuggested: false
         type:  string 

tosca.datatypes.asd.enhancedClusterCapabilities:
    version: 0.1
    derived_from: tosca.datatypes.Root 
    description: "Describes the datatype for parameter mapping"
    properties:
      minKernelVersion:
   "<helmchartname>:[<subchartname>.]^(0..N)[<parentparamname>.]^(0..N)<paramname>".  
              Whether the optional parts of the format are present depends on how the 
              parameter is description:declared >
in the helm chart. An example is: 
        Describes the minimal required Kernel version, e.g. 4.15.0 "chartName:subChart1.subChart2.subChart3.Parent1.Parent2.Parent3.extIP". 
        required: false
      Coded as displayedtype: bylist
 linux command uname –r
      entry_schema:
  required: 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: falsethe name(s) of the deployment artifact input parameter(s) through which 
        type: list
     the orchestrator can entry_schema:
provide the names of the network attachment 
       type: string 
      conflictingKernelModules:
  definitions (NADs) the orchestrator has created description: >as base for the network 
             Kernel modules, which must not be present ininterface the targetextCpdData environmentrepresents. 
             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     type: string   each different 
      requiredCustomResources:
        description: >  orchestration  templating  technology  used      (Helm, Teraform, etc.). 
            List the customCurrently resourceonly kindsa requiredformat tofor beuse supportedwith inHelm thecharts targetis suggested:
                 environment. The list shall include those custom resource kinds which 
            are not delivered with the application.			 
        required: false
        type: list
   "<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: 
           entry_schema:
   chartName:"subChart1.subChart2.subChart3.Parent1.Parent2.Parent3.nadName".
              Note type3: A direct attached (passthrough) network interface, such as an sriov 
              interface, attaches to a network via only one of the two switch planes 
              in the infrastructure.
              When using a direct attached network interface one therefore commonly in a 
              pod uses a mated pair of sriov network attachments, where each interface 
              attaches same network but via different switchplane.
              The application uses the mated pair of network interfaces as a single 
              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