[
https://issues.apache.org/jira/browse/WHIRR-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041412#comment-13041412
]
Tom White commented on WHIRR-318:
---------------------------------
This seems like a good direction to me. I assume that it would be an
alternative to properties file.
Rather than carrying over the role1+role2 notation, which can get awkward, it
would be better to use a more natural YAML syntax (or JSON, if we use that).
Something like
{noformat}
templates:
hadoop-master:
roles:
- hadoop-namenode
- hadoop-jobtracker
image-id: ...
{noformat}
> More extensible cluster spec file format
> ----------------------------------------
>
> Key: WHIRR-318
> URL: https://issues.apache.org/jira/browse/WHIRR-318
> Project: Whirr
> Issue Type: Improvement
> Reporter: Andrei Savu
> Attachments: hadoop.yml
>
>
> We are slowly getting to the point were our ability to improve Whirr will be
> limited by the cluster spec format. I'm opening this issue so that we can
> start to think about a new format that it's going to be more flexible.
> Some of the characteristics of the new format should be:
> * low verbosity and easily editable using standard text editors. (e.g yaml)
> * easy to parse using existing libraries (e.g. snakeyaml)
> * should allow values to be overridden as CLI parameters (e.g yaml
> liniarization - elasticsearch is doing this).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
