[
https://issues.apache.org/jira/browse/WHIRR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125033#comment-13125033
]
David Alves commented on WHIRR-243:
-----------------------------------
{quote}
As far as a know we don't track install script execution - we only worry about
provisioning (seeing the machine running)
{quote}
AFAIK that is not the case. JClouds actually keeps calling status on init
scripts until it receives exitCode 1. All init scripts must be done before
going into configuration phase.
The slightly modified LogDryRunModule (which delays the emission of exitCode=1
until 10 calls have been made) and the attached log illustrate this behavior.
Even with this modification the barrier still seems to work well, i.e., all
init scripts are finished before executing the configuration ones.
> 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-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
