ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Magda (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-790) Cross-cloud IpFinder for nodes auto discovering
Date Tue, 28 Apr 2015 16:06:06 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517292#comment-14517292

Denis Magda commented on IGNITE-790:

Changes after the review:
- class renamed to TcpDiscoveryCloudIpFinder
- filtering out not running instances from the registered list
- removed discoveryPort from finder's configuration
- split a single test on cloud specific tests
- added java and config example to the doc

> Cross-cloud IpFinder for nodes auto discovering
> -----------------------------------------------
>                 Key: IGNITE-790
>                 URL: https://issues.apache.org/jira/browse/IGNITE-790
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>            Reporter: Denis Magda
>            Assignee: Denis Magda
>             Fix For: sprint-4
> The goal is to create an IpFinder that can be used with many cloud providers without
a necessity to create a vendor specific implementation.
> The IpFinder must discover Ignite nodes automatically.
> At least at the first iteration the workflow is the following:
> - the finder gets private and public (?) IP addresses (without port numbers) of all cloud
machines using corresponding jcloud API;
> - optionally the addresses may be filtered out by some predicate (elaborate lately);
> - the addresses returned in getRegisteredAddresses() as is, the underlying code will
add a valid port number;
> User is responsible for:
> - setting all required cloud specific parameters (credentials, secret key);
> - setting a port number that will be used by every Ignite node on every machine.
> Limitations:
> - only one Ignite node will run per a cloud virtual machine.
> When done, existed S3 and Google Cloud Storage implementations should be deprecated.

This message was sent by Atlassian JIRA

View raw message