stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chamila De Alwis <chami...@wso2.com>
Subject Re: Re. multi-tenancy capability
Date Tue, 26 Jan 2016 19:16:14 GMT
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

Mime
View raw message