[
https://issues.apache.org/jira/browse/WHIRR-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483287#comment-13483287
]
Graham Gear edited comment on WHIRR-672 at 10/24/12 3:00 PM:
-------------------------------------------------------------
Attach an alternative implementation, which localises the patch to the public
host resolution code, not calling out to DNS in the case of a stub provider
spawned instance.
https://issues.apache.org/jira/secure/attachment/12550632/WHIRR-672_VERSION_3.patch
Note although this implementation is cleaner, it does use a private jClouds
API, which could be avoided if we were to expose the Cloud provider at layer
publicly accessible to the org.apache.whirr.Instance, eg
org.jclouds.compute.domain.NodeMetadata.
was (Author: graham.gear):
Attach an alternative implementation, which localises the patch to the
public host resolution code, not calling out to DNS in the case of a stub
provider spawned instance.
https://issues.apache.org/jira/secure/attachment/12550632/WHIRR-672_VERSION_3.patch
> Allow eager caching of instance hostname based on pre-provision instance
> metadata
> ----------------------------------------------------------------------------------
>
> Key: WHIRR-672
> URL: https://issues.apache.org/jira/browse/WHIRR-672
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: Graham Gear
> Assignee: Graham Gear
> Priority: Minor
> Attachments: WHIRR-672_VERSION_1.patch, WHIRR-672_VERSION_2.patch,
> WHIRR-672_VERSION_3.patch
>
>
> Allow eager caching of instance hostname based on pre-provision instance
> metadata.
> This would be nice when running the dry run test-harness against services
> which require host name lookups, avoiding long blocking timeouts on DNS with
> nonexistent hostnames, dramatically improving unit test run times.
> It is expected this pre-cache will only be executed by non-production code
> paths, eg unit tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
