Hi René,

I think what you describe is something we do with Vamp (www.vamp.io). Vamp 
provides blueprints to describe/manage the marathon deployment, and workflows 
to run all kinds of workflows, like auto up/downscaling (both horizontally and 
vertically), rebalancing traffic (we use haproxy to enable canary style 
routing/lb'ing) or any other metrics driven scenario that makes sense for you. 
For these workflows we provide DSL-based built-in patterns, or you can create 
your own workflows with JavaScript or Go. 

Let me know if this answers your questions. 

Cheers, Olaf 

> On 08 Feb 2016, at 16:53, Rene Moser <[email protected]> wrote:
> 
> Hi
> 
> Thanks for your suggestions, but there was a misunderstanding.
> 
> I don't looking for roles or playbooks to install mesos/marathon/chronos.
> 
> I am referring to modules, which can be used as tasks (within
> roles/playbooks) to interact with the api of chronos and marathon.
> 
> E.g. something similar to this:
> 
> marathon-app: name=webapp cpu=2 instances=2 mem=1 state=present
> 
> this would create a marathon app if not present. running the tasks again
> with different instances would scale the app. if not yet scaled.
> 
> marathon-app: name=webapp cpu=2 instances=4 mem=1 state=present
> 
> So you will be able to describe your infra on marathon in playbooks.
> 
> René
> 
> 
>> On 02/08/2016 04:34 PM, Alberto García Lamela wrote:
>> https://github.com/Capgemini/Apollo/tree/master/roles/dcos_cli
>> 
>> Sent from my iPhone
>> 
>> On 8 Feb 2016, at 16:12, Aaron Carey <[email protected]
>> <mailto:[email protected]>> wrote:
>> 
>>> https://github.com/udacity/ansible-marathon
>>> https://github.com/AnsibleShipyard/ansible-marathon
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------
>>> *From:* Antonio Fernandez [[email protected]
>>> <mailto:[email protected]>]
>>> *Sent:* 08 February 2016 15:08
>>> *To:* [email protected] <mailto:[email protected]>
>>> *Subject:* Re: ansible modules?
>>> 
>>> René,
>>> 
>>> take a look on this repo from CiscoCloud:
>>> 
>>> https://github.com/CiscoCloud/microservices-infrastructure
>>> 
>>> There are already many ansible modules there, but probably something
>>> can be missing.
>>> 
>>> Hope it helps.
>>> 
>>> On Mon, 8 Feb 2016 at 15:42 Rene Moser <[email protected]
>>> <mailto:[email protected]>> wrote:
>>> 
>>>    Hi
>>> 
>>>    Has anyone already built ansible modules for marathon's and
>>>    chronos' api
>>>    and wants to share?
>>> 
>>>    If not, I would like to start with it. Any help is welcome
>>> 
>>>    René
>>> 
>>> -- 
>>> 
>>> Antonio Fernández Vara
>>> 
>>> (SW Devops Leader)
>>> 
>>> +34 91 787 67 07  Ext: 1850
>>> 
>>> Calle Dublin, 1, Planta Primera
>>> 
>>> Ed. Sevilla.
>>> 
>>> Európolis
>>> 
>>> 28232 Las Rozas - Madrid
>>> 
>>> bq.com <http://www.bq.com/>
>>> 
>>> <http://facebook.com/bqreaders>  <http://twitter.com/bqreaders>   
>>> <https://plus.google.com/+bqreaders/posts>   
>>> <https://www.youtube.com/user/canalbq>   <https://instagram.com/bq_global/>
>>> 
>>> 
>>> ^  ^Nos encantan los árboles. No me imprimas si no es necesario.
>>> 
>>> Protección de Datos:Mundo Reader S.L. le informa de que los datos
>>> personales facilitados por Ud. y utilizados para el envío de esta
>>> comunicación serán objeto de tratamiento automatizado o no en nuestros
>>> ficheros, con la finalidad de gestionar la agenda de contactos de
>>> nuestra empresa y para el envío de comunicaciones profesionales por
>>> cualquier medio electrónico o no. Puede consultar en www.bq.com
>>> <http://www.bq.com/>los detalles de nuestra Política de Privacidad y
>>> dónde ejercer el derecho de acceso, rectificación, cancelación y
>>> oposición.
>>> 
>>> Confidencialidad:Este mensaje contiene material confidencial y está
>>> dirigido exclusivamente a su destinatario. Cualquier revisión,
>>> modificación o distribución por otras personas, así como su reenvío
>>> sin el consentimiento expreso está estrictamente prohibido. Si usted
>>> no es el destinatario del mensaje, por favor, comuníqueselo al emisor
>>> y borre todas las copias de forma inmediata. Confidentiality:This
>>> e-mail contains material that is confidential for de sole use of de
>>> intended recipient. Any review, reliance or distribution by others or
>>> forwarding without express permission is strictly prohibited. If you
>>> are not the intended recipient, please contact the sender and delete
>>> all copies.
>>> 

Reply via email to