=== 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/ [15:56] * marcoceppi struts up and down the hallway [15:56] I see a white space, instead of the normal "starting soon" message. [15:56] Is the URL correct? [15:56] rbasak: the URL is being fixed [15:57] Thanks :) [15:58] I had to reload, but I'm good now. [16:01] The stream is good. [16:01] \o/ [16:13] feel free to ask questions [16:18] I 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] Also, I'd love to see the "juju help" stuff available online somewhere, as typing commands by hand to see it is tedious [16:18] rbasak: slow to load initially, or slow to load after first load (ie the navigation, etc) [16:18] marcoceppi: every page load is slow. [16:19] rbasak: juju help as HTML would probably be good as well, I'll file a bug for that [16:19] I usually need to jump around several pages, but am following links, so don't immediately know where I'm going. [16:19] That makes it hard to keep tabs open to work around that. [16:19] IMHO, things need to be tuned so that my browser's cache will work. [16:20] rbasak: I know there's a lot of javascript that manipulates that page, which might be the slow down [16:20] That would make repeated viewing lightning fast, and IMHO it's repeated viewing that matters for new charmers. [16:20] marcoceppi: I'm pretty sure it's the server response time. I'm not sure though. [16:21] cf. python docs for example, where everything is cached, so repeated viewing is fast. [16:34] Not a bad thought rbasak, thanks for the input === 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/ [18:05] https://plus.google.com/hangouts/_/hoaevent/AP36tYcmtPjdBaJyRVZ9A6AdW8lzfQvVZ9tylv8p1hdSOyGfN-SMGw?authuser=0&hl=en [18:05] just about to start [18:05] o/ hi. [18:06] o/ [18:06] http://pad.ubuntu.com/uds-1403-maas-hwe [18:13] hey, how much code would be needed to create a "driver" that you are talking about? [18:18] http://paste.ubuntu.com/7086140/ [18:18] o/ [18:18] zyga-uds, i'll try to answer [18:18] or ask your question [18:18] IMHO, these are the same problem. [18:19] The problem is mapping what we know of the hardware to a set of kernels that can boot it. [18:19] HWE kernels are different from flavor kernels to us, but they are both related to exactly the same problem. [18:20] I think it's fine to abstract this so that we just announce what hardware a particular kernel supports. [18:21] smoser: +1 [18:33] I'm looking at non-server hadware, think laptops that we know of statically [18:33] and that we can turn on and off [18:34] and that boot remotely [18:34] but have no standard management at all [18:34] ok [18:34] it looks doable then [18:35] thabjs [18:36] thanks :) === 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