14:01:05 #startmeeting meeting 14:01:05 Meeting started Mon Dec 7 14:01:05 2015 UTC. The chair is mvollmer. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:01:05 The meeting name has been set to 'meeting' 14:01:12 I hope the logs works today 14:01:26 yeah 14:01:33 .hello mvo 14:01:36 mvollmer: mvo 'Marius Vollmer' 14:01:52 .hello andreasn 14:01:53 andreasn: andreasn 'Andreas Nilsson' 14:02:14 #topic Agenda 14:02:19 * Debian 8 14:02:48 * tuned support 14:03:02 * container scanning 14:03:05 * realmd with non-freeipa 14:03:06 .hello stefw 14:03:07 stefw: stefw 'Stef Walter' 14:03:30 * Ideas vs. Issues 14:04:33 okay, let's go. 14:04:37 #topic Debian 8 14:04:43 I tink I have touched ground 14:04:48 all tests are green 14:05:03 only two bugs found in Debian, which is pretty good. :-) 14:05:14 many tests are skipped 14:05:50 https://mvo.fedorapeople.org/logs/test-fdcf2a96-debian-8/log.html 14:06:06 storage, kubernetes, and realm tests are skipped 14:06:20 and sosreport 14:06:21 well 14:06:22 are the skipped tests for things that are not packaged on debian? 14:06:31 yes 14:06:33 ie, those cockpit subpackages are not packaged there (yet)? 14:06:44 nothing is skipped because of bugs 14:07:15 i have to step back from this a bit 14:07:31 and write down the follow up work 14:08:11 we need to improve some UI scenarios, such as handling network interfaces that are not managed by NM 14:08:45 but I think we can pretty soon start testing on Debian 8 and expect it to be green. 14:09:03 do you mean on a system with both NM and something else? or no NM at all? 14:09:16 with both NM and something else 14:09:25 right 14:09:53 on Fedora, NM can manage traditional old text-file configuration, but on Debian it can not. I think. 14:10:04 ah, I see 14:10:17 is that deliberate from debians side? or just a bug? 14:10:18 so on Fedora you can let it manage everything and it will be alright even for greybeards 14:10:26 but on Debian you have to choose 14:10:53 and by default Debian chooses to not let NM manage the devices that were present during installation 14:10:57 (I think.) 14:11:00 ah, I see 14:11:11 seems deliberate 14:11:43 * mvollmer notes that he starts to get a grey beard 14:11:54 actually, silver 14:11:58 cool 14:12:32 okay, so #3202 is no longer WIP 14:12:47 I'll read over the review comments etc 14:13:01 so should we disable our NM ui (with curtains for instance) when it's not relevant on Debian? 14:13:09 maybe 14:13:15 I mean, yes, when it is not relevant 14:13:19 sure 14:13:24 I am not sure whether it is relevant 14:13:26 probably not 14:13:40 but the tests work OK 14:14:07 in any case, we should handle unmanaged interfaces 14:14:14 people have those also on Fedora 14:15:07 if that turns out nice, we might leave NM enabled on Debian, and maybe help people get their interfaces managed 14:15:39 but let's ask Debian also, of course 14:15:51 another thing worth mentioning: 14:16:14 user synch should probably be removed from the normal "add machine" flow 14:16:28 stefw and I had a discussion about this 14:16:53 and synching between Fedora and Debian is non-trivial because of the group differences 14:17:01 yes, we now have the ability to use disparate users between machines 14:17:03 and we don't need that synching to much anymore 14:17:06 we don't need to push people towards syncing 14:17:32 right now when adding a machine 14:17:53 if we can't login first try we push them toward syncing 14:18:17 it can still be available in other locationts 14:18:17 but doesn't need to be part of the flow 14:18:34 hmmm, i always get the syncing ui 14:18:46 yes, it always shows 14:18:47 me, too, I think 14:19:23 but i was wondering if we want to leave it in the case of a failed initial login 14:19:29 or remove it all together 14:19:43 currently it shows up as the last step of add server 14:19:43 oh ok 14:19:43 so lets make it conditional, yes 14:20:04 and call it "Create Users", maybe? 14:20:11 ok, i'll open a ticket 14:20:15 ok 14:20:43 I'll open issues for the other things 14:21:22 but let me see you nod: We want to test each PR on debian-8, just like we do with fedora-23, etc. 14:21:26 right? 14:21:29 * mvollmer nods 14:22:21 yup 14:22:22 I have actually found myself working on other things using my Debian VM as a devbox, just because that was in the command history 14:22:33 worked just fine 14:22:54 okay 14:22:58 next topic? 14:23:27 yup 14:23:39 #topic tuned support 14:24:01 Ryan Barry has contributed a plugin for tuned support 14:24:04 which is really great 14:24:12 tuned lets you set the CPU performance profile of a server 14:24:42 #info https://github.com/cockpit-project/cockpit/pull/3279 14:24:42 so if you would like it to use more power, and be faster, etc.. 14:24:43 the plugin is not ready to be merged 14:24:45 but it does work once it gets a little patch 14:24:50 #info https://trello.com/c/eRlWwPcu/12-tuned-support 14:25:00 yes, this is one of the features on our roadmap 14:25:25 so it's a very nice contribution 14:25:26 so i guess i have several questions 14:25:26 do we want to prioritize this and bump it up our roadmap 14:25:26 because someone has contributed it 14:25:28 and finish it up 14:25:34 I would say yes 14:25:43 the alternative, would be to get the minimum functionality finished 14:25:46 yes 14:26:05 and merge it early, and then finish it up later as a real feature 14:26:05 i would prefer the former 14:26:09 but likely i wouldn't be the one to do the work for that option :) 14:26:15 this needs some tests, right? 14:26:21 and a better design 14:26:26 right 14:26:41 I think a better design could be fairly straight forward for the minimum functionality 14:26:50 i should work on my bug backlog 14:26:50 we can see how much ryan wants to implement the design 14:27:00 but I can help with the tests 14:27:02 like moving it to the server frontpage and change the wording a bit 14:27:53 so start with this minimum, and then create a full feature out of it at a later point+ 14:27:55 ? 14:28:07 like "Tuned: part 2" 14:28:23 well that was one of the alternatives 14:28:29 if we can do it right, especially with design the first time around 14:28:31 i think that would be best 14:29:07 I've done some research before this meeting, since I hadn't heard about tuned before 14:29:08 I agree 14:29:35 but I haven't really figured out the capabilities of it 14:30:02 but I'll keep reading up on it 14:32:01 okay, conclusion is to try to do this right, correct? 14:32:18 yeah, i think so 14:32:19 andreasn, will you create a feature page? 14:32:22 sure 14:33:45 alright, next? 14:34:06 sure 14:34:07 #topic container scanning 14:35:02 I've done some more work on this. Filled out the feature page https://github.com/cockpit-project/cockpit/wiki/Feature:-container-security-scanning 14:35:35 and worked on mockups, but those are not 100% done yet. Maybe 90% there now 14:36:17 is anyone interested in the implementation part of that once it's done? 14:36:47 sure 14:36:54 cool 14:36:55 andreasn, are you thinking the "pushes to production" is part of this UI? 14:37:42 petervo: no, that would be a separate thing I think 14:37:45 is this on our roadmap? I can't see it. 14:38:04 https://trello.com/c/sE5cjZ6C/217-container-image-scanning 14:38:12 ok good 14:39:09 andreasn, should it be also listed here https://trello.com/c/ieN2nnXd/176-feature-roadmap ? 14:39:25 mvollmer: it's on the atomic roadmap (I thinkl) 14:39:35 yup https://trello.com/c/fhLkR7PZ/162-atomic-features 14:39:50 oh, look. tuned is also there! :) 14:40:04 ohh, right! 14:40:17 so much to do... 14:41:04 we can rest when we're dead 14:41:10 :) 14:41:20 \m/ 14:41:24 next topic? 14:41:37 #topic realmd with non-freeipa 14:41:44 this came up with Debian 14:42:02 Debian can't join FreeIPA because it doesn't have the client yet 14:42:12 (I hope that is a correct statement.) 14:42:25 (Maybe one can join FreeIPA in other ways, I don't know.) 14:42:29 what domain solution do they have? 14:42:50 But I think that Cockpit can _only_ join FreeIPA domains 14:42:57 that would be extremely hard 14:43:03 and the error message on Debian is not helpful 14:43:06 to join IPA without the client (it does a lot of things) 14:43:28 maybe soon FreeIPA can be treated as AD? 14:43:36 anyway, I don't know these things 14:44:01 so, I think the right thing on Debian would be to disable the domain button, actually. 14:44:35 just hide that whole row? 14:44:41 or we make sure that Cockpit can join non-FreeIPA domains. 14:45:06 Debian should be able to join AD domains 14:45:32 IPA domains won't show up as valid domains if realmd support for them is disabled 14:45:39 Cockpit only every calls KerberosMembership.Join() on realmd 14:45:43 this seems like a Debian bug 14:45:59 well it calls Discover() 14:46:08 how would it avoid thath? 14:46:19 I mean, it never tries to join via a different interface 14:46:29 if IPA support is properly disabled in Debian realmd 14:46:42 is KerberosMembership.Join the right thing to join to AD? 14:46:47 then cockpit will handle that case correctly (by not joining, or offering to join IPA domains) 14:46:50 mvollmer, yes 14:46:55 that's the whole point of realmd 14:47:00 to abstract that sorta stuff away 14:47:01 ok, I see 14:47:07 AD is kerberos based 14:47:10 how does it work in GNOME on Debian? 14:47:41 i imagine if you point realmd at an IPA domain using gnome-control-center you'll have the same behavior 14:48:58 I open an issue for this. 14:49:13 let's use the time for the remaining topics, I'd say 14:49:32 #topic Ideas vs. Issues 14:49:42 ohh, simo was here :-) 14:50:06 we discussed a bit elsewhere about moving very broad RFE style issues into an Ideas page 14:50:40 Sorry, I forgot about this meeting. Can we go back to the realmd discussion? 14:51:16 it would be best to keep the Issues to things that are reasonably going to have a conclusion 14:51:17 either because they're a bug and pretty much have to be fixed 14:51:17 or are assigned to someone who's going to fix it 14:51:17 or are concrete missing functidonality in an already implemented feature 14:51:19 First of all, I *think* Debian does in fact have an ipa-client these days. 14:51:32 sgallagh_, later, please 14:51:38 ok 14:51:41 Ping me. 14:51:42 thanks 14:52:06 broad ideas with no backing from someone who's going to contribute them should go onto the Ideas page 14:52:06 they can serve as inspiration, and ideally would find a contributor at some point in which case a pull request, and further 'issues' would result 14:52:06 does that make sense? 14:52:10 yeah, otherwise things are just going to get lost in the issue tracker 14:52:27 hmmm, looks like we're experiencing net splits or something 14:52:32 makes sense to me. 14:52:50 should I go ahead and create the page in the wiki? 14:53:15 the networkmanager idea fits what we have discussed above about handling unmanaged interfaces 14:53:25 andreasn, it exists 14:53:34 https://github.com/cockpit-project/cockpit/wiki/Ideas 14:53:44 nice 14:53:45 #info https://github.com/cockpit-project/cockpit/wiki/Ideas 14:53:45 This is the page 14:53:45 https://github.com/cockpit-project/cockpit/wiki/Ideas 14:53:45 and i've added 5 things so far 14:53:45 mvollmer, ok, could you remove the networkmanager item 14:53:46 and assign the bug to yourself? 14:53:58 yes 14:54:25 we should probably link to it from the main wiki page and maybe add a line or two about it to the Roadmap page 14:54:40 yes, and from the Hackfest page 14:54:46 and Contributing page 14:57:27 okay 14:57:44 #topic realmd with non-freeipa 14:57:50 sgallagh_, ping 14:57:50 mvollmer: Ping with data, please: https://fedoraproject.org/wiki/No_naked_pings 14:57:56 sgallagh_, ping with data 14:58:00 mvollmer: Heh 14:58:06 :-) 14:58:23 OK, so I know that Timo Aaltonen has been maintaining the FreeIPA-on-Debian/Ubuntu effort for a long while now 14:58:50 I'm 95% sure that ipa-client works on Debian now and I seem to recall hearing that they actually have the server as well these days 14:59:00 Though possibly only on Debian-Testing 14:59:03 freeipa-client is in unstable only, no? 14:59:27 Might be 14:59:36 https://tracker.debian.org/pkg/freeipa 15:00:13 it's still ahead of cockpit, of course. 15:00:17 That's teh server... 15:00:32 so when cockpit goes to unstable (fingers crossed), we have to look at this again, true. 15:00:59 The client landed in Debian at least a year ago, probably two 15:01:20 client and server are built from the same source package, no? 15:01:38 sgallagh_, yes, it landed in unstable 15:02:05 you are right, I should have said that more clearly. 15:02:17 we are testing on debian 8 now, which doesn't have it. 15:02:25 OK 15:02:53 mvollmer: Might be worth testing on recent Ubuntu as well. I *know* ipa-client is available there. 15:02:56 but cockpit will go to unstable of course, so have to figure out how we test that 15:03:30 Yeah, my experience with the Debian process in minimal. 15:03:36 s/in/is/ 15:04:38 mvollmer: Presumably unstable packages in Debian can depend on one another? 15:04:50 yes 15:04:51 I know apt has the "Recommends" concept; we could Recommends: ipa-client 15:05:11 ohh look at this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787593 15:05:21 we will run into this as well,I guess 15:05:32 or maybe not 15:06:19 anyway, thanks for reminding me that Debian 8 is not really the thing that Cockpit has to integrate with. 15:06:33 i started to forget aboutt hat 15:06:49 /me nods 15:07:33 ok, done? 15:07:38 I have nothing else 15:07:45 #topic Any other business 15:08:10 nothing, good. :) 15:08:13 #endmeeting