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

Posted to dev@aurora.apache.org by "Mark Chu-Carroll (JIRA)" <ji...@apache.org> on 2014/01/23 23:23:40 UTC

[jira] [Updated] (AURORA-76) Implement bridging for clientv2 command line framework.

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

Mark Chu-Carroll updated AURORA-76:
-----------------------------------

    Summary: Implement bridging for clientv2 command line framework.  (was: Implement bridging framework for clientv2 command line.)

> Implement bridging for clientv2 command line framework.
> -------------------------------------------------------
>
>                 Key: AURORA-76
>                 URL: https://issues.apache.org/jira/browse/AURORA-76
>             Project: Aurora
>          Issue Type: Task
>          Components: Client
>            Reporter: Mark Chu-Carroll
>            Assignee: Mark Chu-Carroll
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> To eventually start supporting deployment of clientv2, and to help users gradually migrate to v2, we need to have a mechanism in the command-line processing to take commands that aren't recognized by the v2 client, and pass them to the v1 client for processing.
> So running "aurora list_jobs example" will run the client v1 "list_jobs" command; running "aurora status a/b/c/d" will run the v1 "status" command, and running "aurora job status a/b/c/d" will run the v2 status command.



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