19:00:57 #startmeeting core public irc meeting 19:00:57 Meeting started Tue Nov 20 19:00:57 2018 UTC. 19:00:57 This meeting is logged and archived in a public location. 19:00:57 The chair is bcoca. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:57 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:57 The meeting name has been set to 'core_public_irc_meeting' 19:01:12 o/ 19:01:23 #topic to mount or not to mount https://github.com/ansible/ansible/pull/48608 19:01:25 * gundalow waves 19:01:46 #chair sdoran gundalow 19:01:46 Current chairs: bcoca gundalow sdoran 19:01:50 @sivel? 19:01:53 @abadger1999 ? 19:02:06 think the 3 of us have handled mount 'the most' 19:02:09 Hello 19:02:35 mount2 and fstab modules 19:02:48 2 main options i think we can add (while we rewrite whoel thing) are 'update_fstab' and 'manage_mount_dir' 19:03:00 ^ though mount2 and fstab also appeals to me 19:03:27 specially since current is very ... lineinfileish ... 19:03:28 As booleans? 19:03:50 taht is my current thinking, but if you have other types that fit better? 19:04:08 I'm in favor of mount2 and fstab. 19:04:15 I am in agreement with mount2 and fstab 19:07:21 so we all give up on current mount module and expect it to die slow death? 19:07:34 I could see an update_fstab boolean option (not sure of the other as this module is named "mount" so it feels like everything should mount and unmount... only fstab being optional.)... but I would much rather people spend time on making two separate modules since they are very different things. 19:08:12 currently it deletes mountpoint on unmount ... which is really bad imo, but we should not change outright 19:08:28 ah. 19:08:44 only reason i suggest that, since currently it creates/removes it 19:08:49 Okay, so separate from the fstab versus mount functionality altogether. 19:09:00 yep ... i would not add any of it to mount2 19:09:05 19:09:19 its just current behaviour is bad and since we cannot realy just change it, toggle seems least bad solution 19:10:31 I could see both booleans, still would rather people spent time creating the two new modules. 19:10:52 agreed 19:11:04 so we can answer that on ticket 19:11:09 19:11:10 Yep. 19:11:17 @sivel that works for you? 19:11:26 anyone else have opinion? 19:12:15 sorry, off doing 3 things 19:12:22 who isn't? 19:12:40 but yes. 2 new modules 19:13:04 k, i'll let you respond to author, that we prefer 2 modules, but i thin that if they insist on just option, we should accept for now 19:13:10 just bikeshed on name 19:14:47 #topic https://github.com/ansible/ansible/pull/46675 19:15:00 @rajeevarakkal ? 19:15:25 #topic https://github.com/ansible/ansible/pull/47690 19:15:45 ^ need more eyes on it, lgtm but want to make sure rest dont see issues with it 19:16:20 @bcoca Well... new option that's a boolean rather than new state. (for the mount summary) 19:16:44 yeah, states are unchanged, just what happens during those states 19:16:58 'also update fstab' and 'also manage dir' 19:17:05 ^ 2 main asks for it 19:17:16 with 'not' being what some people ask 19:17:58 so no one against returning regex matches with wait_for ? 19:18:29 #topic open floor 19:18:41 =1 wait_for 19:18:43 +1 19:19:00 had me there for a sec with =1 .... 19:19:19 I would changelog things like that 19:19:29 But the code looks good. 19:19:42 btw, we need to wrap this meeting up within 10 minutes today 19:19:55 Changing sleep 10 to sleep 3 in the integration test... not sure if that is good. 19:19:56 at open floor, if nothing else, i'll close sson 19:20:09 that was ask from reviewers 19:22:25 I think that wait_for addition is fine. The UI is a bit convoluted since you kinda have to understand somewhat how `re` and groups work. 19:22:37 bcoca: Heh, you merged too quickly.. 19:22:46 Made the comment about hte timeout change on the ticket. 19:22:52 And it didn't have a changelog yet. 19:23:04 abadger1999: looking at the blame, that line was added with 10 seconds from the initial commit 19:23:12 so doesn't seem we adjusted it 19:23:27 https://github.com/ansible/ansible/commit/0a972ea6bf39794de406a3a4780977cad15e999b 19:23:35 just as an FYI 19:23:47 but yes, changelogs 19:23:49 19:24:18 well, since no new topics, going to end this in 1 min 19:26:31 #endmeeting