[03:48] <cameron_C> Hi, how to deploy a service to lxc auto select the machine or add a new machine with lxc?
[07:31] <gnuoy> jamespage, morning, we need to define an interface for the peer relation for the openstack api charms. Each Openstack API charm uniquely names the interface atm (eg keystone-ha, nova-ha, neutron-api-ha etc). I propose that we create an openstack-ha interface and have new charms use that. Sound ok?
[08:33] <jamespage> gnuoy, well so long as the interface uses the same data semantics, I think its ok to use a single type
[08:33] <jamespage> gnuoy, so we might endup with charms that have two peer relations - one general, one specific
[08:33] <jamespage> but leader storage should avoid most of that
[08:33] <jamespage> gnuoy, can you take a peek at https://review.openstack.org/#/c/317910/
[08:33] <jamespage> its the peer to one that's already landed in ceph-mon
[08:34] <jamespage> gnuoy, I also have a few stragglers for a general charm helpers resync across master and stable charms yesterday
[08:34] <jamespage> I'll fix those up this morning
[09:26] <jamespage> gnuoy, hey - could you nudge https://review.openstack.org/#/c/318220/
[09:27] <jamespage> beisner and I agreed not todo full rechecks for the syncs...
[09:28] <gnuoy> jamespage, done...
[09:28] <jamespage> ta
[10:38] <jamespage> gnuoy, governance review ressurected and companion email sent to openstack-dev!
[10:38] <jamespage> here we come ....
[10:38] <jamespage> that was worth an extra dot
[10:43] <jamespage> gnuoy: https://review.openstack.org/#/c/318231/ and https://review.openstack.org/#/c/318221/ are good to go
[10:43] <jamespage> beisner, I had to create some offical charm branches on launchpad to get the stable amulet tests to pass...
[11:07] <beisner> jamespage, oh yah, i suspect for the newbies, mon, lxd, et al?
[11:08] <beisner> jamespage, this --> https://review.openstack.org/#/q/topic:switch-to-bundletester   should allow us to use the version of amulet that contains the git branch fix.
[11:08] <beisner> ie. be able to resurrect that change review you took a stab at a while back
[11:24] <beisner> welcome back, gnuoy :)
[11:25] <beisner> jamespage, ceph-osd + odl-controller stable sync passed, ready to land?
[12:10] <jamespage> beisner, yes
[12:11] <beisner> gnuoy got 'em
[12:12] <gnuoy> I did!
[12:12] <kjackal> Hey lazyPower
[12:12] <kjackal> Quick questio
[12:12] <kjackal> where does the kibana charm live?
[12:13] <kjackal> its source?
[12:14] <jamespage> gnuoy, beisner: https://review.openstack.org/#/c/317910/
[12:15] <gnuoy> done
[12:15] <beisner> jamespage, curious - are ceph-mon or -osd affected similarly?
[12:16] <beisner> asked, with my 'keep the cephs in alignment' hat on
[12:19] <jamespage> beisner, erm for which?
[12:19] <jamespage> beisner, oh -mon already fixed; ceph is the sync
[12:19] <jamespage> then I'll stable branch cherry pick them both
[12:20] <jamespage> beisner, no - -osd was effected - not -mon
[12:20] <jamespage> that's the other one...
[12:21] <beisner> well look, there it is :-)
[12:25] <jamespage> beisner, gnuoy: https://review.openstack.org/#/c/317313/
[12:25] <jamespage> that should sort out the deployment race for the landscape team
[12:54] <lazyPower> kjackal - i based my branch off of the upstream charmer repo - https://code.launchpad.net/~charmers/charms/trusty/kibana/trunk
[12:54] <kjackal> lazyPower, I have a fix for the Kibana test that is failing
[12:55] <kjackal> should I submit the fix upstream? Is it well maintained?
[12:55] <kjackal> is it maintained by us?
[12:55] <kjackal> never checked
[12:57] <jcastro> hey lazyPower
[12:57] <jcastro> are you on the latest beta?
[12:58] <lazyPower> i am
[12:58] <jcastro> do you have any issues with it getting stuck on creating units with "pending"?
[12:59] <lazyPower> not with the clouds, i haven't been using LXD
[12:59] <lazyPower> so ymmv
[12:59] <tvansteenburgh> i'm on lxd, no probs
[12:59] <jcastro> huh.
[12:59] <lazyPower> kjackal well... yeah :)
[13:00] <lazyPower> but i wouldn't say its well maintained. its a long lived charm. As i'm sure you can tell poking around in there its long in the tooth
[13:00] <lazyPower> prior to this last round of updates, i think icey upgraded it to kibana4, so its got a few hands looking after it
[13:17] <jcastro> tvansteenburgh: do you leave your deployments running for a long period of time?
[13:17] <jcastro> seems for me it only acts up when I leave it running overnight
[13:18] <magicaltrout> don't answer! its a trap!
[13:18] <tvansteenburgh> jcastro: yeah, overnight quite a bit
[13:21] <lazyPower> kjackal - with these pr's are you still seeing the failure wrt the relations?
[13:22] <kjackal> Nope! Everything is GREEN :)
[13:22] <lazyPower> Solid, thanks for the contributions
[13:22] <lazyPower> I'm not real excited about the sleeps... but i see why its a pain. I had intermittent failures during test runs myself because of that
[13:22] <lazyPower> we kind of need a more deterministic way to sniff that out
[13:35] <jcastro> anyone know where actions went in 2.0?
[13:35] <jcastro> list-actions and juju actions are missing now
[13:36] <lazyPower> http://paste.ubuntu.com/16506582/
[13:36] <lazyPower> i call schenanigans
[13:36] <magicaltrout> bugg@tomsdevbox:~$ juju list-actions joshua-decoder
[13:36] <magicaltrout> No actions defined for joshua-decoder
[13:36] <magicaltrout> does something for me
[13:37] <jcastro> http://paste.ubuntu.com/16506594/
[13:37] <jcastro> what's happening to me
[13:37] <magicaltrout> indeed jorge! thats a very prudent question
[13:38] <tvansteenburgh> well are you gonna specify a service name??
[13:38] <magicaltrout> i am on beta4 so they may have gone away
[13:38] <magicaltrout> ah yeah lol
[13:38] <kjackal> Ok, lazyPower! The patch for the failing Kibana test is here: https://bugs.launchpad.net/charms/+source/kibana/+bug/1576706
[13:38] <mup> Bug #1576706: Tests are failure prone <kibana (Juju Charms Collection):New> <https://launchpad.net/bugs/1576706>
[13:38] <jcastro> oh, lol
[13:38] <lazyPower> kjackal on it
[13:38] <lazyPower> jcastro - i love how it told you what was wrong xD
[13:39] <tvansteenburgh> never underestimate the power of reading
[13:39] <jcastro> in my defense I was following instructions for a charm written for 1.25
[13:40] <jcastro> $ juju action do spark/0 smoke-test
[13:40] <jcastro> ERROR unrecognized command: juju action
[13:40] <tvansteenburgh> defense rejected
[13:40] <tvansteenburgh> run-action
[13:40]  * jcastro nods
[13:41] <lazyPower> ooo tim swingin the gavel of readme/2.0-translation justice
[13:41] <tvansteenburgh> Juju Judge Judy
[13:41] <jcastro> and to get the results of an action?
[13:41] <jcastro> it's not in the devel docs
[13:41] <tvansteenburgh> show-action-output
[13:42] <tvansteenburgh> show-action-status for just the status
[13:42] <jcastro> man, I am really missing tab completion now
[13:43] <tvansteenburgh> mine still works
[13:44] <jcastro> I am failing at computers today it seems
[13:46] <jcastro> cory_fu: hey so I got bigdata-dev/apache-processing-spark running, the readme says it's a standalone cluster, but the status for spark says it's waiting for a relation to hadoop plugin
[13:48] <aisrael> tvansteenburgh: how long should CI test results stay around? I'm seeing runs less than 2 weeks old go 404 on me: https://code.launchpad.net/~timkuhlman/charms/trusty/rsyslog-forwarder-ha/nrpe/+merge/292987
[13:48] <tvansteenburgh> aisrael: not unusual, it only keeps the latest 300 iirc. the new revq caches the results forever
[13:49] <cory_fu> kjackal: Is that status message a known issue with that bundle?  ^
[13:49] <aisrael> tvansteenburgh: ack. I will make an offering of redbull and daycare to the revq gods in that case.
[13:54] <tvansteenburgh> aisrael: those gods prefer beer and pipe tobacco i think
[14:01] <cory_fu> kwmonroe: I fixed the charm references in the bigtop repo's tests, built and published the charms, and updated the bundle in the bigtop repo & store.  So, both the PR and store are updated.
[14:01] <Shruthima> Hi All, I am developing IBM-Http Server on top of IBM-IM layer, Can we have separate license for HTTP server are do we need to use only one license that we are getting from ibm-base layer....?
[14:05] <Shruthima> Actually we are facing one issue when we use common license i.e when we use this state in reactive of HTTP server  @when ('ibm-http-server.installed') @when_not ('ibm-base.license.accepted')   and the below states in reactive of ibm-im  @when ('ibm-im.installed') @when_not ('ibm-base.license.accepted')
[14:05] <Shruthima> it is picking randomly ibm-im state first and then ibm-http  which should not happen bec IBM-Installation Manager will not be uninstalled till the products installed through IM are uninstalled.
[14:06] <Shruthima> Could you please suggest on the same....
[14:10] <tvansteenburgh> Shruthima: if the conditions for multiple handlers are true, you can't know which will run first
[14:11] <Shruthima> ya that is the issue ,can we use seperate license for http server ?
[14:13] <tvansteenburgh> Shruthima: i'm not sure that is the right solution
[14:14] <kjackal> jcastro, I am looking at the bundle issue
[14:14] <Shruthima> tvansteenburgh: ok thanks
[14:14] <kjackal> how urgent is it?
[14:15] <jcastro> kjackal: average I guess? I am blogging about it
[14:15] <jcastro> but don't expect to publish it until closer to juju 2.0
[14:15] <kjackal> jcastro, thanks
[14:43] <dweaver> Anyone know how to recover juju state server when it thinks it is upgrading after a reboot?
[14:45] <dweaver> Would upgrading the tools to a later version and starting the jujud service solve it, or is there somewhere in mongo that needs to be tweaked?
[14:55] <Shruthima> Hi kwmonroe/mbruzek , I have sent an email regarding the issue with common license.. could you please suggest on the same....!!
[15:01] <kwmonroe> hi Shruthima, the thought with a single config variable for the license in the ibm-base layer is that setting this to "True" would indicate that the user accepts whatever terms and conditions the charm requires -- whether it's one license or multiple licenses.
[15:02] <kwmonroe> Shruthima: so yes, the http server can have a separate license.  in the http server README, you would simply say "ibm http server requires the acceptance of license X, Y, and Z.  if you agree, indicate your acceptance of these terms by entering "juju set <charm> license_accepted=True"'
[15:03] <kwmonroe> Shruthima: i'll follow up to your email and we can decide if more thought is necessary to handle multiple licenses in your layered charms.
[15:04] <Shruthima> kwmonroe: oh ok thanks :)
[15:04] <kwmonroe> np
[15:08] <lazyPower> dweaver ah thats a tricky one. I've only seen fixes to "unstick" an upgrade
[15:08] <lazyPower> not when it thinks its upgrading erroniously
[15:24] <dweaver> lazyPower, OK, that's not good news.  It thinks it should be upgrading and this was only after a reboot of the state server, not an upgrade request. I am prepared to modify the mongo database or fiddle with the versions installed myself.  However, if this is not recoverable at all, then this is going to be a show stopper.  And this is likely to be published as this is a case study
[15:25] <lazyPower> dweaver - dont abandon hope yet, we can likely get a core dev to lend a hand. I'm not even sure where to begin debugging other than starting with a bug and collecting the controller logs.
[15:25] <lazyPower> dweaver - which version of juju is this? 1.25.5 i assume?
[15:25] <dweaver> lazyPower, OK, I'll raise a proper bug with lots of log information, it's actually 1.25.0, which means I can force an upgrade manually, if I need to.
[15:32] <lazyPower> can i get a hot review on this? I need to land it so i can rebase on top of it and prep/trim/rebase the tls branch on top of it. https://github.com/juju-solutions/layer-etcd/pull/13
[15:32] <lazyPower> mbruzek ^
[15:40] <xilet> So, I am new to working with juju, it looks like the cs branch of ~openstack-charmers-next/xenial/percona-cluster is out of date with the current branch. So mysql deployments are failing due to this bug https://bugs.launchpad.net/charms/+source/percona-cluster/+bug/1571789,   I was curious a.) if this is something that should be reported somewhere, and b.) is there a way to force change over juju to use the up
[15:40] <mup> Bug #1571789: install hook failing on Xenial with unmet dependency on mysql-client <uosci> <percona-cluster (Juju Charms Collection):Fix Released by 1chb1n> <https://launchpad.net/bugs/1571789>
[15:40] <xilet> dated branch in the meantime?
[15:42] <beisner> xilet, fyi https://jujucharms.com/u/openstack-charmers/percona-cluster/xenial   (cs:~openstack-charmers/xenial/percona-cluster-0)  does contain the fix
[15:42] <beisner> fyi, the -next charms are dev/possibly-bloody versions
[15:44] <xilet> Good to know, stupid question, any idea why ubuntu 16.04 LTS ships with those as the defaults?
[15:47] <stokachu> beisner: xilet, there is the latest openstack package in xenial-proposed that fixes this
[15:47] <stokachu> as for the next question it was because those stable charms were released after xenial GA
[15:47] <beisner> stokachu, excellent.   thanks for the clarification.   so, a change is in flight to stabilize it in xenial main.
[15:48] <stokachu> beisner: yea soon as someone marks verification-done on the sru
[15:49] <stokachu> beisner: xilet, https://bugs.launchpad.net/ubuntu/+source/openstack/+bug/1576412
[15:49] <mup> Bug #1576412: package does not use released charms <verification-needed> <openstack (Ubuntu):Fix Released by adam-stokes> <openstack (Ubuntu Xenial):Fix Committed> <https://launchpad.net/bugs/1576412>
[15:50] <xilet> stokachu: thanks!
[15:51] <stokachu> though i was just made aware of some issues with ceph-osd which I think are being worked out now
[15:51] <stokachu> but that wont require an update to openstack package
[15:51] <lazyPower> dweaver - just a follow up - many of our team members are at a planning sprint and thus responses have been latent. I'm trying to track someone down to lend a hand
[15:52] <lazyPower> it may take some time however, if you're willing to be patient and hand off the bug once its filed i'll be happy to run it up the pole
[15:52] <geetha> @kevin/matt: Hi!
[15:53] <mbruzek> hello
[15:53] <geetha> we need a clarification for state names that are set by interface. For ex: Websphere is connecting to DB2 and metadat.yaml file in Websphere charm has 'requires' definition and relation name as 'db' so in reactive script we are using state name as 'db.available'. But you suggested to use state name as 'ibm-was-base.db.available', if we give relation name as 'ibm-wa-base.db' in metadata.yaml, it's giving me error.
[15:54] <xilet> Should "juju upgrade-charm --force-units  mysql --switch=cs:~openstack-charmers/xenial/percona-cluster-0" pull the correct version of mysql? I am still getting the error though juju status is showing the new repo.  (Not sure if I have the correct syntax)
[15:58] <mbruzek> geetha: In this case "db" is the relation name, that has nothing to do with state names.
[15:58] <geetha> If I use same relation name i.e, 'db' in both(WAS and DB2) metadata.yaml file, it's not giving me any conflicts and state names set by interface is 'db.available' in both charms(without layer name prefix) is that ok?
[15:58] <mbruzek> geetha: kwmonroe and I recommended using the layer prefix (dot) state name.
[15:59] <dweaver> lazyPower, yes, willing to be patient, thanks.  I'll ping you with a bug ID once it is submitted with all the info.  Will be most appreciative thanks.
[15:59] <mbruzek> geetha: I think we have a disconnect here. We were not recommending renaming the relation name.
[15:59] <mbruzek> and I don't think relation names can have dots in there.
[16:00] <mbruzek> dot/period etc
[16:00] <mbruzek> geetha: can you give me a code example? Perhaps I don't understand your question
[16:01] <lazyPower> An interface name is a string that must only contain characters a-z and -, and neither start nor end with -. It's the single determiner of compatibility between charms; and it carries with it nothing more than a mutual promise that the provider and requirer somehow know the communication protocol implied by the name.
[16:01] <mbruzek> pastebin or something
[16:01] <lazyPower> mbruzek - thats what i found here
[16:01] <lazyPower> mbruzek and typically they are decorated with @hook('{relation_name}-joined')
[16:02] <lazyPower> that hook decorator string is run through some helpful templating functions in reactive to expand that relation_name to expand to whatever you have defined in metadata
[16:02] <lazyPower> so in this example, it should probably be declared in metadata like so
[16:03] <lazyPower> requires:   db2-database: ibm-db2
[16:03] <lazyPower> where db2-database would be the relationship name
[16:03] <lazyPower> so the state would become @when('db2-database.available')
[16:03] <lazyPower> geetha ^ does that help?
[16:04] <lazyPower> and i totally biffed on that @hook decorator code... its not *that* simple, there's a bit more to it, and it declares the interface inline like so: @hook('{provides:db2}-relation-joined') --- sorry for the typo. i was going from memory :)
[16:04] <geetha> then it will be 'db2-database.available'. there is no <layer name > prefix right?
[16:05] <lazyPower> geetha - right, its all predicated by what you name it in the metadata
[16:05] <geetha> it will take what ever relation name we give in metadata.yaml file.
[16:05] <lazyPower> the <layer name> prefix is a convention we use in the layers, when setting states so we can avoid collision with other layers. Similar care should be taken when defining relationship names
[16:08] <lazyPower> geetha - here's a super simple interface class that illustrates the code i was typing out above https://github.com/juju-solutions/interface-consul/blob/master/provides.py#L11.  Notice the use of that same template marco teh '{relation_name}' -  that expands and controls the states you will subscribe to in your layer.
[16:12] <gennadiy> hi guys
[16:14] <beisner> dimitern, jamespage - "install error: private-address not set" artifact and traceback on bug 1583109
[16:14] <mup> Bug #1583109: error: private-address/public-address not set (1.25.5) <sts> <juju-core:New> <https://launchpad.net/bugs/1583109>
[16:14] <geetha> Then we can give 'ibm-was-base-database' as a relation name in Websphere side right?
[16:14] <gennadiy> i can't bootstrap juju for openstack environment
[16:14] <jamespage> beisner, \o/
[16:15] <gennadiy> we have deployed openstack and would like to use juju to deploy software to it
[16:15] <geetha> then it will be @when 'ibm-was-base-database.available'
[16:15] <dimitern> beisner: you mean you got repro + trace logging? \o/ indeed!
[16:15] <beisner> dimitern, yessir
[16:15] <gennadiy> but now i have got error  ERROR juju.cmd supercommand.go:429 cannot set initial environ constraints: index file has no data for cloud {regionOne http://10.9.8.21:5000/v2.0/} not found
[16:16] <dimitern> beisner: awesome! tyvm, will have a look shortly
[16:16] <gennadiy> it happens when it setups tools on machine 0
[16:16] <gennadiy> i run it with: juju bootstrap -v --upload-tools --metadata-source /home/juju/.juju --debug --show-log
[16:16] <lazyPower> gennadiy is this juju 1.25?
[16:16] <beisner> machine-0.log is 11+MB and I'd like to turn trace off now if that gives you what you're after dimitern
[16:17] <dimitern> beisner: can you point me to the log?
[16:17] <dimitern> (too many logs there..)
[16:18] <gennadiy> yes, it's 1.25
[16:18] <gennadiy> do i need to reinstall?
[16:19] <lazyPower> i'm not certain, i've never seen that error before
[16:19] <dimitern> beisner: ah, got it - 0-var-log.tar.bz2
[16:19] <gennadiy> our openstack has own regionname - regionOne
[16:19] <beisner> bingo dimitern
[16:19] <gennadiy> so we need to use custom --metadata-source
[16:19] <lazyPower> gennadiy  https://bugs.launchpad.net/juju-core/+bug/1567763
[16:19] <mup> Bug #1567763: bootstrapping private openstack, with --metadata-source fails when instance-type constraint is specified <bootstrap> <constraints> <simplestreams> <juju-core:Triaged> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1567763>
[16:20] <gennadiy> i can't bootstrap env
[16:21] <lazyPower> right i get that, it seems like theres some streams you'll have to setup because of it but i'm not positive
[16:21] <lazyPower> but that bug looks applicable
[16:21] <gennadiy> but i don't use "--constraints"
[16:22] <dimitern> beisner: great, the log has everything I need (and suspected as the cause) - feel free to reset the logging-config to lower level
[16:22] <beisner> dimitern, ack tyvm
[16:23] <gennadiy> i used this tutorial - https://blog.felipe-alfaro.com/2014/04/29/bootstraping-juju-on-top-of-an-openstack-private-cloud/
[16:23] <gennadiy> i added image to openstack and generated metadata
[16:30] <jcastro> bdx: ping
[16:32] <dweaver> lazyPower, The bug is submitted here: https://bugs.launchpad.net/juju-core/+bug/1583683 log files are uploaded to the bug.
[16:32] <mup> Bug #1583683: juju thinks it is upgrading after a reboot <juju-core:New> <https://launchpad.net/bugs/1583683>
[16:52] <lazyPower> dweaver - thanks for the bug. I'll send this over to the appropriate parties. You should get updates via email as the bug gets triaged/worked. That'll be our focal point for resolution/updates.
[17:04] <xilet> Hrmm cs:~openstack-charmers/xenial/percona-cluster-0  has the same mysql-client issue
[17:18] <gennadiy> why remote bootstrapped machine does't use provided image-metadata-url?
[17:18] <gennadiy> seems it tryiesto use https://streams.canonical.com/juju/images/releases/streams/v1/index2.json
[17:18] <beisner> hi xilet - i just did a juju bootstrap ... then juju deploy cs:~openstack-charmers/xenial/percona-cluster-0 to check/confirm sanity of that charm and it looks good from that:  http://pastebin.ubuntu.com/16510376/    are you sure that charm is what is deployed?
[17:19] <gennadiy> i see in the log - " skipping index "http://cloud-images.ubuntu.com/releases/streams/v1/index.sjson" because of missing information: index file has no data for cloud {regionOne http://10.9.8.21:5000/v2.0/} not found" but i have provided own url - http://192.168.177.51:8888/
[17:26] <xilet>  beisner checking,
[18:20] <bdx> hows it going everyone? Have vlan tenant networks on a lxd openstack been verified as something that should work? Has anyone got their feet wet in this area yet, or is it just me?
[19:52] <magicaltrout> lazyPower: you'll know the answer to this
[19:52] <magicaltrout> if I use a layer like https://github.com/juju-solutions/layer-hadoop-client
[19:53] <magicaltrout> do I need to define the provides/requires stuff in metadata.yaml ?
[19:53] <magicaltrout> or does layers just sort that stuff out
[19:53] <lazyPower> it sorts it out as the metadata.yaml is already there
[19:54] <lazyPower> and it declares the interfaces in its layer.yaml
[19:54] <lazyPower> so it should be a single line include
[19:54] <magicaltrout> ta
[19:57] <magicaltrout> ooh yeah so it does
[19:57] <magicaltrout> funky stuff
[20:05] <Dirler>  Hi All, if I have kvm machines listed in “virsh list” but not listed in “juju status” for kvm environment,  Can I add such machines in juju kvm environment?
[20:06] <Dirler> p.s. such machines can exist in some scenarios: deployed using libvirt api directly, was exist before juju installation and so on.
[20:58] <penguinRaider> Hi, I am using juju to deploy ceph using the command juju deploy  cs:trusty/ceph -n 3 --config=ceph.yaml with just fsid and mon-secret in the yaml file. But when I try to do the same with cs:xenial/ceph it fails with this trace http://paste.ubuntu.com/16513817/. Am I doing something wrong here?
[21:18] <gennadiy_> hi. does it juju support images-metadata-url from openstack env config?
[21:18] <gennadiy_> i provided it but juju use standard ubuntu cloud url
[21:28] <gennadiy_> if we provide --metadata-source for bootstrap command it creates zero machine in openstack but throws error during software installetion(agent setup)
[21:45] <bdx> jcastro: sup
[22:13] <gennadiy> also how to use "juju metadata generate-image" in juju2? it requires model but model doesn't exist because controller is not bootstrapped