You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aurora.apache.org by "Kevin Sweeney (JIRA)" <ji...@apache.org> on 2014/01/13 23:27:50 UTC

[jira] [Created] (AURORA-35) rework Python SchedulerClient

Kevin Sweeney created AURORA-35:
-----------------------------------

             Summary: rework Python SchedulerClient
                 Key: AURORA-35
                 URL: https://issues.apache.org/jira/browse/AURORA-35
             Project: Aurora
          Issue Type: Task
          Components: Client, Technical Debt
            Reporter: Kevin Sweeney
            Priority: Minor


We need a better URI scheme for locating schedulers. Right now we conflate cluster name with cluster location (e.g. ablocal, localhost:1234, smf1-test)
SchedulerClient is also poorly factored, e.g. LocalSchedulerClient, ZookeeperSchedulerClient. Instead there should be separate local / zookeeper resolvers that then feed into a non-inherited SchedulerClient.
Also, most people should be interacting with SchedulerProxy. It's likely that SchedulerProxy/SchedulerClient should be merged together, and possibly the session acquisition should be plumbed into the AuroraClientAPI.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)