Skip to content

p1CreateResultCc: actual-equipment should not be required in the result-cc.equipment schema #295

Description

@redchy

Problem

The result-cc/equipment schema currently requires fields (actual-equipment, physical-properties,temperature) that do not always exist in the processed data.
According to the current schema definition, each equipment entry requires:

https://github.com/openBackhaul/DevicePerformanceManagementDataProcessor/blob/develop/spec/Functions/p1StreamPmData/p1ProcessDevice/p1CreateResultCc/1.0.0/variables.yaml

 equipment:
type: array
x-key: uuid
description: >
'List of equipment at the device
overwritten from {$p1RemoveOutOfRangeTemperature.output#/equipment}'
items:
type: object
required:
- uuid
- actual-equipment
properties:
uuid:
type: string
actual-equipment:
type: object
required:
- local-id
- physical-properties
- structure
properties:
local-id:
type: string
physical-properties:
type: object
required:
- temperature
properties:
temperature:
type: string
structure:
type: object
required:
- category
properties:
category:
type: string
enum:
- 'core-model-1-4:EQUIPMENT_CATEGORY_SUBRACK'
- 'core-model-1-4:EQUIPMENT_CATEGORY_CENTRAL_PROCESSING_UNIT'

Actual Behavior

In the processed Result CC data:

  • some equipment entries exist without actual-equipment
  • physical-properties / temperature may be absent

As a result, schema validation fails although the produced data may still be consistent with the implemented processing logic.

Expected Behavior

  • the schema is updated to match the processed Result CC data

Metadata

Metadata

Labels

bugSomething isn't working

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions