/srv/irclogs.ubuntu.com/2013/06/13/#juju.txt

=== defunctzombie_zz is now known as defunctzombie
=== defunctzombie is now known as defunctzombie_zz
=== defunctzombie_zz is now known as defunctzombie
=== thumper is now known as thumper-afk
=== defunctzombie is now known as defunctzombie_zz
=== thumper-afk is now known as thumper
=== danilos__ is now known as danilos
pavelIs there any way I can increase size of root partition in EC2 instance? Or at least attach extra ebs volume?09:37
pavelmy problem is that by default lucid images are 8gb and it's totally not enough for my purposes09:41
=== huats_ is now known as huats
mgzgah, why are recreating the error of having 'docs' as a series of the main project?10:27
mgzjuju-core/docs makes no sense10:28
stuboh noes! Where has debug-hooks gone10:52
mgzstub: bug 102787610:55
_mup_Bug #1027876: cmdline: Support debug-hooks <cmdline> <juju-core:Confirmed> <https://launchpad.net/bugs/1027876>10:55
stubIn the -broken hook, the relation is already gone... so I need to use my -changed hooks to remember state somewhere else so my -broken hook can actually clean up?10:56
mgzthat sounds possible to me, hopefully someone with experience of charming something like that can give suggestions10:58
mthaddonhi folks, I have three instances in an environment that I want to get rid of (no longer needed). I've removed them via juju destroy-service (for 2) and a juju remove-unit (for 1). I've then done a nova delete, but juju has reprovisioned the instances. Is this expected behaviour? is there some way to work around it?11:11
mgzyes, you want `juju terminate-machine`11:13
mgzmthaddon: ^11:13
mthaddonmgz: awesome, thanks11:13
=== wedgwood_away is now known as wedgwood
ehghi - does anyone have any idea of how to get rid of zombie services/machines in the go juju DB? i.e. services that won't die, machines that are pending14:04
RAZORQHi guys14:41
RAZORQi have question about Ubuntu for phones. I Have ZTE GXI with Intel atom processor, and i want to know that, will be there ubuntu for my phone official, or i must port it on my own?14:42
=== RAZORQ changed the topic of #juju to: k
=== marcoceppi changed the topic of #juju to: Reviewer: ~charmers || Review Calendar: http://goo.gl/uK9HD || Review Queue: http://jujucharms.com/review-queue || Charms at http://jujucharms.com || Want to write a charm? https://juju.ubuntu.com/docs/charm-store.html || OSX client: http://jujutools.github.com/
=== medberry is now known as med_
=== defunctzombie_zz is now known as defunctzombie
=== defunctzombie is now known as defunctzombie_zz
vennenno(?)16:53
jamespagewedgwood, adam_g_: cached decoration and some hookenv normalization - https://code.launchpad.net/~james-page/charm-helpers/caching_hookenv/+merge/16916016:59
=== defunctzombie_zz is now known as defunctzombie
wedgwoodjamespage: we can't cache relation-get. we may want to see our own relation variables17:01
wedgwoodsame for the other relation_* commands17:02
wedgwooder, some of them anyway. the ones that call relation-get17:03
jamespagewedgwood: not sure I understand why that is?17:31
wedgwoodjamespage: if, in one part of my hook I call relation-get -r <some relation id> - <my unit name>, then relation-set -r <same relation id>, I won't see the changes if they're cached17:32
jamespagewedgwood: you can't see data in that way within a relation17:33
jamespagehmm - or maybe...17:33
wedgwoodjamespage: I'm pretty sure you can17:33
wedgwoodjamespage: I did a lot of experimenting when I wrote http://senselessranting.org/post/52242864437/juju-relations-how-do-they-work17:33
wedgwoodjamespage: you can see your own changes immedately17:33
wedgwoodthey're not committed and sent to other units until you exit the hook, but you can see your own17:34
wedgwoodnone of the rest of charm-helpers operates with that assumption, but I wouldn't want to surprise someone17:35
wedgwoodjamespage: I also have another branch that may give you similar results.17:36
wedgwoodjamespage: it's not completely finished: https://code.launchpad.net/~mew/charm-helpers/persistence17:36
wedgwoodjamespage: you could always call cached(relation_get(...)) in your own charm.17:38
jcastrowedgwood: mind if I syndicate that blog on juju.u.c?17:38
wedgwoodjcastro: by all means17:38
jamespagewedgwood: well I never even knew you could do that17:41
wedgwoodneither did I :)17:41
jamespagewedgwood: I can probably figure out how to selectively flush the cache if that happens17:43
=== defunctzombie is now known as defunctzombie_zz
SlaytorsonHow can I destroy a charm?17:55
jcastrocan you specify what you mean by destroy?17:58
jcastroas in, remove the machine it's running on or destroy the service or ... ?17:59
SlaytorsonPerhaps I meant service. Completely delete and terminate the service and all machines running it17:59
jcastrolook at destroy-service and destroy-machine18:01
SlaytorsonThanks. I did "juju --help" and nothing about destroying came about.18:01
jcastroactually, I wonder what happens when you destroy-machine before destroying a service18:01
jcastro`juju help commands` is what you want18:01
jcastrooh, which version of juju are you on?18:01
SlaytorsonNot sure. juju --version doesn't give me the version18:02
jcastroif you do "juju" and then hit enter do you get a nice list of basic commands and a link to the website?18:03
SlaytorsonSort of. I don't get anything about destroying. https://gist.github.com/bslayton/197c168321381135556e18:05
jcastroah yeah18:05
jcastroyou're on the right version then18:05
jcastrobut still crappy that we don't make --version, etc.18:05
jcastroI think I filed a bug about that18:05
jcastrohttps://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/118289818:06
_mup_Bug #1182898: Please support `juju --version` <amd64> <apport-bug> <raring> <juju-core:New> <juju-core (Ubuntu):New> <https://launchpad.net/bugs/1182898>18:06
=== koolhead11|away is now known as koolhead17
jhfhey all - I think I'm in some weird state.. after a reboot (with all my juju running and happy), when I run 'juju status' I get 'ERROR could not connect before timeout' yet 'juju bootstrap' reports 'ERROR Environment already bootstrapped' - this is using LXC containers.19:32
jhfany ideas?19:32
jhf'juju -v status' errors with Socket [10.0.3.1:60460] zk retcode=-4, errno=111(Connection refused): server refused to accept the client19:33
sarnoldjhf: I vaguely think I recall someone complaiing about their network bridge not coming back up after a reboot recently...19:41
jhfyeah… I ended up doing a destroy-environment and starting over for now..19:41
jhfbut I imagine if I reboot again it'll happen again.19:41
jcastrohttp://andrewsomething.wordpress.com/2013/06/13/introducing-bug-2-trello/20:13
jcastrom_3: marcoceppi: arosales ^^^^^20:13
marcoceppijcastro: wat. awesome20:14
marcoceppiOh, I thought it did sync stuff, it's a chrome plugin20:14
marcoceppistill, very cool20:14
thumperFunnyLookinHat: ping21:35
FunnyLookinHatthumper, howdy21:35
thumperFunnyLookinHat: hey hey21:35
thumperso21:35
thumpercontainers...21:35
FunnyLookinHatHa21:35
thumpergood progress is being made21:35
thumperbut nothing ready to test yet21:35
thumperwe have managed to get some things working with manual poking21:36
thumperbut not fully automated yet21:36
FunnyLookinHatAh interesting21:36
FunnyLookinHatAny idea on a timeline ?21:36
thumper:)21:36
thumperthat's the question isn't it?21:36
thumperas fast as possible21:36
* thumper considers carefully21:36
thumperI *think* we should have something very beta by the end of next week (hopefully(21:37
thumperthis depends on some network refactoring21:37
thumperto make sure the containers are properly addressable from the rest of the machines21:37
thumpersorry it isn't more concrete21:38
thumperbut since this is the first iteration21:38
thumperit is bound to be wrong21:38
* thumper quotes kiko - the first two times will be wrong21:39
thumperFunnyLookinHat: are you on the juju-dev email list?21:40
thumperFunnyLookinHat: I'm trying to post updates there21:40
thumperFunnyLookinHat: so, completely different question - the new ultrabook - does it have a metal outer?21:42
FunnyLookinHatSorry was AFK - had to take care of something21:42
thumperFunnyLookinHat: np21:42
FunnyLookinHatOk so - Q#1 - at some point could you give me a high level idea of how the charms would work to deploy applications within containers?  i.e. will much have to change from a standard charm?  On top of that - I'm still not sure if this means I'd put the entire LAMP stack in the container or just LAP and then do MySQL elsewhere.21:44
FunnyLookinHatRE: mailing list - I'm not - I asked for approval and never got it I believe :21:44
FunnyLookinHatRE: Ultrabook - not metal, but a VERY strong polycarbonate.  I can't bend the one sitting next to me at all if I try to twist one way or another21:45
FunnyLookinHatThe metal chassis inside is quite awesome :)21:45
thumper?! you need approval for juju-dev list?21:46
FunnyLookinHatI guess so?  I threw in my email address and it said "pending approval" - no emails yet  :)21:46
thumperA#1 - charms shouldn't need any modification *at all* - should ben entirely transparent21:46
FunnyLookinHatI used my personal, so that might be it - funnylookinhat@gmail.com - if you could approve21:47
thumperI'll take a look21:47
FunnyLookinHatthumper, ok - so charm theory follow-up.  Given that I don't care about actually "scaling" any of our deployed applications, would it make sense to have a charm wrap an entire LAMP stack?  I would _really_ like to be able to do that for security and backup purposes21:56
thumperFunnyLookinHat: I think that idea may well suit your needs very well21:56
FunnyLookinHatOk - good deal.21:56
FunnyLookinHatGotta run - but thanks for the update thumper22:04
=== wedgwood is now known as wedgwood_away
=== mramm2 is now known as mramm
=== mramm is now known as mramm22
=== mramm22 is now known as mramm

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!