[01:27] Problem installing MAAS nodes on Intel NUC | http://askubuntu.com/q/489786 [01:51] sorry to be a bother, but has anyone setup a maas node on an intel NUC? [01:54] l1fe: was it you how posted the askubuntu question that got linked in here? [01:54] http://askubuntu.com/q/489786 [01:54] l1fe: i haven't but i know it's been done [01:54] l1fe: what are you using for power control? [01:54] mwhudson: that would be me [01:55] mwhudson: I'm using wake on lan (it's a haswell NUC) [01:55] ok [01:56] when you say that you boot the device and it looks like the old install [01:56] how are you booting it? [01:56] so first boot is with PXE, that installed the image (i'm guessing) that enlisted the node [01:57] second boot, was also with PXE [01:57] and i think that's when it was commissioning [01:57] 3rd boot was normal boot to hdd [01:58] * mwhudson tries to remember maas terminology [01:58] i don't think that's quite how it works though [01:58] the image isn't installed until you provision the node [01:59] with maas, you're not expected to boot the device yourself ever -- maas does it [01:59] yeah, unfortunately it doesn't seem to WoL [01:59] and the end of every step seems to be the NUC shutting down, while maas thinks the node is "ready" [02:00] that's expected [02:00] the shutdown thing i mean [02:00] i think maas really expects some more uh enterprisey oob management [02:00] like ipmi or hp ilo [02:01] right, it just never starts it back up - guessing that's why the folks who I think got NUC setup with maas used the non-haswell version with AMT enabled [02:01] yes [02:01] certainly i know that's why the orange box has that particular version... [02:06] hmm that's kind of disappointing...guess I'll have to see if I can make this work somehow [02:07] you can always use the human pdu approach :) [02:09] haha, that's basically what I've been doing - but the success rate seems to be lacking... === vladk|offline is now known as vladk === vladk is now known as vladk|offline === CyberJacob|Away is now known as CyberJacob === vladk|offline is now known as vladk === vladk is now known as vladk|offline === frobware- is now known as frobware === vladk|offline is now known as vladk === g_ is now known as Guest88496 [12:37] allenap: Unless jtv has other ideas, you could start with adding the new config template / generation stuff for DHCPv6 [12:38] gmb`: For DHCP? === gmb` is now known as gmb [12:39] * rvba agree with gmb. The DHCP stuff is probably the next big thing to get sorted. [12:39] agrees* even [12:39] Yarp. [12:39] allenap: Yes. [12:40] gmb: Mucho gracias. [12:40] allenap: the trick is that we need to get two servers up and running. [12:40] De nada. [12:40] allenap: What rvba said. The config stuff is the easy part, but we’ll need two instance of dhcpd… which isn’t that hard either, but that’s potentially the trip-up point. [12:46] seen this? http://www.test-ipv6.com/ [12:49] Yep. I've used it when testing that my ISP was supporting IPv6 out of the box. [13:02] rvba: my modem doesn;t support ipv6 :/ [13:02] /o\ [13:04] rvba: stuck with tunnelling then [13:04] Yep === plars_ is now known as plars === ftp21 is now known as d4rkn3t [13:54] hello dear, I neet help with MAAS/JUJU is there someone can help me? thanks [13:54] I've run the command "juju bootstrap --upload-tools -e maas --debug" during the all debug JUJU try to connect to a node "Node02Cluster01Svr:22". the node change its status from ready to allocated, with the OS in running. after 10 minutes the error is this "ERROR juju.cmd supercommand.go:305 waited for 10m0s without being able to connect: ssh: Could not resolve hostname node02cluster01svr: Name or service not known". In the Region Contro [13:54] ller I've set DNS and DHCP service. [13:59] juju bootstrap using maas unable to ssh into nodes | http://askubuntu.com/q/490000 [14:04] * rvba replies on http://askubuntu.com. === jfarschman is now known as MilesDenver === CyberJacob is now known as CyberJacob|Away === vladk is now known as vladk|offline [18:33] can someone go over the different states that maas can be in? currently i have four nodes in "allocated to root" - does this mean they are ready to be used or is there something else that needs to happen? [18:33] i tried to juju bootstrap, but I keep on getting 409 conflict with no nodes available [18:34] l1fe: allocated to root means they should be started and running [18:34] l1fe: since they're all allocated, there are no more for juju to bootstrap with [18:35] l1fe: you'll want to stop them if you want to make them available to juju; they should be in the Ready state then [18:35] hmm ok [18:35] i must be really confused about how maas and juju interact [18:35] sorry for the obtuse questions :) === jfarschman is now known as MilesDenver === vladk|offline is now known as vladk === vladk is now known as vladk|offline [21:57] deploying charms using juju fails with tcp connection timed out | http://askubuntu.com/q/490141