You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Imesh Gunaratne <im...@apache.org> on 2013/12/10 08:19:43 UTC
[Discuss] [Load Balancer] Load Balancer Clusters for Network Partitions
Hi All,
According to the cloud partitioning concept in Apache Stratos (incubating)
4.0.0 architecture load balancer clusters could be dynamically created
according to the deployment policy selected for a service subscription.
*What does a Deployment Policy do?*
A deployment policy describes which cloud partitions are used by a service.
*What is a Cloud Partition?*
A cloud partition defines an area of an IaaS cloud used by a service
subscription.
<partition id="P1">
<!-- A sample provider level partition -->
<property name="provider" value="ec2"/>
</partition>
<partition id="P2">
<!-- A sample region level partition -->
<property name="provider" value="openstack"/>
<property name="region" value="region-x"/>
</partition>
<partition id="P3">
<!-- A sample zone level partition -->
<property name="provider" value="ec2"/>
<property name="region" value="region-y"/>
<property name="zone" value="zone-1"/>
</partition>
*What is a Network Partition?*
A network partition defines an area of network where a set of VM instances
could access each other using their private IP addresses.
*How to optimize Load Balancer clusters?*
The following diagram illustrates a sample service subscription deployment
where there are three cloud partitions span across two network partitions.
For each network partition a load balancer cluster could be created.
The idea of this design is to minimize the latency between the member and
the load balancer by creating a load balancer cluster per network partition.
[image: Inline image 3]
Please feel free to add your thoughts.
Many Thanks
Imesh
Re: [Discuss] [Load Balancer] Load Balancer Clusters for Network Partitions
Posted by Imesh Gunaratne <im...@apache.org>.
Great thanks Lahiru!
A good point, at the moment that information is not there in topology I
guess. It's still being introduced by Nirmal in Autoscaler.
Thanks
On Tue, Dec 10, 2013 at 1:04 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> Hi Imesh,
>
> Design looks good.
>
> Does the topology reflect whether particular set of instances are in one
> network partition?
>
> Thanks.
>
>
> On Tue, Dec 10, 2013 at 12:49 PM, Imesh Gunaratne <im...@apache.org>wrote:
>
>> Hi All,
>>
>> According to the cloud partitioning concept in Apache Stratos
>> (incubating) 4.0.0 architecture load balancer clusters could be dynamically
>> created according to the deployment policy selected for a service
>> subscription.
>>
>> *What does a Deployment Policy do?*
>> A deployment policy describes which cloud partitions are used by a
>> service.
>>
>> *What is a Cloud Partition?*
>> A cloud partition defines an area of an IaaS cloud used by a service
>> subscription.
>>
>> <partition id="P1">
>> <!-- A sample provider level partition -->
>> <property name="provider" value="ec2"/>
>> </partition>
>> <partition id="P2">
>> <!-- A sample region level partition -->
>> <property name="provider" value="openstack"/>
>> <property name="region" value="region-x"/>
>> </partition>
>> <partition id="P3">
>> <!-- A sample zone level partition -->
>> <property name="provider" value="ec2"/>
>> <property name="region" value="region-y"/>
>> <property name="zone" value="zone-1"/>
>> </partition>
>>
>> *What is a Network Partition?*
>> A network partition defines an area of network where a set of VM
>> instances could access each other using their private IP addresses.
>>
>> *How to optimize Load Balancer clusters?*
>> The following diagram illustrates a sample service subscription
>> deployment where there are three cloud partitions span across two network
>> partitions. For each network partition a load balancer cluster could be
>> created.
>>
>> The idea of this design is to minimize the latency between the member and
>> the load balancer by creating a load balancer cluster per network partition.
>>
>> [image: Inline image 3]
>>
>> Please feel free to add your thoughts.
>>
>> Many Thanks
>> Imesh
>>
>
>
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
Re: [Discuss] [Load Balancer] Load Balancer Clusters for Network Partitions
Posted by Lahiru Sandaruwan <la...@wso2.com>.
Hi Imesh,
Design looks good.
Does the topology reflect whether particular set of instances are in one
network partition?
Thanks.
On Tue, Dec 10, 2013 at 12:49 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi All,
>
> According to the cloud partitioning concept in Apache Stratos (incubating)
> 4.0.0 architecture load balancer clusters could be dynamically created
> according to the deployment policy selected for a service subscription.
>
> *What does a Deployment Policy do?*
> A deployment policy describes which cloud partitions are used by a
> service.
>
> *What is a Cloud Partition?*
> A cloud partition defines an area of an IaaS cloud used by a service
> subscription.
>
> <partition id="P1">
> <!-- A sample provider level partition -->
> <property name="provider" value="ec2"/>
> </partition>
> <partition id="P2">
> <!-- A sample region level partition -->
> <property name="provider" value="openstack"/>
> <property name="region" value="region-x"/>
> </partition>
> <partition id="P3">
> <!-- A sample zone level partition -->
> <property name="provider" value="ec2"/>
> <property name="region" value="region-y"/>
> <property name="zone" value="zone-1"/>
> </partition>
>
> *What is a Network Partition?*
> A network partition defines an area of network where a set of VM instances
> could access each other using their private IP addresses.
>
> *How to optimize Load Balancer clusters?*
> The following diagram illustrates a sample service subscription deployment
> where there are three cloud partitions span across two network partitions.
> For each network partition a load balancer cluster could be created.
>
> The idea of this design is to minimize the latency between the member and
> the load balancer by creating a load balancer cluster per network partition.
>
> [image: Inline image 3]
>
> Please feel free to add your thoughts.
>
> Many Thanks
> Imesh
>
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146