Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-1155

[Spike] Investigate changes to simplify cores/sockets normalization per system

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: Normal Normal
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      As a swatch developer, I'd like to simplify the cores/sockets normalization, so that I can remove redundant and confusing fields/columns.

      Currently:

      • some normalization of the cores/sockets values happens in a central place (FactNormalizer), and is recorded in instance_measurements; e.g. setting effective cores/sockets to 0 based on the selected unit for OpenShift hosts.
      • some normalization happens in the product-specific usage collector (e.g. unmapped guests being mapped to 1 socket) and is recorded in host_tally_buckets.
      • some normalization happens in both places (marketplace instances having effectively 0 sockets/cores)

      This can lead to conflicting values for sockets/cores between the tables, and is quite confusing.

      In order to resolve this, we need to update the normalization to move the sockets/cores normalization logic to a more central place, and perform in the product only categorization logic and in-the-box logic.

      QE: added for design review. 

       DONE

      • Create a design document outlining proposed changes, review with team
      • Create cards based on review

              Unassigned Unassigned
              khowell@redhat.com Kevin Howell
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: