[07:07] <rvba> roaksoax: thanks a lot!  I'll test that sometime today.
[09:55] <Bicyus> Hi there!
[10:21] <Bicyus> guys i'm taking this error when installing a node from PXE:
[10:21] <Bicyus> true && in-target sh -c 'f=$1; shift; echo $0 > $f &&chmod 0440 $f $* 'ubuntu ALL=(ALL) NOPASSWD: ALL ' /etc/sudoers.d/maas && wget "http://maas-ip:80/cblr/svc/op/nopxe/system/$system_name" -o /dev/null && true
[10:21] <Bicyus> failed wit exit 1
[10:22] <Bicyus> cant find any answer on google...
[10:22] <Bicyus> any clue why this is happening?
[10:49] <bigjools> Bicyus: update to the version in ppa:maas-maintainers/stable
[10:51] <Bicyus> thanks bigjools i'm trying again, without automatic commisioning
[10:53] <Bicyus> is that PPA production ready? i mean, we are testing to deploy openstack on a small private cloud
[10:54] <bigjools> it's getting SRUed soon
[15:52] <roaksoax> jtv: still around?
[15:55] <jtv> roaksoax: barely!  Hi.
[15:55] <jtv> I'm in Europe.
[15:55] <roaksoax> jtv: was just wondering the ETA for having the support to move all the templates to 'etc' ?
[15:56] <jtv> I just started on it!  Shouldn't take long.
[15:56] <jtv> Actually I wanted to ask you one thing: would it be OK for the package just to install an entire directory etc/maas/templates as /etc/maas/templates, in one go?  Or would you want me to break that up further?
[15:57] <roaksoax> jtv: ok cool, yeah I just saw the ETC_DIRECTORY thing, but I was wondeirng if it would make sense to continue to do things like: POWER_TEMPLATE_DIR, PXE_TEMPLATE_DIR, etc
[15:57] <roaksoax> jtv: i was thinking that the best would be: /etc/maas/templates/<power,pxe,etc>/*.template
[15:58] <roaksoax> and we also need /etc/maas/preseeds/<all preseeds>
[15:58] <roaksoax> so a PRESEED_TEMPLATE_DIR variable would be nice too (if it doesn't yet exist)
[15:59] <jtv> AFAICT what you describe for the templates is exactly what I documented.
[15:59] <roaksoax> jtv: yeah just reading :)
[16:00] <jtv> POWER_TEMPLATE_DIR etc. will all be gone — with a provision for previous settings, I suppose, but people won't be invited to edit them individually any more.
[16:01] <roaksoax> jtv: I think the location of the template dir's should be configurable for each of the templates
[16:01] <jtv> Can you give me an example of when that would be useful?
[16:03] <roaksoax> jtv: Personally, I have stronger preference for POWER_TEMPLATE_DIR, PXE_TEMPLATE_DIR, PRESEED_TEMPLATE_DIR, etc
[16:04] <roaksoax> jtv: that way you are providing more flexibility
[16:04] <roaksoax> smoser: ^^ thohgts?
[16:04] <roaksoax> thoughts?
[16:04] <jtv> I understand the flexibility is nice, but it won't come for free — it means more maintenance burden, more to keep in mind.  So it's important I think to keep an eye on practical uses.
[16:12] <roaksoax> jtv: if that's easier for you to maintain then I'd suggest TEMPLATE_DIR = '/etc/maas/templates' and then it goes from there
[16:12] <roaksoax> jtv: however, don;'t we currently have a template dir for each? say the code nows where to find DHCP temapltes, where to find DNS temapltes, etc etc
[16:12] <roaksoax> so that would mean only extending that to be configurable
[16:14] <jtv> Writing it is easy — I'm not worried about that.  But this kind of thing does add friction to maintenance.  Can you give me an example of how you'd use this?
[16:14] <jtv> I need to understand what the purpose is.
[16:15] <roaksoax> jtv: the purpose is the same as why we currently have POWER_CONFIG_DIR/POWER_TEMPLATES_DIR, DNS_CONFIG_DIR, etc
[16:15] <roaksoax> it allows more flexibility for the packager
[16:15] <roaksoax> for the user
[16:15] <roaksoax> etc
[16:16] <roaksoax> jtv: that way the user can create custom directory *names* to store their templates
[16:16] <roaksoax> jtv: so if the user wants, they can do: POWER_TEMPLATES_DIR = /var/lib/whatever/power_management_templates/
[16:16] <jtv> How do you manage upgrades to those?
[16:17] <roaksoax> instead of being restricted to only "power"
[16:17] <jtv> In that kind of situation, if the packaged version changes, how do you detect & resolve the difference?
[16:17] <roaksoax> jtv: you don't need to, packaging will default to /etc/maas/templates/{power,pxe,etc}
[16:18] <roaksoax> jtv: TBH, I personally think separate DIR vars for each dir is best due to flexibility, but if it is more convenient to keep them under one single variable, i'm fine with that too
[16:18] <jtv> I do think it simplifies the celery config, which is quite awkward to get one's head around.
[16:19] <jtv> There will be separate directories for different kinds of templates, so you can still mess with the config at that level if you really want.
[16:19] <roaksoax> jtv: well the celery config already has the concept of separate DIR's
[16:19] <jtv> Only some.
[16:20] <roaksoax> jtv: and yes, the idea is that configs are meant to be user configurable
[16:20] <roaksoax> but if it is one dir, then make it TEMPLATES_DIR instead of ETC_DIRECTORY
[16:21] <jtv> BTW right now the only templates directory that I see a configuration option for is the one for the power templates.
[16:22] <roaksoax> jtv: i know :) that's why I thought we were gonna add 1 var per temaplte type
[16:23] <jtv> I guess you could always create your own version and then softlink to the regular one in /etc for the things you don't want to change...
[16:24] <roaksoax> jtv: so to make things simpler, I think we should just go for TEMPLATES_DIR (instead of ETC_DIRECTORY)
[16:24] <roaksoax> jtv: so that would allow us to do: 'etc/maas/templates' or 'etc/maas/xyz', etc
[16:24] <jtv> Yes, we can do that...  It'll cost us one simplification I was hoping to make, but I can live with that.
[16:25] <roaksoax> jtv: so the idea is not really that templates are to be limited to live in ETC< but rather, that you can decide where you want your templates regardless of whether it is on /etc/<someplace> or not
[16:28] <roaksoax> jtv: and in the case of power, note that power has both, templates and config, in that case, it does make sense to have separate variables for the templates and the config
[16:32] <jtv> Not a pleasant thought to have separately configurable template and config directories just for the power methods.  :/
[16:38] <jtv> Is it really that much of a problem to have a single directory that's mostly softlinks to the packaged version, with a few customized files?
[16:39] <roaksoax> no it is not
[16:39] <roaksoax> again i'm fine with TEMPLATES_DIRECTORY = '/etc/maas/templates'
[16:40] <roaksoax> i mean default can be TEMPLATES_DIRECTORY = None which will look for the templates the place tjhey are now
[16:40] <roaksoax> but if set, then it will look for the templates in the currently set directory
[16:40] <jtv> We can't look for the templates the place they are now — the point of all this is to move them.
[16:41] <jtv> Right now, the code just looks in its own location.
[16:41] <jtv> The move takes that easy default away.
[16:41] <roaksoax> right
[16:42] <roaksoax> I think there should *always* be a default
[16:42] <roaksoax> that you can configure later on
[16:42] <roaksoax> currently, the POWER_TEMPLATE_DIR allows you to have a sane default, but also allows you to move the templates and place them something else
[16:42] <roaksoax> and I think that's how it should be designed
[16:44] <roaksoax> the idea is to allow the change of location of the templates, making it configurable. The idea is not to restrict them to 'etc'
[16:44] <jtv> I do think it makes sense to keep all those customized directories together, so that there's a single standard layout wherever you put them.
[16:45] <jtv> Separating the power templates from the power config does make that harder.
[16:45] <roaksoax> jtv: i would be fine having the config reside at the same location of the template
[16:46] <roaksoax> jtv: at the end, the file extension will differ file.{template,config}
[16:46] <jtv> That would simplify it a lot...  technically it's not a "template" but it seems close enough.
[16:47] <roaksoax> yeah
[16:48] <jtv> It could be argued that it's not "config" either because it's just stuff that's got to be sent over, not something that controls MAAS's behaviour.
[16:48] <roaksoax> yeah
[16:49] <roaksoax> in reality it is a config template
[16:50] <jtv> Okay, I'll revise tomorrow to make the split at the /etc/maas/templates level.  Can I make maas-cluster-controller.install just install that whole directory in one go?
[16:50] <roaksoax> jtv: yes
[16:51] <jtv> Great.  Thanks.
[16:51] <jtv> And now I'll be off!
[16:53] <roaksoax> have a good one
[16:53] <jtv> nn
[17:32] <kumquat> hi there everyone.  i hate to ruin the silence by asking a question, but i'm running 1.3 in development at the moment and my nodes time out when trying to access metadata during cloud-init and after pxeboot (169.254.169.254/meta-data/instance-id/ timeout).  i don't have any oauth credentials defined in the enlistment preseed; could this be the source of the problem?