/srv/irclogs.ubuntu.com/2015/12/07/#juju.txt

gnuoyjamespage, coreycb, fyi https://github.com/juju/charm-tools/issues/6909:23
jamespagegnuoy, urgh09:53
gnuoyjamespage, https://code.launchpad.net/~gnuoy/charms/+source/interface-rabbitmq/+git/interface-rabbitmq/+merge/279743 does that address your concerns?09:56
jamespagegnuoy, yes09:58
jamespagegnuoy, newer odl versions appear to have a way to determine whether they are up or not10:50
jamespagehttps://github.com/openstack/networking-odl/blob/master/devstack/odl-releases/lithium-snapshot-0.3.2#L2810:51
gnuoy\o/10:51
gnuoyChristmas has come early10:51
gnuoyjamespage, why wouldn't I put every possible key the service I'm joining with could throw back at me in auto_accessors ?12:44
gnuoy"you would" being the reply I'm hoping for12:44
jamespageprobably12:47
jamespagegnuoy, I'd put auto_accessors in for any key that will be eventually consistent across all remote units12:47
gnuoyjamespage, so we should remove 'private-address' then I guess12:48
jamespagegnuoy, yeah I guess so12:51
jamespagegnuoy, and pick on from the list of hosts for 'host' in the adapter12:51
=== kwmonroe_ is now known as kwmonroe
gnuoyjamespage, got a sec for https://code.launchpad.net/~gnuoy/charms/trusty/openvswitch-odl/duplicate-controllers/+merge/279251 ?15:24
jamespagegnuoy, I'll peek in a bit15:29
lazypoweraisrael marcoceppi tvansteenburgh - http://paste.ubuntu.com/13792602/ i appear to have whiffed on making my module extension. Can I bother one of you for help debugging this?16:39
aisraellazypower: the magic is in charms/__init__.py16:40
lazypoweraisrael https://github.com/juju-solutions/charms.docker/blob/master/charms/__init__.py16:40
aisraeland then your code in charms/docker/* will be properly namespaced16:40
aisraelThat's a bit odd, then. cory_fu might be better suited to help with this. He came up with the original pattern (I think)16:42
lazypoweraisrael: i'm not entirely convinced, that I have some hinky package setup in this module16:42
lazypowerfair, ta16:42
marcoceppilazypower: link to your setup.py?16:42
lazypowermarcoceppi https://github.com/juju-solutions/charms.docker/blob/master/setup.py16:43
marcoceppilazypower: you're missing a packages declaration16:43
lazypowerAh!16:44
lazypowerthanks :)16:44
lazypowermarcoceppi: I need to declare both 'charms' and 'charms.docker' corect?16:50
marcoceppilazypower: im not sure. it seems wrong, tbh16:50
lazypowerDeclaring both packages in the setup.yaml?16:51
lazypowerer .py16:51
marcoceppilazypower: yes, seems wrong to me16:51
marcoceppidoes it work with just charms.docker as the package?16:52
lazypoweryep16:52
lazypoweri just veriified in a venv16:52
marcoceppiyou found your answer :)16:52
mbruzeklazypower: and marcoceppi is this package declaration a pip thing, or a pypi thing?16:57
lazypowerPip thing16:57
marcoceppiIt's a python thing.16:57
lazypower^ that16:57
mattywso In my charm's amulet test I do self.d.add("mycharm")17:17
mattywshouldn't that work out what charm it's in and use that?17:17
mattywbecause I'm getting charmworldlib.charm.CharmNotFound: API request failed: Request failed with: 40417:18
mattywalso - if it's using layers, do I have to build the charm first?17:18
marcoceppimattyw: yes you have to build the charm first, for now (?) we've not thought that far17:19
marcoceppimattyw: we'd need a full traceback and the version of amulet you're using17:19
mattywmarcoceppi, ok, but there'll be spoilers17:20
marcoceppimattyw: spoilers?17:20
mattywmarcoceppi, http://paste.ubuntu.com/13793744/17:21
mattywmarcoceppi, you'll know what charm I'm working on ;)17:21
marcoceppiWELL NOW THIS LOOKS FAMILAR :)17:21
mattywlol17:22
mattywmarcoceppi, 1.12.117:22
marcoceppimattyw: don't use the charm= commmand17:22
marcoceppimattyw: just d.add('minecraft')17:22
marcoceppicharm= overrides the autodetection behaviour, since you've explicitly given it a charm to use17:22
mattywmarcoceppi, nope, I get the same thing17:23
marcoceppimattyw: bleh17:23
mattywsorry :(17:23
marcoceppimattyw: Ah17:24
marcoceppihave you tried tests/01-listening17:24
marcoceppiinstead of doing it from within the tests directory17:24
mattywthat works17:24
mattywbut unit: minecraft/0: machine: 1 agent-state: error details: hook failed: "leader-settings-changed"17:24
mattywis that the charm-tools bug?17:25
mattywactually17:25
mattywignore me17:25
mattywactually yeah, that does seems like the problem I see now17:25
lazypowercory_fu: ping for when you have a moment17:26
marcoceppimattyw: yeah, so amulet assumes the tests is executed from CHARM_DIR, since that's a requirement of all test runners17:28
marcoceppimattyw: what's the error for that say?17:28
mattywmarcoceppi, nah - might be me actually17:30
bloodearnestmarcoceppi, hey there. My code in reactive/foo.py cannot import code from reactive/bar.py, due I think it not being a normal import, rather using manual load_source17:38
bloodearnestmarcoceppi, if I have some library code for my charm's reactive hooks, where should that live in the charm?17:39
bloodearnestfwiw, the code foo can import bar perfectly fine when running unit tests17:39
marcoceppibloodearnest: what are you trying to import?17:44
bloodearnestmarcoceppi, my own code, just in a different file in the charm17:45
cory_fulazypower: Ok, just finished.  What's up?  Hangout?17:45
bloodearnestI can stick it all in the same file, but it would be nicer separate17:45
lazypowercory_fu: sure, point the direction17:45
cory_fulazypower: https://plus.google.com/hangouts/_/canonical.com/big-data-sync17:46
marcoceppibloodearnest: well, we've adopted a convention of putting code you want shared between layers in lib/<module>.py17:46
marcoceppieg, the nginx layer produces a lib/nginxlib.py, django has a lib/charms/django.py, etc17:46
marcoceppilib is in the import path for charms, so it works around the entry_point issue17:47
bloodearnestmarcoceppi, right, sounds like that's what I want. My code is not really for sharing between layers, more for organisation with a layers (and testing usage)17:48
mbruzekcory_fu: Getting an error with the wheelhouse, http://paste.ubuntu.com/13794767/18:00
cory_fumbruzek: File "/var/lib/juju/agents/unit-k8s-0/charm/reactive/k8s.py", line 4418:00
cory_fudef leader-settings-changed():18:00
cory_fuCan't use dashes in function names18:00
mbruzekI fixed that in the code, and re-installed18:01
cory_fumbruzek: Also, the error at the bottom indicates that your wheelhouse still contains actual wheels.  Are you on the newest charm-tools?18:01
mbruzekcory_fu: possibly not18:02
cory_fumarcoceppi: When will the point release of charm-tools be available?18:02
lazypowermbruzek: which version of charm-tools are you using?18:02
mbruzekcharm-tools 1.10.018:07
cory_fumbruzek: You might need to rebuild your charm from the layer from scratch, or manually remove wheelhouse/*.whl18:11
marcoceppicory_fu: whenever you want me to cut it18:12
marcoceppiI was going to wait until 3pm EST but can move to get it out before 2PM18:12
cory_fuI think we should probably get it out, since charms being built now are broken because of the newline.18:13
marcoceppicory_fu: ack, will cut asap18:28
cory_fumarcoceppi: You're the best.  :)18:29
mattywmarcoceppi, has there been a new release of charmhelpers over the past couple of days? install_remote keeps failing for me with TypeError: must be str, not bytes18:41
mattywwasn't doing that last week18:41
jrwrenmattyw: sounds like its python3 now when it was python2 before?18:44
mattywjrwren, could be - but the charm was working on friday18:45
mattywjrwren, and today it isn't18:45
jrwrenmattyw: oh, same charm. nevermind.18:45
=== scuttle` is now known as scuttle|afk
lazypowermattyw: charm-tools revved to 1.10.0 on Friday evening19:12
lazypowermattyw: and the base layer was updated in sync w/ that charm tools rel, the hooks are now python3 by default19:12
mattywlazypower, makes sense19:16
mattywlazypower, might be a problem with install_remote then19:16
mattywlazypower, I'm cheating for now19:16
mbruzekjcastro: Is the tag named "adoption" no other hyphens or prefix ?19:26
mbruzekjcastro: https://bugs.launchpad.net/juju-core/+bug/149597819:27
mupBug #1495978: Juju does not deploy CentOS images in LXC <adoption> <centos> <containers> <juju> <lxc> <system> <juju-core:Triaged> <https://launchpad.net/bugs/1495978>19:27
jcastrombruzek: yeah19:42
mbruzekjcastro: thanks19:42
jcastroarosales: I need some graph help if you have a minute19:42
arosalesjcastro: yo, for sure19:44
jcastrohttps://plus.google.com/hangouts/_/canonical.com/eco-wx?authuser=119:44
jcastroarosales: ^^^19:44
mbruzeklazypower: cory_fu found an empty sections on the proposed docs. http://52.0.202.26:8000/en/developer-layers.html  Should "Layer Encapsulation" have a paragraph describing that?20:11
lazypowerah yeah, i didnt know what to put there20:11
lazypoweri forgot to remove the section title/link20:11
cory_fumbruzek: Which branch should I be using?  developer-guide or mbruzek-developer-guide?20:13
mbruzekdeveloper-guide20:13
lazypowerActually20:15
lazypoweri dont see encapsulation in the navigation.tpl20:15
lazypower:-/20:15
cory_fumbruzek: https://github.com/mbruzek/docs/pull/4020:16
cory_fuHopefully that's on the righ tbranch now20:16
krondorwhat's the story with charmhelpers.fetch.giturl?  Was working earlier in the week, and now fails GitPython does not support Python 3.20:19
krondorahh nevermind I see mattyw seeing similar issues with python 2 to 3 switch.  Any chance we'll see fetch git working again or should I work around?20:21
cory_fukrondor: It looks like that assertion is no longer true and GitPython should work fine on Python 320:27
cory_fuIn fact, according to https://github.com/gitpython-developers/gitdb/issues/4 it's been supported for 2 years20:29
cory_fuSorry, 1 year20:29
krondorcory_fu:  That's the error that fetch threw, but I see now there is an new charm tools as of this afternoon for me.  I'll update again and see if anything has changed.20:30
marcoceppicory_fu gnuoy cmars axw_: charm-tools 1.10.1 is out20:31
cmarsmarcoceppi, thanks!20:31
marcoceppiThanks for the report!20:31
cory_fukrondor: It won't have: https://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/fetch/giturl.py#L2520:31
cory_fumarcoceppi: Thanks!20:31
=== scuttle|afk is now known as scuttlemonkey
cory_fukrondor (and also marcoceppi): https://code.launchpad.net/~johnsca/charm-helpers/python3/+merge/27981720:51
krondorcory_fu:  Thank you, I'll test20:53
krondorcory_fu:  I think it's going to be more involved than that.  giturl tries to apt install python-git which depends on 2.7.  from git import Repo fails with No Module Named 'git'21:18
cory_fuAh.  Shoot21:22
cory_fuAnd there isn't a python3-git packages21:22
cory_fu*package21:22
krondorcory_fu, right kind of a bind21:23
bcsalleriirc our deps on git stuff are very thin and could be handled with subprocess, we don't really inspect the data very much21:48
cory_fuTrue.  I was just hoping it would be a trivial change.  But I guess not21:53
=== scuttlemonkey is now known as scuttle|afk
krondorbscaller: yeah I'm going back to subprocess at least for the interim21:56
marcoceppi+1 on subprocess, the sooner we can drop bzrlib the closer we get to Python3 support21:57
=== scuttle|afk is now known as scuttlemonkey
jrwrencharmers: kindly requeue http://review.juju.solutions/review/2357 please.22:35
jcastrokrondor: I ran into a snag in magento so you might end up beating me on this22:47
TheJeffgood day charmers!22:52
TheJeffrun into an issue deploying things, hopeing you can clarify22:52
TheJeffack in just a few minutes because fire.22:54
TheJeffalright I'm back -- so I'm following this here guide:23:00
TheJeffhttps://help.ubuntu.com/lts/clouddocs/en/Installing-OpenStack.html23:00
TheJeffI'm at the point where I source novarc23:00
TheJeff# nova endpoints <-- execute this, got Invalid Openstack Nova credentials23:01
TheJeffnow, I'm sure I need to change the novarc file - it's mostly autopoulated23:01
TheJefffrom that script23:01
TheJeffassume its the OS_password variable23:01
mgzTheJeff: if you add --debug you can see the actualy request json you send to keystone23:02
TheJeffwhere would one obtain said password?  Is it the one I set in the keystone portion of the openstack-config?  Otherwise its all default afaik, and it's still not working23:02
mgzpassword is what is set up for that user in keystone23:02
TheJeffseems that throws the same error though23:03
TheJeffassuming its what i set as admin-password: in my yaml when I spun it up23:04
mgznope23:04
mgzhm, I can't remember all the details here,23:05
TheJeffand nova endpoints --debug throws an error that --debug isnt a valid flag23:05
TheJeffcan I reset this somehow?23:06
TheJeffI'm less concerned with where it went sideways than setting it right side up23:06
mgzit's `nova --debug endpoints`23:07
TheJeffCould not find user, admin.", "code": 401, "title": "Unauthorized"23:07
TheJeffis this perhaps my maas user?23:08
mgzTheJeff: see https://bugs.launchpad.net/charms/+source/keystone/+bug/143590623:08
mupBug #1435906: provide stable mechanism to retrieve admin credentials <keystone (Juju Charms Collection):Triaged> <https://launchpad.net/bugs/1435906>23:09
mgzlook in that file for the real password, /var/lib/keystone/keystone.passwd23:09
mgzand yeah, looks like you have the user name wrong too?23:09
mgzthat's `admin-user` in the charm config23:09
TheJeffmgz: admin-user huh23:11
TheJeffthat's not anywhere in this yaml23:11
TheJeffnor this doc :(23:12
TheJeffand this workaround you linked states 'use juju-set' -- but that's not a command I've got23:12
mgzthe default should be 'admin'''23:13
mgzTheJeff: it's `juju set`23:13
mgzsee the help for that, takes a service and config key/value pair23:13
TheJeffaha23:14
TheJeffso is it OS_PASSWORD I'm setting?23:15
TheJeffas is in the nova.rc23:15
TheJeffis that the key?  can I list keys?23:15
TheJeffjuju list|grep user && juju set {} <password>23:16
TheJeff^some way of this???23:16
marcoceppiTheJeff: hey23:26
* marcoceppi reads scroll23:27
marcoceppiTheJeff: did you run the script here? https://help.ubuntu.com/lts/clouddocs/en/Installing-OpenStack.html#configuring-access-to-openstack23:30
TheJeffmarcoceppi: yep23:43
TheJeffthat populated nova.rc fine23:43
marcoceppiTheJeff: does the .novarc file look right?23:43
marcoceppicool23:43
TheJeffbut it says invalid creds23:44
TheJeffactually just sat back down nothing has changed since my last message above^23:44
marcoceppistill trying to read through the backlog23:44
adam_gTheJeff, the keystone charm generates admin password for you, unless one is configured. try: juju set keystone admin-password=foo23:44
adam_glet it run its config-changed hook and that should now be the admin password23:44
TheJeffooo23:44
TheJeffok23:44
adam_gupdate OS_PASSWORD in your envirnment accordingly23:44
TheJeffok ok wait so i actually just ran that shell script again23:46
TheJeffand it punched back keystone admin token23:46
TheJeffis that it?23:46
TheJeffyeah ok so thats a neat thing23:49
TheJeffI ran juju set admin-user=admin23:49
TheJeffwarning: already set23:49
TheJeffran juju set admin-password=<password>23:49
TheJeffwarning already set (and matches23:49
TheJeffsource nova.rc23:49
TheJeffnova endpoints23:49
TheJeffinvalid nova credentials :(23:49
TheJeffoh.  there's all kinds of bad looking stuff in my juju status23:51
TheJeffkeystone:      message: 'Missing relations: database'23:51
TheJeffrabbit saying           message: 'hook failed: "shared-db-relation-changed" for mysql:shared-db'23:51
TheJeffswift saying23:51
TheJeff      message: Not enough related storage nodes23:51
TheJeffugh23:52
TheJeffrelated?23:52
TheJeffyeah keystone saying           message: 'hook failed: "shared-db-relation-changed" for mysql:shared-db'23:54
TheJeffalright, I'm starting over.23:57
TheJeffis there a doc that's up to date?  The one I'm following (canonical) mentions deploying quantum-gateway, which juju states is end of life, and deploying openstack-dashboard for example complains there's no config23:59

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