Hi,As per the discussion in [1], I have pushed patchset [1]. Can you please
review the patch. I want to take comments on this patch before I push test
cases and container-list operation because there was a discussion on this topic
whether to have this or not. (from my previous experience :) ).
: 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
num. 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 07:44:49 +0800
gt;
> [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
@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 "mag
it to corresponding conductor.
> And the conductor will handle the json input. Let me know your opinions.
>
>
> Regards
> Bharath T
>
>
>
>
> [1]https://goo.gl/f46b4H
> [2]https://mesosphere.github.io/marathon/docs/application-basics.html
>
&g
stack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.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 mes
@lists.openstack.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 int
, 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 docker interface and
mesos interface. One point that when you introduce that fe
: bharath thiruveedula
To: OpenStack Development Mailing List not for usage questions
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
: [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
as there is a
gt; thoughts.
>> >
>> > Best regards,
>> > Hongbin
>> >
>> > [1] https://docs.mesosphere.com/using/cli/marathonsyntax/
>> >
>> > From: bharath thiruveedula [mailto:bharath_...@hotmail.com]
>> > Sent: November-18-15 1:20 PM
>> > To:
ready offers. However,
> if you can point out a valid use case to wrap the API, I will give it more
> thoughts.
> >
> > Best regards,
> > Hongbin
> >
> > [1] https://docs.mesosphere.com/using/cli/marathonsyntax/
> >
> > From: bharath thiruveedula [mai
n
>
> [1] https://docs.mesosphere.com/using/cli/marathonsyntax/
>
> From: bharath thiruveedula [mailto:bharath_...@hotmail.com]
> Sent: November-18-15 1:20 PM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [magnum] Mesos Conductor
>
> Hi all,
&g
ntax/
From: bharath thiruveedula [mailto:bharath_...@hotmail.com]
Sent: November-18-15 1:20 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [magnum] Mesos Conductor
Hi all,
I am working on the blueprint
[<https://blueprints.launchpad.net/magnum/+spec/mesos-conductor>1]. As per m
Hi all,I am working on the blueprint [1]. As per my understanding, we have two
resources/objects in mesos+marathon:1)Apps: combination of instances/containers
running on multiple hosts representing a service.[2]2)Application Groups: Group
of apps, for example we can have database application gro
16 matches
Mail list logo
