VPC Peering

VPC peering for tenant-unaware storage networks

Create VPC peering

post

https://localhost:8443http://localhost:8787

/fabrics/{fabricName}/vpcpeering

Peers two VPCs within a fabric. Designed for tenant-unaware storage network configurations, allowing a tenant VPC to connect with the default storage VPC. Supported from ONES 4.2 onwards.

Typical operator workflow:

1. Create Tenant — POST /fabrics/{fabricName}/tenants

2. Allot GPUs — PATCH /fabrics/{fabricName}/tenants/{tenantName}

3. Fetch VPC names — use GET /fabrics for defaultStorageName; use GET /fabrics/{fabricName}/tenants/{tenantName} for the tenant vnets.name

4. Peer the VPCs — POST /fabrics/{fabricName}/vpcpeering

Path parameters

fabricNamestringRequired

Name of the fabric. Required in every API request.

Example: Fabric2SU

Body

application/json

namestringRequired

Unique name for this peering connection.

Example: xyz-storage

vpcnamestringRequired

Identifier of the requester VPC. Obtain from vnets.name in the Get Tenant Details response.

Example: pepsi-north-south

peervpcnamestringRequired

Identifier of the peer VPC — typically the default storage VPC. Obtain from defaultStorageName in the Get Fabrics response.

Example: STORAGE

Responses

200

VPC peering created successfully

No content

400

Invalid input

application/json

post

/fabrics/{fabricName}/vpcpeering

HTTPcURLJavaScriptPython

POST /fabrics/{fabricName}/vpcpeering HTTP/1.1
Host: localhost:8443
Content-Type: application/json
Accept: */*
Content-Length: 76

{
  "name": "xyz-storage",
  "vpcname": "pepsi-north-south",
  "peervpcname": "STORAGE"
}

No content