[01:18] <jose> marcoceppi: is there anyone who's got op access to this channel to fix ^?
[01:19] <marcoceppi> jose: fix what?
[01:19] <jose> marcoceppi: there's someone who's joining and parting massively due to ping timeouts, been like that for almost a week now
[01:19] <marcoceppi> apuimedo, you mean? What would you like me to do about it?
[01:20] <jose> yep, /mode +b$##fix_your_connection
[01:22] <marcoceppi> jose: I'm not a channel operator, I'll find out who
[01:22] <jose> says niemeyer but there's probably someone else
[01:24] <niemeyer> jose, marcoceppi: have you tried talking to him?
[01:25] <jose> niemeyer: he won't get messages, he's pinging timeout just after he connects
[01:25] <lazyPower> I speak to apuimedo_  bi-weekly give or take. probably a bouncer issue
[01:27] <niemeyer> Let's try that first..
[01:27] <lazyPower> niemeyer: i've got a reminder set, i'll reacho ut in the AM
[01:27] <lazyPower> EU hours
[01:27] <niemeyer> lazyPower: Thanks!
[01:27] <lazyPower> np
[01:31] <lazyPower> cargonza - so your messages aren't coming through?
[02:49] <lazyPower> mbruzek: https://bugs.launchpad.net/juju-core/+bug/1532063
[02:49] <mup> Bug #1532063: Unit seems unable to proceed after watcher died in the middle of hook execution <juju-core:New> <https://launchpad.net/bugs/1532063>
[09:54] <philip_stoev> Hi, I wanted to ask if there is a trick that would serialize the execution of the hooks so that they run sequentially across the entire environment, rather than just within a machine?
[09:55] <philip_stoev> In other words, only one hook is running at any given time within the environment
[12:02] <tiagogomes_> Hello! Is it possible to use JuJu with multiple providers? Or use Juju on an OpenStack installation with multiple regions?
[12:31] <stub> tiagogomes_: I don't know about multiple regions. But for multiple providers, you currently need choose one and add vms from the user provider manually (using 'juju add-machine ssh:... ')
[12:31] <stub> tiagogomes_: It works, but you need to handle networking stuff yourself. I use it for hybrid OpenStack/MAAS deployments.
[13:27] <tiagogomes_> stub cool, and does the JuJu GUI support multiple environments as well?
[13:32] <tiagogomes_> looks like no :(
[13:39] <coreycb> jamespage, gnuoy:  can one of you review this? https://code.launchpad.net/~corey.bryant/charm-helpers/git-1531612/+merge/281994
[13:41] <gnuoy> coreycb, ack, I can take a look
[13:41] <coreycb> gnuoy, thanks
[14:25] <lazyPower> tiagogomes_ the gui will support multiple environments (the term will change to models soon) ~ when juju 2.0 lands
[14:25] <lazyPower> tiagogomes_: we debut'd this feature at the last ODS, the videos are still floating around on youtube :)
[14:27] <tiagogomes_> lazyPower nice! is there an expected release date?
[14:29] <lazyPower> tiagogomes_ dont quote me on this but i think its in march
[14:30] <lazyPower> its coming soon, but i forget the dates. a hair preoccupied with the work leading up to that launch :)
[14:31] <tiagogomes_> lazyPower thanks!
[14:39] <d4rks1d3> Hi
[14:41] <rick_h_> tiagogomes_: lazyPower the GUI will be out this month
[14:41] <rick_h_> tiagogomes_: lazyPower but the multi-models support in Juju is 2.0 in 16.04 in april (testable in alphas currently)
[14:41] <lazyPower> o/ d4rks1d3
[14:41] <lazyPower> rick_h_ fan-tastic!
[14:42] <lazyPower> rick_h_ correct me if i'm wrong, but hte new gui is currently bet-able as well right?
[14:42] <rick_h_> lazyPower: yes
[14:42] <rick_h_> lazyPower: there's a charm in the store to test
[14:42] <lazyPower> when i'm not buried in TLS libraries, i'm soooo on board
[14:43] <rick_h_> search the juju mailing list for title "Juju GUI 2.0 - public beta"
[14:43] <rick_h_> with various insturctions on getting/testing/filing bugs and such
[14:45] <lazyPower> flagged, and earmarked
[14:45] <lazyPower> thanks rick
[14:45] <rick_h_> lazyPower: np
[15:13] <coreycb> gnuoy, I have another little follow-on mp for charm-helpers if you could take a look: https://code.launchpad.net/~corey.bryant/charm-helpers/depth-clone-only/+merge/282016
[15:14] <coreycb> gnuoy, it's a corner case so I don't think we need to pick it up in the openstack charms until the next larger sync
[16:37] <Odd_Bloke> lazyPower: Forgive my ignorance, but where can I find the test code that produced the failure in https://bugs.launchpad.net/charms/+source/ubuntu-repository-cache/+bug/1526928 ?
[16:37] <mup> Bug #1526928: Test fails due to peer having rsync cron job <ubuntu-repository-cache (Juju Charms Collection):New> <https://launchpad.net/bugs/1526928>
[16:37] <Odd_Bloke> lazyPower: Oh, it's in the charm.  *hangs head*
[16:37] <lazyPower> Odd_Bloke <#
[16:37] <lazyPower> and <3 as well
[18:24] <natefinch> rogpeppe: first off, lemme say, holy crap, charm upload is awesome. First time I tried it I thought something was broke because it worked so fast and flawlessly.
[18:26] <natefinch> rogpeppe: however, I can't actually deploy the charm... I keep getting "resolved charm URL has no series"
[19:30] <pmatulis> trying to test 1.26-alpha3 with LXD. anyone know what's going on here? http://paste.ubuntu.com/14440220/
[20:29] <marcoceppi> pmatulis: you're not on wily or xenial, probably trusty
[20:29] <marcoceppi> pmatulis: it does not work on trusty
[20:29] <marcoceppi> unless you do a whole lot of hacks
[20:40] <kwmonroe> is personal namespace ingestion working? ~ibm-charmers had a few revs to ibm-db2/README.md in the last 3 weeks.. none of them are showing on https://jujucharms.com/u/ibmcharmers/ibm-db2/trusty/
[20:42] <kwmonroe> charm proof shows 5 info issues, but no W or E.
[21:06] <aisrael> kwmonroe: I'm wrapping up a review of that charm now. I didn't think it was promulgated?
[21:06] <aisrael> Oh, just in their namespace
[21:06] <lazyPower> kwmonroe: this is the second report of an issue w/ ingestion. :( we had one yesterday from natefinch about his charm, but it had proof errors
[21:07] <lazyPower> probs should file an ingestion bug so they take a look
[21:13] <natefinch> lazyPower: btw, my charm proof blows up with an exception (dumping a stack trace to the command line no less... bad form).  How do I update it?  I presume I have some ancient version
[21:14] <lazyPower> natefinch: the charm-tools package has that
[21:14] <natefinch> hmm... say it's already at the newest version
[21:15] <natefinch> lazyPower: thoughts? http://pastebin.ubuntu.com/14440929/
[21:16] <lazyPower> natefinch can i get a bug filed for that? https://github.com/juju/charm-tools/issues
[21:16] <lazyPower> because i have no idea why pyopenssl is barfing :(
[21:17] <natefinch> will do
[21:18] <lazyPower> natefinch looks like you need to update requests though
[21:18] <lazyPower> http://stackoverflow.com/a/29081240
[21:19] <natefinch> lol... exception uninstalling the old requests
[21:20] <natefinch> oh, permission denied.... someone couldn't have put in a catch for that? geez
[21:23] <natefinch> oh man, charm proof is way too strict, geez
[21:23] <natefinch> E: Unknown root metadata field (series)
[21:23] <lazyPower> natefinch: thats a relatively new thing
[21:23] <natefinch> the check isn't, though
[21:24] <natefinch> who cares if I put unknown stuff in the root of the yaml?
[21:24] <lazyPower> obviously proof does
[21:24] <natefinch> sure, make it a warning... but don't prevent me from putting it in the charm store under my own namespace :/
[21:24] <lazyPower> I disagree
[21:24] <lazyPower> it should prevent you from putting garbage in the metadata
[21:25] <lazyPower> but the lack of ingestion was a bummer, sure
[21:25] <natefinch> if it deploys to juju, it should be able to exist in the store
[21:25] <natefinch> perhaps not promulgated, but geez, in my own namespace?
[21:25] <lazyPower> natefinch: juju doesn't validate policy though
[21:25] <lazyPower> proof is our only line of automatically enforcing policy
[21:26] <lazyPower> when charm2 lands, and you can just upload your charm - this issue goes away
[21:26] <lazyPower> and it will only be enforceable on ~recommended
[21:26] <natefinch> which makes me happy :)
[21:27] <lazyPower> just a friendly reminder, that whats frustrating you, is a source of frustration for the ~charmer team as well :)   Imagine the correspondences we have when proof just lets things go and we nack a review on many many items that proof could, and should, be catching.
[21:27] <lazyPower> <3
[21:37] <natefinch> lazyPower: btw, thanks for the tip, updating requests fixed charm proof (perhaps this was obvious by my complaining about charm proof ;)
[21:37] <lazyPower> np :)
[21:38] <lazyPower> google-fu ftw
[21:45] <kwmonroe> lazyPower: ingestion issue filed - you reckon this is the best place? https://github.com/CanonicalLtd/jujucharms.com/issues/189
[21:45] <lazyPower> kwmonroe yep, thats where we were directed to file any store related bugs
[21:46] <kwmonroe> and while i'm grumping around, *my* charm hasn't ingested either :/  (but it's only been a few hours)
[21:46] <lazyPower> kwmonroe: rattle cages! shake trees!
[21:46] <kwmonroe> :)
[22:13] <pmatulis> marcoceppi: does not work on trusty? oh wow ok