[05:52] <bigjools> mwhudson: did you get anywhere with the split downloads yet?
[05:52] <mwhudson> bigjools: no
[05:52] <bigjools> mwhudson: fair enough :)
[05:53] <mwhudson> bigjools: i seem to have about three jobs all of a sudden!
[05:53] <bigjools> \o/
[05:55] <mwhudson> bigjools: did you get anywhere with your ... stuff?
[05:56] <bigjools> mwhudson: if you're talking about the sekrit stuff, waiting on a third party
[05:57] <mwhudson> ok
[05:57] <mwhudson> (i was)
[14:49] <roaksoax> rvba: still around?
[14:51] <rvba> roaksoax: yes, but otp
[14:54] <roaksoax> rvba: ok let me know when done :)
[15:25] <rvba> roaksoax: what's up?
[15:26] <roaksoax> rvba: so I was wondering when are we going to have the autod-distro detection/;selection mechanisms
[15:26] <roaksoax> or whatever is it that you guys are planning to have there?
[15:27] <rvba> roaksoax: you mean using distro-info's output instead of hardcoding the name of the releases?
[15:27] <roaksoax> yeah
[15:28] <roaksoax> rvba: I guess a better question would be what are the plans around it exactly? I think it would make sense to either do 1 of two things 1. maas-import-pxe-files determines which releases are available in MAAS itself, by enabling those for which we have images of. or 2. select the images that we will import in MAAS and make them available for maas-import-pxe-files to import
[15:29] <rvba> roaksoax: it's definitely in a blueprint… but I confess we haven't thought about it much…
[15:30] <roaksoax> rvba: i think it is something that we really need to care about soonish
[15:30] <roaksoax> and try to SRU it
[16:02] <ehw> hey, guys, anyone know how to set the "public ssh key" in juju-core? -ENODOCS
[16:03] <ehw> getting this: error: error parsing environment "maas": no public ssh keys found
[16:21] <AskUbuntu> Node is still in commissioning state! | http://askubuntu.com/q/306911