/srv/irclogs.ubuntu.com/2013/05/29/#maas.txt

=== dannf` is now known as dannf
rvbaroaksoax: thanks a lot!  I'll test that sometime today.07:07
BicyusHi there!09:55
Bicyusguys i'm taking this error when installing a node from PXE:10:21
Bicyustrue && 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 && true10:21
Bicyusfailed wit exit 110:21
Bicyuscant find any answer on google...10:22
Bicyusany clue why this is happening?10:22
bigjoolsBicyus: update to the version in ppa:maas-maintainers/stable10:49
Bicyusthanks bigjools i'm trying again, without automatic commisioning10:51
Bicyusis that PPA production ready? i mean, we are testing to deploy openstack on a small private cloud10:53
bigjoolsit's getting SRUed soon10:54
=== kentb-out is now known as kentb
roaksoaxjtv: still around?15:52
jtvroaksoax: barely!  Hi.15:55
jtvI'm in Europe.15:55
roaksoaxjtv: was just wondering the ETA for having the support to move all the templates to 'etc' ?15:55
jtvI just started on it!  Shouldn't take long.15:56
jtvActually 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:56
roaksoaxjtv: 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, etc15:57
roaksoaxjtv: i was thinking that the best would be: /etc/maas/templates/<power,pxe,etc>/*.template15:57
roaksoaxand we also need /etc/maas/preseeds/<all preseeds>15:58
roaksoaxso a PRESEED_TEMPLATE_DIR variable would be nice too (if it doesn't yet exist)15:58
jtvAFAICT what you describe for the templates is exactly what I documented.15:59
roaksoaxjtv: yeah just reading :)15:59
jtvPOWER_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:00
roaksoaxjtv: I think the location of the template dir's should be configurable for each of the templates16:01
jtvCan you give me an example of when that would be useful?16:01
roaksoaxjtv: Personally, I have stronger preference for POWER_TEMPLATE_DIR, PXE_TEMPLATE_DIR, PRESEED_TEMPLATE_DIR, etc16:03
roaksoaxjtv: that way you are providing more flexibility16:04
roaksoaxsmoser: ^^ thohgts?16:04
roaksoaxthoughts?16:04
jtvI 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:04
roaksoaxjtv: if that's easier for you to maintain then I'd suggest TEMPLATE_DIR = '/etc/maas/templates' and then it goes from there16:12
roaksoaxjtv: 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 etc16:12
roaksoaxso that would mean only extending that to be configurable16:12
jtvWriting 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
jtvI need to understand what the purpose is.16:14
roaksoaxjtv: the purpose is the same as why we currently have POWER_CONFIG_DIR/POWER_TEMPLATES_DIR, DNS_CONFIG_DIR, etc16:15
roaksoaxit allows more flexibility for the packager16:15
roaksoaxfor the user16:15
roaksoaxetc16:15
roaksoaxjtv: that way the user can create custom directory *names* to store their templates16:16
roaksoaxjtv: so if the user wants, they can do: POWER_TEMPLATES_DIR = /var/lib/whatever/power_management_templates/16:16
jtvHow do you manage upgrades to those?16:16
roaksoaxinstead of being restricted to only "power"16:17
jtvIn that kind of situation, if the packaged version changes, how do you detect & resolve the difference?16:17
roaksoaxjtv: you don't need to, packaging will default to /etc/maas/templates/{power,pxe,etc}16:17
roaksoaxjtv: 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 too16:18
jtvI do think it simplifies the celery config, which is quite awkward to get one's head around.16:18
jtvThere 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
roaksoaxjtv: well the celery config already has the concept of separate DIR's16:19
jtvOnly some.16:19
roaksoaxjtv: and yes, the idea is that configs are meant to be user configurable16:20
roaksoaxbut if it is one dir, then make it TEMPLATES_DIR instead of ETC_DIRECTORY16:20
jtvBTW right now the only templates directory that I see a configuration option for is the one for the power templates.16:21
roaksoaxjtv: i know :) that's why I thought we were gonna add 1 var per temaplte type16:22
jtvI 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:23
roaksoaxjtv: so to make things simpler, I think we should just go for TEMPLATES_DIR (instead of ETC_DIRECTORY)16:24
roaksoaxjtv: so that would allow us to do: 'etc/maas/templates' or 'etc/maas/xyz', etc16:24
jtvYes, we can do that...  It'll cost us one simplification I was hoping to make, but I can live with that.16:24
roaksoaxjtv: 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 not16:25
roaksoaxjtv: 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 config16:28
jtvNot a pleasant thought to have separately configurable template and config directories just for the power methods.  :/16:32
jtvIs 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:38
roaksoaxno it is not16:39
roaksoaxagain i'm fine with TEMPLATES_DIRECTORY = '/etc/maas/templates'16:39
roaksoaxi mean default can be TEMPLATES_DIRECTORY = None which will look for the templates the place tjhey are now16:40
roaksoaxbut if set, then it will look for the templates in the currently set directory16:40
jtvWe can't look for the templates the place they are now — the point of all this is to move them.16:40
jtvRight now, the code just looks in its own location.16:41
jtvThe move takes that easy default away.16:41
roaksoaxright16:41
roaksoaxI think there should *always* be a default16:42
roaksoaxthat you can configure later on16:42
roaksoaxcurrently, the POWER_TEMPLATE_DIR allows you to have a sane default, but also allows you to move the templates and place them something else16:42
roaksoaxand I think that's how it should be designed16:42
roaksoaxthe 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
jtvI 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:44
jtvSeparating the power templates from the power config does make that harder.16:45
roaksoaxjtv: i would be fine having the config reside at the same location of the template16:45
roaksoaxjtv: at the end, the file extension will differ file.{template,config}16:46
jtvThat would simplify it a lot...  technically it's not a "template" but it seems close enough.16:46
roaksoaxyeah16:47
jtvIt 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
roaksoaxyeah16:48
roaksoaxin reality it is a config template16:49
jtvOkay, 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
roaksoaxjtv: yes16:50
jtvGreat.  Thanks.16:51
jtvAnd now I'll be off!16:51
roaksoaxhave a good one16:53
jtvnn16:53
kumquathi 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?17:32
=== kentb is now known as kentb-out

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!