[00:18] <jose> it's gonna require some variables and stuff, so I'd say subordinate, otherwise action
[03:05] <firl> lazPower: how’s it going?
[08:20] <gennadiy> hi, seems i still have issue with my bundle. it's terrible to disturb somebody to check error log. do you have another method to get error report?
[08:39] <jamespage> mgz, hey - when you're around I have a bzr fast-import error I need a hand with
[10:11] <mgz> jamespage: not sure I can help much with that
[10:55] <gennadiy> could somebody can help with publish bundle error? can somebody review publishing error?
[10:55] <gennadiy> https://code.launchpad.net/~dataart.telco/charms/bundles/dataart-telco-demo/bundle
[11:08] <beisner> jamespage, fyi neutron-api/next amulet test failing on:  n-c-c:  Unknown job: nova-api-ec2  @ trusty-liberty.   i'll propose an update at n-api.
[11:18] <jamespage> beisner, I got that in my last update I think
[11:18] <beisner> jamespage, even better, thanks!
[11:19] <beisner> jamespage, hey i've got some control-file type stuff for new review automation that I'd like to place in our github space so they're controllable via PR.  migration-tools, or init a new thing?
[11:20] <jamespage> beisner, not fussed - up to you
[11:20] <beisner> jamespage, on that note, shall we have your branch sync stuff live alongside the lp:gh script foo?
[11:20] <beisner> it seems like a logical place
[11:20] <jamespage> beisner, sure - I'll move it over in a bit
[11:21] <jamespage> beisner, http://10.245.162.36:8080/job/charm_amulet_test/521/console
[11:22] <jamespage> its not ec2 or objectstore...
[11:22] <beisner> neutron api relation data key missing
[11:24] <jamespage> hmm
[11:25] <jamespage> beisner, ok fix pushed
[11:27] <beisner> jamespage, notice how jenkins-wrapped subprocess buffers sometimes get mixed up, and trace text land somewhere odd?   like that console output ;-)  weird.
[11:32] <jamespage> beisner, ftr I get two tempest smoke test failures against mitaka-staging on trusty UCA - both todo with telemetry for glance images...
[11:33] <jamespage> other than that smokes well with my three inflight branches...
[11:36] <beisner> jamespage, ack, i've not exercised m-staging but lmk when those are ready to run.  are the folks in os-dev who are reporting trouble using staging or updates?
[11:38] <jamespage> xnox, https://code.launchpad.net/~james-page/charms/+source/openstack-on-lxd-bundle/+git/openstack-on-lxd-bundle
[11:39] <jamespage> I just created a xenial one specially for you
[11:39] <jamespage> xnox, it won't work just yet - we have some inflight fixes for mitaka/xenial support that I should get landed today...
[11:43] <xnox> jamespage, i like! on g+ =)
[11:46] <jamespage> beisner, I'm promoting proposed -> updates for mitaka - it will break charm amulet tests until the neutron-gateway and neutron-openvswitch charm updates land - on those next
[11:47] <beisner> jamespage, ack
[12:10] <jamespage> beisner, I think my n-gteway and n-api updates are inter-dependent - i.e. I can't get one through testing without the other
[12:11] <jamespage> beisner, disable *mitaka on one first, land, land the other and then re-enable sound ok?
[12:20] <beisner> jamespage, yes.  alternatively, with things like this in the past, i've deployed the topology ahead of time with the desired charm branches, then just exec  ./tests/0nn-yadda
[12:21] <beisner> jamespage, i'd really like to move all of the amulet tests to just consume a bundle in the tests/ dir.  then it would be super easy for a user to manually verify something like this.
[12:21] <beisner> ie.  instead of defining dicts on the fly in the test itself
[12:21] <jamespage> beisner, well I need the promotion to flush through and then I'll work that
[12:21] <jamespage> beisner, agreed
[12:21] <jamespage> beisner, we also probably want to think about a way of defined check tests and gate tests for amulet
[12:22] <jamespage> beisner, as a thirdparty CI I guess we can see when someone +2's right?
[12:23] <beisner> jamespage, we should, yes.  right now our sandbox job is testing everything that hits openstack/ci-sandbox and I'm seeing notifications.
[12:23] <jamespage> beisner, awesome
[12:23] <beisner> today my priority is to nail down the initial amulet test chain that is triggered by that.  right now it's just a noop "you are here"
[12:23] <jamespage> beisner, btw is the missing relation between glance and rmq intentional in our bundles?
[12:24] <beisner> jamespage, seems like we id'd that and resolved at o-c-t.  where are you seeing that?
[12:24] <jamespage> beisner, next bundle with trusty-mitaka-*
[12:25] <beisner> jamespage, workload status is satisfied:  http://10.245.162.36:8080/view/Dashboards/view/OpenStack%20Deploy/job/deploy_with_deployer/428/artifact/juju-stat-tab-collect.428/*view*/
[12:25] <beisner> do we need to make that a required relation in the workload status bits?
[12:25] <jamespage> beisner, yeah its an optional relation
[12:26] <jamespage> beisner, its only required when deploying ceilometer...
[12:27] <beisner> jamespage, looks like we should add that rel to next and default yamls, and have a look at the affected amulet tests.
[12:28] <jamespage> beisner, ok
[12:30] <bentzy> hi. how am i supposed to increment my charm version # ? I get everytime <charm_name>-0. I want to be able to run "charm build" and then update the charm by clicking "Change Version" at gui
[12:31] <magicaltrout> -thanks jose. I think subordinate or a relation of some sort, that way people can plugin different implementations. I'm gonna have a think, it would be cool if, like the monitoring stuff there was a "backup" type relation for different services that different backup platforms could consume
[12:31] <magicaltrout> 12 hours lag response... not bad ;)
[12:51] <wesleymason> is there a way of doing "when any" as opposed to just "when all"/"when not any", maybe I'm missing something but wasn't obvious in the reactive docs
[12:52] <wesleymason> ah, just saw the any_states helper, nvm
[12:54] <wesleymason> no wait, that doesn't help really
[13:29] <coreycb> jamespage: could you take a look at these when you get a moment?  it's systemd support for openstack charms deploy from source.  I'll fix up tests post review.
[13:29] <coreycb> https://code.launchpad.net/~corey.bryant/charm-helpers/systemd/+merge/287110
[13:29] <coreycb> https://code.launchpad.net/~corey.bryant/charms/trusty/keystone/systemd/+merge/287112
[13:46] <magicaltrout> i'm supposed to be doing Java dev.... lets write some charms instead \o/
[13:56] <lazyPower> firl - pretty good
[13:56] <lazyPower> firl - squashed the ETCD bug if you want to give it a go
[13:57] <lazyPower> wesleymason - thats a known feature request, to be able to OR rather than AND @when() decorators
[13:58] <lazyPower> magicaltrout - that's a winning idea if i've ever heard one :)
[14:00] <magicaltrout> lol
[14:00] <magicaltrout> maybe
[14:04] <magicaltrout> cory_fu: kwmonroe https://medium.com/airbnb-engineering/data-infrastructure-at-airbnb-8adfb34f169c#.4z4rc5eqo
[14:04] <magicaltrout> might be of interest to you guys
[14:10] <jcastro> magicaltrout: that's a great link, thanks
[14:11] <magicaltrout> no probs
[14:13] <jcastro> magicaltrout: where you the one working on a layered gitlab charm?
[14:13] <magicaltrout> thats me
[14:13] <jcastro> so I have an idea
[14:13] <magicaltrout> hit me
[14:13] <jcastro> so I was thinking when it's ready, we should approach them and like, ask them to highlight it on their download page, etc.
[14:14] <jcastro> or whereever they put their "solutions" stuff
[14:15] <magicaltrout> indeed. I have already asked Pentaho if they can highlight the PDI charm on their community pages somewhere
[14:15] <jamespage> beisner, I'm going to land https://code.launchpad.net/~james-page/charms/trusty/neutron-api/mitaka-b2/+merge/287028
[14:15] <jcastro> magicaltrout: ooh lmk what they say
[14:15] <jamespage> its broken due to the b2 updates I just pushed to -updates for mitaka - but other tests passed
[14:15] <magicaltrout> they'll say yes, me and their community guy have worked together for 10 years :P
[14:16] <jcastro> magicaltrout: I would be happy to offer anyone who highlights a charm comarketing announcements, etc. on our pages
[14:16] <jcastro> if that helps your argument, heh
[14:16] <magicaltrout> but i need to finish the pdi charm and then i want to do a couple of video's to put on their pages so people know how to use it
[14:16] <beisner> jamespage, yep, looks like the test failure is down to the n-g change dependency
[14:16] <magicaltrout> its great having stuff available, not great if no one knows how to spin it up ;)
[14:16] <lazyPower> magicaltrout - hi o/ you said the trigger word video
[14:17] <lazyPower> magicaltrout - let me know if you want a hand there
[14:17] <magicaltrout> uh oh
[14:18] <magicaltrout> my videos' tend to suck, although i was messing around with the idea of a green screen the other day so I can actually appear on the screen whilst running a demo behind me :)
[14:18] <magicaltrout> I get bored of screencast type demos
[14:19] <magicaltrout> part of why i like presentations and community meetups as a way to convey information
[14:19] <jamespage> beisner, ok https://code.launchpad.net/~james-page/charms/trusty/neutron-gateway/mitaka-neutron-changes/+merge/286900 is up next sans mitaka tests
[14:19] <lazyPower> I understand that sentiment
[14:20] <jcastro> I think out of all of them I prefer screencasts
[14:20] <jcastro> because you can be ad-hoc
[14:20] <jcastro> there's no pressure to like make each thing perfect because it's live, you just roll with it.
[14:20] <magicaltrout> i watch back my onair hangouts and stuff and end up in tears ;)
[14:20] <magicaltrout> that said other people like them, so they must float some peoples boat
[14:21] <lazyPower> magicaltrout  you just hit exactly what i was trying to type out :)
[14:21] <lazyPower> so, we have this juju channel over on youtube
[14:21] <lazyPower> and having your pdi video's there would help discoverability
[14:21] <lazyPower> i think anyway :)  wide net and all that
[14:22] <magicaltrout> ah yeah
[14:22] <magicaltrout> i can see you on screen :P
[14:22] <lazyPower> O_o
[14:23] <lazyPower> jcastro - can we put a link to the youtube channel in /topic?
[14:26] <jcastro> drop the summit bit, that should let the channel fit
[14:26] <jcastro> it's https://www.youtube.com/c/jujucharms
[14:26] <magicaltrout> aww shit
[14:26] <magicaltrout> i can see my face
[14:26] <magicaltrout> i tried so hard to hide in that photograph
[14:35] <magicaltrout> talking of presentations, I have a presentation in the summer at NASA JPL which will involve Data Management & Juju. Now if an organisation needed some help doing application modelling, that's one! ;)
[14:36] <magicaltrout> i suspect they are rather stuck in their ways, but you never know
[14:36] <lazyPower> I've seen some NASA video's and I've seen Unity in the background. I have a sneaky suspicion they <3 ubuntu and they'll <3 juju just as much
[14:37] <lazyPower> speaking of which, i wonder if anyone patched the mars rover for heartbleed
[14:37] <magicaltrout> hehe
[14:41] <magicaltrout> when writing a layered charm, is there anything stopping me creating a bunch of different rective/*.py stuff so I can dump my state changes in one and hooks in another?
[14:51] <stub> magicaltrout: You can create as many *.py files as you like in reactive. I'd suggest putting them in reactive/mycharm/*.py though to avoid any possiblity with clashes.
[14:52] <stub> magicaltrout: But if you want them to be able to import from one another, you currently need a hack.
[14:57] <magicaltrout> thanks stub not to worried about the importing I don't think, just some logical separation
[15:44] <jcastro> hey aisrael
[15:44] <aisrael> yo
[15:44] <jcastro> let's say we wanted to start doing a LXD/juju vagrantbox but like for 16.04
[15:44] <jcastro> what's the tldr on getting that to work?
[15:45] <jcastro> I am thinking since juju has auto-lxd setup on first run
[15:45] <jcastro> the box is literally just juju and lxd preinstalled
[15:45] <aisrael> That's totally doable, but we'd need to enlist utlemming to adjust the vagrant build to support it
[15:46] <aisrael> I think that's the way to go, once we start building the xenial boxes
[15:46]  * jcastro nods
[16:12] <jcastro> aisrael: so like, if new juju2 and lxd lands next week, and we got a box out
[16:12] <jcastro> that would effectively let everyone test it without jumping through the hoops of getting all of that working in trusty
[16:21] <jamespage> mgz, it might be more of a bzr question - no sure...
[16:22] <aisrael> jcastro: Yes
[16:32] <apuimedo> jamespage: Corey Johns nick is johnsca, right?
[16:32] <cmagina> so, I'm seeing this when using bundletester with the apache-core-batch-processing bigdata-dev bundle http://pastebin.ubuntu.com/15198610/
[16:32] <jamespage> apuimedo, cory_fu
[16:32] <cmagina> i'm trying to use the local provider for this
[16:32] <cory_fu> jamespage: Yes?
[16:32] <apuimedo> cory_fu: that was me calling
[16:33] <jamespage> ;)
[16:33] <apuimedo> I just had the trusty cassandra charm explode on install hook
[16:33] <cory_fu> apuimedo: Oh, I see
[16:33] <apuimedo> on maas
[16:33] <apuimedo> first time it happened
[16:33] <apuimedo> and I see there's a change from less than an hour ago
[16:34] <cory_fu> apuimedo: Hrm.  You have the error?
[16:34] <apuimedo> sure
[16:34] <apuimedo> http://paste.ubuntu.com/15198649/
[16:34] <cory_fu> Also, I wouldn't have expected that MP to have ingested into the store yet
[16:35] <apuimedo> that's true
[16:35] <apuimedo> it looks like a repos issue actually
[16:35] <cory_fu> Though it seems it has
[16:36] <apuimedo> I'll try to re-trigger
[16:36]  * apuimedo doing that now
[16:36] <cory_fu> apuimedo: Seems from the error that something else on that unit was running apt-get at the same time
[16:36] <apuimedo> same issue
[16:36] <cory_fu> Did you deploy this on a fresh unit?
[16:36] <apuimedo> cory_fu: it's running on its own lxc
[16:37] <apuimedo> as allocated by the juju bundle deployer
[16:37] <apuimedo> and yes, the dpkg lock can't be taken even now
[16:39] <apuimedo> cory_fu: http://paste.ubuntu.com/15198698/
[16:42] <apuimedo> cory_fu: should I just destroy the service and lxc and re-deploy the previous revision?
[16:42] <magicaltrout> hello folks attmepting to mess around with this: http://pythonhosted.org/charms.templating.jinja2/ in my reactive layer but when it runs I get ImportError: No module named 'charms.templating'
[16:42] <magicaltrout> am i doing something moronic?
[16:42] <cory_fu> apuimedo: I don't see anything in the MP that should cause a dpkg lock issue.  The only thing that even touches it is switching from a manual fetch.add_source to fetch.configure_sources, but that shouldn't break anything
[16:43] <cory_fu> And I imagine stub is well out for the day
[16:43] <lazyPower> magicaltrout pastebin to your source using templating?
[16:43] <cory_fu> apuimedo: You can try, but TBH, I'm not certain this is related to the MP
[16:43] <lazyPower> oh this looks new...
[16:44] <lazyPower> but more or less just an extended port of whats in charmhelpers.core.templating.jinja2
[16:44] <magicaltrout> ah thats better I knew there was some templating stuff kicking around somewhere
[16:44] <magicaltrout> thanks lazyPower
[16:45] <lazyPower> np magicaltrout - lmk if you still have an issue w/ templating w/ that lib
[16:45] <cory_fu> apuimedo: Did you deploy it with any specific config options set?
[16:45] <apuimedo> cory_fu: I did
[16:46] <cory_fu> Can you share those with me?
[16:46] <mwenning> good morning juju team!    trying to bootstrap an all-vm system, node failing on seed_random module, see pastebin.ubuntu.com/15198749
[16:47] <apuimedo> sure
[16:47] <lazyPower> mwenning - troublemaker ;)
[16:47] <mwenning> mwenning, ees broke :-(
[16:50] <apuimedo>       options:
[16:50] <apuimedo>         authenticator: AllowAllAuthenticator
[16:50] <apuimedo>         cluster_name: midonet
[16:50] <apuimedo>         install_keys: 7E41C00F85BFC1706C4FFFB3350200F2B999A372
[16:50] <apuimedo>         install_sources: deb http://debian.datastax.com/community 2.0 main
[16:50] <apuimedo>         extra_packages: dsc20
[16:52] <apuimedo> cory_fu: ^^
[16:54] <cory_fu> apuimedo: Could it be an issue with the datastax PPA?
[16:55] <apuimedo> I don't know
[16:55] <cory_fu> apuimedo: Oh.  install_sources is supposed to be a Yaml list (as a string)
[16:57] <magicaltrout> right, another stupid question, but this is the terminology stuff confusing me more than anything else I think. I want to slap Apache2 over gitlab as an optional relation, so reverseproxy etc to gitlab
[16:58] <magicaltrout> what the f**k interface do I need to slurp up?
[16:58] <magicaltrout> https://api.jujucharms.com/charmstore/v5/trusty/apache2/archive/metadata.yaml from that lot
[16:58] <lazyPower> interface: http
[16:58] <lazyPower> reverse proxy is a consumer relationship, you just need to provide interface: http on gitlab
[16:58] <apuimedo> cory_fu: these bundle settings I've been using unmodified for a week or two
[16:59] <lazyPower> apache2:reverse-proxy should be enough tog et it going, its just going to read in private-address and port.    give it a go with haproxy and apache2
[16:59] <magicaltrout> hmm right lazyPower, i was reading some stuff in the apache docs about the vhost-config relation but then couldn't figure out how to define it
[16:59] <lazyPower> ah yeah our apache2 charm is like, geekmode++
[16:59] <magicaltrout> lol
[16:59] <lazyPower> IS wrote it and maintains most of it, so its next level on the combination of base64 encoded wizardry
[17:00] <magicaltrout> yeah i have like a base64 encoded vhost template and shit
[17:00] <magicaltrout> okay i'll scrub that and look to reverseproxy
[17:00] <magicaltrout> so in my charm I provide http so apache2 can consume it then?
[17:00] <lazyPower> should be able to
[17:00] <magicaltrout> okay cool
[17:01] <lazyPower> seriously deploy haproxy in front of your gitlab
[17:01] <lazyPower> if you have http already implemented you're basically done
[17:01] <cory_fu> apuimedo: Ah, nm.  It should accept a yaml list or a single string
[17:02] <cory_fu> apuimedo: Let me try deploying with those settings.  Are you trying the previous version?
[17:02] <apuimedo> not yet
[17:04] <cory_fu> apuimedo: Ok, I got the same thing.  It's definitely something about those config options and I guess the change to how the sources are loaded.
[17:04] <apuimedo> cory_fu: so the change modified the source management
[17:05] <apuimedo> cory_fu: I'll re-deploy with the previous version
[17:07] <cory_fu> Prev version seems to work fine
[17:08] <cory_fu> I'm trying to see what it is about the changes, but it looks like it should just work.  :(
[17:08] <apuimedo> :P
[17:08] <apuimedo> maybe you can add some amulet test for the install_sources
[17:09] <cory_fu> The charm does have a lot of Amulet tests, and there are specific tests added for this change.
[17:09] <cory_fu> All of which are passing
[17:14] <jose> so, question. when I want to implement an action in a layered charm, should I just add an 'actions' folder in the root folder?
[17:15] <lazyPower> yep
[17:15] <lazyPower> you'll additionally need the actions.yaml definition
[17:17] <jose> all of that in the root, right?
[17:17] <lazyPower> of your layer, yep
[17:18] <jose> cool, thanks!
[17:21] <cory_fu> apuimedo: Ok, I've got it.  The ppa:stub/cassandra and ppa:openjdk-r/ppa are both required (with nulls for the keys).  This config works for me: http://pastebin.ubuntu.com/15199178/
[17:23] <cory_fu> I think it's probably worth reverting the merge and kicking it back for that, since anyone who had been using that config option is almost certainly going to be broken
[17:24] <jamespage> beisner, ok with https://code.launchpad.net/~james-page/charms/trusty/neutron-gateway/mitaka-neutron-changes/+merge/286900 ?
[17:24] <kilty> has anyone had success with deploying juju on a private openstack cloud?
[17:25] <kilty> I generate the metadate and tools, and begin the bootstrap. It creates a ost instance on my openstack cloud, but it then tells me that RROR index file has no data for cloud {RegionOne http://192.168.4.11:5000/v2.0} not found
[17:26] <kilty> s\RROR\ERROR
[17:28] <beisner> jamespage, looks like i, K, L are happy with the changes. having a bit deeper look, sec..
[17:29] <apuimedo> cory_fu: Agreed
[17:34] <beisner> jamespage, ok, pretty sure i understand everything going on there.  +1
[17:34] <jamespage> beisner, thanks
[17:41] <jamespage> beisner, https://code.launchpad.net/~james-page/charms/trusty/neutron-openvswitch/mitaka-neutron-changes/+merge/286910
[17:41] <jamespage> that next...
[17:42] <cory_fu> apuimedo: It's been reverted and should be ingested before too long
[17:42] <apuimedo> cory_fu: thanks. Much appreciated
[17:43] <cory_fu> apuimedo: No problem.  Sorry I missed that side-effect and let this through.
[17:43] <apuimedo> no problem
[17:43] <apuimedo> now, on to find whatever happened with Puppet. It seems it was also updated and broke my charms...
[17:44] <jamespage> dosaboy, https://code.launchpad.net/~hopem/charms/trusty/ceph/lp1523871/+merge/286487 lgtm - but please wait for osci tocomplete - not long now....
[17:44] <jamespage> apuimedo, module breakage?
[17:46] <apuimedo> jamespage: I don't know. It's a bit strange, it's complaining about a missing hiera variable that I was never setting
[17:46] <apuimedo> most likely
[17:46] <apuimedo> some of our puppet module dependencies updated and became more strict about undefined values
[17:46] <apuimedo> or it's not taking the default
[17:47] <jamespage> apuimedo, hmm - tricky for repeatable deployments
[17:47] <jamespage> apuimedo, could you snapshot the modules into the charm in some way to avoid this?
[17:47] <apuimedo> jamespage: I can do better, I can pin the versions for all the puppet modules
[17:47] <apuimedo> and be done with it
[17:47] <jamespage> apuimedo, that indeed would be better
[17:48] <apuimedo> now I only need to find the culprit :-)
[18:38] <dosaboy> jamespage: thanks for the reviews
[18:38] <apuimedo> I think I found it!
[18:38] <apuimedo> https://forge.puppetlabs.com/ripienaar/module_data
[18:38] <apuimedo> released today
[18:38] <apuimedo> looks very suspicious
[18:39] <apuimedo> I often wonder what makes it so hard for the ruby/puppet community to keep backwards compatibility
[19:44] <kilty> has anyone had success with deploying juju on a private openstack cloud?
[20:01] <apuimedo> jamespage: I got it right. Ripienaar fixed the bug ;-)
[20:01] <apuimedo> I'll try to get our puppet stable module dependencies pinned
[20:01] <apuimedo> so that it doesn't happen in the future
[20:07] <firl> you around lazyPower ?
[20:16] <cory_fu> apuimedo: Can you take a look at stub's reply on https://code.launchpad.net/~stub/charms/trusty/cassandra/ensure-thrift/+merge/279869
[20:17] <apuimedo> let's see
[20:20] <lazyPower> firl i iam
[20:20] <firl> hey man
[20:21] <firl> Any updates by any chance?
[20:21] <lazyPower> you bet
[20:21] <lazyPower> juju deploy ~lazypower/bundle/kubernetes-core
[20:21] <firl> do i need to compile the bundle again?
[20:21] <firl> or the layer rather
[20:22] <lazyPower> nope
[20:22] <lazyPower> etcd just moved to layers
[20:22] <firl> need something newer than 1.25?
[20:22] <firl> ERROR expected a charm URL, got bundle URL "cs:~lazypower/bundle/kubernetes-core-0"
[20:22] <lazyPower> oh, thats possible yeah
[20:22] <lazyPower> argh
[20:22] <lazyPower> new stuff
[20:22] <firl> :)
[20:22] <lazyPower> want to trywith new stuff?
[20:23] <firl> sure, this is a scratch environment
[20:23] <lazyPower> docker pull lazypower/charmbox:devel
[20:23] <lazyPower> juju 2.0-beta1
[20:23] <lazyPower> i'm speaking in half fragmented sentences because i'm excited you showed up. I feel like i have a mountain of candy you've been asking for patiently
[20:23] <lazyPower> and man, i gotchoo covered
[20:23] <firl> haha
[20:24] <firl> let me pull up a vm to do the docker stuffs
[20:24] <lazyPower> ok. if you want to add devel ppa on your current scratch thing
[20:24] <firl> that’s fine too
[20:24] <firl> I have a build node for when you gave me the layer stuff
[20:24] <lazyPower> just know that you cant upgrade from 1.25 to 2.0 cleanly *yet*
[20:24] <lazyPower> and the $JUJU_HOME's are incompatible.
[20:24] <lazyPower> actually
[20:24] <firl> it won’t break the juju agent environment with the state machines will it?
[20:24] <lazyPower> you have the source - github.com/chuckbutler/layer-etcd - is current devel focus
[20:25] <firl> ya i have that
[20:25] <lazyPower> which will unblock your k8s work
[20:25] <firl> ok i need to hit up a meeting, will try this right after
[20:25] <lazyPower> tip of mbruzek/layer-k8s works out of the box with that replacement etcd
[20:25] <lazyPower> ack, lmk if you have *any* questions firl
[20:38] <apuimedo> cory_fu: replied
[20:58] <firl> lazyPower ok back
[20:58] <lazyPower> woo
[21:03] <firl> so I need to add the devel ppa and upgrade the juju CLI locally, correct?
[21:03] <firl> or should I just build the layer-k8s?
[21:05] <lazyPower> just build layer-k8s
[21:05] <lazyPower> additionally, you'll want to deploy cs:~lazypower/trusty/etcd-4, or build from my layer-etcd
[21:09] <firl> so from a bundle prespective
[21:09] <firl> this ok? http://pastebin.com/N3YEpVHm
[21:10] <lazyPower> firl - that looks kind of old compared to what our config is now.. default has bumped to v1.1.7, the generated charm is "kubernetes"
[21:12] <lazyPower> > charm: cs:trusty/etcd-4 - is the last -stable revision before the connection string revisions. try charm: cs:~lazypower/trusty/etcd
[21:13] <firl> should I just use: https://api.jujucharms.com/charmstore/v5/~lazypower/bundle/kubernetes-core-0/archive/bundle.yaml
[21:13] <lazyPower> That'll work :)
[21:13] <firl> haha
[21:14] <firl> so should I pull it in via gui / store? or build the layer and deploy
[21:14] <lazyPower> if you're interested in just consuming the kubernetes charms, pull it in via gui/store
[21:14] <lazyPower> if you want to help dev, build from layers and beat on it a bit
[21:14] <lazyPower> i'll keep updating this bundle as i drop features, pre-release style
[21:17] <firl> gotcha
[21:19] <firl> can’t pull it in via gui
[21:20] <firl> “fetching the entity failed”
[21:20] <lazyPower> argh
[21:20] <firl> :)
[21:20] <firl> this is why I am here right? hah
[21:21] <lazyPower> yeah, i'm depressed. this is due to some new things i've been piloting
[21:21] <firl> haha
[21:21] <firl> don’t worry man
[21:21] <lazyPower> if you're on 2.0, you can get at the charms
[21:21] <firl> I can upgrade
[21:21] <lazyPower> looks like 1.25 is only serving charms from ingest
[21:21] <firl> i don’t mind
[21:21] <lazyPower> ok, welcome to a whole new world :)
[21:21] <firl> haha upgrade instructions?  i need to upgrade the cli, the agent and the state machines?
[21:22] <lazyPower> so, its an incompatible upgrade right now
[21:22] <lazyPower> do you have work in 1.25 that you need to keep accessing?
[21:22] <firl> I have a jenkins setup that I need
[21:22] <firl> just 2 machines
[21:22] <lazyPower> ok lets isolate your 2.0 environment
[21:22] <firl> alright, this could be a pain but lets do it
[21:23] <firl> last time I tried to create a new juju environment on openstack it had issues
[21:23] <firl> Creating a new project now
[21:23] <firl> is there up to date install on openstack instructions?
[21:24] <lazyPower> one sec, the definitive guide came out as a mailing list post
[21:24] <firl> I should have it then someplace
[21:24] <lazyPower> firl https://lists.ubuntu.com/archives/juju/2016-February/006618.html
[21:24] <firl> so use Xenial?
[21:25] <lazyPower> nooooooo
[21:25] <lazyPower> you can do this on trusty just fine
[21:25] <firl> kk trust still right?
[21:25] <firl> ok
[21:25] <lazyPower> first paragraph, its co-installable with 1.25
[21:25] <firl> I don’t care in all honesty, it’s all just vm’s
[21:25] <lazyPower> update-alternatives --config juju is how you switch between the releases
[21:25] <magicaltrout> I need a pissing server sat under my desk, stuff this cloud nonsense
[21:25] <magicaltrout> *yawn*
[21:26] <lazyPower> magicaltrout - keep it family friendly please :)
[21:28] <magicaltrout> indeed, I shouldn't mention that C word....
[21:37] <magicaltrout> alright then 2 hours of expense claiming done. Lets take this http interface for a spin
[21:37] <jrwren> i'm so confused, i can't tell if the bad c word is cloud or co-installable or config ;]
[21:39] <magicaltrout> hehe
[21:47] <magicaltrout> okay so i still don't get this
[21:47] <magicaltrout> unit-apache2-0: 2016-02-25 21:46:21 INFO unit.apache2/0.juju-log server.go:269 reverseproxy:4: Vhost Template not provided, not configuring: 80
[21:47] <magicaltrout> i'm guessing thats quite important
[21:48] <lazyPower> magicaltrout did it work with haproxy?
[21:48] <magicaltrout> apache2:reverseproxy do I still pass it a vhost file?
[21:48] <magicaltrout> i've not got that far yet :P
[21:48] <magicaltrout> let me rip out apache and find out
[21:53] <magicaltrout> okay so i'm doing something stupid, mostly because i'm trying to learn python at the same time instead of just copying the bash examples :P
[21:54] <magicaltrout> https://gist.github.com/buggtb/ff52067809a00101d4f1
[21:54] <magicaltrout> whats up with that?
[21:54] <magicaltrout> there's no problem with the deployment but I get
[21:54] <magicaltrout> unit-haproxy2-0: 2016-02-25 21:52:01 INFO unit.haproxy2/0.juju-log server.go:269 reverseproxy:7: No port in relation data for 'gitlab/0', skipping.
[21:54] <magicaltrout> unit-haproxy2-0: 2016-02-25 21:52:01 INFO unit.haproxy2/0.juju-log server.go:269 reverseproxy:7: No backend servers, exiting.
[21:54] <firl> lazyPower: having issues bootstrapping 2.0
[21:55] <firl> not sure what the “endpoint” should be
[21:57] <lazyPower> one sec, i lost the post
[21:57] <firl> https://lists.ubuntu.com/archives/juju/2016-February/006618.html
[21:57] <firl> that one?
[21:59] <lazyPower> yeah
[21:59] <lazyPower> looking it over, one sec, i dont use openstack as a substrate often so i'm not as familiar with the config
[22:00] <firl> “#### Private Clouds” section
[22:02] <lazyPower> ddellav beisner : ping
[22:02] <lazyPower> firl - if this doesnt yeild good results, i vote to change my answer to "build from layers and deploy"
[22:02] <firl> haha
[22:03] <lazyPower> this quickly turned into a ball of yarn. 2.0 was a weekend discovery for me
[22:03] <firl> lol ok
[22:03] <firl> so i need to have a 1.25 juju environment and then do a charm build on the git repo right?
[22:04] <lazyPower> yep
[22:04] <lazyPower> both git repos*
[22:04] <lazyPower> layer-k8s, and layer-etcd
[22:04] <firl> let me clone layer-etcd
[22:04] <firl> https://github.com/chuckbutler/layer-etcd ?
[22:04] <lazyPower> thats the one
[22:05] <firl> ok now?
[22:05] <lazyPower> with those built, replace both charms with local references, remove the default config option for kubernetes version and you should be in like flynn
[22:06] <firl> in this file ?
[22:06] <firl> https://api.jujucharms.com/charmstore/v5/~lazypower/bundle/kubernetes-core-0/archive/bundle.yaml
[22:06] <lazyPower> yep
[22:06] <lazyPower> i was thinking your bundle, but mine works
[22:06] <lazyPower> either/or :) six of one, half dozen of the other
[22:06] <firl> the other bundle was from matt i think
[22:06] <lazyPower> oh right on
[22:08] <firl> http://pastebin.com/APinzAeu
[22:08] <firl> ?
[22:09] <lazyPower> when you ls your $JUJU_REPOSITORY, do you see k8's or kubernetes?
[22:10] <firl> i see both
[22:10] <firl> let me clean
[22:10] <firl> kubernetes is the latest from the charm build
[22:10] <lazyPower> ok, change line 4 to local:trusty/kubernetes
[22:11] <firl> on it
[22:17] <lazyPower> firl - also fyi, i think that endpoint setting in the credentials.yaml for your privcloud is the same as the auth-url in the 1.25 config
[22:17] <lazyPower> your keystone endpoint
[22:17] <firl> I tried that one
[22:18] <firl> that’s why I was asking
[22:19] <lazyPower> :(
[22:19] <lazyPower> i'll bring that up and see if i can get you an answer firl
[22:22] <jamespage> beisner, if you are still around - https://code.launchpad.net/~james-page/charms/trusty/neutron-openvswitch/mitaka-neutron-changes/+merge/286910
[22:22] <jamespage> lgtm now
[22:42] <firl> “local charms not allowed for service kubernetes: local:trusty/kubernetes”
[22:42] <firl> lazyPower
[22:46] <lazyPower> firl - have you exported JUJU_REPOSITORY?
[22:47] <firl> http://pastebin.com/CFK6C05U
[22:48] <firl> i created my local juju repository via sym links to ./trusty
[22:50] <lazyPower> ah quickstart doesn't work with local urls.
[22:50] <firl> :)
[22:50] <lazyPower> juju-deployer does, or the juju deploy command from juju2
[22:52] <firl> just going to add units
[23:21] <firl> lazyPower http://pastebin.com/x0bMLf8B
[23:24] <magicaltrout> https://github.com/OSBI/layer-gitlab/blob/master/reactive/gitlabhooks.py#L14 can anyone see anything stupidly obvious that means that wont install properly, yet when I paste it into debug-hooks it works as expected....
[23:29] <lazyPower> firl - i'm going to EOD, but if you need anything feel free to ping
[23:29] <lazyPower> i'll circle back and check in on ya after dinner
[23:29] <firl> hah I sent a pastebin
[23:29] <lazyPower> oh
[23:29]  * lazyPower missed that
[23:29] <firl> charm build doesn’t give a charm that is deployable
[23:30] <lazyPower> ah
[23:30] <lazyPower> the etcd layer has 2.0 features in it
[23:30] <lazyPower> if you delete series: -trusty out of metadata.yaml that'll fix that
[23:30] <lazyPower> lame :|
[23:31] <firl> hrmm
[23:32] <lazyPower> firl if you pull from master i just updated the layer
[23:32] <firl> for etcd?
[23:32] <firl> oh i see ya, I did -series: “trusty"
[23:33] <firl> WARNING failed to load charm at "/home/ubuntu/work/trusty/kubernetes": metadata: series: expected string, got []interface {}([]interface {}{"trusty", "wily", "xenial"})
[23:34] <lazyPower> weird, why would k8s be complaining? it does't even have series in metadata.
[23:34] <firl> yeah
[23:34] <firl> it’s weird
[23:35] <firl> it shows up in the metadata output
[23:35] <firl> cleaning and rebuilding
[23:36] <firl> http://pastebin.com/NyxPL9Cd
[23:36] <firl> maybe something is aggregating based upon charm build deps
[23:36] <lazyPower> its layer-docker that pulled that in
[23:36] <lazyPower> ok, hang on, thats a breaking update
[23:38] <firl> haha
[23:38] <firl> we can do this another time too after you eat
[23:40] <lazyPower> firl - https://github.com/juju-solutions/layer-docker/pull/27
[23:40] <lazyPower> i need to land that and i think.. thats the last of the 2.0 features we baked in
[23:40] <firl> haha
[23:40] <firl> should I also build that locally from your pr branch or is it pretty quick for the pr
[23:41] <firl> oh nm i see you already did
[23:41] <lazyPower> go ahead and pave/rebuild
[23:41] <beisner> jamespage, ah so good, the theory and the plan came to a pass on 286910  :-)
[23:41] <firl> how soon for juju 2.0? couple weeks
[23:41] <firl> ?
[23:42] <lazyPower> its in beta, i think it lands as -stable in a little over a month
[23:42] <lazyPower> dont quote me on that though, i actually haven't asked. I've been so deep in using it :)
[23:43] <firl> added charm to env
[23:43] <lazyPower> woo \o/
[23:43] <lazyPower> paydirt
[23:43] <firl> i can have the etcd charm reside on the same units as the kubernetes units right?
[23:43] <firl> haha
[23:43] <lazyPower> err, dont do that
[23:43] <firl> so 6 nodes
[23:43] <lazyPower> we're still gutting some stuff from k8s
[23:43] <lazyPower> yeah
[23:43] <firl> 3 kube 3 etcd
[23:43] <lazyPower> k8s launches some etcd containers on the host that we're phasing out
[23:44] <lazyPower> that was a leftover from the initial import we didnt notice
[23:44] <firl> to grow +1kube node no need to grow etcd for testing right?
[23:44] <lazyPower> right
[23:44] <firl> kk
[23:44] <lazyPower> and you can pair down etcd to single node
[23:44] <firl> lol
[23:44] <lazyPower> you only need to run 3/5 in production scenarios or proper HA testing
[23:44] <firl> already triggerred 3
[23:44] <lazyPower> welp
[23:44] <lazyPower> it supports scale up
[23:44] <firl> I will remove units after
[23:44] <lazyPower> but not scale down
[23:44] <firl> lols
[23:45] <lazyPower> thats where i'm at now in the fixes
[23:45] <lazyPower> but to be fair, the old charm had the same behavior
[23:45] <firl> so I will blow it away before the relation
[23:45] <lazyPower> yeah
[23:45] <firl> and do just 1 unit
[23:45] <lazyPower> ok, off for now, will be back later
[23:45] <lazyPower> o/
[23:45] <firl> see ya
[23:45] <firl> thanks again!
[23:46] <lazyPower> hey np :) sorry it was a bumpy road getting to this point
[23:46] <lazyPower> reminder that not everybody is in -beta land with me
[23:59] <magicaltrout> oh you're fscking kidding me
[23:59] <magicaltrout> i spend all evening messing around with a website-relation-changed hook not firing and find including the http interface and a @when('website.available')
[23:59] <magicaltrout> sorts me out in about 30 seconds