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

Scheduler API v1

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Epic
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.24.0
    • None
    • Scheduler API v1

    Description

      Currently Mesos frameworks (schedulers and executors) interact with Mesos (masters and slaves) via drivers provided by Mesos. While the driver helped in providing some common functionality for all frameworks (master detection, authentication, validation etc), it has several drawbacks.

      --> Frameworks need to depend on a native library which makes their build/deploy process cumbersome.

      --> Pure language frameworks cannot use off the shelf libraries to interact with the undocumented API used by the driver.

      --> Makes it hard for developers to implement new APIs (lot of boiler plate code to write).

      This proposal is for Mesos to provide a well documented public HTTP API that frameworks (and maybe operators) can use to interact with Mesos.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            marco-mesos Marco Massenzio
            vinodkone Vinod Kone
            Votes:
            2 Vote for this issue
            Watchers:
            19 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment