# Task workflow

**URL:** <https://forum.ansible.com/t/task-workflow/12065>\
**Category:** Ansible Project\
**Created:** [November 2, 2012, 7:35pm UTC](https://forum.ansible.com/t/task-workflow/12065 "2012-11-02T19:35:54Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Edgars](https://avatars.discourse-cdn.com/v4/letter/e/f17d59/32.png) [@Edgars](https://forum.ansible.com/u/Edgars)\
**Post date:** [November 2, 2012, 7:35pm UTC](https://forum.ansible.com/t/task-workflow/12065/1 "2012-11-02T19:35:54Z")

</div>

Hi everyone!

Before Ansible I was using Rundeck (actually I still am) and there is one thing which is in Rundeck and which I miss in Ansible (or I just cant find it) - task workflow. Is there a way to define in what order tasks are performed? What I mean is - sometimes I need to perform all tasks on one node after another, node by node. But then again I might need to perform one task on all nodes and then next task on all nodes… task by task. Is this possible in Ansible?

I hope explained clear enough.

Thanks,  
Edgars

---

<div class="post-metadata">

**Author:** ![Brian\_Coca1](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@Brian\_Coca1](https://forum.ansible.com/u/Brian_Coca1)\
**Post date:** [November 2, 2012, 7:37pm UTC](https://forum.ansible.com/t/task-workflow/12065/2 "2012-11-02T19:37:58Z")

</div>

put all tasks you want to run on each host in one play, create plays for tasks you want to run across all hosts before going on to the next play.

---

<div class="post-metadata">

**Author:** ![Romeo\_Theriault](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@Romeo\_Theriault](https://forum.ansible.com/u/Romeo_Theriault)\
**Post date:** [November 2, 2012, 7:39pm UTC](https://forum.ansible.com/t/task-workflow/12065/3 "2012-11-02T19:39:22Z")

</div>

Also, check out the serial option, this allows you to limit how many  
hosts a play happens on before moving onto the next host:

[http://ansible.cc/docs/playbooks2.html?highlight=serial#rolling-updates](http://ansible.cc/docs/playbooks2.html?highlight=serial#rolling-updates)

Romeo

---

<div class="post-metadata">

**Author:** ![Walid](https://avatars.discourse-cdn.com/v4/letter/w/ea5d25/32.png) [@Walid](https://forum.ansible.com/u/Walid)\
**Post date:** [June 19, 2013, 4:05pm UTC](https://forum.ansible.com/t/task-workflow/12065/4 "2013-06-19T16:05:57Z")

</div>

So would Ansbile replace completely the need and usage for rundeck?

---

<div class="post-metadata">

**Author:** ![Brian\_Coca1](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@Brian\_Coca1](https://forum.ansible.com/u/Brian_Coca1)\
**Post date:** [June 19, 2013, 8:33pm UTC](https://forum.ansible.com/t/task-workflow/12065/5 "2013-06-19T20:33:57Z")

</div>



---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [June 19, 2013, 9:15pm UTC](https://forum.ansible.com/t/task-workflow/12065/6 "2013-06-19T21:15:00Z")

</div>

Yes, rundeck is basically a GUI for pushing scripts (but lacks the resource model).

Also, if you want a GUI, AnsibleWorks AWX completely eliminates the need for something like a Rundeck by allowing you to trigger playbooks graphically (and dive into their results and track their history over time).

We demoed this at AnsibleFest and should have some more details up on our website soon.

---

<div class="post-metadata">

**Author:** ![Brian\_Coca1](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@Brian\_Coca1](https://forum.ansible.com/u/Brian_Coca1)\
**Post date:** [June 19, 2013, 11:04pm UTC](https://forum.ansible.com/t/task-workflow/12065/7 "2013-06-19T23:04:20Z")

</div>

whatis GUI? this webby interface you speak of sounds forgein to me.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [June 19, 2013, 11:12pm UTC](https://forum.ansible.com/t/task-workflow/12065/8 "2013-06-19T23:12:01Z")

</div>

[http://www.ansibleworks.com/ansibleworks-awx/](http://www.ansibleworks.com/ansibleworks-awx/)

---

<div class="post-metadata">

**Author:** ![Edgars](https://avatars.discourse-cdn.com/v4/letter/e/f17d59/32.png) [@Edgars](https://forum.ansible.com/u/Edgars)\
**Post date:** [June 20, 2013, 7:36am UTC](https://forum.ansible.com/t/task-workflow/12065/9 "2013-06-20T07:36:37Z")

</div>

I haven’t used Rundeck for a while, but last time when I did, it was just command dispatcher with GUI. It lacked a lot of features to be called configuration manager.

Edgars

---

<div class="post-metadata">

**Author:** ![Bob\_Tiernay](https://avatars.discourse-cdn.com/v4/letter/b/b3f665/32.png) [@Bob\_Tiernay](https://forum.ansible.com/u/Bob_Tiernay)\
**Post date:** [December 17, 2013, 4:33pm UTC](https://forum.ansible.com/t/task-workflow/12065/10 "2013-12-17T16:33:19Z")

</div>

Actually Rundeck has a resource model and a number of plugins associated with it

[http://rundeck.org/docs/administration/node-resource-sources.html](http://rundeck.org/docs/administration/node-resource-sources.html)

I should also mention that Rundeck is more than just a GUI. It can be used completely in the shell. One benefit is has over AWX is that there is no limit in the number of nodes you can use for free.

ps. I’m not affiliated with Rundeck. I actually use both systems for different reasons. I think of Rundeck as the Jenkins for Ops.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [December 17, 2013, 4:48pm UTC](https://forum.ansible.com/t/task-workflow/12065/11 "2013-12-17T16:48:58Z")

</div>

Many many thousands of people use Ansible with Jenkins.

– Michael
