[04:56] <bigjools> jtv: just landing a packaging fix now
[04:56] <jtv> Thanks
[05:07] <bigjools> jtv: it's in
[05:13] <jtv> bigjools: sent you my draft reply.
[05:15] <bigjools> jtv: looking
[05:46] <jtv> bigjools: could I bother you for a review?  https://code.launchpad.net/~jtv/maas/bug-1379568/+merge/237893
[05:47] <bigjools> jtv: doing one already but I'll take a look
[05:50] <jtv> Thanks.
[06:01] <bigjools> gmb: instead of the red error banner, do you think a separate oops page would be better?
[06:01] <bigjools> it confused me until I realised what was going on
[07:59] <gmb> bigjools: If the red error banner is confusing, then yes, we should do something different. I think we have a chunk of work to do on error reporting, actually: at the moment errors that happen in bulk actions are barely reported at all (just "couldn't be executed on N nodes:").
[09:37] <jtv> Any reviewers available?
[09:37] <jtv> rvba: I'll also need landing approval, but I'm going to run some local Q/A first.
[09:51] <allenap> jtv: I want to get my branches on the way to landingdom, then I’ll get stuck into your reviews.
[09:51] <jtv> Thanks!
[10:11] <jtv> allenap: thanks for the swarm of reviews.
[10:13] <allenap> jtv: You’re welcome. The code was good so it was easy.
[10:16] <jtv> Thanks.  Really making a point of facilitating reviews.
[10:35] <gmb> allenap, jtv, (rvba): Review needed when you have chance gents: https://code.launchpad.net/~gmb/maas/bug-1379154/+merge/237936
[10:35] <jtv> I'll take it.
[10:35] <gmb> Thanks
[10:37]  * gmb -> moar tea
[10:53] <gmb> jtv: Gah, I missed the ", you"! But yay, made you look :)
[10:54] <gmb> Thanks for the review :)
[11:22] <zezom> I'm currently running proxmox at home on a single server + NAS but I'm quite impressed with what I've seen MASS + JUJU do. Unfortunately I am unable to tell if I can run MAAS, JUJU and my virtuals all on a single server. I would like the ability to add more servers in the future but for now one server is all I have. I've read through the MAAS install doco on ubuntu.com but it doesn't say if the MASS controller install can run any virtual's on i
[11:22] <zezom> t's self or if it's only used to bootstrap other nodes to run virtual's.
[11:24] <zezom> I also have a Ubuntu desktop but I shut it down when not in use.
[11:28] <rbasak> zezom: no need for MAAS at all if you only have one server. You can just use Juju on it directly, and Juju can create VMs or containers as needed.
[11:29] <rbasak> zezom: you can use the "manual" Juju provider for this. Or the "local" provider if you never want to go beyond one server (it's a bit easier).
[11:29] <zezom> rbasak, that's great. and in the future I can install maas when required?
[11:29] <rbasak> For just a small handful of servers, the "manual" provider should be fine.
[11:30] <rbasak> Beyond that, to switch to MAAS, you'll need to redeploy to a new MAAS environment.
[11:30] <zezom> should I install the cloud version of the Ubuntu server image then? Or just the standard server image?
[11:30] <rbasak> For the manual or local providers, just the standard server image will be fine.
[11:30] <rbasak> If local, bootstrap Juju from the server itself. If manual, I think you can bootstrap it from your desktop.
[11:31] <rbasak> Hmm.
[11:31] <zezom> when you say redeploy will that mean I'll have to recreate the setup? or I can just move the setup to the new hardware after presenting it to the existing juju?
[11:31] <rbasak> If you want to manage the deployment from your desktop, the manual provider might be easier in that case.
[11:31] <rbasak> Anyway, #juju would probably be more relevant for this conversation. People there know more than I do about this.
[11:31] <rbasak> You'll have to recreate.
[11:32] <rbasak> Juju has functionality that makes this easier though, with backup/restore stuff (I'm not familiar with it though)
[11:32] <zezom> thank you for the info. it's appreciated.
[11:45] <gmb> rvba, https://code.launchpad.net/~gmb/maas/bug-1379154/+merge/237936 needs approval for landing when you have a moment.
[11:50] <jtv> And a bunch of mine as well...
[12:08] <rvba> gmb: just reviewed your branch.
[12:08] <gmb> rvba: thx
[12:09] <jtv> rvba: could you review landing-approval-review mine as well?
[12:09] <rvba> jtv: doing it now
[12:09] <jtv> I've got 4 up, but they're not big.
[12:09] <jtv> Thanks.
[13:29] <gmb> jtv, rvba: https://code.launchpad.net/~gmb/maas/fix-register_event_and_event_type-bug-1379401 needs reviewing if you have the time and bandwidth.
[13:29] <gmb> allenap: ^^
[13:30] <allenap> gmb: I have spare girth in my band.
[13:54] <jtv> Simple documentation review: https://code.launchpad.net/~jtv/maas/update-ipv6-limitations/+merge/237982
[14:02]  * gmb -> out; errands. Back later
[14:44] <th3rt> I'm trying to use MaaS to setup some super micro nodes with the IPMI on a separate maas network.  I can't seem to get MaaS to associate the IPMI interfaces with the correct host (I think because they are on a different network in MaaS).  Can anyone tell me what I'm doing wrong?
[14:46] <jtv> th3rt: having them on a separate network should be fine.  No idea what could be going wrong there.
[14:47] <th3rt> If I delete all the nodes from MaaS,  how can I get MaaS to re-discover the nodes?
[14:48] <th3rt> ... or is that the wrong thing to do.  I didn't set this MaaS server up originally (and have never used MaaS before) so I'm not sure how the discovery process works once a node has been deleted.
[14:48] <jtv> th3rt: as long as they're set to netboot, just turn them on.
[14:49] <jtv> Assuming you're letting MAAS manage DHCP, and letting the nodes netboot,
[14:49] <jtv> turning a node on will netboot it off the maas server.
[14:49] <jtv> It will boot into an ephemeral image that registers the node with the server.
[14:51] <th3rt> jtv,  thanks much.  That helps.  I am letting MaaS manage DHCP.
[14:51] <jtv> np
[22:57] <DominiKiD> can anyone help me with my maas configuration?
[22:57] <DominiKiD> i beent ryign to do this for weeks and i have no clue of what im doung..
[22:57] <DominiKiD> doing
[22:58] <DominiKiD> i been  trying to make my own home server and add a node
[22:58] <DominiKiD> i installed mass on one of the computers
[22:58] <DominiKiD> and eveyrthign seems to be working..
[22:58] <DominiKiD> now i dont have a blue how to configure the dhcp
[22:58] <DominiKiD> the clusters
[22:59] <DominiKiD> help enyone?