Commits on Apr 19, 2024

1. Changing Discovery & PeeringCandidate CRDs behaviour (#1) …

   1.PeeringCandidate CR has no longer Reserved flag
   2.Discovery CRD keeps a matching PC list in its status rather than a single PC.
   3. Removing PeeringCandidate info from Solver status.
   4. The Discovery controller only creates PC for found flavors. It no longers auto-select a PC for reservation.
   5. The Discovery controller returns a list of PC in its status, no longer a single (reserved) PC.
   5. The Reservation controller first checks if its associated peeringCandidate it is available. If so, it makes it anavailable and goes ahead; otherwise it fails.
   6. The association between a Solver and a PC is now available only at the PC CR through spec.solverID; we no longer have any info of the PC inside the Solver CR. Because of this, we no longer have logic handling PC inside the Solver controller.
   
   * adjusting CRD creation functions and PC list creation in Discovery controller
   
   * bug fix
   
   * deleting useless config files
   
   * fixing discovery controller misbehaviour
   
   * bug fix: adding PC Spec update into reservtion controller
   
   * adding creation time info into PC status at creation time
   
   * restore default solver sample
   
   * bug fix: parse flavour & forgePeeringCandidate
   
   cleaning up code
   
   second clean up
   
   third clean up for merge
   
   cleaning up the code
   
   removing useless file
   
   fix artifacts generation
   
   fix comment for linting
   
   second fix comment for linting
   
   code clean up

   

   fracappa committed Apr 19, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 5b921ec
   • Browse repository at this point

   Copy the full SHA

   5b921ec View commit details

   Browse the repository at this point in the history