[00:15] <burnbrighter> Can anyone tell me why after juju bootstrapping, it is defaulting always to the same bootstrapping node?  What information related to juju is cached?
[00:15] <burnbrighter> I should elaborate, what information related to juju is cached/stored by MAAS or Cobbler?
[00:26] <lifeless> nothing
[00:26] <lifeless> they are separate layers
[00:26] <lifeless> maas doesn't randomise node selection though
[00:27] <burnbrighter> I just asked the question over on the juju side and they said it was maas? :)
[00:28] <lifeless> doing the node choice, yes.
[00:28] <lifeless> but not remembering that its a specific way
[00:33] <burnbrighter> is node choice information cached/stored?
[00:34] <burnbrighter> ok, I see what you are saying - no its not
[00:34] <burnbrighter> why is the same node getting chosen each time then?
[00:34] <burnbrighter> its not the first node that gets bootstrapped
[00:35] <burnbrighter> that's what one would logically expect if the information isn't cached
[01:06] <lifeless> burnbrighter: lowest mac address perhaps ?
[09:41] <rvba> roaksoax: I've tested your package on precise.  The application loads fine, no signe of a wsgi error.
[09:44] <rvba> s/signe/sign/
[13:01] <smoser> roaksoax, looks like jeroen approved.
[13:03] <smoser> roaksoax, ping.
[13:19] <allenap> roaksoax: Want to talk about setup.py at some point?
[13:28] <roaksoax> smoser: pong
[13:28] <roaksoax> allenap: sure give me a few minutes
[13:28] <roaksoax> rvba: yeah.. that means something is screwed in my system then
[13:29] <rvba> roaksoax: seems so.  I've done the test on a brand new canonistack precise instance.
[13:29] <roaksoax> rvba: ok awesome, It failed for me to on a canonicastack, but then worked so something on my system is screwing it for sure
[13:29] <roaksoax> Daviey: i'm ready when you are
[13:36] <roaksoax> rvba: ok so I had to manually ship the enums.js cause building it buildseverything first apparently and gets stuff from pypi it seems
[13:40] <rvba> roaksoax: I guess that's all right for now, just to get us going.  allenap wants to change how we build things.
[13:41] <roaksoax> rvba: hehe yeah it is necessary for some part
[13:41] <roaksoax> allenap: ok so i'm all yours
[13:41] <roaksoax> allenap: I agree that what setup.py is doing now is good, though I personally believe it should build everything (or almost everythin) this way a makefile is not shipped
[13:41] <allenap> roaksoax: Okay, now I need a few minutes :) rvba, roaksoax: want to talk at 1400 UTC?
[13:42] <rvba> Ok.
[13:42] <allenap> Thanks.
[13:42] <roaksoax> sounds good :)
[14:02] <allenap> roaksoax, rvba: I've invited you to a hangout, https://plus.google.com/hangouts/_/30bec8fa14bb528af4c54648cfc5df6003d80c21?authuser=0&hl=en-GB
[14:30] <Daviey> roaksoax: i have a call now
[14:31] <roaksoax> allenap: while you look into getting the enums.js being installed, I can look into installing other files I install manually on packaging
[14:31] <roaksoax> Daviey: ok, let me know when you free to talk then :)
[14:31] <smoser> roaksoax, ok. so i'm still confused about how your maas-celeryd.conf job works.
[14:31] <allenap> roaksoax: Do you mean you'll fix lp:maas for us? :)
[14:31] <smoser> obviously i'm an idiot.
[14:31] <smoser> everyone knows that.
[14:32] <smoser> but i do not think it is PYTHONPATH that is going to get the config found.
[14:32] <smoser> (grep PYTHONPATH from packaging branch shows only the maas executable. and the maas user doesn't even have a home directory, so its not something there)
[14:32] <roaksoax> rvba: can you explain us how exactly celery works and how come it ends up sourcing the config file from /usr/share/maas?
[14:33] <rvba> roaksoax: well, celery simply does "import celeryconfig".
[14:33] <rvba> Whatever is one the path gets loaded.
[14:35] <roaksoax> allenap: I'll fix setup.py to install those files I manually install from packaging, such as: txlongpoll.yaml or pserv.yaml, etc
[14:35] <roaksoax> smoser: ^^
[14:35] <allenap> \o/
[14:36] <rvba> s/one/on/
[14:36] <smoser> rvba, 'path' as in PYTHONPATH ?
[14:36] <rvba> smoser: Yes
[14:36] <smoser> then i dont understand how that job is going to do this.
[14:36] <roaksoax> smoser: the job starts the daemon, which imports whatever is in the path
[14:37] <rvba> fwiw that's how we run it on a dev instance: http://paste.ubuntu.com/1066125/
[14:37] <smoser> yes. and there is no special PYTHONPATH for that job
[14:37] <smoser> i can only think that the upsart job is busted then.
[14:42] <roaksoax> smoser: maybe so, I haven't thought of that :)
[14:43] <roaksoax> smoser: I just assumed that celeryd will import from /usr/share/maas
[14:43] <roaksoax> smoser: the same way maas imports its config form there
[14:45] <roaksoax> allenap: i.e. http://paste.ubuntu.com/1066136/
[14:45] <roaksoax> err e.g.
[14:58] <smoser> roaksoax, so i was hoping that you could just explicitly pass it the path to the file to load
[14:58] <smoser> but it appears '--config /etc/maas/celeryconfig.py' doesnt work
[14:58] <smoser> so unfortunately, it seems that you will have to set PYTHONPATH to include /etc/maas
[14:58] <smoser> which seems stupid, to be honest
[14:58] <rvba> smoser: yeah, that would be much more clean, but unfortunately celeryd does not support it.
[14:59] <smoser> as it would then have implications on any python that runs from celeryd or subproceses
[15:00] <smoser> rvba, is this 'celeryconfig.py' actually a config file?
[15:00] <smoser> ie, would you ever expect for it to be modified by a user?
[15:00] <roaksoax> smoser: i'll include /usr/share/maas to PYTHONPATH
[15:00] <smoser> because if not, we shouldn't put it in /etc/
[15:00] <smoser> roaksoax, but that will have the same implications.
[15:00] <smoser> if its not a config file, then lets not put it in /etc/
[15:00] <smoser> and if it is a config file
[15:01] <rvba> smoser: it's a config file indeed.
[15:01] <smoser> rvba, really?
[15:01] <smoser> what would be changed?
[15:01] <smoser> i'm reading http://paste.ubuntu.com/1066166/
[15:01] <rvba> smoser: I assure you :).  As weird as it may sound.
[15:01] <smoser> and it doesn't seem like anything would be changed.
[15:02] <smoser> or, if the user had to change something, it would make sense to ake those chagnes in
[15:02] <smoser> 'user_maasceleryconfig'
[15:02] <smoser> but i admit to not understanding anything.
[15:02] <rvba> Yeah, same trick we used for the django settings file.
[15:02] <smoser> so this one is not a config file
[15:02] <smoser> but 'user_maasceleryconfig' is
[15:02] <smoser> ?
[15:02] <smoser> no?
[15:02] <rvba> Depends what you call a config file I guess.  This configures how celery should work.
[15:03] <rvba> e.g. we want it to work with "CELERY_ACKS_LATE = True".
[15:03] <rvba> That's in that file.
[15:03] <smoser> ok. i'llbuy that.
[15:03] <smoser> so, generally, though, i tihnk it is a bad idea to put either /usr/share/maas or /etc/maas into PYTHONPATH
[15:03] <smoser> would not you agree?
[15:04] <rvba> I don't.  /usr/share/maas contains the Django project.
[15:04] <smoser> so then that makes more sense.
[15:04] <rvba> Err.
[15:04]  * rvba checks.
[15:05] <roaksoax> rvba: yes, usr/share/maas contains the project
[15:05] <rvba> No, /usr/share/maas/maas contains the project.
[15:06] <roaksoax> rvba: usr/share/maas contains the 'maas' project  :)
[15:07] <rvba> Ah, right. /usr/share/maas/maas *is* the project.
[15:09] <smoser> roaksoax, so in the upstart job, we modify the environment to contain PYTHONPATH=/usr/share/maas
[15:09] <smoser> you dont actually have to worry about appending to pythonpath, becauase when upstart runs the job its not going to have any
[15:09] <smoser> (ie, you dont have to PYTHONPATH=${PYTHONPATH:+:${PYTHONPATH}}
[15:09] <smoser> )
[15:19] <roaksoax> smoser: ok ;)
[15:29] <roaksoax> smoser: however, is it possible to set pythonpath in the upstart job?
[15:30] <smoser> well, you could do it 2 ways:
[15:30] <smoser> exec env PYTHONPATH=... celeryd ...
[15:30] <smoser> or add
[15:30] <roaksoax> env PYTHONPATH='/usr/share/maas/'
[15:30] <roaksoax> export PYTHONPATH
[15:30] <roaksoax> ?
[15:31] <Daviey> smoser: How did the config get in the python path?
[15:31] <smoser> env PYTHONPATH=....
[15:31] <smoser> as part of the upstart job
[15:31] <smoser> Daviey, it did not.
[15:31] <Daviey> .. i happened to discuss it with smoser earlier... i was confused aswell
[15:32] <Daviey> smoser: so how did it work?
[15:32] <smoser> roaksoax, you'll see other examples in your /etc/init/*.conf of 'env'
[15:32] <smoser> oh.
[15:32] <smoser> its awesome.
[15:32] <smoser> Daviey,
[15:32] <smoser> celery doesn't fail if it doesnt find a config file
[15:32] <smoser> it just keeps running.
[15:32] <smoser> (it does warn)
[15:33] <smoser> http://paste.ubuntu.com/1066217/
[15:34] <Daviey> ahh
[15:34] <roaksoax> rvba: would it make sense to rename maas_local_settings_sample.py to maas_local_settings.py so it gets installed by setup.py?
[15:35] <smoser> celeryd really should have *some* way to pass path to a thing to load.
[15:35] <Daviey> it does...
[15:35] <rvba> roaksoax: I've got no problem with that at all.  That file is only there to be used by the package.
[15:36] <Daviey> smoser: you can declare from the cmd line
[15:36] <smoser> Daviey, it takes a --config argument, yes.
[15:36] <roaksoax> smoser: I hit that too, but when I symlinked from etc/maas to /usr/share/maas, the warning was gone! that's why I assumed it picked up the config: http://pastebin.ubuntu.com/1066222/
[15:36] <smoser> and then it tries to load that thing by essentially 'import <that-string>'
[15:37] <smoser> but if that-string is not in PYTHONPATH, it doesn't work.
[15:37] <smoser> (and you can't pass it a full path)
[15:37] <smoser> roaksoax, i don tunderstand how that could possibly work
[15:37] <smoser> do you?
[15:39] <roaksoax> smoser: I don't that's exactly why it seems strange to me why celery works
[15:39] <roaksoax> smoser: that';s why I assu,med it sourced that path
[15:39] <roaksoax> smoser: you are welcome to install the package from PPA and see it for yourself
[15:41] <roaksoax> rvba: ok cool then
[15:41] <smoser> roaksoax, you didn't see the error because it only goes to stderr
[15:41] <smoser> it doesn't go to the log
[15:41] <smoser> (interestingly)
[15:42] <smoser> and upstart jobs stderr is going nowwhere.
[15:43] <roaksoax> smoser: anywyas, it makes no sense to continue argueing about this cause I already applied that to the upstart job :)
[15:54] <roaksoax> rvba: https://code.launchpad.net/~andreserl/maas/maas_rename_settings_file.py/+merge/112800 please :)
[15:55] <rvba> Done.
[15:55] <rvba> :)
[15:55] <roaksoax> rvba: thank you !
[16:37] <roaksoax> allenap: still around?
[16:54] <allenap> roaksoax: Not really. Is it urgent?
[16:55] <roaksoax> allenap: yes and no, but if you could quickly review https://code.launchpad.net/~andreserl/maas/maas_setup_data_files/+merge/112810 i'll be gratefull (as will allow me to continue)
[16:56] <allenap> roaksoax: Done, +1 :)
[16:56] <roaksoax> allenap: thanks!
[16:56] <roaksoax> :)
[17:22]  * roaksoax lunch
[19:49] <roaksoax> smoser: would you care to review/approve https://code.launchpad.net/~andreserl/maas/packaging_updates_bzr704/+merge/112837 please?
[19:55] <smoser> approved.
[20:12] <roaksoax> smoser: thanks