> ## Documentation Index > Fetch the complete documentation index at: https://docs.internal.nscale.com/llms.txt > Use this file to discover all available pages before exploring further. # List deployment summary by row > DC-standup `Row view`: each row's racks, with device counts per stage. One entry per rack `Location`, ordered down the hall, each rack ordered along its row. A rack's `device_by_stage` is the pipeline card narrowed to that rack, and `with_customer` is true only when every one of its placed devices is in customer hands. Unpaginated, like the four cards and the matrix: the whole site arrives in one ordered body, because the Row view charts it whole. `page` and `limit` are not accepted. ## OpenAPI ````yaml /openapi/fleet-manager-openapi.yaml get /api/v1/sites/{site_id}/operations/racks/standup/row-summary/ openapi: 3.0.3 info: title: Fleet Manager API version: 1.0.0 description: API for the Nscale Fleet Manager servers: [] security: [] paths: /api/v1/sites/{site_id}/operations/racks/standup/row-summary/: get: tags: - Operations summary: List deployment summary by row description: >- DC-standup `Row view`: each row's racks, with device counts per stage. One entry per rack `Location`, ordered down the hall, each rack ordered along its row. A rack's `device_by_stage` is the pipeline card narrowed to that rack, and `with_customer` is true only when every one of its placed devices is in customer hands. Unpaginated, like the four cards and the matrix: the whole site arrives in one ordered body, because the Row view charts it whole. `page` and `limit` are not accepted. operationId: api_v1_sites_operations_racks_standup_row_summary_list parameters: - in: query name: device_class schema: type: array items: $ref: '#/components/schemas/StandupDeviceClassEnum' description: >- Optional. Count only devices of these classes; repeat the param to include more than one (e.g. gpu_compute + cpu_baremetal). Accepts exactly what the standup matrix accepts, so a filtered card and a filtered matrix agree. - in: path name: site_id schema: type: string format: uuid description: Site identifier. required: true responses: '200': content: application/json: schema: type: array items: $ref: '#/components/schemas/StandupRowSummary' description: '' '400': description: Validation error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Authentication credentials were not provided or are invalid. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: You do not have permission to perform this action. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Not found. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - oauth2: - operations:read - cookieAuth: [] components: schemas: StandupDeviceClassEnum: type: string enum: - cpu_baremetal - cpu_hypervisor - gpu_compute StandupRowSummary: type: object description: One rack `Location` and the racks it holds. properties: location_id: type: string format: uuid description: >- The row's `Location`. Group and key on this rather than on `location_name`: a site can hold two rows sharing a name (london14 has two `Row C`), and they are different rows. location_name: type: string racks: type: array items: $ref: '#/components/schemas/StandupRackRowSummary' required: - location_id - location_name - racks ErrorResponse: type: object description: >- Uniform error body for every 4xx/5xx response. `detail` is a human-readable message, always present, safe to display to end users. `code` is the machine-readable identifier. `field_errors` lists per-input-field validation messages and is empty for non-field errors (auth, permission, not-found, conflict, server). required: - detail - code - field_errors properties: detail: type: string code: $ref: '#/components/schemas/ErrorCodeEnum' field_errors: type: array items: $ref: '#/components/schemas/FieldError' StandupRackRowSummary: type: object description: One rack's pipeline progress in the DC-standup Row view. properties: rack_id: type: string format: uuid rack_name: type: string device_by_stage: allOf: - $ref: '#/components/schemas/StandupPipelineSummary' description: >- Device counts for this rack, keyed by `StandupPipelineColumnEnum`. Every column is present, and every `status` and `verdict` key inside it, zero included — the same shape and the same rules as the site-wide `pipeline-summary` card, narrowed to this rack. Summing one column across every rack in every row reproduces that card exactly. with_customer: type: boolean description: >- Whether the whole rack is in customer hands — true only when *every* one of its placed devices is `available` or `in_use`, the same operational state that places a device at its terminal stage in the standup matrix. A rack part-way through release reports false. This is current handover state, not pipeline history: a device that reached `available` without running the pipeline still counts. Under a `device_class` filter it reads only the devices that survive it, like every count beside it — so a rack whose GPUs are handed over reports true to a `gpu_compute` read even while its head nodes are still in standup. required: - device_by_stage - rack_id - rack_name - with_customer ErrorCodeEnum: type: string description: >- Stable machine-readable error identifier. New members may be added within this API version; clients must tolerate unknown values. enum: - error - invalid - parse_error - authentication_failed - not_authenticated - permission_denied - not_found - method_not_allowed - not_acceptable - unsupported_media_type - conflict - enrollment_infrastructure_reference_pending - enrollment_infrastructure_reference_changed - unprocessable_entity - throttled - service_unavailable FieldError: type: object description: One input field's validation messages. required: - field - messages properties: field: type: string description: >- Dotted path to the offending input field, or to the collection row when the whole row is invalid (e.g. `filters.end_date`, `memberships.0.role`, `memberships.0`). messages: type: array minItems: 1 items: type: string StandupPipelineSummary: type: object description: >- Fleet pipeline chart, keyed by `StandupPipelineColumnEnum`. Every column is present. required: - enrolment - quarantine - single_node_test - multi_node_test - release properties: enrolment: $ref: '#/components/schemas/StandupColumnSummary' quarantine: $ref: '#/components/schemas/StandupColumnSummary' single_node_test: $ref: '#/components/schemas/StandupColumnSummary' multi_node_test: $ref: '#/components/schemas/StandupColumnSummary' release: $ref: '#/components/schemas/StandupColumnSummary' StandupColumnSummary: type: object description: Device counts for one pipeline column. required: - status - verdict properties: status: $ref: '#/components/schemas/StandupStatusCounts' verdict: allOf: - $ref: '#/components/schemas/StandupVerdictCounts' nullable: true description: Null for columns with no acceptance gate. StandupStatusCounts: type: object description: >- Device count per `StandupDeviceStatusEnum`. Every status is present, zero included. required: - not_started - pending - running - succeeded - failed properties: not_started: type: integer minimum: 0 pending: type: integer minimum: 0 running: type: integer minimum: 0 succeeded: type: integer minimum: 0 failed: type: integer minimum: 0 StandupVerdictCounts: type: object description: >- Device count per `StandupGateVerdictEnum` for the acceptance gate holding the device in this column. Every verdict is present, zero included. A device in a gated column whose resource class has no policy for that gate has no verdict to report and is counted in `status` but not here, so the two need not sum alike. required: - pass - missing-evidence - stale-evidence - topology-incomplete - execution-error - threshold-failure - pending properties: pass: type: integer minimum: 0 missing-evidence: type: integer minimum: 0 stale-evidence: type: integer minimum: 0 topology-incomplete: type: integer minimum: 0 execution-error: type: integer minimum: 0 threshold-failure: type: integer minimum: 0 pending: type: integer minimum: 0 securitySchemes: oauth2: type: oauth2 flows: {} cookieAuth: type: apiKey in: cookie name: sessionid ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.