=== kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 === kadams54 is now known as kadams54-away === kadams54 is now known as kadams54-away === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away === marlinc_ is now known as marlinc === underyx|off is now known as underyx [10:29] tvansteenburgh: Hi there. Let me know if you managed to sort out the auto-test issues. I've got a branch I'd love to land for elasticsearch (I've tested it locally, as well as manually upgrading some deployment scenarios): https://code.launchpad.net/~michael.nelson/charms/trusty/elasticsearch/firewall_optional/+merge/240211 (it's got a prereq branch which is also approved) [14:04] hi, new here. need to write a charm to deploy a django stack (apache, postgres, gunicorn) and would like to look at an existing charm for this as an example to emulate. I'm using python-django for the django part. the postgres part seems straightforward. the apache2 (and I wnat to do haproxy at some point, but small steps) is not at all as obvious to me [14:13] skay: we actually use bundles for that purpose [14:14] skay: if you have juju-gui deployed, you acn visit your gui instance and build the bundle in your env, or you can model a deployment on jujucharms.com at zero cost to you (kind of a drafting tool really) then export the bundle and deploy to your provider. [14:16] lazyPower: oh, ok. I'll play around with that and look at the code it generates. [14:18] skay: http://paste.ubuntu.com/8761147/ [14:19] skay: thats just drag n drop stuff - you can get more detailed with the deployment like placing your django and postgres instances in lxc/kvm containers on a single host to cut down on costs, and deploy haproxy to the host machine handling your web routing - thus effectively placing your entire stack in a single machine. [14:19] lazyPower: thanks [14:20] skay: stay tuned, early next week i'll have a video tutorial published about a new charm hazmat has in the works to do software defined networking to do cross-host container communication so you can do density with your deployments in lxc and scale out. [14:21] skay: you may also want to look at https://jujucharms.com/bundle/django/2/example-single/ -- fair warning: i've never deployed this bundle, but it at least looks close to what you want.. [14:21] kwmonroe: thanks. I did find that one and download it just now (searched for bundles and it popped right up) [14:22] thanks both! [14:22] kwmonroe: nice follow up [14:22] thanks lazyPower. nice initial outreach. let's see if we can pat each other's backs all day long. [14:23] kwmonroe: hit me with your best shot :D [14:23] i'm over it [14:23] someone's feeling spunky today [14:24] caffeine is a helluva drug [14:29] my maas nodes are stuck in "commissioning" state. Looks like the node is not able to update packages. Any ideas on debugging this problem? [14:31] khuss: is your mass-controller node able to reach the internet? [14:32] lazyPower: the maas controller is able to reach the internet [14:32] khuss: ok, i ask because there is a curtain proxy on all nodes that routes through your controller. [14:33] khuss: have any logs we can look at? [14:33] lazyPower: i tried by making the controller both DHCP and DNS [14:33] lazyPower: also by making it just the DHCP server [14:33] lazyPower: which log files? [14:34] lazyPower: i suspect it could be the proxying issue. but not sure how to debug it [14:34] khuss: is this a VMAAS setup with KVM machines or are you running bare metal? [14:35] lazyPower: bare metal on Dell PowerEdge [14:35] lazyPower: when the commissioning fails, the nodes gets powered down [14:35] hmm i'm not sure, i'm poking around in my maas logging directory for the logs we'd be interested in [14:35] 1 moment [14:36] noodles775: jenkins is still fubar [14:36] i'm far from a maas expert, but i've got some experience in troubleshooting a vmaas setup (ie: my own) [14:36] lazyPower: thanks [14:36] noodles775: fwiw your tests all pass for me on lxc [14:36] noodles775: i can't even bootstrap on ec2 atm [14:36] khuss: maybe ask in #maas as well [14:38] khuss: yeah i forget where the logs are located :( sorry i wasn't much help. [14:38] lazyPower: ok.. tx for trying [14:48] skay: the bundle i linked is subject to a bug i just discovered -it exported "null" and .nan in the keys for postgres - which will fail a deployment for you [14:48] i've got people looking into it, but treat that as the worst case example - the bundle you fetched from teh store will not have this behavior. [14:49] lazyPower: *nod* [15:10] mbruzek: can you point me to docs or a test.py that does something besides assert that deployment worked? i want budnletester to twiddle config, but am not sure of the syntax. [15:11] kwmonroe: sure. [15:11] I always point people to my lamp tests [15:12] http://bazaar.launchpad.net/~ibm-demo/charms/trusty/lamp/trunk/view/head:/tests/10-deploy-test.py [15:12] kwmonroe: ^ [15:13] cool mbruzek - thanks! [15:13] Documented like it should be [15:13] i see that. but you got a thing against whitespace? [15:14] * tvansteenburgh chuckles [15:15] There is whitespace in there [15:15] Just not very much [15:15] :) just giving you grief. it's probably faster this way. [15:17] this test does not go into config, sorry kwmonroe [15:18] kwmonroe: Here is another example [15:18] http://bazaar.launchpad.net/~charmers/charms/precise/tomcat/trunk/view/head:/tests/10-configured-deploy.py [15:19] kwmonroe: line 124 where the code calls unit.file_contents [15:20] nice mbruzek - those help alot [17:43] is there a good way to force a charm in to an error state? or do we have a testing charm that fails for certain hooks? [17:46] wwitzel3: edit the charm and throw in a line that errors out [17:47] wwitzel3: pretty trivial to write a test charm to use [17:48] natefinch: yeah, I was just chekcing to make sure there want something like fail-install-charm .. before i went and tweaked one to do that [17:48] Is there a way to file a bug against a PPA in launchpad? [18:06] aisrael: just the project unfortunately. [18:08] lazyPower: Thanks! === CyberJacob|Away is now known as CyberJacob === fuzzy is now known as Ponyo === kadams54 is now known as kadams54-away === lazyPower is now known as lazyWeekend [23:11] Can anyone using mongodb charm and relating it to other charms via database relation, please ping me.? === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [23:55] jrwren: ping [23:56] tvansteenburgh: <3 [23:56] fuzzy: :( [23:56] It's ok, I still love ya :) [23:56] Happy Halloween [23:56] lazyWeekend: ! [23:56] you must think i'm blowing you off by this point, but i'm really not. it's been a really bad week [23:57] Not at all [23:57] I can only assume you are as busy as me [23:57] if that's the case then i feel sorry for you :) [23:58] it won't always be like this