[00:25] <marcoceppi> agunturu: you can juju action status <UUID> or juju action fetch <UUID> to get more details
[00:31] <metsuke> does anyone use juju with a cinder backend and find it to be robust?
[09:39] <Razva> hey! is there any know bug regarding network interfaces not named eth?
[10:21] <axino> hi charmers, can I get your attention on https://code.launchpad.net/~chris-gondolin/charms/trusty/nrpe/fix-sub-postfix/+merge/285692 ? cc gnuoy` thedac
[11:31] <jamespag`> gnuoy, working through beisner's 16.02 testing sweepup merges
[11:32] <gnuoy> jamespag`, ah, ok. I said I'd do that if you want to leave that to me
[11:32] <jamespag`> gnuoy, i have cycles inbetween things
[11:32] <gnuoy> kk, thank you
[11:43] <Razva> hey! is there any know bug regarding network interfaces not named eth?
[11:43] <magicaltrout> thats like the most cryptic question ever
[11:44] <jamespag`> beisner, gnuoy: hey can we switch amulet test cases to use /usr/bin/env python instead of /usr/bin/python?
[11:44] <jamespag`> I'd like to be able to execute them in a venv (think under tox) but right now that's not possible
[11:44] <gnuoy> jamespag`, I have no objection
[11:45] <Razva> magicaltrout I'm using Ubuntu 14 and trying to install OS using Juju. It seems that as long as I'm using ethX...the install will work. If I use the "native" naming (enoX, emX etc) it will basically...fail.
[11:45] <Razva> OS = OpenStack
[11:45] <magicaltrout> jamespag` and co are your people for that ;)
[11:46] <jamespag`> Razva, can we see a log?
[11:46] <jamespag`> will help with triage as to where you problem lies...
[11:48] <jamespage> I was developing a tick
[11:48] <magicaltrout> painful
[11:51] <jamespage> beisner, your landme's are landed
[11:51] <Razva> darn netsplits.
[11:52] <marcoceppi> magicaltrout: I shot over a pull req https://github.com/OSBI/juju/pull/1
[11:52] <magicaltrout> its like the 90's all over again
[11:52] <marcoceppi> I really want m4 instance types in Juju
[11:52] <magicaltrout> Razva: if you didn't see james asked for a pastebin log
[11:53] <magicaltrout> oh thats mine marcoceppi thanks for that, I just ignored it as I assumed it was against the pull i submitted :)
[11:53] <marcoceppi> magicaltrout: our builder will fail pull req that haven't been formated according to golangs `go fmt`
[11:54] <magicaltrout> ah
[11:54] <magicaltrout> sorry about that
[11:54] <marcoceppi> wallyworld: this has been updated https://github.com/juju/juju/pull/4426 any chance we can get a JFDI?
[11:55] <wallyworld> marcoceppi: np, doing it now
[11:55] <wallyworld> will be in beta1
[11:55] <marcoceppi> wallyworld: \o/
[12:24] <jamespage> gnuoy, which bits of https://pastebin.canonical.com/148351/ still need review?
[12:26] <jamespage> beisner, yah - https://code.launchpad.net/~james-page/charms/trusty/neutron-gateway/xenial/+merge/285862
[12:26] <jamespage> has some more bits there as well
[12:26] <beisner> jamespage, ah good deal
[12:51] <wallyworld> marcoceppi: merged \o/
[12:51] <marcoceppi> woop woop!
[12:51] <marcoceppi> thanks for the fix magicaltrout
[12:52] <magicaltrout> sweet
[12:52] <magicaltrout> hopefully I'll find some time to actually learn some go and do something more exciting than copy and paste
[12:53] <magicaltrout> right, I have a quick one about publishing and stuff that I don't quite get
[12:53] <magicaltrout> so I have a charm in github
[12:53] <magicaltrout> and supposedly I can publish that to the charm store
[12:55] <magicaltrout> so in my local repo I can run: juju publish --from=. cs:~f-tom-n/trusty/gitlab cs:~f-tom-n/trusty/gitlab
[12:55] <magicaltrout> or something like that?
[12:55] <magicaltrout> even though I've not created anything in launchpad or bzr?
[12:58] <marcoceppi> magicaltrout: theoretically, yes, it'll look something like this:
[12:58] <magicaltrout> nice caveating
[12:58] <marcoceppi> charm push .
[12:59] <marcoceppi> since the charm command knows who you are, and the name of the charm it'll just upload to cs:~f-tom-n/trusty/gitlab
[12:59] <marcoceppi> the new charm 2.0 stuff is private beta atm, but I can see about adding you if you're interested
[13:00] <magicaltrout> hmm someone lied then and told me I could do it! :P
[13:00] <marcoceppi> you could do it, if you have early access to the tool - I imagine we're pretty close to public beta though esp since we're submitting them to Xenial
[14:28] <magicaltrout> hello there people who know more than I do
[14:29] <magicaltrout> submitting a layered charm
[14:29] <magicaltrout> how on earth do you do it?
[14:29] <magicaltrout> or do you submit the built thing?
[14:29] <rick_h_> magicaltrout: you submit the built thing
[14:29] <magicaltrout> k
[14:29] <rick_h_> magicaltrout: and submit any layers you've added to http://interfaces.juju.solutions/
[14:29] <rick_h_> if they're useful to others out there
[14:39] <lazyPower> or  include in your finally assembled charms readme a breadcrumb trail back to your upstream layers source control system for bug reporting purposes, and the ~charmers will appreciate your attention to detail.
[14:40] <magicaltrout> ah yeah good point
[14:50] <icey> any support yet for controlling a remote lxd controller / juju env from an OSX host? The lxd machine would be running Xenial and be accesible over a local network
[14:51] <beisner> icey, that would just rock.  better yet, control multiple remote lxd hosts and voila, a rockin local cloud.
[14:52] <icey> beisner: yes, that is why I'm excited about lxd!
[14:52] <icey> I'm trying to set it up from the release notes now :)
[14:52] <rick_h_> icey: no, we'll look at adding more awesome lxd support, but it'll happen in the next cycle
[14:52] <icey> awww rick_h_ :(
[14:54] <icey> looking at the docs I'm not sure why I couldn't use the remote lxd host?
[14:55] <rick_h_> icey: it might be something you can hack up. I just think the juju provider assumes it's a local lxd
[14:55] <icey> rick_h_: it looks like there's config for remote-url so I'm hopeful :)
[14:55] <rick_h_> icey: let me know how it goes. I've been wrong before, but thought that didn't make the current cut for feature freeze
[14:56] <icey> if I get it working, I'm blogging about it because it'll be like LOCAL PROVIDER ON A MAC!
[14:56] <icey> lazyPower: ^^
[14:56] <rick_h_> even better :)
[14:56] <lazyPower> icey: you said the magic word!
[14:57] <lazyPower> man its 2016 and i have cut exactly 0 blog posts :/ i feel like i'm slackin
[14:57] <rick_h_> lazyPower: I'm comin for you!
[14:57] <lazyPower> oye?
[14:57] <rick_h_> lazyPower: for blog posts :P
[14:57] <rick_h_> lazyPower: need to get you doing one on resources maybe. Surely you've got some charm that can use it :P
[14:57] <lazyPower> tempt me with a good time whydontchya :D
[14:58] <lazyPower> I have a few ideas
[14:58] <lazyPower> and a weekend to make it happen
[14:59] <rick_h_> lazyPower: good stuff, just giving you a hard time :)
[15:01] <icey> so far so good, rick_h_:
[15:01] <icey> ./juju bootstrap -m lxd
[15:01] <icey> Bootstrapping model "lxd"
[15:01] <icey> Starting new instance for initial controller
[15:01] <icey> Launching instance
[15:01] <icey> from my mac
[15:01] <icey> :)
[15:01] <rick_h_> icey: interesting
[15:02] <icey> $ lxc list
[15:02] <icey> +-----------------------------------------------------+---------+------------------+------+-----------+-----------+
[15:02] <icey> |                        NAME                         |  STATE  |       IPV4       | IPV6 | EPHEMERAL | SNAPSHOTS |
[15:02] <icey> +-----------------------------------------------------+---------+------------------+------+-----------+-----------+
[15:02] <icey> | juju-12f338d5-04f6-4628-88cb-0d18179c8d74-machine-0 | RUNNING | 10.0.4.97 (eth0) |      | NO        |         0 |
[15:02] <icey> +-----------------------------------------------------+---------+------------------+------+-----------+-----------+
[15:02] <icey> on the remote host :)
[15:02] <suchvenu> Hi Kevin
[15:03] <jacekn> kjackal: cory_fu: hey. Thank for the review, I updated my collectd layer so if any of you has time I would love re-review: https://bugs.launchpad.net/charms/+bug/1538573
[15:03] <mup> Bug #1538573: New collectd subordinate charm <Juju Charms Collection:Triaged> <https://launchpad.net/bugs/1538573>
[15:06] <jose> question, let's say I have a config value that I want to be different for each instance, is there a set it with juju set?
[15:06]  * icey sadface
[15:06] <icey> lazyPower rick_h_: 2016-02-17 15:05:19 ERROR cmd supercommand.go:448 no registered provider for "lxd"
[15:06] <icey> ERROR failed to bootstrap model: subprocess encountered error code 1
[15:07] <icey> that's after we downloaded the tools
[15:08] <icey> that's also in the cloud-init-output.log on the lxc container started to be the controller
[15:09] <icey> but I can bootstrap this lxd environment from on that host
[15:11] <kjackal> Thank you for your effort jacekn , I just changed the status of the bug ticket to new so that it comes back up on the review queue (I think it is needed)
[15:11] <kjackal> I haven't seen anything like this jose
[15:11] <icey> jose: the closest you will probably get is to deploy the charm multiple times to give them different configuration values as all units share the same configuration
[15:12] <jose> right, right. I'll experiment a bit with actions and otherwise juju run. thanks!
[15:23] <marcoceppi> icey: use --upload-tools
[15:23] <icey> marcoceppi: ERROR failed to bootstrap model: no matching tools available
[15:23] <marcoceppi> icey: that was /with/ upload-tools?
[15:23] <icey> that may be the part that rick_h_ says is missing right now
[15:23] <icey> yes marcoceppi, it gets a LOT farther without upload tools
[15:23] <marcoceppi> what.
[15:23] <icey> goes through to ERROR cmd supercommand.go:448 no registered provider for "lxd"
[15:24] <icey> marcoceppi: machine I'm trying to bootstrap from is a Mac
[15:24] <icey> if that helps
[15:25] <marcoceppi> icey: you've got alpha2?
[15:25] <icey> 2.0-alpha2-elcapitan-amd64
[15:25] <icey> marcoceppi:
[15:26] <jamespage> wolsen, re https://bugs.launchpad.net/charms/+source/cinder/+bug/1468306
[15:26] <mup> Bug #1468306: Missing os_region_name for mult-region cinder with nova <cpec> <hitlist> <openstack> <sts> <cinder (Juju Charms Collection):Fix Committed by billy-olsen> <nova-cloud-controller (Juju Charms Collection):In Progress by billy-olsen> <nova-compute (Juju Charms Collection):In Progress by
[15:26] <mup> billy-olsen> <https://launchpad.net/bugs/1468306>
[15:26] <jamespage> cinder landed - nova-cc and nova-compute need a little change - but looking good
[15:26] <marcoceppi> icey: interesting
[15:26] <jamespage> mainly cause I jumped you with mitaka templates...
[15:26] <jamespage> sorry...
[15:27] <rick_h_> icey: hmm, yea I think it's something that we *should* be able to do without much more work, but with freeze and such it'll be something next cycle unfortunately
[15:28] <rick_h_> icey: 2.0 has folks heads down atm
[15:28] <icey> yeah rick_h_; ideally bootstrap lxd from mac will be there for 2.0 ;-)
[15:49] <thedac> gnuoy: Can I ask you to merge this please. Already approved https://code.launchpad.net/~ajkavanagh/charm-helpers/add-service-checks-lp1524388/+merge/285604
[15:51] <gnuoy> thedac, sure
[15:51] <thedac> ta
[16:08] <magicaltrout> whoop its only taken 2 days to write a very basic charm... its like belgium take 2 \o/
[16:12] <lazyPower> magicaltrout - it gets easier every time you do it :)
[16:12] <magicaltrout> hehe
[16:13] <lazyPower> <3 me some layers and no more boilerplate
[16:13] <lazyPower> and broken english apparently. but i digress, its quite pleasant :D
[16:13] <magicaltrout> indeed, the chaming bit wasn't what took time, its the parsing of the configs and stuff for configuration changes that took some figuring out
[16:13] <lazyPower> magicaltrout - we riffed on the bus right?
[16:14] <magicaltrout> we did indeed
[16:14] <lazyPower> nice :)
[16:14]  * lazyPower adds you to the list "my people"
[16:14] <magicaltrout> lol
[16:20] <magicaltrout> er right
[16:20] <magicaltrout> next random one
[16:20] <magicaltrout> I running trunk.... as you do
[16:21] <magicaltrout> i tried running bundletester but it seems to be using the non trunk install I have as its attempting to run bootstrap
[16:21] <magicaltrout> even though my env is bootstrapped
[16:21] <magicaltrout> sound plausible? and can i get it to use my trunk stuff
[16:21] <magicaltrout> I have my PATH set to use the trunk binary
[16:22] <marcoceppi> magicaltrout: IIRC, bundletester resets your path for you ;)
[16:22] <marcoceppi> let me take a look
[16:22] <magicaltrout> bonus
[16:26] <wolsen> jamespage, thanks for the review, I'll take a look at the comments on nova-cc and nova-compute
[16:29] <gnuoy> thedac, landed
[16:29] <thedac> ta
[16:38] <magicaltrout> other question
[16:38] <magicaltrout> actually, scrap it
[16:38] <magicaltrout> i'm an adult I can work it out ;)
[16:51] <marcoceppi> magicaltrout: feel free to ask anyways :)
[16:59] <magicaltrout> nope I'm cool, apart from the charm updating appearing sluggish ;(
[17:02] <magicaltrout> https://jujucharms.com/u/f-tom-n/gitlab/trusty/ up to date gitlab for the masses, I shall write a few more tests and get it into the store
[17:02] <marcoceppi> magicaltrout: nice!
[17:08] <magicaltrout> yeah, I'm just migrating a client
[17:08] <magicaltrout> so the stuff that isn't yet charmed I need to charm
[17:08] <magicaltrout> so I'll do my best to get it to a decent standard for general consumption
[17:09] <magicaltrout> I need to finish off the PDI charm me and kwmonroe were working on tomorrow
[17:09] <magicaltrout> thats the missing piece of the puzzle for this migration, but all that is missing is some random actions, the majority of the charm now works
[17:09] <kwmonroe> and what a fine charm that was magicaltrout!  the memories bring much joy ;)
[17:10] <magicaltrout> lol
[17:10] <kwmonroe> my favorite part was when cory_fu looked at our python in disgust.
[17:10] <magicaltrout> hehe
[17:10] <kwmonroe> exit 0 for life!
[17:10] <magicaltrout> "pfft you could have done that shit in bash"
[17:10] <magicaltrout> I stuck with it though, I did gitlab in bash as well for no real reason other than, I could ;)
[17:11] <magicaltrout> s/bash/python
[17:11] <kwmonroe> heh, awesome.
[17:12] <cory_fu> :)
[17:16] <jose> bdx: ping
[17:20] <lazyPower> interesting, has anyone seen a charm actively dismantle security features such as  enabling password auth and root login via ssh?
[17:32] <cory_fu> lazyPower: No.  Why would a charm want to do that?
[17:33] <lazyPower> cory_fu - good question, and its been noted in the review
[18:04] <icey> marcoceppi: I managed to get it working by bootstrapping from the lxd machine and copying over Juju's files to my mac
[18:04] <icey> now I can work with lxd from my Mac, I just can't bootstrap
[18:09] <icey> looks like it may be having some other issue now though, juju shows a new machine as pending for a while...it seems to be trying to get tools from the host machine rather than the bootstrap node -_-
[18:23] <marcoceppi> icey: this is because the bootstrap state-server is probably configured as to the wrong address
[18:24] <icey> I bootstrapped from the served lxd is running on, then tried depoloying from a remote machine; deploy worked, container came up, but then it looks like yeah, the state-server was configured wrong; the bootstrap container had an ip on both the lxcbr and the normal network
[19:05] <icey> lazyPower: your consul charm seems to be broken now
[19:07] <lazyPower> icey - maintainer is in metadata and the readme :D
[19:07] <lazyPower> das not meeeeee
[19:09] <icey> The Consul charm maintainers are: - Charles Butler ( @chuckbutler ) ...
[19:10]  * lazyPower touches his nose
[19:10] <lazyPower> whats goin on with it icey ?
[19:10] <icey> hashicorp pulled everything off of bintray
[19:10] <lazyPower> ah
[19:10] <lazyPower> thats a config.yaml update
[19:10] <lazyPower> \o/
[19:10] <icey> DL links have to change to releases.hashicorp.com
[19:10] <icey> not a version thing...
[19:11] <lazyPower> can you update config.yaml, give a quick test and PR that back upstream?
[19:11] <beisner> jamespage, all clear on:  https://code.launchpad.net/~james-page/charms/trusty/neutron-gateway/xenial/+merge/285862
[19:11] <icey> there are literally no longer any versions on bintray
[19:11] <lazyPower> thats fine
[19:11] <beisner> thedac, ^ as a prev. reviewer on that, can you have another peek?
[19:11] <lazyPower> you should be able to change the source_url
[19:11] <thedac> beisner: sure
[19:11] <lazyPower> to whatever, just grab the sha1sum of the bin and stuff that in config
[19:11] <icey> no source_url...
[19:11] <beisner> thedac, tyvm
[19:12] <icey> lazyPower: i'm going to have to muck around in the hooks/consul.py to fix it
[19:12] <lazyPower> icey rewrite the charm, give me a PR
[19:12] <lazyPower> :D
[19:12]  * icey seems to be doing that a lot lately
[19:12] <lazyPower> we like your work, what can I say?
[19:13] <lazyPower> icey matt and i can update that with a source_url/hash config option
[19:13] <lazyPower> did they drop deb delivery all together?
[19:14] <icey> it's now thgouth https://releases.hashicorp.com/consul/0.5.2/consul_0.5.2_linux_amd64.zip
[19:14] <thedac> beisner: jamespage: merged \o/
[19:14] <icey> with shasums at https://releases.hashicorp.com/consul/0.5.2/consul_0.5.2_SHA256SUMS
[19:14] <beisner> thedac, right on!
[19:14] <icey> lazyPower: almost ready to test this change and then I'll send a PR :)
[19:14] <lazyPower> woo \o/
[19:15] <lazyPower> icey - install_remote() will handle that natively
[19:15] <icey> basically a lot of {0}_{1} => {0}/{0}_{1}
[19:15] <icey> handle downloading the zip, download a separete shasum, confirm and drop in place?
[19:15] <icey> lazyPower: ^
[19:16] <lazyPower> should, the sum i think is expected to be handed to install_remote
[19:16] <lazyPower> vs fetching the shasum file
[19:16] <lazyPower> but it may just work, i haven't tried handing it a url
[19:16] <icey> lazyPower: this way we can get the new shasum by just updating the version in config though :)
[19:16] <icey> AND
[19:16] <icey> it shouldn't break again given that it's /their/ own CDN to handle downloads
[19:16] <lazyPower> we can hope
[19:29] <marcoceppi> hey magicaltrout, where do you keep your gitlab layer? I have a few things I'd like to contribute
[19:49] <magicaltrout> funny, I don't recall submitting my charm to the review queue ;)
[20:13] <marcoceppi> magicaltrout: I'm really keen on gitlab, I tried to write a charm for it a few years ago, I run it myself manually
[20:14] <magicaltrout> well
[20:15] <magicaltrout> marcoceppi: the scale out stuff with omnibus isn't great, plus i'm not a fan of the complete package stuff either
[20:15] <magicaltrout> but https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md
[20:15] <magicaltrout> I don't mind doing that
[20:15] <magicaltrout> but that involves manually compiling Ruby
[20:15] <magicaltrout> !
[20:15] <marcoceppi> magicaltrout: well upstream doesn't always know what's best ;)
[20:16] <marcoceppi> the omnibus is fine, we can just modify the configuration afterwards
[20:18] <magicaltrout> okay, so install via omnibus, and an exploded shell script
[20:18] <magicaltrout> and then if someone connects an alternative postgres then the hook updates the config and shunts the DB over to the separate DB?
[20:19] <magicaltrout> yesterday i was thinking about doing similar with Nginx even though it doesn't support proper clustering and scale out yet
[20:19] <marcoceppi> magicaltrout: thta's what I'm thinking, do an export and import of the database when related
[20:19] <marcoceppi> on relation removal, remote dump the db locally then allow the removal
[20:20] <marcoceppi> but that's a bit more involved
[20:20] <marcoceppi> just starting out I like the idea of going single -> scaleout
[20:20] <magicaltrout> aye
[20:20]  * marcoceppi will submit a few pull req
[20:22] <magicaltrout> okay marcoceppi, if you fancy tackling the DB as and when, I'll fiddle with optionally decoupling Ngnix and the crappy script
[20:23] <marcoceppi> magicaltrout: sure, sounds fun!
[20:23] <magicaltrout> if hacking DB connection hooks is your idea of fun :P
[20:24] <balloons> so marcoceppi, I get to bug you about GSOC again. Have you gotten your ideas on paper yet? I can fill them in the wiki even if needed. We need to have them done by Friday to submit the app
[20:24] <marcoceppi> balloons: yeah, I had some questions
[20:24] <balloons> I know jose is ok with doing some charm tasks.. But we could just assign the rest to him too ;-)
[20:24] <marcoceppi> balloons: is this targeted like Google Code In?
[20:24] <balloons> sure, ask away
[20:24] <jose> wat?
[20:24] <jose> me wat?
[20:25] <balloons> marcoceppi, no it's not the same. This is 1 on 1 mentoring, and over the summer. so May - August
[20:25] <marcoceppi> balloons: then I have a few ideas of charms we'd want to write
[20:25] <jose> and for university students who are 18 or older, and currently enrolled in a university program
[20:25] <marcoceppi> that I can help get on paper
[20:25] <marcoceppi> give me like, 40 mins, otp
[20:25] <balloons> right, so presumably they have more experience than the hs students
[20:26] <balloons> marcoceppi, brillant. jose, did you have charm ideas, or are you simply open to mentoring whatever marcoceppi comes up with?
[20:26] <jose> balloons: I can probably be the backup for Marco's ideas
[20:26] <balloons> tag-teaming them is a good idea
[20:28] <lazyPower> charmschool all the things
[20:34] <jose> lazyPower: you will mentor as well? fantastic!
[20:57] <lazyPower> sure
[21:05] <icey> is it possible to make a charm that will optionally be a subordinate?
[21:05] <rick_h_> icey: not currently. It's declared in metadata to be a subordinate or not
[21:05] <icey> rick_h_: that's what I thought; thanks!
[21:07] <icey> is it possible to relate two charms through the peer relation?
[21:10] <marcoceppi> icey: no, but you can use the same interface
[21:10] <marcoceppi> in the provides/requires section
[21:14] <icey> marcoceppi: so if I use the same interface, they will relate?
[21:14] <marcoceppi> no
[21:14] <marcoceppi> peers is only for inter-unit relations
[21:14]  * icey is sad
[21:14] <icey> I'll have to use the same hook for both a peer and vspecific relation then
[21:14] <icey> specific*
[21:15] <icey> alright, thanks marcoceppi!
[21:42] <ChrisHolcombe> cmars, do you know if the az zone gets set for ec2 instances ?
[21:57] <balloons> marcoceppi, how's it coming along?
[22:02] <marcoceppi> balloons: any chance I can get back to you tomorrow?
[22:02] <marcoceppi> I have to finish these FFe and I'm OTP atm
[22:03] <balloons> marcoceppi, yep. Tomorrow is fine. Since they are in your head, it should just be as simple as finding some time to get them written down.
[22:03] <balloons> thanks
[22:35] <apuimedo> Good God gracious, the lxd deployer in juju 2.0 is so much faster than the juju-deployer in returning control
[22:35] <apuimedo> good job guys
[22:35] <apuimedo> the juju status is also much better
[22:42] <marcoceppi> apuimedo: glad you like! it's been awesome to see what the juju-core people have been doing to make juju much nicer to use
[22:43] <apuimedo> marcoceppi: the only thing I don't know is why the "overrides" section in my bundle doesn't work. Has it changed in v4?
[22:43] <apuimedo> marcoceppi: agreed, the UX is miles better
[22:45] <marcoceppi> apuimedo: overrides aren't officially part of the bundle spec, sadly
[22:45] <marcoceppi> apuimedo: so they won't work in native juju deploy
[22:45] <apuimedo> :(
[22:45] <marcoceppi> apuimedo: we're working on defining how overrides should/will work in the next version of juju
[22:45] <apuimedo> that's a bit inconvenient
[22:45] <apuimedo> cool
[22:46] <apuimedo> looking forward to that
[22:46] <marcoceppi> apuimedo: it's not osmething we've forgotten, we just want to make sure the experience is good
[22:46] <apuimedo> ;-)
[22:46] <blahdeblah> Anyone know why juju mangles /root/.ssh/authorized_keys, and what I can do to fit in with that, whilst still enabling my charm to write a working entry in there?
[22:46] <marcoceppi> apuimedo: Mark made some mention of "flavors" of a bundle onthe mailing list recently https://lists.ubuntu.com/archives/juju/2016-February/006545.html
[22:47] <marcoceppi> blahdeblah: I wasn't aware juju mangles that - what provider are you using?
[22:47] <blahdeblah> marcoceppi: openstack (in Canonistack)
[22:47]  * apuimedo is ashamed. I've not followed the list recently
[22:47]  * blahdeblah grabs sample
[22:48] <marcoceppi> apuimedo: I admit I even have a hard time keeping up with all the mailing lists I watch
[22:48] <marcoceppi> blahdeblah: interesting. I suppose it's so the operator can juju ssh <machine-#> which would be a root login
[22:48] <apuimedo> yeah... With the openstack ones I have more than enough
[22:50] <blahdeblah> marcoceppi: Except that the main point of it is to break that: http://pastebin.ubuntu.com/15103537/
[22:50] <marcoceppi> blahdeblah: wat.
[22:51] <blahdeblah> marcoceppi: read the fine pastebin :-)
[22:51] <marcoceppi> blahdeblah: I did
[22:51] <marcoceppi> that was my reaction
[22:51] <blahdeblah> :-)
[22:51] <marcoceppi> blahdeblah: I don't see that in my 2.0-alpha2 deployed service
[22:51] <blahdeblah> I asked in #juju-dev (twice) why they do that, and I got crickets.
[22:51] <marcoceppi> blahdeblah: is that a problem with the image you're using?
[22:51] <blahdeblah> marcoceppi: this is stable
[22:52] <marcoceppi> pfft, stable
[22:52] <marcoceppi> who uses that! ;)
[22:52] <blahdeblah> and the keys are clearly marked as being put there by juju - look at the last field
[22:52] <marcoceppi> blahdeblah: sure, but the first parts of the file
[22:52] <blahdeblah> marcoceppi: don't make me come over there! :-)
[22:52] <marcoceppi> I'm not sure that's juju
[22:52] <marcoceppi> let me boot up my 1.25.3 vm
[22:54] <beisner> thedac, up for landing 2 test updates?  takes n-c-c and dashboard to the maximum passable test level, and marks the end this pass of test updates from me.
[22:55] <beisner> https://code.launchpad.net/~1chb1n/charms/trusty/nova-cloud-controller/next-amulet-1602b/+merge/286392
[22:55] <beisner> https://code.launchpad.net/~1chb1n/charms/trusty/openstack-dashboard/next-amulet-1602/+merge/285955
[22:55] <thedac> sure, I'll take a look
[22:56] <beisner> thedac, appreciate it
[23:04] <thedac> beisner: just want to confirm that lines 215 - 220 are correct on the nova-cc. >= trusty_mitaka use legacy_ratelimit? Seems like that should be the "future" not legacy