Sanjeev,
Please see answers inline. You may want to also check out
https://cwiki.apache.org/confluence/display/CLOUDSTACK/OVS+Tunnel+Manager+f
or+CloudStack for general limitation etc.
Some of the question are good points that needed to be in FS, I will add
them where ever appropriate.
On 09/04
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] region level VPC and guest network spanning multiple
zones
Please find the FS for this proposal at below link. I will be sending out a
different proposal covering the enhancements called out in the FS.
https://cwiki.apache.org/confluence
Please find the FS for this proposal at below link. I will be sending out
a different proposal covering the enhancements called out in the FS.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Region+level+VPC+and
+guest+network+spanning+multiple+zones
On 19/12/13 5:54 PM, "Murali Reddy" w
Ah OK. Just want to make sure that traffic accounting for access to in-DC
services is separate even though it may go through the same interface as
the public traffic.
On 12/20/13 2:09 AM, "Murali Reddy" wrote:
>On 20/12/13 5:50 AM, "Chiradeep Vittal"
>wrote:
>
>>Is there any reason to restrict
On 20/12/13 5:50 AM, "Chiradeep Vittal"
wrote:
>Is there any reason to restrict a subnet to a single zone? AFAIK, AWS VPC
>lets you stretch a subnet across AZ.
>This way you can replicate *within* the DB tier to another zone.
As per [1] in AWS VPC, "Each subnet must reside entirely within one
Av
Is there any reason to restrict a subnet to a single zone? AFAIK, AWS VPC
lets you stretch a subnet across AZ.
This way you can replicate *within* the DB tier to another zone.
Also, once you introduce distributed routing, access to other datacenter
services (S3 for instance) from within the VM wil
