[
https://issues.apache.org/jira/browse/WHIRR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Alves updated WHIRR-243:
------------------------------
Attachment: WHIRR-243.patch
This patch provides a completed LogDryRunModule.
Andrei the test is incomplete (I have some other urgent matters today) but it
shows where we should change the jclouds property and where we can test the
correct behavior with LogDryRunModule.
Regarding what is correct behavior IMHO what could be done is:
- Either a bootstrap completely fails on some init script timeout-ing or
- Timeout-ing nodes are shutdown and removed from the pool of nodes that will
be configured or
- Simply wait until all is done (increase timeout)
> Allow to run component tests in memory
> --------------------------------------
>
> Key: WHIRR-243
> URL: https://issues.apache.org/jira/browse/WHIRR-243
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: David Alves
> Assignee: Adrian Cole
> Priority: Minor
> Attachments: WHIRR-243-LogOutput.txt,
> WHIRR-243-Mod-Delay-Init-Script-Return.log,
> WHIRR-243-Mod-Delay-Init-Script-Return.patch,
> WHIRR-243-only-LogDryRunModule.patch, WHIRR-243.patch, WHIRR-243.patch,
> WHIRR-243.patch, WHIRR-243.patch, WHIRR-243.patch, WHIRR-243.patch,
> WHIRR-243.patch, WHIRR-243.patch, WHIRR-243.patch
>
>
> While jclouds now features the awesome BYON mode it might be useful to be
> able to run compoenent and systems tests without jclouds.
> I tried jclouds stub features but unless I'm missing something (I might)
> there is no way of stubbing a compute service that allows to call
> runOnNodesMatching.
> So my idea is to alter ComputeServiceContextBuilder a bit to account for a
> new provider ("test") in which case an instance of a
> StubComputeServiceContext is returned (which features a StubComputeService
> internal class). This allows to make assertion regarding which nodes were
> started or not and on which order, which I think is useful.
--
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
