[00:32] <bdx> core, dev: how can I modify the pxe boot interface of a node?
[01:38] <bdx> ^^within the context of maas
[01:39] <bdx> per ^ I'm not finding any entries in the db for pxe interface ... where is this set?
[02:46] <mup> Bug #1553848 opened: [2.0a1] TFTP back-end crashes <MAAS:New> <https://launchpad.net/bugs/1553848>
[03:16] <mup> Bug #1553855 opened: [2.0a1] Enlistment results in bad IPMI passwords <MAAS:New> <https://launchpad.net/bugs/1553855>
[04:46] <mup> Bug #1553841 opened: [2.0a1] MAAS should ensure that BMC password is correct before saving <MAAS:New> <https://launchpad.net/bugs/1553841>
[04:55] <mup> Bug #1553841 changed: [2.0a1] MAAS should ensure that BMC password is correct before saving <MAAS:New> <https://launchpad.net/bugs/1553841>
[05:04] <mup> Bug #1553841 opened: [2.0a1] MAAS should ensure that BMC password is correct before saving <MAAS:New> <https://launchpad.net/bugs/1553841>
[12:33] <voidspace> hey, what's the best way to install 2.0 for testing?
[12:34] <voidspace> From source?
[14:03] <Hvis> hey , i'm trying to setup openstack/cloud in a box. So can anyone help how can i proceed
[16:39] <voidspace> hey, what's the best way to install 2.0 for testing?
[16:39] <voidspace> From source?
[16:42] <roaksoax> voidspace: ppa:maas/next-proposed
[16:42] <roaksoax> voidspace: although, ew haven't yet made an annoucement
[16:43] <voidspace> roaksoax: thanks
[17:22] <voidspace> frobware: creating a new clone just worked....
[17:22] <voidspace> frobware: go figure
[17:23] <voidspace> frobware: hmmm... although network config may be screwed.
[17:24] <voidspace> frobware: nope, working fine
[17:37] <mag009_> hi guys
[17:37] <mag009_> as always I have more questions .. what is the best practice to scale out maas and for the redundancy
[17:39] <mag009_> for the db having a master-master is fine but what about the front end (since it's just) web request I suppose I can just put a vip and load-balance across multiples instances of maas that share the same db ?
[17:48] <mup> Bug #1554152 opened: pollinate fails in many circumstances, cloud-init reports that failure, maas reports node failed deployment <amd64> <apport-bug> <uec-images> <xenial> <cloud-init:New> <MAAS:New> <cloud-init (Ubuntu):New> <pollinate (Ubuntu):New> <https://launchpad.net/bugs/1554152>
[17:57] <mup> Bug #1554152 changed: pollinate fails in many circumstances, cloud-init reports that failure, maas reports node failed deployment <amd64> <apport-bug> <uec-images> <xenial> <cloud-init:New> <MAAS:New> <cloud-init (Ubuntu):New> <pollinate (Ubuntu):New> <https://launchpad.net/bugs/1554152>
[18:00] <roaksoax> mag009_: MAAS <=1.10 does not support HA, so you wont be able to add redundancy other than the DB
[18:00] <roaksoax> mag009_: scale out, more cluster controllers
[18:00] <mag009_> but more cluster controllers that mean each cluster have their own db
[18:00] <mag009_> am i correct /
[18:00] <mag009_> ?
[18:01] <roaksoax> mag009_: no
[18:01] <roaksoax> mag009_: the cluster controllers dont have a DB
[18:01] <roaksoax> they connect to the region
[18:01] <roaksoax> the region is where the DB would normally be
[18:03] <mag009_> ok and how do link cluster to a single region ?
[18:03] <mag009_> I haven't found anything in the doc :)
[18:05] <mag009_> nvm i can figured
[18:05] <mag009_> out*
[18:06] <mup> Bug #1554152 opened: pollinate fails in many circumstances, cloud-init reports that failure, maas reports node failed deployment <amd64> <apport-bug> <uec-images> <xenial> <cloud-init:New> <MAAS:New> <cloud-init (Ubuntu):New> <pollinate (Ubuntu):New> <https://launchpad.net/bugs/1554152>
[18:49] <mup> Bug #1039701 opened: Wrong RAM memory size <lshw:New> <MAAS:New> <landscape-client (Ubuntu):Invalid> <lshw (Ubuntu):New> <https://launchpad.net/bugs/1039701>
[19:57] <timello> hey folks! Using Xenial with MaaS 1.10... when commissioning P8 boxes, it creates netboot ethX (pxelinux.0) entry, but it does not creates the 'exec' entry which actually fires the boot
[19:57] <timello> anything am I missing?
[20:04] <roaksoax> timello: can you explain a bit more as I don't quite understand what you mean
[20:04] <timello> roaksoax: sure!
[20:06] <timello> roaksoax: I'm using MaaS 1.10 from Xenial to commission/deploy Ubuntu on Power 8 boxes. I setup the IPMI, it boots correctly, the netboot shows up in the petitboot menu... the kernel points to tftp://<IP>/pxelinux.0
[20:07] <timello> older versions I used to see another entry in the petitboot menu, which was 'exec' with kernel, initrd and boot args
[20:08] <timello> roaksoax: s/boots/powers on
[20:08] <roaksoax> timello: right, so 1.10 is actually really only 1.9 running on django 1.8/python3
[20:08] <roaksoax> timello: the exec, IIRC, was created by petiboot automatically to exect the kernel
[20:09] <timello> yeah... that is not being created and I thought the information comes from MaaS...
[20:09] <timello> dhcp is working
[20:10] <timello> nic gets the ip
[20:10] <timello> just missing the exec entry
[20:10] <roaksoax> timello: right, so MAAS 1.10 should provide the exact same PXE information as 1.9, becuase MAAS 1.10 is just MAAS 1.9 running on python3/django1.8
[20:11] <timello> roaksoax: ok, I haven't tried 1.9 to be honest... my maas controller was running 14.04 with 1.7.X or something... not even 1.8.
[20:12] <roaksoax> timello: right... I'd suggest you try 1.9 for now, since 1.10 is just a transitional release and will be suprseeded by 2.0
[20:12] <timello> roaksoax: ok, let me try a downgrade
[20:15] <timello> roaksoax: thanks