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

Custom allocators should implement Allocator instead of AllocatorProcess

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.23.0
    • allocation

    Description

      Currently new allocation policies can be added by implementing AllocatorProcess interface, while Allocator class is a thin wrapper around it. This architecture may be not very favourable, because it imposes restriction on how allocators should be implemented. Additionally, the current design is not consistent with other pluggable—or potentially pluggable—Mesos components, e.g. Isolator, Authenticator.

      As we are moving to modularizing the allocator, this ticket aims to change the way we implement allocation policies and instantiate allocators. Allocator tests and MockAllocatorProcess will be affected as well.

      Attachments

        Issue Links

          is depended upon by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MESOS-2160 Add support for allocator modules

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. MESOS-2286 Simplify the allocator architecture

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Activity

            People

              alexr Alex R
              alexr Alex R
              Niklas Quarfot Nielsen Niklas Quarfot Nielsen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: