全部产品
Search
文档中心

:ALIYUN::Eflo::Vpd

更新时间:Jul 07, 2026

ALIYUN::Eflo::Vpd类型用于创建灵骏网段。

语法

{
  "Type": "ALIYUN::Eflo::Vpd",
  "Properties": {
    "Cidr": String,
    "VpdName": String,
    "ResourceGroupId": String,
    "Subnets": List,
    "SecondaryCidrBlocks": List,
    "Tags": List
  }
}

属性

属性名称

类型

必须

允许更新

描述

约束

Cidr

String

是

否

VPD 的 CIDR 网段。

建议使用 RFC 私有网段作为灵骏 CIDR 块,例如 10.0.0.0/8、172.16.0.0/12、192.168.0.0/16。在灵骏 CIDR 块相互连接或与 VPC 连接的场景下,请确保地址不冲突。* 您也可以使用除 100.64.0.0/10、224.0.0.0/4、127.0.0.0/8 或 169.254.0.0/16 及其子网之外的自定义 CIDR 块,作为 VPD 的主 IPv4 CIDR 块。

VpdName

String

是

是

灵骏 CIDR 块实例名称。

无

ResourceGroupId

String

否

是

资源组 ID。

无

SecondaryCidrBlocks

List

否

是

附加网段信息列表。

最多支持配置100个网段信息。

Subnets

List

否

否

灵骏子网信息列表。

更多信息,请参考Subnets属性。

Tags

List

否

是

VPD 的标签。

更多信息,请参考Tags属性。

Subnets语法

"Subnets": [
  {
    "SubnetName": String,
    "Type": String,
    "Cidr": String,
    "ZoneId": String,
    "RegionId": String
  }
]

Subnets属性

属性名称

类型

必须

允许更新

描述

约束

Cidr

String

否

否

子网网段。

子网的网段必须是所属灵骏网段的真子集,且掩码位数在 16~29 位之间,可提供 8~65536 个地址。

例如,灵骏网段为 192.168.0.0/16,其子网网段范围为 192.168.0.0/17 至 192.168.0.0/29。

- 每个子网网段的首尾三个 IP 地址由系统保留。

例如,子网的四个 IP 地址块为 192.168.1.0/24,保留地址为 192.168.1.0、192.168.1.253、192.168.1.254 和 192.168.1.255。

RegionId

String

否

否

地理位置。

无

SubnetName

String

否

否

灵骏子网实例名称。

无

Type

String

否

否

灵骏子网使用类型。

取值:

  • OOB

  • LB

  • 通用类型不填;

ZoneId

String

否

否

可用区。

无

Tags语法

"Tags": [
  {
    "Value": String,
    "Key": String
  }
]

Tags属性

属性名称

类型

必须

允许更新

描述

约束

Key

String

是

否

标签键。

无

Value

String

否

否

标签值。

无

返回值

Fn::GetAtt

  • ResourceGroupId:资源组ID。

  • Cidr:VPD 的 CIDR 网段。

  • SecondaryCidrBlocks:附加网段信息列表。

  • VpdId:VPD 的 ID。

  • CreateTime:资源的创建时间。

  • GmtModified:修改时间。

  • VpdName:灵骏 CIDR 块实例名称。

  • Tags:资源的标记。

示例

ROSTemplateFormatVersion: '2015-09-01'
Parameters:
  Cidr:
    Description:
      en: The CIDR block of the VPD. * We recommend that you use an RFC private endpoint
        as the Lingjun CIDR block, such as 10.0.0.0/8,172.16.0.0/12,192.168.0.0/16.
        In scenarios where the Doringjun CIDR block is connected to each other or
        where the Lingjun CIDR block is connected to a VPC, make sure that the addresses
        do not conflict with each other. * You can also use a custom CIDR block other
        than 100.64.0.0/10, 224.0.0.0/4, 127.0.0.0/8, or 169.254.0.0/16 and their
        subnets as the primary IPv4 CIDR block of the VPD.
    Required: true
    Type: String
  ResourceGroupId:
    AssociationProperty: ALIYUN::ECS::ResourceGroup::ResourceGroupId
    Description:
      en: 'System-defined parameter. Value: **ChangeResourceGroup**.'
    Required: false
    Type: String
  SecondaryCidrBlocks:
    AssociationProperty: List[Parameter]
    AssociationPropertyMetadata:
      Parameter:
        Description:
          en: Additional network segment.
        Required: true
        Type: String
    Description:
      en: List of additional network segment information.
    MaxLength: 100
    MinLength: 0
    Required: false
    Type: Json
  Subnets:
    AssociationProperty: List[Parameters]
    AssociationPropertyMetadata:
      Parameters:
        Cidr:
          Description:
            en: 'The Subnet segment.

              - The network segment of the subnet must be a proper subset of the network
              segment of Lingjun to which it belongs, and the mask must be between
              16 bits and 29 bits, which can provide 8~65536 addresses.

              For example, the network segment of the Lingjun network segment is 192.168.0.0/16,
              and the network segments of the subnets under the Lingjun network segment
              are 192.168.0.0/17 to 192.168.0.0/29.

              - The first and last three IP addresses of each subnet segment are reserved
              for the system.

              For example, the four IP address blocks of the subnet are 192.168.1.0/24,192.168.1.0,
              192.168.1.253, 192.168.1.254, and 192.168.1.255.'
          Required: false
          Type: String
        RegionId:
          Description:
            en: Geography.
          Required: false
          Type: String
        SubnetName:
          Description:
            en: Lingjun subnet instance name.
          Required: false
          Type: String
        Type:
          Description:
            en: 'Lingjun subnet usage type; Optional; Optional value:

              - **General type does not fill in * *;

              - **OOB**:OOB type

              - **LB**: LB type.'
          Required: false
          Type: String
        ZoneId:
          AssociationProperty: ZoneId
          Description:
            en: Availability Zone.
          Required: false
          Type: String
    Description:
      en: Lingjun subnet information List.
    MaxLength: 100
    MinLength: 0
    Required: false
    Type: Json
  Tags:
    AssociationProperty: List[Parameters]
    AssociationPropertyMetadata:
      ListMetadata:
        Order:
          - Key
          - Value
      Parameters:
        Key:
          Required: true
          Type: String
        Value:
          Required: false
          Type: String
    Description:
      en: Tags of vpd.
    MaxLength: 20
    Required: false
    Type: Json
  VpdName:
    Description:
      en: Lingjun CIDR block instance name.
    Required: true
    Type: String
Resources:
  ExtensionResource:
    Properties:
      Cidr:
        Ref: Cidr
      ResourceGroupId:
        Ref: ResourceGroupId
      SecondaryCidrBlocks:
        Ref: SecondaryCidrBlocks
      Subnets:
        Ref: Subnets
      Tags:
        Ref: Tags
      VpdName:
        Ref: VpdName
    Type: ALIYUN::Eflo::Vpd
Outputs:
  Cidr:
    Description: The CIDR block of the VPD. * We recommend that you use an RFC private
      endpoint as the Lingjun CIDR block, such as 10.0.0.0/8,172.16.0.0/12,192.168.0.0/16.
      In scenarios where the Doringjun CIDR block is connected to each other or where
      the Lingjun CIDR block is connected to a VPC, make sure that the addresses do
      not conflict with each other. * You can also use a custom CIDR block other than
      100.64.0.0/10, 224.0.0.0/4, 127.0.0.0/8, or 169.254.0.0/16 and their subnets
      as the primary IPv4 CIDR block of the VPD.
    Value:
      Fn::GetAtt:
        - ExtensionResource
        - Cidr
  CreateTime:
    Description: The creation time of the resource.
    Value:
      Fn::GetAtt:
        - ExtensionResource
        - CreateTime
  GmtModified:
    Description: Modification time.
    Value:
      Fn::GetAtt:
        - ExtensionResource
        - GmtModified
  ResourceGroupId:
    Description: 'System-defined parameter. Value: **ChangeResourceGroup**.'
    Value:
      Fn::GetAtt:
        - ExtensionResource
        - ResourceGroupId
  SecondaryCidrBlocks:
    Description: List of additional network segment information.
    Value:
      Fn::GetAtt:
        - ExtensionResource
        - SecondaryCidrBlocks
  Tags:
    Description: The tag of the resource.
    Value:
      Fn::GetAtt:
        - ExtensionResource
        - Tags
  VpdId:
    Description: The ID of the VPD.
    Value:
      Fn::GetAtt:
        - ExtensionResource
        - VpdId
  VpdName:
    Description: Lingjun CIDR block instance name.
    Value:
      Fn::GetAtt:
        - ExtensionResource
        - VpdName
                        
{
  "ROSTemplateFormatVersion": "2015-09-01",
  "Parameters": {
    "Subnets": {
      "AssociationPropertyMetadata": {
        "Parameters": {
          "SubnetName": {
            "Type": "String",
            "Description": {
              "en": "Lingjun subnet instance name."
            },
            "Required": false
          },
          "Type": {
            "Type": "String",
            "Description": {
              "en": "Lingjun subnet usage type; Optional; Optional value:\n- **General type does not fill in * *;\n- **OOB**:OOB type\n- **LB**: LB type."
            },
            "Required": false
          },
          "Cidr": {
            "Type": "String",
            "Description": {
              "en": "The Subnet segment.\n- The network segment of the subnet must be a proper subset of the network segment of Lingjun to which it belongs, and the mask must be between 16 bits and 29 bits, which can provide 8~65536 addresses.\nFor example, the network segment of the Lingjun network segment is 192.168.0.0/16, and the network segments of the subnets under the Lingjun network segment are 192.168.0.0/17 to 192.168.0.0/29.\n- The first and last three IP addresses of each subnet segment are reserved for the system.\nFor example, the four IP address blocks of the subnet are 192.168.1.0/24,192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255."
            },
            "Required": false
          },
          "ZoneId": {
            "Type": "String",
            "AssociationProperty": "ZoneId",
            "Description": {
              "en": "Availability Zone."
            },
            "Required": false
          },
          "RegionId": {
            "Type": "String",
            "Description": {
              "en": "Geography."
            },
            "Required": false
          }
        }
      },
      "Type": "Json",
      "AssociationProperty": "List[Parameters]",
      "Description": {
        "en": "Lingjun subnet information List."
      },
      "Required": false,
      "MinLength": 0,
      "MaxLength": 100
    },
    "ResourceGroupId": {
      "Type": "String",
      "AssociationProperty": "ALIYUN::ECS::ResourceGroup::ResourceGroupId",
      "Description": {
        "en": "System-defined parameter. Value: **ChangeResourceGroup**."
      },
      "Required": false
    },
    "Cidr": {
      "Type": "String",
      "Description": {
        "en": "The CIDR block of the VPD. * We recommend that you use an RFC private endpoint as the Lingjun CIDR block, such as 10.0.0.0/8,172.16.0.0/12,192.168.0.0/16. In scenarios where the Doringjun CIDR block is connected to each other or where the Lingjun CIDR block is connected to a VPC, make sure that the addresses do not conflict with each other. * You can also use a custom CIDR block other than 100.64.0.0/10, 224.0.0.0/4, 127.0.0.0/8, or 169.254.0.0/16 and their subnets as the primary IPv4 CIDR block of the VPD."
      },
      "Required": true
    },
    "SecondaryCidrBlocks": {
      "AssociationPropertyMetadata": {
        "Parameter": {
          "Type": "String",
          "Description": {
            "en": "Additional network segment."
          },
          "Required": true
        }
      },
      "Type": "Json",
      "AssociationProperty": "List[Parameter]",
      "Description": {
        "en": "List of additional network segment information."
      },
      "Required": false,
      "MinLength": 0,
      "MaxLength": 100
    },
    "VpdName": {
      "Type": "String",
      "Description": {
        "en": "Lingjun CIDR block instance name."
      },
      "Required": true
    },
    "Tags": {
      "AssociationPropertyMetadata": {
        "Parameters": {
          "Value": {
            "Type": "String",
            "Required": false
          },
          "Key": {
            "Type": "String",
            "Required": true
          }
        },
        "ListMetadata": {
          "Order": [
            "Key",
            "Value"
          ]
        }
      },
      "Type": "Json",
      "AssociationProperty": "List[Parameters]",
      "Description": {
        "en": "Tags of vpd."
      },
      "Required": false,
      "MaxLength": 20
    }
  },
  "Resources": {
    "ExtensionResource": {
      "Type": "ALIYUN::Eflo::Vpd",
      "Properties": {
        "Subnets": {
          "Ref": "Subnets"
        },
        "ResourceGroupId": {
          "Ref": "ResourceGroupId"
        },
        "Cidr": {
          "Ref": "Cidr"
        },
        "SecondaryCidrBlocks": {
          "Ref": "SecondaryCidrBlocks"
        },
        "VpdName": {
          "Ref": "VpdName"
        },
        "Tags": {
          "Ref": "Tags"
        }
      }
    }
  },
  "Outputs": {
    "ResourceGroupId": {
      "Description": "System-defined parameter. Value: **ChangeResourceGroup**.",
      "Value": {
        "Fn::GetAtt": [
          "ExtensionResource",
          "ResourceGroupId"
        ]
      }
    },
    "Cidr": {
      "Description": "The CIDR block of the VPD. * We recommend that you use an RFC private endpoint as the Lingjun CIDR block, such as 10.0.0.0/8,172.16.0.0/12,192.168.0.0/16. In scenarios where the Doringjun CIDR block is connected to each other or where the Lingjun CIDR block is connected to a VPC, make sure that the addresses do not conflict with each other. * You can also use a custom CIDR block other than 100.64.0.0/10, 224.0.0.0/4, 127.0.0.0/8, or 169.254.0.0/16 and their subnets as the primary IPv4 CIDR block of the VPD.",
      "Value": {
        "Fn::GetAtt": [
          "ExtensionResource",
          "Cidr"
        ]
      }
    },
    "SecondaryCidrBlocks": {
      "Description": "List of additional network segment information.",
      "Value": {
        "Fn::GetAtt": [
          "ExtensionResource",
          "SecondaryCidrBlocks"
        ]
      }
    },
    "VpdId": {
      "Description": "The ID of the VPD.",
      "Value": {
        "Fn::GetAtt": [
          "ExtensionResource",
          "VpdId"
        ]
      }
    },
    "CreateTime": {
      "Description": "The creation time of the resource.",
      "Value": {
        "Fn::GetAtt": [
          "ExtensionResource",
          "CreateTime"
        ]
      }
    },
    "GmtModified": {
      "Description": "Modification time.",
      "Value": {
        "Fn::GetAtt": [
          "ExtensionResource",
          "GmtModified"
        ]
      }
    },
    "VpdName": {
      "Description": "Lingjun CIDR block instance name.",
      "Value": {
        "Fn::GetAtt": [
          "ExtensionResource",
          "VpdName"
        ]
      }
    },
    "Tags": {
      "Description": "The tag of the resource.",
      "Value": {
        "Fn::GetAtt": [
          "ExtensionResource",
          "Tags"
        ]
      }
    }
  }
}