=== menn0_ is now known as menn0 === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away === mjs0 is now known as menn0 [08:38] I've just upgraded some MAAS infrastructure from Precise and 1.4 to Trusty and 1.5, and I notice that one of my cluster controllers is running low on disk due to /var/lib/maas/ephemeral being full of old data. Everything's from months ago, though the Web UI says it has up to date images (which I can find elsewhere). Is it safe for me to blow away /var/lib/maas/ephemeral after my 1.5 upgrade? [10:51] hello everyone [13:12] The cluster controllers in MAAS 1.5 seem to be trying to connect to two high-numbered ports on the region controller. Apache is listening on those ports on the region controller, but I can't find the configuration that sends them there. What are these ports, and are they predictable? === jfarschman is now known as MilesDenver [14:42] are the files in /etc/maas/templates/pxe essentially pxelinux.cfg/syslinux.cfg files? [14:42] and is it safe to edit them (once you copy/rename?) [14:45] onicrom: yes, they are templates for generating files like pxelinux.cfg files [14:46] onicrom: what are you trying to get done by copying/editing them? [14:47] i was looking to add "CONSOLE 0" and "SERIAL 1 115200 0" [14:47] onicrom: have a look at http://maas.ubuntu.com/docs/kernel-options.html [14:47] ive appended console=tty0 console=ttyS1,115200n8 to that [14:48] wasn't sure if the actual pxeboot section [14:48] oh - those are pxelinux directives? [14:48] would be sent to console, or just the install part [14:48] correct [14:48] so you can see pxelinux output on the serial console? [14:48] thats the goal [14:49] if it's pxelinux stuff you should be able to add it in the file wherever you would in a normal pxelinux file [14:49] was copying/renaming just to get a backup? [14:50] well i wasnt sure if i needed to rename either the config.commissioning.template to config.commissioning [14:50] or edit the template [14:50] ahh yeah just edit the template [14:50] or edit the arch specific file [14:50] maas opens the template and renders it and then sends it off via tftp [14:50] ok cool [14:51] so would it be best to add to config.install.tem... config.commissioning.tem... or config.local.amd64.tem.... [14:52] they're for different stages [14:52] if you want pxelinux output all the time, do all of them [14:52] would it be correct in assuming editing the amd64 would be invoked at all stages [14:52] assuming you are using that arch [14:53] config.local.amd64.template is only for localbooting, after an install is complete [14:53] otherwise amd64 uses the generic ones without arch names in the files [14:53] got it [14:53] they're not hierarchical so you have to edit them all [14:54] thanks much [14:54] you're welcome [14:54] config.local and config.local.arch need to be changed then? === chuck_ is now known as zul [14:55] hmmm [14:55] i'm not sure why there are both there [14:55] couldn't hurt :) [14:55] do you work on the project? [14:55] yes [14:57] might i suggest something... the .template extension makes me think these files , should you need to change them, should be renamed removing the .template [14:57] or copy, without .template and make changes, the system reads the non.template files should they exist [14:58] (dont mean to complain just how i assume things to work on other tools) [14:58] i could see how that's confusing [14:58] feel free to file a bug on https://bugs.launchpad.net/maas [14:59] best to have stories from real users for that sort of thing [15:01] i wouldnt vcall it a bug :) [15:01] but sure thing [15:01] i have another question :) around preseed [15:03] ok [15:03] * jhobbs in and out, just ask and i'll try to answer [15:06] https://bugs.launchpad.net/maas/+bug/1352938 [15:06] Launchpad bug 1352938 in MAAS "the use of the file extension .template can be confusing" [Undecided,New] [15:06] bug filed :) [15:08] cool, thanks [15:10] jhobbs: i'm not familair with preseed at all so this is going to be amateur hour, under /etc/maas/preseeds what are the purposes for the various files [15:14] onicrom: have you read this? https://maas.ubuntu.com/docs/development/preseeds.html [15:17] onicrom: preseeds for maas either generate cloud-init, curtin, or debian-installer config, depending on which state/install type is being used [15:18] onicrom: users can use them to customize enlistment/commissioning/installation [15:18] they're template files again, just like the pxe ones [15:18] cool [15:19] i read references to the debian-installer but my maas only says default or fast install [15:19] i assume default is debian installer? [15:19] yeah [15:19] woah i missed this doc entirely somehow :) [15:20] thanks! also... the terms commission,enlist etc are these defined somwhere? [15:25] i can't find anything [15:25] that sucks [15:25] enlistment makes maas aware of the node, commissioning does some hardware inventory [15:25] gotta run for a bit === med_ is now known as Guest26240 [15:33] any takes on 'curtin' [15:37] onicrom: it's the fastpath installer [15:37] onicrom: it's default in newer maas's - it's all i ever use [15:40] intttersting [15:40] how does customization work in this new fancy faster method [15:41] It's designed to be very customisable [15:41] See: http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/view/head:/doc/topics/overview.rst [15:42] You can pretty much replace everything. [15:42] cool i shall readup [15:50] does 14.04's maas pkg get upgraded as releases go stable (1.5->1.6) or is that a more manual process? [15:50] by 'get upgraded' i mean apt-get upgrade or dist-upgrade if more appropriate [15:53] you can apt-get upgrade mas [15:53] *maas [15:54] it will pick up whatever the latest release for trusty is [15:54] as long as that's what you're running [15:57] will trusty upgrade to mewer point releases? [15:57] rather... be upgraded to. [15:58] hmm i think roadmap questions are above my paygrade [15:58] you can always pin to a newer version if you want to though [16:04] nods [16:04] btw [16:04] damn fine job on this thing [16:04] ive setup my fair share of build systems from scratch with jump/kickstart [16:05] all the annoying stuff is taken care of, just need to sort out the customizations :) [16:06] glad you like it and thanks for the feedback! [16:06] bugs on any issues or annoyances you run into are welcome [16:15] well i have 2 data centers im building out (~40 servers) so im going to be diving real deep :) [17:13] does maas read all files in /etc/maas/preseeds? ... if i 'backup' the files in /etc/maas/preseeds (as in /etc/maas/preseeds/preseed_master.dist) will it do badness? === matsubara is now known as matsubara-lunch === roadmr is now known as roadmr_afk === CyberJacob|Away is now known as CyberJacob === matsubara-lunch is now known as matsubara === jfarschman is now known as MilesDenver [19:11] looks like the installer output is not being sent to my serial console .. the commissioning is sent to serial console but the install is not [19:11] hrms [19:19] onicrom, have you been checking the logs in /var/log/maas? [19:26] now its hung [19:30] checking logs thanks :) [19:59] np === roadmr_afk is now known as roadmr [20:15] damn dell drac seems to drop offline whenever the ubuntu installed 'probes' the network devices === roadmr is now known as roadmr_afk === roadmr_afk is now known as roadmr === CyberJacob is now known as CyberJacob|Away === menn0_ is now known as menn0 === jfarschman is now known as MilesDenver