[01:41] <benlake> any thoughts as to why using a host name in the qemu+ssh:// stanza doesn’t function? The MAAS controller can resolve it, but it just doesn’t work unless I use an IP address.
[01:50] <pmatulis> benlake, as the user 'maas' on the rack controller, does 'host <kvm hostname>' work?
[03:36] <benlake> pmatulis: yessir
[04:15] <benlake> what the smack, why does makring something broken power it down… ugh
[09:48] <mup> Bug #1695868 opened: [2.2. bzr6054-0ubuntu1~16.04.1, Machine details - Interfaces] I tried to create a bond from two bridges and the creation failed but I didn't get any feedback on the UI <ui> <MAAS:New> <https://launchpad.net/bugs/1695868>
[14:59] <ThiagoCMC> hey guys, is there any way to deploy nodes with root login enabled (via ssh)?
[15:27] <roaksoax> ThiagoCMC: no, you can customize your deployment though
[15:27] <roaksoax> ThiagoCMC: e.g. userdata, or via preseeds
[15:28] <ThiagoCMC> ok, I know... I was just wondering if there was an option on UI to do that...
[15:28] <ThiagoCMC> No biggied
[17:10] <mup> Bug #1695937 opened: [2.2] NTP server selection might not be optimal for racks serving multiple VLANs <MAAS:Triaged> <https://launchpad.net/bugs/1695937>
[18:52] <benlake> roaksoax: you mentioned custom curtin scripts and I expressed interest. I’ll now express interest in your mention of customer preseeds. Please esplain? Just point me at something, I haven’t found such info myself.
[18:55] <roaksoax> benlake: https://insights.ubuntu.com/2017/06/02/customising-maas-installs/
[18:56] <benlake> roaksoax: hero!
[19:44] <roaksoax> :)
[19:51] <roaksoax> benlake: /win 4
[19:51] <roaksoax> err
[19:51] <roaksoax> sorry
[20:23] <benlake> is there a way to configure a VLAN associated subnet on an interface in an untagged manner?
[20:24] <benlake> that’s a heavy question. Basically, I know this interface has access to VLAN 123, but I can’t tell MAAS to use subnet 456 on the interface unless I also set it up to be tagged, which I don’t want.
[20:31] <ThiagoCMC> benlake, deploy it as tagged, then, edit the /etc/network/interfaces file and remove the tag manually (I'm not an MaaS expert but, should work)... I'm doing similar things...
[20:32] <benlake> well, I mean I know I can setup what I need manually. Trying to use MAAS native functions as much as possible
[20:33] <benlake> but doing what you suggest at least let’s the IPAM function
[20:35] <benlake> was hoping to let MAAS handle the interfaces file solely and not cross streams with deployment tooling
[21:13] <mup> Bug #1695994 opened: [2.2] Error message when MAAS cannot resolve upstream is not user friendly <MAAS:New> <MAAS 2.2:New> <https://launchpad.net/bugs/1695994>
[22:38] <benlake> is there a way to change an IP post deployment? that seems like it’d be a pretty reasonable use case. Especially if it was statically assigned.