Public Core Meeting Agenda - June, July 2017

[thaumos]

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~~

[thaumos]

@gundalow would like to discuss ansible/proposals#65

[thaumos]

@erasmix would like to discuss PR#21857 and PR#21764

[thaumos]

@pilou- would like request reviews for PR#23862.

[thaumos]

@dagwieers would like to discuss "guidance on ordered dictionaries for Windows modules. I prefer a common solution. ansible/ansible#25265 (comment)"

[thaumos]

@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

[thaumos]

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

[thaumos]

@cyberark-bizdev would like to discuss PR#21857 and PR#21764

@erasmix will be attending
@cyberark-bizdev will be in standby for discussion

[thaumos]

@azaghal would like to discuss if there is anything else they could do to have the following pull requests merged:

• Implement ability to limit module documentation building ansible#24576
• New module: Add module for manipulating the dconf database (system/dconf) ansible#23015
• Refactor and improve gconftool2 module ansible#22956

[alikins]

@alikins would like to discuss the fact related prs at

• More statvfs info for mount facts rebase 12073 ansible#25454 (based on Add new size computation on mountpoint (used space, block size/used/a… ansible#12073)
• Add UUID, label and id links to devices when building facts (based on 23477) ansible#25448 (based on Provide all available persistent IDs (labels, uuids, etc) for block devices ansible#23477)

Both add more detail about storage devices and mount points to facts that could be useful, but could also be too much.

[thaumos]

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

[robinro]

I'd like to discuss autotagging roles with their name: ansible/ansible#25132

Edit:
Follow-up in proposal ansible/proposals#66

[thaumos]

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]

@cben I'd like to discuss ansible/ansible#25106,
first step of contributing ManageIQ modules from https://github.com/dkorn/manageiq-ansible-module/

[gundalow]

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]

NO MEETING: Tuesday 20th June

NO MEETING: Thursday 22th June

NEXT MEETING: Tuesday 27th June

[willthames]

@thaumos I think you mean June :)

[cben]

And is there a core meeting today (Thursday 15th June)?

[itdependsnetworks]

Can you add the review of:

ansible/ansible#20717

to the list?

[thaumos]

@cben, there is one today.

Of course I meant June! I don't know why you all are saying otherwise ;-)!

[thaumos]

@itdependsnetworks, I am going to review this PR. So stand by.

[thaumos]

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

[mikedlr]

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

1. Fix hacking/test-module to allow running modules with pdb ansible#23339 - a trivial bug fix in hacking - a docs question arose, but that should be a separate PR merged
2. Mdd psql user aws fix ansible#23988 - a bug fix for postgresql - this lacks tests, however that in no way makes the situation worse than currently. The tests will require creating an RDS so really depend on RDS split updated with new integration tests [slow tests] ansible#25646 below - thus waiting for them will considerably delay this. merged
3. aws working group - add a utility modules file about what goes there #187 - community / needs AWS

Needs AWS CI Permissions then should be reasonable merge

1. RDS split updated with new integration tests [slow tests] ansible#25646 - RDS split updated with new integration tests
2. Lambda policy with tests - integration tests for PR #20890 ansible#24951 - Lambda policy with tests
3. Lambda integration tests ansible#24722 - Lambda integration tests
4. Lambda modules refactored to use new ansible.module_utils.aws.core. ansible#26059 - Lambda using new aws utils

Needs comments and reviews.

1. aws.core in new aws dir in module utils - module with AnsibleAWSModule class and fail_json_aws ansible#25780 - aws module with AnsibleAWSModule class in module utils
2. [WIP] new aws/rds module utility python module  ansible#26594 - rds.py utilities file

Waiting for other merges above

1. new RDS modules need rds utility merge first
   1.1. new rds_instance_facts module - split of RDS module ansible#26598 - new rds_instance_facts module
   1.2. new rds_snapshot_facts module - split of RDS module ansible#26599 - new rds_snapshot_facts module
   1.3. [obsolete] new rds_instance module - split of RDS module ansible#26602 - new rds_instance module
   1.4. new rds_snapshot module - split of RDS module ansible#26604 - new rds_snapshot module
   1.5. integration tests for RDS modules - split of RDS module ansible#26606 - integration tests for RDS modules

[cyberark-bizdev]

I would like to discuss PR# 21857 and 21764

[dagwieers]

I would like to discuss PR ansible/ansible#25950 and PR ansible/ansible#26028

[abadger]

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.

[thaumos]

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

[yaacov]

For next meeting I would like to speak about ansible/ansible#26641

[Spredzy]

Introducing testing suite for openssl_* modules ansible/ansible#26684

[alikins]

Introducing ansible/ansible#22756 (support multiple vault passwords)

[fgbulsoni]

For the next meeting I'd like to talk about the HPE OneView FcNetworkModule ansible/ansible#26026

[thaumos]

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

[dagwieers]

I would like to discuss merging ansible/ansible#25323 (new xml module)

[pilou-]

I would like to discuss: ansible/ansible#26729 (fix searched paths in DataLoader.path_dwim_relative).

[bcoca]

ansible/ansible#20119

[thaumos]

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

[thaumos]

@dagwieers, we'll still cover your item when you hop onto the next meeting!

[mkrizek]

I would like to discuss introducing ansible/ansible#15460

[thaumos]

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

[bcoca]

new feature to group_by ansible/ansible#26401

[abadger]

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: ansible/ansible#27312

[thaumos]

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

[liquidat]

Where is the issue for the next meetings in August, has that already been created?

[bcoca]

If we get august ticket , add this ansible/ansible#18662 (mostly to bikeshed on option name)

[cyberark-bizdev]

Add PR# 27519 for discussion: ansible/ansible#27519

[dagwieers]

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.

[bcoca]

ansible/ansible#27537

[abadger]

August meeting agenda: #220