=== dvestal_ is now known as dvestal === dvestal_ is now known as dvestal === dvestal_ is now known as dvestal === dvestal_ is now known as dvestal === ayr_ton is now known as ayr-ton === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away [07:54] hi === rogpeppe1 is now known as rogpeppe [10:31] jamespage: looks like success. I used the ceph tool to remove the mon and osd in ceph and removed the node from maas. Then added it back into maas and used juju add-unit and it seems to have setup the monitor. I'm not sure it's got the OSD yet but that could be due to bad gpt partition table. [10:32] next bit will be waiting for it to come up properly (currently has clock skew) and for the osd's to rebalance then I'll try the next node. === bloodearnest_ is now known as bloodearnest === jw4 is now known as jcw4 [14:29] natefinch: wrt: reviewboard - whats the question being proposed? teh charm has been accepted to the store. https://jujucharms.com/precise/reviewboard-1 [14:40] lazyPower_: sorry, I should have given more context. we're trying to set it up for use with juju core and github, with a plugin so we can log in with our github usernames. [14:41] natefinch: ah ok. I thought it was with relation to teh service not having been charmed yet or something. *hattip* ok glad its nothing thats pending on ~charmers [14:42] lazyPower_: thanks for pointing out my email was too vague :) [14:54] stokachu, ping? [15:06] mattyw, hey === lamont` is now known as lamont === niemeyer_ is now known as niemeyer [17:16] is it possible to 'expose' a service to a specific IP or set of IP addresses? [17:16] or is that a planned feature? (i haven't search the issues list yet.) [17:36] zirpu: I think the solution would be preparing a subordinate service that runs appropriate ufw or iptables commands yourself; the different cloud providers have different granularities on their "security groups" [17:37] jcastro, marcoceppi: do you guys have time to talk about charmer pain points today? [17:37] sarnold: agreed. i'd already thought about that. just was hoping it was included as a possible parameter to 'expose'. [17:38] zirpu: agreed :) === lazyPower_ is now known as lazyPower [17:58] natefinch: I do! [17:59] marcoceppi: for a minute I thought you guys didn't have any complaints, and I was just going to stay home for the rest of the week :) [18:00] ....the joke is funnier when you don't work from home :/ [18:00] natefinch: hah, you wish. was otp [18:00] natefinch: what you want to know? === roadmr is now known as roadmr_afk [18:03] marcoceppi: have you seen this: https://docs.google.com/a/canonical.com/spreadsheets/d/1ZC76hkbxDF7idcSbU9DI-homfom224q484HOLNFSIM8/edit#gid=0 [18:03] natefinch: not yet [18:05] marcoceppi: take a look, let me know what you think about the charmer stuff... my team will be working on those. Mostly, I need details on how you'd like it to work. [18:05] Guys, is possible to make a charm that deploy and setup other charms? [18:05] marcoceppi: meeting time for me [18:05] ayr-ton: technically, yes, but it's not a very clean and pretty thing [18:06] natefinch: want me to just dump them here? or email? or? [18:07] marcoceppi, What is the best practice for do something like this? For example, if I want to setup a jenkins master, 4 runners, a gitlab server, a sonarquobe and integrate this. Like, calling a script with all the steps. [18:07] marcoceppi: let's hang out later today if you have time [18:08] Like, I want to setup this enviroment in my development machine, with a script. And then, push this to another juju environment. [18:09] natefinch: i have time for this [18:09] ayr-ton: that's a bundle [18:09] marcoceppi, hmmm [18:09] ayr-ton: a bundle is a static representation of a deployment with configuration and relations coded in [18:10] marcoceppi: cool... in a meeting for the next 30-60mins but any time after until 5 is cool [18:10] natefinch: I've got a standup at 3p, I'll ping after that [18:10] marcoceppi, this: https://juju.ubuntu.com/docs/charms-bundles.html? [18:10] ayr-ton: yeah, that's the doc page, I'll link you to a few examples too. [18:12] ayr-ton: http://bazaar.launchpad.net/~maarten-ectors/charms/bundles/presto/bundle/view/head:/bundles.yaml is an example and here's a bunch more: https://code.launchpad.net/charms/bundles [18:12] marcoceppi, thank you very much (: It is enough to get started. [18:14] natefinch, marcoceppi, let's hop on a G+ [18:14] jcastro: he's in a meeting, we should sync post-our-daily [18:14] marcoceppi, that link nate showed you is the addition of all the feedback from our team, plus others. [18:15] jcastro: yeah, it's awesome === CyberJacob|Away is now known as CyberJacob [18:29] uhuuu! https://bugs.launchpad.net/charms/+bug/1315428 "fix commited" [18:29] Bug #1315428: Review needed: Drupal Charm [18:29] what that means? :P [18:33] sebas5384: it changes nothing, justsome testing with the new review queue [18:37] ahhh :( [18:37] hehe [18:37] marcoceppi:I run to the charm store to see if the charm was recommended hehe [18:46] sebas5384: fix released is when it gets promulgated [18:59] ahhh ok marcoceppi thanks :) [19:05] hey hatch - http://blog.dasroot.net/the-power-of-community-charming/ [19:05] loooking [19:06] your blog looks so good [19:07] O_o [19:07] thanks [19:16] awesome post hatch :) [19:17] wops! [19:17] lazyPower: sorry now that i sow it was yours hehe [19:18] haha THANKS [19:18] :P [19:20] Thanks :D [19:20] if you dont mind, syndicate that. We need to get the word out about personal namespaces being the recommended path for starting - i've got a todo item to updat the docs as well [19:20] We should see that land sometime by early next week. [19:23] yo natefinch === roadmr_afk is now known as roadmr [19:48] marcoceppi: sorry, stepped out for a bit. Want to talk now? [19:54] natefinch: yeah jcastro ^^ [19:54] I have a call, but pass me the URL [19:54] I'll join after [19:56] marcoceppi: https://plus.google.com/hangouts/_/canonical.com/moonstone?authuser=1 === wallyworld_ is now known as wallyworld [22:12] Hi to all. Can anyone help me get my head wrapped around the differences between Salt and Juju? [22:15] Are they simply two different approaches to the same problem, or are the complementary tools. I'm obviously a noob. [22:32] MrDan: I'm not really familiar with salt [22:32] MrDan: juju is not just about setting up environments, but also making sure the different services communicate [22:32] and keep communicating as things change [22:39] thumper: my understanding is that Saltstack has been adopted by LinkedIn among other large sites. [22:39] thanks for the reply, though. [22:43] MrDan: sure, there are many users of all the deployment tools [22:52] thumper: One of the differences I see from just a very cursory reading of Salt - it provides remote execution management. Am I correct in thinking this might make a good complement for Juju? [22:53] MrDan: juju has some now, and gaining more with actions [22:53] Ah. Interesting. [22:54] I just came across the "salt-master" charm. Looks like I need to do some more digging. [22:55] thanks for the feedback. [23:00] One small rant about this space. The cheeky vocabulary used by tools like Chef, Puppet, Salt, etc.... is more hurdle than help (IMHO). [23:00] cheeky? [23:03] As an example, since I've been talking about Salt, it has "minions", "pillars", "grains", etc.... [23:03] More thematic than helpful. [23:03] maybe "cheeky" is the wrong work. [23:03] *word [23:12] MrDan: Salt is very much a config management toolchain. Juju is a layer above that [23:12] juju can orchestrate a salt stack, and push salt to the limits of its capabilities by providing information outside of salt that juju then plugs into a remote (salt, chef, bash, python, puppet, etc) CM framework to perform operations. [23:12] Juju is like the all powerful all knowing oracle of your deployment infrastructure [23:13] and it makes things dead simple when you combine that with the simplicity of the Juju GUI [23:13] so to think of Juju as just config management of machines is only the first step, its also responsible for scaling, relations between services in a SOA approach, and has some capacity to do more with the use of juju-run and well scripted tasks. [23:15] lazyPower: that's helpful. [23:16] MrDan: a bit wordy in terms of adverbs - but juju really is an amazing tool with what it brings to the table when you consume well written charms. [23:16] are there any specific questions you have about juju that I may be able to answer for you? [23:19] Unfortunately, my inquiry is still at the forest level. I have a lot more digging to do, but am impressed with the responsiveness of this group. [23:21] We try to be. Community is our biggest winner when you go with juju - the charm store is an amalgamation of a community of effort.