Skip to content
StratumStratum Docs

List FIP meta-pools (bootstrap-admin).

GET
/v1/admin/network/meta-fip-pools
Code sample: Shell / cURL
curl --request GET \
  --url https://stratum.example.com/v1/admin/network/meta-fip-pools \
  --header 'Authorization: Bearer <token>'

Operator meta-pools are the supply of public FIP CIDR space that per-project carve-outs are cut from. Install- scope; gates on the network:ListMetaFipPools Cedar action.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Query Parameters

Section titled “Query Parameters”
region
string

Responses

Section titled “Responses”

200

Section titled “200”

Meta-pools.

Media typeapplication/json

Complete: returns every meta floating-IP pool.

This list is bounded by the install’s own configuration rather than by tenant activity, so it is not paginated and carries no nextPageToken. A client has the whole set in one response.

object
items
required
Array<object>

operator meta-pool — the supply of public FIP CIDR space that per-project carve-outs are cut from.

object
id
required
string
/^metafip-[a-z0-9-]+$/
region
required
string
cidr
required

The CIDR supply this meta-pool offers for carve-outs.

string
carvePrefix
required

Default prefix length for per-project carve-outs (default 24).

integer
>= 16 <= 28
state
required
string
Allowed values: active draining
createdAt
required
string format: date-time
createdBy
string

Example 

{
  "items": [
    {
      "cidr": "198.51.100.0/22",
      "state": "active"
    }
  ]
}

403

Section titled “403”

Authenticated but not authorized.

Media typeapplication/problem+json
object
type
required
string format: uri
title
required
string
status
required
integer
>= 400 <= 599
detail
string
instance
string format: uri-reference
requestId
required
string
code
required
string
issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object
code
required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string
statement
required

Index of the statement at fault; -1 for the document as a whole.

integer
>= -1
detail
required
string
action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string
errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object
field
required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string
message
required
string
details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object
key
additional properties
any

Example 

{
  "issues": [
    {
      "code": "ACTION_NOT_APPLICABLE",
      "action": "compute:CreateVpc"
    }
  ]
}