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

axisyson my 16.04 I tried to follow this https://jujucharms.com/get-started and failed miserably00:14
axisys$ juju quickstart mediawiki-single00:14
axisysjuju: command not found00:14
axisysThat's the step 200:14
axisysI already went through step 100:14
axisysany suggestion how to get it working?00:14
admcleod1cory_fu: looks good00:44
lazyPoweraxisys i think thats a typo, it should read juju-quickstart mediawiki-single01:57
lazyPowerhowever the fact its saying juju isn't found isn't promising...01:57
lazyPoweraxisys if you wander back and still need help i'll be around a couple hours longer. feel free to ping and i'll help get you sorted01:59
a123I'm having trouble building juju(cb347bb). Following the instructions in the README.md results in: cannot find package "github.com/Azure/azure-sdk-for-go/Godeps/_workspace/src/github.com/Azure/go-autorest/autorest/mocks"02:01
lazyPowera123 check in #juju-dev, the core hackers that are around should be able to lend a hand02:03
a123thanks lazyPower02:04
=== redir_ is now known as 16WAADNFF
=== 16WAADNFF is now known as redir
=== scuttlemonkey is now known as scuttle|afk
sam_yanTo begin juju,should I use ubuntu-server or ubuntu-desktop?07:45
sam_yanwhen I "juju quickstart mediawiki-single",juju gui is not in my browser08:12
magicaltroutsam_yan: what version of juju are you running for a start?08:12
sam_yan1.25.5-wily08:13
sam_yanneed in ubuntu-server  ? I  use ubuntu-desktop08:13
magicaltroutyou read my DCOS tweet  you aiming to get to that point?08:13
magicaltroutor just general hacking around with Juju?08:14
sam_yanhave not. I am a newer.I read the "install juju and deploy your services in minutes"08:15
magicaltrouthttps://twitter.com/sam_yankun you're not that person who looks like an owl? :P{08:15
sam_yanI am08:15
magicaltroutso https://twitter.com/sam_yankun/status/724927897123852288 was you ;)08:16
magicaltroutanyway! On your main computer you can run either run Desktop or Server08:16
magicaltroutdoesn't matter08:16
magicaltroutI run my main juju controller in the data centre so I run ubuntu server but you can use desktop locally as well08:17
magicaltroutit doesn't matter08:17
magicaltroutalso, if you're starting from scratch, grab a copy of Xenial if you can08:17
sam_yanok . https://jujucharms.com/get-started  I am learning this.08:17
magicaltroutit has Juju 2.0 beta which you're better off getting started with08:17
magicaltroutso my controller runs Ubuntu Server Xenial08:17
sam_yanbut  after "juju quickstart mediawiki-single",there is no response08:18
magicaltroutokay well that should work08:18
magicaltroutrun juju status08:18
magicaltroutdoes it say your stuff is up and running?08:18
magicaltroutif you want a gui, run "juju deploy juju-gui"08:19
sam_yanit says "service unknow"08:19
sam_yanhttps://jujucharms.com/get-started    it says "running this command will open the juju gui in your browser"08:21
magicaltroutjuju status says service unknown?08:22
magicaltroutthat said, it will only open juju gui once it's bootstrapped a new environment, so you need to go through the stuff you see in the terminal in that page first08:23
sam_yani will try08:23
magicaltroutsam_yan: basically, juju should ask you for AWS credentials or something, so it has somewhere to host your units08:23
magicaltroutthen when you fill them in, it should bootstrap a node in the cloud to run the controller, and if it or you deploy juju gui it will bootstrap another node to run juju gui08:24
sam_yanI use vmware,it matters?08:24
magicaltroutdunno08:24
magicaltroutI'm not sure how that quickstart stuff works I've not used it. There is also juju local which will deploy stuff to your computer as opposed to cloud services08:25
magicaltroutif you want to test lcoally08:25
sam_yanwhere?08:25
magicaltroutwhere what?08:25
sam_yanjuju local08:26
magicaltrouthttps://jujucharms.com/docs/1.25/config-local08:27
sam_yanit is for 12.04LTS,I use 15.1008:29
magicaltroutthe docs should be the same I believe08:30
magicaltroutor same-enough08:30
sam_yanok  thank you08:30
sam_yan<magicaltrout>:juju add-unit dcos-agent -n 3  it says "ERROR service "dcos-agent" not found"08:37
magicaltroutsam_yan: dcos hasn't been deployed to the charm store08:38
magicaltroutso it wont deploy08:38
sam_yanhow can I try?08:38
magicaltroutyou need to checkout my 3 github repositories and setup your environment to build charms08:39
magicaltroutexport JUJU_REPOSITORY=$HOME/charms08:39
magicaltroutexport LAYER_PATH=$JUJU_REPOSITORY/layers08:39
magicaltroutexport INTERFACE_PATH=$JUJU_REPOSITORY/interfaces08:39
magicaltroutthat should pretty much do you08:39
magicaltroutthen inside dcos-master and dcos-agent08:39
magicaltroutrun  charm build --series wily08:40
magicaltroutjuju deploy --repository=/home/youruser/charms local:wily/dcos-master08:40
magicaltroutwould then deploy the master for you08:40
magicaltroutand08:40
magicaltroutjuju deploy --repository=/home/youruser/charms local:wily/dcos-agent08:40
magicaltroutwould deploy the agent08:40
sam_yanok .I think the first thing to do is to be familiar with the juju,and to do as you say. thank you magicaltrout   I will do as you tell me08:42
magicaltroutno problem. Its not hard to build, but it helps to have a working environment first ;)08:42
sam_yanyear08:43
bbaqarguys need some help. Lets say the latest availble charm revision is cs:trusty/charm-name-10 .. if i push a revision on top of it .. that revision should be accessible on cs:trusty/charm-name-1109:33
bbaqarright?09:33
bbaqarnot happening for a charm of mine09:33
magicaltroutbbaqar: you using the launchpad ingestion stuff?09:34
magicaltroutie: commit to LP, wait an hour, see if its updated?09:34
bbaqarmagicaltrout: that is exacly what i did .. but its been two days now ..09:35
magicaltroutyeah its broken, and it looks pretty terminal09:35
magicaltrout(speaking from a non canonical emplyee pov :) )09:36
magicaltroutthere were a couple of posts to the mailing list09:36
magicaltroutits recommended you use the new charm publish stuff to get charms into the charm store09:36
magicaltroutalso its instant, you don't have to wait09:36
magicaltrouthttps://insights.ubuntu.com/2016/04/16/charm-charm-tools-2-0/09:36
bbaqarmagicaltrout: okay i ll try that out .. but can i push to any space? like lp:~<team name>/charms/trusty/<charm-name>/trunk09:38
magicaltroutit will login to the charmstore using your LP creds09:39
magicaltroutso I think you end up doing the same thing09:39
magicaltrouti'm not sure though, if you swing back in an hour or 3 marcoceppi will be able to offer much greater insight than me09:39
bbaqarmagicaltrout :thanks alot09:45
magicaltroutno probs09:45
tvansteenburghcan anyone tell me how to get a username/password from the rabbitmq-server charm so i can connect with an amqp:// url?11:56
sam_yanI  use  "juju help local-provider       use on this computer"   and  get "public-address: 10.0.3.205".   But in firfox,it tells "The proxy server is refusing connections"      Why?12:11
ReSammy percona-cluster on xenial fails at creating new databases: INFO shared-db-relation-changed _mysql_exceptions.OperationalError: (1045, "Access denied for user 'root'@'localhost' (using password: YES)")13:31
ReSamany ideas?13:31
gahanHi. I had some issues with date on the server, time went forward, and since then I have logs of errors from 2032 saying "watcher has been stopped". I'm using OpenStack Autopilot and wondered about restarting watcher?13:51
gahanI'm not getting any logs at the moment13:51
gahantail -f /var/log/juju/*.log feeds nothing back, used to be quite crazy13:52
beisnerbdx, howdy.  jewel 10.2 release dates and xenial release dates were out of alignment, but 10.2 is on its way to Yakkety, then Xenial as part of the FFe/SRU @ bug 156371414:32
mupBug #1563714: [FFe][SRU] Ceph Jewel stable release <ceph (Ubuntu):In Progress by james-page> <https://launchpad.net/bugs/1563714>14:32
gahanbootstrapped juju environment stopped responding, juju debug-log hangs14:36
Sharanhi, i was trying to install juju2.0 , if i do "juju status" it is getting hung14:50
beisnerhi tvansteenburgh - aiui, rmq creates users @ amqp-relation-changed --> configure_amqp() --> create_user()  ie. https://github.com/openstack/charm-rabbitmq-server/blob/master/hooks/rabbitmq_server_relations.py#L15215:01
=== redir_ is now known as redir
tvansteenburghbeisner: thanks. it turns out the guest/guest user worked, i was just trying to connect to a vhost that didn't exist :/15:02
beisnertvansteenburgh, yah but that won't work forever, as it's an undesirable security gap, locking down when this gets resurrected:  https://code.launchpad.net/~pjdc/charms/trusty/rabbitmq-server/no-more-guest-user/+merge/27683115:03
beisnerdepending on the rmq version, the guest user either is or is not accessible from remote hosts, so it's kind of bad vs. bad15:04
tvansteenburghbeisner: yah. for my use case right now it's ok15:05
beisnertvansteenburgh, woot.  just wanted to make sure you didn't get used to that unintended feature15:06
axisysso I end up installting juju-2.0 and now I have juju15:09
axisyslazyPower: ^15:09
axisysdoes it work with vmware vcenter or vmware vsphere?15:09
axisysI like to test install a hadoop cluster and we have over 20 sites I can access through vcenter.. so testing with vagrant and it works .. wanted to test with juju15:10
jcastrohttps://jujucharms.com/docs/devel/config-vmware15:11
jcastrohowever that is for juju-115:12
jcastrohmmm, shouldn't vmware be there if I `juju update-clouds` and then `juju list-clouds`?15:12
lazyPowermbruzek https://github.com/juju-solutions/layer-tls/pull/2615:21
axisysjcastro: ah ok.. I see it now15:23
axisysjcastro: ~$ juju-1 generate-config --show | grep -A1 vmware15:23
axisys    vmware:15:23
axisys      type: vsphere15:23
jcastroyeah it's just in 2.0 it should set that up automatically, you shouldn't be mangling the config file by hand15:23
jcastroI know it works in juju-115:24
lazyPowerjcastro - i dont see vmware mentioned in the release notes for beta-515:24
jcastronor me15:24
axisyspicky me.. would be nice if there were a bash completion of the juju arguments .. like git has15:25
jcastroit does have that normally15:25
marcoceppiaxisys: there will be, for juju 2.0, when it's released iirc15:25
jcastroI don't know why it's currently broken, I just noticed that today15:25
marcoceppibcsaller cory_fu I want to use a custom tactic in my layer. how can I?15:28
nottrobinwhy would this charm https://jujucharms.com/u/charmers/block-storage-broker/trusty/2 be at lp:~charmers/trusty/block-storage-broker/trunk but not at lp:charms/trusty/block-storage-broker ?15:29
marcoceppinottrobin: because it's not promulgated15:29
axisyshmm.. juju quickstart fails,  what am I doing wrong? http://dpaste.com/20N9MQN15:29
cory_fuOstensibly, you put the tactic in your layer, and add it to the "tactics" key in layer.yaml.  However, lazyPower ran into an issue with how `charm build` loads the tactics: https://github.com/juju/charm-tools/pull/19115:29
cory_fumarcoceppi: ^15:29
marcoceppiaxisys: what does `juju version` say?15:30
axisysI picked automatically create and bootstrap a local enviroment15:30
axisys2.0-beta4-xenial-amd6415:30
axisysmarcoceppi: ^15:30
marcoceppiaxisys: you don' tneed quickstart for 2.015:30
magicaltroutwhat in gods name is a tactic?!15:30
* magicaltrout cracks out the juju dictionary15:30
cory_fumarcoceppi: Here's the example using the tactic in a layer: https://github.com/juju-solutions/layer-docker/pull/43/files  Note the docstring15:31
marcoceppiaxisys: just bootstrap an enivronment, then juju deploy mediawiki-single15:31
axisysmarcoceppi: I need a get started for 2.0 :-)15:31
axisysmarcoceppi: ok15:31
jcastroaxw: looks like you touched the vmware provider last in march, do you know why it wouldn't be showing as an option in add-clouds or list-clouds?15:31
marcoceppiaxisys: yes https://jujucharms.com/docs/devel/getting-started15:31
marcoceppiaxisys: 2.0 is still technically in development15:32
marcoceppimagicaltrout: tactics are used in charm build to determine how to handle files/merging15:32
axisysjcastro: I decided to come back.. dont have same environmen anymore..15:32
* jcastro nods15:32
marcoceppicory_fu: my django layer had a django.yaml, which I'm converting to layer.yaml, so I'd like to basically have a tactic that, if django.yaml is found it just yells at the user to migrate15:34
cory_fumarcoceppi: Testing that PR on charm-tools would be much appreciated.  But the main thing you need to worry about without it is that your imports at the top of the file containing the tactic likely won't be visible when your tactic is actually invoked.  lazyPower could tell you if there are other issues, and I know he ended up removing the custom tactic in the end, so there might be15:36
lazyPowercory_fu - only until it gets merged into charm-tools15:36
cory_fuHrm15:36
lazyPowercory_fu - that patch that you linked worked. and i commented on teh commit itself as thats what i had to go on15:37
* lazyPower will comment on the bug15:37
marcoceppilazyPower cory_fu thanks for the feedback, I left the merge because I didn't see much feedback/way to test15:37
marcoceppialso, no one checked of the checklist15:38
lazyPowersorry15:38
lazyPowerpreoccupied with a mountain of things to try to land by EOW15:38
marcoceppilazyPower: no worrie15:40
cory_fumarcoceppi: Did you set that checklist up as a template for PRs or something?15:46
marcoceppicory_fu: yes15:46
cory_fuWhere do you set that up?  That's pretty awesome15:46
marcoceppihttps://github.com/juju/charm-tools/tree/master/.github15:47
cory_fuOh, nice15:47
marcoceppicory_fu: I wanted to experiment with the charm-tools repo before pushing it out elsewhere15:47
marcoceppiesp since both charmstore-client and charm-tools are confusing15:47
LiftedKiltis baking the gui into the bootstrap node still planned?16:47
LiftedKiltor did that get abandoned16:47
ReSamLiftedKilt: already done I guess.16:50
ReSam"juju gui" works out-of-the-box with 2.0beta-something16:50
LiftedKiltReSam: oh snap cool16:53
LiftedKiltI must have missed that16:53
LiftedKiltcreating models is still broken from the gui though haha16:55
marcoceppiLiftedKilt: what version of juju?16:58
marcoceppiLiftedKilt: are you using the baked in gui - because that totaly works16:58
LiftedKiltbeta616:58
LiftedKiltusing baked in gui16:58
LiftedKiltopen drop down, type in name of model, click new -> it just closes the drop down but doesn't create anything. It has never worked for me though16:59
LiftedKiltin firefox or chrome16:59
=== rcj` is now known as rcj
=== rcj is now known as Guest12905
=== Guest12905 is now known as rcj
cmarsany of y'all written a charm with resources yet?17:21
cmarslooking for an example to learn from17:22
lazyPowercmars - its not complete, but i've been looking at adding it to layer-tls so easyrsa is not beign pulled in via git17:22
cmarslazyPower, what's a good way to locate the resource file after resource-get from within the charm?17:22
lazyPowerthat i dont know :) i haven't gotten further than declaring it exists17:23
cmarslazyPower, maybe os.path.join(hookenv.charm_dir(), '..', 'resources', resource-name) ?17:23
cmarsok, i'll play with it17:23
lazyPowerthat sounds like a charm-helper waiting to be written17:23
cmarsand share if i get it working17:23
cmarsyeah17:23
lazyPoweror a charms.module17:23
lazyPowercmars - much <3 if you do. I'm eager to see how you solve it17:23
LiftedKiltis there a way to just watch the output of [Units] from juju status?18:11
LiftedKilti've been doing:18:11
LiftedKiltwatch "juju status | sed -n '/\[Units\]/,/\[Machines\]/ p' | head -n -2"18:11
LiftedKiltbut wondering if there's a more elegant way18:11
suchvenuHi18:12
suchvenuI am facing some issue while running amulet test, Can anyone please help me!18:13
suchvenu2016-04-27 17:59:45 DEBUG juju.worker.logger logger.go:45 reconfiguring logging from "<root>=DEBUG" to "<root>=WARNING;unit=DEBUG" 2016-04-27 17:59:46 INFO install /usr/bin/env: python3: No such file or directory 2016-04-27 17:59:46 ERROR juju.worker.uniter.operation runhook.go:107 hook "install" failed: exit status 12718:13
LiftedKiltexit18:13
mgzLiftedKilt: not as such, but I wonder what `juju status "*/*"` displays18:13
LiftedKiltmgz: [Services]: command not found18:14
mgzsuchvenu: you don't have python3 installed but your install script uses it18:14
suchvenuyes i have it18:14
SaltySolomonHi, quick question, how to debug juju charms?18:15
mgzsuchvenu: locally, but not on the machine that's being run? ssh in and poke around18:15
suchvenui have written in my 00-setup file18:16
suchvenu cat << EOF > local.yaml ibm-repo:     db2_curl_url: "$DB2_CURL_URL"     db2_curl_opts: "$DB2_CURL_OPTS"     db2_licese_accepted: "$DB2_LICENSE"     #db2_package_name: "$PACKAGE_NAME" EOF  #is sudo required here ? sudo add-apt-repository ppa:juju/stable -y sudo apt-get update sudo apt-get install amulet python3 -y18:16
mgzSaltySolomon: https://jujucharms.com/docs/stable/authors-intro and so on18:17
mgzsuchvenu: I don't see how that helps18:19
SaltySolomonmgz: I got one of the default packages from the charms store and keystone is not working18:19
mgzSaltySolomon: you can pastebin the yaml status, and the unit log from keystone (get with juju ssh keystone/0) into a mailinglist post or bug on launchpad18:23
mgzsuchvenu: for your install hook to work, you need use a scripting language that's pre-installed on the default image18:26
mgzsuchvenu: old ubuntu series didn't have python3 by default18:26
mgzsuchvenu: so either your charm needs to say it's xenial only, or you need to make the install script bash that installs python 3 then invokes from there18:27
suchvenusorry was away18:27
suchvenuok... I see18:28
suchvenulet me check18:28
suchvenumgz : So i need to specifically install python3 in my install hook, right ?18:31
mgzsuchvenu: depending on the series of you charm, yes. and obviously using any kind of python to do that install hook is therefore a problem (for multi-series charms)18:38
suchvenui am using trusty18:38
suchvenuand i am writing as a layered charm18:38
mgzthen just change "#!/usr/bin/env python3" to "#!/usr/bin/env python" and be done18:39
mgzor... whatever with layered charms, bug one of the maintainers18:39
suchvenuIts getting deployed manually, some env issue with amulet18:43
suchvenui am trying to change python3 to python as you said18:43
mgzmight be something we need marcoceppi for then18:43
suchvenuno, it didn;t help with that18:45
mgzsuchvenu: send a mail to the juju list, I think everyone's at ODS this week18:47
suchvenuok18:47
suchvenuwill do18:47
marcoceppimgz: what's up?19:09
mgzmarcoceppi: suchvenu was having issues writing amulet tests that looked like something was assuming python3 is installed on trusty19:11
tinwoodcory_fu, do you have time for a quick question?  It's about ignoring files in interfaces when they get copied as part of reactive charms.19:39
cory_fuSure19:39
tinwoodSo, 'we' (as in OpenStack charmers) are trying to add tests to interfaces, but they get copied into the final charm and then blow up on install (due to missing python modules). ...19:40
tinwoodcory_fu, so I looked at the code and found an 'ignore' key, but it only seems to work for layers (or just the top level charm).19:41
tinwoodcory_fu, I stared at the code and saw that during the interface copy it uses the target_config of the layer that brings in the interface, but doesn't use any config from the interface.19:42
cory_futinwood: Did you try adding the "ignore" key to interface.yaml?19:42
tinwoodcory_fu, so I was wondering how hard it would be to change it so that we could ignore files from the interface during the copy?19:42
tinwoodcory_fu, yep, it's ignored.  They only seem to work in layers.19:42
cory_fuHrm19:42
tinwoodIt's due to the target_config in plan_interfaces() using the layer rather than the interfaces' yaml.  (I think).19:44
tinwoodcory_fu, (which is probably for a very good reason!) :)19:44
cory_futinwood: I don't know.  It seems like it should honor ignores in the interface.yaml as well.  InterfaceCopy should still have access to those ignores, via self.interface.config.ignores, so I think we might just need to add that list to the target config's list at https://github.com/juju/charm-tools/blob/master/charmtools/build/tactics.py#L15919:47
cory_fubcsaller: Can you chime in whether there's a reason that only the charm layer's ignores are honored?19:47
cory_fuOr if it's just an oversight19:47
tinwoodcory_fu, yes, I wasn't sure where the best place was to add it, nor whether there was an important reason to not do it; it seemed that the framework was there to make it work.19:48
cory_futinwood: I think we should also have an additional set of default ignores for interface layers.  E.g., I don't think every interface layer should have to explicitly exclude tests19:49
tinwoodcory_fu, right. Yes, that makes sense.19:50
lazyPowermbruzek if you have a sec, i could use eyes on this one - https://github.com/juju-solutions/charms.docker/pull/18/files19:50
bcsallercory_fu: most likely an oversight, I can't recall an intent19:51
tinwoodcory_fu, it would be great if 'tests' was added to DEFAULT_IGNORE list as that could create a template for how to add unit tests to an interface or layer.19:51
cory_fuWe don't always want to exclude tests from every layer, though, do we?19:51
tinwoodcory_fu, however, that might be going to far!19:51
cory_fuSeems like it would make sense for interface layers, as they won't get picked up anyway.  But base layers could potentially add amulet tests to the final charm, or something19:52
tinwoodcory_fu, no you're probably right.  I can see the source charm for the build bundling tests for the final built version that can be exercised by the CI as a gate.  So yes, it would be foolish to ignore them by default.19:52
tinwoodcory_fu, bcsaller, how would you like to proceed?  Shall I raise a bug?  I can also (try to) to do a pull request if that helps?19:55
cory_futinwood: Yeah, that would be good.  I'm optitmistic that it'll be a simple change at the line I linked above19:56
magicaltroutthats what they all say....19:57
magicaltrout..... 6 days of hacking later19:57
tinwoodcory_fu, okay, I'll try it and let you know. :)19:57
cory_fulol, too true, magicaltrout19:57
tinwoodmagicaltrout, indeed.  Down the rabbit hole one proceeds ...19:58
natefinchmarcoceppi: juju.fail’s server DNS address could not be found.  :(20:02
marcoceppinatefinch: oops, that'll be addressed in a hot min20:03
natefinchmarcoceppi: forget to pay your registrar again? ;)20:04
marcoceppinatefinch: honestly, so many domains across so many registrars, a few have old credit cards20:04
natefinchmarcoceppi: I hear ya20:04
magicaltroutits like a startup all over again!20:04
natefinchmarcoceppi: I'm lucky I only have domains on two registrars... I'd love to migrate off godaddy, but it's such a hassle.  That's how they get you, I guess.20:05
marcoceppinatefinch: melbourne it, tucows, godaddy, google domains, iwantmyname, ghandi20:06
marcoceppinatefinch: those are the ones I remember20:06
natefinchmarcoceppi: ouch20:06
natefinchmarcoceppi: million dollar idea - service that migrates your domains for you.  Actually... I'm surprised the bigger registrars don't code something up to make it easier.20:07
marcoceppinatefinch: it's pretty straight forward, but it still requires human intervention20:07
marcoceppinatefinch: and yo0u have th pay for another year on xfer20:07
marcoceppithat'd be like me dolling out a few grand to consolidate20:07
magicaltrouta few grand to consolidate sounds like a bargain20:08
* magicaltrout goes to setup such a service20:08
natefinchif letsencrypt can figure out a way to make getting a friggin' cert automatic,  we should be able to figure out how to transfer a stupid domain20:09
marcoceppinatefinch: juju.fail should be back unless you've got dns cache20:12
natefinchmarcoceppi: it seems I do20:16
marcoceppinatefinch: if it's still not owrking, try a different browser20:33
magicaltroutor reset your router :)20:34
tinwoodcory_fu, bcsaller: the good news is that your suggested change of 'self.config.ignores' -> 'self.interface.config.ignores' works to pick up the ignore config option in interfaces.yaml. I'll do a PR.20:34
cory_futinwood: Make sure you also include the existing ignores.  It should be `self.config.ignores + self.interface.config.ignores`20:36
magicaltroutwoooo \o/20:36
cory_fuGlad to hear it was easy, tho20:36
tinwoodcory_fu, they'll be dups then as both lists contain the defaults (I'm guessing).  Shall I list(set()) them to get a unique list?20:37
cory_futinwood: self.config.ignores would contain the "ignores" key from the top (charm) layer's layer.yaml, while self.interfaces.config would contain the "ignores" key from interface.yaml20:38
tinwoodcory_fu, I printed them both and they both contain the DEFAULT_LIST: ...20:39
tinwoodThe ignore list is: ['.bzr/', '.git/', '**/.ropeproject/', '*.pyc', '*~', '.tox/', 'build/']20:39
tinwoodThe self ignores list is: ['.bzr/', '.git/', '**/.ropeproject/', '*.pyc', '*~', '.tox/', 'build/']20:39
* tinwood duh, wrong one:20:39
tinwoodcharmtools.build.tactics: Copying Interface keystone: /home/ubuntu/charms/trusty/designate/build/builds/designate/hooks/relations/keystone20:39
tinwoodThe ignore list is: ['.bzr/', '.git/', '**/.ropeproject/', '*.pyc', '*~', '.tox/', 'build/']20:40
tinwoodThe self ignores list is: ['tests', '.bzr/', '.git/', '**/.ropeproject/', '*.pyc', '*~', '.tox/', 'build/']20:40
cory_futinwood: It shouldn't matter if it has dupes20:45
tinwoodcory_fu, okay, I'll concat the two vars.  Thanks very much for your help!  Typically, how long will this take to land (assuming it's accepted)?20:46
cory_fumarcoceppi: ^20:47
marcoceppicory_fu: IM CONFUSED20:50
marcoceppiim also caps locked20:50
cmarsis there a way to skip installing g++ in the basic layer? a configuration option, perhaps?20:59
cory_fumarcoceppi: If a PR is accepted on charm-tools, how long until it will be available (somehow, e.g., ppa)?  Or are we still too new to the release process?20:59
cmarsmost of my charms don't need it and some ops folks are hesitant to deploy compilers into a production env20:59
marcoceppicory_fu: I'm working on getting an MRE, which means we can turn around a micro release (patch) in a copule of days21:00
cmarsas for me, i think it just slows down the install hook21:00
marcoceppicmars: it's typically installed for python-dev21:00
=== natefinch is now known as natefinch-afk
cmarsmarcoceppi, can i not install python-dev?21:00
marcoceppicmars: maybe? but not atm21:01
cmarsok21:01
marcoceppicory_fu: ^?21:01
tinwoodcory_fu, marcoceppi thanks for the info.  we'll work around the problem with a post build script until the patch (I've not yet submitted!) lands.21:34
tinwoodgnuoy, ^^^ - found issue, have solution,  but need to keep the delete workaround until it lands (... this is for tests appearing in the built charm).21:34
cory_fuaisrael: I'm seeing some strange behavior when trying to use the watch-files options of rsyslog-forwarder-ha in a bundle.  If I don't tag the revision explicitly, I get an error saying the option is invalid, but if I explicitly give it -8, it works.  Any idea why?21:41
cory_fuaisrael: Did you by chance use `charm publish` for rev 8?21:41
axwjcastro: IIRC you have to set a feature flag for vsphere to show up22:02
jcastroaxw: yeah alexis had me file a bug on that, thanks22:04
axwnp22:05
aisraelcory_fu: I don't think that's one I used charm publish for. The first one I used that on was auditd23:03
cory_fuVery strange23:05

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