[00:52] <bigjools> roaksoax: I approved your packaging change
[00:53] <bigjools> can I land it as-is?
[01:10] <roaksoax> bigjools: cool thanks
[01:10] <bigjools> roaksoax: actually
[01:10] <bigjools> roaksoax: wait
[01:11] <bigjools> I have got so many branches I am getting them mixed up
[01:11] <roaksoax> bigjools: so I created a packaging.precise.sru which is what was in quantal at the time, plus your merges
[01:11] <roaksoax> bigjools: or your change to the upstart job
[01:11] <roaksoax> bigjools: i'll get that updated :)
[01:11] <bigjools> we have not backported the celery import-pxe-files
[01:12] <roaksoax> bigjools: ok, no harm since it was only a 1 line addition
[01:12] <roaksoax> to the sudoers file for maas
[01:12] <bigjools> roaksoax: no I mean your https://code.launchpad.net/~andreserl/maas/quantal_packaging_updates/+merge/135264
[01:12] <bigjools> it was more than that, 167 lines of diff :)
[01:12] <roaksoax> bigjools: the change for that is: debian/extras/99-maas-sudoers
[01:13] <roaksoax> bigjools: the rest, is for maas-cluster-controller shipping maas-import-pxe-files and storing the images
[01:14] <bigjools> roaksoax: none of it is needed
[01:14] <bigjools> I think
[01:15] <bigjools> grar, let me check again
[01:15] <roaksoax> bigjools: hold on, isn't bug #1068843 the one one which the cluster controller has to have the images?
[01:16] <roaksoax> bigjools: so that bug,which i see was backported to the stabilkization branch is where the images are no longer on the region controller and are on the cluster controller
[01:16] <bigjools> roaksoax: right right
[01:16] <bigjools> I am getting two changes mixed up
[01:16] <roaksoax> bigjools: the thing for celery to work, was simply adding permission for the maas user to run maas-import-pxe-files
[01:16] <roaksoax> bigjools: which is a 1 line change
[01:17] <bigjools> roaksoax: yup :)
[01:18] <roaksoax> bigjools: ok, so now
[01:18] <roaksoax> bigjools: i have updated it
[01:18] <roaksoax> :)
[01:18] <roaksoax> bigjools: now, I had to rebase the python-django package because a securoity fix landed in archives
[01:18] <roaksoax> bigjools: and your changes needed to be applied on top of that package
[01:19] <roaksoax> bigjools: now, It would be great if you could open a bug report for each of those patches
[01:19] <bigjools> roaksoax: you already did it? I was about to do it
[01:19] <bigjools> :)
[01:19] <roaksoax> so i can reference the changelog and SRU the package
[01:19] <bigjools> I will file
[01:20] <bigjools> where is your precise packaging branch?  I made a bunch of changes just in the PPA
[01:20] <bigjools> (for maas)
[01:20] <roaksoax> bigjools: awesome, assign them to me and I'll take care of the rest
[01:20] <bigjools> coolio
[01:21] <roaksoax> bigjools: lp:~maas-maintainers/maas/packaging.precise.sru
[01:22] <roaksoax> bigjools: this is the only change i made of top for the packaging: http://bazaar.launchpad.net/~maas-maintainers/maas/packaging.precise.sru/revision/146
[01:22] <roaksoax> in comparison to the quantal one
[01:23] <roaksoax> bigjools: in terms on packaging I didn't see any other change
[01:24] <bigjools> roaksoax: ok I have a *bunch* of changes, it might be best if I just blow your branch away and replace it with mine
[01:24]  * bigjools diffs
[01:24] <roaksoax> bigjools: sure, branch the quantal with the recent changes you just approved and put them on top
[01:24] <roaksoax> bigjools: that way I can make sure what differs from quantal
[01:25] <bigjools> I branched the old precise packaging and changed on top of that
[01:25] <bigjools> since that is the branch that we really want to use, right?
[01:25] <roaksoax> bigjools: uhmmm nope
[01:25] <bigjools> whut?
[01:26] <roaksoax> bigjools:  the quantal branch updates precise -> quantal right?
[01:26] <roaksoax> bigjools: the quantal version is going to be the same as precise
[01:26] <bigjools> the code is the same, the packaging is a fair bit different now
[01:26] <roaksoax> bigjools: it shouldn't be
[01:26] <bigjools> but I see why you're approaching it this way
[01:27] <bigjools> let me diff them, hang on
[01:28] <roaksoax> bigjools: note that when you backport, you use the same package as ubuntu+1, + any singularities that you need to do in that particula release
[01:28] <roaksoax> bigjools: in our case, we are SRU'ing a whole release
[01:28] <bigjools> ok
[01:28] <roaksoax> so the packaging should be the same + changes for precise
[01:28] <roaksoax> bigjools: cause the upgrade path is going to be the same
[01:29] <bigjools> well for reference, here's the diff from my your sru packaging to my sru packaging http://pastebin.ubuntu.com/1373861/
[01:30] <roaksoax> bigjools: yeah, too much complication :)
[01:30] <roaksoax> s/too much complication/too complicated/
[01:30] <bigjools> I have an equally big diff to the quantal branch
[01:30] <bigjools> let's see what I can do
[01:31] <roaksoax> bigjools: the one iuploaded in the PPA, only seemed to have the upstart changes as packaging changes
[01:32] <bigjools> I have changelog and upstart
[01:32] <roaksoax> bigjools: right, I merged your changelog entry for the upstart change
[01:32] <roaksoax> bigjools: and i added all the biuglist we are closing
[01:32] <roaksoax> bigjools: which you partially had
[01:32] <roaksoax> bigjools: there should not be any more changes AFAIK
[01:32] <bigjools> indeed
[01:33] <roaksoax> bigjools: ok so I will rebase packaging.precise.sru with latest fixes
[01:33] <bigjools> roaksoax: looks like your branch is up to date then
[01:35] <bigjools> excellenbt
[01:35] <bigjools> roaksoax: did you rebase the django package already?
[01:35] <roaksoax> bigjools: yes
[01:35] <bigjools> roaksoax: awesome
[01:36] <roaksoax> :)
[01:36] <roaksoax> bigjools: alright, I hope that tomorrow i can at least upload yui3, python-tx-tftp, and django
[01:36] <bigjools> \o/
[01:36] <bigjools> to quantal and precise?
[01:36] <roaksoax> yui3, django to precise
[01:37] <roaksoax> and python-tx-tftp to quantal, and once accepted to precise
[01:37] <bigjools> nice!
[01:37]  * bigjools files bugs
[01:42] <bigjools> roaksoax: 1st one https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/1081388
[01:43] <roaksoax> bigjools: could you also please explain what it does, or "fixes" maas problem
[01:47] <bigjools> roaksoax: any better?
[01:49] <bigjools> roaksoax: 2nd https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/1081391
[01:49] <bigjools> one more to go
[01:52] <bigjools> roaksoax: https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/1081392
[01:52] <bigjools> I can attach patches for reference if you need
[01:52] <roaksoax> bigjools: cool thanks
[01:52] <roaksoax> bigjools: no not really
[01:52] <bigjools> ok
[01:53] <roaksoax> i'll take care of them tomorrow
[01:53] <roaksoax> now, I'm off
[01:53] <roaksoax> have a good day :)
[01:55] <bigjools> roaksoax: excellent, thank you.  Have a good evening!
[04:49] <AskUbuntu> Adding nodes to MAAS server | http://askubuntu.com/q/220049
[09:43] <Nafallo> hi
[09:43] <Nafallo> where in maas can I define my own preseeds? :-)
[09:43] <Nafallo> I need to specify an http proxy for apt in my environment.
[09:52] <bigjools> Nafallo: yes, /etc/maas/
[09:52] <bigjools> edit existing one
[09:56] <Nafallo> can't see one in there?
[09:56] <Nafallo> I'm using Ubuntu 12.10 btw.
[09:56] <Nafallo> so maas=0.1+bzr1269+dfsg-0ubuntu1
[09:57] <bigjools> Nafallo: I have to dash, rvba should be able to point you to the right place
[09:57] <bigjools> but 12.10 already points a proxy at the squid-deb-proxy on the region controller
[09:58]  * bigjools outta here
[09:58] <rvba> Nafallo: the preseeds are in /usr/share/maas/preseeds/
[09:59] <rvba> Nafallo: like bigjools said, you'll see that /usr/share/maas/preseeds/generic already sets the proxy to be the squid-deb-proxy on the region controller
[09:59] <Nafallo> hmm. I guess the alternative is to point squid-deb-proxy to use a proxy then? :-P
[09:59] <Nafallo> cause my maas is on rfc1918 space, and I'm not planning to NAT it.
[10:00] <rvba> Yeah, you can configure that proxy to use a parent proxy.
[10:01] <Nafallo> I think that will be the best option then, cause currently the machines just time out :-)
[10:01] <Nafallo> thanks. I'll test that :-)
[16:23] <rvba> roaksoax: Hi Andres.  Quick question for you, what is the format of the generated /etc/maas/maas_cluster.conf file?  Right now we have only one value in there (MAAS_URL=http://10.98.0.90/MAAS).  Is that guaranteed that it will be key=value\nkey2=value2?
[16:25] <roaksoax> rvba: if you make it so yes
[16:26] <rvba> roaksoax: ok, apparently we simply populate this file manually in the packaging so I've got my answer.
[16:26] <roaksoax> rvba: yep, so you'd need to add a new /sed/ in order to replace the second key=value
[16:26] <rvba> roaksoax: ok, got it,ta
[16:26] <roaksoax> rvba: but that file already comes with one key value, and the value for that key is being replaced
[17:01] <rvba> roaksoax: can you please triage this (pretty critical if you ask me)?  https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1081212 allenap or I will work on a fix for it.
[17:03] <roaksoax> rvba: is this bug present in the archives?
[17:03] <rvba> roaksoax: yes
[17:04] <roaksoax> done
[17:04] <rvba> ta
[17:16] <allenap> roaksoax: Could you do the same for bug 1081660 please?
[17:16] <roaksoax> allenap: sure thing
[17:16] <allenap> Ta.
[17:17] <roaksoax> allenap: weird, that bug didn't happen before
[22:36] <roaksoax> bigjools: howdy! is bug #1081392 not fixed in 1.4/quantal?
[22:45] <bigjools> roaksoax: hi
[22:45] <bigjools> roaksoax: it's already in quantal
[22:45] <bigjools> I only noticed the bug on precise
[22:49] <roaksoax> bigjools: ok cool
[22:53] <bigjools> roaksoax: note that this particular fix is already in upstream 1.3, but I did a patch as that saves worrying about bringing in many changes if upstream is refreshed
[22:54] <roaksoax> bigjools: ok cool
[22:54] <roaksoax> bigjools: yeah we shouldn't have issues for this
[23:18] <bigjools> roaksoax: did you see https://bugs.launchpad.net/bugs/1081660
[23:19] <bigjools> ah you did, you triaged it :)
[23:28] <roaksoax> bigjools: yeah, which i found pretty werid
[23:29] <roaksoax> cause that error never appeared before
[23:29] <roaksoax> so unless someone changed something
[23:30] <roaksoax> bigjools: this is how it handles it: ip=$(ifconfig eth0 | awk '$1 == "inet" { sub("addr:","",$2); print $2; }') && [ -n "${ip}" ] && host=$(dig +short -x $ip)  && host=${host%.}
[23:31]  * bigjools blinks
[23:32] <bigjools> roaksoax: I expect it's a genuine timeout and dig is returning that string
[23:32]  * bigjools reconnecting
[23:35] <roaksoax> bigjools: yeah that might indeed be the issue, though I've never seen it before :/
[23:36] <roaksoax> i can't reproduce it
[23:42] <bigjools> roaksoax: sigstop the dns server?
[23:44] <bigjools> btw I copied all the packages from experimental to testing