15:00:38 #startmeeting Cockpit public meeting 2014-10-06 15:00:38 Meeting started Mon Oct 6 15:00:38 2014 UTC. The chair is andreasn. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:38 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:45 #meetingname Cockpit 15:00:45 The meeting name has been set to 'cockpit' 15:00:53 #chair andreasn mvollmer stefw sgallagh 15:00:53 Current chairs: andreasn mvollmer sgallagh stefw 15:00:59 #topic Welcome 15:01:07 .hellomynameis andreasn 15:01:08 andreasn: andreasn 'Andreas Nilsson' 15:01:15 .hellomyname is mvo 15:01:19 * stefw is here 15:01:20 .hellomynameis mvo 15:01:21 mvollmer: mvo 'Marius Vollmer' 15:01:34 .hellomynameis stefw 15:01:35 andreasn: stefw 'Stef Walter' 15:01:45 heh! :-) 15:01:55 #topic Agenda 15:02:20 * as mvollmer said, Fedora 21 15:02:22 Fedora 21, GSSAPI, Modular arch, roadmap? 15:02:39 yeah 15:03:06 #info agenda is Fedora 21, GSSAPI, Modular arch, Roadmap 15:03:17 #topic Fedora 21 15:03:56 I am running out of things to fix, stef is merging like a hero. 15:04:08 still have a ways to go ... 15:04:11 on merging 15:04:31 yes, and there will be things to fix about the pull requests 15:04:42 there is quite a bunch of pull requests 15:04:55 so, question: are we forgetting something important? 15:05:06 4 of them are f21-proposed 15:05:23 I would maybe look at #1176, and not much else 15:05:26 sgallagh, do you have any feedback on anything missing for f21? 15:05:51 andreasn, I think the pull request labels and milestones are not very consistent. 15:05:59 ah, ok 15:07:10 what do we need to do outside of cockpit? 15:07:21 NetworkManaer testing and release 15:07:34 stefw: Sorry, wasn't following. 15:07:37 One moment to read scrollback, please 15:07:40 sure 15:09:16 Ideally, I'd like the modular capabilities in sufficient shape that it might be feasible to add some domain-controller UI post-F21, but that's firmly a nice-to-have. 15:09:43 sgallagh, how much time do we have? 15:10:06 sgallagh, there's a slight chance these modular capabilities would land 15:10:09 but more importantly 15:10:11 they would not be stable 15:10:13 sgallagh, I was thinking to wrap up Fedora 21 from our point of view in this week. 15:10:23 and therefore any such domai-controller UI would be prototypical 15:10:28 mvollmer: Oct 14th is Beta Freeze 15:10:38 Like I said, firmly in the nice-to-have category. 15:10:39 let me reword that 15:10:49 there's a slight chance one branch towards the modular capabilities might land 15:11:04 so unfortunately, although it would have been nice, we're likely going to have to skip on this 15:11:11 sgallagh, so we'd need to have that by the end of this week, right? 15:11:52 Yes 15:12:01 right 15:12:24 so, let's see. :-) 15:12:35 everyone looks at stefw... 15:12:38 heh 15:13:04 so if we can't land the modulization stuff for f21 anyway, might be better to focus on polish stuff 15:13:12 or start moving on to the next stage 15:13:42 yup 15:14:27 stefw, what do you think, first prio is merging/rejecting the pull requests we ave? 15:14:38 yes 15:14:53 yes, very good. 15:15:31 then we make a release for F21 beta, and then we concentrate on the module stuff. 15:15:43 sounds good 15:16:09 if we can make it happen without regressions, we can then see whether we feel comfortable about putting it into F21 stable. 15:16:16 or just the copr. 15:16:43 i would be uncomfortable merging even the first modular code branch into f21 15:16:57 i would suggest we essentially stabilize f21 before we merge it 15:16:59 even if we do have more time 15:17:01 ok, much easier that way. 15:18:17 oh, right, the bot 15:18:43 #info no modularization work for f21 15:19:16 #info first priority is to merge the pull requests we have at https://github.com/cockpit-project/cockpit/pulls 15:19:33 cool 15:19:38 next topic? 15:19:40 #info Cockpit release for Fedora 21 will be cut at the end of this week. 15:20:01 #topic GSSAPI 15:20:05 #action everyone help stef with pull request review 15:20:19 sounds good 15:20:52 I'll rebase everything and run VERIFY 15:21:13 ok, GSSAPI? 15:21:45 Can we advertise it for F21? 15:22:24 I have to admit I have no idea what gssapi is 15:22:29 You can't log in as wheel with Kerberos, and you can't use really use Cockpit as non-hweel. 15:22:46 oh, is it the single-sign-on? 15:22:54 i don't think we can advertise it 15:23:13 but i like it being there since it lights a fire under people to actually fix the underlying platform bugs we have have listed. 15:23:20 yes. 15:23:43 sgallagh, does this affect our Fedora Server documentation or release notes? 15:23:55 remoting via ssh doesn't work with SSO either, right? 15:23:56 the fact that GSSAPI works, but actually doesn't (because no wheel)? 15:24:00 #info You can't log in as wheel with Kerberos, and you can't use really use Cockpit as non-hweel. 15:24:05 mvollmer, yes, that branch has not been merged yet 15:24:13 and needs rebasing, testing and fixing 15:24:21 stefw, should we try to do that? 15:24:28 yes, i think so 15:24:29 to make the fire hotter? 15:24:33 ok. 15:24:40 it would be nice to get that into f21, again for the reason above 15:24:47 so people can try out kerberos support 15:24:51 stefw: We haven't made any statements about SSO at all 15:24:53 #info even though not everything works, it's a good motivator for others to fix underlying platform bugs 15:24:54 and very easily reproduce the issues that don't work 15:24:57 sgallagh, ok, good to know 15:25:02 So I think continuing to not say anything is probably fine 15:25:05 #info finish #1226 for Fedora 21. 15:25:58 is that a action for stefw or mvollmer, or both? 15:26:08 both, I guess. 15:26:24 tbh, I have ignored that pr mostly... :-/ 15:26:31 #action mvollmer and stefw to finish #1226 for Fedora 21 15:26:50 great, next topic? 15:27:25 * mvollmer nods 15:27:40 #topic Modular architecture 15:28:13 so, as discussed, I'd say it has low priority for this week 15:28:18 sure 15:28:27 stefw, do you agree? 15:28:41 low priority for a merge 15:28:48 yes 15:28:52 but a high priority to get it in a reviewable and discussable state 15:29:00 too many people are waiting for this 15:29:13 and soon it will become a road block in our path forward 15:29:18 yes, but this week we really want to get F21 done. :-) 15:29:36 indeed 15:29:37 #info won't merge this week, since we're focusing on F21 15:29:53 #info really important path forward though 15:29:54 so for me that means working on the gssapi delegation pullreq 15:29:57 and doing reviews 15:29:59 next week, full speed on modular stuff 15:30:24 yes 15:30:26 #info next week will be focus on modular arch 15:30:30 great! 15:30:53 next topic? (hope I'm not rushing things) 15:31:07 no this is good 15:31:15 agree 15:31:18 #topic Roadmap 15:31:34 (this should be a regular topic every week) 15:31:47 (and means: update the roadmap wiki page) 15:31:50 #info first roadmap now up at https://github.com/cockpit-project/cockpit/wiki/Roadmap 15:32:41 ok, next four weeks: 15:32:49 let's remove the second bullet. 15:33:00 is mount points merged? 15:33:20 no, but it's in good shape and doesn't need to be pointed out, I'd say. 15:33:39 so likley to be merged this week? 15:33:53 stefw, mvollmer andreasn Hi, sorry for late coming at the meeting 15:33:57 let's add "SSO enablers" and move "Modular architecture" to 4w. 15:33:58 no worries 15:34:35 #info mount points fix in good shape to be merged soon. Can be removed from roadmap 15:34:44 something important was introduced today from QA side? 15:34:48 I'll just do it live 15:35:04 #info SSO enablers and Modular architecture can be moved from the section 4 months to 4 weeks 15:35:20 jscotka, let's add a topic to todays agenda. 15:35:46 we'll quickly finish the roadmap polish, and then we can talk about QA. 15:35:53 sounds good 15:36:03 thanks 15:36:20 so, atomic. 15:36:32 i think we should have a go at it soonish. 15:36:37 is Embedding still in the right place on the roadmap? 15:36:53 not sure... 15:37:09 is it tied to the navigation redesign? 15:37:19 I think so. stefw? 15:37:24 it is indeed 15:37:40 embedded will arrive along with modular work 15:37:44 and the two need to be considered together 15:37:51 so also 4 weeks actually? 15:38:00 right 15:38:05 navigation also? 15:38:07 yes, for a initial work 15:38:08 yeah 15:38:15 it would be nice if navigation did 15:38:23 it would make life much simpler 15:38:26 but it could be decopled 15:38:32 then "4 months" is empty. :-) 15:38:42 #info move navigation and embedability to 4 weeks 15:39:02 lets fill that from 2 years then :) 15:39:08 sounds like we need a more detailed plan of attack. 15:39:35 I have at least two things we need at "some point in the future" 15:39:48 better timers UI: https://github.com/cockpit-project/cockpit/issues/1297 15:40:10 Firewall support: https://github.com/cockpit-project/cockpit/issues/1297 15:40:19 yeah, 15:40:22 I make links.. 15:40:45 we have a whole bunch of things under https://github.com/cockpit-project/cockpit/issues/1297 15:41:15 might be a good time to update patternfly for example after f21 15:41:41 ups, wrong link above https://github.com/cockpit-project/cockpit/labels/enhancement 15:41:45 andreasn, is the link correct? it only talks about cron. 15:41:49 i see 15:41:59 patternfly update: https://github.com/cockpit-project/cockpit/issues/788 15:42:59 firewall support: https://github.com/cockpit-project/cockpit/issues/1094 15:43:16 andreasn, could you sort those into the roadmap offline? 15:43:22 yep! 15:43:34 and then we discuss that next week, or ad-hoc. 15:43:36 I'll put them under 2 years for now 15:43:53 i have put patternfly under 4m now. 15:44:01 #action andreas to sort issues from https://github.com/cockpit-project/cockpit/labels/enhancement on to the roadmap page 15:44:12 sounds correct 15:44:42 so server roles under 4 months? 15:44:48 sounds like it, no? 15:44:59 andreasn, Is there any future feature page, what is planned (like adding support for firewall as mentioned, or cron, or new one, like printers, etc) ? 15:45:02 ahh, actually, maybe not. 15:45:16 jscotka: yes, here you go https://github.com/cockpit-project/cockpit/wiki/Roadmap 15:45:49 andreasn, thanks, it is exactly what I was searching for :-) 15:45:49 ok, I think the 4w section is OK, so let's move on to QA, ok? 15:46:29 I would move Atomic stuff from 4 weeks to 4 months 15:46:40 but anyway, yeah, next topic 15:46:47 #topic Q&A 15:47:02 andreasn, yeah, agreed. 15:47:33 cool navigation redesign is coming! 15:47:53 yesss 15:48:07 I'm looking forward 15:48:13 * mvollmer makes complicated secret hadn shake with andreasn 15:48:19 hehe 15:48:51 so, what do we have for Q&A? 15:49:07 no, "QA" 15:49:13 Quality Assurance 15:49:21 :-) 15:49:45 sounds better :-) Q&A sound like questions & answers 15:49:48 oh, right 15:49:50 jscotka, so you are getting up to speed? 15:49:53 sorry 15:49:55 #topic QA 15:50:35 but I need some Questions :-) where are stored your #xy logs? 15:50:54 our IRC logs? 15:51:01 andreasn will send them around after the meeting 15:51:12 yes, ah okay 15:51:20 #undo 15:51:20 Removing item from minutes: 15:51:22 #undo 15:51:22 Removing item from minutes: 15:51:28 #topic QA 15:51:44 so it is not somewhere sent automatically 15:51:48 thanks sgallagh! 15:52:36 the meeting logs get stored here http://meetbot.fedoraproject.org/cockpit/ 15:53:16 I'll plan to integrate your current testsuite to internal testing infrastructure as first step. 15:54:15 jscotka, we currently run the tests only manually. 15:54:16 thanks for link to meetbot 15:54:45 and we would like to run them automatically for each github pullrequest 15:54:48 indeed 15:54:53 and publish the results 15:55:04 can the internal infrstructure do that? 15:55:05 I'll create it beaker compliant 15:55:10 #info jscotka will intergrate the current cockpit test suite to the interal RH testing infrastructure as a first step 15:55:46 beaker means testing on bare metal, right? 15:56:06 mvollmer, on various HW bare metal and virt as well 15:56:14 ok 15:56:47 so, can we publish the results? 15:56:51 It should also help me to find how it works now 15:57:23 right 15:57:23 mvollmer, it would be possible without problems 15:57:28 ok, nice! 15:58:41 so we hear from you how it is going, right? 15:58:41 how is testsute scheduled now? manually via make test? or is it internal part of build process? 15:58:58 we run it manually 15:59:03 during our work process 15:59:03 there is also travis 15:59:05 on our own machines 15:59:08 there is 'make check' 15:59:11 which is unit tests 15:59:19 that is scheduled automaticalcly via a github.com pull request 15:59:21 okay, 15:59:24 the integration test suite 15:59:26 does not run automatically 15:59:42 but the end goal would be to have it run automatically for each github.com pull request 15:59:48 and or update to a pull request 16:00:00 similar to how travis works for us right now, with the unit test suite 16:00:00 just like travis, basically. 16:00:10 #info end goal would be for the test suite to run for each github.com pull request 16:00:47 yes, I'll plan also to do it as part of our internal contionous integration project and results could be exported somewhere. 16:01:15 jscotka, puiterwijk has been working on this in the past. you could contact him. 16:01:42 mvollmer, thanks I'll do. 16:02:00 #action jscotka to contact puiterwijk, who's been working on this in the past 16:02:07 how long running testsuite takes now? 16:02:24 several minutes, if done in parallel 16:02:32 using the TEST_JOBS=4 environment variable 16:02:39 on one core, maybe 15 minutes? 16:02:42 but it can take about 15 minutes if TEST_JOBS is not defined 16:02:49 andreasn, It is so fast, so it is perfect 16:03:13 jscotka, it is still small, but it should grow! :-) 16:03:22 it doesn't feel fast to me when waiting on it :) 16:03:33 andreasn, I have to learn how to work with your hashtags syntax :-) 16:03:58 it's for the meeting minutes 16:05:23 jscotka, ok, so you are happy for now? Anything else to discuss now? 16:05:35 mvollmer, is there any possibility to automate also webUI tasks? I know that there is possible to use frameworks like seleniun-ish, but it is possible to do it via curl (with some stored secret cookie or another session storing abilities)? 16:05:45 mvollmer, yes I'm happy :-) 16:05:49 we use phantomjs 16:05:55 and sometimes ucrl 16:05:56 curl 16:06:04 stefw, perfect 16:06:16 most of our test suite revolves around automating web ui tasks 16:06:27 the integration test suite that is ^^ 16:06:30 very racy stuff... 16:06:47 most of the *unit* test suite revolves around testing backend logic, javascript internals, etc.. 16:06:59 mvollmer, stefw mvollmer for now it is everything. Too much info for now :-) 16:07:03 heh 16:07:06 ok! 16:07:10 one more thing, though! 16:07:41 jscotka, we have some abstractions in place that might suit you: 16:08:04 (hmm, how do I put this briefly.) 16:08:24 we had planned to run the tests on either local vms or remote openstack instances 16:08:38 so maybe you can hook into that when running things on beaker. 16:08:56 just to keep in mind that there is already something in the code that might do this. 16:09:00 mvollmer, perfect, I hope that in next 2 weeks I'll understand that 16:09:07 when you get to it, just ask again for the details. 16:09:29 mvollmer, thanks a lot 16:09:59 nowadays I undestand Cockpit only from user side :-) 16:10:25 all right, we're 10 past the hour. Anything else for the meeting? 16:10:50 * mvollmer puts down pencil. 16:11:04 all right 16:11:11 * jscotka leaving&eating :-) 16:11:20 enjoy! 16:11:22 thanks everyone for your time! 16:11:27 #endmeeting