[07:04] <rvba> Thanks for the reviews gmb.
[07:04] <gmb> np
[07:27] <bigjools> jtv: ha, just had this discussion with gmb.  He sent mockups to the devel list
[07:27] <bigjools> a while ago
[07:30] <bigjools> rvba: FYI I just said to gmb not to bother with pushing keyring blobs through
[07:30]  * gmb was about to type exactly the same thing…
[07:31] <rvba> bigjools: Do you mean getting rid of BootSource.keyring_data?
[07:32] <bigjools> don't get rid of it, we just don't need it yet, a file will suffice
[07:32] <bigjools> file name
[07:32] <bigjools> because the keyring is already installed for all known sources as of this point in time
[07:33] <rvba> Well, I already did the work in the API to support it.
[07:33] <bigjools> how much is left to finish this then? I thought it wasn't near completion
[07:34] <rvba> All the API for BootSource is done.  I need to add support for BootSourceSelection and we're done.
[07:35] <jtv_> Leaving UI.
[07:35] <rvba> Yeah, I'm only talking about the API.
[07:36] <jtv_> Didn't mean to derail you there.
[07:37] <rvba> Don't worry, you didn't :).
[07:37] <jtv_> :)
[07:37] <bigjools> [17:27:16] <bigjools> jtv: ha, just had this discussion with gmb.  He sent mockups to the devel list
[07:38] <bigjools> jtv_: ^
[07:38] <bigjools> bloody netsplits
[07:38] <jtv_> Yeah.  That was my other nick.  I'll check email.
[07:38] <bigjools> jtv_: they were sent a while ago
[07:38] <bigjools> "Getting rid of bootresources.yaml (sort of)"
[07:39] <bigjools> rvba, gmb: sorry, so how much work is left to push these keyring blobs through? gmb made it sound like a lot of work
[07:39] <gmb> bigjools: My bad… there’s not a massive amount of work, it’s just tedioous.
[07:40] <bigjools> and how do you plan on getting the keyring blobs *into* the DB?
[07:40] <gmb> Maybe a day’s worth.
[07:40] <gmb> The only complex part is deciding where to write the keyring data out.
[07:40] <gmb> s/complex/thinko-ridden
[07:40] <gmb> bigjools: File upload, read the file, stick the contents in the DB
[07:41] <bigjools> gmb: in the web UI?
[07:41] <bigjools> what about the default config?
[07:41] <bigjools> this is one of the reasons I was sceptical when I saw you were doing this :)
[07:41] <gmb> bigjools: Default config will use the default cloud image keyring
[07:42] <bigjools> gmb: and is that going to be installed on each appserver?
[07:42] <gmb> Hmm, good point.
[07:42] <bigjools> check the package dependencies
[07:43] <bigjools> but I would seriously consider just using what's on the cluster machine for now
[07:43]  * bigjools heads for dinner, back later
[07:44] <gmb> k
[09:24] <jtv_> What does the "remove default config file value for MIPF" mean exactly?
[09:26] <rvba> jtv_: just changing the import script so that it doesn't use /etc/maas/bootresources.yaml by default.
[09:27] <jtv_> Thanks.  I'll annotate the card.
[09:28] <jtv_> Or, unless anybody minds, change it to "Wean import script off bootresources.yaml."
[09:46]  * gmb -> location switch
[10:48] <gmb> allenap: So, to clarify: we’re going to 1) Add a dependency for maas-region-controller->ubuntu-cloud-image-keyring ; 2) Read the cloud-image-keyring into the DB as part of ensure_boot_source on the cluster 3) Proceed as specified with blobbity stuff.
[10:52] <gmb> allenap: I was a bit distracted at the end of the call; so could use confirmation from someone else’s brain :)
[10:52] <gmb> rvba, jtv: Your memories will also be more accurate than mine on this score ^^ :)
[11:00] <jtv_> I don't think we can do that as part of ensure_boot_source_definition.
[11:00] <jtv_> Didn't we say we'd just let the cluster register the installed keyring as a blob?
[11:01] <jtv_> We can of course install a _region-side_ keyring in ensure_boot_source_definition.
[11:02] <jtv_> As the default value, that is.
[11:02] <jtv_> Re-reading in that light, I think the only thing I'm objecting to is where you say "on the cluster."
[11:14] <gmb> jtv_: Sorry, I wasn’t clear: “on the cluster” meant “on the cluster model when the cluster is created"
[11:14] <gmb> So the region is the canonical source for the keyring(s).
[11:18] <jtv_> Right ho then.
[11:19] <jtv_> It won't actually be on the cluster model, of course, but rather on the BootSource one.
[11:33] <gmb> jtv_: Right. Complete confusion on my part.
[11:34]  * gmb likes the throw-it-at-the-wall model of conversation
[11:42]  * jtv_ learned the hard way about anchoring shared understanding
[11:50] <gmb> Yeah.
[12:19] <allenap> gmb: Yes, except for the bit about loading the keyring into the database. When a keyring is identified by a filename it should be, imo, loaded from that file.
[12:20] <allenap> Every time, not cached in the database.
[15:00] <AskUbuntu> Setting up MAAS on 14.04LTS Region + Cluster on same server DHCP not working | http://askubuntu.com/q/469649
[15:52] <rvba> gmb: if you feel like reviewing the rest of the API work, I just put it up for review.
[15:52] <gmb> rvba: I just saw :). I’ll take a look in a mo. Just unknotting something.
[15:52] <rvba> Cool.
[16:23] <gmb> allenap: I have a question about mocking for you.
[16:24] <gmb> allenap: By which I mean “using the mock” module, not “belittling people”
[17:57] <l1l> Ok folks, I am having a problem with maas-dns. The reverse dns isn't working and I am seeing a error in the celery-region.log
[18:02] <l1l> rndc_command: Command `rndc -c /etc/bind/maas/rndc.conf.maas reload 16.172.in-addr.arpa` returned non-zero exit status 1:
[18:02] <l1l> None
[19:06] <AskUbuntu> Juju bootstraping gomaasapi timestamp error | http://askubuntu.com/q/469778
[20:20] <AskUbuntu> JUJU MAAS Bootstrap all on VM | http://askubuntu.com/q/469810
[22:22] <AskUbuntu> Can't Deploy Wordpress | http://askubuntu.com/q/469848
[22:59] <phillw> Hi good people, I'm following http://maas.ubuntu.com/docs1.5/install.html#pkg-install and it seems very badly broken (the ppa doesn't work, the mass-dhcp and mass-dns do not exist. Is there a working set of instructions for installing cloud onto a trusty server?
[23:15] <mwhudson> hm
[23:15] <mwhudson> i definitely managed to install maas on trusty recently :-)
[23:17] <phillw> mwhudson: well, any hints / tips or a set of working instructions would be gratefully received :)
[23:18] <mwhudson> i'm trying to remember
[23:18] <mwhudson> phillw: what do you mean maas-dns doesn't exist?
[23:18] <mwhudson> it looks installable to me
[23:19] <mwhudson> i'm not sure you need the ppa if you're running trusty but don't take my world for that
[23:20] <mwhudson> well certainly you don't need the ppa to install it
[23:23] <gaughen> mwhudson, phillw I am running trusty and have maas on my system.. maas-dhcp and maas-dns too (v1.5)
[23:23] <phillw> the system reported back that I do not need the ppa, but it also could not find maas-dhcp or maas-dns
[23:23] <gaughen> and yes, no ppa required
[23:23] <mwhudson> phillw: can you pastebin the error message?
[23:25] <phillw> it seems to have woken up!!!! 209 apps to install :)
[23:25] <mwhudson> heh
[23:26] <mwhudson> it's the usual thing, complain about something in public and it instantly fixes itself
[23:26] <phillw> it is a very new VM, maybe it had not fully linked to the world :)
[23:26] <phillw> and, it's not a typ, as I scrolled back through my commands to re-issue :)
[23:28] <gaughen> phillw, I suspect it may not have been linked to the world because I just created a new vm with trusty and did an apt-get on those three packages and it's going fine
[23:29] <gaughen> like mwhudson said complain in public and it fixes itself ;-)
[23:30] <phillw> indeed... well it may be because I told the student eagerly awaiting it that I was going to bed and would have another attempt later today (I'm UK time)