14:02:29 #startmeeting Weekly Cockpit meeting 2017-03-20 14:02:29 Meeting started Mon Mar 20 14:02:29 2017 UTC. The chair is andreasn. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:29 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:02:29 The meeting name has been set to 'weekly_cockpit_meeting_2017-03-20' 14:02:33 .hello 14:02:33 andreasn: (hello ) -- Alias for "hellomynameis $1". 14:02:42 .hello andreasn 14:02:43 andreasn: andreasn 'Andreas Nilsson' 14:02:46 .hello stefw 14:02:47 stefw: stefw 'Stef Walter' 14:03:06 .hello garrett 14:03:07 garrett: garrett 'Garrett LeSage' 14:03:26 [cockpit] petervo pushed 1 new commit to master: https://git.io/vyFNP 14:03:26 cockpit/master eaabf6c Stef Walter: common: Change 'dropping message' message to debug note... 14:03:33 [cockpit] petervo closed pull request #6156: common: Change 'dropping message' message to debug note (master...dropping-message-no-message) https://git.io/vyF4m 14:04:22 #topic Agenda 14:05:13 * Staging the verify container as a way to simply run the tests 14:05:27 [cockpit] cockpituous opened pull request #6159: Image refresh for rhel-7 (master...refresh-rhel-7-2017-03-20) https://git.io/vyFNQ 14:07:41 I guess that's all 14:07:54 #topic Staging the verify container as a way to simply run the tests 14:09:22 stefw: ? 14:09:29 oh hey 14:09:55 i'd like to change the test stuff around so that cockpit/infra-verify is the one stop entry point for running the verify tests (or any integration tests) locally on a machine 14:10:07 The goal: 14:10:11 1. Have a git checkout 14:10:18 2. sudo docker run cockpit/infra-verify 14:10:22 and have the tests build and start 14:10:32 obviously the current use cases of the cockpit/infra-verify containter should still work 14:10:35 but are we okay with that model? 14:10:52 3. sudo docker run cockpit/infra-verify [testsuite] 14:10:56 to run an additional test suite? 14:11:02 I am, but we need to think about how each case is invoked 14:11:05 or specific test suite 14:11:26 stefw, so all the current ways of running it would go away? 14:11:29 nope 14:11:32 or is this in addition to? 14:11:34 oh ok 14:11:37 the github-task stuff would be invoked with either an alternate --entrypoint 14:11:41 or perhaps a command line flag 14:11:57 which would be seamlessly included in the cockpit-verify.service file 14:12:10 i could even add that part first 14:12:19 so as to deploy to all the verify machines, before we do any breaking change 14:12:28 [cockpit] petervo pushed 4 new commits to master: https://git.io/vyFA9 14:12:28 cockpit/master 7963b66 Stef Walter: ws: Send Negotiate auth header unless we know GSSAPI is unavailable... 14:12:28 cockpit/master e897ec8 Stef Walter: test: Check that the kerberos login sends back a valid cookie... 14:12:28 cockpit/master 2406c52 Stef Walter: ws: Clear the environment in cockpit-session more regularly... 14:12:29 or perhaps we could have a new name/tag for the container? 14:12:32 the goal here is 14:12:39 1. Make it easy for people to get started with the tests 14:13:06 2. Work towards a simple way to stage our tests in other test runners 14:13:09 i forgot --privileged 14:13:14 I think it would be good 14:13:18 which is obviously part of the 'docker run' invocation above 14:13:21 as is likely '-i' 14:13:25 to produce output 14:14:51 yeah i'm on board 14:15:16 ok, hopefully some pull requests soon :) 14:15:24 there's quite a few issues 14:15:43 in order to make it work ... so the pull requests will a bit disconnected 14:15:52 i hope outlining the goal here is clear enough, and I can refer back to it 14:18:34 i guess that's the end of that topic 14:19:10 cool 14:19:14 #topic Open Floor 14:20:53 seems nothing 14:20:57 short meeting today. 14:21:01 #endmeeting