aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Khutornenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1492) Improve "aurora update start" command output
Date Mon, 14 Sep 2015 21:38:45 GMT

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

Maxim Khutornenko commented on AURORA-1492:
-------------------------------------------

I don't necessarily consider this as echoing. There are plenty of cases when the outcome of
the command is unknown ahead of time until the diff is calculated. Sure, in case of something
like {{aurora update start devcluster/www-data/prod/hello/0}} the output may appear redundant
but in case of a more generic (e.g.: no instance spec) or more complex (e.g.:/0,1-10,123,150-178)
spec having something like "12 instances are going to be updated" would clearly help to measure
the impact. 

> Improve "aurora update start" command output
> --------------------------------------------
>
>                 Key: AURORA-1492
>                 URL: https://issues.apache.org/jira/browse/AURORA-1492
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Maxim Khutornenko
>            Priority: Minor
>              Labels: newbie
>
> Customer feedback when trying to update a single job instance:
> {quote}
> It would provide peace of mind if somewhere in the output of {{aurora update start}}
it said "1 of X instances of <job_key> will be updated" just so that I knew that I didn't
mess up the command.
> {quote}
> The diff details are already available in the {{startJobUpdate}} rpc, so reporting the
above should be trivial.



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

Mime
View raw message