|
|
|
|
|
|
by mpdehaan2
4332 days ago
|
|
|
I'm not finding the new generation term particularly meaningful. One thing that was somewhat unique about Ansible was it was designed for rolling updates as the initial use case, and the desire to solve deployment problems rather than just CM problems. Everybody tends to view orchestration differently, so see our take: http://www.ansible.com/blog/orchestration-you-keep-using-tha... and http://www.ansible.com/blog/2013/11/29/ansibles-architecture... Ultimately, for us, it meant boiling back a lot of things to base concepts, and taking parts we liked from a lot of different things. But is there a generation? I don't think so. Some models make things a bit more or less flexible, or allow different capabilities. |
|
|