aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raul Gutierrez Segales (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-34) Add an `aurora cluster` subcommand to automatically generate clusters.json
Date Mon, 13 Jan 2014 21:47:53 GMT

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

Raul Gutierrez Segales commented on AURORA-34:
----------------------------------------------

Would be nice if --zk could take a list of hosts for people who don't use DNS to discover
their ZK cluster, no?

> 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
>            Priority: Minor
>
> 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.1.5#6160)

Mime
View raw message