From 8f06492a3d631f1146834c0f8d76f8ca77436a3d Mon Sep 17 00:00:00 2001 From: "Mitch Harding (the weird one)" Date: Tue, 7 Jan 2025 17:20:08 -0500 Subject: [PATCH] CASMCMS-9242: Update BOS OpenAPI spec to pull in new options --- cray/modules/bos/openapi.yaml | 21 ++++- cray/modules/bos/swagger3.json | 138 +++++++++++++++++++++++++++++++-- 2 files changed, 151 insertions(+), 8 deletions(-) diff --git a/cray/modules/bos/openapi.yaml b/cray/modules/bos/openapi.yaml index 59f817e..e5e132d 100644 --- a/cray/modules/bos/openapi.yaml +++ b/cray/modules/bos/openapi.yaml @@ -1182,10 +1182,15 @@ components: Options for the boot orchestration service. type: object properties: + bss_read_timeout: + type: integer + description: The amount of time (in seconds) to wait for a response before timing out a request to BSS + example: 20 + minimum: 10 + maximum: 86400 cfs_read_timeout: type: integer - description: | - The amount of time (in seconds) to wait for a response before timing out a request to CFS + description: The amount of time (in seconds) to wait for a response before timing out a request to CFS example: 20 minimum: 10 maximum: 86400 @@ -1204,6 +1209,12 @@ components: discovery_frequency: type: integer description: How frequently the BOS discovery agent syncs new components from HSM. (in seconds) + hsm_read_timeout: + type: integer + description: The amount of time (in seconds) to wait for a response before timing out a request to HSM + example: 20 + minimum: 10 + maximum: 86400 logging_level: type: string description: The logging level for all BOS services @@ -1216,6 +1227,12 @@ components: max_power_off_wait_time: type: integer description: How long BOS will wait for a node to power off before forcefully powering off (in seconds) + pcs_read_timeout: + type: integer + description: The amount of time (in seconds) to wait for a response before timing out a request to PCS + example: 20 + minimum: 10 + maximum: 86400 polling_frequency: type: integer description: How frequently the BOS operators check component state for needed actions. (in seconds) diff --git a/cray/modules/bos/swagger3.json b/cray/modules/bos/swagger3.json index 1ab8003..7dbe16a 100644 --- a/cray/modules/bos/swagger3.json +++ b/cray/modules/bos/swagger3.json @@ -2582,9 +2582,16 @@ "description": "Options for the boot orchestration service.\n", "type": "object", "properties": { + "bss_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to BSS.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "cfs_read_timeout": { "type": "integer", - "description": "The amount of time (in seconds) to wait for a response before timing out a request to CFS.\n", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to CFS.", "example": 20, "minimum": 10, "maximum": 86400 @@ -2609,6 +2616,13 @@ "type": "integer", "description": "How frequently the BOS discovery agent syncs new components from HSM. (in seconds)" }, + "hsm_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to HSM.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "logging_level": { "type": "string", "description": "The logging level for all BOS services" @@ -2625,6 +2639,13 @@ "type": "integer", "description": "How long BOS will wait for a node to power off before forcefully powering off (in seconds)" }, + "pcs_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to PCS.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "polling_frequency": { "type": "integer", "description": "How frequently the BOS operators check component state for needed actions. (in seconds)" @@ -3607,9 +3628,16 @@ "description": "Options for the boot orchestration service.\n", "type": "object", "properties": { + "bss_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to BSS.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "cfs_read_timeout": { "type": "integer", - "description": "The amount of time (in seconds) to wait for a response before timing out a request to CFS.\n", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to CFS.", "example": 20, "minimum": 10, "maximum": 86400 @@ -3634,6 +3662,13 @@ "type": "integer", "description": "How frequently the BOS discovery agent syncs new components from HSM. (in seconds)" }, + "hsm_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to HSM.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "logging_level": { "type": "string", "description": "The logging level for all BOS services" @@ -3650,6 +3685,13 @@ "type": "integer", "description": "How long BOS will wait for a node to power off before forcefully powering off (in seconds)" }, + "pcs_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to PCS.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "polling_frequency": { "type": "integer", "description": "How frequently the BOS operators check component state for needed actions. (in seconds)" @@ -5153,9 +5195,16 @@ "description": "Options for the boot orchestration service.\n", "type": "object", "properties": { + "bss_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to BSS.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "cfs_read_timeout": { "type": "integer", - "description": "The amount of time (in seconds) to wait for a response before timing out a request to CFS.\n", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to CFS.", "example": 20, "minimum": 10, "maximum": 86400 @@ -5180,6 +5229,13 @@ "type": "integer", "description": "How frequently the BOS discovery agent syncs new components from HSM. (in seconds)" }, + "hsm_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to HSM.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "logging_level": { "type": "string", "description": "The logging level for all BOS services" @@ -5196,6 +5252,13 @@ "type": "integer", "description": "How long BOS will wait for a node to power off before forcefully powering off (in seconds)" }, + "pcs_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to PCS.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "polling_frequency": { "type": "integer", "description": "How frequently the BOS operators check component state for needed actions. (in seconds)" @@ -14640,9 +14703,16 @@ "description": "Options for the boot orchestration service.\n", "type": "object", "properties": { + "bss_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to BSS.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "cfs_read_timeout": { "type": "integer", - "description": "The amount of time (in seconds) to wait for a response before timing out a request to CFS.\n", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to CFS.", "example": 20, "minimum": 10, "maximum": 86400 @@ -14667,6 +14737,13 @@ "type": "integer", "description": "How frequently the BOS discovery agent syncs new components from HSM. (in seconds)" }, + "hsm_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to HSM.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "logging_level": { "type": "string", "description": "The logging level for all BOS services" @@ -14683,6 +14760,13 @@ "type": "integer", "description": "How long BOS will wait for a node to power off before forcefully powering off (in seconds)" }, + "pcs_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to PCS.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "polling_frequency": { "type": "integer", "description": "How frequently the BOS operators check component state for needed actions. (in seconds)" @@ -14729,9 +14813,16 @@ "description": "Options for the boot orchestration service.\n", "type": "object", "properties": { + "bss_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to BSS.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "cfs_read_timeout": { "type": "integer", - "description": "The amount of time (in seconds) to wait for a response before timing out a request to CFS.\n", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to CFS.", "example": 20, "minimum": 10, "maximum": 86400 @@ -14756,6 +14847,13 @@ "type": "integer", "description": "How frequently the BOS discovery agent syncs new components from HSM. (in seconds)" }, + "hsm_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to HSM.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "logging_level": { "type": "string", "description": "The logging level for all BOS services" @@ -14772,6 +14870,13 @@ "type": "integer", "description": "How long BOS will wait for a node to power off before forcefully powering off (in seconds)" }, + "pcs_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to PCS.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "polling_frequency": { "type": "integer", "description": "How frequently the BOS operators check component state for needed actions. (in seconds)" @@ -14807,9 +14912,16 @@ "description": "Options for the boot orchestration service.\n", "type": "object", "properties": { + "bss_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to BSS.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "cfs_read_timeout": { "type": "integer", - "description": "The amount of time (in seconds) to wait for a response before timing out a request to CFS.\n", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to CFS.", "example": 20, "minimum": 10, "maximum": 86400 @@ -14834,6 +14946,13 @@ "type": "integer", "description": "How frequently the BOS discovery agent syncs new components from HSM. (in seconds)" }, + "hsm_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to HSM.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "logging_level": { "type": "string", "description": "The logging level for all BOS services" @@ -14850,6 +14969,13 @@ "type": "integer", "description": "How long BOS will wait for a node to power off before forcefully powering off (in seconds)" }, + "pcs_read_timeout": { + "type": "integer", + "description": "The amount of time (in seconds) to wait for a response before timing out a request to PCS.", + "example": 20, + "minimum": 10, + "maximum": 86400 + }, "polling_frequency": { "type": "integer", "description": "How frequently the BOS operators check component state for needed actions. (in seconds)"