Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-3147

Allocator refactor

    XMLWordPrintableJSON

Details

    Description

      With new features such as dynamic reservation, persistent volume, quota, optimistic offers, it has been apparent that we need to refactor the allocator to

      1. solidify the API (e.g. consolidate updateSlave and updateAvailable)
      2. possibly move the offer generation to the allocator from the master
      3. support for allocator modules where the API involves returning libprocess::Future

      The sequence of implementation challenges for dynamic reservation master endpoints are captured in this document.

      Attachments

        Issue Links

          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MESOS-4553 Manage offers in allocator.

          • Major - Major loss of function.
          • Accepted

          Activity

            People

              Unassigned Unassigned
              mcypark Michael Park
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: