[Architecture] Properties based LB configuration?

Nirmal Fernando nirmal at wso2.com
Fri Mar 16 04:39:56 PDT 2012


On Fri, Mar 16, 2012 at 1:45 PM, Afkham Azeez <azeez at wso2.com> wrote:

> The LB does not know about the EC2 specific stuff. Those are just
> properties. It is up to some other component to make sense of those
> properties.


Great then!


>
>
> On Fri, Mar 16, 2012 at 1:02 PM, Nirmal Fernando <nirmal at wso2.com> wrote:
>
>> Hi,
>>
>> On Wed, Mar 14, 2012 at 2:51 PM, Afkham Azeez <azeez at wso2.com> wrote:
>>
>>> How about the following?
>>>
>>> ec2_access_key          ${AWS_ACCESS_KEY};
>>> ec2_private_key         ${AWS_PRIVATE_KEY};
>>> ec2_ssh_key             stratos-1.0.0-keypair;
>>> instance_mgt_epr        https://ec2.amazonaws.com/;
>>> disable_api_termination true;
>>> enable_monitoring       false;
>>>
>>> loadbalancer {
>>>     securityGroups      stratos-appserver-lb;
>>>     instanceType        m1.large;
>>>     instances           1;
>>>     elasticIP           ${ELASTIC_IP};
>>>     availabilityZone    us-east-1c;
>>>     payload             /mnt/payload.zip;
>>> }
>>>
>>> services {
>>>     defaults {
>>>         payload                 resources/cluster_node.zip;
>>>         availability_zone       us-east-1c;
>>>         security_groups         default-2011-02-23;
>>>         instance_type           m1.large;
>>>
>>         min_app_instances       1;
>>>         max_app_instances       5;
>>>         queue_length_per_node   400;
>>>         rounds_to_average       10;
>>>         instances_per_scale_up  1;
>>>         message_expiry_time     60000;
>>>
>>
>> Aren't some of the above ec2 specific? With the addition of new
>> autoscaler service, this would not make sense.
>> Wouldn't it better to add ec2 specific stuff together, separated from
>> 'services'? In future too, if we have any other type we can easily add them
>> separately.
>>
>> Also, when would this be applied to trunk?
>>
>>     }
>>>
>>>     appserver {
>>>         hosts                   appserver.stratoslive.wso2.com,
>>> as.stratoslive.wso2.com;
>>>         domain                  wso2.as.domain;
>>>         payload                 resources/cluster_node.zip;
>>>         availability_zone       us-east-1c;
>>>     }
>>>
>>>     esb {
>>>         hosts                   esb.stratoslive.wso2.com;
>>>         domain                  wso2.esb.domain;
>>>         payload                 resources/cluster_node.zip;
>>>         availability_zone       us-east-1c;
>>>     }
>>> }
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> Architecture at wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Software Engineer- Platform Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>**
> email: **azeez at wso2.com* <azeez at wso2.com>* cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 

Thanks & regards,
Nirmal

Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.wso2.org/pipermail/architecture/attachments/20120316/782999a7/attachment-0001.html>


More information about the Architecture mailing list