: December-01-15 7:49 PM
To: OpenStack Development Mailing List not for usage questions
Subject: Re: [openstack-dev] [magnum] Mesos Conductor
Hi,
Sorry I was off for some days because of health issues.
So I think the work items for this BP[1] are:
1)Add support to accept json file in container-create
in magnum. I think we need approval for this BP and then implementation?
>>
>> [1]https://blueprints.launchpad.net/magnum/+spec/mesos-conductor
>>
>> Regards
>> Bharath T(tbh)
>>
>>
>> ----------
>> Date: Fri, 20 Nov 2015 0
[1]https://blueprints.launchpad.net/magnum/+spec/mesos-conductor
>
> Regards
> Bharath T(tbh)
>
>
> --
> Date: Fri, 20 Nov 2015 07:44:49 +0800
> From: jay.lau....@gmail.com
> To: openstack-dev@lists.openstack.org
>
> Subject: Re: [open
@lists.openstack.org
Subject: Re: [openstack-dev] [magnum] Mesos Conductor
It's great that we come to some agreement on unifying the client call ;-)
As i proposed in previous thread, I think that "magnum app-create" may be
better than "magnum create", I want to use "magnum a
k.org>
From: wk...@cn.ibm.com<mailto:wk...@cn.ibm.com>
Date: Thu, 19 Nov 2015 10:47:33 +0800
Subject: Re: [openstack-dev] [magnum] Mesos Conductor
@bharath,
1) actually, if you mean use container-create(delete) to do on mesos bay for
apps. I am not sure how different the interface between doc
9, 2015 at 10:36
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org
> >>
> Subject: Re: [openstack-dev] [magnum] Mesos Conductor
>
> I’m open to allowing magnum to pa
t for usage questions)"
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [magnum] Mesos Conductor
I’m open to allowing magnum to pass a blob of data (such as a lump of JSON or
YAML) to the Bay's native API. That approach strikes a balance th
g List not for usage questions
<openstack-dev@lists.openstack.org>
Date:19/11/2015 10:31 am
Subject: Re: [openstack-dev] [magnum] Mesos Conductor
@hongin, @adrian I agree with you. So can we go ahead with magnum
container-create(delete) ... for mesos bay (which actually c
Hi Bharath,
I agree the "container" part. We can implement "magnum container-create .." for
mesos bay in the way you mentioned. Personally, I don't like to introduce
"apps" and "appgroups" resources to Magnum, because they are already provided
by native tool [1]. I couldn't see the benefits to
Just want to input more for this topic, I was also thinking more for how we
can unify the client interface for Magnum.
Currently, the Kubernetes is using "kubectl create" to create all of k8s
objects including pod, rc, service, pv, pvc, hpa etc using either yaml,
json, yml, stdin file format; The
Bharath,
I agree with Hongbin on this. Let’s not expand magnum to deal with apps or
appgroups in the near term. If there is a strong desire to add these things, we
could allow it by having a plugin/extensions interface for the Magnum API to
allow additional COE specific features. Honestly,
: [openstack-dev] [magnum] Mesos Conductor
+1.
One problem I want to mention is that for mesos integration, we cannot limited
to Marathon + Mesos as there are many frameworks can run on top of Mesos, such
as Chronos, Kubernetes etc, we may need to consider more for Mesos integration
: bharath thiruveedula <bharath_...@hotmail.com>
To: OpenStack Development Mailing List not for usage questions
<openstack-dev@lists.openstack.org>
Date: 19/11/2015 10:31 am
Subject: Re: [openstack-dev] [magnum] Mesos Conductor
@hongin, @adrian I agree with
+1.
One problem I want to mention is that for mesos integration, we cannot
limited to Marathon + Mesos as there are many frameworks can run on top of
Mesos, such as Chronos, Kubernetes etc, we may need to consider more for
Mesos integration as there is a huge eco-system build on top of Mesos.
On
14 matches
Mail list logo
