402 advance scheduling improvements

[kthare10]

#402
Changes Made:

• Orchestrator Update: Enhanced to query resources from the Broker’s BQM at level = 0, providing full capacity details of testbed resources. This information is automatically refreshed every 30 minutes by default.

• Advanced Scheduling:

  • API Enhancement: The API now allows specifying a future time range by passing start, end, and the lifetime of the slice (in hours).
  • Time Range: The specified time range (start and end) represents the interval within which the ControlFramework checks for resource availability for the requested lifetime duration.
  • Asynchronous Processing: Requests for future slices are handled asynchronously to enhance performance. Processing them synchronously could increase response time.
  • AdvanceSchedulingThread:
    • Attempts to determine a feasible start time for the requested resources within the specified time interval (start-end).
    • If a start time is found, the slice is scheduled at that time. Users will see this update as fablib submit periodically polls for slice status.
    • If no start time is found, the request is processed with the original start time and will fail with an "Insufficient resources" error if resources are unavailable.