[01:43] <mup> Bug #1429680 was opened: keystone charm do not support conf file injection <juju-core:New> <https://launchpad.net/bugs/1429680>
[01:52] <mup> Bug #1429680 changed: keystone charm do not support conf file injection <juju-core:New> <https://launchpad.net/bugs/1429680>
[01:58] <mup> Bug #1429680 was opened: keystone charm do not support conf file injection <juju-core:New> <https://launchpad.net/bugs/1429680>
[06:37] <mattyw> morning all
[07:06] <mattyw> axw, are you still around?
[07:06] <axw> mattyw: hey, yes
[08:36] <dooferlad> morning! o/
[08:38] <dimitern> morning dooferlad
[08:49] <dimitern> dooferlad, how's your new shiny maas? :)
[08:50] <dooferlad> dimitern: not too bad. Unfortunately they don't support AMT and MAAS can get quite confused with WOL.
[08:50] <dooferlad> dimitern: so plenty of pressing power buttons.
[08:51] <dooferlad> dimitern: though I did get some useful debugging done on Friday with them :-)
[08:51] <dimitern> dooferlad, ah, right
[08:51] <voidspace> morning all
[08:51] <dimitern> hey voidspace! welcome back :)
[08:51] <dooferlad> voidspace! Welcome back!
[08:51] <TheMue> morning o/
[08:52] <voidspace> dimitern: dooferlad: TheMue: morning :-)
[08:53] <dimitern> dooferlad, I managed to get maas installed on an old i386 P4 box and added my 2 nucs in it
[08:54] <dooferlad> dimitern: great!
[08:54] <dimitern> dooferlad, it works - but I have mixed success with amt - it works like 50% of the time
[08:55] <dimitern> dooferlad, my goal is to have openstack installed on top of that and share it with you guys - maas is already visible at http://kubrik.us.to:8888/MAAS/
[08:55] <dimitern> dooferlad, but to expose the nodes behind it a bit more networking needs to happen
[08:57] <dooferlad> dimitern: heh, I know the feeling!
[09:00] <dimitern> morning, TheMue, I'm omw
[09:00] <TheMue> dimitern: /me too
[10:06] <perrito666> morning
[10:14] <TheMue> perrito666: heya
[10:15]  * perrito666 needs to update the fw on his samsung evo 840 and notices the first step requires a ... DOS bootable usb
[10:28] <voidspace> yay, powercut over
[10:28] <voidspace> dimitern: ping
[10:29] <dimitern> voidspace, hey, nice!
[10:29] <dimitern> voidspace, just in time of our 1:1 :)
[10:29] <voidspace> hah, ok
[10:29] <voidspace> dimitern: omw
[10:50] <mup> Bug #1429790 was opened: juju debug-hooks not working when tmux not installed <juju-core:New> <https://launchpad.net/bugs/1429790>
[11:10] <voidspace> dimitern: oh, I forgot to mention - I ordered a new laptop
[11:10] <voidspace> dimitern: so I will be running Ubuntu native at the Nuremberg sprint
[11:10] <dimitern> voidspace, nice!
[11:10] <dimitern> voidspace, not macbook ?
[11:10] <voidspace> dimitern: Dell XPS 15 - quad core i7, 16Gb ram
[11:10] <voidspace> dimitern: no :-)
[11:11] <dimitern> voidspace, sweeet!
[11:11] <voidspace> dimitern: although I will need to keep it to sync with my iphone
[11:11] <voidspace> dimitern: I have an Ubuntu phone on order too
[11:11] <voidspace> dimitern: if it's good enough to use as a main phone maybe I can ditch the iphone too...
[11:11] <dimitern> voidspace, I have my eye on that same model - will need to replace my current one in october
[11:11] <voidspace> dimitern: I got a refurb one for £1000
[11:12] <dimitern> voidspace, ah, that's a bit tricky - last time I tried to replace my main phone with ubuntu it wasn't quite usable - mostly due to the battery running out in a couple of hours
[11:12] <voidspace> dimitern: right, we'll see
[11:13] <voidspace> dimitern: I'll *probably* go to Android as having a good camera is important to me
[11:13] <voidspace> dimitern: but with a camera, a browser and maps I can do most things
[11:13] <dimitern> voidspace, I'll be interested to hear about your experience with the ubuntu phone once you had it for a while
[11:13] <voidspace> dimitern: apparently the google maps *web app* works pretty well with Ubuntu phone
[11:13] <voidspace> dimitern: and I *presume* they've sorted battery life as they wouldn't be able to do a public release like that
[11:13] <dimitern> voidspace, I hope so :)
[11:18] <voidspace> Just discovered why the power cut. Someone posted some photos to facebook.
[11:18] <voidspace> "The tipper lorry, having dumped his load of topsoil (on the wrong side of the road by the look of it) drove forward with the tipper still up and pulled down a power cable."
[11:18] <dimitern> wow!
[11:19] <dimitern> voidspace, priceless *lol*
[11:21] <voidspace> yeah, nice :-)
[12:41]  * TheMue steps out for a moment, bbiab
[13:18] <mup> Bug #1429853 was opened: unit test TestInstallCommandsShutdown...initSystemSuite fails <ci> <gccgo> <ppc64el> <regression> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1429853>
[13:22] <TheMue> back
[13:35]  * dimitern steps out for ~1.5h
[14:00] <mup> Bug #1429864 was opened: juju should support putting units/services into WIP/frozen mode <juju-core:New> <https://launchpad.net/bugs/1429864>
[14:12] <sinzui> ericsnow, I think bug 1429853 relates to your commit.
[14:12] <mup> Bug #1429853: unit test TestInstallCommandsShutdown...initSystemSuite fails <ci> <gccgo> <ppc64el> <regression> <test-failure> <juju-core:In Progress by ericsnowcurrently> <https://launchpad.net/bugs/1429853>
[14:13] <ericsnow> sinzui: oh, it definitely does :)
[14:13] <ericsnow> sinzui: I thought I was being careful about map order in tests this time :(
[14:13] <sinzui> ericsnow, I am making a snapshot of the vivid-slave before trying to switch to systemd. we have the package, but I need to mess with the boot options to make it work';
[14:14] <ericsnow> sinzui: won't the new images coming out today do that for you?
[14:14] <sinzui> ericsnow, yes, but that requires me to schedule the build of a new slave
[14:14] <ericsnow> sinzui: ah
[15:02] <ericsnow> could I get a quick review on http://reviews.vapour.ws/r/1105/
[15:02] <ericsnow> it fixes the CI blocker
[15:03] <mgz> ericsnow: lgtm
[15:04] <ericsnow> mgz: thanks
[15:12] <mup> Bug #1429680 changed: keystone charm do not support conf file injection <keystone (Juju Charms Collection):New> <https://launchpad.net/bugs/1429680>
[15:17] <ericsnow> mgz: I'm not sure this worked right: http://juju-ci.vapour.ws:8080/job/github-merge-juju/2426/console
[15:17] <ericsnow> mgz: it passed without actually running any tests?
[15:18] <mgz> ericsnow: looking
[15:18] <mgz> yerp, that's terrible
[15:19] <mgz> well, at least it was your change and it's a nice tiddly one that's not relevent for the lander
[15:20] <mgz> jesse's also had the same thing
[15:20] <ericsnow> mgz: yep :)
[15:20] <ericsnow> mgz: perhaps it's related to the grub messages?
[15:21] <ericsnow> mgz: probably not
[15:21] <mgz> yeah, it's the run-unit-test script not erroring out when it should
[15:21] <ericsnow> mgz: ah
[15:22] <mgz> I have a short-term fix and a better longer one
[15:25] <ericsnow> mgz: cool
[15:25] <ericsnow> mgz: thanks for jumping on that
[15:25] <ericsnow> wwitzel3: you see that email about HA?
[15:29] <ericsnow> mgz: why does the publish-revision job take so long?
[15:31] <mgz> ericsnow: okay, updated the ami, which is the quick fix
[15:32] <mgz> ericsnow: does quite a bit of work... but does seem to have been taking about an hour for a while
[15:33] <ericsnow> mgz: no problem, just curious (since it's the blocker for all the other release jobs)
[15:34] <mgz> ericsnow: it may be worth trying to speed up, I've not looked into where the time is spent
[15:35] <ericsnow> mgz: if you have time for it :)
[15:35] <mgz> we have to build on several platforms, may be more parellisable
[15:36] <ericsnow> mgz: when trying to fix a failed CI test any improvement to the total time-to-test-comletion is super helpful
[15:44] <wwitzel3> ericsnow: looking now
[15:45] <ericsnow> wwitzel3: thanks!
[15:45] <wwitzel3> ericsnow: what list?
[15:45] <ericsnow> wwitzel3: no list
[15:46] <wwitzel3> ericsnow: don't see it
[15:46] <ericsnow> wwitzel3: the "Nate out today" thread
[15:49] <wwitzel3> ericsnow: I see it, thanks
[15:54] <alexisb> wwitzel3, btw, thank you for the extra hours on that oil bug
[15:55] <wwitzel3> alexisb: sorry I couldn't get it figured out, I'm convinced that it is related to the power script not resulting in a clean shutdown.
[16:36] <ericsnow> sinzui: am I okay marking bug 1429853 as "fix released" since the failing CI test just passed?
[16:36] <mup> Bug #1429853: unit test TestInstallCommandsShutdown...initSystemSuite fails <ci> <gccgo> <ppc64el> <regression> <test-failure> <juju-core:Fix Committed by ericsnowcurrently> <https://launchpad.net/bugs/1429853>
[16:38] <sinzui> ericsnow, we really should wait for all the run-unit-tests to pass
[16:38] <sinzui> I am waiting for run-unit-tests-precise-i386 to complete
[16:38] <ericsnow> sinzui: okay; I'm always just antsy to unblock CI :)
[16:39] <sinzui> ericsnow, i understand. I want to avoid the 32 days and 77 commits case were fixed blockers, but never actually got a passing revision
[16:40] <ericsnow> sinzui: agreed
[17:02] <sinzui> dimitern, do you have a moment to review http://reviews.vapour.ws/r/1018/
[17:03] <dimitern> sinzui, sure, looking
[17:04] <dimitern> sinzui, it seems it has been submitted already
[17:06] <sinzui> dimitern, sorry, wrong review, me looks
[17:06] <mup> Bug #1429853 changed: unit test TestInstallCommandsShutdown...initSystemSuite fails <ci> <gccgo> <ppc64el> <regression> <test-failure> <juju-core:Fix Released by ericsnowcurrently> <https://launchpad.net/bugs/1429853>
[17:08] <sinzui> dimitern, review board might be lagging. https://github.com/juju/juju/pull/1776 is what I am working with
[17:09] <dimitern> sinzui, LGTM
[17:09] <sinzui> thank you dimitern
[17:14] <mattyw> katco, ping?
[17:14] <katco> mattyw: hello!
[17:44] <sinzui> dimitern, TheMue: does bug 1428430 need to be fixed before we branch 1.23
[17:44] <mup> Bug #1428430: AllWatcher does not remove last closed port for a unit, last removed service config <api> <juju-core:Triaged by themue> <https://launchpad.net/bugs/1428430>
[17:45] <TheMue> sinzui: I'm on it, when exactly will you branch?
[17:46] <sinzui> TheMue, I was planning to do it when the current revision passes because I thought all the bugs for 1.23-beta1 were fixed. I didn't see the new bug
[17:47] <sinzui> TheMue, I think the pressure is from core developers wanting to merge 1.24 work. I can branch from any commit
[17:48] <mup> Bug #1427149 changed: Tests require predictable map ordering <ci> <regression> <test-failure> <juju-core:Fix Released by dooferlad> <https://launchpad.net/bugs/1427149>
[17:48] <TheMue> sinzui: as I said, I'm on it and I hope I will have it in a few moments. fighting a bit with the test
[17:49] <dimitern> sinzui, TheMue, it's ok to move that bug for 1.24, it's not critical
[17:49] <sinzui> TheMue, okay. I am not rushing. I have the 1.22-beta5 release to do
[17:49] <dimitern> TheMue, if you manage, ok, if not - no problem
[17:49] <TheMue> dimitern: but I want to *lol*
[18:06] <mup> Bug #1404397 changed: charm actions.yaml simplification breaks master tests <actions> <charm> <tech-debt> <juju-core:Fix Released by binary132> <https://launchpad.net/bugs/1404397>
[18:06] <mup> Bug #1415961 changed: juju gives up on bootstrapping with 'bootstrap instance started but did not change to Deployed state' <bootstrap> <maas-provider> <oil> <juju-core:Fix Released by dooferlad> <juju-core 1.22:Fix Released by wallyworld> <https://launchpad.net/bugs/1415961>
[18:06] <mup> Bug #1416928 changed: juju agent using lxcbr0 address as apiaddress instead of juju-br0 breaks agents <api> <lxc> <network> <juju-core:Fix Released by dooferlad> <juju-core 1.21:Fix Released by dimitern> <juju-core 1.22:Fix Released by dooferlad> <https://launchpad.net/bugs/1416928>
[18:06] <mup> Bug #1417594 changed: failure to retrieve the template to clone: lxc container with 1.22 beta2 <lxc> <oil> <juju-core:Fix Released by wallyworld> <juju-core 1.22:Fix Released by wallyworld> <https://launchpad.net/bugs/1417594>
[18:06] <mup> Bug #1420049 changed: ppc64el - jujud: Syntax error: word unexpected (expecting ")") <deploy> <openstack> <regression> <uosci> <juju-core:Fix Released by axwalk> <juju-core 1.22:Fix Released by axwalk> <https://launchpad.net/bugs/1420049>
[18:06] <mup> Bug #1423036 changed: precise services cannot be deployed (again) <ci> <precise> <regression> <ubuntu-cloud-archive:Fix Released> <juju-core:Fix Released by wallyworld> <juju-core 1.22:Fix Released by wallyworld> <https://launchpad.net/bugs/1423036>
[18:06] <mup> Bug #1425435 changed: juju-deployer/jujuclient incompatibility with 1.21.3 <api> <cts> <network> <oil> <openstack> <orange-box> <regression> <uosci> <juju-core:Fix Released by themue> <juju-core 1.22:Fix Released by themue> <https://launchpad.net/bugs/1425435>
[19:06] <marcoceppi> sinzui: can we get this elevated to a critical? lp1424069
[19:07] <sinzui> marcoceppi, I can raise it in the release meeting in 2 hours
[19:07] <marcoceppi> sinzui: thanks, it's a regression still present in trunk
[19:07] <marcoceppi> tested again as of Friday
[19:07] <marcoceppi> by aisrael
[19:07] <sinzui> marcoceppi, I added the tag to emphasis regression
[19:15] <marcoceppi> sinzui: I was under the impression that critical severity level was to mark regressions, but I don't have a firm understanding of how the triaging works
[19:16] <sinzui> marcoceppi, it is but Core have negotiated an ambigous High to NOT fix regressions immediately to ensure they can keep merging
[19:17] <marcoceppi> sinzui: that sounds lame to me ;)
[19:17] <sinzui> marcoceppi, critical means stop, fix this now. I think your issue is critical, but I need management to agree
[19:17] <marcoceppi> sinzui: ack, thanks for the clarification
[19:18] <marcoceppi> arosales: ^^
[19:27] <arosales> well it should be community input, but I would say a regression of this nature that could leave a user without a way to fix a issue is a big deal
[19:27] <arosales> marcoceppi:  sinzui ^
[19:28] <sinzui> arosales, no one disagrees about fixing it. the issue is in trunk, not a release. Core will fix it for a release
[19:28] <sinzui> arosales, and as a stakeholder, you have every right to say fix now
[19:31] <arosales> marcoceppi: aisrael: can you guys sync up with sinzui and folks here on the nature of the problem and when a fix could is needed, perhaps the next release going out is sufficient
[19:32] <sinzui> arosales, marcoceppi aisrael: as you are running master, you get the fix as soon as it is merged.
[19:33] <sinzui> arosales, marcoceppi aisrael: as Core are focused on releasing 1.22.0 and stablising 1.23 for a beta release, your bug will be fixed soon, core is looking for an engineer now
[19:34] <aisrael> sinzui: arosales: marcoceppi: ack, I'll re-test as soon as I see the merge hit.
[19:34] <marcoceppi> sinzui: I think this exists in 1.23, is there an alpha out?
[19:35] <sinzui> marcoceppi, no. no releases until we cut 1.22.0
[19:35] <marcoceppi> sinzui: ack
[19:36] <arosales> sinzui: thanks for the help
[19:39] <alexisb> katco, perrito666, cherylj, ericsnow, any of you have spare cycles (its ok to say no, I am just looking for available folks)?
[19:39] <ericsnow> alexisb: probably not today
[19:39] <katco> alexisb: i'm in the middle of trying to push something up, but if it's important you can intervene :)
[19:39] <perrito666> wow, that took my brain a lot to process you where not asking me for a byke
[19:39] <perrito666> bike
[19:39] <cherylj> alexisb: I have some time.
[19:39] <perrito666> alexisb: sorry, nope
[19:39] <ericsnow> alexisb: or until vivid/systemd settles down :)
[19:40] <alexisb> cherylj, are you comfortable looking at a regression bug?
[19:40] <cherylj> alexisb: I can try!
[19:40] <alexisb> maybe if katco can provide some backup
[19:40] <alexisb> ok can you please take a look at 1424069
[19:40] <cherylj> alexisb: looking...
[19:40] <katco> https://bugs.launchpad.net/juju-core/+bug/1424069
[19:40] <mup> Bug #1424069: juju resolve doesn't recognize error state <regression> <resolved> <juju-core:Triaged> <https://launchpad.net/bugs/1424069>
[19:40] <alexisb> perrito666, heh
[19:41] <alexisb> perrito666, i will make sure to use lots of common American metaphors for you from now on
[19:41] <perrito666> alexisb: that is how you get a bike on the mail
[19:41] <perrito666> be warned
[20:01] <alexisb> thumper, just so you know I volunteered cherylj for a bug that will soon be marked as critical
[20:01] <alexisb> she can fill you in on the details
[20:01] <alexisb> o and thumper happy tuesday :)
[20:03] <perrito666> that was evil
[20:20] <TheMue> anyone free to review http://reviews.vapour.ws/r/1106/, it's the fix for #1428430
[20:20] <mup> Bug #1428430: AllWatcher does not remove last closed port for a unit, last removed service config <api> <juju-core:Triaged by themue> <https://launchpad.net/bugs/1428430>
[20:31] <menn0> katco: ping
[20:31] <katco> menn0: hey there menn0!
[20:31] <menn0> katco: hey hye
[20:31] <menn0> hey even
[20:31] <menn0> katco: i'm probably going to create a feature test soon and wanted to ask you some questions
[20:31] <katco> menn0: awesome!
[20:32] <menn0> katco: looking at the leadership feature test i noticed that the setup does a lot of work that seems to double up on what AgentSuite (embedded by the feature test's suite) can do
[20:32] <menn0> katco: in terms of setting up the machine agent
[20:32] <menn0> katco: i'm guessing there's some parts that didn't work the way you needed them to. do you remember what?
[20:32] <katco> menn0: right; that is a bit of an anachronism
[20:33] <menn0> katco: i'm hoping to short cut any lesson you learned
[20:33] <katco> menn0: i believe it was more that eventually we were wanting to obviate the agent tests' full-stack testing
[20:33] <katco> menn0: iirc, the agent suite was just doing way more than the leadership functionality needed
[20:34] <menn0> katco: ok so, it was more a matter of starting afresh for the feature tests?
[20:34] <katco> menn0: yeah
[20:34] <katco> menn0: i.e. make the feature tests as linear and clean as possible
[20:34] <katco> menn0: no chain of suites
[20:35] <menn0> katco: cool. I just wanted to be sure I wasn't missing something
[20:35] <katco> menn0: nothing that at least i can remember :)
[20:35] <menn0> katco: I think my feature test (for logging to the db) will require a similar setup to the leadership feature test
[20:35] <menn0> katco: you're not against sharing test setup within the featuretest package right?
[20:36] <katco> menn0: personally? i don't like that pattern. it makes the tests very brittle and hard to understand
[20:36] <katco> menn0: but i think that's probably up to the developer
[20:37] <katco> menn0: i am a big fan of very dumb, linear, tons of code tests
[20:37] <menn0> katco: i see where you're coming from but part of me doesn't like copying and pasting all that code to set up the machine and machine agent
[20:37] <katco> menn0: because when i'm reading a test, it's telling me a story, and i don't want to learn a 2nd way to interact with juju
[20:37] <katco> menn0: right, that's the inverse argument
[20:38] <katco> menn0: at the very least, if we wanted to de-dupe code
[20:38] <menn0> katco: yeah I get that. especially when there's lots of alternate ways of interacting with juju in different test suites
[20:38] <katco> menn0: i would say pull functionality out into functions, and call the same functions from multiple suites
[20:38] <katco> menn0: and then you don't have to chain suites
[20:39] <menn0> menn0: I like that approach. easier to understand. I've been doing that a bit recently in some apiserver tests, although there it's a mix of helper funcs and shared suites.
[20:39] <menn0> katco: ^^^ (I didn't mean to talk to myself :))
[20:39]  * menn0 needs more coffee
[20:40] <katco> menn0: haha :)
[20:40] <menn0> katco: well i'll see how the db logging feature tests pan out. i'll aim to keep wha I do in line with the existing approach.
[20:40] <katco> menn0: so that's my take on things. you are awesome, and your code will be as such :)
[20:41] <menn0> katco: thanks but that's not guaranteed :)
[20:41] <menn0> katco: thanks for the chat. very helpful.
[20:41] <katco> menn0: happy to help!
[20:47] <katco> for anyone working with restful services + wadl files in go: https://github.com/katco-/wadl2go
[21:12]  * katco away for a bit
[21:40] <alexisb> cherylj, can you please assign yourself to lp 1424069?
[21:41] <voidspace> right, way past EOD
[21:41] <voidspace> g'night all
[21:42] <cherylj> alexisb: sure
[21:43] <DaveJ__> Hi - can anyone tell me if JuJu supports CentOS/RedHat guests yet?  I looked about a year ago and it didn't appear ready yet, but can't find any updated info
[21:45] <bogdanteleaga> DaveJ_: not yet, but we're working on it right now
[21:49] <DaveJ__> bogdantelega: Thanks - is there any kind of ETA for that feature? Or is there even a way I can build the packages and try it out myself?
[21:50] <DaveJ__> Our product currently runs on CentOS, and I'd really like to try and deploy it as set of charms
[21:50] <bogdanteleaga> DaveJ_: well currently we're working on the userdata part: the codebase only supports apt for linux packages and yum is needed on centos
[21:51] <bogdanteleaga> DaveJ_: we want to finish it until the end of the month
[21:51] <bogdanteleaga> DaveJ_: there might still be some broken functionality at that point but it should be usable to some extent
[21:51] <DaveJ__> bogdanteleaga: No worries, I'm not afraid to get into the code and work around any issues.
[21:51] <DaveJ__> Even if I can get a basic prototype working
[21:52] <DaveJ__> bogdanteleaga:  Anywhere I can track the progess?  End of the month doesn't seem that bad
[21:53] <bogdanteleaga> DaveJ_: look for centOS related pull requests on github
[21:54] <bogdanteleaga> DaveJ_: https://github.com/juju/juju/pull/1759
[21:54] <bogdanteleaga> DaveJ_: this is a start, but there's more to be done
[21:58] <DaveJ__> bogdanteleaga: Understood. Thanks for the info
[22:58] <mup> Bug #1430049 was opened: unit "ceph/0" is not assigned to a machine when deploying with juju 1.22-beta5 <juju-core:New> <https://launchpad.net/bugs/1430049>
[23:17] <davecheney> hr.canonical.com is so stupif
[23:17] <davecheney> it just let me enter a personal objective "gain the power of flight"
[23:17] <davecheney> and back date it to the day i was born
[23:17] <katco> wallyworld_: anastasiamac: axw: i think i keep freezing
[23:17] <axw> katco: last thing I heard from you was "our dogs"
[23:17] <wallyworld_> katco: sprry, we hung up on you
[23:18] <axw> or maybe "out dogs"
[23:18] <katco> "out dogs" ;)
[23:18] <wallyworld_> lol
[23:18] <anastasiamac> :D
[23:18] <davecheney> what's out dog ?
[23:18] <katco> davecheney: it's kind of like up dog?
[23:18] <axw> out, dogs
[23:18] <anastasiamac> who let the dogs out
[23:18] <davecheney> ... wait a second !
[23:19] <katco> ok off to dinner... tc all!
[23:19] <axw> enjoy
[23:23] <anastasiamac> menn0: thumper: I was reviewing http://reviews.vapour.ws/r/1107/ but it was stamped and merged under me :D u r fast...
[23:24] <thumper> :)
[23:24] <thumper> sorry
[23:24] <thumper> davecheney: heh
[23:44] <cherylj> perrito666: are you still around?
[23:56] <cherylj> Is there anyone else around who worked on the Unit Agent stuff?
[23:59] <anastasiamac> cherylj: maybe just ask a question - m sure that someone may be able to help :D
[23:59] <wallyworld_> cherylj: what did you want to know about unit agent?