Looks cool albeit i've a rant:<p>It's "funny" that for a deployment system, its own deployment follows all this crappy standards people have been running by lately.<p>Config in $HOME, startup with a random shell script, install is a compilation of python/bash/etc scripts that do magic, ... I mean look at this:
<a href="https://github.com/spinnaker/spinnaker/blob/master/gradlew#L149" rel="nofollow">https://github.com/spinnaker/spinnaker/blob/master/gradlew#L...</a> (or actually, read the whole script, be scared)<p>Software nowadays.. a bunch of shell scripts with hacks all over which few actually knows how to write :/ (writing bash scripts well does take quite a bit of knowledge)<p>/rant over, send me your downvotes.
Also, the blog post here: <a href="http://techblog.netflix.com/2015/11/global-continuous-delivery-with.html" rel="nofollow">http://techblog.netflix.com/2015/11/global-continuous-delive...</a>
Anyone know why this wasn't published in github.com/neflix as the rest of the NetFlix OSS tools are but rather in a new account at github.com/spinnaker? They've also gone through the trouble of doing more PR and setting up spinnaker.io for this.
This is Netflix's replacement for their Asgard platform: <a href="http://techblog.netflix.com/2015/09/moving-from-asgard-to-spinnaker.html" rel="nofollow">http://techblog.netflix.com/2015/09/moving-from-asgard-to-sp...</a><p>Also largely written in Groovy / Spring Boot.
<a href="http://www.groovy-lang.org" rel="nofollow">http://www.groovy-lang.org</a>
I'm interested in what this says about Netflix's plans to stay on AWS, move off of it, or simply diversify their infrastructure. Maybe' we'll see a Chaos (Whatever's bigger than Kong), that models knocking out an entire provider: i.e., don't have to rely on Amazon's WAN anymore because they also have Cloud Platform/Azure to supply things.
Jeeze; for a second I thought Netflix had somehow made a sentient CD platform...<p>> <a href="http://www.artificialbrains.com/spinnaker" rel="nofollow">http://www.artificialbrains.com/spinnaker</a>
We had looked at Asgard, but didn't use it because it used dedicated load balancers (e.g. separate ec2 instances) instead of ELBs (IIRC).<p>Our deployments were already using ELBs and we wanted to stay with that.<p>Does anyone know if this has changed with Spinnaker?<p>I would not be surprised if Spinnaker's canary/etc. features require finer-grained control over the traffic than an ELB with just course-grained "add/remove instance" gives you, so it probably makes sense.
Curious how this compares to Jenkins Workflow plugin suite. At first glance Spinnaker seems to be simpler and has a prettier UI. Workflow has a lot more customization possible and the crappy Jenkins UI to go along with it. I might look at Spinnaker anyways just to keep from gouging my eyes out on the Jenkins "UI".
I have a mixed feeling about this. I mean how do you Deliver Spinnaker. The project is fucking complex, if everything goes wrong you are pretty much done..
at a glance... seems nearly identical to OpsWorks. am i right? why would i use one or the other?<p>that said, and maybe i can answer my own question... OpsWorks has been a grand pain in the ass, so new options even built on AWS come welcome.
I really like they used Python for this sort of "system tool". Didn't know Netflix actually uses Python at all, I was expecting all of it to be Java.