[00:15] <derekcat> Happy Wednesday #juju!
[00:15] <derekcat> Anyone seen this error when trying to deploy an OpenStack bundle to MAAS?
[00:15] <derekcat> Deploying charm "cs:ceph-269"
[00:15] <derekcat> ERROR cannot deploy bundle: cannot deploy application "ceph": cannot add application "ceph": unknown space "storage-cluster" not valid
[00:30] <pixelate> fun
[01:43] <stokachu> marcoceppi, hmm cannot assign unit "ghost/0" to machine 0/lxd/0: adding storage to lxd container not supported
[01:44] <marcoceppi> stokachu: you can't use storage in lxd (it would seem)
[01:44] <stokachu> works just fine with localhost though, its only when deploying to a lxd container on a bare metal machine via maas
[01:44] <marcoceppi> stokachu: sounds like some aggressive check code
[01:44] <stokachu> yea
[01:45] <babou> how do i remove a charm which failed to install?
[01:46] <babou> i deployed a local charm, its install failed, i fixed the problem, but when i try to deploy it again it says the application has already been deployed
[01:46] <babou> when i try remove-application, there is no output and the application remains on the controller
[01:46] <stokachu> babou, juju resolved <app>/<unit>
[01:47] <stokachu> oh you probably want to juju debug-hooks <app>/<unit> and fix it there so you can do a juju upgrade-charm from your working copy
[01:49] <babou> sorry im quite new to all of this
[01:49] <babou> juju resolved had no effect
[01:49] <babou> debug-hooks ssh me into the container
[01:49] <babou> you're saying I should edit the code from within the container instead of externally and redeploying?
[02:00] <babou> the debug-log just keeps looping
[02:00] <babou> saying the install hook is failing again and again
[02:00] <babou> restarting the machine had no effect, it immediately began failing the install hook again
[02:06] <stokachu> babou, juju debug-hooks <app>/<unit> install
[02:06] <stokachu> then in another terminal type juju resolved <app>/<unit> and the debug-hooks window will show up an "install" tab
[02:06] <stokachu> from there you can edit the currently installed hook to make it work
[02:07] <stokachu> when you ctrl+d out of that terminal juju should continue on through the other hooks
[02:07] <babou> i was able to upgrade it by running this command
[02:07] <babou> juju upgrade-charm --force-units --repository=./buses buses
[02:07] <stokachu> if all else works you'll get an active status and can then run `juju upgrade-charm`
[02:07] <babou> where buses is the name of my charm
[02:07] <stokachu> ah ok
[02:07] <babou> and then running resolved
[02:07] <stokachu> that works too :D
[02:07] <babou> onward to the next error!
[02:07] <stokachu> i should probably look at the help output more
[02:08] <stokachu> babou, cool gl
[02:08] <babou> got help from this page which i had to translate to v2
[02:08] <babou> http://marcoceppi.com/2015/01/force-upgrade-best-juju-secret/
[02:08] <marcoceppi> babou: o/
[02:08] <stokachu> ah yes i remember that post
[02:09] <stokachu> maybe time to update it :D
[02:09] <marcoceppi> yes, *updates post*
[02:09] <stokachu> your posts aren't on github are they?
[02:10] <marcoceppi> stokachu: no, wordpress
[02:10] <babou> @marcoeppi i have no idea who you are, but i feel like im meeting a famous person
[02:10] <stokachu> marcoceppi, ah ok
[02:10] <stokachu> babou, he is famous
[02:10]  * marcoceppi blushes
[02:50] <marcoceppi> babou: thanks for the updated commands, I've refreshed my blog post
[02:54] <rick_h> marcoceppi: stokachu storage on lxd is on this cycle's roadmap of items. Couple of folks are working on it
[02:55] <rick_h> marcoceppi: stokachu that's both lxd provider and lxd on another cloud (maas, etc)
[03:50] <babou> does anyone know how to install a modern version of node to a controller?
[03:51] <babou> the way this one does it, it installs 0.10.3
[03:51] <babou> https://api.jujucharms.com/charmstore/v5/precise/node-app-11/archive/hooks/install
[08:30] <kjackal> Good morning Juju world
[09:18] <Spaulding> morning!
[13:42] <anrah> question about layers and interface-layers
[13:43] <magicaltrout> goooo anrah gooooooooo!
[13:43] <anrah> I have a interface-layer which I (perhaps) want to peer on all nodes on my model
[13:44] <anrah> then i have base-layer on which all other apps are build on
[13:44] <anrah> apparently i can't use my peer-interface on all nodes?
[13:45] <anrah> as now it seems that all diffent apps have their own peering, even the interface is same on all applications
[13:46] <magicaltrout> https://github.com/juju-solutions/interface-spark-quorum/blob/master/peers.py you have something like that?
[13:46] <anrah> yes
[13:46] <magicaltrout> and you have the scope set?
[13:46] <anrah> yes, global
[13:48] <anrah> Relation  Provides          Consumes          Type
[13:48] <anrah> test    app-control  app-control  peer
[13:48] <anrah> test    app-worker   app-worker   peer
[13:48] <anrah> it shows like that
[13:48] <anrah> what I would like to have is that all different applications would peer with each other
[13:48] <anrah> throught that layer
[13:48] <anrah> I might have wrong idea on my mind and I need ot change the approach, but that is how I planned it :)
[13:49] <magicaltrout> that output looks right from my limited knowledge of peer relations.
[13:49] <magicaltrout> You're wanting to peer app-control to app-worker as well?
[13:49] <anrah> Yes
[13:49] <magicaltrout> yeah thats not happening afaik
[13:49] <magicaltrout> kjackal:
[13:49] <anrah> Without requires-provides
[13:49] <magicaltrout> help the poor person
[13:50] <anrah> I think that I'll have a beer and think this otherway around :)
[13:50] <kjackal> hello magicaltrout
[13:50] <magicaltrout> marcoceppi is answer emails
[13:50] <magicaltrout> he'll know as well
[13:50] <kjackal> let me see give me a sec to catchup
[13:50] <marcoceppi> wat
[13:50] <magicaltrout> peer relations across different charms
[13:50] <magicaltrout> I think in a nutshell
[13:51] <marcoceppi> does not exist
[13:51] <marcoceppi> peers are only for unit <-> unit communication wihtin a single application
[13:51] <magicaltrout> figured as much
[13:51] <magicaltrout> there you go anrah
[13:51] <marcoceppi> you can reuse the interface for a peer relation in the provides/requires though
[13:51] <marcoceppi> but it's a seprate relations
[13:52] <anrah> I thought so
[13:52] <anrah> Then I'll have a beer and think other way around :)
[13:52] <magicaltrout> have 5
[13:52] <magicaltrout> its more effective
[13:53] <anrah> basically the need is just to get ip-addresses of all units within a model
[13:53] <anrah> inside the charm
[13:53] <magicaltrout> there must be a way to get that that marcoceppi can python up
[13:54] <marcoceppi> anrah: ah, so, juju-info will be your savior
[13:54] <kjackal> there is the juju-info interface that is implicit to all charms
[13:54] <marcoceppi> anrah: but it's still a bit, dull
[13:55] <marcoceppi> anrah: basically, juju-info is an interface you can require in your charm that allows you to connect to any application deployed. It only sets the `private-address` field so you can relation_get('private_address') but it requires the bundle or operator to add a relation to each component
[13:55] <marcoceppi> anrah: without using the API, that's the best you can get
[13:57] <anrah> thanks! I'll try that
[14:30] <caribou> Hello, when creating actions for a charm in python, if I keep the .py suffix, the action is not identified by the script name w/o the .py
[14:31] <caribou> what is the best approach to create actions in python ? just drop the .py ?
[14:31] <magicaltrout> i did some yesterday
[14:31] <magicaltrout> drop the .py and make sure you have a shebang in the top of the script
[14:31] <caribou> if I use a symlink (layered charm), when the charm is built, it drops the symlink & copy the file
[14:32] <caribou> magicaltrout: then it becomes an issue with unittests
[14:32] <magicaltrout> tests are for wimps
[14:32] <caribou> :)
[14:33] <magicaltrout> dunno, i asked marco the other day, he said, just write them in python so I did it like that
[14:33] <magicaltrout> i've not tried testing them yet
[14:35] <mattyw> rick_h, ping?
[14:35] <rick_h> mattyw: otp pong
[14:36] <marcoceppi> caribou: magicaltrout you could do this, a pattern some charms have produced: https://github.com/juju-solutions/vpe-router/
[14:36] <marcoceppi> that's a python stub for the actions/<action> and then a start of the reactive loop
[14:37] <marcoceppi> it's not super clean, but it's something we're looking at cleaning up in reactive
[14:37] <marcoceppi> caribou magicaltrout alternatively, put the heavy lifting in lib/charms/layer/ and import it from the action stub
[14:37] <marcoceppi> unit test the library and don't worry about the stub
[14:38] <caribou> marcoceppi: hmm, good idea
[14:38] <stub> or land stub's branch to avoid the stub
[14:40] <marcoceppi> stub's stub is one approach
[14:40] <marcoceppi> fwiw stub, we'll be looping back around to reactive 2.0 in the coming weeks, actions is one of the items on this list
[14:41] <caribou> magicaltrout: marcoceppi: that seems to do the trick as well : collect = imp.load_source('collect', 'actions/collect')
[14:41] <caribou> at the top of the test script, instead of "import actions.collect"
[15:19] <stub> marcoceppi: I need to be writing actions in under two weeks time, in reactive 1.
[15:55] <mattyw> anyone around for a question about contraints?
[16:04] <pmatulis> mattyw, dunno, best ask
[16:05] <mattyw> pmatulis, according to the docs it's acceptable to set the arch constraints to no value. but: juju deploy ./ msql --constraints "arch=""" --series win2012r2 returns ERROR cannot add application "msql": invalid constraint value: arch=
[16:06] <aisrael> marcoceppi: stub: Unless I'm missing some context here, actions in reactive aren't terribly difficult, just a little clunky. Totally functional, though.
[16:06] <pmatulis> mattyw, yeahh i saw something similar with 'mem'
[16:06] <pmatulis> mattyw, i think something changed recently
[16:09] <stub> aisrael: I need actions that tie into the reactor. I can't do that without my patch, and I've seen no alternatives.
[16:10] <aisrael> stub: This is what I've been doing for actions: https://github.com/AdamIsrael/vnfproxy
[16:13] <stub> aisrael: Hmm... You might have reimplemented my branch from 6 months ago, but without the charms.reactive patches
[16:14] <aisrael> stub: Dunno. I've been using actions with reactive like this almost since reactive was released.
[16:15]  * aisrael smells a blog post
[16:15] <stub> aisrael: I don't recall it being brought up in Pasadena, and haven't heard it mentioned as an alternative
[16:16] <stub> aisrael: (which is surprising, since I've been escalating this the last month)
[16:17] <aisrael> stub: I'll make a point to call it out more. I didn't realize it was a pain point. I've been head-down working on open source mano and must have missed the discussion. :(
[16:21] <stub> aisrael: I'll need to revisit my old branch, but I think all that is missing is the @action decorator and that is just a style choice.
[16:22] <aisrael> stub: I'm happy to take a look at what you've got. I definitely think we can make actions easier to implement
[16:22] <stub> aisrael: https://github.com/juju-solutions/layer-basic/pull/69/files was my template, which might look very familiar :)
[16:23] <aisrael> Hah, sure does. Yours is pulling the action name directly from hookenv, which is something I wanted to add to my template. :D
[16:24] <stub> aisrael: oh, my reactive patch is adding a new phase so the main action body is guaranteed to kick in before the rest of the reactive handlers. But I don't think I need that, at least for now.
[16:26] <stub> aisrael: Ta. This unblocks me nicely :)
[16:26] <aisrael> stub: Excellent, good to hear!
[16:32] <stub> (amusingly, I used to have states too for actions but removed that from the patch on request ;) , https://github.com/juju-solutions/charms.reactive/pull/66 )
[16:38] <aisrael> stub: I'll try to  weigh in on that discussion today or tomorrow.
[16:38] <marcoceppi> cory_fu: I'll merge, but I could use a review https://github.com/juju/charm-tools/pull/298
[16:42] <cory_fu> marcoceppi: Comment added: Do you think you could add a trusty series to the mysql layer's metadata.yaml to ensure that de-dupe works across layers as well (since you ran in to that while testing)?
[16:42] <marcoceppi> cory_fu: sure
[16:43] <kjackal> cory_fu: kwmonroe: Here is the error http://pastebin.ubuntu.com/23747121/
[16:44] <stub> marcoceppi: I think you lose the declared series ordering, so the preferred series (first) might change when you 'charm build'
[16:45] <marcoceppi> probably should use ordered set then stub ?
[16:45] <stub> marcoceppi: There is an ordered set?
[16:45] <marcoceppi> I mean, "yes"
[16:46] <stub> (hey, there is an ordered dictionary... wouldn't surprise me if there was an ordered set lurking around somewhere in stdlib)
[16:46] <marcoceppi> it's not in stdlib, but there's a generally accepted class that implements it
[16:47] <kjackal> cory_fu: kwmonroe: something very important cwr filed but it did not retrun an error code so the script tried to release the charms (even if the tests failed)
[16:47] <cory_fu> kjackal: There's a card on the board for that
[16:49] <kjackal> cory_fu: so how can we move forward with this PR then? Should we have a check (eg grep FAILURE) against the output directory and stop the jenkins job?
[16:49] <cory_fu> kjackal: We should address the card on the board and make cwr return a proper exit code
[16:50] <cory_fu> kjackal: Ok, I know what the problem is.  Your invocation with the charm doesn't have a reference bundle
[16:51] <cory_fu> kjackal: http://54.205.68.190:8080/job/charm-apache-tomee/2/console vs http://54.205.68.190:8080/job/charm-topbeat/2/console
[16:51] <kwmonroe> ahhh. nice!
[16:51] <cory_fu> PM'd you the login
[16:52] <cory_fu> kjackal: Note the "echo 'bundle: /tmp/bundles/'" vs "echo 'bundle: /tmp/bundles/cs_beats_core'"
[16:53] <cory_fu> We need to detect no reference bundle and use the charm path / name instead
[16:53] <cory_fu> That, or make the reference bundle required
[16:54] <cory_fu> I'm leaning toward the latter
[16:55] <kjackal> cory_fu: if we make the reference bundle required then we are losing all our customer base :)
[16:57] <kjackal> I am not sure, I am a bit puzzled
[16:57] <marcoceppi> stub: good catch on the ordering
[16:58] <kjackal> cory_fu: so we will say if you want to make a charm you should first have a bundle for it before using the CI we are building?
[16:58] <cory_fu> kjackal: Part of the justification for reference bundle is that we want to heavily push for testing of bundles instead of charms.  I don't think it's unreasonable to make that a requirement, but I'm not 100% set on it.
[16:58] <cory_fu> arosales: What's your opinion on that?  ^
[16:58] <cory_fu> kjackal: Pretty much, yes
[16:59]  * arosales reads back scroll
[16:59] <cory_fu> kjackal: Otherwise, you're back to having to write amulet tests to get any testing done.  If you have even a trivial bundle, you can test it with matrix
[17:00] <arosales> we had talked about policy in making a reference bundle mandatory, thus I would be a +1 on making a reference bundle mandatory
[17:00] <arosales> a charm that doesn't have a bundle doesn't make much sense
[17:00] <arosales> I guess at a very minimum if someone did have a use case for a single charm they could still make a bundle of 1 charm. I wouldn't suggest it, but there is still that option
[17:01] <arosales> cory_fu: kjackal  ^
[17:03] <kjackal> arosales: cory_fu: It is a chiken and egg issue here. Let say we want to have a CI for juju from day 1 of development. That means that day 0 should start with creting a bundle. And day 2 you can create a charm.
[17:03] <kjackal> arosales: cory_fu: anyway, I am out for today
[17:04] <kjackal> On Monday, i will look at the multiple controllers
[17:04] <kjackal> bye
[17:05] <marcoceppi> cory_fu: I found another problem, the way combine works
[17:05] <marcoceppi> it's appending series list, instead of prepending
[17:06] <cory_fu> marcoceppi: Why is that wrong?
[17:07] <marcoceppi> cory_fu: if lower layer is trusty, precise, and upper layer is xenial, trusty, order will be trusty, precise, xenial
[17:08] <marcoceppi> but upper layer should take precedence
[17:08] <cory_fu> Ah, yeah
[17:29] <stokachu> rick_h, thanks re: storage on lxd
[17:30] <rick_h> stokachu: <3
[17:30] <arosales> kjackal: I think in that case we could still just have a bundle of 1 charm
[17:30] <arosales> at a very minimum if that charm doesn't have any relations yet
[17:44] <smgoller> hey all, so I'm using 2.1 beta3 to talk to maas 2.1. When I try to bootstrap, juju errors out because MAAS doesn't support the 1.0 api anymore. Is there a workaround for this?
[17:46] <lazyPower> marcoceppi - got a second? mbruzek and I are looking to share a controller we have hosted for the team, but we want teh shares to be admin level users
[17:47] <lazyPower> can you grant controller wide admin access?
[17:48] <rick_h> lazyPower: grant superuser https://jujucharms.com/docs/2.0/users-models#controller-access
[17:48] <lazyPower> rick_h ta
[18:24] <smgoller> anybody? How do I tell juju to use api version 2?
[18:24] <smgoller> (for maas)
[18:29] <smgoller> this is the error i'm getting
[18:29] <smgoller> 2017-01-05 17:57:23 ERROR cmd supercommand.go:458 new environ: Get http://<ipv4address>/MAAS/api/1.0/version/: dial tcp <ipv4address>:80: getsockopt: connection timed out
[18:29] <smgoller> ERROR failed to bootstrap model: subprocess encountered error code 1
[18:29] <smgoller> but curl on that url from the host works just fine
[18:46] <lazyPower> smgoller what version of juju?
[19:17] <magicaltrout> so here's a weird one
[19:17] <magicaltrout> that is completely left field at the moment, but I need to figure out how to deploy Juju stuff to this bad boy... https://www.tacc.utexas.edu/systems/wrangler
[19:17] <magicaltrout> thats quite a powerful computer...
[19:23] <cory_fu> marcoceppi: Are you working on the append vs insert issue or is #298 ready for review again?
[19:24] <h00pz> hey folks got a mysql question regarding the openstack deployment from juju
[19:27] <lazyPower> magicaltrout hoooo, DSSD rack scale? I bet that disk IO is *in-sane*
[19:27] <lazyPower> analytics with bandwidth of 1TB/s and 250M IOPS (6x faster than Stampede)
[19:27] <marcoceppi> cory_fu: working on it
[19:28] <h00pz> in the past (non juju deployed openstack) I would be able to log into my mysql servers and do a “show databases;” and voila my openstack dbs
[19:28] <h00pz> now I juju ssh mysql/0 and then log into mysql and do the same and all I see is schema and test
[19:29] <lazyPower> h00pz - not to be daft, but i'm fairly certain our openstack offering uses percona
[19:29] <lazyPower> wouldn't that then be warehoused in percona/0 not mysql/0?
[19:29] <h00pz> yah it does hence my complete lack of brain cells
[19:29] <lazyPower> well I wasn't going to go that far :D  Its a common mistake
[19:29] <lazyPower> i do ask, as some people modify the bundle, and its not always obvious if thats the case
[19:30] <h00pz> ubuntu@maas:~$ juju status | grep percona
[19:30] <h00pz> mysql                  5.6.21-25.8  active          1  percona-cluster        jujucharms  246  ubuntu
[19:30] <h00pz> ubuntu@maas:~$ juju ssh percona/0
[19:30] <h00pz> ERROR unit "percona/0" not found
[19:30] <h00pz> so mysql/0 exists but not percona/0
[19:30] <lazyPower> ok, they aliased the percona charm as mysql
[19:31] <lazyPower> makes sense to me so far. When you log into the percona unit you dont see any databases related to openstack right?
[19:31] <rick_h> h00pz: right, you can name the applications once deployed whatever you want.
[19:31] <h00pz> correct
[19:31] <lazyPower> hmmm
[19:31] <rick_h> h00pz: e.g. you might deploy mysql twice, once as mysql-leader, and a second time as follower
[19:32] <h00pz> i did a first-timer juju deploy of the basic openstack bundle and didn’t fiddle with it.
[19:32] <rick_h> h00pz: so to ssh to each you'd use your names you gave it, mysql-leader and such
[19:32] <h00pz> services are working fine i just need to edit a couple fields (i tied to delete vms when rabbitmq was down)
[19:33] <rick_h> h00pz: right, so juju ssh mysql/0 should work for you in this case?
[19:33] <h00pz> yes that does and once in there no darn dbs
[19:33] <rick_h> h00pz: this was running before or is a new deploy?
[19:34] <h00pz> been running fine (and still is) for over a month
[19:34] <h00pz> im just trying to find the darn dbs to edit some stuff
[19:35] <rick_h> h00pz: k, and how are you listing the dbs on the mysql?
[19:35] <h00pz> ubuntu@maas:~$ juju ssh mysql/0
[19:35] <h00pz> ubuntu@juju-e039b2-0-lxd-1:~$ mysql -u mysql
[19:35] <h00pz> mysql> show databases;
[19:35] <h00pz> +--------------------+
[19:35] <h00pz> | Database           |
[19:35] <h00pz> +--------------------+
[19:35] <h00pz> | information_schema |
[19:35] <h00pz> | test               |
[19:35] <h00pz> +--------------------+
[19:35] <h00pz> 2 rows in set (0.00 sec)
[19:36] <rick_h> h00pz: can you get an interactive mysql shell and try "SELECT User FROM mysql.user;"
[19:37]  * rick_h dusts off some old mysql know-how
[19:37] <bildz> heh
[19:37] <bildz> im sitting next to h00pz btw
[19:37] <rick_h> bildz: howdy
[19:37] <bildz> hey rick_h
[19:38] <h00pz> its telling me to faq off, clearly no adequate perms
[19:38] <rick_h> bildz: h00pz so my suspicion is that it's not showing all databases, but only the ones you have permission to see
[19:38] <rick_h> bildz: h00pz so the ones for the OS aren't shown as the charms will create users/dbs with permissions in case that mysql is reused with other applications
[19:38] <rick_h> e.g. a blog and a drupal and a ...
[19:38] <rick_h> h00pz: bildz so try using "sudo mysql
[19:39] <bildz> yeah that's very odd
[19:39] <rick_h> to get mysql running as root
[19:39] <rick_h> sorry, w/o the "
[19:39] <bildz> well, you can mysql -u root -p
[19:39] <bildz> same thing
[19:39] <rick_h> ok, same thing
[19:39] <rick_h> bildz: but not mysql -u mysql?
[19:39] <rick_h> bildz: so might be completely
[19:39] <bildz> im guessing we could parse the configs of services using mysql to see what it's using :)
[19:40] <rick_h> sudo mysql
[19:40] <rick_h> use mysq;
[19:40] <rick_h> select User from mysql.user;
[19:40] <bildz> yeah basing that root has no passwd
[19:40] <rick_h> bah, use mysql;
[19:40] <bildz> but its appearing to have one
[19:40] <rick_h> right, it's ubuntu so you should be able to sudo from the ubuntu user
[19:40] <smgoller> lazypower: I figured it out. it's not an api problem
[19:40] <smgoller> it's a network connectivity problem.
[19:41] <smgoller> the problem being the command was being executed on the bootstrapped controller, not the machine i was running the bootstrap from
[19:41] <lazyPower> smgoller ok good :)
[19:41] <smgoller> and the controller couldn't talk to maas
[19:41] <lazyPower> glad you figured out the blocker
[19:41] <lazyPower> i wasn't entirely sure where to start but i figured best to start with what juju
[19:41] <lazyPower> and go from there
[19:41] <lazyPower> +1 for your debugging routine :)
[19:42] <h00pz> yah so imi thinking that the only way to get into the openstack table space is from the root user WITH PASSWORD which we dont know or setup during the juju deploy
[19:42] <lazyPower> h00pz thats in /var/lib/mysql  or /var/lib/percona respectively
[19:42]  * rick_h goes to deploy the percona-db charm and will be back in a sec
[19:43] <lazyPower> h00pz specifically /var/lib/mysql/mysql.passwd
[19:43] <h00pz> on the controller ?
[19:43] <lazyPower> That should exist on any mysql unit you have deployed
[19:44] <lazyPower> thats a convention baked into the db charms when it auto-generates a password, it leaves a little cache file around on disk with the contents of the root users password, only readable by root
[19:45] <h00pz> i have /var/lib/percona-xtradb-cluster but no mysql.passwd
[19:49] <h00pz> i did a find and a grep for that file name, no dice
[19:57] <lazyPower> hmm
[19:57] <lazyPower> perhaps something changed and i wasn't aware its been a bit since i've looked at those charms
[19:57] <lazyPower> beisner, or thedac - any suggestions on how to get the root password for the percona charm these days?
[19:58] <rick_h> lazyPower: h00pz bildz this is the only thing I can find atm https://help.ubuntu.com/community/MysqlPasswordReset
[19:58] <rick_h> lazyPower: h00pz bildz lots of thing say that if not provided during install it creates on in the log file
[19:59] <rick_h> but my deploy doesn't have a password line I can tell
[19:59] <beisner> howdy lazyPower, we typically set it on deploy, but i think there is a retrieval method.  pretty sure it's in rel data.  thedac may have more detail?
[20:00] <rick_h> https://jujucharms.com/percona-cluster/#charm-config-root-password yea
[20:00] <rick_h> hmm, /me wonders if you can change it via charm config?
[20:00] <h00pz> bwahahahaha are telling me I can set it through the juju gui
[20:01] <rick_h> h00pz: I'm testing it out :)
[20:01] <rick_h> h00pz: hmm, doesn't look like it took
[20:01] <h00pz> this —> Root password for MySQL access; must be configured pre-deployment for Active-Active clusters. <—
[20:02] <rick_h> yea...that seems about right
[20:02] <h00pz> lemme try
[20:03] <h00pz> nope might have to try lazypower’s suggestion to break the passwoid
[20:03] <lazyPower> beisner ok, i hand't thought about the rel data being the key holder. Percona is non reactive correct?
[20:05] <rick_h> h00pz: bildz yea, have to suggest to go the password recovery route
[20:05] <rick_h> seems this is the way it works these days to keep things secure
[20:05] <h00pz> k will do thanks guys.
[20:05] <kjackal> cory_fu: I am doing two minor changes in "Store and serve CWR reports and build artifacts"
[20:06] <beisner> lazyPower, indeed, it's old style
[20:06] <cory_fu> kjackal: What changes?
[20:07] <magicaltrout> indeed lazyPower that is some serious compute power
[20:07] <magicaltrout> not sure how i'm gonna get charms deployed on int
[20:07] <magicaltrout> it
[20:07] <magicaltrout> but always like a challenge
[20:07] <kjackal> cory_fu: the ref-bundle param should be mundatory in the build-on-release as well and something is not right in the descriptiona
[20:08] <cory_fu> kjackal: OK, thanks
[20:23] <kjackal> cory_fu: last show stopper in this PR (at least for me) is the CWR not reporting a failure. How do we want to handle this in respect to the PR. Should we merge the PR now knowing that this needs to be fixed or should we keep the PR pending?
[20:25] <cory_fu> kjackal: It will have to be fixed in the CWR repo anyway, so I'd say treat it as a separate issue.
[20:25] <cory_fu> kjackal: However, hold on one sec, I have one more minor change to make
[20:29] <cory_fu> kjackal: Ok, pushed
[20:29] <kjackal> cory_fu: Ok, so we move forward with the merge (as soon as you are done). One last question. What is more important: multiple controllers vs cwr retruning an error code on failure? If you ask me the latter because with that PR the build-on-* are not safe to be used.
[20:30] <kjackal> Basically I am asking for priority of tasks for Monday morning
[20:31] <cory_fu> kjackal: Well, they're safe to use if you don't use push-to-channel, and that won't affect our demo next week, so I'd actually say the multiple clouds is higher.  But they're both important.
[20:32] <kjackal> Ok, multiple controllers it is then (unless someone else goes for it tomorrow)
[20:33] <magicaltrout> marcoceppi: i get the feeling i'll know the answer to this but.... if i wanted to use the manual provider, apart from the controller, do the other units need to be Ubuntu?
[20:33] <lazyPower> magicaltrout nah you can manually enlist other series
[20:33] <lazyPower> i'm like 80
[20:33] <lazyPower> % certain of this
[20:33] <lazyPower> its that last 20% that might bite you
[20:33] <magicaltrout> lol
[20:34] <magicaltrout> well i'll have a bunch of other issues as well so i'll need to fork and extend
[20:34] <magicaltrout> but its worth investigating
[20:37] <kjackal> cory_fu: Sorry to bother you again. Do we export the cloud credentials so that Matrix knows about them? What should happen in the case of multiple controllers?
[20:38] <cory_fu> kjackal: Ugh
[20:39] <cory_fu> kjackal: You're right.  And now I realize that my work-around of using the env var won't work
[20:40] <cory_fu> kjackal: I can't believe I missed that
[20:54] <cory_fu> kjackal: Ok, I removed the exports.  I'll have to figure out another way to do it
[20:57] <kjackal> cory_fu: multiple controllers seems an easy task. Should be one day.
[20:59] <kwmonroe> kjackal: cory_fu: where did the "usage: cwr [-h] [--result-output RESULT_OUTPUT]" get fixed?  kjackal reported it in pr21 because the cwr invocation was --result-dir (not --result-output).  was there a commit in layer-cwr to update the install location of cloud-weather-report?
[20:59] <cory_fu> kwmonroe: kjackal somehow had an old version of cwr
[20:59] <kwmonroe> right cory_fu.. now i've got it.
[21:00] <kwmonroe> and iirc, pypi wasn't updated, so layer-cwr did a clone/install (or wget master.zip or something)
[21:00] <kjackal> kwmonroe: cory_fu: yes, I probably had an old cwr. Probably because I reused a jenkins deployment
[21:10] <sfeole> hey guys, i'm working on a new charm and the install hook keeps failing with the following:   http://pastebin.ubuntu.com/23748751/     looks to be related to wheelhouse, has anyone ran into this before?
[21:12] <thedac> lazyPower: looking that up for you now. The file is written on disk somewhere. Not where I expected. Give me a few.
[21:16] <thedac> lazyPower: no it is shipped of to leader settings: juju run --unit percona-cluster/0 leader-get
[21:16] <lazyPower> thedac aha! thats excellent. Thanks for the follow up
[21:17] <lazyPower> h00pz - still poking around?
[21:17] <thedac> no problem
[21:20] <kwmonroe> kjackal: did you fix it by manually updating cwr on the jenkins slave?  i ask because my cwr charm (on the jenkins unit) says to pip_install_from_git, so i know that's correct.  however, the cwr installed on the jenkins system is *not* the same as the github repo.
[21:21] <kwmonroe> it's like cwr is getting pip installed prior to the 'pip_install_from_git' and being skipped.
[21:21] <kwmonroe> cory_fu: do you have pypi release rights to cwr?
[21:21] <kwmonroe> (not that that's the right answer, just curious)
[21:24] <cory_fu> kwmonroe: I do not.  Only ses
[21:24] <kjackal> kwmonroe: I am back. So I fixed it by going to bed and woke-up realising what I was doing wrong
[21:24] <kwmonroe> :)
[21:24] <kjackal> kwmonroe: let me parse what you are sayiing
[21:25] <kwmonroe> kjackal: let me help:  i deployed the latest cwr-ci bundle and upgraded the cwr charm with the feature/reports-and-artifacts branch.
[21:25] <kwmonroe> the jenkins principal has an old version of cloud-weather-report pip installed
[21:26] <kjackal> yeap, that will not work.
[21:26] <kwmonroe> it doesn't seem to be using the "pip_install_from_git(..., http://repo/c-w-r)
[21:26] <kjackal> I just destroyed the model and tried manually from scrach
[21:26] <cory_fu> kwmonroe: It's working fine for me
[21:27] <kwmonroe> not possible!
[21:27] <cory_fu> kwmonroe: As kjackal said, did you re-deploy the jenkins, or did you upgrade it from an old deploy?
[21:28] <cory_fu> kwmonroe: Of course, this would be moot if we had the workloads containerized.
[21:28] <kwmonroe> cory_fu: this is a new jenkins deploy.. from ~kos.<greek-name>
[21:28] <cory_fu> Very strange
[21:30] <kwmonroe> cory_fu: should cwr be in the /var/lib/juju/agent/cwr/.venv or on the system?  it feels like i'm getting cwr installed outside of the cwr charm.  and that feels bad.
[21:30] <cory_fu> I've deployed many times and not hit that, but it might be a heisenbug
[21:30] <cory_fu> kwmonroe: It should be in the system now, because it's not python3 so isn't compatible with the venv.  Really, it should be in the containerized job env
[21:30] <kwmonroe> heh, you keep saying "containerized" like we have time to do something about that
[21:31] <cory_fu> Yeah.  :(
[21:32] <magicaltrout> fix it!!!! fiiiiix iiiiiiit!
[21:32] <kwmonroe> well, i had a stale ciuser preventing me from doing the build-on-commit, so let me tear all the way down again.  if i deploy cs:~kos.greek/jenkins + local cwr from feature/reports-and-artifacts, i should have a cwr that supports --results-dir?
[21:33] <cory_fu> Yes
[21:35] <kwmonroe> awww heck.  i know what happened.  i didn't upgrade jenkins, but i did 'cwr' (hence cwr-ci.installed was already set).  damn.
[21:38] <cory_fu> kwmonroe: :)
[21:39] <kwmonroe> totally not my fault.  you asked "did you re-deploy the jenkins ... or upgrade it".  you said nothing of the cwr subordinate.
[21:51] <cory_fu> tvansteenburgh, kwmonroe, petevg: https://github.com/juju/python-libjuju/pull/43
[21:51] <kwmonroe> i don't look at PRs until travis is done
[21:52] <cory_fu> :)
[21:52] <tvansteenburgh> i don't look at PRs when ppl ping me about them right after i get the email from github
[21:53] <cory_fu> lol
[21:55] <kwmonroe> cory_fu: i'll approve this part: https://github.com/juju/python-libjuju/pull/43/files#diff-9aa2102e02a5e20ed59d041e8ee2b2e4L91, tvansteenburgh can approve the rest.  python async isn't really my thing.
[21:55] <tvansteenburgh> haha
[21:55] <tvansteenburgh> that line was there for a reason, -1
[21:57] <kwmonroe> good point.  lack of comment for why 2 blank lines weren't needed.  -1.
[21:57] <cory_fu> tvansteenburgh: Was the reason to give lint errors?
[21:58] <cory_fu> kwmonroe: Do you want lint errors?  Because this is how you get lint errors.
[21:58] <kwmonroe> lol
[21:58] <tvansteenburgh> cory_fu: confirmed
[21:58] <cory_fu> :)
[21:58] <cory_fu> Ok, travis passed.  Someone feel free to merge it so I can submit my next PR
[21:58] <cory_fu> ;)
[22:02] <cory_fu> kwmonroe, petevg: https://github.com/juju-solutions/matrix/pull/66
[22:02] <cory_fu> petevg: Ok, looking at your PR now.  Sorry for the delay
[22:03] <kwmonroe> whitespace seems legit
[22:07] <petevg> That's my bad, apparently.
[22:07] <petevg> I usually catch that sort of nonsense.
[22:10] <kwmonroe> petevg: emacs has a box for "add superfluous whitespace".  maybe check that out.
[22:13] <cory_fu> petevg: Technically, that indentation was correct, because the timeout value went with the wait_for(), but I changed it to make it less confusing
[22:14] <petevg> cory_fu: ah. You are right.
[22:14] <cory_fu> Sometimes getting indentation to be reasonable while sticking to < 80 columns is a PITA
[22:17] <cory_fu> petevg: Crap, that's a good catch.  I think that log message is rather important, so I'm +1 to blocking that until I can figure out a fix.
[22:17] <petevg> cory_fu: cool.
[22:17] <petevg> I don't have any immediate suggestions. unfortunately :-/
[22:18] <petevg> cory_fu: you might actually be able to do try: else: finally, actually (all on the same indentation level).
[22:19] <petevg> ... though I'm not sure how to nested Exception will interact with it ...
[22:20] <cory_fu> petevg: Actually, the way it's structured, crashdump won't happen if add_model fails
[22:20] <petevg> That's not good either.
[22:20] <petevg> cory_fu: thx for merging the output dir PR. :-)
[22:24] <petevg> cory_fu: darn. If an exception is raised during an "else" after a try-except, it doesn't look like the "finally" executes :-(
[22:25] <petevg> cory_fu: actually, hang on ... it does work. Flaw in my script.
[22:25] <cory_fu> petevg: Too late, it's updated
[22:26] <cory_fu> Yeah, I tested it and it seems to work properly with the else
[22:26] <cory_fu> Though, TBH, if run_once kicks up an uncaught exception, I'm pretty sure it will hang Matrix
[22:27] <cory_fu> But it has internal exception catching, so it should be ok
[22:28] <petevg> cory_fu: I think that run_once won't hang matrix. An uncaught Exception in the "finally" block definitely will, but there's not too much to be done about that other than being careful.
[22:28] <petevg> cory_fu: in any case, I am +1 on this.
[22:29] <cory_fu> Sweet, gonna merge it
[22:29] <cory_fu> We might actually have a demo yet.  ;)
[22:30] <cory_fu> Ok, I have to EOD now.
[22:31] <tvansteenburgh> cory_fu: https://github.com/juju/python-libjuju/tree/local-charm-bundle-support
[22:31] <tvansteenburgh> i just deployed a bundle with local charms using that branch
[22:31] <cory_fu> tvansteenburgh: That's fantastic!
[22:32] <tvansteenburgh> needs some cleanup before merge, but feel free to test it out
[22:32] <tvansteenburgh> i have to eod now too, will finish it up in the morning
[22:46] <cholcombe> how does the charm review process work again with promulgated charms and their code living at github?
[22:49] <rick_h> cholcombe: use the review queue to submit a request for review
[22:49] <cholcombe> rick_h, is it still review.juju.solutions?
[22:50] <cholcombe> rick_h, nvm i found the link
[22:50] <rick_h> cholcombe: I thought the old one was going away but that doesn't look right
[22:52] <cholcombe> rick_h, https://review.jujucharms.com/reviews/81 looks good :)
[22:53] <rick_h> cholcombe: ok cool
[22:53]  * rick_h thought there was a big request review button but is blind atm
[22:53] <cholcombe> yeah you're correct rick.  i was looking at the old site again.  it comes up in my search history.  i need to delete it
[22:54] <rick_h> cholcombe: gotcha
[22:54] <rick_h> ah right, there you go
[22:54] <rick_h> I missed the url change from first paste to the other
[22:59] <cholcombe> rick_h, do you know if amulet works with juju storage yet?  that was my blocker last time
[23:00] <rick_h> cholcombe: not that I'm aware of
[23:00] <cholcombe> gah
[23:18] <marcoceppi> cholcombe: so amulet will slowly be deprecated for python-libjuju. Amulet will eventually adopt libjuju instead of deployer at which case you'll have access directly to the model
[23:19] <cholcombe> marcoceppi, interesting
[23:19] <cholcombe> marcoceppi, so should i start developing against libjuju?
[23:22] <marcoceppi> cholcombe: if you're comfortable with async io
[23:22] <cholcombe> i am but it looks like libjuju is also missing storage support
[23:22] <marcoceppi> cholcombe: it shouldn't it implements every aspect of the Juju api
[23:23] <cholcombe> hmm alright i'll dig deeper