[01:05] <lazyPower> fuzzy_: still wrestling with mongodb?
[01:09] <fuzzy_> lazyPower: yes
[01:09] <fuzzy_> Following, https://maas.ubuntu.com/2012/11/30/lets-shard-something/ using the command "juju add-relation mongos:mongos-cfg configsvr:configsvr" I get "ERROR service "mongos" not found".  What am I doing wrong?
[01:09] <lazyPower> do you have a service named 'mongos' deployed?
[01:10] <fuzzy_> not that I see
[01:10] <fuzzy_> that's why the howto doesn't make sense
[01:12] <lazyPower> fuzzy_: are you trying to deploy the sharded/replicated cluster? there is a bundle for it
[01:12] <lazyPower> that howto looks really old
[01:12] <lazyPower> https://jujucharms.com/bundle/mongodb/5/cluster/
[01:12] <lazyPower> take care to note that there are 3 replicated units per shard/configsvr
[01:13] <lazyPower> thats 13 total units listed in that bundle
[01:13] <fuzzy_> thank you
[01:14] <lazyPower> fuzzy_: the mongodb charm is notoriously finicky as well. I've put some elbow grease into it in the past - if you run into any issues with it please file bugs here:   https://bugs.launchpad.net/charms/+source/mongodb
[01:15] <fuzzy_> i'm just going to reroll everything and try one more time
[01:18] <lazyPower> ok. I typically have to do that when i botch a mongodb deploy as well, start over from scratch
[01:18] <lazyPower> there appears to be a race condition in teh charm I haven't tracked down on one of the roles.
[01:18] <lazyPower> sorry about the weak experience with the charm :( MongoDB has been a problem child for me when triaging/maintaining
[01:19] <lazyPower> I'm open to any suggestions on how we can make it a better experience, any documented cases / examples will definately help as we move forward with the next iteration.
[01:19] <fuzzy_> i'm curious why python-yaml ins't part of a machine bootstrap
[01:20] <lazyPower> I've run into this on 2 substrates - DigitalOcean and Linode
[01:20] <lazyPower> its standard on AWS, HPCloud, and Joyent
[01:20] <fuzzy_> i figured that is sort of lsb stuff
[01:20] <fuzzy_> ah
[01:20] <lazyPower> i think they are using modified cloud images, but i have no data to back up my claim
[01:21] <lazyPower> I've had to go back through and add the python-yaml dependency to any of the python based charms as i run across them testing on DO
[01:21] <fuzzy_> you hooked the do api
[01:21] <fuzzy_> is it fully automated yet?
[01:21] <lazyPower> mostly - its a phaux provider
[01:21] <lazyPower> https://github.com/kapilt/juju-digitalocean
[01:21] <fuzzy_> because linode does have an api
[01:21] <fuzzy_> and it's not hard to hook
[01:22] <lazyPower> mhm, i've mentioned this approach to you before
[01:22] <fuzzy_> i just didn't know how hard the juju side of it would be
[01:22] <fuzzy_> i know you did
[01:22] <fuzzy_> i just lost the link
[01:22] <lazyPower> well that plugin is about all i can reference for you - i'm not familiar enough with core to make a recommendation.
[01:22] <fuzzy_> do you use it to admin your do boxes?
[01:22] <lazyPower> however hazmat has all teh goods when he's around. he's the author of that plugin.
[01:22] <lazyPower> i do. I've got ~ 6  nodes running on DO right now
[01:23] <fuzzy_> hmmmmmmm
[01:23] <lazyPower> (including the api server)
[01:25] <fuzzy_> damn that drives a hard bargin
[01:27] <fuzzy_> are you using digital oceans private network to do the deed?
[01:27] <fuzzy_> lamont:
[01:27] <fuzzy_> ack
[01:27] <fuzzy_> lazyPower:
[01:27] <lazyPower> I'm watching ;) no need to ping
[01:27] <lazyPower> Yeah, it automatically adds the private networking to the droplet.
[01:31] <fuzzy_> *sigh* I hope this is worth it
[01:31]  * fuzzy_ crosses fingers
[01:33] <fuzzy_> lazyPower: see if you got any digital ocean promo codes for new accounts so you can get hooked up with this
[01:34] <lazyPower> i do actually, 1 moment
[01:34] <lazyPower> https://www.digitalocean.com/?refcode=b6ac387b6f36 - $10 free credit with a new account
[01:44] <fuzzy_> ok I think I got a do account now
[01:44] <lazyPower> awesome
[01:45] <fuzzy_> awww crap
[01:45] <lamont> lol
[01:45] <fuzzy_> stupid do
[01:45] <lazyPower> ?
[01:45] <fuzzy_> this might not actually work
[01:46] <fuzzy_> remember when they screwed up nyc2 for all those weeks last year?
[01:46] <lazyPower> mhmm, the juniper upgrade
[01:46] <fuzzy_> well i moved everything off of them
[01:46] <fuzzy_> but one of the droplets kept running until it racked up a bill
[01:47] <lazyPower> whoops
[01:47] <fuzzy_> and I told them no way I was paying it, I wasn't even using the box it was a left over from an idle
[01:47] <fuzzy_> now they just took $5 out of paypal and locked my account
[01:47] <fuzzy_> before i could make a droplet
[01:47] <fuzzy_> oh nope there it goes
[01:47] <fuzzy_> whooo
[01:48] <fuzzy_> ok i'm in business
[01:48] <lazyPower> the DO guys are really reasonable.
[01:49] <lazyPower> Every time i've reachedo ut or support i get an answer in an hour or less, and 90% of the time its resolution.
[01:49] <lazyPower> *out for
[01:49] <fuzzy_> actually nope
[01:49] <fuzzy_> i'm locked
[01:49] <fuzzy_> lets seee
[01:50] <fuzzy_> but now i'm limited to 1 droplet
[01:51] <lazyPower> I'd open a ticket and explain whats going on
[01:51] <lazyPower> they should crank you up to 5 instances for your first month or so
[01:52] <fuzzy_> I just did
[01:52] <fuzzy_> now I wait
[02:42] <fuzzy_> https://github.com/charms/mongodb when I try juju deploy mongos i get failure
[02:43] <fuzzy_> weird it took that time
[02:53] <fuzzy_> lazyPower: http://hastebin.com/dadetadepu.sm
[02:53] <fuzzy_> it claims to be running, but i can't seem to find the exposed console for mongo
[02:58] <fuzzy_> yea i don't get it, netstat on that box shows it's listening to 28017, i made sure to disable it's firewall and i still can't see it remotely
[03:00] <fuzzy_> http://hastebin.com/patadakepo.hs
[03:00] <fuzzy_> makes no sense
[03:03] <fuzzy_> So reading the juju log on mongos/0 i get alot of permission denied.  I think that might be because of ufw
[03:03] <fuzzy_> i'm going to tear it down and retry without ufw and ssh configured differently
[07:10] <fuzzy> yea it was ufw fighting me i got a mongo console lazyPower
[15:56] <jamespage> gnuoy`, nudge - https://code.launchpad.net/~james-page/charms/trusty/nova-cloud-controller/cluster-sync-fix/+merge/234475
[15:56] <gnuoy`> ack
[17:07] <marcoceppi> Review Queue is going down for an upgrade
[17:08] <marcoceppi> Review Queue is going down for an upgrade
[20:12] <mbruzek> Hey marcoceppi since we have automated testing now, we should start requiring all new charms to have tests.
[20:14] <whit> mbruzek, that's what I thought the policy was... I didn't realize it hadn't been more widely disseminated
[20:14] <marcoceppi> mbruzek: that's not a bad idea, we should propose this policy to the list
[20:14] <whit> jose, sorry about that :[
[20:15] <marcoceppi> There's a bunch of previous talks about it on the list, I'll round them up and make a new post
[20:16] <jose> whit: don't worry, not a prob :)
[20:49] <marcoceppi> Should we consider unit testing sufficient?
[20:50] <marcoceppi> mbruzek lazyPower jose ^? et al
[20:50] <jose> what would you define as unit testing?
[20:51] <marcoceppi> anything that tests the hooks without being deployed
[20:51] <jose> I would be good with something saying 'hey! I deployed mycharm successfully, even though I haven't accessed it it didn't error while deploying+relating!"
[20:51] <jose> would that be unit testing?
[20:52] <marcoceppi> so, some charms have python unit tests
[20:52] <mbruzek> marcoceppi, I don't see how we can ask authors to write python tests if they don't know it.
[20:52] <marcoceppi> would that be enough to satisify new policy for all chams need tests
[20:53] <marcoceppi> mbruzek: I'm saying, is unittesting enougth to satisfy testing or should we required functional/integration testing as well?
[20:53] <mbruzek> marcoceppi, could they write a bash deployment or a bundle
[20:53] <marcoceppi> that's not unit testing, that's fucntional testoing
[20:53] <marcoceppi> and that's basically what we think of testing today, a la bundle/amulet tests
[20:54] <mbruzek> marcoceppi, I think we should unit test at minimum but HIGHLY suggest having a bundle or amulet test that deploys a working unit.
[20:54] <jose> I have to leave for uni. Giving some input later.
[20:54] <marcoceppi> jose: thanks o/
[20:55] <marcoceppi> mbruzek: right, that's my question, is unittesting enough to satisfy testing requirement in policy
[20:56] <mbruzek> yes.
[20:56] <mbruzek> I don't like only unit tests because I still may not know how to deploy said charm.
[20:56] <marcoceppi> cool, I'll wait for feedback from jose and lazyPower and draft teh policy
[20:56] <marcoceppi> mbruzek: that;'s a readme issue
[20:56] <marcoceppi> and nackable based on that alone
[20:56] <mbruzek> yes.
[21:46] <lazyPower> marcoceppi: i think unit tests or integratino tests at bare minimum. i've been treating it as an either/or
[21:47] <lazyPower> marcoceppi: my reasoning is we still have a ton of bash charms in the store, and bash hasn't exhibited any ground breaking unit test frameworks.
[21:58] <mbruzek> +1 lazyPower