lace, 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)
tion 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 wrote:
> Kishan, I see some sensible additions but also some unnecessary omissions.
>
iginal 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 orchestrat
gland [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
---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)
An
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 desi
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.
ilto: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
(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 d
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,
dag 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 orchestr
ack 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 orc
gt; 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
&g
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
uster. (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: [
published don't have anything
> specific to container_clusters and can be used for any service.
>
> -Original Message-
> From: Murali Reddy [mailto:muralimmre...@gmail.com]
> Sent: 02 February 2017 02:34 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add nativ
d can be used for any service.
-Original Message-
From: Murali Reddy [mailto:muralimmre...@gmail.com]
Sent: 02 February 2017 02:34 PM
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service
Thanks for the feedback. There have been some concerns here
Thanks for the feedback. There have been some concerns here with this proposal.
I think we had sufficient valid arguments why we need this functionality in
CloudStack. While this proposal is to use k8s as container orchestrator design
should be able to adopt other container orchestrator.
Unle
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 prov
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 containe
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
I have been following the discussion on this thread here. I agree with
everything that has been posted about the responsibility of
maintaining/supporting plugins that sometimes we feel are being left aside
and we do not know to what extent they are being used. However, as Will and
others highlighte
-service . I’ve been doing some prototypes on a similar kind of
abstraction.
-Original Message-
From: Murali Reddy [mailto:murali.re...@shapeblue.com]
Sent: Monday, January 30, 2017 1:24 PM
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service
I
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 action if needed. We
have two good examples for both. When SDN was hot technology CloudS
I agree that we need to be careful what we take on and own inside
CloudStack. I feel like some of the plugins or integrations which we have
been "maintaining" may serve us better to abandon, but I feel like that is
a whole discussion on its own.
In this case, I feel like there is a minimum viable
> Op 27 januari 2017 om 16:08 schreef Will Stevens :
>
>
> Hey Murali,
> How different is this proposal than what ShapeBlue already built. It looks
> pretty consistent with the functionality that you guys open sourced in
> Seville.
>
> I have not yet used this functionality, but I have reports
Hey Murali,
How different is this proposal than what ShapeBlue already built. It looks
pretty consistent with the functionality that you guys open sourced in
Seville.
I have not yet used this functionality, but I have reports that it works
quite well.
I believe the premise here is to only orches
On Fri, Jan 27, 2017 at 7:20 AM, Murali Reddy wrote:
> All,
>
> I would like propose native functionality into CloudStack to provide a
> container service through which users out-of-the box can use to launch
> container based application. Idea is to support ability to orchestrate the
> resource
Wido,
This proposal is not suggesting CloudStack do the job of container
orchestration like you mentioned we have number of purpose built options for
that.
As described in the FS, running containers on VM’s provisioned by IAAS is
popular deployment model. If user wants to do same on CloudSt
> Op 27 januari 2017 om 7:20 schreef Murali Reddy :
>
>
> All,
>
> I would like propose native functionality into CloudStack to provide a
> container service through which users out-of-the box can use to launch
> container based application. Idea is to support ability to orchestrate the
> re
All,
I would like propose native functionality into CloudStack to provide a
container service through which users out-of-the box can use to launch
container based application. Idea is to support ability to orchestrate the
resources and automate aspects of setting up container orchestrator throu
31 matches
Mail list logo
