15:02:53 #startmeeting Cockpit public meeting 2014-10-20 15:02:53 Meeting started Mon Oct 20 15:02:53 2014 UTC. The chair is andreasn___. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:53 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:03:04 .hellomyname is mvo 15:03:07 #meetingname Cockpit 15:03:07 The meeting name has been set to 'cockpit' 15:03:11 #chair puiterwijk andreasn mvollmer stefw sgallagh 15:03:11 Current chairs: andreasn andreasn___ mvollmer puiterwijk sgallagh stefw 15:03:18 * mvollmer is too grammatical 15:03:22 .hellomynameis mvo 15:03:23 mvollmer: mvo 'Marius Vollmer' 15:03:24 .hellomynameis andreasn 15:03:26 andreasn___: andreasn 'Andreas Nilsson' 15:03:33 #topic Welcome 15:03:55 andreasn, let's have a quick round on agenda. 15:03:57 #chair puiterwijk andreasn mvollmer stefw sgallagh jscotka 15:04:07 thanks, sorry jscotka 15:04:09 :-) 15:04:32 ok, lets start with the agenda we already started with :) 15:04:35 #topic agenda 15:04:40 * next steps 15:04:45 * url schema 15:04:48 * general status 15:04:53 * roadmap 15:04:59 * freeipa terminal 15:05:04 ok, lets start 15:05:11 general status first 15:05:18 #topic general status 15:05:47 so, the new navigation is moving forward well 15:05:48 so "New Navigation" is almost there, some polish, some testing, looks good. 15:06:16 some code cleanups have happened, but hopefully more with the upcoming URL scheme rethinkg 15:06:34 #info new navigation layout, issue #1369 is almost there, some polish and testing remaining before merge 15:06:37 stefw? 15:07:29 is he even here? he's on PTO today I think 15:07:41 ohh. 15:07:54 ok, I try. 15:08:15 is there anything for testing, should it be tested from usability side? 15:08:35 I think he is busy now with the AMD, the asynchronous module loader. 15:08:54 and dbus3. 15:09:19 packages work well so far, maybe some more bugs to shake out. 15:09:20 jscotka: yes, the pull request for the new navigation is in #1369. It should be fairly straight forward, but extra eyes is always good 15:09:39 jscotka, what's your status? 15:09:47 I'll look at it 15:10:04 thanks! 15:10:54 I've tested 0.27 version with patches about compilation and another base directories, and it seems very well. 15:11:33 It seems to be closer to be distro-independent. 15:11:51 ok, sounds good. 15:11:57 cool, anything more for navigation? it needs review from stefw, right? 15:12:06 yes 15:12:25 #info navigation branch needs code review from stefw 15:12:30 As I saw some discusson last week. It seems that more users expected that it will work everywhere. I think that also raspberry was mentioned 15:12:36 #action stefw to review 15:12:51 andreasn, he knows. :-) 15:13:02 mvollmer: yes, mostly for completeness :) 15:13:10 :-) 15:13:42 topic url schema next? 15:13:56 yeah, will be short. :-) 15:14:03 #topic url schema 15:14:24 jscotka: lets take the raspberry point as part of open floor 15:14:32 we want to rethink our UI URLs one more time 15:14:47 #info we need to rework the ui url scheme again 15:14:58 is there a open issue about it? 15:15:03 so that they fit the new navigation better and are maybe nicer to read also. 15:15:16 andreasn, not sure. 15:15:32 #info for easier readability and to fit better with the reworked navigation 15:15:54 no issue for it. 15:16:44 they will look somethink like https://f21.cockpit.lan:9090/#/blue/server/vg/test 15:16:52 sorry. 15:16:57 they will look somethink like https://f21.cockpit.lan:9090/#/blue/storage/vg/test 15:17:05 blue is the host name. 15:17:40 needs discussion with stef 15:17:46 all right 15:17:58 #info needs further discussion 15:18:03 anything else? 15:18:33 at the same time, we will rethink how pages are handled in JavaScript, so that this all works beautifully with packages loaded into iframes. 15:19:31 I think our next goal could be that the navigation bar is filled dynamically based on package manifests loaded from each host. 15:20:00 right 15:20:00 #info needs rethinking how we handle pages in javascript as well, so it all works well together 15:20:21 I'll work on that and discuss with stef 15:21:01 ok, next? 15:21:02 cool 15:21:04 yep 15:21:19 #topic roadmap 15:21:38 freeipa terminal? 15:22:36 how do I undo the topic 15:22:38 #undo 15:22:39 Removing item from minutes: 15:22:48 ok, lets do the terminal 15:22:56 #topic freeipa terminal 15:23:05 that's our first customer for the embeddble terminal. 15:23:32 stef has approached them, now might be the time to have them test it with 0.28. 15:24:03 #info stef have been talking to freeipa about using our terminal via embedding 15:24:24 #info cockpit's code is ready with the 0.28 release 15:25:35 right, now roadmap? 15:25:42 we are fast today... 15:25:47 yep 15:25:51 #topic roadmap 15:26:08 #info https://github.com/cockpit-project/cockpit/wiki/Roadmap 15:26:11 we could expand on Navigation redesign abit. 15:26:32 how do you mean? 15:26:47 Add the things that are missing. 15:26:56 isn't really necessary... 15:27:07 yes, the sidebar with the other machines is a missing piece 15:27:11 and already covered by "modular architecture" anyway, I guess. 15:27:13 instead of a separate page 15:27:17 right, that one. 15:27:27 I'll add that to the roadmap 15:27:54 ok. 15:28:04 Is there planned to use same graphics for some mobile devices or some similar smalled displays? 15:28:22 #aciton andreasn to add navigation subitems to the roadmap 15:28:40 #action andreasn to add navigation subitems to the roadmap 15:28:58 has anything changed about the roadmap? I guess not. 15:29:05 jscotka: you should be able to use it on a tablet or cell phone todauy 15:29:07 today 15:29:20 the navigation should be able to reflow well 15:29:38 but I'll make sure to test that a bit extra to make sure we didn't miss anything 15:29:58 andreasn, should we try to tackle the patternfly update soon? 15:30:02 my vm-bridge is acting a bit weird right now, but I'll get it working again after the meeting 15:30:12 mvollmer: yes, I wonder if that's next maybe 15:30:21 andreasn, Sounds good, I have to test it. It is question focused on redesign to be still able navigate somewhere when I have small display 15:30:23 so should be moved to next four weeks 15:30:50 jscotka: yes you should, having it work on a tablet is a quite important case 15:31:03 if nothing else, for demos :) 15:31:10 :-) 15:31:22 #action andreasn to add patternfly update to the 4 week section 15:32:02 is anything under "4 weeks" done already? 15:32:32 nope 15:32:57 all right 15:33:05 anything else for roadmap? 15:33:33 I would like to get started on mockups for the atomic features soon too 15:33:49 andreasn, did someone ask you for them? 15:34:11 stefw said it might be good to start on them sometime last week 15:34:21 andreasn, right. 15:34:29 most of it is to improve our container story in general 15:34:42 esp on the storage side 15:34:56 #action andreasn to start with mockups for the atomic/docker features 15:34:58 true 15:35:09 all right, that's all I had for roadmap 15:35:28 open floor next? 15:35:43 alright! 15:35:43 #topic open floor 15:36:25 jscotka: you mentioned Cockpit on Raspberries, could you expand on that? 15:37:42 andreasn, I saw discussion there on #cockpit channel, that some user I think with nick like: ilovelinux mentioned that he would like to use/install cocpit there 15:37:50 ah, I see 15:38:10 there is a bunch of different images for rpi, like the debian one, and the fedora based one 15:38:33 the fedora based one is not too far away from a regular fedora, something we run on already 15:38:43 but I think it might be missing some dependecies 15:38:55 not sure if there is a udisks in those repositories 15:39:00 etc 15:39:13 yep, there is imporatnt make cockpit the more universal the more possible 15:40:22 ideally in early phase of cockpit. Lots of users is searching for some universal administration tools over more linux distros. (Have more various servers) 15:41:20 apart from udisks, the pidora images does have systemd and stuff, so that's good 15:41:37 but it would need someone to do the job of building and packaging 15:42:45 andreasn, Would it be possible to do it for example via some modules, like, I have systemX with this app for communication with disk, I will be able to write some wrapper, or something like that which allows cockpit to communicate with system via defined interface. It is only idea, not plan :-) 15:43:30 that is above my level of knowledge, that's a question for a programmer :) 15:43:40 jscotka, yes, the idea is that Cockpit has specific UI+code for specific management interfaces. 15:44:18 so if the system has journald, Cockpit will load the "journald" module for it. 15:44:28 if it has something else, it will load another module. 15:44:48 that's the idea, reality will follow soonish. 15:44:51 mvollmer, like network management via NetworkManager or via for example OpenLMI? 15:45:40 this module loading sounds very good 15:47:10 jscotka, yes, exactly. 15:47:51 cool, anything else for the open floor? 15:48:03 another dimension is that people can contribute these modules via independent rpms/debs. 15:49:52 mvollmer, It will be nice. I still hope that OpneLMI devels wrote their modules, for cockpit and then cocpit will be able to communicate via LMI specification. 15:49:52 andreasn, doesn't look like it. 15:50:19 all right, thank you everyone for attending this weeks meeting 15:50:23 #endmeeting