aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mehrdad Nurolahzade (JIRA)" <>
Subject [jira] [Commented] (AURORA-1492) Improve "aurora update start" command output
Date Tue, 17 May 2016 18:34:13 GMT


Mehrdad Nurolahzade commented on AURORA-1492:

I can see that for killing job instances we do have a similar info message:

aurora job killall devcluster/www-data/prod/hello
 INFO] Killing tasks for job: devcluster/www-data/prod/hello
 INFO] Instances to be killed: [0]
Successfully killed instances [0]
Job killall succeeded

To improve consistency, I would suggest a similar info message like:

aurora update start devcluster/www-data/prod/hello ./aurora/examples/jobs/updated_hello_world.aurora

 INFO] Starting update for: hello
 INFO] Instances to be updated: 2
Job update has started. View your update progress at http://aurora.local:8081/scheduler/www-data/prod/hello/update/7709df5d-920a-4315-a2df-fc073916ae0b

> Improve "aurora update start" command output
> --------------------------------------------
>                 Key: AURORA-1492
>                 URL:
>             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

View raw message