[00:26] MichaelFischer, sorry, no. i don't think maas supports custom kernels/images [00:27] Bummer.. Thanks [08:07] in MAAS 2.0, what is the CLI to add MX and CNAME records to DNS? [08:43] wooot! FIgured it out! [08:45] CLI would be for MX records: maas dnsresource-records create fqdn=mail.maas rrtype=mx rrdata=' mail.maas' [08:50] CLI for CNAME is: maas dnsresource-records create fqdn=www.maas rrtype=cname rrdata=webserver.maas [10:08] Hi everyone, how can i configure maas to add a user to nodes while deploying them? [10:14] while deploying those nodes* [15:57] In maas 2.0, how can I override the boot disk. I have a small USB installed directly on the motherboard that contains a boot image, which often enumerates as sda. I see that apparently it was possible in 1.9, but I can't find it in 2.0. === valeech_ is now known as valeech [19:34] stack_korora, greetings, happy sunday to you [19:35] Greetings! Happy Sunday to you as well! [19:35] stack_korora, now did you set up the power type for these vmware-backed nodes? and was the resulting power check successful? [19:35] I set them to manual [19:36] hm, i don't think i ever tried that. i've used 'virsh' and 'ipmi' for kvm-backed and hardware-backed nodes respectively [19:37] I looked at setting up the automated path with the VMWare option, but it was asking for things that I think are ESX based, not workstation based. So when it didn't work, I didn't try that hard. I just set it to manual. :-) [19:37] I am spinning up that box & vm's now. [19:40] stack_korora, i found this https://goo.gl/JzZmWD . it's dated but it may still be good [19:40] OK. Let me try. I just got the systems up and verified network. [19:42] pmatulis, after further investigation, I discovered that my USB mic is supported by the xenial kernel; the problem I have is that the iface isn't configured in /etc/network/interfaces. So I don't think I need a custom kernel, just a way of configuring the iface. [19:42] *USB nic [19:45] Found the info for the disk. Maas shows it to be a "VMWare Virtual S" it sees the path as /dev/sda. All of that is correct, so not sure why it tells me in the node Storage section that no storage is found. [19:45] is it possible to run some custom script when commissioning and during deployment? This only appears to be an issue with Ubuntu as centos configures the USB nic appropriately. [19:48] MichaelFischer, interesting. i believe you can customize the preseed stuff [19:49] MichaelFischer, are you familiar with preseed? [19:49] stack_korora, does the power check succeed? [19:49] pmatulis, Nope, do you know where I can find documentation for that? [19:50] MichaelFischer, i may have something that is maas-specific. lemme look [19:51] otherwise, in the meantime, just google 'ubuntu preseed' to get the basics of what it is [19:51] it's the debian/ubuntu version of red hat's kickstart [19:51] Not yet. It doesn't seem to like any Host value I give it. It didn't like the host MAC for the same virtual LAN the vm's are on, nor did it like the real MAC address. [19:52] stack_korora, if the power check fails nothing will work [19:52] Oh. Really? Then why have a manual setup? [19:53] Or am i misunderstanding something? [19:53] stack_korora, yeah, that i'm not sure about tbh [19:53] manual sounds like the user will need to power on and off but that needs to be done at very specific times. i need to play around with that [19:54] stack_korora, are you prompted to power cycle when you choose 'manual'? [19:54] Yes [19:54] ohh [19:55] interesting [19:55] i'm going to file a doc issue about providing more info on the different power types [19:56] Which I will probably need to use IRL anyway. Some of the specialty equipment we have runs SL6, but doesn't support PXE or IPMI. :-/ [19:56] Although the big concern for me ATM is the new hardware coming in which should all support IPMI and PXE. So I can worry about the manual stuff later. [19:57] this page is srsly lacking: http://maas.io/docs/manage-power [19:59] So where I am stuck ATM on the power thing is that it "sees" my vmware host, but says it isn't a rack controller with access to that host. [20:00] Probably because it is on a different lan segment. [20:00] oh my [20:00] I was trying really hard to mimic my work environment virtually. [20:00] I get a few ports on a network that I have zero control over. Those ports get me internet access. [20:01] tbh, you should be testing in a more controlled and ideal environement, then start going towards something more realistic [20:01] I have a few hosts plugged into them and a "back lan" where I manage my cluster farm. [20:01] get off the ground, test it out first [20:01] Fair enough, but I still haven't found a good document explaining what good MAAS environment looks like... [20:02] I know it needs to be on the same LAN as the node sit controls, but that is about as much as the docs say about it. [20:02] I also know it really doesn't like multiple networks. [20:02] And I don't want it controlling (or attempting to control) other VMs or computers on the network. [20:03] so I gave it its very own private LAN. [20:03] And am adding VMs to that virtual LAN. [20:03] so my "network" looks something like this: [20:05] "The Real Internet"<->My physical host <->my virtual network<->bridge VM<->private VM with all MAAS nodes. [20:08] Hrm. I am thinking about trying to move it onto a second virtual network that shares with the host directly. [20:08] Let me see how that works... [20:16] Well...I have goofed something in my routing...not getting out to the internet from the MAAS server...but the rest of the networking with the host is working....Let me try the chassis again. [20:17] OK. That worked (at least to save the configuration!). Let me try adding a host now. [20:19] Hrm...nope....:-/ Let me try something else... [20:21] MichaelFischer, yeah, maas used preseed but now it looks like it now uses something called 'curtin' which is a faster way to install. i don't know it well but maybe this will get you started: https://goo.gl/xiIhfI [20:21] also see contents of /etc/maas/preseeds [20:22] Okay, thanks for the info. [20:26] Yeah, I can't get the Shared VM (I created a new one) to talk to the MAAS VM, regardless of which network it is on. [20:27] I have never used the Shared VM's before. Let me do some reading on them. [20:33] Oooooooohhhhhhh. That's why. The Shared VM's sit on the network proper! They are getting the same IP/network as my host system going out to the network! [20:33] Yeah...I can't have MAAS jacking around with that network.... [20:49] stack_korora, i'm not sure about vmware networks but, generally, yes, you need to put MAAS on its own network b/c it must use its own DHCP for PXE booting (enlisting,commissioning) [20:53] I am not sure how to link it to the network on the Shared VM. I have tried a half dozen things I found online but I still can't get the Shared VM's on the same network. [20:53] But I am trying something else [20:54] I created a private LAN that removes most of the layers of the network. So the host is really just a gateway on the network right now. [20:54] Doing a quick rebuild of MAAS from ISO. [20:55] So I won't have power control, but I should have a simpler network for the VM which I will do manual power on again. [21:04] MichaelFischer, stack_korora: if you still have troubles your next step would be a mailing list. i don't know why there is only a devel list but i guess that's all there is at this time. see channel topic [21:06] OK. Thanks for your help pmatulis. I do appreciate you taking the time to help me out. [21:33] Thanks Peter! [23:32] 100% failure to deploy trusty tahr. Deployed, ssh 22 connect refused. SSH key verifyed, account acquired. [23:32] Can anyone help? [23:36] batkins61, have you got any kind of node deployed? [23:42] All nodes commissioned and deploy successfully. All nodes ping on ICMP. Zero nodes respond to SSH. All nodes acquired by root account in MAAS, with verified SSH key. [23:42] All nodes report connect refused on ssh from maas controller. [23:43] maas 2.0 [23:43] 14.04.5 installed, with 16.04.1 as commissioning OS (14.05 fails to handle disks correctly). [23:46] In short, no. Whether trying to deploy 16.04.1 or 14.04.05, nothing has deployed successfully. [23:49] batkins61: so the machines change from "deploying" to "failed deployment" [23:49] ? [23:53] No, all report deployed, and stay as deployed. But, there is no ssh access, and no access from the consoel. [23:53] console. [23:53] ssh on 22 returns connect refused, no change of port configured at all. [23:54] console just refuses ubuntu or root. [23:54] Hey, maybe an override to allow ubuntu or root console access would be good? Does one exist? [23:56] beisner: if the machine is "deployed" then it /must/ have imported ssh keys [23:56] err [23:56] batkins61: ^^ [23:56] batkins61: othereise if wouldnt have been marked as deployed [23:57] it wouldnt* [23:57] That's what I thought. But ssh ubuntu@ gives connect refused. In the GUI, that is what is reported as provided by DHCP for the server. [23:58] No other interfaces are configured. [23:58] batkins61: is your interface in "auto assign"? [23:58] No, DHCP [23:58] batkins61: probably the machine has a different IP and maas hasnt updated that yet [23:59] batkins61: try with "auto assign"