Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


    1. IF

      1. VNF specific HealthCheck is available on the VNF, execute the VNF HealthCheck on the VNF:

        1. Connect to the VNF via (REST, Chef or Ansible) via the endpoint configured in the APPC CDT Tool.

        2. Initiate the VNF HealthCheck on the VNF.

    2. ELSE:

      1. APPC will obtain VNF details from A&AI
      1. Including:
        1. vserver details in order to enable checking each VM/VNFC in the VNF
      2. APPC performs HealthCheck on each vserver via Cloud Provider API
      3. Obtain Cloud Provider details.
      4. Connect to the Cloud Provider for each VM/VNFC
        1. I.e. for OpenStack Compute API:
          1. Show Server Details
          2. /servers/{server_id} /“OS-EXT-STS:vm_state”
        2. Mark VM/VNFC Failed marking the state.
        3. If any state other than “active” the HealthCheck for the VM/VNFC will be marked failed.
      5. IF ANY VM/VNFC is in a failed state the overall HealthCheck of the VNF will return failed along with the failure reason in the HealthCheck response payload.
  • Response:

    • VNF level HealthCheck response will:

    1. Conform to the APPC LCM Response format per the APPC LCM API Guide.
    2. Return Success/Failed status code as well as status code message (APPC LCM Response includes a “status” section with subsections of “code” and “message.”
    3. Include the Failed VM(s)/VNFC(s) details in the Response Payload.
    4. Any parameters/values returned from the VM/VNF should be returned as name/value pairs.

VM Level HealthCheck

  • Request:

...

    1. Return Success/Failed status code as well as status code message (APPC LCM Response includes a “status” section with subsections of “code” and “message.”
    2. Include the Failed VM/VNFC details in the Response Payload.
    3. Any parameters/values returned from the VM/VNF should be returned as name/value pairs.

Backward Compatibility

  • The current proposal is to develop a new API and persist the existing HealthCheck API in order to support the integrity of the current HealthCheck.

References