/srv/irclogs.ubuntu.com/2016/08/31/#juju.txt

=== natefinch-afk is now known as natefinch
=== menn0 is now known as menn0-afk
=== menn0-afk is now known as menn0
kjackal_Hello Juju World!07:15
=== frankban|afk is now known as frankban
=== jamespag` is now known as jamespage
=== gnuoy` is now known as gnuoy
=== ant_ is now known as Guest45561
=== arturt__ is now known as arturt
KpuCkohello is it that any way to change the juju controller ip address? I've installed juju with lxdbr0 random generated network as a bridge, now i prefere to use manually created bridge to access my vm's in easy ways, so now when i type juju status, juju cannot connect to juju controller08:43
=== dpm_ is now known as dpm
magicaltroutah one of those quality days where you try and start ec2 nodes and they just fail in error :)09:39
magicaltroutanybody around who know what on earth you do in beta16 now upload-tools seems to have vanished?09:47
admcleod_magicaltrout: sync-tools instead?09:48
magicaltroutwhat the f**k09:49
magicaltroutyou need to tell your overlords to stop being so pedantic09:49
admcleod_im just guessing. i remembered upload-something was obsolete but that appears to be upload-series09:49
admcleod_also, i cant really help since im mainly using 1.2509:52
magicaltroutyou make me sad admcleod_09:52
magicaltroutget with the times09:52
admcleod_thats why im here ;) are you going to strata ny?09:52
magicaltrouti'm not. I'm doing spain and pasadena twice before the end of the year09:53
magicaltroutany more and the mrs might kill me09:53
admcleod_also are you saying --upload-tools is missing from bootstrap?09:53
magicaltroutthat is correct09:53
magicaltroutit was there in 1509:53
magicaltroutsync-tools does look suspiciously like its what its moved to09:54
magicaltroutbut it did used to live in the bootstrap09:54
babbageclunkmagicaltrout: There's a thread about it here: https://lists.ubuntu.com/archives/juju-dev/2016-August/005893.html10:05
babbageclunkI guess it was only discussed on the juju-dev list because people assumed that it was only used by devs. Oops!10:06
magicaltroutthanks babbageclunk it probably ended up in a release email somewhere I failed to read as well10:07
magicaltroutno problem10:08
rock_Hi. I deployed OpenStack on LXD using https://github.com/openstack-charmers/openstack-on-lxd. I have created "cinder-storagedriver" charm . I pushed the created charm to public charm market place(charm store). So Using JUJU GUI when i was trying to deploy "cinder-storagedriver" charm by adding relation  to "cinder" it was throwing an error.11:20
rock_ERROR: Relation biarca-openstack:juju-info to cinder:juju-info: cannot add relation   "biarca-openstack:juju-info cinder:juju-info" : principal and subordinate applications' series must match.11:20
rock_Manually , When I was deployed our charm by taking from charm store then it is able to deploy and able to add relation to cinder.11:20
rock_As part of debug,  I deployed juju-gui as $juju deploy cs:juju-gui-134 on our setup. But it was showing series as trusty even we have choosen xenial.11:21
rock_I am thinking this is JUJU-GUI issue.11:22
rock_(or) Is it some other issue? Please anyone respond to this issue.11:23
kjackalHi rock_ the series of the deployed charms should be shown on your juju status11:39
kjackalcan you make sure you have biarca-openstack and cinder charms on the same series?11:39
kjackalrock_: you are on juju 2.0?11:40
kjackalyou could choose the series with the --series flag at deploy time11:41
rock_kjackal: Hi. biarca-openstack and cinder charms are in the same series(Xenial). Yes juju 2.011:42
rock_But I can able to deploy my charm through juju cli by taking from charm store.11:43
rock_And I can able to add relation to cinder successfully.11:43
rock_When I did from Juju CLI everything working fine.11:44
D4RKS1D3Hi, I want to change the mtu of juju-br0, I changed the value of the associated interface but when i restart the machine change other time to 1500.11:45
D4RKS1D3Someone knows how to change always? the interface in /etc/networks/interfaces is in manual and i can not change in this config file.11:46
rock_kajackal: But from JUJU gui, I am not able to add relation to cinder . It was giving   ERROR: Relation biarca-openstack:juju-info to cinder:juju-info: cannot add relation   "biarca-openstack:juju-info cinder:juju-info" : principal and subordinate applications' series must match.11:47
kjackalrock_: where is your cinder-storagedriver charm?11:47
kjackalrock_: can I see it?11:47
rock_Yes. Type  "biarca"  in charm store.11:48
kjackalrock_: this one: cinder-storagedriver11:49
kjackalrock_: this one: https://jujucharms.com/u/siva9296/biarca/011:49
kjackalrock_: Looks ok to me. You could ask at #juju-gui and #openstack-charm . It might be a bug11:51
rock_kjackal: ok. Thank you.11:54
magicaltroutT-1hour12:00
magicaltroutstill working on my demo \o/12:00
PCdudehé magicaltrout , hru?12:09
magicaltroutlol12:09
magicaltrouttired... still hacking12:09
magicaltroutyou know12:09
magicaltroutthe usual before a 50 minute presentation ;)12:09
PCdudehaha, 50 minutes and u are wasting time here ;) , good time managment12:10
PCdudebut anyway, good luck!12:10
magicaltroutthanks :P12:10
marcoceppigood luck magicaltrout12:10
magicaltroutaye... then i need to come back to the speakers room and start tomorrows :P12:11
magicaltroutwhich you guys claim to want to film and slap on youtube... never good12:11
magicaltroutwoop thanks for that dump cmars12:31
magicaltroutit started working12:31
cmarsmagicaltrout, awesome!12:31
magicaltroutdon't think i got my original config.yaml stanza correct12:31
admcleod_magicaltrout: good luck12:48
lazyPowermagicaltrout knock em downnnn12:53
admcleod_break someones leg12:54
marcoceppismash 'em mash 'em stick 'em in a stew!12:56
marcoceppior, whatever12:56
admcleod_ill take 2 whatevers12:58
lazyPowerpetevg Thanks for https://github.com/juju/docs/pull/131712:59
lazyPowerpetevg looks good from my house, and it gets us some proper representation of what charmers should be thinking about as they organize and structure their modules.13:00
kjackalhey petevg, are you there?13:02
magicaltroutall done13:45
magicaltroutnot a bad turn out, must have been 30 odd13:45
admcleod_did you tell any jokes?13:49
magicaltroutI don't believe i did13:50
magicaltrouti did ask who'd heard of Juju13:51
magicaltroutand a whole 2 hands went up13:51
RandlemanNice13:52
magicaltroutnow i need to write my talk and demo for tomorrow :P13:53
jrwrenmagicaltrout: were they your two best friends, or were they complete strangers?13:57
magicaltroutpfft13:57
magicaltroutactually  the only guy i knew in the room was a guy that hacks on Karaf in his spare time13:58
magicaltroutnot got many friends at this one =/13:58
magicaltroutanyway! in reality whilst we all wish everyone knew of and used juju at talks its probably better to talk to a room of people who don't know what it is13:59
magicaltrouthell, it was in my talk title and still 30 people showed up ;)13:59
jrwrenmagicaltrout: well, that is pretty good then!13:59
magicaltroutaye14:00
magicaltroutand appears 30odd are likely to turn up tomorrow to my Business Intelligence juju talk14:01
magicaltroutso at least its getting faces in front of the software14:01
magicaltroutappears to be standing room only at Bluefin tomorrow night14:05
magicaltroutbetter come up with something half decent then14:05
petevgkjackal: I am here, though apparently I'm not paying attention to my IRC client ...14:13
kjackalpetevg: :)14:14
petevgkjackal: I just pushed a new revision of the Zookeeper charm. If those timeouts are legit, it should fix them.14:14
kjackalI wanted to ask you something on the zookeeper charm14:14
petevgkjackal: ask away.14:14
petevglazyPower: thank you for the positive feedback on that testing PR :-)14:15
kjackalI see that now the zookeeper waits for a service restart when new units are added14:15
petevgkjackal: It does. We did that because the Zookeeper docs advised that it's not always stable after removing or adding units.14:16
kjackalpetevg: have you tested this behaviour with the HA bundles that expect ZK to have 3 units?14:16
petevgkjackal: I haven't. That is a very good test to add to the bundle tests.14:16
kjackalpetevg: Yes I remember that, I am not sure how this behavior will play along with the hadoop processing and the rest of the bundles14:16
petevgkjackal: it probably will function well. The Zookeepers don't stop working as they're waiting for the restart. They just won't pick up new peers until you do the restart.14:17
kjackalHm... so we need the restart to have Zookeeper HA14:18
petevgkjackal: if you specify three zookeepers in your bundle, I believe that this works around the issue; Zookeeper will only wait for a restart if it has already setup a quorum that then changes.14:19
petevgLet me verify that ...14:19
kjackalI have tested "juju deploy zookeeper -n 3" and the restart is needed there14:20
valeechSorry guys. I just registered for the charmers summit. I hope I don’t hold back too many people :)14:20
kjackalpetevg: And what happens upon restart? Do the ZK records of all peers get merged?14:21
petevgkjackal: I'm not sure what Zookeeper does internally. I just know that the docs advise that you do a rolling restart after you've changed the number of peers.14:21
petevg... if you don't, in the Zookeeper version that we're using, a job can get left without a peer to attach to.14:22
petevgkjackal: darn it. You're right about the peers needing a restart even on setup. I bet that the timing of things changed when we ripped out the openjdk relation :-/14:27
jamespagemarcoceppi, hey - I need to add uosci-testing-bot to the charmers team to support our automated push/publish process for promulgated charms - is that OK with you?14:45
marcoceppijamespage: you don't actually need to do that14:47
marcoceppijamespage: we can just give uosci-testing-bot write access to the charms that it needs to publish14:47
jamespagebeisner, ^^14:47
jamespagemarcoceppi, oh yeah that's a good idea14:48
jamespagebeisner, ^^14:48
* jamespage faceplatns14:48
marcoceppibeisner jamespage just give me a list of entities and I'll give you guys the commands, I'm sure a few of your are still ~charmers ;)14:48
beisnerjamespage, marcoceppi - hrm yah, looks like perms are good for some of them, but not all, for the bot user.14:48
marcoceppibeisner jamespage tl;dr: charm grant <charm> --channel stable --acl write uosci-testing-bot14:49
beisnerack marcoceppi thank you14:50
valeechrunning juju2.0beta15 when trying to deploy to lxd container, I get the following error: 'failed to ensure LXD image: unable to get LXD image for ubuntu-xenial: The requested image couldn''t be found.' If I ssh into the machine and run “sudo -E lxc launch ubuntu:16.04” it starts just fine. Here is the yaml file I am using to deploy: http://pastebin.com/hzx6icGk14:54
magicaltroutitsn't it some naming thing14:55
magicaltroutisn't14:55
magicaltroutlike14:55
magicaltroutyou download the image and tag it with a custom name, in your case ubuntu-xenial14:55
magicaltroutits been a while, my memory might be failing me14:55
petevgkjackal: on that failing zookeeper test run, are there tracebacks in the juju logs?14:56
valeechmagicaltrout: That makes sense. I am learning so I am cutting and pasting from different sources and I bet that is the case.14:57
kjackalpetevg: I am afraid not14:57
magicaltroutvaleech:14:57
magicaltroutif you run14:57
magicaltroutlxc image list14:57
magicaltroutyou'll see the alias column on the left14:58
magicaltroutthats what it uses14:58
valeechmagicaltrout: I see that. How do you set that on newly created machines from maas?14:59
magicaltrouterm14:59
magicaltroutwell you do it when you do an image pull14:59
magicaltroutdoes that happen in MAAS or is it magic?14:59
valeechmagicaltrout: It is very possible there is a gap in my understanding, but doesn’t maas deploy a vanilla image on the machine then hand it over to juju? At that point, juju would need to pull down whatever images it needs for lxd?15:01
magicaltroutah yeah, now i get you15:01
magicaltroutso this is during juju bootstrap?15:02
magicaltroutor post bootstrap?15:02
magicaltroutlike, if you do a juju bootstrap it should just dump it on the metal15:02
magicaltroutso no lxd involved to my knowledge15:02
valeechCorrect. I have a new juju model setup and I am trying to deploy my first charm to a container. So juju has to get a machine from maas to work with15:02
magicaltroutk15:03
valeechthat part works. when juju tries to setup the container to push the app to the container fails to start.15:03
magicaltroutwell, i asked around the other day and my understanding was that whilst it needs an image, thats not a lxd image15:03
magicaltroutokay, so you have MAAS spin up a node, then you try and push a LXD charm to it?15:04
valeechKinda. juju asks maas to spin up a node which will become machine 0 in juju. Then juju attempts to initialize a container on machine 0 which would become machine 0/lxd/0 in juju. Then juju would push the charm to that container.15:05
magicaltrouti'm sufficently confused, I tried to get MAAS running on virtualbox the other day and it failed, but i did ask around and was told that if you "juju deploy mycharm" it would go onto the bare metal not a lxd container15:07
skaydoes mojo with with juju2 yet?15:07
lazyPowervaleech - there has been a ton of work around that. this is juju 2.0-beta16 right?15:07
lazyPowerskay - last i heard it was still 1.25 only15:07
valeechThat is correct. It will deploy to bare metal. I am trying to get the next step which is deploy inside a container on the bare metal.15:08
skayaw15:08
valeechlazyPower: it is beta 15. I can load beta 16.15:08
lazyPowershouldn't make too big of a difference.15:08
lazyPowerdo you have logs from the container thats failing to start?15:09
magicaltroutvaleech: i'd update anyway15:09
magicaltroutbecause the charm store will make your instance explode as soon as you get going :)15:09
valeechok, I will update. as far as container logs, how would I go about getting those?15:09
valeechhaha15:10
babbageclunkvaleech - I've seen that as well - I think it's resolved by beta16.15:21
valeechbabbageclunk: great. I am upgrading to beta16 now but having some trouble...15:22
babbageclunkvaleech: trouble?15:35
valeechbabbageclunk: I don’t think I upgraded properly. I did an apt-get upgrade juju which upgrade the juju client host to beta16. Then in the controller model I did juju upgrade-juju. It said is was upgrading but when I would issue a juju status I would get this error: “ERROR invalid entity name or password (unauthorized access)” Maybe I didn’t wait long enough?15:39
babbageclunkvaleech: hmm - I'm not really familiar with using upgrade-juju. Are you in a position where you can rebootstrap instead?15:40
valeechbabbageclunk: That is what I did :) It is adding my redundant controllers right now from juju enable-ha.15:41
babbageclunkvaleech: ok cool - so things are looking alright at the moment?15:42
valeechbabageclunk: everything looks good. About to deploy this charm to the container and see what happens.15:44
babbageclunkvaleech: fingers crossed.15:46
valeechbabbageclunk: it spun up the container!! Now it’s installing the charm :)15:53
* babbageclunk dances15:54
valeechbabbageclunk: Woohoo! mysql/0  active    idle   0/lxd/0  10.0.129.59            Unit is ready15:56
valeechmany thanks to babbageclunk, magicaltrout and lazyPower15:56
jaceknis threre a known problem with "charm build" not working any more? I'm getting "ERROR unrecognized command: charm build" when I try to compose charm using charm 2.1.1-0ubuntu115:58
lazyPowernice valeech15:59
lazyPowerjacekn - try charm-tools from the snap channels16:00
jaceknlazyPower: ah that could be it, thanks16:00
magicaltroutjacekn: also it got broken into  a bunch of binaries16:24
magicaltroutcharm-build16:24
magicaltroutfor example16:24
jaceknmagicaltrout: tha's fine as long as dependencies and/or sensible error messages are there16:27
magicaltroutsensible error messages?16:27
magicaltroutthis is juju16:27
valeechok, next challenge, how do I set the lxd container to use a specific bridge? when juju created it inside of machine 0, lxdbr0 was added to machine 0 with what looks like a random IP segment. Is there a mechanism that I can tell juju to use a specific interface for containers so I can make sure the containers end up inthe correct IP segment?16:31
PCdudemagicaltrout:  how did it go?16:37
magicaltroutnot  bad PCdude16:37
magicaltrout30 odd people and i streched it out to  40 mins16:37
magicaltroutso i guess  it was a success16:37
PCdudesounds like a succes16:37
magicaltroutjust tomorrow to do now16:37
PCdudewhats tomorrow?16:38
magicaltroutbusiness intelligence and juju talk for a user group in london16:38
PCdudeah ok, u keep urself busy haha16:38
magicaltroutinitially both talks were on the same day16:39
magicaltroutone in ams one in london16:39
PCdudewell it is possible, but convenient is something else16:39
PCdudemagicaltrout:  let me ask u, sometimes questions on stackexchange takes years before they get answered and on IRC is sometimes hard too to find answers, were do u go when u have questions?16:42
magicaltroutIRC16:42
magicaltroutmailing lists16:42
magicaltrouti do  a lot of  apache stuff16:43
magicaltroutthats all mailing lists16:43
PCdudeI never used mailings lists, how does that work exactly?16:43
magicaltroutyou sign up16:44
magicaltroutand send emails16:44
magicaltrout... mailing.... lists ;)16:44
babbageclunkvaleech: I'm not sure - I think the best people to help you have dropped off for the day, sorry.16:44
magicaltroutPCdude: juju relies heavily on IRC and mailing lists16:47
magicaltroutif people are offline on IRC16:47
magicaltroutyou generally post to the list and get an answer there16:47
magicaltroutdepends on the project though, not all use mailing lists but many do16:47
PCdudemagicaltrout: ah ok, so if I am correct, I add my e-mail address there and when I have a question that e-mail is send to anyone in that list?16:48
PCdudeand anyone can repond to that mail16:48
magicaltrouthttps://lists.ubuntu.com/mailman/listinfo/juju16:48
magicaltroutyou subscribe there16:48
magicaltroutthen you will recieve mails sent to the list16:48
magicaltroutand you can send to the list16:48
PCdudebut on what speed are those e-mails send? I mean a regular forum goes so fast that means 5 mails a second16:49
magicaltroutfew a day16:50
joseit's a discussion list. not extremely heavy volume, but not as low as an announcement only list.16:50
magicaltroutPCdude: i get about 800 a day from apache projects, you'll be fine ;)16:51
PCdudeah ok, good to know, lets not use my primary mail address haha, I just wanna get closer to the heat :)16:51
holocronhi all, quick question i hope.. I already have some machines that are added to my model and I'd like to specify them sa the targets in a juju bundle16:51
magicaltrouti just have  a bunch of filters16:52
holocronthe machines were manually added:16:52
holocronwhenever i attempt to deploy a bundle, it goes and tries to make 4 more machines, but i'd rather it just used the 4 i already have16:53
magicaltroutholocron: you probably need to use --to:... in the deploy stanza16:53
magicaltroutto tell it where to go16:53
holocronmagicaltrout: sure I can direct charm deployment to the machines16:54
holocronbut i want to do it from a bundle16:54
magicaltrouti suspect you're out of luck16:54
magicaltroutbut lazyPower might know better16:54
* lazyPower reads scrollback16:55
lazyPowerbundle machine #'s dont necessarily correspond to machine #'s already in the model16:55
lazyPoweri'm not certain how to do that other than to use maas tagging holocron, but that assumes you're using the maas juju provider16:55
holocronunfortunately i'm not lazyPower, I'm using the lxc provider16:56
=== frankban is now known as frankban|afk
holocronlazyPower, can you tell me where some of this might be documented better? https://jujucharms.com/docs/devel/charms-bundles is not very telling17:17
holocronin particular, i'm looking for the specification on placement directives17:21
lazyPowerholocron - that seems bug worthy holocron. If you dont mind opening a bug at http://github.com/juju/docs/issues with the specifics you're looking for I can make sure we get it addressed17:31
holocronlazyPower okay.. i think i answered my own question after reading the page i linked for a 2nd time17:32
holocronthere's simply no way to use a pre-defined machine directly from a bundle unless it's MAAS controlled?17:32
lazyPowerholocron - can you pastebin me your bundle?17:33
kwmonroepetevg: i notice you have a convention with branch names at https://github.com/juju-solutions/layer-apache-bigtop-base.  i'd like to adopt it.. what are your keys?  i see bug/foo and feature/foo.  anything else?17:35
petevgkwmonroe: I've just been using bug and feature. If you have something that doesn't fit, feel free to add a word, and let me know about it, so that I can use it, too :-)17:36
holocronlazyPower http://pastebin.com/getn0Vzm17:36
holocronthat isn't importable due to "The following errors occurred while retrieving bundle changes: placement "3" refers to a machine not defined in this bundle.." etc etc17:36
holocroni have machines 1-4 defined to juju already17:37
holocronbut there's no way to indicate them from the bundle it seems17:37
cory_fukwmonroe, petevg: If there is a corresponding bug / issue number, what do you think about including it in the branch name so that it's easy to associate them?  Something like "feature/123-foo"?17:37
petevgcory_fu: that's officially part of the convention that I've borrowed, though I'm not always great at remembering. I'll try to be better about it :-)17:39
cory_fuOh, I didn't realize.  Carry on, then17:39
kwmonroecory_fu: i think the 123 won't be useful in practice.  how would you know if it was a gh issue, lp bug, or jira?17:40
cory_fukwmonroe: Hrm.  What about feature/gh-123/foo?17:41
kwmonroei suppose you could say bug/gh123-foo, feature/lp-bug... heh.. yeah cory_fu17:41
lazyPowerholocron - i think this is a regression.  Bugs would def. be welcome around this so we can get eyes on it.17:41
holocronokay lazyPower, i'll open a bug .. LP or github?17:41
cory_fukwmonroe, petevg: Actually, is knowing that something is a feature vs bug useful info?17:41
lazyPowerhttps://launchpad.net/juju/  would be preferrable, if its closed fairly quickly with instructions we can port those into the docs.17:42
kwmonroei think so cory_fu.. i (will) tend to look at bug branches before features.. i think.17:42
cory_fuAlso, should we worry about cleaning up our branches after they're merged?17:42
cory_fukwmonroe: Fair enough17:43
lazyPowerI'm a +1 for cleaning up branches after merging17:43
lazyPowerbut nobody asked me :)17:43
cory_fulazyPower: We appreciate your input all the same, you special snowflake, you. ;)17:43
kwmonroe+1 for lazyPower being a good person.  and yes cory_fu, i'm all about deleting branches, whether they're merged or not.17:44
cory_fulol17:44
kwmonroe;)17:44
cory_fuI should create a bot that deletes kwmonroe's branches as soon as he pushes them17:44
petevgI'm merciless about cleaning up branches locally.17:44
petevgI would be down with cleaning them up remotely, too.17:44
lazyPower@cory_fu have you seen: https://github.com/jfrazelle/ghb0t17:44
cory_fuI wish GH had a "Merge and delete this branch" button17:45
petevgThat actually fixes the issue where you squash a branch to get it ready to merge, and then you confuse someone who has the branch checked out locally.17:45
petevgIf the branch is just gone, the error is much less confusing.17:45
petevgcory_fu: the delete button does appear right after you click the merge button ... but yeah, it would be nice to do it in one go.17:45
cory_fulazyPower: Nice17:45
kwmonroeok cory_fu petevg kja-tab-tab-tab, so here's our new thing:  branches are bug/lp-123/<short-desc>, feature/gh-123/<short-desc>, bug/jira-123/<short-desc> and the merger deletes the branch.  sound good?17:46
cory_fu+117:46
lazyPowerLOL @ tab-tab-tab17:46
petevgOoh. Extra forward slashes. Makes it look all neat and organized.17:46
lazyPowerRIP17:46
petevg+1 :-)17:46
kwmonroeaight cory_fu petevg, wiki step 2 updated: https://github.com/juju-solutions/bigdata-community/wiki/Bigtop-Patch-Process17:53
petevgNice!17:53
holocronhttps://bugs.launchpad.net/juju/+bug/161899617:56
mupBug #1618996: unable to specify manually added machines from bundle.yaml <juju:New> <https://launchpad.net/bugs/1618996>17:56
lazyPowerjcastro ping18:00
Prabakaranhello Team, I am not getting any proper info on the error when i am using make lint command on the build charm. I meant, make lint command is not showing from which file i am getting these error. Could someone please explain me on this?18:03
=== rmcall_ is now known as rmcall
kwmonroePrabakaran: will you pastebin your charm's Makefile and 'make lint' output?18:06
Prabakaranya sure kwmonroe18:06
lazyPowerholocron thanks, i'll bring this up18:06
Prabakarankwmonroe: i have pasted here http://pastebin.ubuntu.com/23117014/18:07
kwmonroeah, that's an easy one Prabakaran :)  your machine is out of space.. what does "df -h" show?18:08
Prabakarankwmonroe: link is here http://pastebin.ubuntu.com/23117020/18:09
kwmonroeyup Prabakaran.. your / filesystem at /dev/sda3 is 100% full18:09
Prabakarankwmonroe: you meant all these error are because of memory of the machine18:10
kwmonroeyup Prabakaran.  the "apt-get install $apt_prereqs" failed because it didn't have enough space to write data to /var/lib/apt.18:11
magicaltroutsad times18:12
Prabakaranthanks kwmonroe18:12
Prabakarani wil clear my machine space and try this out18:12
kwmonroenp Prabakaran.  if you've downloaded any charms from magicaltrout, i'd suggest deleting those first.18:13
Prabakarankwmonroe: magicaltrout means?18:13
kwmonroeheh, sorry Prabakaran.. it was a joke.  magicaltrout is the guy in this channel that causes so many problems.  i like to blame all things on him first ;)18:14
magicaltroutlol18:14
Prabakaranthats no problem :)18:14
magicaltroutkwmonroe: you're so mean18:58
magicaltroutyou make me sad18:58
magicaltroutin other todos... graylog, we should get graylog onto juju18:58
kwmonroepretty sure it's the weather that's making you sad magicaltrout.  you need southern california stat.18:59
magicaltrouthehe18:59
magicaltroutour summer has been very nice18:59
magicaltroutcompared to the last few years18:59
magicaltroutbut i do need southern california19:00
magicaltrouti even have a car god help you all19:00
x58stub: Are you stub42 on Github?19:27
PCdudemagicaltrout:  for some weird reason is the MAAS error gone now :D19:32
magicaltroutmagic19:34
magicaltrouttold you PCdude we all have those19:34
PCdudemagicaltrout: best guess is something with the networkcard, when installing with only one card it fails, but thats it and frankly I dont care anymore it works now19:35
x58Is there a helper in charmhelpers for restarting  a systemd service?19:51
lazyPowerx58 - i think thats a missing feature, however there is a juju-reboot hook tool that will safely reboot a unit in the context of juju + containers that may be running on the host (lxd based)20:17
lazyPowerx58 https://jujucharms.com/docs/stable/reference-hook-tools#juju-reboot20:23
x58lazyPower: I found charmhelpers.core.services.base which has service_restart which is a wrapper around charmhelpers.core.host.service_restart20:38
x58or something like that.20:38
x58Anyway, my @when_file_changed hook correctly restarts my service.20:38
x58As for other accomplishments... published my second charm today =)20:39
x58https://jujucharms.com/u/bertjwregeer/snmpd20:39
lazyPowernice! ^520:39
x58^520:39
lazyPoweroo your readme is from teh apt layer20:40
x58marcoceppi: https://jujucharms.com/u/bertjwregeer/snmpd (another charm built in anger ;-))20:40
x58Refresh a couple of times..20:40
x58It should show my .rst20:40
x58which isn't rendered ;-)20:41
x58Unless I need to make cs:~bertjwregeer/snmpd-2 public? Although I am not sure that should be required since I can see it...20:41
marcoceppix58: weird the RST isn't rendering, this might be a bug in our GUI20:44
x58marcoceppi: It is. I have an open bug for it on Github20:44
x58marcoceppi: https://github.com/CanonicalLtd/jujucharms.com/issues/31320:46
marcoceppix58: cool thanks!20:46
marcoceppicharm looks awesome though20:46
x58Thanks :-)20:47
x58Ultimately ended up being fairly simple, but the docs aren't all that nice to get to that point ;-)20:47
x58Also, charm proof is angry that I don't have any "provides", but I am not sure what my charm would provide exactly.20:48
kwmonroecory_fu: halp!!20:55
cory_fukwmonroe: What up?20:55
kwmonroecory_fu: http://paste.ubuntu.com/23117537/20:55
kwmonroethat's pip 8.1.2 in charmbox.. is it me pip or me python-distutils-extra?20:55
cory_fukwmonroe: Do you have an old version of the layer:apt?20:57
x58marcoceppi: BTW, even with layer.yaml in layer:apt having ignore: ['README.md'] in my layer.yaml won't let charm build succeed.20:58
cory_fukwmonroe: Or a modified version?  There's no wheelhouse.txt file in the apt layer20:59
=== natefinch is now known as natefinch-afk
kwmonroeyeah cory_fu.. i think you're right21:00
kwmonroe(rebuilding)21:00
kwmonroeall good kwmonroe21:01
kwmonroeheh21:01
kwmonroederp21:01
kwmonroeall good cory_fu21:01
cory_fu:)21:01
kwmonroeyou were right.. this time ;)21:01
lazyPower kwmonroe - you can embed github repos in a wheelhouse like the openstack-layer has done - https://github.com/openstack/charm-layer-openstack/blob/master/wheelhouse.txt21:04
lazyPowerjust fyi21:04
kwmonroegracias lazyPower!21:06
lazyPoweranytime homie21:06
kwmonroetwo Ms in hommie, hommie.21:06
x58Cue "you are not my hommie, pal" :P21:09
kwmonroelol21:14
lazyPowerdont call me buddy, guy!21:14
x58Abbott and Costello. My favourite still has to be whose on first.21:15
lazyPowerthats better than my weak reference to an old adam sandler routine before he lost any sense of credibility :)21:18
x58lol21:19
x58For those nostalgic: https://www.youtube.com/watch?v=kTcRRaXV-fg21:20
catbus1Hi, is agenda available for the upcoming juju charmers summit?22:31
marcoceppicatbus1: yes, a tentative one is22:33
catbus1marcoceppi: Can I see it now and share with an attendee from a technology partner company? Or is it too early to share now?22:36
marcoceppicatbus1: nope, we mailed the Juju mailing lits on it22:42
marcoceppicatbus1: https://lists.ubuntu.com/archives/juju/2016-August/007743.html22:43
catbus1marcoceppi: thank you!22:43
bdxmarcoceppi: I seem to be hitting some kind of limit on my aws charm-dev account -> http://paste.ubuntu.com/23118016/22:48
bdxmarcoceppi: can you clear out my instances ... or something ..22:49
bdxpls22:49
rajithhi while bootstraping on juju2 beta 16 getting error : ERROR cmd supercommand.go:458 creating LXD client: Get https://10.35.77.1:8443/1.0: Unable to connect to: 10.35.77.1:8443 ERROR failed to bootstrap model: subprocess encountered error code 123:21
bdxrajith: you need to run `sudo lxd init` again, and configure lxd for api access23:37
bdxrajith: to my knowledge, this means you need to first wipe your existing lxd containers23:38
bdxrajith: and images23:39
bdxmbruzek: http://paste.ubuntu.com/23118148/23:49

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