You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Dan Norris (JIRA)" <ji...@apache.org> on 2014/05/15 05:50:14 UTC
[jira] [Assigned] (AURORA-34) Add an `aurora cluster` subcommand to
automatically generate clusters.json
[ https://issues.apache.org/jira/browse/AURORA-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Norris reassigned AURORA-34:
--------------------------------
Assignee: Dan Norris
> Add an `aurora cluster` subcommand to automatically generate clusters.json
> --------------------------------------------------------------------------
>
> Key: AURORA-34
> URL: https://issues.apache.org/jira/browse/AURORA-34
> Project: Aurora
> Issue Type: Story
> Components: Client
> Reporter: Kevin Sweeney
> Assignee: Dan Norris
> Priority: Minor
> Labels: newbie
>
> Right now a user needs to manually create a clusters.json and put it in {{~/.aurora/clusters.json}} in order to talk to a cluster. Make this process a little more friendly by adding a {{cluster}} subcommand to perform CRUD operations similar to git-remote.
> A sketch of how it might look:
> {noformat}
> # Create an entry in clusters.json
> aurora cluster add local --scheduler_uri localhost:8082
> aurora cluster add example --zk zookeeper.example.com --scheduler_zk_path /service/aurora/scheduler
> # List available clusters
> aurora cluster list
> # Verify an entry by calling getVersion
> aurora cluster ping local
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)