tou ahould check out AWX
On Thu, Dec 13, 2018 at 12:19 AM pradeep.hk <[email protected]> wrote:
> Got it. Thanks for your time.
> My requirement is to be able to sequence together tasks(to create a
> workflow) and after some prototyping, I found ansible playbook to meet that
> requirement.
> But then, scalability is turning out to be an issue. If we could daemonize
> the ansible process so that it can receive requests and execute playbook in
> a thread, that would scale.
> But then, that is not how ansible is supposed to work
>
>
> On Wednesday, December 12, 2018 at 5:02:56 PM UTC+5:30, Kai Stian Olstad
> wrote:
>>
>> On 12.12.2018 11:22, pradeep.hk wrote:
>> > The requirement is to be able to launch a playbook on receiving a
>> > request
>> > (ie on demand). So, if 100 requests are received, it will result in 100
>> > playbooks being executed parallely.
>> > You mentioned - Ansible uses about 50MB of memory per playbook. Is
>> > there
>> > something that can be done to optimize on that ?
>>
>> 50MB is just the minimum, it might be a lot more depending on playbook.
>> I highly doubt there is much that can be done.
>>
>> Just a Hello World in python uses 7MB
>>
>> $ /usr/bin/time -f %M python -c 'print "Hello World"'
>> Hello World
>> Mem used in kB: 7316
>>
>>
>>
>> An Ansible equivalent Hello World uses 48MB
>>
>> $ /usr/bin/time -f "Mem used in kB: %M" ansible-playbook test.yml
>>
>> PLAY [localhost]
>> ***********************************************************
>>
>> TASK [debug]
>> ***************************************************************
>> ok: [localhost] => {}
>>
>> MSG:
>>
>> Hello World
>>
>>
>> PLAY RECAP
>> *****************************************************************
>> localhost : ok=1 changed=0 unreachable=0
>> failed=0
>>
>> Mem used in kB: 48316
>>
>>
>> If you use Ansible dynamic inventory you can easily change the inventory
>> depending on the dynamic demand.
>>
>
>> --
>> Kai Stian Olstad
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/6d1609ed-7b2e-4067-af41-ad40de8e78ff%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/6d1609ed-7b2e-4067-af41-ad40de8e78ff%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Jonathan lozada de la matta
AUTOMATION PRACTICE
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAFYJA%2BKrbG5mRd%2B9o%3DrrhzKzxrUCP35VscvEUUaq9MZJ2AOhMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
