Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-4512

ExecutionBroker scheduling and resource booking

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • SRCnet
    • Hide

      A key part of the ExecutionBroker design was that it would keep track of the available resources over and ensure that it did not offer more resources that are available for a given time period.

      If it makes an offer for 200 cpu cores for 2 hours starting in 10 minutes, the user can be confident that those resources will be available for that length of time.

      Reserving resources like this becomes more important the larger the task and the more resources it requires, but it also impact smaller shorter tasks. If a user requests a quick task with only 2 cores starting now, they want to be confident that their task will execute now, rather than having to wait because there is a larger long running task ahead of them in the queue.

      Show
      A key part of the ExecutionBroker design was that it would keep track of the available resources over and ensure that it did not offer more resources that are available for a given time period. If it makes an offer for 200 cpu cores for 2 hours starting in 10 minutes, the user can be confident that those resources will be available for that length of time. Reserving resources like this becomes more important the larger the task and the more resources it requires, but it also impact smaller shorter tasks. If a user requests a quick task with only 2 cores starting now, they want to be confident that their task will execute now, rather than having to wait because there is a larger long running task ahead of them in the queue.
    • Hide

      AC1: The repository includes a new version of the ExecutionBroker that includes time scheduling and resource reservations. 

      AC2: Demo showing time scheduling functionalities

      Show
      AC1: The repository includes a new version of the ExecutionBroker that includes time scheduling and resource reservations.  AC2: Demo showing time scheduling functionalities
    • 8
    • 0

    • PI24 - UNCOVERED

    • SRCNet0.x

    Description

      For PI23 we split ExecutionBroker into two parts to make it possible to implement in a single iteration. As a result, the current prototype omits the time scheduling and resource booking functionality described in the IVOA document.

      The current prototype does not take into account the requested start time or the expected load when it makes offers. It does not keep a record of how many resources have been allocated and it does not reserve resources for executions. As a result it may over commit the available resources, offering more tasks to execute that the resources can support. Leading to tasks being cancelled or left waiting in a queue. If you request for an execution that starts now, it will say yes, regardless of how many other tasks are already executing. If you request for an execution that starts tomorrow, it will say yes, regardless of how many other tasks are expected to be executing at that time.

      In this feature we will focuse on implementing the time scheduling and resource booking functionality.  The system will use a database to keep track of resources allocations over time, will allocate its offers from within a fixed quota of resources, rejecting requests that would exceed the quota. 

      Attachments

        Issue Links

          Child Of

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-4781 Distributed Data Computing v0.2 - Roadmap

          • Not Assigned - Priority is not assigned yet.
          • Funnel
          mentioned in

          Page Loading...

          Structure

            Activity

              People

                b.mort Mort, Ben
                S.SanchezExposito Sanchez Exposito, Susana
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 8.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete00.0
                  Total00.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel