[09:07] <jtv> It will now be possible for a single MAC to allocate an IPv4 and an IPv6 address of different types.
[09:08] <jtv> bigjools, do you see any problem with ^ ?  I think we need to support it, because it seems reasonable to allocate e.g. a specific sticky IPv6 address to a node, and then have it claim a static IPv4 address "off the shelf."
[09:09] <bigjools> jtv: seems cromulent to me
[09:09] <jtv> Right ho.  Won't be anywhere near as nice a check, of course.
[09:10] <bigjools> jtv: self.assertCromulent() - I need do add this immediately.
[09:10] <bigjools> to*
[09:10] <jtv> I once got official permission to add -ffascist and -Wanal to gcc.
[09:10] <jtv> And I stress, official.
[09:10] <bigjools> O_o
[09:10] <jtv> Yet somehow it never happened.
[09:11] <jtv> I think it was Ray Dassen's routine way of summarising my usual raft of compiler options.
[09:13] <bigjools> allenap: does getClient() now just wait automatically?  I can't remember.
[09:29] <allenap> bigjools: In the region, yes. In the cluster, not yet.
[09:29] <bigjools> allenap: ah ok so I'll need to add my retry code
[09:29] <allenap> bigjools: (It’s getClientFor in the region.)
[09:29] <bigjools> I'll let you refactor it later ;)
[09:30] <allenap> bigjools: It’s on my in-memory stack to fix.
[09:30] <bigjools> eek
[09:30] <allenap> I’ll put it in cards.
[09:30] <allenap> Right now I have to be elsewhere :-/
[14:10] <jtv> Oops, my static-IP-allocation branch grew to just under 800 lines.  Anyone brave enough to review it?
[14:10] <jtv> https://code.launchpad.net/~jtv/maas/allocate-ips-on-multiple-cluster-interfaces/+merge/231368
[14:53] <blake_r> allenap: can I get a review of both https://code.launchpad.net/~blake-rouse/maas/bootresource-store/+merge/231260 and https://code.launchpad.net/~blake-rouse/maas/region-image-downloader/+merge/231383
[14:54] <blake_r> allenap: uses twisted and the thread database locking so would like you to take a look
[14:54] <allenap> blake_r: Sure. I’m in the middle of something right now, but I’ll look at it straight afterwards.
[14:54] <blake_r> allenap: no rush, thanks
[14:54] <blake_r> jtv: i will take it
[14:55] <blake_r> jtv: jk, looks liek gmb already has it
[14:55] <gmb> Yes, yes.
[14:55]  * gmb is a masochist
[14:56] <blake_r> haha
[15:08]  * gmb -> switching locations
[19:52] <aslaen> hello, is there a way to rename an active node?
[19:53] <jhobbs> aslaen: why are you trying to rename an active node?
[19:53] <jhobbs> aslaen: you can in the very latest maas code, but not in the released maas
[19:53] <jhobbs> aslaen: but i'm curious what your use case is
[19:59] <aslaen> jhobbs I am deploying openstack for a customer, and they named their hosts incorrectly.  I wanted to rename without losing the progress I had already made
[19:59] <jhobbs> aslaen: ah ok, thanks
[20:00] <jhobbs> aslaen: even on latest maas where you can change maas's idea of what a host's name is while its running, it wont change the hosts idea of what its name is
[20:01] <aslaen> right, I can run hostname to rename it, but doing that in current maas release renames it when node is rebooted right?
[20:09] <aslaen> jhobbs ^^ sorry forgot to mention you
[20:11] <jhobbs> i don't think that will change the name in dns after a reboot, but i might be wrong
[20:12] <aslaen> ya it's not in DNS it's the local hostname
[20:12] <aslaen> When I update the hostname with `hostname blah1.example.com` rebooting it cloud-init kicks in and renames it back to what is in MaaS
[20:12] <jhobbs> ah