[00:04] this ssh to bootstrap thing is perplexing === CyberJacob is now known as 23LAAWP3T === CyberJacob is now known as 45PABAHTB === dspiteri is now known as Guest30044 === rektide is now known as 14WAB035R === bjorne is now known as 45PABBKPP === jose- is now known as JoseeAntonioR === timrc-afk is now known as timrc === timrc-afk is now known as timrc === timrc-afk is now known as timrc === rogpeppe2 is now known as 16WAALSO4 === 16WAALSO4 is now known as rogpeppe === timrc-afk is now known as timrc === niemeyer is now known as 45PABCUAQ === ubot5` is now known as ubot5 === bradm is now known as 5EXAAH0BV === wallyworld is now known as Guest64110 === benji is now known as Guest23911 [13:01] Is there a trick with juju get and set ? I try to "get" the settings from one charm, and a simple set with the same file does not work (says "no settings found for " === gary_poster|away is now known as gary_poster === sarnold_ is now known as sarnold === Guest23911 is now known as benji === jcverdie is now known as 23LAA12CK === markthomas_ is now known as markthomas [14:06] Hi, what is the best way to modify a charm? Are the charm recipes kept somewhere incache on my pc? [14:08] jcverdie: the code for charms is kept in source control on launchpad. The best way to modify a charm is to branch from the main repository for the charm. [14:08] jcverdie: if you go to the charm you want to modify on jujucharms.com, there will be a link to the source under the name of the charm on the left, like this one for mongodb: https://jujucharms.com/precise/mongodb-21/ === rogpeppe is now known as rogpeppe1 === rogpeppe1 is now known as rogpeppe === 14WAB1TAR is now known as vila === _thumper_ is now known as thumper === freeflying is now known as freeflying_away === Geek_Juice is now known as Bryanstein [14:48] thanks, but gerrit charm is not mainstream it comes from cs:~canonical-ci/precise/gerrit-59 [14:48] so i'm confused where to find the sources [14:48] and where to send patches (I found a couple of misbehaviour) === vds` is now known as vds [15:00] guys, can someone please take a look at this? it's been sitting there for around two months waiting to get reviewed/promoted. https://bugs.launchpad.net/charms/+bug/1125869 [15:00] <_mup_> Bug #1125869: New charm: postfix === rcj` is now known as rcj [15:10] if I go to https://bazaar.launchpad.net/%7Ecanonical-ci/charms/precise/gerrit/trunk/files I get unauthorized ? Any help :) [15:20] i asked to join the charmers team, hope to get access :) [15:21] but the canonical-ci page is private :( [15:23] hi, i have tried to deploy multiple juju charms on a single node with the command "juju deploy X -to lxc:0" but sth went wrong as it seems. Please have a look at the output of the "juju status" command: http://pastebin.ubuntu.com/6867420 === zz_frobware is now known as frobware [15:24] so, the "agent-state-info" indicates some error and the charms itself stay in the state "pending" [15:41] is there a way to UNDEPLOY a single charm?= [15:44] what sources in source.list do i need for juju? [15:45] tomixxx: you can destroy a single unit, or the service to "undeploy" the charm [15:45] tomixxx: typically you will want to add ppa:juju/stable - and run off the stable tree of juju for your production environment. [15:45] yeah, i have already found out the command: juju destroy-service mysql for example [15:46] Hi lazyPower, hope you had a wonderful superbowl party yesterday :) I solved & deployed my gerrit...Thanks for your help! [15:46] Hey thats great news jcverdie! glad I was of some service. [15:46] if I go to https://bazaar.launchpad.net/%7Ecanonical-ci/charms/precise/gerrit/trunk/files I get unauthorized access... So I can't file bugs & submit patches to complete a clean install of this charm [15:47] jcverdie: ah, yeah I am on that list too. It appears that since its only intended to be used by Canonical internally we aren't privvy to the launchpad assets. [15:48] lazyPower: how do i add "ppa:juju/stable"? [15:48] so what's the idea here? I can't even fork it to fix it :( ? [15:49] tomixxx: apt-add-repository ppa:juju/stable [15:49] lazyPower: thx [15:49] jcverdie: email the list, and someone on the team may be able to work something out for you. [15:52] lazyPower: Is there a possibility to clear the log message in agent-state-info when i call "juju status"? [15:55] lazyPower: how can i destroy a lxc container? [15:59] tomixxx: whatare you trying to do? if you're trying to delete a lxc container that juju is managaing you will encounter some issues as the bootstrap node handles all that. === xnox_ is now known as xnox [16:00] lazyPower: done:) [16:00] lazyPower: excactly, i want to delete an lxc container because thre creation of the container failed [16:01] lazyPower: http://pastebin.ubuntu.com/6867420 [16:01] i could also do "destroy-environment" but it needs a lot of time to reset juju at all [16:06] tomixxx: you can run the lxc-destroy command to remove the containers, but you will encounter an issue with juju thinking the containers are still around in an error state and will desync your local provider from the bootstrap node. at least thats the behavior I have seen when i've remoevd lxc containers without juju's help [16:07] ok, so what could i do instead? [16:07] personally, i would rebootstrap the environment [16:07] destory & rebootstrap [16:08] lazyPower: ok but it seems "apt-add-repository ppa:juju/stable" was not sufficient abecause it failed again to get http:s//cloud-images.ubuntu.com/query/precise/server/released-dl.current.txt" [16:09] ah i guess i have to call sudo apt-get update [16:11] sorry :( === timrc is now known as timrc-afk === Makyo is now known as Guest92118 === timrc-afk is now known as timrc === jono is now known as Guest16175 === frobware is now known as zz_frobware === medberry is now known as med_ === Guest92118 is now known as Makyo === manu is now known as seelaman === jono is now known as Guest82971 === zz_mwhudson is now known as mwhudson === adam_g` is now known as adam_g === cp is now known as Guest2850 === BradCrittenden is now known as bac [20:30] marcoceppi: hello [20:30] rkpaul: hello! [20:30] rkpaul: what happens when you go to https://store.juju.ubuntu.com/charm-info?charms=cs%3A~marcoceppi%2Fprecise%2Fdiscourse in your browser? [20:31] on the host system, I'm getting some json. When I wget it in the VM, I'm getting a cert error [20:32] ERROR: cannot verify store.juju.ubuntu.com's certificate, issued by ‘/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certificates.godaddy.com/repository/CN=Go Daddy Secure Certification Authority/serialNumber=07969287’: [20:32] Issued certificate not yet valid. [20:32] rkpaul: yeah, it seems you don't have the CA chain on theVM [20:32] and it's a 13.10 VM? [20:32] yeah [20:32] rkpaul: can you make sure ca-certificates is installed [20:33] yeah, already installed [20:35] rkpaul: well this is unfortunate and very odd. I've got 13.10 on my laptop without issue it seems to be missing some root ca in your chain to validate the godaddy cert [20:35] very weird [20:36] I'll try spinning up a new vm with 13.10 and see what happens [20:36] rkpaul: please, I'm in Europe right now so it's nearing my EOD, but I'll hang around for a bit. [20:36] rkpaul: the charm is also broken, I can try to patch it, but upstream changed the way production database configuration options are stored [20:37] so you're already walking in to a bit of a trap ;) It's one of the reasons I've not submitted the charm to the charm store, given how fast upstream is moving [20:37] ok, no worries. I was just messing around with discourse and figured it'd be an interesting way to start looking at juju [20:38] rkpaul: feel free to give it a whirl anyways, there's an earlier version of discourse that will work with the charm [20:38] * marcoceppi looks it up [20:41] rkpaul: you can run `juju deploy cs:~marcoceppi/discourse`; then immediately after run `juju set discourse release=v0.9.8.1` [20:41] which is the version right before the config change [20:41] cool, thanks! [20:42] rkpaul: cheers, feel free to pop in with any questions about juju! [20:44] very weird, new VM isn't exhibiting the cert issue [20:44] wonky [20:44] hopefully you can press forward without any other weirdness [20:44] sorry to have bothered you with it, thanks for helping! :-) [20:44] rkpaul: np anytime! === _mup__ is now known as _mup_ === ev_ is now known as ev === amol__ is now known as amol_ === timrc_ is now known as timrc === drrk_ is now known as drrk === dspiteri is now known as DarrenS === beuno_ is now known as beuno === 5EXAAH0BV is now known as bradm