aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Renan DelValle (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AURORA-1288) Design for supporting custom executor
Date Thu, 25 Jun 2015 03:23:04 GMT

    [ https://issues.apache.org/jira/browse/AURORA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14600531#comment-14600531
] 

Renan DelValle edited comment on AURORA-1288 at 6/25/15 3:22 AM:
-----------------------------------------------------------------

Right, my line of thought was that Thermos is kind of the "default" custom executor for Aurora
right now. It made sense in my head to give it a special case. I guess, to me, it's more of
an issue as to wether Aurora will be configured out of the box for Thermos or something else
(like the Command Executor) and how this will be accomplished.

In terms of using an ExecutorType enumerator, I was thinking of having only those 3 cases
included (maybe even 2 if it is decided that Thermos will fall under the Custom moniker).
 The idea is that, for any custom executor, only the path is passed from the client side,
making every single executor that is not thermos, or command executor, fall under the custom
umbrella.* I think it's another point where we should come to a consensus of how we want this
to implement this before moving forward.

Let me know if I'm any of this doesn't make sense. 

*This assumes the custom executor is able to use the information currently generated by the
MesosTaskFactory.



was (Author: rdelvalle):
Right, my line of thought was that Thermos is kind of the "default" custom executor for Aurora
right now. It made sense in my head to give it a special case. I guess, to me, its more of
an issue as to wether Aurora will be configured out of the box for Thermos or something else
(like the Command Executor) and how this will be accomplished.

In terms of using an ExecutorType enumerator, I was thinking of having only those 3 cases
included (maybe even 2 if it is decided that Thermos will fall under the Custom moniker).
 The idea is that, for any custom executor, only the path is passed from the client side,
making every single executor that is not thermos, or command executor, fall under the custom
umbrella.* I think it's another point where we should come to a consensus of how we want this
to implement this before moving forward.

Let me know if I'm any of this doesn't make sense. 

*This assumes the custom executor is able to use the information currently generated by the
MesosTaskFactory.


> Design for supporting custom executor
> -------------------------------------
>
>                 Key: AURORA-1288
>                 URL: https://issues.apache.org/jira/browse/AURORA-1288
>             Project: Aurora
>          Issue Type: Task
>            Reporter: Meghdoot Bhattacharya
>
> The goal is to capture the list of changes in the client and the scheduler required to
support any executor other than thermos. This will help non thermos use cases to adopt aurora
easily.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message