[00:02] <aimatt> ah intersting
[00:03] <aimatt> ok, thanks for the input
[00:03] <sarnold> (you could just have openstack without juju, if that's more acceptable to your operations folks.. :)
[00:03] <sarnold> then you'd only have one juju in play, and that might be easier to wrap heads around
[00:03] <aimatt> I want the charms! lol
[00:03] <aimatt> we are losing our primary sysadmin, so we are exploring options
[00:03] <aimatt> and juju is looknig very good
[00:55] <marcoceppi> aimatt: Right, what sarnold described is pretty accurate as far as using Juju to drive both the bare metal and then deployments on the bare metal. I'll dig up a few links for you, but there are video demos of sabdfl having a cluster a machines registered in MaaS, then deploying OpenStack on that in under 15 mins, then deploying services on to the OpenStack environment right after that. It's a little inception-like but a very
[00:55] <marcoceppi> interesting use case
[01:10] <marcoceppi> ahasenack: ping
[01:38] <jcastro> aimatt: another nice benefit of juju is the reusability of charms
[01:38] <jcastro> you don't need to write a memcached charm
[01:38] <jcastro> we have one already
[07:20] <weblife> I just finished a three part tutorial on how to get going with Node.js / MongoDB on Ubuntu and then deploy it to cloud services.  Could I get any interested parties to review it for fixes / ideas on how to improve it?  https://github.com/TheMindCompany/mongonode-app/blob/master/tutorial.pdf
[07:33] <Tantor> Hello. I'm trying to use juju. However I'm having a problem. I did juju-deploy juju-gui
[07:34] <Tantor> Then juju added another node as machine #1, however this machine has the agent-state 'not-started'. When I login through SSH to this machine and do sudo restart juju-machine-agent. I get a message that it's restarted, but still no change in the status. Here is the output of juju status: http://pastebin.com/Uv7Zg2qx
[08:51] <weblife> What would be the best way to stress test a web application or better yet possibly have Juju auto scale an application.
[10:57] <drj11> Hmm. I have a problem trying to terminate-machine
[10:57] <drj11> I get: $ juju terminate-machine 40
[10:57] <drj11> error: no machines were destroyed: container info for machine 40 not found
[10:57] <drj11> (I've recently upgraded to 1.11.5-raring-amd64)
[10:58] <drj11> the machine exists and has no services running on it (previously ran destroy-service which worked just fine).
[10:58] <drj11> is this likely to a recent bug?
[12:05] <marcoceppi> drj11: it may be, I've not encountered that error before.
[12:22] <pavelpachkovskij> hi
[12:22] <pavelpachkovskij> can someone merge fix for this bug? https://bugs.launchpad.net/charms/+source/memcached/+bug/1206491
[12:22] <_mup_> Bug #1206491: Memcached service doesn't start <memcached (Juju Charms Collection):Fix Committed> <https://launchpad.net/bugs/1206491>
[12:30] <pavelpachkovskij> marcoceppi, thanks
[12:30] <marcoceppi> pavelpachkovskij: np
[13:40] <pavelpachkovskij> and one more https://code.launchpad.net/~charmers/charms/precise/redis-master/trunk/+merge/177828
[13:42] <marcoceppi> pavelpachkovskij: it says there are 0 lines to merge
[13:42] <pavelpachkovskij> crap
[13:42] <marcoceppi> ah, the merge is backwards
[13:43] <pavelpachkovskij> marcoceppi, I did smth wrong?
[13:43] <marcoceppi> pavelpachkovskij: you're requestion to merge lp:charms/redis-master in to your branch. Resubmit with your branch merging in to lp:charms/redis-master
[13:43] <pavelpachkovskij> marcoceppi, ah
[13:43] <pavelpachkovskij> marcoceppi, one sec
[13:44] <marcoceppi> pavelpachkovskij: FWIW, I just looked at your commit and it LGTM
[13:44] <marcoceppi> surpised that wasn't caught sooner
[13:44] <pavelpachkovskij> https://code.launchpad.net/~pavel-pachkovskij/charms/precise/redis-master/fixed-open-port-issue/+merge/177847
[13:46] <pavelpachkovskij> marcoceppi, thanks again )
[13:46] <marcoceppi> np
[15:45] <weblife> I just finished a three part tutorial on how to get going with Node.js / MongoDB on Ubuntu and then deploy it to cloud services.  Could I get any interested parties to review it for fixes / ideas on how to improve it?  https://github.com/TheMindCompany/mongonode-app/blob/master/tutorial.pdf
[15:45] <weblife> last night not just now :)
[15:50] <weblife> I think I should try and put more detail into using Juju.  Around page 10(beginning of juju lesson) I got tired and lazy.
[15:51] <marcoceppi> weblife: I'll take a look in a bit. thanks for the link!
[15:54] <jcastro> juju charmers meeting in ~6 minutes!
[15:55] <jcastro> weblife: have you seen the node-app charm?
[15:55] <jcastro> it automates pages 1-3 of your tutorial, heh
[15:57] <weblife> marcoceppi Thank you
[15:57] <jcastro> https://plus.google.com/hangouts/_/b853ceaa631f9a4d4359556e3cbf27ffae3abc81?authuser=0&hl=en
[15:57] <jcastro> the hangout will be there for anyone who wants to participate in the meeting
[15:58] <weblife> jcastro I used the node-app charm.  But my revision that installs from source and installs express also
[15:58] <jcastro> adding an option to the charm to install from source and do express would be a nice contribution!
[15:59] <weblife> <weblife is conflicted (watch Kaptest prep for GRE or charmer hangout)
[15:59] <weblife> jcastro I know.  Trying to gain experience so you guys allow me into charmers so I can submit
[16:00] <jcastro> oh, you don't need to be in charmers to submit
[16:00] <jcastro> you just can start submitting
[16:00] <jcastro> charmers is for when you want to review etc, later on when you're experienced with juju
[16:00] <weblife> pavelpachkovskij from CSU Fullerton??
[16:02] <pavelpachkovskij> hello
[16:02] <pavelpachkovskij> is there a link to charmers meeting already?
[16:02] <marcoceppi> Pad: http://pad.ubuntu.com/7mf2jvKXNa
[16:02] <jcastro> We'll be streaming the meeting on http://ubuntuonair.com if anyone wants to follow along
[16:02] <jcastro> https://plus.google.com/hangouts/_/b853ceaa631f9a4d4359556e3cbf27ffae3abc81?authuser=0&hl=en
[16:02] <jcastro> if you want to participate
[16:02] <pavelpachkovskij> weblife, no
[16:03] <weblife> good :x
[16:03] <weblife> hehe
[16:06] <weblife> yes Brandon Clark is me
[16:07] <marcoceppi> o/
[16:26] <weblife> experimental kernel messing up my connection :x
[16:42] <weblife> Hmm.  I don't think its my kernel anymore, it could be g-hangouts :x
[16:42] <weblife> TRy one more time to listen in
[16:44] <weblife> Or is it over?? haha
[16:44] <marcoceppi> weblife: they're published to youtube so you can always watch post-recording
[16:45] <weblife> I know but want to be able and chime in if I wanted to.  Let you guys know other care your doing it also.
[16:46] <marcoceppi> weblife: if you have feedback or questions you can reply to the mailing list email that Jorge sends out every week with the highlights. We're always happy to answer questions and field comments from users!
[16:48] <weblife> marcoceppi Thank you.  Your always a help.
[16:53] <jcastro> marcoceppi: hey for local provider
[16:53] <jcastro> it seems default-series: precise doesn't work for me
[16:53] <marcoceppi> jcastro: yaeh?
[16:53] <jcastro> ideas?
[16:53] <marcoceppi> jcastro: define "doesn't work" for you?
[16:53] <jcastro> it launches saucy containers
[16:53] <marcoceppi> machine 0 will always reflect the host machine, each additional machien should be the default-series defined
[16:54] <jcastro> ah nuts
[16:54] <jcastro> so like if I bootstrap
[16:54] <jcastro> but do juju deploy --to 0 wordpress
[16:54] <jcastro> error: cannot assign unit "wordpress/0" to machine 0: series does not match
[16:54] <marcoceppi> jcastro: you're going to have a bad time
[16:54] <jcastro> nod
[16:54] <jcastro> ok so test on a real cloud is what you're saying. :)
[16:54]  * marcoceppi nods
[16:55] <marcoceppi> I hear HP is nice this time of year
[16:55] <jcastro> juju switch hpcloud
[16:55] <jcastro> :)
[16:55] <jcastro> I love this command
[16:55] <jcastro> I can just switch from local to cloud in one go
[16:55] <marcoceppi> I still haven't used juju switch
[16:55] <jcastro> !!
[16:56] <jcastro> you're not doing -eblahblah every time are you?
[16:56] <marcoceppi> jcastro: I am
[16:56] <marcoceppi> old habbits die hard
[16:56] <marcoceppi> I'm terrified of not using switch and accidentally destroying ubuntu-discourse instead of local or something silly
[16:56] <jcastro> true dat
[16:57] <marcoceppi> Maybe I'll add a plugin or something that is a safe guard
[16:57] <marcoceppi> like juju safe destroy-environment
[16:57] <marcoceppi> which will just confirm every action you do by telling you current environment, etc
[16:57] <jcastro> in pyju there was an env setting you ould set to make it so you could never accidentally blow it away
[16:58] <jcastro> IMO juju should always echo the current environment on every command
[16:58] <jcastro> "blah blah success/failed on $env"
[16:58] <marcoceppi> Well, juju-core gives you just enough rope. Especially since it doesn't offer an ack mechanism
[16:58] <marcoceppi> jcastro: that doesn't help prevent the issue though, just tells you even sooner that you goof'd
[16:58] <sarnold> $PS1 mangling? :)
[16:59] <marcoceppi> I think -v offers that too jcastro "2013-07-31 16:58:45 INFO juju.environs.local environprovider.go:32 opening environment "local-core"
[16:59] <marcoceppi> "
[16:59] <marcoceppi> is the first line typically when using -v
[16:59] <marcoceppi> anywho, -v could use some work on not being so verbose
[17:06] <stub> marcoceppi: 'juju lock-environment' + 'juju unlock-environment' ?
[17:06] <stub> marcoceppi: ie. a flag that you can set to help protect you from blowing off your foot?
[17:07] <jcastro> http://ec2-54-211-7-242.compute-1.amazonaws.com/?p=4
[17:07] <jcastro> haha man
[17:07] <jcastro> that was --to easy
[17:08] <jcastro> marcoceppi: wanna siege up that badboy, see how it performs?
[17:19] <weblife> Hmm strange.  Juju status says no instances after I bootstrap AWS.  Haven't had this happen before.
[17:20] <weblife> weblife destroy's it to try again.
[17:22] <pavel>  weblife this happens time to time
[17:23] <pavel> I think possible reason may be when you try to bootstrap right after destroy-environment
[17:23] <pavel> but this is just my theory
[17:23] <weblife> can't delete security groups from ec2 console either, grrr.  I'm going to eat them.
[17:23] <weblife> pavel: that is what I did.  Makes sense...
[17:24] <weblife> now I know
[17:25] <marcoceppi> weblife: it's also "the cloud" in general. Sometimes weird stuff just happens
[17:30] <jcastro> rick_h: this search result bug where it goes back to the result instead of the readme is killing me
[17:31] <rick_h> jcastro: it's landed, there was talk of doing a deploy on wed
[17:31] <rick_h> gary_poster: is that deploy on deck for today? ^^
[17:32] <gary_poster> rick_h, we can't deploy till benji gets the cache bug landed, and we make a release.  At this point I'm guessing tomorrow, rick_h and jcastro.
[17:32] <rick_h> gary_poster: k, thanks for the heads up.
[17:33] <jcastro> ok guys, so deploy --to is basically awesome
[17:33] <rick_h> jcastro: yea, checking our your weekly call video now. I need to test that out and lxc out
[17:34] <weblife> marcoceppi & pavel:  I believe in this case it may have been the AWS region. Used west-1 after a little wait the second time and still happened
[17:35] <weblife> worked on east-1 though
[17:35] <marcoceppi> gary_poster: Is "--to" support on the roadmap for gui?
[17:36] <gary_poster> marcoceppi, yes.  we think it will be actually a place where the GUI can give a significantly better experience than the CLI, including automated searching for available machines based on constraints.  We will be talking about tech plans next week at the manager sprint and work is slated to begin september
[17:37] <gary_poster> engineering work, that is
[17:37] <marcoceppi> gary_poster: awesome news, thanks :D
[17:37] <gary_poster> :-)
[17:38] <weblife> Question!!  Why would I get: error: no settings found for "mongonode-app".  Here is my config.yaml: http://github.com/TheMindCompany/node-app/blob/master/config.yaml
[17:38] <weblife> It works if I deploy local with --repository
[17:39] <marcoceppi> weblife: what's the deploy command you're using?
[17:40] <weblife> marcoceppi: juju deploy --config config.yaml node-app mongonode-app
[17:40] <weblife> I am operating from ~/
[17:40] <marcoceppi> weblife: So, when you deploy with --config there needs to be a filed called config.yaml (or whatever is named in the flag) and it needs to be a key value set of options you want to deploy with preceeded by the service name
[17:41] <marcoceppi> Let me give you an example
[17:42] <marcoceppi> weblife:
[17:43] <marcoceppi> http://paste.ubuntu.com/5933505/
[17:43] <marcoceppi> You don't need to specify a --config flag during deployment, it's only if you want to preseed config values
[17:44] <marcoceppi> weblife: You could just as easily do juju set mongonode-app app-port=80 install_root=/home/ubuntu app_node_env=development
[17:44] <marcoceppi> after deployment
[17:46] <jcastro> http://ec2-50-19-27-38.compute-1.amazonaws.com/
[17:46] <jcastro> less than 10 minutes guys
[17:46] <jcastro> look at that!
[17:47] <weblife> jcastro social sign returns json error file
[17:48] <weblife> or fb one did
[17:48] <jcastro> google one works
[17:48] <jcastro> I think for FB I need an API key
[17:48] <sarnold> jcastro: these guys claim they can have an instance up and running in 55 seconds.. https://www.digitalocean.com/
[17:48] <weblife> jcastro I am sure thats it if you haven't registered it
[17:48] <sarnold> jcastro: interesting if true ;) I wonder how much effort it'd be to hook up their API with juju..
[17:48] <jcastro> "instance up and running" doesn't count. "service up and running" is what counts.
[17:49] <jcastro> sarnold: when we get an SSH provider we'll get digital ocean
[17:49] <sarnold> jcastro: sure, but getting an OS going in 55 seconds is a darn sight quicker than my AWS testing so far :)
[17:49] <jcastro> true dat
[17:49] <jcastro> that's like having the indy 500 be about who can start their car up faster. That doesn't win the race.
[17:49] <jcastro> but yeah, 55 seconds is nice!
[17:52] <sarnold> jcastro: heh, races can be won or lost on pitcrew performance..
[17:55] <jcastro> arosales: do you have the recordmydesktop snippet handy?
[17:55] <jcastro> I am going to do a video on this
[17:55] <jcastro> too cool not to
[17:56] <arosales> jcastro, recordmydesktop --freq=22050 --buffer-size 96000 --width 1024 --height 768 --fps 24 -x 6 -y 96 --delay 3 -o "<juju-scale-name>.ogv"
[17:58] <arosales> jcastro, the buffer size may not need to be that large but I errored on it being larger just to be safe
[17:58] <jcastro> nod
[18:00] <weblife> marcoceppi: Thank you this has had me confused.  Now the getting started guide makes sense to me on this.
[18:10] <weblife> marcoceppi:  Have you experienced problems when connecting to your node-app deployments on the first connection after startup?  It seems like I always get a 504 first try, then I refresh and everything is okay.
[18:13] <weblife> Maybe if I ping the localhost site in the startup script after it loads this won't happen.
[18:26] <weblife> my connection hates me today :x
[19:28] <sidnei> jamespage: around?
[19:33] <marcoceppi> weblife: Not that I can recall
[19:36] <adam_g> sidnei, he's on holiday
[19:37] <sidnei> adam_g: oh. so let me throw this out there and see if anybody cares: https://bugs.launchpad.net/juju-core/+bug/1203816 is about setting up some proxying for the local provider
[19:37] <_mup_> Bug #1203816: local provider should support use of local proxy <juju-core:New> <https://launchpad.net/bugs/1203816>
[19:38] <sidnei> i hacked together something that reads MIRROR from /etc/default/lxc, but i wonder if it would be best to run apt-config dump Acquire::http::Proxy instead
[19:38] <sidnei> and accordingly, set 'apt_proxy' in cloud-init instead of 'apt_mirror'
[19:50] <adam_g> sidnei, seems sensible. i still hope for someday being able to express some subset of cloud-config via environments.yaml
[19:50] <sidnei> adam_g: that's an alternative too, and i think it might not be too hard to implement. for all environments i guess?
[19:52] <jcastro> arosales: hey so what do you think about a dedicated review day next week?
[19:52] <jcastro> we need to get out of this hole
[19:56] <adam_g> sidnei, yea, i suppose.
[20:01] <arosales> jcastro, marcoceppi and I are talking about it atm
[20:05] <jcastro> heya sidnei
[20:06] <jcastro> have you considered becoming a ~charmer and do an occasional review?
[20:19] <arosales> jcastro, all squired away on the ODS submissions?
[20:20] <jcastro> we're good
[20:20] <jcastro> helped adam power through one of his
[20:20] <arosales> jcastro, thx
[20:20] <jcastro> standing by if anyone needs help
[20:22] <weblife> gonna test one more thing before I submit my patch to node-app
[20:54] <sidnei> jcastro: i have *wink*. i also need to polish my 3mo old apache/squid/haproxy branches to the latest charm-helpers.
[20:55] <sinzui> Does anyone have an example of using nrpe-external-master so that verify I have written a hook properly?
[20:57] <sidnei> speaking of which
[20:57] <sidnei> sinzui: http://bazaar.launchpad.net/~sidnei/charms/precise/apache2/trunk/view/head:/hooks/hooks.py#L257 it's using the old charm-helpers but i think it only needs the imports to be adjusted
[20:57] <sinzui> sidnei, I am past that
[20:58] <sidnei> should be good then
[20:58] <sinzui> sidnei, I have nagios, juju-gui, and nrep deployed. I joined nagios to juju-gui, and I see it monitored.
[20:59] <sinzui> sidnei, I joined nrpe-external-master to juju-gui, I saw the hook fire. I do not see it in nagios
[21:00] <sinzui> sidnei, I joined nrpe-external-master to nagios, I do not see the the extra checks in nagios
[21:00] <sidnei> sinzui: nrpe-external-master doesn't talk to nagios, it needs be manually rsync off to an existing nagios or some such
[21:00] <sinzui> I have set the nagios_master property to the ip of nagios, but I still don't see any extra checks
[21:01] <sidnei> wedgwood: ^ you know a bit more about nrpe-external-master and how it's rsynced
[21:02] <wedgwood> looking
[21:03] <sidnei> sinzui: iirc setting the nagios_master property sets up an rsync entry point so that you can rsync from the nagios host, but that needs triggering manually
[21:03] <sidnei> sinzui: it's meant only for webops since they manage their nagios outside of juju
[21:03] <wedgwood> sinzui: where's your hook code?
[21:04] <sinzui> wedgwood, https://code.launchpad.net/~sinzui/charms/precise/juju-gui/nagios/+merge/177588
[21:04] <sinzui> ^ I fixed a typo in my local copy, but it is otherwise the same
[21:11] <weblife> Trying to submit a merge into https://code.launchpad.net/~web-brandon/+junk/node-app but it tells me : This branch is not mergeable into lp:~web-brandon/+junk/node-app.  Anyone understand why?
[21:11] <sinzui> weblife, it is +junk
[21:11] <sinzui> personal branches are yours.
[21:12] <weblife> okay I think I get it.
[21:12] <sinzui> weblife, merged are supported by shared contexts like a project or a package
[21:14] <sinzui> weblife, when a personal branch (+junk is a bad term) is ready to be shared with others for collaboration, you need to push it to a new or existing project.
[21:16] <sinzui> weblife, I think you want to push your branch to web-brandon/charms/precise/node-app/install-fix
[21:19] <wedgwood> sinzui: I don't see where scripts/update-nrpe.py is called
[21:21] <sinzui> wedgwood, that script is also symlinked as hooks/nrpe-external-master-relation-changed
[21:21] <wedgwood> ah
[21:26] <wedgwood> sinzui: ok, sorry, read scrollback more closely.
[21:26] <wedgwood> nrpe-external-master doesn't do anything on its own. I think your nagios server will need to initiate the rsync from /var/lib/nagios/export
[21:27] <wedgwood> that dir contains the nagios configs to be consumed by the server
[21:27] <sinzui> wedgwood, np. I am the one truly confused. I don't no how to verify my updated charm truly works as it needs to on prodstack
[21:27] <sinzui> bugger /no/know
[21:28] <sinzui> This day is too long
[21:28] <sidnei> sinzui: if you also implement the nrpe interface then you can use the plain nrpe charm, but it takes a bit more setup.
[21:28] <thumper> hi sinzui
[21:28] <wedgwood> I understand. I think it's ... I won't say sufficient... indicative to check whether that directory is populated after the hook fires.
[21:31] <weblife> sinzui: that pushed  and I was able to merge.  Thank you very much
[21:31] <sinzui> weblife, great
[21:31] <sinzui> hi thumper
[21:31] <weblife> https://code.launchpad.net/~charmers/charms/precise/node-app/trunk/+merge/177943
[21:49] <marcoceppi> weblife: Thanks for the submission, but you've done it backwards :) You want to merge your branch  in to lp:charms/node-app - not the other way around
[21:54] <weblife> lol, what did I do? Let me take a look.
[21:55] <arosales> jcastro, marcoceppi had a good point that folks should probably email the juju list when requesting membership to ~charmers
[21:55] <marcoceppi> weblife: you had them reversed, if you look at the merge proposal it says no diff output
[21:55] <arosales> jcastro, and then charmers and +1/give feedback on the applicant
[21:56] <arosales> I will email the list so folks can comment there since it is somewhat of a policy change.
[21:57] <weblife> haha,  whoops. weblife is an obvious newbie to launchpad now...
[21:59] <marcoceppi> weblife: it's okay, I botched probably the first 10-15 merges on launchpad when I really started using it. I'm very accustomed to the Github pull req interface
[22:04] <arosales> jcastro, is there a link to the charm reviewer calendar?
[22:04] <jcastro> arosales: see /topic
[22:04] <arosales> jcastro, I don't see a link?
[22:04] <jcastro>  Review Calendar: http://goo.gl/uK9HD
[22:05] <arosales> jcastro, sorry I didn't scroll :-/
[22:05] <arosales> thanks
[22:08] <weblife> marcoceppi That seems backwards how they make you do that.  Okay gave it another go.
[22:09] <marcoceppi> weblife: much better. I'm not going to be able to get to this today, and the review queue is a bit long, but I'm officially on deck for review next week. So if it isn't reviewed this week, it should be covered by end of next week!
[22:14] <weblife> marcoceppi: No problem, I'm happy with the experience at this point.  Needed to learn how launchpad works because I have been wanting to involve myself in projects like this.
[22:15] <weblife> Helped make node-app better and helped update important documentation.  Good experience.
[22:16] <marcoceppi> weblife: LP can be daunting at first, but it's actually pretty intuiative once you start using it
[22:16] <weblife> Now its time to focus on my tutorial and some how-to videos.  Maybe someone will hire me soon. :)
[22:17] <weblife> marcoceppi: yes it was
[22:17] <weblife> I appreciate all your help over the last few
[22:18] <marcoceppi> weblife: no problem! Happy to help. Thank you for your contributions!
[22:21] <AskUbuntu> Issues with JuJu Bootstrapping | http://askubuntu.com/q/327177
[22:24] <marcoceppi> ahasenack: Are these two problems similar to what you're experiencing right now?  http://askubuntu.com/q/318970/41  http://askubuntu.com/q/327177/41
[22:43] <ahasenack> marcoceppi: let me check
[22:44] <ahasenack> marcoceppi: it is, I don't know to which container/path to upload the json files produced by image-metadata