[jira] [Updated] (CASSANDRA-15337) Document usage of Ec2Snitch for multiple regions cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-15337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Haddad updated CASSANDRA-15337:
---
Fix Version/s: 4.0-alpha
Source Control Link:
https://github.com/apache/cassandra/commit/03424b4fd728cb3e97be30117a03532f37459858
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed, thanks!
> Document usage of Ec2Snitch for multiple regions cluster
>
>
> Key: CASSANDRA-15337
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15337
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation/Website
>Reporter: Serban Teodorescu
>Assignee: Serban Teodorescu
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ec2MultiRegionSnitch was (probably) done because it was not possible in AWS
> to have intra-region VPC peering. This changed pin 2017, see [AWS
> announcement|https://aws.amazon.com/about-aws/whats-new/2017/11/announcing-support-for-inter-region-vpc-peering/]
> (and extended with 9 more regions in 2018, see
> [link|https://aws.amazon.com/about-aws/whats-new/2018/02/inter-region-vpc-peering-is-now-available-in-nine-additional-aws-regions/]):
> {quote}Inter-Region VPC Peering allows VPC resources like EC2 instances[...]
> running in different AWS regions to communicate with each other using private
> IP addresses, without requiring gateways, VPN connections or separate network
> appliances.
> {quote}
> Since the datacenter/rack names are loaded in Ec2Snitch using AWS API there
> is no reason why this snitch would not work in a multi-datacenter setup. I
> tested and used this in a production environment. So the documentation should
> be changed to include this usage.
> Proposed change:
> [https://github.com/apache/cassandra/compare/trunk...serban21:15337-trunk]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15337) Document usage of Ec2Snitch for multiple regions cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-15337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Haddad updated CASSANDRA-15337:
---
Reviewers: Jon Haddad, Jon Haddad (was: Jon Haddad)
Jon Haddad, Jon Haddad (was: Jon Haddad)
Status: Review In Progress (was: Patch Available)
> Document usage of Ec2Snitch for multiple regions cluster
>
>
> Key: CASSANDRA-15337
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15337
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation/Website
>Reporter: Serban Teodorescu
>Assignee: Serban Teodorescu
>Priority: Normal
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ec2MultiRegionSnitch was (probably) done because it was not possible in AWS
> to have intra-region VPC peering. This changed pin 2017, see [AWS
> announcement|https://aws.amazon.com/about-aws/whats-new/2017/11/announcing-support-for-inter-region-vpc-peering/]
> (and extended with 9 more regions in 2018, see
> [link|https://aws.amazon.com/about-aws/whats-new/2018/02/inter-region-vpc-peering-is-now-available-in-nine-additional-aws-regions/]):
> {quote}Inter-Region VPC Peering allows VPC resources like EC2 instances[...]
> running in different AWS regions to communicate with each other using private
> IP addresses, without requiring gateways, VPN connections or separate network
> appliances.
> {quote}
> Since the datacenter/rack names are loaded in Ec2Snitch using AWS API there
> is no reason why this snitch would not work in a multi-datacenter setup. I
> tested and used this in a production environment. So the documentation should
> be changed to include this usage.
> Proposed change:
> [https://github.com/apache/cassandra/compare/trunk...serban21:15337-trunk]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15337) Document usage of Ec2Snitch for multiple regions cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-15337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Haddad updated CASSANDRA-15337:
---
Status: Ready to Commit (was: Review In Progress)
> Document usage of Ec2Snitch for multiple regions cluster
>
>
> Key: CASSANDRA-15337
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15337
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation/Website
>Reporter: Serban Teodorescu
>Assignee: Serban Teodorescu
>Priority: Normal
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ec2MultiRegionSnitch was (probably) done because it was not possible in AWS
> to have intra-region VPC peering. This changed pin 2017, see [AWS
> announcement|https://aws.amazon.com/about-aws/whats-new/2017/11/announcing-support-for-inter-region-vpc-peering/]
> (and extended with 9 more regions in 2018, see
> [link|https://aws.amazon.com/about-aws/whats-new/2018/02/inter-region-vpc-peering-is-now-available-in-nine-additional-aws-regions/]):
> {quote}Inter-Region VPC Peering allows VPC resources like EC2 instances[...]
> running in different AWS regions to communicate with each other using private
> IP addresses, without requiring gateways, VPN connections or separate network
> appliances.
> {quote}
> Since the datacenter/rack names are loaded in Ec2Snitch using AWS API there
> is no reason why this snitch would not work in a multi-datacenter setup. I
> tested and used this in a production environment. So the documentation should
> be changed to include this usage.
> Proposed change:
> [https://github.com/apache/cassandra/compare/trunk...serban21:15337-trunk]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15337) Document usage of Ec2Snitch for multiple regions cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-15337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Haddad updated CASSANDRA-15337:
---
Test and Documentation Plan: CI
Status: Patch Available (was: Open)
> Document usage of Ec2Snitch for multiple regions cluster
>
>
> Key: CASSANDRA-15337
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15337
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation/Website
>Reporter: Serban Teodorescu
>Assignee: Serban Teodorescu
>Priority: Normal
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ec2MultiRegionSnitch was (probably) done because it was not possible in AWS
> to have intra-region VPC peering. This changed pin 2017, see [AWS
> announcement|https://aws.amazon.com/about-aws/whats-new/2017/11/announcing-support-for-inter-region-vpc-peering/]
> (and extended with 9 more regions in 2018, see
> [link|https://aws.amazon.com/about-aws/whats-new/2018/02/inter-region-vpc-peering-is-now-available-in-nine-additional-aws-regions/]):
> {quote}Inter-Region VPC Peering allows VPC resources like EC2 instances[...]
> running in different AWS regions to communicate with each other using private
> IP addresses, without requiring gateways, VPN connections or separate network
> appliances.
> {quote}
> Since the datacenter/rack names are loaded in Ec2Snitch using AWS API there
> is no reason why this snitch would not work in a multi-datacenter setup. I
> tested and used this in a production environment. So the documentation should
> be changed to include this usage.
> Proposed change:
> [https://github.com/apache/cassandra/compare/trunk...serban21:15337-trunk]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15337) Document usage of Ec2Snitch for multiple regions cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-15337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRA-15337:
---
Labels: pull-request-available (was: )
> Document usage of Ec2Snitch for multiple regions cluster
>
>
> Key: CASSANDRA-15337
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15337
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation/Website
>Reporter: Serban Teodorescu
>Assignee: Serban Teodorescu
>Priority: Normal
> Labels: pull-request-available
>
> Ec2MultiRegionSnitch was (probably) done because it was not possible in AWS
> to have intra-region VPC peering. This changed pin 2017, see [AWS
> announcement|https://aws.amazon.com/about-aws/whats-new/2017/11/announcing-support-for-inter-region-vpc-peering/]
> (and extended with 9 more regions in 2018, see
> [link|https://aws.amazon.com/about-aws/whats-new/2018/02/inter-region-vpc-peering-is-now-available-in-nine-additional-aws-regions/]):
> {quote}Inter-Region VPC Peering allows VPC resources like EC2 instances[...]
> running in different AWS regions to communicate with each other using private
> IP addresses, without requiring gateways, VPN connections or separate network
> appliances.
> {quote}
> Since the datacenter/rack names are loaded in Ec2Snitch using AWS API there
> is no reason why this snitch would not work in a multi-datacenter setup. I
> tested and used this in a production environment. So the documentation should
> be changed to include this usage.
> Proposed change:
> [https://github.com/apache/cassandra/compare/trunk...serban21:15337-trunk]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15337) Document usage of Ec2Snitch for multiple regions cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-15337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Haddad updated CASSANDRA-15337:
---
Change Category: Semantic
Complexity: Low Hanging Fruit
Reviewers: Jon Haddad
Status: Open (was: Triage Needed)
> Document usage of Ec2Snitch for multiple regions cluster
>
>
> Key: CASSANDRA-15337
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15337
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation/Website
>Reporter: Serban Teodorescu
>Assignee: Serban Teodorescu
>Priority: Normal
>
> Ec2MultiRegionSnitch was (probably) done because it was not possible in AWS
> to have intra-region VPC peering. This changed pin 2017, see [AWS
> announcement|https://aws.amazon.com/about-aws/whats-new/2017/11/announcing-support-for-inter-region-vpc-peering/]
> (and extended with 9 more regions in 2018, see
> [link|https://aws.amazon.com/about-aws/whats-new/2018/02/inter-region-vpc-peering-is-now-available-in-nine-additional-aws-regions/]):
> {quote}Inter-Region VPC Peering allows VPC resources like EC2 instances[...]
> running in different AWS regions to communicate with each other using private
> IP addresses, without requiring gateways, VPN connections or separate network
> appliances.
> {quote}
> Since the datacenter/rack names are loaded in Ec2Snitch using AWS API there
> is no reason why this snitch would not work in a multi-datacenter setup. I
> tested and used this in a production environment. So the documentation should
> be changed to include this usage.
> Proposed change:
> [https://github.com/apache/cassandra/compare/trunk...serban21:15337-trunk]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15337) Document usage of Ec2Snitch for multiple regions cluster
[
https://issues.apache.org/jira/browse/CASSANDRA-15337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serban Teodorescu updated CASSANDRA-15337:
--
Description:
Ec2MultiRegionSnitch was (probably) done because it was not possible in AWS to
have intra-region VPC peering. This changed pin 2017, see [AWS
announcement|https://aws.amazon.com/about-aws/whats-new/2017/11/announcing-support-for-inter-region-vpc-peering/]
(and extended with 9 more regions in 2018, see
[link|https://aws.amazon.com/about-aws/whats-new/2018/02/inter-region-vpc-peering-is-now-available-in-nine-additional-aws-regions/]):
{quote}Inter-Region VPC Peering allows VPC resources like EC2 instances[...]
running in different AWS regions to communicate with each other using private
IP addresses, without requiring gateways, VPN connections or separate network
appliances.
{quote}
Since the datacenter/rack names are loaded in Ec2Snitch using AWS API there is
no reason why this snitch would not work in a multi-datacenter setup. I tested
and used this in a production environment. So the documentation should be
changed to include this usage.
Proposed change:
[https://github.com/apache/cassandra/compare/trunk...serban21:15337-trunk]
was:
Ec2MultiRegionSnitch was (probably) done because it was not possible in AWS to
have intra-region VPC peering. This changed pin 2017, see [AWS
announcement|https://aws.amazon.com/about-aws/whats-new/2017/11/announcing-support-for-inter-region-vpc-peering/]
(and extended with 9 more regions in 2018, see
[link|https://aws.amazon.com/about-aws/whats-new/2018/02/inter-region-vpc-peering-is-now-available-in-nine-additional-aws-regions/]):
{quote}Inter-Region VPC Peering allows VPC resources like EC2 instances[...]
running in different AWS regions to communicate with each other using private
IP addresses, without requiring gateways, VPN connections or separate network
appliances.
{quote}
Since the datacenter/rack names are loaded in Ec2Snitch using AWS API there is
no reason why this snitch would not work in a multi-datacenter setup. I tested
and used this in a production environment. So the documentation should be
changed to include this usage.
> Document usage of Ec2Snitch for multiple regions cluster
>
>
> Key: CASSANDRA-15337
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15337
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation/Website
>Reporter: Serban Teodorescu
>Assignee: Serban Teodorescu
>Priority: Normal
>
> Ec2MultiRegionSnitch was (probably) done because it was not possible in AWS
> to have intra-region VPC peering. This changed pin 2017, see [AWS
> announcement|https://aws.amazon.com/about-aws/whats-new/2017/11/announcing-support-for-inter-region-vpc-peering/]
> (and extended with 9 more regions in 2018, see
> [link|https://aws.amazon.com/about-aws/whats-new/2018/02/inter-region-vpc-peering-is-now-available-in-nine-additional-aws-regions/]):
> {quote}Inter-Region VPC Peering allows VPC resources like EC2 instances[...]
> running in different AWS regions to communicate with each other using private
> IP addresses, without requiring gateways, VPN connections or separate network
> appliances.
> {quote}
> Since the datacenter/rack names are loaded in Ec2Snitch using AWS API there
> is no reason why this snitch would not work in a multi-datacenter setup. I
> tested and used this in a production environment. So the documentation should
> be changed to include this usage.
> Proposed change:
> [https://github.com/apache/cassandra/compare/trunk...serban21:15337-trunk]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
