Commit 03ba47c0 authored by Mudassar Khan's avatar Mudassar Khan Committed by Giacomo Bernini
Browse files

update test cases of VNFFaultManagement-API as per SOL 002 version 5.1.1

parent 48c7ee09
Loading
Loading
Loading
Loading
+48 −1
Original line number Diff line number Diff line
@@ -23,7 +23,7 @@
              "oneOf": [
                {
                  "required": [
                    "vnfdId"
                    "vnfdIds"
                  ]
                },
                {
@@ -199,6 +199,53 @@
      "description": "String formatted according to IETF RFC 3986.\n",
      "type": "string"
    },
    "pmJobConnection": {
      "description": "An access information and interface information to monitor the FM of VNF instance by the VNFM.  This can include for instance certain interface endpoint URI together with necessary credentials to access it.\n",
      "type": "array",
      "items": {
        "description": "The MonitoringConnection shall follow the indications. * NOTE:\tThe VNFM can be made aware of monitoring connection information, including their identifiers to \n        be used by configuration means outside the scope of the present document (e.g. using relevant NFV-MANO management \n        APIs as defined in ETSI GS NFV-SOL 009). \n",
        "type": "object",
        "required": [
          "id",
          "monitoringType"
        ],
        "properties": {
          "id": {
            "description": "An identifier with the intention of being globally unique.\n",
            "type": "string"
          },
          "monitoringType": {
            "description": "Type of monitoring way. VALUES: \n  ΓÇó\tVIM_CISM\n  ΓÇó\tEXTERNAL\n  ΓÇó\tPAAS\n",
            "type": "string",
            "enum": [
              "VIM_CISM",
              "EXTERNAL",
              "PAAS"
            ]
          },
          "vimId": {
            "description": "An identifier with the intention of being globally unique.\n",
            "type": "string"
          },
          "paasServiceId": {
            "description": "An identifier with the intention of being globally unique.\n",
            "type": "string"
          },
          "interfaceInfo": {
            "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
            "type": "object"
          },
          "accessInfo": {
            "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
            "type": "object"
          },
          "extra": {
            "description": "A string defined in IETF RFC 8259.\n",
            "type": "string"
          }
        }
      }
    },
    "_links": {
      "description": "Links for this resource.\n",
      "type": "object",
+48 −1
Original line number Diff line number Diff line
@@ -25,7 +25,7 @@
                "oneOf": [
                  {
                    "required": [
                      "vnfdId"
                      "vnfdIds"
                    ]
                  },
                  {
@@ -201,6 +201,53 @@
        "description": "String formatted according to IETF RFC 3986.\n",
        "type": "string"
      },
      "pmJobConnection": {
        "description": "An access information and interface information to monitor the FM of VNF instance by the VNFM.  This can include for instance certain interface endpoint URI together with necessary credentials to access it.\n",
        "type": "array",
        "items": {
          "description": "The MonitoringConnection shall follow the indications. * NOTE:\tThe VNFM can be made aware of monitoring connection information, including their identifiers to \n        be used by configuration means outside the scope of the present document (e.g. using relevant NFV-MANO management \n        APIs as defined in ETSI GS NFV-SOL 009). \n",
          "type": "object",
          "required": [
            "id",
            "monitoringType"
          ],
          "properties": {
            "id": {
              "description": "An identifier with the intention of being globally unique.\n",
              "type": "string"
            },
            "monitoringType": {
              "description": "Type of monitoring way. VALUES: \n  ΓÇó\tVIM_CISM\n  ΓÇó\tEXTERNAL\n  ΓÇó\tPAAS\n",
              "type": "string",
              "enum": [
                "VIM_CISM",
                "EXTERNAL",
                "PAAS"
              ]
            },
            "vimId": {
              "description": "An identifier with the intention of being globally unique.\n",
              "type": "string"
            },
            "paasServiceId": {
              "description": "An identifier with the intention of being globally unique.\n",
              "type": "string"
            },
            "interfaceInfo": {
              "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
              "type": "object"
            },
            "accessInfo": {
              "description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
              "type": "object"
            },
            "extra": {
              "description": "A string defined in IETF RFC 8259.\n",
              "type": "string"
            }
          }
        }
      },
      "_links": {
        "description": "Links for this resource.\n",
        "type": "object",
+3 −3
Original line number Diff line number Diff line
@@ -153,11 +153,11 @@
      ]
    },
    "faultType": {
      "description": "Additional information to clarify the type of the fault. If the alarm is related to changes in the state of virtualised resources due to NFVI  operation and maintenance, this attribute shall be set to \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE _CHANGE\".\n",
      "description": "Additional information to clarify the type of the fault. Valid values applicable to specific Alarms are specified as \"Alarm definition identifier\"  values of the Alarm applicable to Ve-Vnfm reference point. If the alarm is related to changes in the state of virtualised resources due to NFVI  operation and maintenance, this attribute shall be set to \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE _CHANGE\".\n",
      "type": "string"
    },
    "probableCause": {
      "description": "Information about the probable cause of the fault. If the attribute \"faultType\" has the value ΓÇ£NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEΓÇ¥, the  permitted values are: \n  - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. physical maintenance/repair, \n    hypervisor software updates, etc.\n  - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n  - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g. to support energy\n    efficiency or resource usage optimization.\n",
      "description": "Information about the probable cause of the fault. Valid values applicable to specific Alarms are specified as \"Probable cause\"  values of the Alarm applicable to Ve-Vnfm reference point. If the attribute \"faultType\" has the value ΓÇ£NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEΓÇ¥, the  permitted values are: \n  - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. physical maintenance/repair, \n    hypervisor software updates, etc.\n  - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n  - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g. to support energy\n    efficiency or resource usage optimization.\n",
      "type": "string"
    },
    "isRootCause": {
@@ -173,7 +173,7 @@
      }
    },
    "faultDetails": {
      "description": "Provides additional information about the fault. See notes 1 and 2.\n",
      "description": "Provides additional information about the fault. See notes 1 and 2. Valid values applicable to specific Alarms are specified as \"Fault details\" values  of the Alarm applicable to Ve-Vnfm reference point.\n",
      "type": "array",
      "items": {
        "type": "string"
+3 −3
Original line number Diff line number Diff line
@@ -185,11 +185,11 @@
          ]
        },
        "faultType": {
          "description": "Additional information to clarify the type of the fault. If the alarm is related to changes in the state of virtualised resources due to NFVI  operation and maintenance, this attribute shall be set to \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE _CHANGE\".\n",
          "description": "Additional information to clarify the type of the fault. Valid values applicable to specific Alarms are specified as \"Alarm definition identifier\"  values of the Alarm applicable to Ve-Vnfm reference point. If the alarm is related to changes in the state of virtualised resources due to NFVI  operation and maintenance, this attribute shall be set to \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE _CHANGE\".\n",
          "type": "string"
        },
        "probableCause": {
          "description": "Information about the probable cause of the fault. If the attribute \"faultType\" has the value ΓÇ£NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEΓÇ¥, the  permitted values are: \n  - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. physical maintenance/repair, \n    hypervisor software updates, etc.\n  - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n  - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g. to support energy\n    efficiency or resource usage optimization.\n",
          "description": "Information about the probable cause of the fault. Valid values applicable to specific Alarms are specified as \"Probable cause\"  values of the Alarm applicable to Ve-Vnfm reference point. If the attribute \"faultType\" has the value ΓÇ£NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEΓÇ¥, the  permitted values are: \n  - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. physical maintenance/repair, \n    hypervisor software updates, etc.\n  - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n  - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g. to support energy\n    efficiency or resource usage optimization.\n",
          "type": "string"
        },
        "isRootCause": {
@@ -205,7 +205,7 @@
          }
        },
        "faultDetails": {
          "description": "Provides additional information about the fault. See notes 1 and 2.\n",
          "description": "Provides additional information about the fault. See notes 1 and 2. Valid values applicable to specific Alarms are specified as \"Fault details\" values  of the Alarm applicable to Ve-Vnfm reference point.\n",
          "type": "array",
          "items": {
            "type": "string"
+3 −3
Original line number Diff line number Diff line
@@ -155,11 +155,11 @@
        ]
      },
      "faultType": {
        "description": "Additional information to clarify the type of the fault. If the alarm is related to changes in the state of virtualised resources due to NFVI  operation and maintenance, this attribute shall be set to \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE _CHANGE\".\n",
        "description": "Additional information to clarify the type of the fault. Valid values applicable to specific Alarms are specified as \"Alarm definition identifier\"  values of the Alarm applicable to Ve-Vnfm reference point. If the alarm is related to changes in the state of virtualised resources due to NFVI  operation and maintenance, this attribute shall be set to \"NFVI_OAM_VIRTUALISED_RESOURCE_STATE _CHANGE\".\n",
        "type": "string"
      },
      "probableCause": {
        "description": "Information about the probable cause of the fault. If the attribute \"faultType\" has the value ΓÇ£NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEΓÇ¥, the  permitted values are: \n  - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. physical maintenance/repair, \n    hypervisor software updates, etc.\n  - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n  - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g. to support energy\n    efficiency or resource usage optimization.\n",
        "description": "Information about the probable cause of the fault. Valid values applicable to specific Alarms are specified as \"Probable cause\"  values of the Alarm applicable to Ve-Vnfm reference point. If the attribute \"faultType\" has the value ΓÇ£NFVI_OAM_VIRTUALISED_RESOURCE_STATE_CHANGEΓÇ¥, the  permitted values are: \n  - \"NFVI_COMPONENT_MAINTENANCE\": Maintenance of NFVI components, e.g. physical maintenance/repair, \n    hypervisor software updates, etc.\n  - \"NFVI_COMPONENT_EVACUATION\": Evacuation of physical hosts.\n  - \"NFVI_COMPONENT_OPTIMIZATION\": Operation and management of NFVI resources, e.g. to support energy\n    efficiency or resource usage optimization.\n",
        "type": "string"
      },
      "isRootCause": {
@@ -175,7 +175,7 @@
        }
      },
      "faultDetails": {
        "description": "Provides additional information about the fault. See notes 1 and 2.\n",
        "description": "Provides additional information about the fault. See notes 1 and 2. Valid values applicable to specific Alarms are specified as \"Fault details\" values  of the Alarm applicable to Ve-Vnfm reference point.\n",
        "type": "array",
        "items": {
          "type": "string"