[
https://issues.apache.org/jira/browse/WHIRR-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karel Vervaeke updated WHIRR-500:
---------------------------------
Attachment: WHIRR-500.patch
Attached a quick hack, I'm all for suggestions on how to do it better.
The yaml model doesn't give you much to work with, so I abused the 'tags'
functionality:
**Yaml
nodes:
- id: ubuntu1
hostname: 192.168.54.160
os_arch: x86
os_family: ubuntu
...
tags:
- tag1
- tag2
** recipe:
whirr.templates.role1+role2.hardwareId=tag1,tag2
-> Only nodes which have both 'tag1' and 'tag2' will be used.
If you use .hardwareId, you should use it on all instance-templates, otherwise
the tagged instances can get assigned to the wrong node.
ps: yay, WHIRR-500 ;-)
> Let users control which hardware is used for each instance template.
> --------------------------------------------------------------------
>
> Key: WHIRR-500
> URL: https://issues.apache.org/jira/browse/WHIRR-500
> Project: Whirr
> Issue Type: New Feature
> Components: core
> Reporter: Karel Vervaeke
> Assignee: Karel Vervaeke
> Priority: Minor
> Fix For: 0.8.0
>
> Attachments: WHIRR-500.patch
>
>
> For non-byon providers, you can use whirr.templates.role1+role2.hardwareId=foo
> For byon, the way roles are assigned to instances is indeterminate (it
> depends on the order of the keys in doAction(eventMap)).
> It would be great if the user could get control over this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
