[
https://issues.apache.org/jira/browse/WHIRR-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated WHIRR-75:
---------------------------
Attachment: WHIRR-75.patch
This is quite a big change, but should make Whirr easier to use and more
flexible. Summary of changes:
* Commons Configuration is now used for managing configuration. This is shared
between tests and the CLI, which means there are fewer places to change when
adding new configuration options.
* ClusterSpec is now immutable and backed by a configuration object.
* The CLI is simplified. Service and cluster names are set using options, and
it's possible to bundle up all the options into a properties file, like so:
whirr launch-cluster --config mycluster.properties. (This makes it easy to
define clusters with different properties - e.g. a 3-node ZK cluster vs a
5-node cross-DC cluster.) You can still specify options on the command line,
and these take precedence over those in the config.
* Tests have a properties file to drive them. This makes it easy to run the
tests with overridden settings (using -Dconfig=mycluster.properties, I use this
to set whirr.client-cidrs, for example), and reduces the amount of code
duplication for creating a ClusterSpec object.
All tests pass.
> Use Commons Configuration to manage cluster specs
> -------------------------------------------------
>
> Key: WHIRR-75
> URL: https://issues.apache.org/jira/browse/WHIRR-75
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.1.0
>
> Attachments: WHIRR-75.patch
>
>
> Apache Commons Configuration
> (http://commons.apache.org/configuration/index.html) would be useful to share
> configuration information between the CLI and the tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
