[
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
Here's my first re-attempt.
Couple of issues (the codebase has changed quite a lot since then)
- Once upon a time there was a complete test and other tests that used this
(this was lost ) so bear with me while I try to rebuild things.
- I added a simple test that launches a stub cluster and tests that two scripts
were executed on one (stub) node. The test is failing because the map returns
two entries instead of one because NodeMetadata's equals contract says that two
nodes are different if the credentials are different. Is this correct?
- Also before RunScriptOnNodeAsInitScriptUsingSsh used to have a name which was
nice to see which scripts were being ran where, but apparently that is no
longer the case.
- Finally aside from the main changes (to ComputeCache's wiring) there are two
additional changes to BootstrapClusterAction and ConfigureClusterAction that
name the tasks accordingly. This change was introduced by adrian with some
purpose. Do you remember which adrian?
> 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-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
>
>
> 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
