Open Stack

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 implement a wrapper API to offer what native tool already 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 [mailto:bharath_ves at hotmail.com]
Sent: November-18-15 1:20 PM
To: openstack-dev at 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 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 group which consists mongoDB app and MySQL App.[3]

So I think we need to have two resources 'apps' and 'appgroups' in mesos conductor like we have pod and rc for k8s. And regarding 'magnum container' command, we can create, delete and retrieve container details as part of mesos app itself(container =  app with 1 instance). Though I think in mesos case 'magnum app-create ..."  and 'magnum container-create ...' will use the same REST API for both cases.

Let me know your opinion/comments on this and correct me if I am wrong

[1]https://blueprints.launchpad.net/magnum/+spec/mesos-conductor.
[2]https://mesosphere.github.io/marathon/docs/application-basics.html
[3]https://mesosphere.github.io/marathon/docs/application-groups.html


Regards
Bharath T
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151118/d0c37ced/attachment.html>