[00:17] <Term1nal> Does it make sense to deploy an ubuntu charm??
[00:18] <davecheney> Term1nal: sure
[00:20] <Term1nal> Could I say............. deploy it to a container? :D
[00:20] <Term1nal> Or do I just add a container and just do whatever it is I needed in that?
[00:21] <Term1nal> Want to deploy a VestaCP setup, I suppose I could make it into a charm...
[01:49] <arosales> Term1nal, you can deploy to a container, and we do have an Ubuntu charm
[01:50] <arosales> Term1nal, http://manage.jujucharms.com/charms/trusty/ubuntu
[01:51] <arosales> Term1nal, re deploying to containers https://juju.ubuntu.com/docs/charms-deploying.html#deploying-to-specific-machines-and-containers
[01:52] <arosales> Term1nal, but VestaCP may make a good suborindate charm and should be pretty straight forward
[01:53] <arosales> given this is the install method for VestaCP, http://vestacp.com/#install
[04:33] <bradm> anyone about who knows about the python-django charm?
[04:34] <AskUbuntu> Can I have multiple local juju environments? | http://askubuntu.com/q/470917
[04:43] <lazyPower> bradm: i have limited knowledge of it, what would you like to know?
[05:13] <bradm> lazyPower: I'm trying to get it to deploy a bzr based project, and its failing on the install hook
[05:14] <bradm> lazyPower: ansible ends up barfing with a "fatal: [localhost] => /etc/ansible/host_vars/localhost: Expecting propert
[05:14] <bradm> y name: line 1 column 2 (char 1)"
[05:14] <bradm> lazyPower: and the task listed is "get mercurial source", which is odd given its a bzr repo
[05:14] <lazyPower> sounds like it may have interpted the resource incorrectly. Can you file a bug with the output?
[05:14] <lazyPower> + charm version
[05:15] <bradm> lazyPower: I'm actually writing one up now :)
[05:15] <lazyPower> thats briliant, thank you!
[05:15] <lazyPower> Fixing problems, one bug at a time.
[05:15] <bradm> its entirely possible my bzr repo isn't right or something, the docs on it are limited
[05:15] <bradm> but I doubt its causing this issue
[05:16] <lazyPower> bradm: did you set the vcs config options to bzr?
[05:16] <bradm> lazyPower: indeed I did
[05:16] <lazyPower> boo, i was hoping for an obvious fix
[05:17] <bradm> lazyPower: my yaml file set vcs to bzr, and repo_url to my bzr branch on lp
[05:17] <lazyPower> hmm, lp:~user/project/branch?
[05:17] <bradm> lazyPower: yup!
[05:17] <lazyPower> can you try giving it the bzr+ssh url?
[05:17] <lazyPower> that may make a difference.
[05:17] <bradm> lazyPower: should there be quotes around the strings?
[05:17] <lazyPower> wouldn't hurt.
[05:18] <bradm> I've tried both with and without quotes
[05:18] <lazyPower> yeah, its not required
[05:18] <bradm> I didn't think so, but the examples aren't consistant
[05:18] <lazyPower> but in the off chance the yaml parser is getting funky during interpretation its best to quote them
[05:18] <bradm> the weird bit is if you look at the ansible playbook, it shouldn't be doing the mercurial task, it shoudl be doing bzr
[05:19] <bradm> which means the variables aren't being set right it seems
[05:19] <lazyPower> do me a favor and run juju run --service python-django config-get and paste me the output
[05:20] <lazyPower> scrub any sensitive details first ofcourse. *friendy reminder*
[05:20] <bradm> lazyPower: http://pastebin.ubuntu.com/7504234/
[05:21] <bradm> lazyPower: I'm learning django, the app I'm deploying is from the django tutorial :)
[05:21] <lazyPower> right on. Exciting stuff learning new frameworks.
[05:21] <lazyPower> I just recently got started with flask, and i'm loving it
[05:21] <lazyPower> the sinatra of the python universe
[05:22] <bradm> oh, interesting, I've heard good things
[05:23] <bradm> I'm a sysadmin though, not a dev, so I pick frameworks to learn most relevant to what I'm doing workwise
[05:23] <lazyPower> ok i just kicked off a deployment with relevant configs, 1 moment while my environment stabilizes.
[05:23] <lazyPower> Yeah, i ride that line between dev and ops every day. I'm a developer at heart, op-smith by trade.
[05:24] <lazyPower> its good to see others picking up the interest in developer <=> ops communication and mindset.
[05:24] <bradm> lazyPower: well, you know I'm from Canonical, right? :)
[05:24] <lazyPower> Nope, but I do now
[05:24] <lazyPower> http://i.imgur.com/A85WCCz.png
[05:25] <bradm> oho, I'm using trusty, that's probably a difference
[05:25] <lazyPower> http://paste.ubuntu.com/7504242/
[05:25] <bradm> and juju 1.18.3, but I doubt that'll make a huge difference either
[05:26] <lazyPower> i got a 500 response code, i didn't remote in to see if its the code or a tanked deployment
[05:26] <lazyPower> but it made it past deployment
[05:26] <bradm> ok, let me redo this with precise and see
[05:27] <bradm> lazyPower: I'm not sure I did the bzr branch right, it wasn't exactly clear what it needed, but thats another thing to debug once I get the install right
[05:28]  * lazyPower nods
[05:28] <lazyPower> I'll be around for another couple of minutes. its pretty late here and I should get some sleep
[05:28] <lazyPower> i'll stick around to see if you hit paydirt though. would be nice to see you unblocked.
[05:29] <bradm> cool, thanks
[05:32] <bradm> just waiting for lxc to catch up to my juju commands now :)
[05:37] <bradm> lazyPower: lxc seems upset at me for some reason, might take a few to fix
[05:37] <lazyPower> ack.
[05:37] <lazyPower> if you need anything further closer to 9am EDT I'll be back at it.
[05:37] <lazyPower> best of luck to you bradm
[05:37] <bradm> lazyPower: thanks heaps for your help, its definately pointed me the right way I think
[06:03] <bradm> lazyPower: huh, I've tried using precise, I've tried using the dev juju version, I still get the same error
[06:19] <bradm> lazyPower: filed LP#1322449
[06:19] <_mup_> Bug #1322449: python-django charm fails to deploy bzr project <python-django (Juju Charms Collection):New> <https://launchpad.net/bugs/1322449>
[08:27] <jamespage> marcoceppi: I made gnuoy a member of the charmers team - he was until he changed teams in Canonical and he's doing lots of work on charms and charm-helpers
[08:27] <jamespage> gnuoy, welcome back!
[08:28] <gnuoy> jamespage, thanks :-)
[09:34] <caribou> Q: when the upgrade-charm hook is fired, should it have all the relations available ?
[09:35] <caribou> I'm calling the function called when 'relation-changed' is fired from the upgrade-charm and apparently it doesn't see any of the relation that 'relation-changed' sees
[10:19] <marcoceppi> jamespage: for future reference there's an application process. if gnuoy needs  access to stuff to work faster we can build teams to do so
[10:19] <marcoceppi> jamespage: ie, if we need to create a charm-helpers maintainers team, etc
[10:19] <jamespage> marcoceppi: oh - the document I read must be wrong then
[10:20] <jamespage> marcoceppi: charmers is appropriate - he's working on charms and will be helping with reviews etc..
[10:20] <jamespage> plus he's lots of good history
[10:20] <marcoceppi> jamespage: https://juju.ubuntu.com/docs/reference-reviewers.html#join-us!
[10:21] <jamespage> marcoceppi: I actioned under "Upon getting involved with these activities, we'll probably ask you if you'd like to join charmers"
[10:21] <marcoceppi> jamespage: ah, well it's ask to apply, wording is vague there
[10:21] <jamespage> marcoceppi: indeed
[10:22]  * marcoceppi updates docs
[10:22] <jamespage> marcoceppi: apologies if I subverted the normal process :-)
[10:22] <marcoceppi> jamespage: no worries! gnuoy gets a +1 for charmer from me so process remains in tact
[10:23] <jamespage> marcoceppi: excellent
[10:23] <gnuoy> marcoceppi, thanks, much appreciated
[10:25] <marcoceppi> gnuoy: I'll send you a welcome email in a bit
[10:25] <gnuoy> thanks
[14:15] <sebas5384> hello o/
[14:15] <sebas5384> did some beer thinking
[14:15] <sebas5384> about the paas thingy with juju
[15:18] <bodie_> sebas5384, aye?
[15:22] <sebas5384> bodie_: oye = ?
[15:23] <bodie_> I was reading the log, and you mentioned you'd done some thinking about juju-paas.  :P
[15:23] <sebas5384> oohh yeah
[15:23] <sebas5384> hehe
[15:23] <sebas5384> sorry
[15:23] <sebas5384> so php, nginx charms, etc...
[15:23] <sebas5384> can make possible the service scale
[15:33] <lazyPower> sebas5384: go on...
[15:34] <bodie_> he named the language that must not be named
[15:34] <lazyPower> I don't see pearl mentioned anywhere in the recent history...
[15:34]  * lazyPower hides
[15:34] <lazyPower> s/pearl/perl
[15:36] <sebas5384> so we can actually use juju as a paas, using some CD tool
[15:37] <bodie_> you'd need a proper deploy target
[15:38] <bodie_> I don't think you necessarily want to spin up a new cloud instance for each app, for example
[15:38] <sebas5384> bodie_: thats not for always
[15:38] <sebas5384> but for example
[15:39] <sebas5384> when we make some deploy to production or stage
[15:39] <sebas5384> the 80% problems are because of some difference between the environments
[15:39] <sebas5384> and thats clearly a waste
[15:40] <lazyPower> sebas5384: as was covered yesterday you can use juju to some semblance of a PAAS
[15:42] <sebas5384> nice lazyPower
[15:42] <lazyPower> well that wasn't supposed to have been sent yet, stupid itchy enter key
[15:42] <lazyPower> anywho
[15:42] <lazyPower> we're getting a proper PAAS in teh coming months with CloudFoundry - its under active dev now.
[15:43] <sebas5384> so making php charms is not a crazy thing
[15:43] <lazyPower> Well, depends on how it fits in your over-arching architecture
[15:43] <lazyPower> There's a long standing todo item to charm up a PHP Framework like Cake, Symphony, Zend, and provide that to the community as well.
[15:44] <sebas5384> i sow some issues about php-app charm
[15:44] <lazyPower> so, it stands to reason that building PHP Application charms are completely within the vision and scope of juju
[15:45] <lazyPower> but it may not offer the same benefits you would get from a PAAS like cloud foundry where you deploy CF, and then allocate app pools within CF and deploy like a madman
[15:45] <lazyPower> heroku kind of set the bar for that, and PAAS's are all the rage these days
[15:48] <lazyPower> sebas5384: However, if you have an idea about using juju as a paas - i'd love to see it.
[15:48] <sebas5384> but for me offering paas using juju, is more friendly to a costumer that haves their own datacenter and build every machine from ground up
[15:49] <sebas5384> lazyPower: great! i'm working on that
[15:49] <lazyPower> sebas5384: I hear ya. I had the same thought a few months ago and dove head first into learning it. My first thought was "Putting the gui overtop of DO would be pure fire for their business model. They sell more VM's and I get a dead simple management interface for SOA"
[15:49] <lazyPower> because lets face it, rick_h_'s team has a really awesome face for juju. The GUI gets more people interested in the product than anything else i've ever done to 'sell it' at talks.
[15:50] <sebas5384> lazyPower: exactly, and the relation thing
[15:50] <sebas5384> for example
[15:50] <sebas5384> openshift had already good stuff happening
[15:50] <sebas5384> but
[15:51] <sebas5384> doesn't have gui, relation and topology portability that juju brings to the table so well
[15:51] <lazyPower> That's true.
[15:52] <sebas5384> so for me buildpack = bundle
[15:52] <sebas5384> and i can have more than one bundle, of the same project
[15:53] <sebas5384> always talking about app is not reality actually, because in the same project you have more than one app running
[15:53] <sebas5384> we have project with node and drupal at the same time
[15:54] <lazyPower> Right. You get into the territory where SOA principals apply. We're running services that utilize messaging to achieve a goal.
[15:54] <sebas5384> lazyPower: nice
[15:54] <sebas5384> i would love to see more of that
[15:54] <lazyPower> sebas5384: you're already seeing that every day
[15:55] <sebas5384> ooh right, service oriented arch
[15:55] <lazyPower> yep
[15:55] <sebas5384> hehe duhh ¬¬
[15:56] <lazyPower> I bought into that methodology a long time ago when i started learning the ruby ecosystem. SOA fits really well within those confines. My web apps were speedy and relied heavily on workers and worker farms to do the heavy lifting
[15:56] <lazyPower> the end user see's a zippy website, while my infrastructure was beaming data bits around to different areas to do different things, such as compute metrics, send emails, etc. None of the heavy lifting was done from the same machine that was presenting the site to the user.
[15:56] <sebas5384> lazyPower: thats what i want for my projects :)
[15:57] <sebas5384> lazyPower: congrats! do you have some slides or post talking about that experience?
[15:57] <lazyPower> MAAS has the same concept using celery and django. Celery is the work horse while django gives you the UX. TO the  user it doesn't matter whats happening under the hood so long as its fast, and easy to use.
[15:58] <sebas5384> exactly
[15:58] <lazyPower> Just the slides I linked you already for my juju talk.  My last job didn't allow me to talk about our tech much. I was under some pretty deep contracts.
[15:58] <sebas5384> hmmm kreepy
[15:58] <sebas5384> oh! i'm going to lunch over here :)
[15:58]  * lazyPower shrugs
[15:59] <lazyPower> marketing
[15:59] <lazyPower> o/ have a good lunch sebas5384. Catch you 'round
[15:59] <sebas5384> alwayssss
[15:59] <sebas5384> hehe
[15:59] <sebas5384> lazyPower: thanks! later :D
[18:49] <sebas5384> sshuttle just is making my mac kernel panic hehe
[18:52] <AskUbuntu> juj status can no lookup nodes by name | http://askubuntu.com/q/471224
[19:04] <sebas538_> kernel panic again!! wtf! hehe
[21:30] <AskUbuntu> Charm Creation General question | http://askubuntu.com/q/471276