[jira] [Updated] (IGNITE-14092) IP Finder API
[ https://issues.apache.org/jira/browse/IGNITE-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-14092: - Ignite Flags: (was: Docs Required,Release Notes Required) > IP Finder API > - > > Key: IGNITE-14092 > URL: https://issues.apache.org/jira/browse/IGNITE-14092 > Project: Ignite > Issue Type: Task > Components: networking >Reporter: Anton Kalashnikov >Priority: Major > Labels: ignite-3 > > Create a service interface that provides the initial set of addresses of > cluster members to a joining node. This service should provide an abstraction > over multiple possible configuration mechanisms, like manual static > configuration, Kubernetes service discovery, cloud environment, etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14092) IP Finder API
[ https://issues.apache.org/jira/browse/IGNITE-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-14092: - Description: Create a service interface that provides the initial set of addresses of cluster members to a joining node. This service should provide an abstraction over multiple possible configuration mechanisms, like manual static configuration, Kubernetes service discovery, cloud environment, etc. (was: IP finder service is needed on a network level to allow nodes to find existing clusters and avoid excessive manual configuration. In some cases like cloud environments manual configuration of all cluster's nodes is impractical. Special implementation of IP Finder solves this problem. In this task we need to design IP Finder API suitable for different use-cases and develop a simplistic static implementation.) > IP Finder API > - > > Key: IGNITE-14092 > URL: https://issues.apache.org/jira/browse/IGNITE-14092 > Project: Ignite > Issue Type: Task > Components: networking >Reporter: Anton Kalashnikov >Priority: Major > Labels: ignite-3 > > Create a service interface that provides the initial set of addresses of > cluster members to a joining node. This service should provide an abstraction > over multiple possible configuration mechanisms, like manual static > configuration, Kubernetes service discovery, cloud environment, etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14092) IP Finder API
[ https://issues.apache.org/jira/browse/IGNITE-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-14092: - Summary: IP Finder API (was: IP Finder API and first implementation to locate and join existing cluster) > IP Finder API > - > > Key: IGNITE-14092 > URL: https://issues.apache.org/jira/browse/IGNITE-14092 > Project: Ignite > Issue Type: Task > Components: networking >Reporter: Anton Kalashnikov >Priority: Major > Labels: ignite-3 > > IP finder service is needed on a network level to allow nodes to find > existing clusters and avoid excessive manual configuration. > In some cases like cloud environments manual configuration of all cluster's > nodes is impractical. Special implementation of IP Finder solves this problem. > In this task we need to design IP Finder API suitable for different use-cases > and develop a simplistic static implementation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14092) IP Finder API and first implementation to locate and join existing cluster
[ https://issues.apache.org/jira/browse/IGNITE-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-14092: - Component/s: networking > IP Finder API and first implementation to locate and join existing cluster > -- > > Key: IGNITE-14092 > URL: https://issues.apache.org/jira/browse/IGNITE-14092 > Project: Ignite > Issue Type: Task > Components: networking >Reporter: Anton Kalashnikov >Priority: Major > Labels: iep-66, ignite-3 > > IP finder service is needed on a network level to allow nodes to find > existing clusters and avoid excessive manual configuration. > In some cases like cloud environments manual configuration of all cluster's > nodes is impractical. Special implementation of IP Finder solves this problem. > In this task we need to design IP Finder API suitable for different use-cases > and develop a simplistic static implementation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14092) IP Finder API and first implementation to locate and join existing cluster
[ https://issues.apache.org/jira/browse/IGNITE-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-14092: - Labels: ignite-3 (was: iep-66 ignite-3) > IP Finder API and first implementation to locate and join existing cluster > -- > > Key: IGNITE-14092 > URL: https://issues.apache.org/jira/browse/IGNITE-14092 > Project: Ignite > Issue Type: Task > Components: networking >Reporter: Anton Kalashnikov >Priority: Major > Labels: ignite-3 > > IP finder service is needed on a network level to allow nodes to find > existing clusters and avoid excessive manual configuration. > In some cases like cloud environments manual configuration of all cluster's > nodes is impractical. Special implementation of IP Finder solves this problem. > In this task we need to design IP Finder API suitable for different use-cases > and develop a simplistic static implementation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14092) IP Finder API and first implementation to locate and join existing cluster
[ https://issues.apache.org/jira/browse/IGNITE-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-14092: - Fix Version/s: (was: 3.0.0-alpha3) > IP Finder API and first implementation to locate and join existing cluster > -- > > Key: IGNITE-14092 > URL: https://issues.apache.org/jira/browse/IGNITE-14092 > Project: Ignite > Issue Type: Task >Reporter: Anton Kalashnikov >Priority: Major > Labels: iep-66, ignite-3 > > IP finder service is needed on a network level to allow nodes to find > existing clusters and avoid excessive manual configuration. > In some cases like cloud environments manual configuration of all cluster's > nodes is impractical. Special implementation of IP Finder solves this problem. > In this task we need to design IP Finder API suitable for different use-cases > and develop a simplistic static implementation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14092) IP Finder API and first implementation to locate and join existing cluster
[ https://issues.apache.org/jira/browse/IGNITE-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-14092: - Parent: (was: IGNITE-14081) Issue Type: Task (was: Sub-task) > IP Finder API and first implementation to locate and join existing cluster > -- > > Key: IGNITE-14092 > URL: https://issues.apache.org/jira/browse/IGNITE-14092 > Project: Ignite > Issue Type: Task >Reporter: Anton Kalashnikov >Priority: Major > Labels: iep-66, ignite-3 > Fix For: 3.0.0-alpha3 > > > IP finder service is needed on a network level to allow nodes to find > existing clusters and avoid excessive manual configuration. > In some cases like cloud environments manual configuration of all cluster's > nodes is impractical. Special implementation of IP Finder solves this problem. > In this task we need to design IP Finder API suitable for different use-cases > and develop a simplistic static implementation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14092) IP Finder API and first implementation to locate and join existing cluster
[ https://issues.apache.org/jira/browse/IGNITE-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-14092: - Description: IP finder service is needed on a network level to allow nodes to find existing clusters and avoid excessive manual configuration. In some cases like cloud environments manual configuration of all cluster's nodes is impractical. Special implementation of IP Finder solves this problem. In this task we need to design IP Finder API suitable for different use-cases and develop a simplistic static implementation. was:IP finder working on a network level is needed to automate node join process to existing cluster: instead of configuring each cluster node manually > IP Finder API and first implementation to locate and join existing cluster > -- > > Key: IGNITE-14092 > URL: https://issues.apache.org/jira/browse/IGNITE-14092 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Kalashnikov >Priority: Major > Labels: iep-66, ignite-3 > Fix For: 3.0.0-alpha3 > > > IP finder service is needed on a network level to allow nodes to find > existing clusters and avoid excessive manual configuration. > In some cases like cloud environments manual configuration of all cluster's > nodes is impractical. Special implementation of IP Finder solves this problem. > In this task we need to design IP Finder API suitable for different use-cases > and develop a simplistic static implementation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14092) IP Finder API and first implementation to locate and join existing cluster
[ https://issues.apache.org/jira/browse/IGNITE-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-14092: - Summary: IP Finder API and first implementation to locate and join existing cluster (was: Simplistic IP Finder to locate and join existing cluster) > IP Finder API and first implementation to locate and join existing cluster > -- > > Key: IGNITE-14092 > URL: https://issues.apache.org/jira/browse/IGNITE-14092 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Kalashnikov >Priority: Major > Labels: iep-66, ignite-3 > Fix For: 3.0.0-alpha3 > > > IP finder working on a network level is needed to automate node join process > to existing cluster: instead of configuring each cluster node manually -- This message was sent by Atlassian Jira (v8.3.4#803005)
