Re: [ansible-project] Re: Can inventory plugin "constructed" create a groups based on ansible_facts

Thank you guys, it was done by enabling facts caching. It was disabled that is why didn't work. -- 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 ansible-proj

[ansible-project] Can inventory plugin "constructed" create a groups based on ansible_facts

Hello community! A have plenty of EC2 servers in AWS and want to categorize them based on gathered from ansible_facts (by module setup), for example have group "CentOS" where ansible_facts['distribution'] == 'CentOS' and so on. But having file "inventory/constructed.yml": plugin: constructed s

Re: [ansible-project] Best way to organize your playbooks

details. > > Say what you will about Puppet but I would consider the reasoning behind > their roles and profiles and how it applies to Ansible: > https://puppet.com/docs/pe/2018.1/the_roles_and_profiles_method.html > > > Sent from my iPhone > > On Aug 1, 2019, at 1:49 AM, М

Re: [ansible-project] Best way to organize your playbooks

Awesome! Looks like a plan! Thanks! чт, 1 авг. 2019 г. в 07:44, Sebastian Meyer : > On 01.08.19 07:31, Михаил Политаев wrote: > > I have a several projects which describing installation 2 different > > applications. Each directory for application: > > > > app1/rol

[ansible-project] Best way to organize your playbooks

I have a several projects which describing installation 2 different applications. Each directory for application: app1/roles/common/main.yml app2/roles/common/main.yml But application have similar between them tasks which described in "main.yml" of role "common" What is the best way have only

Re: [ansible-project] Re: Problem with wildfly with Ansible

Glad to hear! ср, 31 июл. 2019 г., 14:40 Karther : > Hey, > > I have solve my problem, in fact i chack the file standalone.xml of my > application and there had synthax error. > > Thanks, > > Regards, > > Le mercredi 31 juillet 2019 10:37:47 UTC+2, Михаил Политаев

Re: [ansible-project] Re: Problem with wildfly with Ansible

on a question in a specific to application place. Ansible is not. As any other, not related to wildfly10, community probably will not help you. Look in a right place - community wildfly10. ср, 31 июл. 2019 г. в 10:36, Михаил Политаев : > When i lose something you will not find it in place wh

Re: [ansible-project] Re: Problem with wildfly with Ansible

i think > that one person have any idea. > > Thanks for your help, > > Regards, > > Le mercredi 31 juillet 2019 10:29:17 UTC+2, Михаил Политаев a écrit : >> >> Hey Karther! >> >> If you service *wildfly10 *not working after *systemctl start >> wi

[ansible-project] Re: Problem with wildfly with Ansible

Hey Karther! If you service *wildfly10 *not working after *systemctl start wildfly10.service *command, which not related to ansible then there is a problem directly in *wildfly10*, not ansible. Please ask better support or community of that service. Ansible here is not a problem. среда, 31 июл

Re: [ansible-project] Re: import_role from another directory

ster/lamp_simple/roles/common/tasks/main.yml Again install ntp in project "lamp_haproxy": https://github.com/ansible/ansible-examples/blob/master/lamp_haproxy/roles/common/tasks/main.yml ср, 31 июл. 2019 г. в 09:37, Михаил Политаев : > I know it. But i feel from one project to another I

Re: [ansible-project] Re: import_role from another directory

uly 31, 2019 at 11:50:48 AM UTC+5:30, Михаил Политаев wrote: >> >> If import_role cannot look to level up directories how we can avoid >> repeating myself with again and again writing base things which want to be >> included on all roles? >> >> среда, 31 июля 201

[ansible-project] Re: import_role from another directory

If import_role cannot look to level up directories how we can avoid repeating myself with again and again writing base things which want to be included on all roles? среда, 31 июля 2019 г., 8:16:10 UTC+2 пользователь Михаил Политаев написал: > > Hello team! > > My directory ansible

[ansible-project] import_role from another directory

Hello team! My directory ansible-repo follow: ├── base │ ├── group_vars │ │ └── all │ ├── roles │ │ └── common │ │ ├── handlers │ │ │ └── main.yml │ │ ├── tasks │ │ │ └── main.yml │ │ └── templates │ │ └── ntp.conf.j2 │ └── si

Re: [ansible-project] ansible_facts['ansible_os_family'] vs. ansible_facts['os_family']

Thanks for answer James! Also want to know dropping leading "ansible_" are not documented and i am asking not on vain or i just read without attention? вс, 28 июл. 2019 г., 22:16 James Cassell : > > On Sun, Jul 28, 2019, at 12:18 PM, Михаил Политаев wrote: > > Hello

[ansible-project] ansible_facts['ansible_os_family'] vs. ansible_facts['os_family']

Hello community! To determine how to reference variable which store OS family type i ran: ansible node1 -m setup Which throw a lot of output but there was: 192.168.24.24 | SUCCESS => { "ansible_facts": { ..., "ansible_os_family": "RedHat", ... }, "changed": fal

[ansible-project] Re: Directory to store ansible's playbooks

Thanks for answer! That is what I want to hear, to confirm that I am thinking in a right direction. среда, 24 июля 2019 г., 6:58:51 UTC+2 пользователь Михаил Политаев написал: > > Hello team! > > Read the documentation and didn't find where playbooks ansible should be > st

[ansible-project] Directory to store ansible's playbooks

Hello team! Read the documentation and didn't find where playbooks ansible should be store only advice that they should be under source control. I see /etc/ansible/roles directory installed by default. Is it mean that here should be /etc/ansible/playbooks? Or I can store playbook anywhere /op