You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Chris Lambert (JIRA)" <ji...@apache.org> on 2014/09/23 20:44:35 UTC

[jira] [Updated] (AURORA-718) JobUpdateConfiguration should reflect work required for a job update

     [ https://issues.apache.org/jira/browse/AURORA-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Lambert updated AURORA-718:
---------------------------------
    Sprint: Aurora Q3 Sprint 3

> JobUpdateConfiguration should reflect work required for a job update
> --------------------------------------------------------------------
>
>                 Key: AURORA-718
>                 URL: https://issues.apache.org/jira/browse/AURORA-718
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Bill Farner
>            Assignee: Bill Farner
>
> JobUpdateConfiguration contains three fields to reflect the 'before' and 'after' state of a job: instanceCount, newTaskConfig, oldTaskConfigs.  These could be leveraged to do the same, but also show the 'actual work' required for the update.  For example, in an update that is scoped to specific instances, or where not all instances need to be modified (no-ops), these fields should indicate which instances the scheduler needs to modify.
> This ticket tracks a change to how oldTaskConfigs is computed.  AURORA-717 tracks conversion of the other two fields.



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