Uploaded image for project: 'Optimization Framework'
  1. Optimization Framework
  2. OPTFRA-193

Extend HPA constraints to Service Candidates

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • None
    • None

      In our current data models, we capture the HPA as capabilities of the cloud instance, which naturally fits the match-making when spinning up VNFs for the first time. However, I was wondering if there is a case for picking an existing service instance based on the HPA capabilities. This would be relevant only if the same VNF is possibly instantiated with and without the HPA match - maybe because it was at some point an optional requirement from the vendor, but was subsequently made mandatory by the operators.

      This would mean that Homing should pick an existing service instance, based on whether it has an associated HPA capability or based on a simplifying assumption that it was instantiated in a cloud that has the required capability.

            Unassigned Unassigned
            snarayanan snarayanan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: