Re: [PROPOSAL] add native vm-cluster orchestration service (was: [PROPOSAL] add native container orchestration service)

2017-03-01 Thread Syed Ahmed 
+1 for ApplicationCluster. I think it is generic and not tied to a specific
concept (machine,VM, service etc)

On Wed, Mar 1, 2017 at 1:54 AM, Daan Hoogland <daan.hoogl...@shapeblue.com>
wrote:

> Syed, Kilham, et. al.
>
> After some thought I came up with ApplicationCluster. It is not purely
> machines or instances but includes network and storage resources and maybe
> more. Next to that these are meant for running application like k8, mesos
> or DBaaS. I don't like service as prefix because it implies the cluster is
> for servicing the cloud or VMs that may be broken or need a kind of extra
> feature while from user perspective they are an addition, hence application
> to cloudstack.
>
> Any push back?
>
> Sent from Nine<http://www.9folders.com/>
> 
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
> From: Daan Hoogland
> Sent: 28 Feb 2017 6:49 pm
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native vm-cluster orchestration service (was:
> [PROPOSAL] add native container orchestration service)
>
> Syed, I chose machine as they might be bare metal in some cases.
>
> Sent from Nine<http://www.9folders.com/>
> 
> From: Syed Ahmed <sah...@cloudops.com>
> Sent: 28 Feb 2017 4:22 pm
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native vm-cluster orchestration service (was:
> [PROPOSAL] add native container orchestration service)
>
> We already call the VMs as Instances. So, InstanceCluster would be a better
> name imo.
>
> On Tue, Feb 28, 2017 at 10:05 AM, Daan Hoogland <
> daan.hoogl...@shapeblue.com
> > wrote:
>
> > Kishan, I see some sensible additions but also some unnecessary
> omissions.
> > Most of it seems to be Murali’s text so I’ll c your improvements back
> and
> > rename the page to the more sensible title of “MachineCluster service”
> and
> > delete the other.
> >
> > About naming, I was thinking MachineCluster instead of ServiceCluster,
> > makes sense? Or even GuestMachineCluster. ServiceCluster could mean a
> > supporting cluster that delivers e.g. backup as a service to guests, or
> > maybe some build, artifact or networking service. For this ambiguity im
> am
> > :-1: on the name ServiceCluster.
> >
> >
> > On 28/02/17 11:16, "Kishan Kavala" <kishan.kav...@accelerite.com> wrote:
> >
> > Daan,
> >  I've updated the earlier spec to support any Vm cluster. Please let
> > me know your thoughts on this.
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/
> > Service+Cluster+Functional+Specification
> >
> > regards,
> > Kishan
> >
> > -Original Message-
> > From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com]
> > Sent: 27 February 2017 04:02 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [PROPOSAL] add native vm-cluster orchestration service
> > (was: [PROPOSAL] add native container orchestration service)
> >
> > Any follow up Koushik? I want to refactor our proof of concept and
> > integrate it in master.
> >
> >     On 21/02/17 10:42, "Kishan Kavala" <kishan.kav...@accelerite.com>
> > wrote:
> >
> > Sure Daan. I'll publish the design on cwiki and share the link.
> >
> > -Original Message-
> > From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com]
> > Sent: Monday, February 20, 2017 7:27 PM
> > To: dev@cloudstack.apache.org
> > Subject: [PROPOSAL] add native vm-cluster orchestration service
> > (was: [PROPOSAL] add native container orchestration service)
> >
> > So, being very late in the discussion but havingread the whole
> > thread before editting the title of this thread,
> >
> > Can we agree that we want a generic vm-cluster service and leave
> > the container bits to containers? Kishan can you share your design?
> > Shapeblue wants to rebase their k8 service on top of this and I would
> like
> > yours and Murali's work to not conflict.
> >
> > daan.hoogl...@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > 53 Chandos Place, Covent Garden, Utrecht Utrecht 3531
> > VENetherlands @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Paul Angus [mailto:paul.an...@shapeblue.com]
> > Sent: dinsdag 7 februari 201

Re: [PROPOSAL] add native vm-cluster orchestration service (was: [PROPOSAL] add native container orchestration service)

2017-02-28 Thread Daan Hoogland 
Syed, Kilham, et. al.

After some thought I came up with ApplicationCluster. It is not purely machines 
or instances but includes network and storage resources and maybe more. Next to 
that these are meant for running application like k8, mesos or DBaaS. I don't 
like service as prefix because it implies the cluster is for servicing the 
cloud or VMs that may be broken or need a kind of extra feature while from user 
perspective they are an addition, hence application to cloudstack.

Any push back?

Sent from Nine<http://www.9folders.com/>


daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

From: Daan Hoogland
Sent: 28 Feb 2017 6:49 pm
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native vm-cluster orchestration service (was: 
[PROPOSAL] add native container orchestration service)

Syed, I chose machine as they might be bare metal in some cases.

Sent from Nine<http://www.9folders.com/>

From: Syed Ahmed <sah...@cloudops.com>
Sent: 28 Feb 2017 4:22 pm
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native vm-cluster orchestration service (was: 
[PROPOSAL] add native container orchestration service)

We already call the VMs as Instances. So, InstanceCluster would be a better
name imo.

On Tue, Feb 28, 2017 at 10:05 AM, Daan Hoogland <daan.hoogl...@shapeblue.com
> wrote:

> Kishan, I see some sensible additions but also some unnecessary omissions.
> Most of it seems to be Murali’s text so I’ll c your improvements back and
> rename the page to the more sensible title of “MachineCluster service” and
> delete the other.
>
> About naming, I was thinking MachineCluster instead of ServiceCluster,
> makes sense? Or even GuestMachineCluster. ServiceCluster could mean a
> supporting cluster that delivers e.g. backup as a service to guests, or
> maybe some build, artifact or networking service. For this ambiguity im am
> :-1: on the name ServiceCluster.
>
>
> On 28/02/17 11:16, "Kishan Kavala" <kishan.kav...@accelerite.com> wrote:
>
> Daan,
>  I've updated the earlier spec to support any Vm cluster. Please let
> me know your thoughts on this.
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/
> Service+Cluster+Functional+Specification
>
> regards,
> Kishan
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com]
> Sent: 27 February 2017 04:02 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native vm-cluster orchestration service
> (was: [PROPOSAL] add native container orchestration service)
>
> Any follow up Koushik? I want to refactor our proof of concept and
> integrate it in master.
>
> On 21/02/17 10:42, "Kishan Kavala" <kishan.kav...@accelerite.com>
> wrote:
>
> Sure Daan. I'll publish the design on cwiki and share the link.
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com]
>         Sent: Monday, February 20, 2017 7:27 PM
> To: dev@cloudstack.apache.org
> Subject: [PROPOSAL] add native vm-cluster orchestration service
> (was: [PROPOSAL] add native container orchestration service)
>
> So, being very late in the discussion but havingread the whole
> thread before editting the title of this thread,
>
> Can we agree that we want a generic vm-cluster service and leave
> the container bits to containers? Kishan can you share your design?
> Shapeblue wants to rebase their k8 service on top of this and I would like
> yours and Murali's work to not conflict.
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, Utrecht Utrecht 3531
> VENetherlands @shapeblue
>
>
>
>
> -Original Message-
> From: Paul Angus [mailto:paul.an...@shapeblue.com]
> Sent: dinsdag 7 februari 2017 08:14
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
>
> Will is 100% correct.  As I mentioned the Title is misleading.
> However, Murali did clarify in his explanation; this is really about vm
> cluster orchestration.
>
>
>
> 
> From: Will Stevens <wstev...@cloudops.com>
> Sent: 6 Feb 2017 22:54
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
>
> ​My understanding is that what Paul is talking about is what is
> already built and IS what the thread is talking about.​
>
>

Re: [PROPOSAL] add native vm-cluster orchestration service (was: [PROPOSAL] add native container orchestration service)

2017-02-28 Thread Daan Hoogland 
Syed, I chose machine as they might be bare metal in some cases.

Sent from Nine<http://www.9folders.com/>

From: Syed Ahmed <sah...@cloudops.com>
Sent: 28 Feb 2017 4:22 pm
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native vm-cluster orchestration service (was: 
[PROPOSAL] add native container orchestration service)

We already call the VMs as Instances. So, InstanceCluster would be a better
name imo.

On Tue, Feb 28, 2017 at 10:05 AM, Daan Hoogland <daan.hoogl...@shapeblue.com
> wrote:

> Kishan, I see some sensible additions but also some unnecessary omissions.
> Most of it seems to be Murali’s text so I’ll c your improvements back and
> rename the page to the more sensible title of “MachineCluster service” and
> delete the other.
>
> About naming, I was thinking MachineCluster instead of ServiceCluster,
> makes sense? Or even GuestMachineCluster. ServiceCluster could mean a
> supporting cluster that delivers e.g. backup as a service to guests, or
> maybe some build, artifact or networking service. For this ambiguity im am
> :-1: on the name ServiceCluster.
>
>
> On 28/02/17 11:16, "Kishan Kavala" <kishan.kav...@accelerite.com> wrote:
>
> Daan,
>  I've updated the earlier spec to support any Vm cluster. Please let
> me know your thoughts on this.
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/
> Service+Cluster+Functional+Specification
>
> regards,
> Kishan
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com]
>     Sent: 27 February 2017 04:02 PM
>     To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native vm-cluster orchestration service
> (was: [PROPOSAL] add native container orchestration service)
>
> Any follow up Koushik? I want to refactor our proof of concept and
> integrate it in master.
>
> On 21/02/17 10:42, "Kishan Kavala" <kishan.kav...@accelerite.com>
> wrote:
>
> Sure Daan. I'll publish the design on cwiki and share the link.
>
> -Original Message-
>     From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com]
>     Sent: Monday, February 20, 2017 7:27 PM
> To: dev@cloudstack.apache.org
> Subject: [PROPOSAL] add native vm-cluster orchestration service
> (was: [PROPOSAL] add native container orchestration service)
>
> So, being very late in the discussion but havingread the whole
> thread before editting the title of this thread,
>
> Can we agree that we want a generic vm-cluster service and leave
> the container bits to containers? Kishan can you share your design?
> Shapeblue wants to rebase their k8 service on top of this and I would like
> yours and Murali's work to not conflict.
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, Utrecht Utrecht 3531
> VENetherlands @shapeblue
>
>
>
>
> -Original Message-
> From: Paul Angus [mailto:paul.an...@shapeblue.com]
> Sent: dinsdag 7 februari 2017 08:14
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
>
> Will is 100% correct.  As I mentioned the Title is misleading.
> However, Murali did clarify in his explanation; this is really about vm
> cluster orchestration.
>
>
>
> 
> From: Will Stevens <wstev...@cloudops.com>
> Sent: 6 Feb 2017 22:54
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
>
> ​My understanding is that what Paul is talking about is what is
> already built and IS what the thread is talking about.​
>
> *Will STEVENS*
> Lead Developer
>
> <https://goo.gl/NYZ8KK>
>
> On Mon, Feb 6, 2017 at 2:29 PM, Rajesh Ramchandani <
> rajesh.ramchand...@accelerite.com> wrote:
>
> > Hi Paul - I think this is different from what the thread was
> about.
> > The conversation was specifically about adding support for
> container
> > orchestrators. You are talking about provisioning a group of VMs.
> > Although, this is something I think several Cloudstack users have
> > requested before and we should propose a solution to this.
> >
> > Raj
> >
> > 
> > From: Paul Angus <paul.an...@shapeblue.com>
> > Sent: Monday, February 6, 2017 11:16

Re: [PROPOSAL] add native vm-cluster orchestration service (was: [PROPOSAL] add native container orchestration service)

2017-02-28 Thread Syed Ahmed 
We already call the VMs as Instances. So, InstanceCluster would be a better
name imo.

On Tue, Feb 28, 2017 at 10:05 AM, Daan Hoogland <daan.hoogl...@shapeblue.com
> wrote:

> Kishan, I see some sensible additions but also some unnecessary omissions.
> Most of it seems to be Murali’s text so I’ll c your improvements back and
> rename the page to the more sensible title of “MachineCluster service” and
> delete the other.
>
> About naming, I was thinking MachineCluster instead of ServiceCluster,
> makes sense? Or even GuestMachineCluster. ServiceCluster could mean a
> supporting cluster that delivers e.g. backup as a service to guests, or
> maybe some build, artifact or networking service. For this ambiguity im am
> :-1: on the name ServiceCluster.
>
>
> On 28/02/17 11:16, "Kishan Kavala" <kishan.kav...@accelerite.com> wrote:
>
> Daan,
>  I've updated the earlier spec to support any Vm cluster. Please let
> me know your thoughts on this.
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/
> Service+Cluster+Functional+Specification
>
> regards,
> Kishan
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com]
>     Sent: 27 February 2017 04:02 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native vm-cluster orchestration service
> (was: [PROPOSAL] add native container orchestration service)
>
> Any follow up Koushik? I want to refactor our proof of concept and
> integrate it in master.
>
> On 21/02/17 10:42, "Kishan Kavala" <kishan.kav...@accelerite.com>
> wrote:
>
> Sure Daan. I'll publish the design on cwiki and share the link.
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com]
> Sent: Monday, February 20, 2017 7:27 PM
> To: dev@cloudstack.apache.org
> Subject: [PROPOSAL] add native vm-cluster orchestration service
> (was: [PROPOSAL] add native container orchestration service)
>
> So, being very late in the discussion but havingread the whole
> thread before editting the title of this thread,
>
> Can we agree that we want a generic vm-cluster service and leave
> the container bits to containers? Kishan can you share your design?
> Shapeblue wants to rebase their k8 service on top of this and I would like
> yours and Murali's work to not conflict.
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, Utrecht Utrecht 3531
> VENetherlands @shapeblue
>
>
>
>
> -Original Message-
> From: Paul Angus [mailto:paul.an...@shapeblue.com]
> Sent: dinsdag 7 februari 2017 08:14
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
>
> Will is 100% correct.  As I mentioned the Title is misleading.
> However, Murali did clarify in his explanation; this is really about vm
> cluster orchestration.
>
>
>
> 
> From: Will Stevens <wstev...@cloudops.com>
> Sent: 6 Feb 2017 22:54
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
>
> ​My understanding is that what Paul is talking about is what is
> already built and IS what the thread is talking about.​
>
> *Will STEVENS*
> Lead Developer
>
> <https://goo.gl/NYZ8KK>
>
> On Mon, Feb 6, 2017 at 2:29 PM, Rajesh Ramchandani <
> rajesh.ramchand...@accelerite.com> wrote:
>
> > Hi Paul - I think this is different from what the thread was
> about.
> > The conversation was specifically about adding support for
> container
> > orchestrators. You are talking about provisioning a group of VMs.
> > Although, this is something I think several Cloudstack users have
> > requested before and we should propose a solution to this.
> >
> > Raj
> >
> > 
> > From: Paul Angus <paul.an...@shapeblue.com>
> > Sent: Monday, February 6, 2017 11:16:41 AM
> > To: dev@cloudstack.apache.org
> > Subject: RE: [PROPOSAL] add native container orchestration
> service
> >
> > #WhatHeSaid
> >
> > The title is misleading.  The proposal is purely to add the
> notion of
> > Clusters of VMs to CloudStack.  These may be for databases,
> containers
> > or anything

Re: [PROPOSAL] add native vm-cluster orchestration service (was: [PROPOSAL] add native container orchestration service)

2017-02-28 Thread Daan Hoogland 
Kishan, I see some sensible additions but also some unnecessary omissions. Most 
of it seems to be Murali’s text so I’ll c your improvements back and rename 
the page to the more sensible title of “MachineCluster service” and delete the 
other.

About naming, I was thinking MachineCluster instead of ServiceCluster, makes 
sense? Or even GuestMachineCluster. ServiceCluster could mean a supporting 
cluster that delivers e.g. backup as a service to guests, or maybe some build, 
artifact or networking service. For this ambiguity im am :-1: on the name 
ServiceCluster.


On 28/02/17 11:16, "Kishan Kavala" <kishan.kav...@accelerite.com> wrote:

Daan,
 I've updated the earlier spec to support any Vm cluster. Please let me 
know your thoughts on this.

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Service+Cluster+Functional+Specification

regards,
Kishan

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com] 
Sent: 27 February 2017 04:02 PM
To: dev@cloudstack.apache.org
    Subject: Re: [PROPOSAL] add native vm-cluster orchestration service (was: 
[PROPOSAL] add native container orchestration service)

Any follow up Koushik? I want to refactor our proof of concept and 
integrate it in master.

On 21/02/17 10:42, "Kishan Kavala" <kishan.kav...@accelerite.com> wrote:

Sure Daan. I'll publish the design on cwiki and share the link.

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com] 
Sent: Monday, February 20, 2017 7:27 PM
To: dev@cloudstack.apache.org
    Subject: [PROPOSAL] add native vm-cluster orchestration service (was: 
[PROPOSAL] add native container orchestration service)

So, being very late in the discussion but havingread the whole thread 
before editting the title of this thread,

Can we agree that we want a generic vm-cluster service and leave the 
container bits to containers? Kishan can you share your design? Shapeblue wants 
to rebase their k8 service on top of this and I would like yours and Murali's 
work to not conflict.

daan.hoogl...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, Utrecht Utrecht 3531 VENetherlands 
@shapeblue
  
 


-Original Message-
From: Paul Angus [mailto:paul.an...@shapeblue.com]
Sent: dinsdag 7 februari 2017 08:14
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

Will is 100% correct.  As I mentioned the Title is misleading.  
However, Murali did clarify in his explanation; this is really about vm cluster 
orchestration.




From: Will Stevens <wstev...@cloudops.com>
Sent: 6 Feb 2017 22:54
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

​My understanding is that what Paul is talking about is what is already 
built and IS what the thread is talking about.​

*Will STEVENS*
Lead Developer

<https://goo.gl/NYZ8KK>

On Mon, Feb 6, 2017 at 2:29 PM, Rajesh Ramchandani < 
rajesh.ramchand...@accelerite.com> wrote:

> Hi Paul - I think this is different from what the thread was about. 
> The conversation was specifically about adding support for container 
> orchestrators. You are talking about provisioning a group of VMs.
> Although, this is something I think several Cloudstack users have 
> requested before and we should propose a solution to this.
>
> Raj
>
> 
> From: Paul Angus <paul.an...@shapeblue.com>
> Sent: Monday, February 6, 2017 11:16:41 AM
> To: dev@cloudstack.apache.org
> Subject: RE: [PROPOSAL] add native container orchestration service
>
> #WhatHeSaid
>
> The title is misleading.  The proposal is purely to add the notion of 
> Clusters of VMs to CloudStack.  These may be for databases, 
containers 
> or anything else that needs 'clusters' of compute. Self-healing and 
> autoscaling are logical next steps to be added.
>
> Those guys at ShapeBlue have open-sourced their whole k8s container 
> service piece.  If/when the 'cluster' part of that work is added into 
> CloudStack, the k8s specific pieces can be used by anyone who wants 
> to, alternatively they could be used for reference in order to create 
> another types of cluster.  (or ignored completely).
>

Re: [PROPOSAL] add native vm-cluster orchestration service (was: [PROPOSAL] add native container orchestration service)

2017-02-28 Thread Rene Moser 
On 02/20/2017 02:56 PM, Daan Hoogland wrote:
> So, being very late in the discussion but havingread the whole thread before 
> editting the title of this thread,
> 
> Can we agree that we want a generic vm-cluster service and leave the 
> container bits to containers? Kishan can you share your design? Shapeblue 
> wants to rebase their k8 service on top of this and I would like yours and 
> Murali's work to not conflict.

+1

RE: [PROPOSAL] add native vm-cluster orchestration service (was: [PROPOSAL] add native container orchestration service)

2017-02-28 Thread Kishan Kavala 
Daan,
 I've updated the earlier spec to support any Vm cluster. Please let me know 
your thoughts on this.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Service+Cluster+Functional+Specification

regards,
Kishan

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com] 
Sent: 27 February 2017 04:02 PM
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native vm-cluster orchestration service (was: 
[PROPOSAL] add native container orchestration service)

Any follow up Koushik? I want to refactor our proof of concept and integrate it 
in master.

On 21/02/17 10:42, "Kishan Kavala" <kishan.kav...@accelerite.com> wrote:

Sure Daan. I'll publish the design on cwiki and share the link.

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com] 
Sent: Monday, February 20, 2017 7:27 PM
To: dev@cloudstack.apache.org
Subject: [PROPOSAL] add native vm-cluster orchestration service (was: 
[PROPOSAL] add native container orchestration service)

So, being very late in the discussion but havingread the whole thread 
before editting the title of this thread,

Can we agree that we want a generic vm-cluster service and leave the 
container bits to containers? Kishan can you share your design? Shapeblue wants 
to rebase their k8 service on top of this and I would like yours and Murali's 
work to not conflict.

daan.hoogl...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, Utrecht Utrecht 3531 VENetherlands 
@shapeblue
  
 


-Original Message-
From: Paul Angus [mailto:paul.an...@shapeblue.com]
Sent: dinsdag 7 februari 2017 08:14
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

Will is 100% correct.  As I mentioned the Title is misleading.  However, 
Murali did clarify in his explanation; this is really about vm cluster 
orchestration.




From: Will Stevens <wstev...@cloudops.com>
Sent: 6 Feb 2017 22:54
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

​My understanding is that what Paul is talking about is what is already 
built and IS what the thread is talking about.​

*Will STEVENS*
Lead Developer

<https://goo.gl/NYZ8KK>

On Mon, Feb 6, 2017 at 2:29 PM, Rajesh Ramchandani < 
rajesh.ramchand...@accelerite.com> wrote:

> Hi Paul - I think this is different from what the thread was about. 
> The conversation was specifically about adding support for container 
> orchestrators. You are talking about provisioning a group of VMs.
> Although, this is something I think several Cloudstack users have 
> requested before and we should propose a solution to this.
>
> Raj
>
> 
> From: Paul Angus <paul.an...@shapeblue.com>
> Sent: Monday, February 6, 2017 11:16:41 AM
> To: dev@cloudstack.apache.org
> Subject: RE: [PROPOSAL] add native container orchestration service
>
> #WhatHeSaid
>
> The title is misleading.  The proposal is purely to add the notion of 
> Clusters of VMs to CloudStack.  These may be for databases, containers 
> or anything else that needs 'clusters' of compute. Self-healing and 
> autoscaling are logical next steps to be added.
>
> Those guys at ShapeBlue have open-sourced their whole k8s container 
> service piece.  If/when the 'cluster' part of that work is added into 
> CloudStack, the k8s specific pieces can be used by anyone who wants 
> to, alternatively they could be used for reference in order to create 
> another types of cluster.  (or ignored completely).
>
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>
>
>
>
> -Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com]
> Sent: 31 January 2017 13:26
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
>
> s/cloud-init/cloud-config/
>
> On Jan 31, 2017 7:24 AM, "Will Stevens" <williamstev...@gmail.com> wrote:
>
> > I think that is covered in this proposal. There is nothing k8s 
> > specific in this integration (from what I understand), all the k8s 
> > details are passed in via the cloud-init configuration after the 
> > cluster
> has been provisioned.
> >
> > On Jan 31, 2017 3:06 AM, "Lianghwa

Re: [PROPOSAL] add native vm-cluster orchestration service (was: [PROPOSAL] add native container orchestration service)

2017-02-27 Thread Daan Hoogland 
Any follow up Koushik? I want to refactor our proof of concept and integrate it 
in master.

On 21/02/17 10:42, "Kishan Kavala" <kishan.kav...@accelerite.com> wrote:

Sure Daan. I'll publish the design on cwiki and share the link.

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com] 
Sent: Monday, February 20, 2017 7:27 PM
To: dev@cloudstack.apache.org
Subject: [PROPOSAL] add native vm-cluster orchestration service (was: 
[PROPOSAL] add native container orchestration service)

So, being very late in the discussion but havingread the whole thread 
before editting the title of this thread,

Can we agree that we want a generic vm-cluster service and leave the 
container bits to containers? Kishan can you share your design? Shapeblue wants 
to rebase their k8 service on top of this and I would like yours and Murali's 
work to not conflict.

daan.hoogl...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, Utrecht Utrecht 3531 VENetherlands 
@shapeblue
  
 


-Original Message-
From: Paul Angus [mailto:paul.an...@shapeblue.com]
Sent: dinsdag 7 februari 2017 08:14
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

Will is 100% correct.  As I mentioned the Title is misleading.  However, 
Murali did clarify in his explanation; this is really about vm cluster 
orchestration.




From: Will Stevens <wstev...@cloudops.com>
Sent: 6 Feb 2017 22:54
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

​My understanding is that what Paul is talking about is what is already 
built and IS what the thread is talking about.​

*Will STEVENS*
Lead Developer

<https://goo.gl/NYZ8KK>

On Mon, Feb 6, 2017 at 2:29 PM, Rajesh Ramchandani < 
rajesh.ramchand...@accelerite.com> wrote:

> Hi Paul - I think this is different from what the thread was about. 
> The conversation was specifically about adding support for container 
> orchestrators. You are talking about provisioning a group of VMs.
> Although, this is something I think several Cloudstack users have 
> requested before and we should propose a solution to this.
>
> Raj
>
> 
> From: Paul Angus <paul.an...@shapeblue.com>
> Sent: Monday, February 6, 2017 11:16:41 AM
> To: dev@cloudstack.apache.org
> Subject: RE: [PROPOSAL] add native container orchestration service
>
> #WhatHeSaid
>
> The title is misleading.  The proposal is purely to add the notion of 
> Clusters of VMs to CloudStack.  These may be for databases, containers 
> or anything else that needs 'clusters' of compute. Self-healing and 
> autoscaling are logical next steps to be added.
>
> Those guys at ShapeBlue have open-sourced their whole k8s container 
> service piece.  If/when the 'cluster' part of that work is added into 
> CloudStack, the k8s specific pieces can be used by anyone who wants 
> to, alternatively they could be used for reference in order to create 
> another types of cluster.  (or ignored completely).
>
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>
>
>
>
> -Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com]
> Sent: 31 January 2017 13:26
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
>
> s/cloud-init/cloud-config/
>
> On Jan 31, 2017 7:24 AM, "Will Stevens" <williamstev...@gmail.com> wrote:
>
> > I think that is covered in this proposal. There is nothing k8s 
> > specific in this integration (from what I understand), all the k8s 
> > details are passed in via the cloud-init configuration after the 
> > cluster
> has been provisioned.
> >
> > On Jan 31, 2017 3:06 AM, "Lianghwa Jou" 
> > <lianghwa@accelerite.com>
> > wrote:
> >
> >
> > There are many container orchestrators. Those container 
> > orchestrators are happy to run on any VMs or bare metal machines. 
> > K8s is just one of them and there will be more in the future. It may 
> > not be a good idea to make CloudStack to be k8s aware. IMO, the 
> > relationship between k8s and cloudstack should be similar to 
> > ap

RE: [PROPOSAL] add native vm-cluster orchestration service (was: [PROPOSAL] add native container orchestration service)

2017-02-21 Thread Kishan Kavala 
Sure Daan. I'll publish the design on cwiki and share the link.

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@shapeblue.com] 
Sent: Monday, February 20, 2017 7:27 PM
To: dev@cloudstack.apache.org
Subject: [PROPOSAL] add native vm-cluster orchestration service (was: 
[PROPOSAL] add native container orchestration service)

So, being very late in the discussion but havingread the whole thread before 
editting the title of this thread,

Can we agree that we want a generic vm-cluster service and leave the container 
bits to containers? Kishan can you share your design? Shapeblue wants to rebase 
their k8 service on top of this and I would like yours and Murali's work to not 
conflict.

daan.hoogl...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, Utrecht Utrecht 3531 VENetherlands @shapeblue
  
 


-Original Message-
From: Paul Angus [mailto:paul.an...@shapeblue.com]
Sent: dinsdag 7 februari 2017 08:14
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

Will is 100% correct.  As I mentioned the Title is misleading.  However, Murali 
did clarify in his explanation; this is really about vm cluster orchestration.




From: Will Stevens <wstev...@cloudops.com>
Sent: 6 Feb 2017 22:54
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

​My understanding is that what Paul is talking about is what is already built 
and IS what the thread is talking about.​

*Will STEVENS*
Lead Developer

<https://goo.gl/NYZ8KK>

On Mon, Feb 6, 2017 at 2:29 PM, Rajesh Ramchandani < 
rajesh.ramchand...@accelerite.com> wrote:

> Hi Paul - I think this is different from what the thread was about. 
> The conversation was specifically about adding support for container 
> orchestrators. You are talking about provisioning a group of VMs.
> Although, this is something I think several Cloudstack users have 
> requested before and we should propose a solution to this.
>
> Raj
>
> 
> From: Paul Angus <paul.an...@shapeblue.com>
> Sent: Monday, February 6, 2017 11:16:41 AM
> To: dev@cloudstack.apache.org
> Subject: RE: [PROPOSAL] add native container orchestration service
>
> #WhatHeSaid
>
> The title is misleading.  The proposal is purely to add the notion of 
> Clusters of VMs to CloudStack.  These may be for databases, containers 
> or anything else that needs 'clusters' of compute. Self-healing and 
> autoscaling are logical next steps to be added.
>
> Those guys at ShapeBlue have open-sourced their whole k8s container 
> service piece.  If/when the 'cluster' part of that work is added into 
> CloudStack, the k8s specific pieces can be used by anyone who wants 
> to, alternatively they could be used for reference in order to create 
> another types of cluster.  (or ignored completely).
>
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>
>
>
>
> -Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com]
> Sent: 31 January 2017 13:26
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
>
> s/cloud-init/cloud-config/
>
> On Jan 31, 2017 7:24 AM, "Will Stevens" <williamstev...@gmail.com> wrote:
>
> > I think that is covered in this proposal. There is nothing k8s 
> > specific in this integration (from what I understand), all the k8s 
> > details are passed in via the cloud-init configuration after the 
> > cluster
> has been provisioned.
> >
> > On Jan 31, 2017 3:06 AM, "Lianghwa Jou" 
> > <lianghwa@accelerite.com>
> > wrote:
> >
> >
> > There are many container orchestrators. Those container 
> > orchestrators are happy to run on any VMs or bare metal machines. 
> > K8s is just one of them and there will be more in the future. It may 
> > not be a good idea to make CloudStack to be k8s aware. IMO, the 
> > relationship between k8s and cloudstack should be similar to 
> > application and os. It probably not a good idea to make your OS to 
> > be aware of any specific applications so IMHO I don’t think k8s should be 
> > native to CloudStack.
> > It makes more sense to provide some generic services that many 
> > applications can take advantages of. Some generic resource grouping 
> > service makes sense so a group of VMs, baremetal machines or network 
> > can be treated as a single entity. Some life cycle management will 
> > be necessary for these entities too. We can deploy k8s, swarm, dcos 
> > or even non-container specific ser

Re: [PROPOSAL] add native vm-cluster orchestration service (was: [PROPOSAL] add native container orchestration service)

2017-02-20 Thread Wido den Hollander 

> Op 20 februari 2017 om 14:56 schreef Daan Hoogland 
> :
> 
> 
> So, being very late in the discussion but havingread the whole thread before 
> editting the title of this thread,
> 
> Can we agree that we want a generic vm-cluster service and leave the 
> container bits to containers? Kishan can you share your design? Shapeblue 
> wants to rebase their k8 service on top of this and I would like yours and 
> Murali's work to not conflict.
> 

I like that a lot more. This way it wouldn't only be containers, but think of 
spawning a cluster of VMs together which form a MariaDB Galera cluster for 
example.

Such features are very welcome!

Wido

> daan.hoogl...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, Utrecht Utrecht 3531 VENetherlands
> @shapeblue
>   
>  
> 
> 
> -Original Message-
> From: Paul Angus [mailto:paul.an...@shapeblue.com] 
> Sent: dinsdag 7 februari 2017 08:14
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
> 
> Will is 100% correct.  As I mentioned the Title is misleading.  However, 
> Murali did clarify in his explanation; this is really about vm cluster 
> orchestration.
> 
> 
> 
> 
> From: Will Stevens 
> Sent: 6 Feb 2017 22:54
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
> 
> ​My understanding is that what Paul is talking about is what is already built 
> and IS what the thread is talking about.​
> 
> *Will STEVENS*
> Lead Developer
> 
> 
> 
> On Mon, Feb 6, 2017 at 2:29 PM, Rajesh Ramchandani < 
> rajesh.ramchand...@accelerite.com> wrote:
> 
> > Hi Paul - I think this is different from what the thread was about. 
> > The conversation was specifically about adding support for container 
> > orchestrators. You are talking about provisioning a group of VMs. 
> > Although, this is something I think several Cloudstack users have 
> > requested before and we should propose a solution to this.
> >
> > Raj
> >
> > 
> > From: Paul Angus 
> > Sent: Monday, February 6, 2017 11:16:41 AM
> > To: dev@cloudstack.apache.org
> > Subject: RE: [PROPOSAL] add native container orchestration service
> >
> > #WhatHeSaid
> >
> > The title is misleading.  The proposal is purely to add the notion of 
> > Clusters of VMs to CloudStack.  These may be for databases, containers 
> > or anything else that needs 'clusters' of compute. Self-healing and 
> > autoscaling are logical next steps to be added.
> >
> > Those guys at ShapeBlue have open-sourced their whole k8s container 
> > service piece.  If/when the 'cluster' part of that work is added into 
> > CloudStack, the k8s specific pieces can be used by anyone who wants 
> > to, alternatively they could be used for reference in order to create 
> > another types of cluster.  (or ignored completely).
> >
> >
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Will Stevens [mailto:williamstev...@gmail.com]
> > Sent: 31 January 2017 13:26
> > To: dev@cloudstack.apache.org
> > Subject: Re: [PROPOSAL] add native container orchestration service
> >
> > s/cloud-init/cloud-config/
> >
> > On Jan 31, 2017 7:24 AM, "Will Stevens"  wrote:
> >
> > > I think that is covered in this proposal. There is nothing k8s
> > > specific in this integration (from what I understand), all the k8s
> > > details are passed in via the cloud-init configuration after the cluster
> > has been provisioned.
> > >
> > > On Jan 31, 2017 3:06 AM, "Lianghwa Jou" 
> > > wrote:
> > >
> > >
> > > There are many container orchestrators. Those container orchestrators
> > > are happy to run on any VMs or bare metal machines. K8s is just one of
> > > them and there will be more in the future. It may not be a good idea
> > > to make CloudStack to be k8s aware. IMO, the relationship between k8s
> > > and cloudstack should be similar to application and os. It probably
> > > not a good idea to make your OS to be aware of any specific
> > > applications so IMHO I don’t think k8s should be native to CloudStack.
> > > It makes more sense to provide some generic services that many
> > > applications can take advantages of. Some generic resource grouping
> > > service makes sense so a group of VMs, baremetal machines or network
> > > can be treated as a single entity. Some life cycle management will be
> > > necessary for these entities too. We can deploy k8s, swarm, dcos or
> > > even non-container specific services on top of CloudStack. The k8s is
> > > changing fast. One single tenant installation may need more than one
> > > VM group and may actually requires more (k8s federation). It will be a
> > >

[PROPOSAL] add native vm-cluster orchestration service (was: [PROPOSAL] add native container orchestration service)

2017-02-20 Thread Daan Hoogland 
So, being very late in the discussion but havingread the whole thread before 
editting the title of this thread,

Can we agree that we want a generic vm-cluster service and leave the container 
bits to containers? Kishan can you share your design? Shapeblue wants to rebase 
their k8 service on top of this and I would like yours and Murali's work to not 
conflict.

daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, Utrecht Utrecht 3531 VENetherlands
@shapeblue
  
 


-Original Message-
From: Paul Angus [mailto:paul.an...@shapeblue.com] 
Sent: dinsdag 7 februari 2017 08:14
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

Will is 100% correct.  As I mentioned the Title is misleading.  However, Murali 
did clarify in his explanation; this is really about vm cluster orchestration.




From: Will Stevens 
Sent: 6 Feb 2017 22:54
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

​My understanding is that what Paul is talking about is what is already built 
and IS what the thread is talking about.​

*Will STEVENS*
Lead Developer



On Mon, Feb 6, 2017 at 2:29 PM, Rajesh Ramchandani < 
rajesh.ramchand...@accelerite.com> wrote:

> Hi Paul - I think this is different from what the thread was about. 
> The conversation was specifically about adding support for container 
> orchestrators. You are talking about provisioning a group of VMs. 
> Although, this is something I think several Cloudstack users have 
> requested before and we should propose a solution to this.
>
> Raj
>
> 
> From: Paul Angus 
> Sent: Monday, February 6, 2017 11:16:41 AM
> To: dev@cloudstack.apache.org
> Subject: RE: [PROPOSAL] add native container orchestration service
>
> #WhatHeSaid
>
> The title is misleading.  The proposal is purely to add the notion of 
> Clusters of VMs to CloudStack.  These may be for databases, containers 
> or anything else that needs 'clusters' of compute. Self-healing and 
> autoscaling are logical next steps to be added.
>
> Those guys at ShapeBlue have open-sourced their whole k8s container 
> service piece.  If/when the 'cluster' part of that work is added into 
> CloudStack, the k8s specific pieces can be used by anyone who wants 
> to, alternatively they could be used for reference in order to create 
> another types of cluster.  (or ignored completely).
>
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>
>
>
>
> -Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com]
> Sent: 31 January 2017 13:26
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
>
> s/cloud-init/cloud-config/
>
> On Jan 31, 2017 7:24 AM, "Will Stevens"  wrote:
>
> > I think that is covered in this proposal. There is nothing k8s
> > specific in this integration (from what I understand), all the k8s
> > details are passed in via the cloud-init configuration after the cluster
> has been provisioned.
> >
> > On Jan 31, 2017 3:06 AM, "Lianghwa Jou" 
> > wrote:
> >
> >
> > There are many container orchestrators. Those container orchestrators
> > are happy to run on any VMs or bare metal machines. K8s is just one of
> > them and there will be more in the future. It may not be a good idea
> > to make CloudStack to be k8s aware. IMO, the relationship between k8s
> > and cloudstack should be similar to application and os. It probably
> > not a good idea to make your OS to be aware of any specific
> > applications so IMHO I don’t think k8s should be native to CloudStack.
> > It makes more sense to provide some generic services that many
> > applications can take advantages of. Some generic resource grouping
> > service makes sense so a group of VMs, baremetal machines or network
> > can be treated as a single entity. Some life cycle management will be
> > necessary for these entities too. We can deploy k8s, swarm, dcos or
> > even non-container specific services on top of CloudStack. The k8s is
> > changing fast. One single tenant installation may need more than one
> > VM group and may actually requires more (k8s federation). It will be a
> > struggle to be in sync if we try to bring k8s specific knowledge into
> cloudstack.
> >
> > Regards,
> >
> >
> > --
> > Lianghwa Jou
> > VP Engineering, Accelerite
> > email: lianghwa@accelerite.com
> >
> >
> >
> >
> >
> > On 1/29/17, 11:54 PM, "Murali Reddy"  wrote:
> >
> >
> > I agree with some good views Will has shared and I also agree to
> > the concerns raised by Wido and Eric. IMO we need balance of staying
> > relevant/add new features vs stability of CloudStack and take
> > corrective