/srv/irclogs.ubuntu.com/2014/03/13/#ubuntu-uds-hallway.txt

=== ChanServ changed the topic of #ubuntu-uds-hallway to: Currently no events are active in this room - http://summit.ubuntu.com/uds-1403/hallway/ - http://irclogs.ubuntu.com/2014/03/13/%23ubuntu-uds-hallway.html
=== ChanServ changed the topic of #ubuntu-uds-hallway to: Track: Cloud & Server | State of the Juju Ecosystem | Url: http://summit.ubuntu.com/uds-1403/meeting/22209/state-of-the-juju-ecosystem/
* marcoceppi struts up and down the hallway15:56
rbasakI see a white space, instead of the normal "starting soon" message.15:56
rbasakIs the URL correct?15:56
marcoceppirbasak: the URL is being fixed15:56
rbasakThanks :)15:57
rbasakI had to reload, but I'm good now.15:58
rbasakThe stream is good.16:01
marcoceppi\o/16:01
marcoceppifeel free to ask questions16:13
rbasakI have some comments on docs, if that's relevant. I find juju.ubuntu.com/docs too slow - and my browser doesn't cache it, either.16:18
rbasakAlso, I'd love to see the "juju help" stuff available online somewhere, as typing commands by hand to see it is tedious16:18
marcoceppirbasak: slow to load initially, or slow to load after first load (ie the navigation, etc)16:18
rbasakmarcoceppi: every page load is slow.16:18
marcoceppirbasak: juju help as HTML would probably be good as well, I'll file a bug for that16:19
rbasakI usually need to jump around several pages, but am following links, so don't immediately know where I'm going.16:19
rbasakThat makes it hard to keep tabs open to work around that.16:19
rbasakIMHO, things need to be tuned so that my browser's cache will work.16:19
marcoceppirbasak: I know there's a lot of javascript that manipulates that page, which might be the slow down16:20
rbasakThat would make repeated viewing lightning fast, and IMHO it's repeated viewing that matters for new charmers.16:20
rbasakmarcoceppi: I'm pretty sure it's the server response time. I'm not sure though.16:20
rbasakcf. python docs for example, where everything is cached, so repeated viewing is fast.16:21
lazyPowerNot a bad thought rbasak, thanks for the input16:34
=== ChanServ changed the topic of #ubuntu-uds-hallway to: Currently no events are active in this room - http://summit.ubuntu.com/uds-1403/hallway/ - http://irclogs.ubuntu.com/2014/03/13/%23ubuntu-uds-hallway.html
=== ChanServ changed the topic of #ubuntu-uds-hallway to: Track: Cloud & Server | MAAS HWE | Url: http://summit.ubuntu.com/uds-1403/meeting/22153/maas-hwe/
gaughenhttps://plus.google.com/hangouts/_/hoaevent/AP36tYcmtPjdBaJyRVZ9A6AdW8lzfQvVZ9tylv8p1hdSOyGfN-SMGw?authuser=0&hl=en18:05
gaughenjust about to start18:05
beisner-udso/   hi.18:05
smosero/18:06
smoserhttp://pad.ubuntu.com/uds-1403-maas-hwe18:06
zyga-udshey, how much code would be needed to create a "driver" that you are talking about?18:13
smoserhttp://paste.ubuntu.com/7086140/18:18
rbasako/18:18
smoserzyga-uds, i'll try to answer18:18
smoseror ask your question18:18
rbasakIMHO, these are the same problem.18:18
rbasakThe problem is mapping what we know of the hardware to a set of kernels that can boot it.18:19
rbasakHWE kernels are different from flavor kernels to us, but they are both related to exactly the same problem.18:19
rbasakI think it's fine to abstract this so that we just announce what hardware a particular kernel supports.18:20
rbasaksmoser: +118:21
zyga-udsI'm looking at non-server hadware, think laptops that we know of statically18:33
zyga-udsand that we can turn on and off18:33
zyga-udsand that boot remotely18:34
zyga-udsbut have no standard management at all18:34
zyga-udsok18:34
zyga-udsit looks doable then18:34
zyga-udsthabjs18:35
zyga-udsthanks :)18:36
=== ChanServ changed the topic of #ubuntu-uds-hallway to: Currently no events are active in this room - http://summit.ubuntu.com/uds-1403/hallway/ - http://irclogs.ubuntu.com/2014/03/13/%23ubuntu-uds-hallway.html

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!