[07:27] Good morning Juju Wolrd! [09:57] lazyPower / ryebot : hi, a night passed for me, let me backlog and connect to the VPN of the office and I will send you that :) [11:45] Zic: sounds good. Thanks for digging into this [11:46] https://www.youtube.com/watch?v=HI0x0KYChq4 [11:51] o/ magicaltrout [11:51] did you figure out your DNS conundrum? [11:58] for the record, I love the word conundrum [11:58] and mornings and such [11:59] rick_h: i wonder if that says a lot about you [11:59] but it is a fun word [11:59] rick_h: not to be confused with corundum [11:59] coriander? [11:59] lazyPower: I feel like if we sat down to cover the things that "say a lot about me" we'd be here a while :) [11:59] wpk: not dinner time yet, ssssh [12:01] lazyPower, rick_h - hello, lads. Who do I ping these days for review.charmstore.com, do you know, maybe? Tim? [12:02] i didn't lazyPower [12:02] but i'm on vacation next week so i'm over it [12:02] magicaltrout: fair enough [12:03] rick_h: :) [12:03] Mmike: what can I help you with? [12:03] when ya'll get bored...... [12:03] 19:59 < magicaltrout> marcoceppi: can you go through the Developer credits backlog when you get a spare [12:03] slot? :) [12:03] 20:00 < magicaltrout> also can someone review my gitlab charm [12:03] 20:00 < magicaltrout> not cause i'm overly bothered about the promotion, i just want to get a code [12:04] review to see if I'm following the process for the review queue in general [12:04] ta [12:05] lazyPower, trying to request a review for a charm, but I end up with "review.jujucharms.com didn�t send any data." and "ERR_EMPTY_RESPONSE" after I click 'Submit' button on the request-review page [12:06] Mmike: ok thats interesting. Yeah tvansteenburgh would be a good person to ping on that, but i have news for both you and magicaltrout. [12:07] we haven't publically announced this yet as there's still more planning/discussion that needs to happen, but we'll be decomissioning the review queue. Which in turn is going to bring in some new process/policy for charms. [12:07] aww but this is like the first time I've ever tried to do anything properly as well.... [12:08] magicaltrout: you wore us down man. hows it feel? :) [12:08] * lazyPower assigns credit/blame to magicaltrout [12:09] ironically the previous time i attempted to get some stuff reviewed was when you decomissioned the old review queue [12:09] so its plausible [12:13] lazyPower, yup, just had a short chat with dosaboy, he mentioned something in that manner [12:14] lazyPower, but in the meantime I do need to get charm changes to the charmstore! :) I'll ping tim in an hour or so, it's too early for him yet [12:16] Mmike: which Tim are you looking for? [12:17] tvansteenburgh, hello! you sire. Having issues when trying to put a charm up for a review in the review.jujucharms.com [12:20] Mmike, looking, one sec [12:20] thnx [12:22] Mmike: hrm, revq is getting a 503 from the lp api at the moment... [12:24] Mmike: asking about it in #launchpad [12:25] tvansteenburgh, ack, thank you for looking into it [12:30] Mmike: i've asked wgrant to comment over there, so i'll wait and he what he says [12:30] Mmike: i've seen this once before - it seems to happen to some lp accounts but not others [12:31] Mmike: one way forward would be to have someone else submit the review, if the charm is maintained by a team [12:31] tvansteenburgh, ack, thank you. It's no rush, I'd say. [12:32] tvansteenburgh, well, it's maintained by the mongodb-charmers team, which I'm part of... but I always pushed the charm to my personal namespace and the asked for a review [12:33] tvansteenburgh, you think I should try doing it from mongodb-charmers namespace / [12:33] ? [12:33] Mmike: ok, so you've never had this prob before? that gives me hope that it's temporary [12:33] Mmike: yeah, worth a try [12:33] tvansteenburgh, nope, this is a first timer. not that I did tons of reviews either [12:33] Mmike: or just wait to see what wgrant says about that error [12:33] up to you [12:34] i'll wait a bit, have some other things on my plate (NOT lunch, yet :D ), as I said, no rush yet :) [12:34] tvansteenburgh, thank you for the help [12:34] Mmike: k, np [12:53] o/ [12:53] tvansteenburgh: hey - can we get a new charmhelpers released out? I'm working on landing support for OpenStack Pike and our reactive charms need a released version with the right bits... [12:53] jamespage: will do [12:53] tvansteenburgh: also can we talk about moving charmhelpers to github? [12:53] yes! [12:54] I'd like to help make that happen if that's useful [12:54] that'd be great [12:54] I feel we can make alot of use of things like travis which is harder on LP [12:54] yes [12:54] tvansteenburgh: maybe the first step is to just get the code migrated over; then we can iterate from that point onwards [12:55] tvansteenburgh: tell you what - lemme post to that effect on #juju [12:55] ML that is [12:55] +1 [12:55] erik_lonroth: for our party in a few feel free to just follow this link: https://hangouts.google.com/hangouts/_/canonical.com/rick-harding [12:55] jamespage: thanks! [12:58] metaphorical bull grabbed by the horns [12:58] shout me down if I'm sounding truly insane :-) [12:58] :D [12:58] marcoceppi: ^^ [12:59] jamespage: charmhelpers-0.16.0 uploaded to pypi [12:59] tvansteenburgh: tvm [12:59] hmm is that actually a thing [13:00] ta very much [13:00] np [13:02] erik_lonroth: around for our chat? [13:06] the heat is getting to jamespage [13:06] magicaltrout: could be could be [13:07] magicaltrout: hows it on your side of the county? [13:07] Warm [13:07] although i'm off on the broads for a week next week [13:07] so hopefully it'll stay [13:12] magicaltrout: which part? [13:14] jamespage: Boating Stalham down to Hickling then down Acle then up to bure marshes(bewilderwood for the kids) [13:15] magicaltrout: nice [13:15] magicaltrout: my first job was working for a development company in stalham [13:15] meadowhouse bar lazer - I wonder what happened to them? [13:15] we'll see, never done 5 days on a small boat with the kids! ;) [13:15] * jamespage goes to look [13:16] hey lazyPower i could see you fitting into the narrowboat lifestyle nicely ;) [13:16] cruising up and down the canals [13:20] magicaltrout: its not that far of a stretch to the imagination [13:21] i pretty much inhabit a narrow living space now :) [13:22] magicaltrout: did you just plan a trip to 'places with ridiculous names' then? [13:23] hell admcleod i'm from Yorkshire where we get used to americans pronouncing Ruswarp and Grosmont very wrong :) [13:23] presumably they're there because they thought they were going to lie-chester square and got the wrong train [13:23] ah you've met those people then [13:24] i was one :( [13:27] thats what happens with you hold a british passport but don't really like the country! ;) [13:27] hey, i like scotland [13:27] they don't have a passport [13:27] ... yet [13:29] jamespage: I just created the github repo, in advance of the vote passing [13:30] marcoceppi: awesome - url? [13:30] github.com/juju/charm-helpers [18:05] bdx: ping [18:10] yo [18:19] hello all, Was wondering if anyone could explain how the mongodb charm consumes storage ? any options for eps backed storage? [18:19] eps=ebs [18:29] lazyPower / ryebot : sorry, I was far away from my computer this day, was not planed :( -> here is what you asked: http://paste.ubuntu.com/24657948/ [18:30] Zic: fantastic, this gives me someplace to start. That etcd has an invalid cluster config from the relationship vs what the leader is reporting [19:53] Hello guys, a question I'd like to create a new charm, an example could be a video surveillance server type MotionEye, and make that on juju store. What do I must to do? Which are the steps to make? Is there a guide to help to build a charm? Thanks [19:54] dakj_ you should probably start here: https://jujucharms.com/docs/stable/authors-intro [19:54] and feel free to ask questions here or on the juju mailing list [19:56] hatch: thanks a lot, I'll begin from that. [19:58] dakj_ we're still working on the documentation so if you find anything lacking/missing/wrong feel free to file an issue/pr here: https://github.com/juju/docs [19:59] hatch: ok perfect. [20:09] hatch: I'm seeing that on juju store is not present Nginx, if you look for "web" there a bundle called "Web Infrastructure In A Box" where it's present Nginx but if you try to find alone there is just " [20:09] nginx passenger" why? [20:10] nobody has written a nginx charm, typically it's installed within a charm as an internal server [20:10] nginx passenger is quite old, I wouldn't recommend using it as it only supports precise [20:13] dakj_ with all that said though, nothing saying you couldn't write one :) [20:14] hatch: I try it!!! [20:14] :D [20:14] hatch: I'm following that https://jujucharms.com/docs/2.1/authors-charm-building [20:14] I can see an argument for nginx being a standalone charm, and a subordinate [20:15] not really a subordinate, maybe a standalone charm [20:15] it's too hard to model the intricaces required to configure nginx as a subordiante where you woulnd't ever switch out that charm for another web server [20:16] which is why NGINX exists as a layer today [20:16] marcoceppi ohh there is a layer for it [20:16] TIL [20:16] :) [20:16] absolutely [20:16] http://interfaces.juju.solutions/ about half way down [20:16] and there it is http://interfaces.juju.solutions/layer/nginx/ [20:17] it's used in quite a few charms [20:18] marcoceppi would be cool if we could create a dependency graph for layers to see what charms are using which layers [20:18] it already exists [20:18] but the charm store refuses to ingest any dot files, so they get excluded from the store quite often [20:19] ahhh [20:19] if you want to tackle a year+ old bug: https://github.com/CanonicalLtd/charmstore-client/issues/204 [20:20] :D [20:30] dakj nothing to worry about :) [20:31] charms can be built by mixing layers, and we were just talking about a way to know which charms use them [20:36] hatch: is it to complicate to begin? Because I don't see for example a LAMP or LEMP bundle it's for the same way explained of marcoceppi? [20:39] hatch: sorry I want to say, using NGINX as example to build a charm is too hard as starting [20:42] as the beginning [20:42] dakj so the first thing you might want to try to do is simply creating a charm which installs something [20:42] regardless of what it is, then expand from there [20:43] ok [20:46] dakj on the docs navigation there is a heading "Developer Guide" It's probably best to read at least Getting Started, Event Cycle, Charm Layers, Interface Layers first [20:47] hatch: ok I'll begin from that to understand how it works