云服务器内容精选
-
Metadata (OpenStack Metadata API) This API is used to query E CS metadata. URI /169.254.169.254/openstack/latest/meta_data.json Usage method Supports GET requests. Example To use cURL to view Linux ECS metadata, run the following command: curl http://169.254.169.254/openstack/latest/meta_data.json { "random_seed": "rEocCViRS+dNwlYdGIxJHUp+00poeUsAdBFkbPbYQTmpNwpoEb43k9z+96TyrekNKS+iLYDdRNy4kKGoNPEVBCc05Hg1TcDblAPfJwgJS1okqEtlcofUhKmL3K0fto+5KXEDU3GNuGwyZXjdVb9HQWU+E1jztAJjjqsahnU+g/tawABTVySLBKlAT8fMGax1mTGgArucn/WzDcy19DGioKPE7F8ILtSQ4Ww3VClK5VYB/h0x+4r7IVHrPmYX/bi1Yhm3Dc4rRYNaTjdOV5gUOsbO3oAeQkmKwQ/NO0N8qw5Ya4l8ZUW4tMav4mOsRySOOB35v0bvaJc6p+50DTbWNeX5A2MLiEhTP3vsPrmvk4LRF7CLz2J2TGIM14OoVBw7LARwmv9cz532zHki/c8tlhRzLmOTXh/wL36zFW10DeuReUGmxth7IGNmRMQKV6+miI78jm/KMPpgAdK3vwYF/GcelOFJD2HghMUUCeMbwYnvijLTejuBpwhJMNiHA/NvlEsxJDxqBCoss/Jfe+yCmUFyxovJ+L8oNkTzkmtCNzw3Ra0hiKchGhqK3BIeToV/kVx5DdF081xrEA+qyoM6CVyfJtEoz1zlRRyoo9bJ65Eg6JJd8dj1UCVsDqRY1pIjgzE/Mzsw6AaaCVhaMJL7u7YMVdyKzA6z65Xtvujz0Vo=", "uuid": "ca9e8b7c-f2be-4b6d-a639-f10b4d994d04", "availability_zone": "lt-test-1c", "enterprise_project_id" : "0", "hostname": "ecs-ddd4.novalocal", "launch_index": 0, "instance_type": "s3.medium.2", "meta": { "metering.image_id": "3a64bd37-955e-40cd-ab9e-129db56bc05d", "metering.imagetype": "gold", "metering.resourcespeccode": "s3.medium.2.linux", "metering.cloudServiceType": "hws.service.type.ec2", "image_name": "CentOS 7.6 64bit", "metering.resourcetype": "1", "vpc_id": "3b6c201f-aeb3-4bce-b841-64756e66cb49", "os_bit": "64", "cascaded.instance_extrainfo": "pcibridge:1", "os_type": "Linux", "charging_mode": "0" }, "region_id": "xxx", "project_id": "6e8b0c94265645f39c5abbe63c4113c6", "name": "ecs-ddd4" }
-
Instance Type (EC2 Compatible API) This API is used to query an ECS flavor. URI /169.254.169.254/latest/meta-data/instance-type Usage method Supports GET requests. Example Linux: curl http://169.254.169.254/latest/meta-data/instance-type s3.medium.2
-
User Data (OpenStack Metadata API) This API is used to query ECS user data. The value is configured only when you create an ECS. It cannot be changed after the configuration. URI /169.254.169.254/openstack/latest/user_data Usage method Supports GET requests. Example Linux: curl http://169.254.169.254/openstack/latest/user_data ICAgICAgDQoiQSBjbG91ZCBkb2VzIG5vdCBrbm93IHdoeSBpdCBtb3ZlcyBpbiBqdXN0IHN1Y2ggYSBkaXJlY3Rpb24gYW5kIGF0IHN1Y2ggYSBzcGVlZC4uLkl0IGZlZWxzIGFuIGltcHVsc2lvbi4uLnRoaXMgaXMgdGhlIHBsYWNlIHRvIGdvIG5vdy4gQnV0IHRoZSBza3kga25vd3MgdGhlIHJlYXNvbnMgYW5kIHRoZSBwYXR0ZXJucyBiZWhpbmQgYWxsIGNsb3VkcywgYW5kIHlvdSB3aWxsIGtub3csIHRvbywgd2hlbiB5b3UgbGlmdCB5b3Vyc2VsZiBoaWdoIGVub3VnaCB0byBzZWUgYmV5b25kIGhvcml6b25zLiINCg0KLVJpY2hhcmQgQmFjaA== If user data was not passed to the ECS during ECS creation, the query result is 404. Figure 1 404 Not Found
-
Security Key (OpenStack Metadata API) This API is used to obtain temporary AKs and SKs. If an ECS needs to obtain a temporary AK and SK, go to the ECS details page, and configure Agency for the ECS in the Management Information area so that the ECS is authorized on IAM . For details, see Cloud Service Delegation. The validity period of a temporary AK and SK is one hour. The temporary AK and SK are updated 10 minutes ahead of the expiration time. During the 10 minutes, both the new and old temporary AKs and SKs can be used. When using temporary AKs and SKs, add 'X-Security-Token':{securitytoken} in the message header. securitytoken is the value returned when a call is made to the API. URI /openstack/latest/securitykey Usage method Supports GET requests. Examples Linux: curl http://169.254.169.254/openstack/latest/securitykey
-
Hostname (EC2 Compatible API) This API is used to query the name of the host accommodating an ECS. The .novalocal suffix will be added later. URI /169.254.169.254/latest/meta-data/hostname Usage method Supports GET requests. Example Linux: curl http://169.254.169.254/latest/meta-data/hostname vm-test.novalocal
-
Local IPv4 (EC2 Compatible API) This API is used to query the fixed IP address of an ECS. If there are multiple NICs, only the IP address of the primary NIC is displayed. URI /169.254.169.254/latest/meta-data/local-ipv4 Usage method Supports GET requests. Example Linux: curl http://169.254.169.254/latest/meta-data/local-ipv4 192.1.1.2
-
Availability Zone (EC2 Compatible API) This API is used to query the AZ accommodating an ECS. URI /169.254.169.254/latest/meta-data/placement/availability-zone Usage method Supports GET requests. Example Linux: curl http://169.254.169.254/latest/meta-data/placement/availability-zone az1.dc1
-
Public Keys (EC2 Compatible API) This API is used to query the public key of an ECS. URI /169.254.169.254/latest/meta-data/public-keys/0/openssh-key Usage method Supports GET requests. Example Linux: curl http://169.254.169.254/latest/meta-data/public-keys/0/openssh-key ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDI5Fw5k8Fgzajn1zJwLoV3+wMP+6CyvsSiIc/hioggSnYu/AD0Yqm8vVO0kWlun1rFbdO+QUZKyVr/OPUjQSw4SRh4qsTKf/+eFoWTjplFvd1WCBZzS/WRenxIwR00KkczHSJro763+wYcwKieb4eKRxaQoQvoFgVjLBULXAjH4eKoKTVNtMXAvPP9aMy2SLgsJNtMb9ArfziAiblQynq7UIfLnN3VclzPeiWrqtzjyOp6CPUXnL0lVPTvbLe8sUteBsJZwlL6K4i+Y0lf3ryqnmQgC21yW4Dzu+kwk8FVT2MgWkCwiZd8gQ/+uJzrJFyMfUOBIklOBfuUENIJUhAB Generated-by-Nova
-
Network Data (OpenStack Metadata API) This API is used to query information about all NICs attached to an ECS, including their DNS server addresses, network bandwidth, IDs, private IP addresses, EIPs, and MAC addresses. URI /openstack/latest/network_data.json Usage method Supports GET requests. Example instance_max_bandwidth and instance_min_bandwidth are in the unit of Mbit/s. If the value is -1, the bandwidth is not limited. Linux: curl http://169.254.169.254/openstack/latest/network_data.json { "services": [{ "type": "dns", "address": "xxx.xx.x.x" }, { "type": "dns", "address": "100.125.21.250" }], "qos":{ "instance_min_bandwidth": 100, "instance_max_bandwidth": 500 }, "networks": [{ "network_id": "67dc10ce-441f-4592-9a80-cc709f6436e7", "type": "ipv4_dhcp", "link": "tap68a9272d-71", "id": "network0" }], "links": [{ "vif_id": "68a9272d-7152-4ae7-a138-3ef53af669e7", "public_ipv4": "100.100.xx.xx", "ethernet_mac_address": "fa:16:3e:f7:c1:47", "mtu": null, "local_ipv4": "192.169.10.10", "type": "cascading", "id": "tap68a9272d-71" }] }
-
Public IPv4 (EC2 Compatible API) This API is used to query the EIP bound to an ECS. If there are multiple NICs, only the EIP of the primary NIC is displayed. URI /169.254.169.254/latest/meta-data/public-ipv4 Usage method Supports GET requests. Example Linux: curl http://169.254.169.254/latest/meta-data/public-ipv4 46.1.1.2
-
Prerequisites The target ECS has been logged in. Security group rules in the outbound direction meet the following requirements: Protocol: TCP Port: 80 Destination: 169.254.0.0/16 If you use the default security group rules for the outbound direction, the metadata can be accessed because the default rules meet the preceding requirements. Default security group rules for the outbound direction are as follows: Protocol: All Port: All Destination: 0.0.0.0/0
-
User Data (EC2 Compatible API) This API is used to query ECS user data. The value is configured only when you create an ECS. It cannot be changed after the configuration. URI /169.254.169.254/latest/user-data Usage method Supports GET requests. Example Linux: curl http://169.254.169.254/latest/user-data ICAgICAgDQoiQSBjbG91ZCBkb2VzIG5vdCBrbm93IHdoeSBpdCBtb3ZlcyBpbiBqdXN0IHN1Y2ggYSBkaXJlY3Rpb24gYW5kIGF0IHN1Y2ggYSBzcGVlZC4uLkl0IGZlZWxzIGFuIGltcHVsc2lvbi4uLnRoaXMgaXMgdGhlIHBsYWNlIHRvIGdvIG5vdy4gQnV0IHRoZSBza3kga25vd3MgdGhlIHJlYXNvbnMgYW5kIHRoZSBwYXR0ZXJucyBiZWhpbmQgYWxsIGNsb3VkcywgYW5kIHlvdSB3aWxsIGtub3csIHRvbywgd2hlbiB5b3UgbGlmdCB5b3Vyc2VsZiBoaWdoIGVub3VnaCB0byBzZWUgYmV5b25kIGhvcml6b25zLiINCg0KLVJpY2hhcmQgQmFjaA==
-
Scenarios ECS metadata includes basic information of an ECS on the cloud platform, such as the ECS ID, hostname, and network information. ECS metadata can be obtained using either OpenStack or EC2 compatible APIs, as shown in Table 1. The following describes the URI and methods of using the supported ECS metadata.
-
ECS Metadata Types Table 1 does not contain metadata items ami-id, ami-launch-index, ami-manifest-path, block-device-mapping/, instance-action, instance-id and reservation-id. These metadata items are meaningless and are not recommended. Table 1 ECS metadata types Metadata Type Metadata Item Description OpenStack /meta_data.json Displays ECS metadata. For the key fields in the ECS metadata, see Table 2. OpenStack /password Displays the password for logging in to an ECS. OpenStack /user_data Displays ECS user data. This metadata allows you to specify scripts and configuration files for initializing ECSs. For details, see Passing User Data to ECSs. For password-authenticated Linux ECSs, this metadata is used to save password injection scripts. OpenStack /network_data.json Displays ECS network information. OpenStack /securitykey Obtains temporary AKs and SKs. Before enabling an ECS to obtain a temporary AK and SK, make sure that the op_svc_ecs account has been authorized on IAM and that the desired ECS resources have been authorized for management. EC2 /meta-data/hostname Displays the name of the host accommodating an ECS. To remove the suffix .novalocal from an ECS, see: Is an ECS Hostname with Suffix .novalocal Normal? EC2 /meta-data/local-hostname The meaning of this field is the same as that of hostname. EC2 /meta-data/public-hostname The meaning of this field is the same as that of hostname. EC2 /meta-data/instance-type Displays an ECS flavor. EC2 /meta-data/local-ipv4 Displays the fixed IP address of an ECS. If there are multiple NICs, only the IP address of the primary NIC is displayed. EC2 /meta-data/placement/availability-zone Displays the AZ accommodating an ECS. EC2 /meta-data/public-ipv4 Displays the EIP bound to an ECS. If there are multiple NICs, only the EIP of the primary NIC is displayed. EC2 /meta-data/public-keys/0/openssh-key Displays the public key of an ECS. EC2 /user-data Displays ECS user data. EC2 /meta-data/security-groups Displays the security group of an ECS. Table 2 Metadata key fields Parameter Type Description uuid String Specifies an ECS ID. availability_zone String Specifies the AZ where an ECS locates. meta Dict Specifies the metadata information, including the image name, image ID, and VPC ID. hostname String Specifies the name of the host accommodating an ECS. To remove the suffix .novalocal from an ECS, see: Is an ECS Hostname with Suffix .novalocal Normal? enterprise_project_id String Specifies the ID of the enterprise project accommodating an ECS.
-
Notes If the metadata contains sensitive data, take appropriate measures to protect the sensitive data, for example, controlling access permissions and encrypting the data. Perform the following configuration on the firewall: Linux If you need to assign permissions only to user root to access custom data, run the following command as user root: iptables --append OUTPUT --proto tcp --destination 169.254.169.254 --match owner ! --uid-owner root --jump REJECT
-
Hostname (EC2 Compatible API) This interface is used to query the name of the host accommodating a BMS. The .novalocal suffix will be added later. URI /169.254.169.254/latest/meta-data/hostname Method Supports GET requests. Example curl http://169.254.169.254/latest/meta-data/hostname bms-test.novalocal
-
Public IPv4 (EC2 Compatible API) This interface is used to query the EIP of a BMS. If there are multiple NICs, only the EIP of the primary NIC is displayed. URI /169.254.169.254/latest/meta-data/public-ipv4 Method Supports GET requests. Example curl http://169.254.169.254/latest/meta-data/public-ipv4 46.1.1.2
-
User Data (EC2 Compatible API) This interface is used to query BMS user data. The value is configured when you create a BMS. It cannot be changed after the configuration. URI /169.254.169.254/latest/user-data Method Supports GET requests. Example curl http://169.254.169.254/latest/user-data ICAgICAgDQoiQSBjbG91ZCBkb2VzIG5vdCBrbm93IHdoeSBpdCBtb3ZlcyBpbiBqdXN0IHN1Y2ggYSBkaXJlY3Rpb24gYW5kIGF0IHN1Y2ggYSBzcGVlZC4uLkl0IGZlZWxzIGFuIGltcHVsc2lvbi4uLnRoaXMgaXMgdGhlIHBsYWNlIHRvIGdvIG5vdy4gQnV0IHRoZSBza3kga25vd3MgdGhlIHJlYXNvbnMgYW5kIHRoZSBwYXR0ZXJucyBiZWhpbmQgYWxsIGNsb3VkcywgYW5kIHlvdSB3aWxsIGtub3csIHRvbywgd2hlbiB5b3UgbGlmdCB5b3Vyc2VsZiBoaWdoIGVub3VnaCB0byBzZWUgYmV5b25kIGhvcml6b25zLiINCg0KLVJpY2hhcmQgQmFjaA==
-
Public Keys (EC2 Compatible API) This interface is used to query the public key of a BMS. URI /169.254.169.254/latest/meta-data/public-keys/0/openssh-key Method Supports GET requests. Example curl http://169.254.169.254/latest/meta-data/public-keys/0/openssh-key ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDI5Fw5k8Fgzajn1zJwLoV3+wMP+6CyvsSiIc/hioggSnYu/AD0Yqm8vVO0kWlun1rFbdO+QUZKyVr/OPUjQSw4SRh4qsTKf/+eFoWTjplFvd1WCBZzS/WRenxIwR00KkczHSJro763+wYcwKieb4eKRxaQoQvoFgVjLBULXAjH4eKoKTVNtMXAvPP9aMy2SLgsJNtMb9ArfziAiblQynq7UIfLnN3VclzPeiWrqtzjyOp6CPUXnL0lVPTvbLe8sUteBsJZwlL6K4i+Y0lf3ryqnmQgC21yW4Dzu+kwk8FVT2MgWkCwiZd8gQ/+uJzrJFyMfUOBIklOBfuUENIJUhAB Generated-by-Nova
-
Security Key (OpenStack Metadata API) This interface is used to obtain temporary security credentials: Access Key ID (AK) and Secret Access Key (SK). To obtain temporary AK/SK on a BMS, you need to create an agency for BMS on IAM and assign required resource permissions to BMS. For details, see Identity and Access Management User Guide. The temporary AK/SK pair expires an hour later but is updated 10 minutes ahead of the expiration time. During the 10 minutes, both the new and old temporary AK/SK pairs can be used. When using temporary AK/SK, add 'X-Security-Token':securitytoken in the message header. securitytoken is the value returned when a call is made to the API. URI /openstack/latest/securitykey Method Supports GET requests. Example curl http://169.254.169.254/openstack/latest/securitykey
-
Availability Zone (EC2 Compatible API) This interface is used to query AZ information about a BMS. URI /169.254.169.254/latest/meta-data/placement/availability-zone Method Supports GET requests. Example curl http://169.254.169.254/latest/meta-data/placement/availability-zone az1.dc1
-
Instance Type (EC2 Compatible API) This interface is used to query the flavor name of a BMS. URI /169.254.169.254/latest/meta-data/instance-type Method Supports GET requests. Example curl http://169.254.169.254/latest/meta-data/instance-type physical.o2.medium
-
Local IPv4 (EC2 Compatible API) This interface is used to query the fixed IP address of a BMS. If there are multiple NICs, only the IP address of the primary NIC is displayed. URI /169.254.169.254/latest/meta-data/local-ipv4 Method Supports GET requests. Example curl http://169.254.169.254/latest/meta-data/local-ipv4 192.1.1.2
-
Metadata (OpenStack Metadata API) This interface is used to query BMS metadata. URI /169.254.169.254/openstack/latest/meta_data.json Method Supports GET requests. Example The following describes how to use the cURL tool to query the BMS metadata: curl http://169.254.169.254/openstack/latest/meta_data.json { "random_seed": "rEocCViRS+dNwlYdGIxJHUp+00poeUsAdBFkbPbYQTmpNwpoEb43k9z+96TyrekNKS+iLYDdRNy4kKGoNPEVBCc05Hg1TcDblAPfJwgJS1okqEtlcofUhKmL3K0fto+5KXEDU3GNuGwyZXjdVb9HQWU+E1jztAJjjqsahnU+g/tawABTVySLBKlAT8fMGax1mTGgArucn/WzDcy19DGioKPE7F8ILtSQ4Ww3VClK5VYB/h0x+4r7IVHrPmYX/bi1Yhm3Dc4rRYNaTjdOV5gUOsbO3oAeQkmKwQ/NO0N8qw5Ya4l8ZUW4tMav4mOsRySOOB35v0bvaJc6p+50DTbWNeX5A2MLiEhTP3vsPrmvk4LRF7CLz2J2TGIM14OoVBw7LARwmv9cz532zHki/c8tlhRzLmOTXh/wL36zFW10DeuReUGmxth7IGNmRMQKV6+miI78jm/KMPpgAdK3vwYF/GcelOFJD2HghMUUCeMbwYnvijLTejuBpwhJMNiHA/NvlEsxJDxqBCoss/Jfe+yCmUFyxovJ+L8oNkTzkmtCNzw3Ra0hiKchGhqK3BIeToV/kVx5DdF081xrEA+qyoM6CVyfJtEoz1zlRRyoo9bJ65Eg6JJd8dj1UCVsDqRY1pIjgzE/Mzsw6AaaCVhaMJL7u7YMVdyKzA6z65Xtvujz0Vo=", "uuid": "ca9e8b7c-f2be-4b6d-a639-f10b4d994d04", "availability_zone": "lt-test-1c", "hostname": "bms-ddd4-l00349281.novalocal", "launch_index": 0, "meta": { "metering.image_id": "3a64bd37-955e-40cd-ab9e-129db56bc05d", "metering.imagetype": "gold", "metering.resourcespeccode": "physical.s3.small", "metering.cloudServiceType": "service.type.ec2", "image_name": "CentOS 7.6 64bit", "os_bit": "64", "vpc_id": "3b6c201f-aeb3-4bce-b841-64756e66cb49", "metering.resourcetype": "1", "cascaded.instance_extrainfo": "pcibridge:2", "os_type": "Linux", "charging_mode": "0" }, "project_id": "6e8b0c94265645f39c5abbe63c4113c6", "name": "ecs-ddd4-l00349281" }
-
Introduction The BMS metadata includes BMS basic information on the cloud platform, such as the BMS ID, hostname, and network information. The BMS metadata can be retrieved using compatible OpenStack and EC2 APIs listed in Table 1. Table 1 BMS metadata types Metadata Type Metadata Item Description OpenStack type /meta_data.json This interface is used to query BMS metadata. For the key fields in the BMS metadata, see Table 2. /password This interface is used to query the BMS password. If a key pair is selected during the creation of a Windows BMS, Cloudbase-Init is used to save the ciphertext password when the BMS is initialized. /user_data This interface is used to query BMS user data. This metadata allows you to specify scripts and configuration files for initializing BMSs. For details, see Injecting User Data. For password-authenticated Linux BMSs, save the password injection script. /network_data.json This interface is used to query network information of a BMS. /securitykey This interface is used to obtain temporary security credentials: Access Key ID (AK) and Secret Access Key (SK). Before obtaining temporary AK/SK on a BMS, you need to create an agency for BMS on IAM and assign required resource permissions to BMS. EC2 type /meta-data/hostname This interface is used to query the host name of a BMS. To remove the suffix .novalocal from a BMS, see: Is the BMS Host Name with Suffix novalocal Normal? /meta-data/instance-type This interface is used to query the flavor name of a BMS. /meta-data/local-ipv4 This interface is used to query the fixed IP address of a BMS. If there are multiple NICs, only the IP address of the primary NIC is displayed. /meta-data/placement/availability-zone This interface is used to query AZ information about a BMS. /meta-data/public-ipv4 This interface is used to query the EIP of a BMS. If there are multiple NICs, only the EIP of the primary NIC is displayed. /meta-data/public-keys/0/openssh-key This interface is used to query the public key of a BMS. /user-data This interface is used to query BMS user data. /meta-data/security-groups This interface is used to query the name of the security group of the BMS. Table 2 Metadata key fields Parameter Type Description uuid String Specifies the BMS ID. availability_zone String Specifies the AZ where the BMS is located. meta Dict Specifies the metadata information, including the image name, image ID, and VPC ID. hostname String Specifies the hostname of the BMS. To remove the suffix .novalocal from a BMS, see: Is the BMS Host Name with Suffix novalocal Normal? vpc_id String Specifies the ID of the VPC where the BMS is located. The following describes the URI and methods of using the supported BMS metadata.
-
Prerequisites You have logged in to the BMS. Security group rules in the outbound direction meet the following requirements: Protocol: TCP Port Range: 80 Remote End: 169.254.0.0/16 If you use the default security group rules in the outbound direction, the preceding requirements are met, and the metadata can be accessed. The default outbound security group rule is as follows: Protocol: Any Port Range: Any Remote End: 0.0.0.0/16
-
User Data (OpenStack Metadata API) This interface is used to query BMS user data. The value is configured when you create a BMS. It cannot be changed after the configuration. URI /169.254.169.254/openstack/latest/user_data Method Supports GET requests. Example curl http://169.254.169.254/openstack/latest/user_data ICAgICAgDQoiQSBjbG91ZCBkb2VzIG5vdCBrbm93IHdoeSBpdCBtb3ZlcyBpbiBqdXN0IHN1Y2ggYSBkaXJlY3Rpb24gYW5kIGF0IHN1Y2ggYSBzcGVlZC4uLkl0IGZlZWxzIGFuIGltcHVsc2lvbi4uLnRoaXMgaXMgdGhlIHBsYWNlIHRvIGdvIG5vdy4gQnV0IHRoZSBza3kga25vd3MgdGhlIHJlYXNvbnMgYW5kIHRoZSBwYXR0ZXJucyBiZWhpbmQgYWxsIGNsb3VkcywgYW5kIHlvdSB3aWxsIGtub3csIHRvbywgd2hlbiB5b3UgbGlmdCB5b3Vyc2VsZiBoaWdoIGVub3VnaCB0byBzZWUgYmV5b25kIGhvcml6b25zLiINCg0KLVJpY2hhcmQgQmFjaA== If user data is not injected during BMS creation, the query result is 404. Figure 1 404 Not Found
-
Network Data (OpenStack Metadata API) This interface is used to query network information of a BMS. URI /openstack/latest/network_data.json Method Supports GET requests. Example curl http://169.254.169.254/openstack/latest/network_data.json { "services": [{ "type": "dns", "address": "100.125.1.250" }, { "type": "dns", "address": "100.125.21.250" }], "networks": [{ "network_id": "67dc10ce-441f-4592-9a80-cc709f6436e7", "type": "ipv4_dhcp", "link": "tap68a9272d-71", "id": "network0" }], "links": [{ "type": "cascading", "vif_id": "68a9272d-7152-4ae7-a138-3ef53af669e7", "ethernet_mac_address": "fa:16:3e:f7:c1:47", "id": "tap68a9272d-71", "mtu": null }] }
-
响应参数 表3 响应Body参数 参数 参数类型 描述 id String Metadata的ID。 idp_id String 身份提供商名称。 entity_id String Metadata文件中的entityID字段。 protocol_id String 协议ID。 domain_id String 用户所属帐号ID。 xaccount_type String 帐号来源，默认为空。 update_time String 导入或更新Metadata文件的时间。 说明： UTC时间，格式为 YYYY-MM-DDTHH:mm:ss.ssssssZ，日期和时间戳格式参照 ISO-8601，如：2023-06-28T08:56:33.710000Z。 data String Metadata文件的内容。
-
Metadata说明 Metadata是Terraform支持的内置元参数，可以在 provider，resource，data块中使用。本章节主要介绍 resource块支持的元参数，主要包括： depends_on：用于指定资源的依赖项 count：用于创建多个相同配置的资源 for_each：用于根据映射、字符串集合创建多个资源 provider：用于选择非默认的 provider lifecycle：用于定制资源的生命周期 父主题： Metadata
共30条
更多精彩内容
CDN加速
GaussDB
文字转换成语音
免费的服务器
如何创建网站
域名网站购买
私有云桌面
云主机哪个好
云速邮箱
域名怎么备案
手机云电脑
SSL证书申请
云点播服务器
免费OCR是什么
电脑云桌面
域名备案怎么弄
语音转文字
文字图片识别
云桌面是什么
网址安全检测
网站建设搭建
国外CDN加速
SSL免费证书申请
短信批量发送
图片OCR识别
云数据库MySQL
个人域名购买
录音转文字
扫描图片识别文字
OCR图片识别
行驶证识别
虚拟电话号码
电话呼叫中心软件
怎么制作一个网站
Email注册网站
华为VNC
图像文字识别
企业网站制作
个人网站搭建
华为云计算
免费租用云托管
云桌面云服务器
ocr文字识别免费版
HTTPS证书申请
图片文字识别转换
国外域名注册商
使用免费虚拟主机
云电脑主机多少钱
鲲鹏云手机
短信验证码平台
OCR图片文字识别
SSL证书是什么
申请企业邮箱步骤
免费的企业用邮箱
云免流搭建教程
域名价格
