/srv/irclogs.ubuntu.com/2016/04/18/#juju.txt

=== stub` is now known as stub
=== frobware_ is now known as frobware
jamespagegnuoy, do you need me to work through the mitaka keystone v3 updates?09:12
gnuoyjamespage, yes please. just be carefull, there are two with pending results from full rechecks09:14
gnuoyjamespage, oh, actually just one needs us to wait09:15
jamespagegnuoy, I'm assuming you have exercised them with v3 as the amulet tests don't right?09:15
gnuoyjamespage, I did, yes. I've marked the spreadsheet as such09:22
jamespagegnuoy, \o/ +1000 thankyou09:22
jamespagegnuoy, ok they all look good - https://review.openstack.org/#/c/306861/ pending full recheck..09:24
gnuoykk09:25
=== magicalt1out is now known as magicaltrout
gnuoystub, do you write unit tests for any of juju interfaces on http://interfaces.juju.solutions/ ?10:21
stubgnuoy: No. I haven't used them either ;)10:22
=== JoseeAntonioR is now known as jose
=== freeflying__ is now known as freeflying
=== Ursinha_ is now known as Ursinha
=== cppforlife__ is now known as cppforlife_
gnuoyjamespage, got a sec for https://review.openstack.org/#/c/306861/ ?11:32
jamespagegnuoy, done11:36
jamespagegnuoy, about to clone release notes btw11:36
gnuoythanks11:36
gnuoyok, ta11:36
jamespagegnuoy, just a straight copy from 16.01 for now11:38
jamespagehttps://wiki.ubuntu.com/ServerTeam/OpenStackCharms/ReleaseNotes160411:38
gnuoyjamespage, is there a bug for the dashboard upgrade issue you mentioned?11:47
jamespageyes11:47
=== Guest39780 is now known as CyberJacob
=== CyberJacob is now known as Guest41374
=== Guest41374 is now known as CyberJacob
jamespagerockstar, is https://review.openstack.org/#/c/305896 ready to go? I was wondering how your got your commit message into that state?12:03
=== mhall119_ is now known as mhall119
=== jrwren_ is now known as jrwren
=== fginther` is now known as fginther
beisnerhi gnuoy, a lil ++debug @ https://code.launchpad.net/~1chb1n/openstack-mojo-specs/fix-git-checkout-stable/+merge/292078 if you will13:38
beisnerready to land if you're +!13:39
beisner+1 even ;-)13:39
=== A-Kaser_ is now known as A-Kaser
gnuoybeisner, approved13:47
beisnergnuoy, thx sir13:47
gnuoynp13:47
=== plars_ is now known as plars
beisnergnuoy, fyi, i'm going to merge your os-mojo precise bundle update then follow up with another mp for some other things.  thx for IDing the issue :)14:15
beisneralso, o-c-t bundles updated for precise re: nova no longer neutroning14:16
gnuoykk, thanks14:17
rockstarjamespage: commit message into what state?14:17
rockstarjamespage: it is ready to go, but requires a dependent o-c-t branch which I apparently never pushed on Friday, but thought I had. It's up for review now.14:18
gQuigscan we close (or mark incomplete) all the bugs in pyjuju - I always end up looking https://bugs.launchpad.net/juju  instead of juju-core14:25
jamespagerockstar, re commit message - two change-id's ?14:27
rockstarjamespage: it's two commits squished into one.14:28
rockstar(because openstack)14:28
jamespagerockstar, not sure I understand 'because openstack'?14:30
rockstarjamespage: they like you to squish your patch into a single commit. I don't much care for that workflow, but that's the way they want it.14:31
jamespagerockstar, ok14:31
jamespagerockstar, have you read https://wiki.openstack.org/wiki/GitCommitMessages ?14:32
rockstarjamespage: with respect, it seems that that wiki entry is contradictory to what it wants for gerritt.14:35
jamespagerockstar, all I've really been looking for across other reviews is a decent summary title, some details of what and why the change, closure of bugs and the Change-Id...14:36
rockstarjamespage: I can remove the other Change-Id when I rebase, if that helps. I've just been leaving whatever it gives me.14:38
jamespagerockstar, sure - tbh I was trying to figure out how you got two change-ids?  did you squash two commits together?14:38
rockstarYeah, that's exactly what happened.14:38
rockstarBreaking the "one logical change per commit" rule.14:39
suchvenuHi cory_fu14:44
cory_fuHello14:44
suchvenuI am getting the below error while calling the set_db_details function in my interface14:45
suchvenu2016-04-18 14:37:02 INFO config-changed   File "/usr/local/lib/python3.4/dist-packages/charms/reactive/relations.py", line 256, in conversation 2016-04-18 14:37:02 INFO config-changed     raise ValueError('Unable to determine default scope: no current hook or global scope') 2016-04-18 14:37:02 INFO config-changed ValueError: Unable to determine default scope: no current hook or global scope14:45
suchvenuhttp://pastebin.ubuntu.com/15914037/14:46
suchvenuhas the interface code14:47
cory_fusuchvenu: That error means that your relation is scope SERVICE or UNIT and you are not looping over a list of conversations.  Remember that your db2 charm could have any number of consumers asking for a database at a given time.  Your charm code should have a for loop over each consumer and then do the set up and call set_db_details for each one, passing which consumer in as a param which is given to self.conversation(consumer) to pick up the right15:00
cory_fuone15:00
cory_fusuchvenu: See https://github.com/johnsca/juju-relation-mysql/blob/master/provides.py#L8515:01
mbruzekbdx: I know this is a deep "call back" but regarding the tls layer you mentioned a desire for a provides/requires relation. I created an issue against the repository and was hoping you could comment on that https://github.com/mbruzek/interface-tls/issues/315:01
cory_fusuchvenu: And the pastebin I sent you in the email (http://pastebin.ubuntu.com/15851388/) is slightly wrong.  Line 7 should include $service right before $db_name15:01
suchvenuok.15:02
suchvenuWhen my scope is SERVICE, should i always use15:03
mbruzekbdx: I just want to make sure I captured your request properly and if you have any more information to please add it.15:03
suchvenu conversation = self.conversation()         conversation.remove_state or conversation.set_state  always ?15:03
suchvenudoes self.remove_state and self.set_state also work ?15:03
simonklbHey! What would be the best course of action to find the provided hooks from interfaces listed on http://interfaces.juju.solutions/ ?15:05
simonklbis it simply to read the code provided in the repo?15:05
cory_fusuchvenu: You must always use the conversation, but also have to give it an argument unless you're in a @hook decorated method.  So, set_db_details would need to use: conv = self.conversation(consumer)15:05
simonklbor can you list the hooks somewhere?15:05
suchvenuI mean what is the difference between both ways of calling ?15:05
cory_fusuchvenu: Sorry, I'm going to be a few minutes for a meeting right now.  Should be done in ~ 15 min, but I may be slow to respond until then15:06
suchvenuok, no issues15:06
cory_fusuchvenu: When inside @hook, there is only ever one conversation (for that specific hook)15:07
cory_fuAnd you don't know ahead of time what it is, so you just have to use self.conversation() (with no arg) to have it figure it out from the @hook15:08
BrunoRmarcoceppi: charm push does not work for me, also charm login raise an error, but in Ubuntu-SSO webconsole charm shows up as application?15:10
marcoceppiBrunoR: have you logged into jujucharms.com yet?15:10
BrunoRmarcoceppi: ah, mein fehler15:11
mbruzekHi simonklb a well written layer may not write hooks at all.  What is your requirement here?15:11
marcoceppiBrunoR: it's a weird thing, I'll make sure to document it on the site15:11
simonklbmbruzek: I'm currently just getting to know juju - right now I'm looking at setting up a relation with keystone15:16
simonklbI was under the impression that you used interfaces which provided hooks for you to accuire data from other charms15:16
mbruzeksimonklb: First of all welcome.15:16
simonklbthanks!15:16
simonklbacquire* :)15:17
mbruzeksimonklb: It might help to read this document: https://jujucharms.com/docs/devel/developer-event-cycle15:18
simonklbah, so the hooks are usually named in a specific way15:19
simonklbthats good to know!15:19
simonklbI thought it was more arbitrary15:20
mbruzeksimonklb: To answer your question directly any method decorated by the @hook decorator would signify a hook. So you could search the code for @hook.15:20
simonklbright15:20
mbruzeksimonklb: However with well written reactive layers we have found less of a need to use @hook decorators and rely only on states to make writing layers more natural15:21
simonklbperhaps I should be looking at using the openstack-API layer instead15:22
simonklbbut it felt a bit of an overkill including rabbitmq and mysql when the only thing I really need is to talk to the nova api15:22
mbruzeksimonklb: I don't know if the openstack team has rewritten nova or keystone in layers yet. You may have to look at the traditional hooks in the mean time.15:25
mbruzeksimonklb: If you are looking at the traditional charms (non layered) you should not worry about the interfaces.juju.solutions webpage.15:26
simonklbmbruzek: they have this - http://interfaces.juju.solutions/layer/openstack-api/15:26
mbruzekThey have it but I don't know if they *use* it for any charms yet.15:26
simonklbah I see15:27
simonklbheading home for today, thanks for the help!15:27
simonklbI'll probably pop in here from time to time :)15:27
mbruzekI heard they are moving that direction but I don't know if they have written any charms that way15:27
mbruzekyet15:27
mbruzeksimonklb: anytime15:27
mbruzeksimonklb: let me know if you have any other questions when you get home.15:29
=== Guest15381 is now known as medberry
=== medberry is now known as med_
=== smoser` is now known as smoser
cory_fusuchvenu: Did that solve your problem?15:55
=== scuttle|afk is now known as scuttlemonkey
suchvenucory_fu: I didn;t check it still16:32
suchvenuIf its GLOBAL scope, then we can directly call self.set_state ?16:32
suchvenuI mean only for GLOBAL we can call like that ?16:33
cory_fuOnly for GLOBAL, yes16:36
cory_fuBecause GLOBAL scope means that everything shares the same conversation, no matter what16:36
suchvenuok, for SERVICE and UNIT, conversation is required16:39
suchvenuI will try and let you know. So in the reactive layer, i should call the set_db_details in a loop16:40
=== matthelmke is now known as matthelmke-afk
=== cos1 is now known as c0s
jamespagebeisner, gnuoy: https://review.openstack.org/#/c/307076/ ready for review17:36
beisnerjamespage, thx, on it17:36
=== matthelmke-afk is now known as matthelmke
beisnergnuoy, jamespage (fyi cholcombe ) - got a new one.  bug 1571782 (n-api db migration fail) ... complicating the other t-i one we were drilling down (blocked on block  device detection).17:53
mupBug #1571782: Trusty-Icehouse neutron-api is failing shared-db-relation-changed for mysql:shared-db <uosci> <neutron-api (Juju Charms Collection):New> <https://launchpad.net/bugs/1571782>17:53
=== cherylj_ is now known as cherylj
beisnerand weeee!:  bug 157178918:22
mupBug #1571789: install hook failing on Xenial with unmet dependency on mysql-client <uosci> <percona-cluster (Juju Charms Collection):New> <https://launchpad.net/bugs/1571789>18:22
beisner(pxc: your amulet tests will look at lot different after ODS)18:22
kwmonroecory_fu: when i have relation decorators "@when x; @when y; def foo(x, y)", what's the order of foo() params?  it seems to be (y, x) which is odd to me.18:25
cory_fukwmonroe: It follows Python decorator ordering which is a bit odd.  Basically, decorators are processed inside-out (a.k.a. bottom up) and then the args are processed left-to-right.18:27
kwmonroeoh cool - TIL.  thx cory_fu.18:27
cory_fuSo @when x; @when y z; def foo(y, z, x):18:27
cory_fuIt tripped me up just the other day, in fact18:27
=== redir is now known as redir_lunch
=== redir_lunch is now known as redir
BrunoRafter charm push and publish, the named store still shows the old revision of my charm. is there a step which I overlooked?19:08
cory_fuBrunoR: What's the charm store URL?19:17
cory_fuBrunoR: You might need to set the acl, or if you're referring to a promulgated charm then it requires a charmer and another step for promulgation19:21
BrunoRcory_fu: https://jujucharms.com/u/3-bruno/ , e.g. the quobyte-registry charm is linked in revision 2, I would expect revision 419:22
cory_fuBrunoR: Hrm.  That's odd.  https://jujucharms.com/u/3-bruno/quobyte-registry/ points to 4 and everything looks fine in `charm show cs:~3-bruno/trusty/quobyte-registry id published perm`19:27
cory_fuBut your namespace isn't updated19:27
cory_fuThe search page is up to date as well: https://jujucharms.com/q/quobyte-registry19:28
cory_fuBrunoR: Looks like an issue with namespaces19:28
cory_fuLooks like it's affecting ~bigdata-charmers as well19:29
cory_fuBrunoR: Please file a bug at https://github.com/CanonicalLtd/jujucharms.com/issues19:30
=== cos1 is now known as c0s
jamespagebeisner, I swear I installed a pxc on xenial this morning...20:12
beisnerjamespage, yah i'm puzzled too.  the only thing i can think is an image rev, and a dropped pkg20:12
beisnerie. remnants of the mysql 5.6 thing20:13
=== fginther` is now known as fginther
beisnerjamespage, fyi pushed unit test update20:20
jamespagebeisner, ack - look shortly20:20
beisnerthx jamespage20:21
jamespagebeisner, rockstars lxd stuff is not landing - I suspect that its the double Change-Id20:21
beisnerlolz20:21
jamespagebeisner, trying again - https://review.openstack.org/#/c/305896/20:22
=== redir is now known as redir_afk
gnuoybeisner, my gut feel for Bug #1571782 is that you've somehow got an old version of nova-cloud-controller charm. If you hit it again can you attatch the /var/log/juju/* logs from neutron-api and nova-cloud-controller please?20:56
mupBug #1571782: Trusty-Icehouse neutron-api: Table 'quotas' already exists <uosci> <neutron-api (Juju Charms Collection):New> <https://launchpad.net/bugs/1571782>20:56
beisnerjamespage, sure enough, yesterday, a xenial image had mysql-client-5.6 pkg avail:  http://pastebin.ubuntu.com/15920829/20:57
beisnergnuoy, http://10.245.162.36:8080/view/Dashboards/view/Mojo/job/mojo_runner_baremetal/623/consoleFull20:57
beisner00:14:39.627 2016-04-18 19:18:27 [INFO] cloning git://github.com/openstack/charm-nova-cloud-controller20:58
beisnerfyi ^ and yes indeed, more runs underway.20:58
iceyany chance on  quick C-H review? https://code.launchpad.net/~chris.macnaughton/charm-helpers/use-lsblk-to-check-mount/+merge/29219920:59
iceycholcombe: can I get a community review on ^^21:01
cholcombeicey, i'm on it21:01
iceythanks!21:02
beisnericey, what are your intentions with such a thing?  ;-)   you wanna resync some things dontchya?21:02
iceybeisner: I so do!21:02
iceythe ceph/ceph-osd charms can21:02
iceycan't do encryption without that21:02
iceybecause C-H was wrong about detecting if something is moutned21:02
icey:-D21:02
beisnericey, is there a blocking bug on our 16.04 release checklist for that?21:02
iceyno....?21:03
beisnerat this point, i'm only inclined to land things that directly unblock those blockers21:03
iceybeisner: the charm as it stands today will happily deploy itself to broken :)21:03
iceyyour choice ;)21:03
beisnerie.  this would be a fix to land in next/master after 16.04, then do a stable charm update / backport.21:03
beisnerdood where's your bug?21:03
beisnerwhat targets/combos are affected?21:03
iceyuhm, anything hitting infernalis +, so wily+xenial?21:04
* beisner waits for bug21:04
iceyit'll solve https://bugs.launchpad.net/charms/+source/ceph-osd/+bug/151300921:05
mupBug #1513009: With MAAS 1.9a2, lvm disks are not correctly skipped when in-use by ceph disk prepare. <cloud-install-failure> <landscape> <ceph (Juju Charms Collection):Triaged by xfactor973> <ceph-osd (Juju Charms Collection):Triaged by xfactor973> <https://launchpad.net/bugs/1513009>21:05
cholcombebeisner, yeah the lvm one is a long standing bug that I wasn't able to fix21:05
cholcombeit too stems from is_device_mounted not going deep enough21:06
iceyhttps://bugs.launchpad.net/charms/+source/ceph/+bug/1571840 beisner21:07
mupBug #1571840: Ceph will enter an error state when attempting to add a new encrypted block device <ceph (Juju Charms Collection):New> <https://launchpad.net/bugs/1571840>21:07
iceybeisner: https://bugs.launchpad.net/charms/+bug/157184221:08
mupBug #1571842: ceph-osd error encryption <Juju Charms Collection:New> <https://launchpad.net/bugs/1571842>21:08
* icey EODs21:09
beisnercholcombe, icey - please bring those all to the daily tomorrow am.21:11
=== alexlist` is now known as alexlist
=== scuttlemonkey is now known as scuttle|afk
beisnerjamespage, if you're still around, full pass on pxc @ https://review.openstack.org/#/c/307414/21:36

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