A Network Connectivity Center hub is a global management resource to which you attach spokes. A single hub can contain spokes from multiple regions. However, if any of a hub's spokes use the site-to-site data transfer feature, the resources associated with those spokes must all be in the same VPC network. Spokes that do not use site-to-site data transfer can be associated with any VPC network in your project.

LinkedInterconnectAttachments

A collection of VLAN attachment resources. These resources should be redundant attachments that all advertise the same prefixes to Google Cloud. Alternatively, in active/passive configurations, all attachments should be capable of advertising the same prefixes.

LinkedRouterApplianceInstances

A collection of router appliance instances. If you configure multiple router appliance instances to receive data from the same set of sites outside of Google Cloud, we recommend that you associate those instances with the same spoke.

LinkedVpcNetwork

An existing VPC network.

LinkedVpnTunnels

A collection of Cloud VPN tunnel resources. These resources should be redundant HA VPN tunnels that all advertise the same prefixes to Google Cloud. Alternatively, in a passive/active configuration, all tunnels should be capable of advertising the same prefixes.

ListGroupsRequest

Request for HubService.ListGroups method.

ListGroupsResponse

Response for HubService.ListGroups method.

ListHubSpokesRequest

The request for HubService.ListHubSpokes.

ListHubSpokesResponse

The response for HubService.ListHubSpokes.

ListHubsRequest

Request for HubService.ListHubs method.

ListHubsResponse

Response for HubService.ListHubs method.

ListPolicyBasedRoutesRequest

Request for [PolicyBasedRouting.ListPolicyBasedRoutes][] method.

ListPolicyBasedRoutesResponse

Response for [PolicyBasedRouting.ListPolicyBasedRoutes][] method.

ListRouteTablesRequest

Request for HubService.ListRouteTables method.

ListRouteTablesResponse

Response for HubService.ListRouteTables method.

ListRoutesRequest

Request for HubService.ListRoutes method.

ListRoutesResponse

Response for HubService.ListRoutes method.

ListSpokesRequest

The request for HubService.ListSpokes.

ListSpokesResponse

The response for HubService.ListSpokes.

LocationFeature

Supported features for a location

LocationMetadata

Metadata about locations

NextHopVpcNetwork

OperationMetadata

Represents the metadata of the long-running operation.

PolicyBasedRoute

Policy Based Routes (PBR) are more powerful routes that allows GCP customers to route their L4 network traffic based on not just destination IP, but also source IP, protocol and more. A PBR always take precedence when it conflicts with other types of routes. Next id: 22

This message has oneof_ fields (mutually exclusive fields). For each oneof, at most one member field can be set at the same time. Setting any member of the oneof automatically clears all other members.

.. _oneof: https://proto-plus-python.readthedocs.io/en/stable/fields.html#oneofs-mutually-exclusive-fields

RejectHubSpokeRequest

The request for HubService.RejectHubSpoke.

RejectHubSpokeResponse

The response for HubService.RejectHubSpoke.

Route

A route defines a path from VM instances within a spoke to a specific destination resource. Only VPC spokes have routes.

RouteTable

RouteType

The route's type

RouterApplianceInstance

A router appliance instance is a Compute Engine virtual machine (VM) instance that acts as a BGP speaker. A router appliance instance is specified by the URI of the VM and the internal IP address of one of the VM's network interfaces.

RoutingVPC

RoutingVPC contains information about the VPC networks associated with the spokes of a Network Connectivity Center hub.

Spoke

A Network Connectivity Center spoke represents one or more network connectivity resources.

When you create a spoke, you associate it with a hub. You must also identify a value for exactly one of the following fields:

linked_vpn_tunnels
linked_interconnect_attachments
linked_router_appliance_instances
linked_vpc_network

SpokeSummary

Summarizes information about the spokes associated with a hub. The summary includes a count of spokes according to type and according to state. If any spokes are inactive, the summary also lists the reasons they are inactive, including a count for each reason.