.TH "GCLOUD_VMWARE_NETWORK\-PEERINGS_CREATE" 1



.SH "NAME"
.HP
gcloud vmware network\-peerings create \- create a VMware Engine VPC network peering



.SH "SYNOPSIS"
.HP
\f5gcloud vmware network\-peerings create\fR (\fINETWORK_PEERING\fR\ :\ \fB\-\-location\fR=\fILOCATION\fR) \fB\-\-peer\-network\fR=\fIPEER_NETWORK\fR \fB\-\-peer\-network\-type\fR=\fIPEER_NETWORK_TYPE\fR \fB\-\-vmware\-engine\-network\fR=\fIVMWARE_ENGINE_NETWORK\fR [\fB\-\-async\fR] [\fB\-\-description\fR=\fIDESCRIPTION\fR] [\fB\-\-no\-exchange\-subnet\-routes\fR] [\fB\-\-no\-export\-custom\-routes\fR] [\fB\-\-no\-export\-custom\-routes\-with\-public\-ip\fR] [\fB\-\-no\-import\-custom\-routes\fR] [\fB\-\-no\-import\-custom\-routes\-with\-public\-ip\fR] [\fB\-\-peer\-mtu\fR=\fIPEER_MTU\fR] [\fB\-\-peer\-project\fR=\fIPEER_PROJECT\fR] [\fB\-\-vmware\-engine\-network\-project\fR=\fIVMWARE_ENGINE_NETWORK_PROJECT\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "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 \f5gcloud vmware network\-peerings
list\fR.



.SH "EXAMPLES"

To create a VPC network peering called \f5new\-peering\fR that connects the
VMware Engine network \f5my\-vmware\-engine\-network\fR with another VMware
Engine network \f5another\-vmware\-engine\-network\fR from project
\f5another\-project\fR, run:

.RS 2m
$ gcloud vmware network\-peerings create new\-peering \e
    \-\-vmware\-engine\-network=my\-vmware\-engine\-network \e
    \-\-peer\-network=another\-vmware\-engine\-network \e
    \-\-peer\-network\-type=VMWARE_ENGINE_NETWORK \e
    \-\-peer\-project=another\-project
.RE

In this example, the project is taken from gcloud properties core/project and
location is taken as \f5global\fR.



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

VMware Engine VPC network peering resource \- network_peering. The arguments in
this group can be used to specify the attributes of this resource. (NOTE) Some
attributes are not given arguments in this group but can be set in other ways.

To set the \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5network_peering\fR on the command line with a fully
specified name;
.IP "\(em" 2m
provide the argument \f5\-\-project\fR on the command line;
.IP "\(em" 2m
set the property \f5core/project\fR.
.RE
.sp

This must be specified.


.RS 2m
.TP 2m
\fINETWORK_PEERING\fR

ID of the VMware Engine VPC network peering or fully qualified identifier for
the VMware Engine VPC network peering.

To set the \f5network\-peering\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5network_peering\fR on the command line.
.RE
.sp

This positional argument must be specified if any of the other arguments in this
group are specified.

.TP 2m
\fB\-\-location\fR=\fILOCATION\fR

The resource name of the location.

To set the \f5location\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5network_peering\fR on the command line with a fully
specified name;
.IP "\(bu" 2m
provide the argument \f5\-\-location\fR on the command line;
.IP "\(bu" 2m
set location as 'global' (default).
.RE
.sp


.RE
.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-peer\-network\fR=\fIPEER_NETWORK\fR

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.

.TP 2m
\fB\-\-peer\-network\-type\fR=\fIPEER_NETWORK_TYPE\fR

Type of the VPC network to peer with the VMware Engine network.
PEER_NETWORK_TYPE must be one of the following:
.RS 2m
.IP "\(em" 2m
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.
.IP "\(em" 2m
VMWARE_ENGINE_NETWORK: Peering connection used for connecting to another VMware
Engine network.
.IP "\(em" 2m
PRIVATE_SERVICES_ACCESS: Peering connection used for establishing private
services access.
.IP "\(em" 2m
NETAPP_CLOUD_VOLUMES: Peering connection used for connecting to NetApp Cloud
Volumes.
.IP "\(em" 2m
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.
.IP "\(em" 2m
DELL_POWERSCALE: Peering connection used for connecting to Dell PowerScale
Filers.
.IP "\(em" 2m
GOOGLE_CLOUD_NETAPP_VOLUMES: Peering connection used for connecting to Google
Cloud NetApp Volumes. \fIPEER_NETWORK_TYPE\fR must be one of:
\fBPEER_NETWORK_TYPE_UNSPECIFIED\fR, \fBSTANDARD\fR,
\fBVMWARE_ENGINE_NETWORK\fR, \fBPRIVATE_SERVICES_ACCESS\fR,
\fBNETAPP_CLOUD_VOLUMES\fR, \fBTHIRD_PARTY_SERVICE\fR, \fBDELL_POWERSCALE\fR,
\fBGOOGLE_CLOUD_NETAPP_VOLUMES\fR.
.RE
.sp

.TP 2m
\fB\-\-vmware\-engine\-network\fR=\fIVMWARE_ENGINE_NETWORK\fR

ID of the VMware Engine network to attach the new peering to.


.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-async\fR

Return immediately, without waiting for the operation in progress to complete.
The default is \fBTrue\fR. Enabled by default, use \fB\-\-no\-async\fR to
disable.

.TP 2m
\fB\-\-description\fR=\fIDESCRIPTION\fR

User\-provided description of the VPC network peering.

.TP 2m
\fB\-\-exchange\-subnet\-routes\fR

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
\fB\-\-no\-exchange\-subnet\-routes\fR to disable.

.TP 2m
\fB\-\-export\-custom\-routes\fR

True if custom routes are exported to the peered VPC network; false otherwise.
The default value is true. Enabled by default, use
\fB\-\-no\-export\-custom\-routes\fR to disable.

.TP 2m
\fB\-\-export\-custom\-routes\-with\-public\-ip\fR

True if all subnet routes with public IP address range are exported; false
otherwise. The default value is true. Enabled by default, use
\fB\-\-no\-export\-custom\-routes\-with\-public\-ip\fR to disable.

.TP 2m
\fB\-\-import\-custom\-routes\fR

True if custom routes are imported to the peered VPC network; false otherwise.
The default value is true. Enabled by default, use
\fB\-\-no\-import\-custom\-routes\fR to disable.

.TP 2m
\fB\-\-import\-custom\-routes\-with\-public\-ip\fR

True if all subnet routes with public IP address range are imported; false
otherwise. The default value is true. Enabled by default, use
\fB\-\-no\-import\-custom\-routes\-with\-public\-ip\fR to disable.

.TP 2m
\fB\-\-peer\-mtu\fR=\fIPEER_MTU\fR

Maximum transmission unit (MTU) in bytes.

.TP 2m
\fB\-\-peer\-project\fR=\fIPEER_PROJECT\fR

Project ID or project number of the peer network. Use this flag when the peer
network is in another project.

.TP 2m
\fB\-\-vmware\-engine\-network\-project\fR=\fIVMWARE_ENGINE_NETWORK_PROJECT\fR

Project of the VMware Engine network to attach the new peering to. Use this flag
when the VMware Engine network is in another project.


.RE
.sp

.SH "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 \fB$ gcloud help\fR for details.