I have just came across this one here: https://issues.apache.org/jira/browse/AURORA-215
I guess that is what I am looking for :-) ________________________________________ From: Erb, Stephan <[email protected]> Sent: Friday, October 16, 2015 8:48 AM To: [email protected] Subject: Continuous Deployment with Aurora Hi Aurora users, I am interested in how you use the Aurora client or the Aurora API in you daily business of releasing and deploying code: The Aurora client is rather generic. So, what have you build around it to enable concepts like continuous deployment, canary releases, etc? I'd imagine that most of you have somehow scripted the process of a user performing a git commit to actually running this code in production. We are basically looking for some inspiration on what works great with Aurora and what doesn't. A little background: We have used Aurora to replace the backend of an existing inhouse PaaS without changing the external PaaS API. This has been working great for us. However, we also see that Aurora offers some interesting features that we would like to use. We could either continue to invest into our own API wrapper to support those features, or we could try to move into a similar direction as the rest of the community [1]. The latter approach sounds somewhat more sane. [1] for example, as seen in https://github.com/wickman/sacker Thanks for your input. Much appreciated. Stephan PS: Was great to meet some of you in Dublin at MesosCon Europe!
