mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-17 14:26:34 +00:00
gcloud: Wed Nov 15 11:42:54 UTC 2023
This commit is contained in:
parent
03f0979970
commit
d3074f94bb
224 changed files with 6432 additions and 626 deletions
135
gcloud/vmware/network-peerings/create
Normal file
135
gcloud/vmware/network-peerings/create
Normal file
|
|
@ -0,0 +1,135 @@
|
|||
NAME
|
||||
gcloud vmware network-peerings create - create a VMware Engine VPC network
|
||||
peering
|
||||
|
||||
SYNOPSIS
|
||||
gcloud vmware network-peerings create NETWORK_PEERING
|
||||
--peer-network=PEER_NETWORK --peer-network-type=PEER_NETWORK_TYPE
|
||||
--vmware-engine-network=VMWARE_ENGINE_NETWORK [--async]
|
||||
[--description=DESCRIPTION] [--no-exchange-subnet-routes]
|
||||
[--no-export-custom-routes] [--no-export-custom-routes-with-public-ip]
|
||||
[--no-import-custom-routes] [--no-import-custom-routes-with-public-ip]
|
||||
[--peer-mtu=PEER_MTU] [--peer-project=PEER_PROJECT]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
Create a VMware Engine VPC network peering. VPC network peering creation is
|
||||
considered finished when the network peering is in ACTIVE state. Check the
|
||||
progress of a VPC network peering using gcloud vmware network-peerings
|
||||
list.
|
||||
|
||||
EXAMPLES
|
||||
To create a VPC network peering called new-peering that connects the VMware
|
||||
Engine network my-vmware-engine-network with another VMware Engine network
|
||||
another-vmware-engine-network from project another-project, run:
|
||||
|
||||
$ gcloud vmware network-peerings create new-peering \
|
||||
--vmware-engine-network=my-vmware-engine-network \
|
||||
--peer-network=another-vmware-engine-network \
|
||||
--peer-network-type=VMWARE_ENGINE_NETWORK \
|
||||
--peer-project=another-project
|
||||
|
||||
In this example, the project is taken from gcloud properties core/project
|
||||
and location is taken as global.
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
VMware Engine VPC network peering resource - network_peering. This
|
||||
represents a Cloud resource. (NOTE) Some attributes are not given
|
||||
arguments in this group but can be set in other ways.
|
||||
|
||||
To set the project attribute:
|
||||
◆ provide the argument network_peering on the command line with a fully
|
||||
specified name;
|
||||
◆ set the property core/project;
|
||||
◆ provide the argument --project on the command line.
|
||||
|
||||
This must be specified.
|
||||
|
||||
NETWORK_PEERING
|
||||
ID of the VMware Engine VPC network peering or fully qualified
|
||||
identifier for the VMware Engine VPC network peering.
|
||||
|
||||
To set the network-peering attribute:
|
||||
▸ provide the argument network_peering on the command line.
|
||||
|
||||
REQUIRED FLAGS
|
||||
--peer-network=PEER_NETWORK
|
||||
ID of the network to peer with the VMware Engine network. The peer
|
||||
network can be a consumer VPC network or another VMware Engine network.
|
||||
|
||||
--peer-network-type=PEER_NETWORK_TYPE
|
||||
Type of the VPC network to peer with the VMware Engine network.
|
||||
PEER_NETWORK_TYPE must be one of the following:
|
||||
◆ STANDARD: Peering connection used for connecting to another VPC
|
||||
network established by the same user. For example, a peering
|
||||
connection to another VPC network in the same project or to an
|
||||
on-premises network.
|
||||
◆ VMWARE_ENGINE_NETWORK: Peering connection used for connecting to
|
||||
another VMware Engine network.
|
||||
◆ PRIVATE_SERVICES_ACCESS: Peering connection used for establishing
|
||||
private services access.
|
||||
◆ NETAPP_CLOUD_VOLUMES: Peering connection used for connecting to
|
||||
NetApp Cloud Volumes.
|
||||
◆ THIRD_PARTY_SERVICE: Peering connection used for connecting to
|
||||
third-party services. Most third-party services require manual setup
|
||||
of reverse peering on the VPC network associated with the third-party
|
||||
service.
|
||||
◆ DELL_POWERSCALE: Peering connection used for connecting to Dell
|
||||
PowerScale Filers. PEER_NETWORK_TYPE must be one of:
|
||||
PEER_NETWORK_TYPE_UNSPECIFIED, STANDARD, VMWARE_ENGINE_NETWORK,
|
||||
PRIVATE_SERVICES_ACCESS, NETAPP_CLOUD_VOLUMES, THIRD_PARTY_SERVICE,
|
||||
DELL_POWERSCALE.
|
||||
|
||||
--vmware-engine-network=VMWARE_ENGINE_NETWORK
|
||||
ID of the VMware Engine network to attach the new peering to.
|
||||
|
||||
OPTIONAL FLAGS
|
||||
--async
|
||||
Return immediately, without waiting for the operation in progress to
|
||||
complete. The default is True. Enabled by default, use --no-async to
|
||||
disable.
|
||||
|
||||
--description=DESCRIPTION
|
||||
User-provided description of the VPC network peering.
|
||||
|
||||
--exchange-subnet-routes
|
||||
True if full-mesh connectivity is created and managed automatically
|
||||
between peered VPC networks; false otherwise. This field is always true
|
||||
because Google Compute Engine automatically creates and manages
|
||||
subnetwork routes between two VPC networks when the peering state is
|
||||
ACTIVE. Enabled by default, use --no-exchange-subnet-routes to disable.
|
||||
|
||||
--export-custom-routes
|
||||
True if custom routes are exported to the peered VPC network; false
|
||||
otherwise. The default value is true. Enabled by default, use
|
||||
--no-export-custom-routes to disable.
|
||||
|
||||
--export-custom-routes-with-public-ip
|
||||
True if all subnet routes with public IP address range are exported;
|
||||
false otherwise. The default value is true. Enabled by default, use
|
||||
--no-export-custom-routes-with-public-ip to disable.
|
||||
|
||||
--import-custom-routes
|
||||
True if custom routes are imported to the peered VPC network; false
|
||||
otherwise. The default value is true. Enabled by default, use
|
||||
--no-import-custom-routes to disable.
|
||||
|
||||
--import-custom-routes-with-public-ip
|
||||
True if all subnet routes with public IP address range are imported;
|
||||
false otherwise. The default value is true. Enabled by default, use
|
||||
--no-import-custom-routes-with-public-ip to disable.
|
||||
|
||||
--peer-mtu=PEER_MTU
|
||||
Maximum transmission unit (MTU) in bytes.
|
||||
|
||||
--peer-project=PEER_PROJECT
|
||||
Project ID or project number of the peer network. Use this flag when
|
||||
the peer network is in another project.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
--billing-project, --configuration, --flags-file, --flatten, --format,
|
||||
--help, --impersonate-service-account, --log-http, --project, --quiet,
|
||||
--trace-token, --user-output-enabled, --verbosity.
|
||||
|
||||
Run $ gcloud help for details.
|
||||
Loading…
Add table
Add a link
Reference in a new issue