[00:07] <mwenning> lazyPower, you still out there?
[00:08] <mwenning> ok, catch you in the morning
[00:10] <marcoceppi> aisrael: yup, cheetah, but do whatever you want
[00:10] <marcoceppi> you like Jinja? use that
[00:24] <mwenning> good night!
[01:28] <aisrael> marcoceppi: ack. Either one will be new to me, but I'll take a poke around and see which one works the best for me.
[12:46] <gnuoy> I'm trying to do juju sync-tools but I'm getting this error http://paste.ubuntu.com/8417850/ . Does that look like a corrupt entry in the tools already uploaded ? And if so how do I see what tools the maas environment already has ?
[12:49] <gnuoy> juju help sync-tools
[12:54] <gnuoy> mgz, sorry to ping you directly but do you know where maas stores its copy of juju-tools ?
[13:11] <marcoceppi> gnuoy: doesn't it go in the blobstore in postgresql that maas exposes?
[13:12] <gnuoy> marcoceppi, that sounds like a distinct possibility, I'll have a look at the database
[13:45] <mgz> gnuoy: that is indeed the case, you can also use the maas cli to inspect
[13:47] <gnuoy> mgz, excellent. I think I'm hitting a bug tbh but the maas cli should help me confirm
[13:48] <gnuoy> mgz, do you know what the maas cli command is ?
[13:50] <gnuoy> mgz, I see files list but no sign of tools http://paste.ubuntu.com/8418226/
[13:57] <lazyPower> sebas5384: i just saw you accepted the invite. o/ how many will be attending?
[13:58] <sebas5384> hey lazyPower, don't know yet
[13:58] <lazyPower> Okie dokie
[13:58] <sebas5384> but I think at least two people
[13:58] <sebas5384> i'm going to the hangout :)
[14:02] <sebas5384> lazyPower: https://plus.google.com/hangouts/_/canonical.com/drupal-aumlet here?
[14:02] <lazyPower> yep
[14:02] <lazyPower> i'm already there
[14:03] <sebas5384> thats wired
[14:03] <sebas5384> ohhh hangout trolling our life again
[14:03] <lazyPower> having an issue joining?
[14:04] <gnuoy> natefinch, sorry to bother you again but does this error http://paste.ubuntu.com/8418336/ with sync'ing tools ring any bells with you ?
[14:05] <natefinch> gnuoy: no bother, it's specifically my job to help ;)
[14:05] <gnuoy> \o/
[14:06] <natefinch> gnuoy: this part looks suspicious: invalid binary version "1.21-alpha1.1--amd64"
[14:06] <gnuoy> agreed
[14:06] <natefinch> like, why --?
[14:06] <gnuoy> natefinch, my guess is a bug in trying to decode the version data embedded in the tools filename
[14:07] <natefinch> ahh, yeah, I think I get it... it's not --   it's -<series>-  ... except series is empty for some reason
[14:08] <natefinch> so, something is failing to parse the series from win2012r2
[14:09] <natefinch> or, it's failing in the process somewhere, since we're not seeing an actual error until it looks for the binary
[14:10] <jamespage> gnuoy, I think we have some of our joined hook conditional processing based on being leader wrong
[14:15] <natefinch> gnuoy: sorry, in a meeting right now, but I can help later today.  in #juju-dev is gsamafira who wrote a lot of the windows support code, and he might be able to help, too.  I pinged him there, but seems like he's AFK right now.
[14:15] <natefinch> gnuoy: what timezone are you in?
[14:15] <gnuoy> uk
[14:15] <gnuoy> utc+1
[14:19] <natefinch> gnuoy: ok, I'm us-east, UTC-4 so, will try to get back before your EOD
[14:19] <natefinch> ahh, there's gsamfira.  gnuoy is having a problem deploying a windows charm: http://paste.ubuntu.com/8418336/
[14:20] <natefinch> noteably: agent-state-info: invalid binary version "1.21-alpha1.1--amd64"    where -- is -<series>-   ... so series is getting set to an empty string at some point
[14:21] <gsamfira> gnuoy: if you look on the state machine, do you see any errors in the logs
[14:21] <gsamfira> something like "could not find tools for"
[14:21] <gnuoy> otp will look in a sec
[14:22] <gsamfira> also, how are you uploading the tools?
[14:22] <gsamfira> nvm
[14:22] <gsamfira> sync-tools
[14:31] <gnuoy> gsamfira, with sync-tools (I included the sync-tools command in the pastebin)
[14:31] <gsamfira> gnuoy: can you try the latest master of juju. You seam to be using an older version  (it should be alpha2). Also, please provide the logs of your state machine. Also, please use hyper-v server 2012 R2 instead of windows server 2012 R2. You do not need windows server just for nova-hyperv. Hyper-V server 2012 installs quicker, and does not require a license.
[14:31] <gnuoy> gsamfira, I think the statemachine may contain the smoking gun
[14:32] <gnuoy> gsamfira, http://paste.ubuntu.com/8418508/
[14:33] <stokachu> marcoceppi, the test runner for charms does that basically juju deploy a charm in lxc and run whatever is in tests/*.test?
[14:35] <gsamfira> gnuoy: looks like the tools finder might be the problem. I have not touched that in a long time, but someone else might have. Are you using the latest trunk?
[14:35] <stokachu> marcoceppi, also does manage.jujucharms.com interpret TAP output?
[14:36] <gsamfira> let me do a quick test with the latest master
[14:38] <rick_h_> stokachu: no, it doesn't.
[14:38] <stokachu> rick_h_, how does the testing show the report? just pass/fail if the test returns error code?
[14:39] <gnuoy> gsamfira, so I need to. Upload a Hyper-V server 2012 image to maas and switch to using juju 1.21-alpha2 . I built jujud.exe on a windows server 2012 R2 server can I still use that binary or do I need to rebuild with the hyperv edition (I'm guessing I don't need to) ?
[14:39] <rick_h_> stokachu: yes, it used to be that manage would check the test results in jenkins. With the new test suite I don't believe they're hooked up at the moment.
[14:39] <gsamfira> you can use the same binary
[14:39] <gsamfira> gnuoy ^
[14:39] <gnuoy> gsamfira, thanks
[14:39] <rick_h_> stokachu: it's something that has to be worked out as the testing tools get closer to general consumption
[14:39] <rick_h_> stokachu: so the TAP note is interesting
[14:40] <gsamfira> the thing is, that windows server 2012 R2 does not have the hyper-v role enabled by default AFAIK
[14:40] <gsamfira> gnuoy are you using fastpath for windows? :)
[14:40] <rick_h_> stokachu: but would have to work with through jenkins and the test runner it looks like. Not sure if it's on their radar at atm.
[14:40] <stokachu> rick_h_, yea, i think having TAP would be beneficial as people could write tests in whatever language they want
[14:40] <stokachu> rick_h_, so the test runner does jenkins deploy the charm and then run the tests?
[14:41] <rick_h_> stokachu: I believe so. It handles the bootstrap/etc and then then the tests run against the deployment.
[14:41] <stokachu> rick_h_, ok cool, thanks for the response
[14:42] <rick_h_> stokachu: np, thanks for the TAP earworm, something to think about.
[14:42] <stokachu> rick_h_, np, there isn't a place to file enhancement requests for the manage.jujucharms.com app is there?
[14:43] <rick_h_> stokachu: well, it's not really manage. It's really just the consumer. I'm looking to see if the testing stuff is up somewhere a bug can be filed. tvansteenburgh have the link handy?
[14:43] <stokachu> ah ok
[14:44]  * tvansteenburgh reads scrollback
[14:44] <rick_h_> tvansteenburgh: is there a place to file bugs against the charm testing work?
[14:44]  * rick_h_ is looking through GH and LP for something that looks like 'charm testing'
[14:44] <gnuoy> gsamfira does editing the node in maas to set the os and release  set the installer correctly or is there another step there ?
[14:45] <gsamfira> you only set the OS in MaaS if you plan on deploying it via MaaS. Juju takes care of requesting the proper OS from MaaS
[14:45] <gsamfira> so no need to worry about that
[14:46] <gsamfira> gnuoy: the only thing to worry about when deploying windows server 2012, is that you have the KMS keys set up so it won't prompt for a serial key when installing
[14:46] <gnuoy> kk
[14:46] <gnuoy> gsamfira, but thats not a problem when using the hyperv image, right ?
[14:47] <gsamfira> gnuoy: right
[14:47] <gnuoy> excellent
[14:47] <tvansteenburgh> rick_h_, stokachu: https://github.com/tvansteenburgh/charmguardian
[14:47] <tvansteenburgh> that's what actually kicks off a test in jenkins
[14:47] <gsamfira> Hyper-v server does not require a key. Its free to use, unlimited, bla bla bla
[14:48] <tvansteenburgh> rick_h_, stokachu: feel free to file stuff there, i'll move it if necessary
[14:48] <rick_h_> tvansteenburgh: ty much
[14:49] <tvansteenburgh> that repo will move under juju-solutions GH namespace soon, just haven't gotten around to it yet
[14:49] <stokachu> tvansteenburgh, cool, so what causes a test to fail the return code of each test?
[14:49] <tvansteenburgh> stokachu: correct
[14:50] <stokachu> tvansteenburgh, and tests are run like ./tests/00-basic.test individually?
[14:50] <stokachu> or does it run like nosetests or something
[14:50] <tvansteenburgh> stokachu: tests can be anything executable in charmdir/tests/
[14:50] <stokachu> ok cool
[14:50] <tvansteenburgh> it will also run `make lint` and `make test` targets if they exist
[14:50] <tvansteenburgh> stokachu:  ^
[14:51] <gsamfira> gnuoy: http://paste.ubuntu.com/8418625/ <-- latest trunk
[14:51] <stokachu> tvansteenburgh, cool thats good to know, the lint tool could it be a custom one?
[14:51] <tvansteenburgh> stokachu: yeah, whatever you want
[14:51] <stokachu> thats pimp
[14:52] <gnuoy> gsamfira, fantastic, let me give that a try
[14:52] <stokachu> so the frontend just parses this json  output then?
[14:52] <tvansteenburgh> stokachu: yep, that's right http://reports.vapour.ws/charm-tests-by-charm
[14:52] <stokachu> tvansteenburgh, and also what about lint output ?
[14:53] <tvansteenburgh> stokachu: all output is captured and included in the test report details
[14:53] <stokachu> tvansteenburgh, ok cool so long as my output is readable and comprehensable that would be ok?
[14:54] <tvansteenburgh> stokachu: e.g. lint output: http://reports.vapour.ws/charm-tests/charm-bundle-test-942-results/charm/charm-testing-hp/1
[14:54] <tvansteenburgh> stokachu: yep
[14:54] <gsamfira> gnuoy: if you like, you can get the binaries from: http://gaby.rohost.com/tools/
[14:54] <stokachu> sweet
[14:54] <stokachu> tvansteenburgh, so with this setup would it even make sense to support TAP output?
[14:55] <tvansteenburgh> stokachu: sorry i don't know what TAP is?
[14:55] <stokachu> tvansteenburgh, http://testanything.org/
[14:55]  * tvansteenburgh looks
[14:56] <stokachu> tvansteenburgh, i use it a lot with my cpan modules
[14:56] <stokachu> but it works across several languages
[14:58] <tvansteenburgh> stokachu: interesting. patches welcome :)
[14:58] <gsamfira> gnuoy: or even set your tools-metadata-url: to that value in environments.yaml
[14:58] <stokachu> tvansteenburgh, cool, i can work on that if you aren't opposed to it
[14:59] <tvansteenburgh> stokachu: i'm not opposed, i'm just fairly certain that it won't be something i have time for in the near future
[14:59] <gnuoy> gsamfira,  I'll give the binary I built a try but if that fails I'll definitely grab those, thanks
[14:59] <stokachu> tvansteenburgh, no worries i can take a stab at it and open a PR
[14:59] <gsamfira> gnuoy: my pleasure
[15:05] <sebas5384> thanks! lazyPower++
[15:05] <sebas5384> :)
[15:06] <lazyPower> sebas5384: my pleasure. Looking forward to the follow up where we can sink our teeth into your use cases
[15:06] <sebas5384> lazyPower: sounds great!
[15:06] <lazyPower> sebas5384: i'll schedule out a 2 hour block next time as well. Get me the list of names so we can get everyone together at teh same time isntead of a staggered start.
[15:08] <sebas5384> yeah definitively, and now that the team get all excited about, we are going to have more people contributing into it
[15:08] <sebas5384> :)
[15:10] <sebas5384> lazyPower: when you can send us the link of the recorder hangout, there are people that want to see already hehe
[15:10] <lazyPower> sebas5384: sure, let me export it, and edit off the extra 5 minutes i just recorded
[15:10]  * lazyPower forgot i was recording
[15:11] <sebas5384> hehe
[15:13] <lazyPower> sebas5384: exporting now and i'll upload it unlisted to youtube for your team. incoming link shortly.
[15:14] <sebas5384> lazyPower: thanks :)
[15:18] <whit> nice definition of "Da Cloud": https://wiki.mozilla.org/CloudServices#Get_Involved
[16:19] <aisrael> I think a charmer needs to look at this and change the status of this MP (disapproved): https://code.launchpad.net/~jaywink/charms/trusty/postgresql/swiftwal_missing_functionality/+merge/235394
[16:50] <themonk> JoshStrobl, hi
[16:50] <themonk> i am facing a strange problem
[16:51] <themonk> i set relation in join hook in charm 1
[16:52] <themonk> and try to get that data in charm 2 in change hook, but getting None type value
[16:53] <themonk> my other charm are working ok
[16:54] <themonk> can any one give me any hint
[16:55] <stokachu> tvansteenburgh, is make lint run in the deployed charm or just in the checked out repo directory
[16:57] <stokachu> or should i just have a target to make sure required dependencies are installed for a custom lint program to run
[16:58] <tvansteenburgh> stokachu: the latter
[16:58] <stokachu> tvansteenburgh, ok cool, thanks again
[16:58] <tvansteenburgh> np
[16:59] <tvansteenburgh> cd /tmp
[17:02]  * JoshStrobl was afk
[19:15] <rcj> Can I set constraints in environments.yaml?  Specifically instance-type for EC2.
[19:39] <Tug> rcj: You don't set instance-type in evironment config
[19:40] <Tug> Here is the list of available params: http://juju-docs.readthedocs.org/en/latest/provider-configuration-ec2.html
[19:40] <Tug> you can set machine constraints when you deploy a service
[19:40] <Tug> https://juju.ubuntu.com/docs/reference-constraints.html
[19:49] <Tug> Some of my instances are scheduled for reboot by aws. I'm wondering is it something juju can handle ?
[19:49] <Tug> Like did you think about restarting all the units on reboot?
[19:50] <rcj> Tug, I want to avoid 'juju bootstrap --constraints="instance-type=m3.medium"' by having an setting in environment.yaml if it were available.
[19:51] <Tug> rcj, yeah but as you see, it has been deprecated
[19:51] <Tug> not sure it's working today
[19:52] <lazyPower> Tug: once your api controller fires back up and your agents re-connect it will fire a config-changed event across the nodes
[19:54] <Tug> ok thx lazyPower, so I guess config-changed should actually start the process if it's not running
[19:54] <Tug> but it's the job of the charmer to know that
[19:54] <lazyPower> yeah, i've seen a lot of the charms fire off hooks/start
[19:55] <lazyPower> which is a decent pattern to adopt. It'll be a telling story as to which services dont come back online -  also - to note, if they have good upstart scripts you should be fine
[19:56] <Tug> mm not all charms run the underlying service using upstart.
[19:56] <Tug> For instance mongodb is run as a shell command from a python script with a deamonize option
[19:58] <Tug> anyway it's good to know
[19:59] <lazyPower> Tug: are you running the MongoDB charm in production?
[19:59] <Tug> lazyPower, yes
[19:59] <Tug> I have actually modified it
[20:00] <lazyPower> we should talk - as i'm the present hot seat maintainer for the MongoDB charm - anything that you found that was papercut worthy is totally worth investigating
[20:00] <lazyPower> i'm still hacking through other priorities but its high on my list of TODO's to triage it in its current state and give it more love/tests
[20:00] <Tug> sure :)
[20:00] <Tug> I haven't hacked on it for a while
[20:01] <Tug> but I can try to help
[20:01] <lazyPower> are you running a single node, or cluster?
[20:01] <lazyPower> and is it replicated/sharded if cluster?
[20:01] <Tug> I was running a 12 instances cluster (3 shards)
[20:01] <Tug> I'm actually removing 2 shards at the moment
[20:02] <Tug> because it's starting to be quite expensive ^^
[20:03] <lazyPower> indeed. Have you looked at running them on DigitalOcean?
[20:03] <lazyPower> DO makes for a zippy MongoDB host, as their VPS's are SSD backed, and a fraction of AWS costs
[20:03] <Tug> Nop. I have free credits on amazon at the moment (startup credits)
[20:03] <lazyPower> ah, very nice
[20:03] <sarnold> for the micro instances?
[20:04] <sarnold> those things are slooooow :)
[20:04] <Tug> mongod are running on m3.medium instances
[20:05] <Tug> with ebs provisioned iops storage
[20:06] <Tug> sarnold, nop it's real credits for everything on aws for 2 years
[20:06] <Tug> limited to a few K
[20:07] <Tug> anyway, this was my branch https://code.launchpad.net/~dekervit/charms/precise/mongodb/trunk
[20:08] <sarnold> Tug: oh cool :)
[20:08] <lazyPower> ahhh i remember this branch
[20:08] <lazyPower> and the comment on the bug before about the replicaset relation-changed method needing refactoring
[20:09] <Tug> yes, it was me :)
[20:09] <Tug> like 3 months ago
[20:09] <Tug> ;)
[20:09] <lazyPower> mhmm
[20:09] <lazyPower> progress has been slow, i dont have the time to really manage teh charm like it should be managed
[20:10] <Tug> I haven't followed juju development for a while now. I guess you added ways to do automated testing and stuff
[20:10] <natefinch> rcj: it would be worth writing up a bug asking to support constraints in the environments.yaml.... that seems like a pretty nice feature
[20:11] <rcj> natefinch, sounds good
[20:11] <lazyPower> Tug: Yep. Amulet testing, bundletester, etc. I'm working on the charm authorship docs as we speak actually
[20:11] <rcj> natefinch, looks default instance type was removed
[20:12] <Tug> lazyPower, nice, I'll want to have a look :)
[20:13] <lazyPower> http://github.com/juju/docs - if you want to star/watch the repo you can get up to the minute updates
[20:13] <natefinch> rcj: yeah, I think that's been gone ever since we switched away from pyjuju .... the instance-type constraint was only added back fairly recently (April).  It should be pretty trivial to add support for reading constraints from environments.yaml, I'd think.
[20:13] <Tug> lazyPower, done
[20:14] <rcj> natefinch, cool
[20:14] <Tug> anyway I might get back on mongodb charms soon. If I can make it stable enough maybe it can be merged into the main branch ;)
[20:19] <lazyPower> mbruzek, marcoceppi - https://github.com/juju/docs/pull/172
[20:25] <natefinch> rick_h_: let me know if I screwed anything up in that doc ;)
[20:26] <rick_h_> natefinch: thanks looking
[20:28] <mbruzek> lazyPower:  To quote tvansteenburgh, "I saw what you did there, and I didn't like it"
[20:28] <mbruzek> lazyPower: There is some merge text in your document you want to clean up.
[20:28] <lazyPower> what?
[20:29] <lazyPower> looking
[20:29] <mbruzek> lazyPower: your pull request
[20:29]  * lazyPower throws a fit
[20:29] <lazyPower> thats it, i'm going back to vim diff
[20:29] <lazyPower> screw meld
[20:29] <lazyPower> oh wait, it has the .orig file included
[20:29] <lazyPower> what kind of nonsense is this, thats user error
[20:31] <lazyPower> mbruzek: corrected and repushed
[20:33] <lamont> is there really no named charm?
[20:33] <lazyPower> lamont: there's a start to a dns-charm that would have support for named
[20:33] <lazyPower> but its nowhere near ready for public consumption
[20:34] <lazyPower> lamont: https://github.com/chuckbutler/DNS-Charm
[20:34] <lazyPower> there are spec docs included in the charm if you want to lend a hand
[20:34] <lamont> lazyPower: I'll look.
[20:35] <lamont> I also have an openvpn-server charm to upload, that actually charms the things I want charmed (no, the CA does not belong anywhere near the openvpn endpoint)
[20:36] <lazyPower> lamont: stuff it in your namespace, and open a review ticket against it :)
[20:37] <lamont> could you expand upon "my namespace"?
[20:37] <lazyPower> lamont: https://juju.ubuntu.com/docs/authors-charm-store.html#name-space-charms
[20:37] <lamont> thank yo
[20:39] <lazyPower> lamont: the idea is its 2 stage. No reviews required for your charm to be listed in the charm store under your namespace. When you're ready to undergo the review process to become a recommended charm - you then progress to the next stage. This is 2 fold 1) this enables you to get moving quickly and have your charm listed in the charm store without high walls to hurdle. 2) you can get community feedback on your charm through use of your charm in your
[20:39] <lazyPower> namespace, before you have a charmer look at it  (but we're open to reviewing charms anytime regardless of recommended status desire - so feel free to open a review ticket at any time)
[22:24] <lazyPower> hazmat, kwmonroe, mbruzek, marcoceppi - https://github.com/juju/docs/pull/181  - Digital Ocean provider docs
[22:33] <kwmonroe> lazyPower: the v1 api stumped me for a bit earlier this week.  glad you got explicit with the screenshots.  i'll circle back tonight for a merge if nobody has other comments.
[22:33] <lazyPower> ack. Thanks kwmonroe
[23:28] <arosales> lazyPower: DO doc commented on
[23:28] <arosales> thats https://github.com/juju/docs/pull/181 for referernce.