Hi Bruce, On Tuesday, January 13, 2015, Bruce Edge <[email protected]> wrote:
> ...I'm wondering if crankstart is still the way forward for automated deployments > as opposed to custom launchpad configurations.... I haven't heard from anybody besides Artyom and myself using it so far, so while I still think it's a great solution for immutable instances it's not an "official" part of Sling at the moment. OTOH it's not much code so even if you had to maintain it yourself that wouldn't be the end of the world - in the end Sling is just a set of OSGi bundles with configs. And contributions are welcome in this area of course. The logical next step would be to adapt crankstart to use the provisioning model that was created in the meantime (tooling/support/provisioning-model), we designed it to be compatible with the crankstart idea but that hasn't been implemented yet. > ...I started looking into AWS's code-deploy [2], which looks a lot like the Orchestrator in [1]. > I suppose one has to commit to drink the Amazon kool-aid before > considering code-deploy... Yeah, if you agree to get married with a vendor there's lots of nice tools out there. I'm not sure how far Sling needs to go, I suppose best is for us to be friendly to those different tools so that Sling users can select what's best for them. What's very welcome in this case is blog posts or other reports of how you get those things up and running. -Bertrand
