stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Imesh Gunaratne <im...@apache.org>
Subject Re: Re. multi-tenancy capability
Date Wed, 27 Jan 2016 09:44:09 GMT
Hi David,

On Tue, Jan 26, 2016 at 8:28 PM, David Hbase <davidhbase@gmail.com> wrote:

> Hi, Imesh
>
> I have realized the tenancy routing service, but still issues with
> Kubernetes. Would like to know if there any updated kubernetes document?
> etc:
>

AFAIK the documentation is updated, what were the issues you got?

>
> 1. Auto scaling with Kubernetes? ( Dynamic add the minions without
> interrupt the curretn running services ?)
>

Kubernetes (K8S) nodes can be autoscaled by creating a separate composite
application for K8S. Then another application can be created for the
required product to be run on the above K8S cluster. However dynamic load
balancing would be a problem for the pods that run on K8S because Stratos
topology does not get updated with Node IPs when K8S nodes are autoscaled.


> 2. Application Topology can display the service and pods in the Kubernetes
> cluster?
>

No, currently the topology view in the Stratos UI does not show services or
pords. However Kubernetes Cockpit UI can be used for this.

Thanks

On Wed, Jan 27, 2016 at 2:40 PM, David Hbase <davidhbase@gmail.com> wrote:

> Thanks Chamila,
>
> Got great answers with the Kubernetes auto scaling (via node v 1.1 and or
> node). But would like to know what's the Stratos auto scaling functions
> with Kubernetes?
>
> etc: in Stratos we setup the auto scaling policy for the kubernetes
> cluster, when and how can this auto scaling policy work? ( will scaling the
> new pod or node ? )
>
> Thanks
> -D
>
> On Tue, Jan 26, 2016 at 11:16 AM, Chamila De Alwis <chamilad@wso2.com>
> wrote:
>
>> Hi David,
>>
>> On Tue, Jan 26, 2016 at 8:28 PM, David Hbase <davidhbase@gmail.com>
>> wrote:
>>
>>>
>>> 1. Auto scaling with Kubernetes? ( Dynamic add the minions without
>>> interrupt the curretn running services ?)
>>>
>> In Kubernetes, the Node Controller is the component in charge of
>> registration and revocation of Nodes (minions) in a cluster. However as the
>> Kubernetes documentation states [1], it doesn't automatically provision a
>> new node, simply performing the registry task for the list of nodes.
>>
>> Therefore, any autoscaling of Nodes would have to be done at a different
>> layer, based on metrics like CPU usage. CloudWatch for EC2 or Heat for
>> OpenStack are few examples of achieving this. Nodes will have to be
>> configured to auto register with the proxy.
>>
>> If you're looking for Pod autoscaling, this is already implemented in
>> Kubernetes 1.1 [2]. Autoscaling is based on CPU usage.
>>
>> 2. Application Topology can display the service and pods in the
>>> Kubernetes cluster?
>>
>> In Stratos, the Application Topology is the view of the Composite
>> Application deployment. It doesn't show the IaaS specific details such as
>> Services and Pods. These details will have to be retrieved from the
>> Kube-UI.
>>
>> [1] - http://kubernetes.io/v1.1/docs/admin/node.html#node-controller
>> [2] -
>> http://kubernetes.io/v1.1/docs/user-guide/horizontal-pod-autoscaler.html
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>


-- 
Imesh Gunaratne

Senior Technical Lead, WSO2
Committer & PMC Member, Apache Stratos

Mime
View raw message