Thanks Lakmal,
From: Lakmal Warusawithana [mailto:lak...@wso2.com]
Sent: Sunday, December 21, 2014 5:37 PM
To: dev@stratos.apache.org
Subject: Re: [Discuss] Kubernetes Work Flow for 4.1.0 Release
On Mon, Dec 22, 2014 at 4:05 AM, Martin Eppel (meppel)
mailto:mep...@cisco.com>> wro
ry rapidly,
> we have not map all newly introduce kub features but will bring in
> eventually.
>
>
>
>> Thanks
>>
>>
>>
>> Martin
>>
>>
>>
>> *From:* Imesh Gunaratne [mailto:im...@apache.org]
>> *Sent:* Sunday, December 21, 2014 10:0
Sunday, December 21, 2014 10:06 AM
> *To:* dev
> *Subject:* Re: [Discuss] Kubernetes Work Flow for 4.1.0 Release
>
>
>
> Hi Devs,
>
>
>
> I have now completed the initial implementation of the KubernetesIaas and
> pushed changes to master branch.
>
>
>
> Func
Flow for 4.1.0 Release
Hi Devs,
I have now completed the initial implementation of the KubernetesIaas and
pushed changes to master branch.
Functionality:
- A member is mapped to a Kubernetes Pod.
- A replication controller is created for each member. This is to avoid the
following
Hi Devs,
I have now completed the initial implementation of the KubernetesIaas and
pushed changes to master branch.
Functionality:
- A member is mapped to a Kubernetes Pod.
- A replication controller is created for each member. This is to avoid the
following complications that may arise when a r
I have now committed the initial modifications to support this
functionality:
This includes following changes:
- Introduced KubernetesIaas class
- Removed Cartridge.deployerType
- Fixed Member.instanceId property conflict by introducing
Member.clusterInstanceId
- Now Member has two properties: ins
Thanks for the feedback Lakmal!
On Fri, Dec 19, 2014 at 7:54 PM, Lakmal Warusawithana
wrote:
> +1 Imesh, this is what in mind also.
>
> On Fri, Dec 19, 2014 at 7:35 PM, Imesh Gunaratne wrote:
>>
>> Hi Devs,
>>
>> As we have now removed Kubernetes specific cluster monitoring logic in
>> Autoscal
+1 Imesh, this is what in mind also.
On Fri, Dec 19, 2014 at 7:35 PM, Imesh Gunaratne wrote:
>
> Hi Devs,
>
> As we have now removed Kubernetes specific cluster monitoring logic in
> Autoscaler we could now use standard Cloud Controller service methods for
> managing VM instances and containers.
Hi Devs,
As we have now removed Kubernetes specific cluster monitoring logic in
Autoscaler we could now use standard Cloud Controller service methods for
managing VM instances and containers. This will make sure that Autoscaling
logic will work the same way for any type of a cartridge.
The idea i
