User1: 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?
User2: hello everyone
User1: 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?
User2: are the files in /etc/maas/templates/pxe essentially pxelinux.cfg/syslinux.cfg files?
User2: and is it safe to edit them (once you copy/rename?)
User3: User2 yes, they are templates for generating files like pxelinux.cfg files
User3: User2 what are you trying to get done by copying/editing them?
User2: i was looking to add "CONSOLE 0" and "SERIAL 1 115200 0"
User3: User2 have a look at http://maas.ubuntu.com/docs/kernel-options.html
User2: ive appended console=tty0 console=ttyS1,115200n8 to that
User2: wasn't sure if the actual pxeboot section
User3: oh - those are pxelinux directives?
User2: would be sent to console, or just the install part
User2: correct
User3: so you can see pxelinux output on the serial console?
User2: thats the goal
User3: if it's pxelinux stuff you should be able to add it in the file wherever you would in a normal pxelinux file
User3: was copying/renaming just to get a backup?
User2: well i wasnt sure if i needed to rename either the config.commissioning.template to config.commissioning
User2: or edit the template
User3: ahh yeah just edit the template
User2: or edit the arch specific file
User3: maas opens the template and renders it and then sends it off via tftp
User2: ok cool
User2: so would it be best to add to config.install.tem... config.commissioning.tem... or config.local.amd64.tem....
User3: they're for different stages
User3: if you want pxelinux output all the time, do all of them
User2: would it be correct in assuming editing the amd64 would be invoked at all stages
User2: assuming you are using that arch
User3: config.local.amd64.template is only for localbooting, after an install is complete
User3: otherwise amd64 uses the generic ones without arch names in the files
User2: got it
User3: they're not hierarchical so you have to edit them all
User2: thanks much
User3: you're welcome
User2: config.local and config.local.arch need to be changed then?
User3: hmmm
User3: i'm not sure why there are both there
User3: couldn't hurt :)
User2: do you work on the project?
User3: yes
User2: might i suggest something... the .template extension makes me think these files , should you need to change them, should be renamed removing the .template
User2: or copy, without .template and make changes, the system reads the non.template files should they exist
User2: (dont mean to complain just how i assume things to work on other tools)
User3: i could see how that's confusing
User3: feel free to file a bug on https://bugs.launchpad.net/maas
User3: best to have stories from real users for that sort of thing
User2: i wouldnt vcall it a bug :)
User2: but sure thing
User2: i have another question :) around preseed
User3: ok
 * jhobbs in and out, just ask and i'll try to answer
User2: https://bugs.launchpad.net/maas/+bug/1352938
User4: Launchpad bug 1352938 in MAAS "the use of the file extension .template can be confusing" [Undecided,New]
User2: bug filed :)
User3: cool, thanks
User2: User3 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
User3: User2 have you read this? https://maas.ubuntu.com/docs/development/preseeds.html
User3: User2 preseeds for maas either generate cloud-init, curtin, or debian-installer config, depending on which state/install type is being used
User3: User2 users can use them to customize enlistment/commissioning/installation
User3: they're template files again, just like the pxe ones
User2: cool
User2: i read references to the debian-installer but my maas only says default or fast install
User2: i assume default is debian installer?
User3: yeah
User2: woah i missed this doc entirely somehow :)
User2: thanks! also... the terms commission,enlist etc are these defined somwhere?
User3: i can't find anything
User3: that sucks
User3: enlistment makes maas aware of the node, commissioning does some hardware inventory
User3: gotta run for a bit
User2: any takes on 'curtin'
User3: User2 it's the fastpath installer
User3: User2 it's default in newer maas's - it's all i ever use
User2: intttersting
User2: how does customization work in this new fancy faster method
User5: It's designed to be very customisable
User5: See: http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/view/head:/doc/topics/overview.rst
User5: You can pretty much replace everything.
User2: cool i shall readup
User2: does 14.04's maas pkg get upgraded as releases go stable (1.5->1.6) or is that a more manual process?
User2: by 'get upgraded' i mean apt-get upgrade or dist-upgrade if more appropriate
User3: you can apt-get upgrade mas
User3: *maas
User3: it will pick up whatever the latest release for trusty is
User3: as long as that's what you're running
User2: will trusty upgrade to mewer point releases?
User2: rather... be upgraded to.
User3: hmm i think roadmap questions are above my paygrade
User3: you can always pin to a newer version if you want to though
User2: nods
User2: btw
User2: damn fine job on this thing
User2: ive setup my fair share of build systems from scratch with jump/kickstart
User2: all the annoying stuff is taken care of, just need to sort out the customizations :)
User3: glad you like it and thanks for the feedback!
User3: bugs on any issues or annoyances you run into are welcome
User2: well i have 2 data centers im building out (~40 servers) so im going to be diving real deep :)
User2: 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?
User2: 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
User2: hrms
User6: onicrom, have you been checking the logs in /var/log/maas?
User2: now its hung
User2: checking logs thanks :)
User6: np
User2: <bitching> damn dell drac seems to drop offline whenever the ubuntu installed 'probes' the network devices </bitching>
maas
Ubuntu IRC