InlineEdgeCluster1

JSON Example

{
    "allocation_rules": [
        {
            "action": {
                "action_type": "string"
            }
        }
    ],
    "cluster_profile_bindings": [
        "ClusterProfileTypeIdEntry Object"
    ],
    "deployment_type": "string",
    "enable_inter_site_forwarding": false,
    "member_node_type": "string",
    "members": [
        "EdgeClusterMember Object"
    ],
    "node_rtep_ips": [
        "NodeRtepIpsConfig Object"
    ]
}

array of AllocationRule

allocation_rules

Optional

Set of allocation rules and respected action for auto placement of logical router, DHCP and MDProxy on edge cluster members.

array of ClusterProfileTypeIdEntry

cluster_profile_bindings

Optional

Edge cluster profile bindings

string

deployment_type

Optional

This field is a readonly field which shows the deployment_type of members. It returns UNKNOWN if there are no members, and returns VIRTUAL_MACHINE| PHYSICAL_MACHINE if all edge members are VIRTUAL_MACHINE|PHYSICAL_MACHINE. It returns HYBRID if the cluster contains edge members of both types VIRTUAL_MACHINE and PHYSICAL_MACHINE.

Possible values are : VIRTUAL_MACHINE, PHYSICAL_MACHINE, UNKNOWN,

boolean

enable_inter_site_forwarding

Optional

Flag should be only use in federation for inter site l2 and l3 forwarding. Before enabling this flag, all the edge cluster members must have remote tunnel endpoint configured. TIER0/TIER1 logical routers managed by GM must be associated with edge cluster which has inter-site forwarding enabled.

string

member_node_type

Optional

Edge cluster is homogenous collection of transport nodes. Hence all transport nodes of the cluster must be of same type. This readonly field shows the type of transport nodes.

Possible values are : EDGE_NODE, PUBLIC_CLOUD_GATEWAY_NODE, UNKNOWN,

array of EdgeClusterMember

members

Optional

EdgeCluster only supports homogeneous members. These member should be backed by either EdgeNode or PublicCloudGatewayNode. TransportNode type of these nodes should be the same. DeploymentType (VIRTUAL_MACHINE|PHYSICAL_MACHINE) of these EdgeNodes is recommended to be the same. EdgeCluster supports members of different deployment types.

array of NodeRtepIpsConfig

node_rtep_ips

Optional

List of remote tunnel endpoint ipaddress configured on edge cluster for each transport node.

Used By

EdgeCluster