16:05:38 #startmeeting Cockpit meeting 2014-11-24 16:05:38 Meeting started Mon Nov 24 16:05:38 2014 UTC. The chair is andreasn___. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:05:38 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:05:56 #meetingname Cockpit 16:05:56 The meeting name has been set to 'cockpit' 16:06:11 #chair mvollmer stefw sgallagh andreasn 16:06:11 Current chairs: andreasn andreasn___ mvollmer sgallagh stefw 16:06:32 /me waves 16:06:35 .hellomynameis andreasn 16:06:36 andreasn___: andreasn 'Andreas Nilsson' 16:06:40 .hello mvo 16:06:40 .hello sgallagh 16:06:40 .hello stefw 16:06:40 mvollmer: mvo 'Marius Vollmer' 16:06:43 sgallagh: sgallagh 'Stephen Gallagher' 16:06:46 stefw: stefw 'Stef Walter' 16:07:03 #topic agenda 16:07:11 what do we have this week? 16:07:14 * Usability of host switcher 16:07:17 * Trello for roadmap? 16:07:30 * Report on channel metrics 16:07:38 * Report on components 16:07:46 or status rather 16:08:12 * Status of FS channels 16:11:21 am I back? 16:11:21 ugh 16:11:26 yup 16:11:35 sorry about that. Funky connection 16:12:06 did I manage to create the topic, or was that while being actually disconnected? 16:12:20 no topic yet 16:12:46 all right, lets see 16:12:51 #topic Usability of host switcher 16:13:00 https://github.com/cockpit-project/cockpit/pull/1467 16:13:04 so i find myself fighting with the host switcher a lot 16:13:13 in what way? 16:13:22 * it provides no useful value being displayed by default when only viewing one server 16:13:23 the sidebar or the dashboard? 16:13:27 on the sidebar 16:13:34 it causes the page layout to break 16:13:37 so i turn it off 16:13:47 yeah, the page breaks are annoying 16:13:49 but then it shows up again, and my preference is not saved 16:14:01 in addition, the only way to the dashboard which *is* useful with one server 16:14:13 is via the host switcher which totally not useful when i only have one server 16:14:42 i wonder if we can have the dashboard be accessible without the host switcher 16:14:52 i keep clicking the hamburger and expect to go to the dashboard 16:14:54 and have the hostswitcher be an overlay drop down that's not displayed by default 16:14:57 mvollmer, yes me too 16:15:27 like a bubble? 16:15:30 yeah, could work 16:15:33 "popover" 16:15:43 that's the technical term, no? 16:15:50 or at the very least keep the sidebar as a sidebar, but: 16:15:50 * not make it display by default 16:15:51 * make it remember whether you like it or not 16:15:58 * allow access to dashboard that isn't via the host switcher 16:16:12 I wonder if we can have different experience for when having just one server and when having +1 16:16:17 stefw, how does it come back for you? 16:16:42 andreasn, i the key when going from 1 to N servers, is is that the sidebar should remember whether you wanted it to be displayed or not 16:16:54 mvollmer, when i log into cockpit again, the sidebar is back 16:17:00 right 16:17:06 it's also back because i used it to get to the dashboard, even though i didn't want to bring it back :D 16:17:09 yeah 16:17:35 per-user config should be easy now 16:17:43 why not just localStorage()? 16:17:45 ot a cookie? 16:17:52 right 16:17:55 cookies mean more data in the server round trip 16:17:59 i think we can rely on localStorage 16:18:04 yes, localStorage 16:18:17 also for language choice 16:18:27 well that's implemented on the server 16:18:31 so a cookie makes sense there 16:18:37 and it does things like invalidate browser cache 16:18:45 so we have to have Cookie: be set for language choice 16:18:56 and then set a Vary: header so the browser cache does the right thing when switching between languages 16:18:58 hmm, right. 16:19:33 unfortunately that means that language files are not cached between login sessions, since a new login also changes the Cookie: 16:19:39 but such is life 16:19:43 anyway, back to the host switcher 16:19:51 1. remembering the preference is one aspect 16:19:57 2. access to dashboard without showing it 16:20:06 either we need to do those things ^^ 16:20:11 or make the host switcher a popover 16:20:38 although i will note that getting to the dashboard via a popover each time may become irritating 16:21:15 yeah, it's a bit of pro's and cons 16:21:45 but well, it's like one more click 16:22:01 in which case? 16:22:12 right now, it's one more click, that shows the host switcher, and keeps it shown 16:22:29 I mean that you can't have it expanded 16:22:29 so it's one click that explicitly goes against what the user is trying to do 16:24:05 the case that some pages gets odd layouts is a separate bug 16:24:17 andreasn, yes, and one that i probalby just need to do some patches for 16:24:31 but at the core of the issue is that the host switcher is wasted space and not useful for the 1 server case 16:24:39 yes, certainly 16:24:49 the dashboard is useful in the 1 server case 16:24:57 in a way, it might be a bit expensive also for 2-3 servers 16:25:01 right 16:25:12 it's perfect when it's about 10 servers 16:25:56 so how do we decide what to do next here? 16:26:09 should we come up with proposals, and brainstorm in a github issue? 16:26:11 i can file one 16:26:16 yes, that would be great 16:26:19 ok 16:26:44 thanks for bringing these up 16:27:33 so, while we're on the subject of hosts, should we talk about the one that is about to merge? 16:27:39 or is that a separate topic maybe? 16:27:50 i would like to add that to the agenda at some point 16:28:05 * UI reviews and making sure we get it right before merging 16:28:31 like perhaps we need a checklist or something? 16:28:38 but we could talk about that separately 16:28:47 sure 16:29:15 #topic Trello for roadmap 16:30:20 we have this trello board 16:30:20 https://trello.com/b/mtBhMA1l/cockpit 16:30:34 can we use it instead of our Roadmap wiki page, and link to it from there? 16:30:39 sure 16:30:42 is there anything that would help Trello be more useful? 16:30:51 it would be find to change it around until it is useful to us 16:31:06 I just need to remember to pay more attention to it 16:31:19 and change status where appropiate 16:31:41 but it's unnesesary to keep a duplicate of the roadmap 16:31:50 as they go out of sync and all 16:31:53 yeah 16:32:21 anything else on that? 16:32:27 ok, i guess i'll try and pull anything else over 16:32:34 put the distant stuff on the roadmap into Backlog 16:32:34 ok, sounds good. 16:32:42 deal 16:32:44 i tihnk i've moved over most of the other stuff 16:33:27 #topic Report on channel metrics 16:33:46 not that much to report 16:33:56 i've been working on the components all week, trying to get that in shape 16:34:07 but i'll start working on a channel for resource metrics again tomorrow 16:34:09 this is for the graphs 16:34:19 i have some basic code that works with PCP and i started implementing them 16:34:24 but i don't have it to a state where it compiles yet 16:34:24 cool 16:35:19 that's it for that 16:35:24 great 16:35:39 #topic Report on components 16:35:50 the journal is now in a component 16:35:54 ooh 16:36:04 so it's ready for a new contributor to implement the new journal look 16:36:13 if we some of the design issues worked out 16:36:26 https://trello.com/c/if88ORZv 16:36:35 there are the beginnings of a docker component 16:36:43 implementing the console stuff (ie: container terminal and/or logs) 16:36:58 and i've done some work on the networking 16:37:01 migrating the dbus code 16:37:02 https://trello.com/c/1d4RRSUp 16:37:12 there's a checklist at that link on what needs to be done to turn the networking page into a component 16:37:27 I'll take a look at the Journal design again, but if I recall correctly it looked quite good 16:37:37 yes indeed, it's nice work 16:37:52 i noted some issues in the github issue: https://github.com/cockpit-project/cockpit/issues/1378 16:39:08 good 16:40:39 (switched devices) 16:41:57 what was next on the agenda? 16:42:37 fsys channels, I think. 16:42:41 Status of FS channels 16:43:28 #topic Status of FS channels 16:43:47 ok, super review by stef, now ready for second round of review. 16:44:22 i am pondering whether to implement a JS wrapper first before merging. 16:44:52 mvollmer, should we prototype a JS wrapper in the dashboard code first? 16:45:02 yes, we could. 16:45:12 there is no hurry to merge fsread et al 16:45:32 so let's first make another pull request for at least one client. 16:45:40 sounds good 16:45:42 yes ... i did have a situation in mind where we could hurry it along 16:45:52 for some folks who wanted to embed cockpit 16:45:55 but today they seemed less interested 16:45:56 so no rush 16:46:01 right, i see 16:46:44 we could also make the docker page use it in favor of polling. 16:47:03 indeed 16:47:19 i could try to fit that in 16:47:21 that would probably not need a wrapper 16:47:33 i was working on docker stuff today, and man seeing the polling was really painful :S 16:47:44 the wrapper I have in mind would abstract a JSON file and use all three channel payloads in concert 16:48:00 docker doesn't need that 16:48:14 but the dashboard 16:48:35 mvollmer, i want to brain storm the actual storage format of the machines a bit 16:48:43 yes 16:48:46 and prep it for making it more of a public api 16:49:01 it was something that lpol suggested 16:49:14 not sure if we're completely ready for this, but worth brainstorming a bit to see 16:49:21 so that other tools can easily add machines to a dashboard? 16:49:28 yeah 16:49:31 right 16:49:32 whether via cockpit-bridge --add 16:49:38 or just placing files 16:49:42 which look a lot like Desktop files 16:49:43 somewhere 16:49:47 i see 16:49:55 sorta like how you can add stuff to your gnome-shell applications display 16:49:59 by putting Desktop files in the right place 16:50:03 there's an analog here to our dashboard 16:50:10 and that was hinted at by lpol 16:50:10 yes 16:50:19 good observaton 16:50:24 also ... 16:50:43 i would like to lock down cockpit-ws so it'll only load resources from hosts that are explicitly added 16:50:49 to close down any reflection security vulnerabilities 16:51:04 ok 16:51:09 and so if that's the case, then people who are embedding may want to be able to trivially add/remove hosts on the fly in order to access a broader set of servers in a configuration management context. 16:51:15 like i said this latter thing isn't a priority to me 16:51:30 but worth considering while we're working on this 16:52:36 right 16:52:41 anyway, we can brainstorm this later 16:52:48 yes 16:53:28 (reminds me that we need to test directory watching) 16:54:12 yes, for the docker no-poll case too 16:56:17 ok,done? 16:56:44 i think so yes 16:57:22 #topic multi dash sryli 16:57:27 err 16:57:56 #undi 16:58:02 #undo 16:58:02 Removing item from minutes: 16:58:23 #topic multi dash styling 16:59:04 the hovering and button centering? 16:59:07 I fixed the issues stef mentioned 16:59:18 so should be in good shape 16:59:27 i did another round of review 16:59:31 i think we're nearly there 16:59:36 cool 17:01:36 anything else? 17:01:48 i think that's it 17:01:53 great 17:02:12 roadmap update? 17:02:17 sure 17:02:24 or is it now always up-to-date in trello? 17:02:30 #topic roadmap 17:02:33 we should still do it 17:02:47 i can make any changes pointed out 17:04:02 I hve pointed "Multi-server dashboard makeover" to #1467 17:04:27 andreasn, how' are the patternfly and website updates coming? 17:04:46 they are still "backlog", right? 17:04:47 added link to 'Storage Redesign' 17:04:53 still behind on those, yeah 17:05:40 but issues are filed for the website 17:05:54 yep 17:06:13 hope to get to them this week 17:06:28 ok, I just moved them to "next four month". :-) 17:06:39 oh 17:06:39 doesn't make sense, don't know why I did that, actually... 17:06:57 i've put everything from 'Later' into trello 17:08:05 migrated ' 4 months' 17:08:50 put a trello link 17:09:21 ok 17:09:54 so are we going to use only trello from now on? 17:10:10 or part wiki page, part trello? 17:10:22 k, i think everything is migrated 17:10:25 i think only Trello 17:10:31 all right 17:10:32 or did i misunderstand what we talked about above? 17:10:41 but we can change Trello around if it's not useful to us 17:10:46 yeah 17:12:09 i think the roadmap is more for others than for us 17:12:33 does trello have time estimates? 17:12:36 but trello is more than the roadmap so that's cool. 17:13:53 andreasn, yes, they can have due dates 17:13:54 or flags 17:13:57 labels 17:14:05 good 17:14:15 but in general 'Backlog' is the stuff that's far out 17:14:19 and the rest is in some stage of work 17:14:30 whether research, design, coding, etc... 17:15:42 all right 17:17:18 anything else? 17:18:40 sounds like that's it 17:18:49 great 17:18:53 thanks! 17:18:59 yep 17:19:01 #endmeeting