Please leave a comment regarding any agenda item you wish to discuss. If you don't show up for the meeting, your item will be skipped.
If your IRC nick is different from your Github username, leave that as well.
See https://github.com/ansible/community/blob/master/meetings/README.md for the schedule
Once an item has been addressed it should get strike-though ~~strike-though~~
@gundalow would like to discuss https://github.com/ansible/proposals/issues/65
@pilou- would like request reviews for PR#23862.
@dagwieers would like to discuss "guidance on ordered dictionaries for Windows modules. I prefer a common solution. ansible/ansible#25265 (comment)"
@dagwieers
Would like to discuss:
The purpose of connection: local -- ansible/ansible#24083
Allowing host-lists (rather than dicts) in YAML inventories -- ansible/ansible#22567
2017-06-06 Meeting
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-06-06/public_core_meeting.2017-06-06-19.00.html
13:10 Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2017-06-06/public_core_meeting.2017-06-06-19.00.txt
13:10 Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-06-06/public_core_meeting.2017-06-06-19.00.log.html
New messages
@azaghal would like to discuss if there is anything else they could do to have the following pull requests merged:
@alikins would like to discuss the fact related prs at
Both add more detail about storage devices and mount points to facts that could be useful, but could also be too much.
2017-06-08 Meeting
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-06-08/public_core_meeting.2017-06-08-15.00.html
Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2017-06-08/public_core_meeting.2017-06-08-15.00.txt
Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-06-08/public_core_meeting.2017-06-08-15.00.log.html
I'd like to discuss autotagging roles with their name: https://github.com/ansible/ansible/pull/25132
Edit:
Follow-up in proposal https://github.com/ansible/proposals/issues/66
2017-06-13 Meeting
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-06-13/ansible_core_meeting.2017-06-13-19.00.html
12:41 Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2017-06-13/ansible_core_meeting.2017-06-13-19.00.txt
12:41 Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-06-13/ansible_core_meeting.2017-06-13-19.00.log.html
@cben I'd like to discuss https://github.com/ansible/ansible/pull/25106,
first step of contributing ManageIQ modules from https://github.com/dkorn/manageiq-ansible-module/
Ansible Contributor Summit 4 (Part of AnsibleFest 2017 London)
Agenda for Contributor Summit has finalised can be found at https://public.etherpad-mozilla.org/p/ansible-summit-june-2017-agenda.
As a reminder, it will be in #ansible-meeting and BlueJeans
Note that there are sub pages for each topic. It's on the sub pages where you can add any topics there, rather than on the main agenda page.
@thaumos I think you mean June :)
And is there a core meeting today (Thursday 15th June)?
@cben, there is one today.
Of course I meant June! I don't know why you all are saying otherwise ;-)!
@itdependsnetworks, I am going to review this PR. So stand by.
2017-06-15 Meeting
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-06-15/ansible_core_meeting.2017-06-15-15.00.html
Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2017-06-15/ansible_core_meeting.2017-06-15-15.00.txt
Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-06-15/ansible_core_meeting.2017-06-15-15.00.log.html
I'd like some support to merge some of my PRs. Maintaining and rebasing them unmerged is getting to be a pain and quite a few of them are "ready" to merge.
Simple to merge
Needs AWS CI Permissions then should be reasonable merge
Needs comments and reviews.
Waiting for other merges above
I would like to discuss PR ansible/ansible#25950 and PR ansible/ansible#26028
we need to discuss getting rid of docstring format for metadata for 2.4 (this was only added for 2.4).
* Docstring format is currently unwritable by tools as it was added without updating metadatatool.py to handle the format.
* The docstring format adds a third way that metadata could be implemented (in addition to dict format and yaml string format).
* The docstring format is unnecessary for metadata. It was added for making documentation of filters and tests. Unlike documentation, we do not want each individual filter in a file to have its own metadata. Trying to tell people (and the bots) that "only these three functions in filters/mathstuff.py are supported by core. All the rest are supported by community" will be horridly painful. We should just separate out the filters that have different metadata into different files.
I would like to discuss https://github.com/ansible/ansible/pull/24576 and https://github.com/ansible/ansible/pull/25791 which both attempt to tackle the same issue (making a subset of documentation).
2017-06-27 Meeting
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-06-27/core_meeting.2017-06-27-19.00.html
13:04 Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2017-06-27/core_meeting.2017-06-27-19.00.txt
13:04 Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-06-27/core_meeting.2017-06-27-19.00.log.html
2017-06-29 Meeting
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-06-29/core_meeting.2017-06-29-15.00.html
08:45 Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2017-06-29/core_meeting.2017-06-29-15.00.txt
08:45 Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-06-29/core_meeting.2017-06-29-15.00.log.html
Discuss changing current behavior of failed filter now that core engine ignores the rc task return value- current implementation of failed triggers on nonzero RC, but it probably shouldn't anymore. (win_command/win_shell failure tests were false-passing in devel due to this issue)
Just bumping https://github.com/ansible/ansible/pull/20717~~
https://github.com/ansible/ansible/pull/25865 Should this be a role?
ansible/ansible#26335
Apologies, I won't make the meeting (5am) but would like to get it either merged or feedback as to any further improvements / alternative implementations.
Could you please add ansible/ansible#20717 to today's agenda? I will try and be on.
Improve YAML inventory support: https://github.com/ansible/ansible/pull/22567~~
Hello, I would like to speak about a project I began : KIKIN
KIKIN helps to start with Ansible.
It manages user database, ssh keys generation, hosts connections and SSH parameters.
I think it can help system admins to quickly test Ansible and simply begin to use it. Code in very beta state is available here : https://owncloud.liberasys.com/index.php/s/IqmOWKJQ6X44HI8
Nickname I will use : ghusson (Liberasys is the commercial name of my company)
2017-07-11 Meeting
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-11/engine_meeting.2017-07-11-19.00.html
12:59 Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2017-07-11/engine_meeting.2017-07-11-19.00.txt
12:59 Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-11/engine_meeting.2017-07-11-19.00.log.html
T
x2 the kubernetes connection plugin fun
https://github.com/ansible/ansible/pull/24960
https://github.com/ansible/ansible/pull/26668
2017-07-13 Meeting
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-13/core_meeting.2017-07-13-15.00.html
09:32 Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2017-07-13/core_meeting.2017-07-13-15.00.txt
09:32 Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-13/core_meeting.2017-07-13-15.00.log.html
For next meeting I would like to speak about https://github.com/ansible/ansible/pull/26641
Introducing testing suite for openssl_* modules https://github.com/ansible/ansible/pull/26684
Introducing https://github.com/ansible/ansible/pull/22756 (support multiple vault passwords)
For the next meeting I'd like to talk about the HPE OneView FcNetworkModule https://github.com/ansible/ansible/pull/26026~~
2017-07-18 Meeting
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-18/ansible_meeting.2017-07-18-19.00.html
12:58 Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2017-07-18/ansible_meeting.2017-07-18-19.00.txt
New messages
12:58 Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-18/ansible_meeting.2017-07-18-19.00.log.html
I would like to discuss merging https://github.com/ansible/ansible/pull/25323 (new xml module)
I would like to discuss: ansible/ansible#26729 (fix searched paths in DataLoader.path_dwim_relative).
2017-07-20 Meeting
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-20/ansible_meeting.2017-07-20-15.01.html
08:45 Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2017-07-20/ansible_meeting.2017-07-20-15.01.txt
08:45 Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-20/ansible_meeting.2017-07-20-15.01.log.html
@dagwieers, we'll still cover your item when you hop onto the next meeting!
I would like to discuss introducing https://github.com/ansible/ansible/issues/15460~~
2017-07-25 Meeting
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-25/ansible_meeting.2017-07-25-19.00.html
12:59 Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2017-07-25/ansible_meeting.2017-07-25-19.00.txt
12:59 Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-25/ansible_meeting.2017-07-25-19.00.log.html
new feature to group_by https://github.com/ansible/ansible/pull/26401~~
When the fetch module downloads a single file to a directory specified without a trailing slash it currently downloads the file and then errors out. One of those is a bug, we need to decide which one in order to fix it. Full details: https://github.com/ansible/ansible/issues/27312~~
2017-07-27 Meeting
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-27/ansible_meeting.2017-07-27-15.00.html
Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2017-07-27/ansible_meeting.2017-07-27-15.00.txt
Log: https://meetbot.fedoraproject.org/ansible-meeting/2017-07-27/ansible_meeting.2017-07-27-15.00.log.html
Where is the issue for the next meetings in August, has that already been created?
If we get august ticket , add this https://github.com/ansible/ansible/pull/18662 (mostly to bikeshed on option name)
Add PR# 27519 for discussion: https://github.com/ansible/ansible/pull/27519~~
Can we reconsider the new ansible_facts namespace and shorten it to just facts ? Since we are in Ansible anyway, having to specify ansible_facts for every fact seems pretty redundant.
Could we also get rid of the ansible_ prefix for each fact in the new namespace? Since we now have the ansible_facts namespace that pretty much defeats the purpose of having that prefix.
So in the end, I would prefer that
python~~
~~ansible_os_distribution~~
~~
becomes accessible as
python~~
~~facts.os_distribution~~
~~
rather than the existing implementation
python~~
~~ansible_facts.ansible_os_distribution~~
~~
This will be a lot more convenient writing playbooks then the current implementation.
August meeting agenda: https://github.com/ansible/community/issues/220
Most helpful comment
x2 the kubernetes connection plugin fun
https://github.com/ansible/ansible/pull/24960
https://github.com/ansible/ansible/pull/26668