[08:41] <jamespage> tinwood, gnuoy: good morning
[08:41] <tinwood> good morning :)
[08:41] <gnuoy> o/
[08:47] <jamespage> tinwood, mmmm
[08:47] <jamespage> looking at your port up change
[08:47] <tinwood> jamespage, yup ?
[08:47] <freak__>  
[08:47] <freak__> hi guys
[08:48] <freak__> is anybody available rightnow who can help me out
[08:48] <jamespage> tinwood, yeah - your fix is great for a normal port
[08:48] <freak__>  i'm deploying openstack base bundle
[08:48] <jamespage> but for a dpdk port, the ip link commands will fail...
[08:48] <tinwood> jamespage, but broken for other things?
[08:48] <freak__> through command juju quickstart openstack-base
[08:48] <freak__>  but i'm facing issue http://paste.ubuntu.com/15845425/
[08:48] <tinwood> jamespage, oh
[08:48] <jamespage> tinwood, yah - a smaller fix for now would be to specialize that function for dpdk codepath and use th charmhelpers version for non-dpdk
[08:49] <tinwood> jamespage, ya, I understand.  On it.
[08:49] <jamespage> freak__, yeah - your lxc containers look unhappy
[08:49] <tinwood> jamespage, any reading material on dpdk?
[08:50] <jamespage> freak__, "failed to retrieve the template to clone"
[08:50] <jamespage> tinwood, erm
[08:50] <freak__> thats what i want to know why containers not initializing
[08:50] <jamespage> tinwood, look at line 360 of that same file
[08:50] <jamespage> that's the bit that does the dpdk port adds...
[08:50] <tinwood> jamespage, kk thanks.
[08:51] <jamespage> freak__, I'd drop onto one of the physical hosts and take a look in /var/log/juju/machine-*.log
[08:51] <jamespage> might give you a bit more of a clue
[08:51] <freak__> ok.let me check
[08:51] <jamespage> the error is coming from lxc - so it might be some sort of firewall egress issue? is the environment your are deploying in network limited in any way?
[08:52] <freak__> WARNING juju.apiserver.client status.go:679 error fetching public address: public no address
[08:54] <freak__> my lab subnet is different and i'm doing NATing on my router to go to outside world
[08:54] <jamespage> bbaqar, around?
[08:56] <jamespage> freak__, hmm that should be ok
[08:56] <jamespage> freak__, that public address message is probably ignorable as well
[08:58] <freak__> jamespage how can i check whether my cluster controller is performing dhcp and dns correctly or not
[08:58] <freak__> any command to check status of these services
[08:59] <jamespage> freak__, I'd drop onto one of the deployed machines and check dns is all good that way (dig or suchlike)
[08:59] <freak__> ok
[09:00] <freak__> jamespage check this http://paste.ubuntu.com/15845529/
[09:00] <freak__> i think its working fine as far as dns is concerned
[09:00] <jamespage> freak__, yeah - that looks fine
[09:01] <jamespage> hmm
[09:02] <jamespage> freak__, could you pastebin the output of sudo lxc-ls -f
[09:02] <freak__> ok
[09:03] <freak__> http://paste.ubuntu.com/15845565/
[09:13] <freak__> jamespage http://paste.ubuntu.com/15845565/
[09:14] <jamespage> freak__, yeah got it thanks
[09:19] <jamespage> freak__, we need to get a bit more debug output
[09:19] <freak__> ok
[09:19] <jamespage> freak__, the juju controller/bootstrap node caches the images for lxc - I just did a quick test with 1.25.5 locally and it worked OK
[09:20] <jamespage> freak__, ok I think we can do this without re-bootstrapping
[09:20] <freak__> i think that the issue with lxc service start
[09:20] <jamespage> freak__, can you do
[09:21] <jamespage> juju set-env logging-config="<root>=DEBUG;unit=DEBUG"
[09:21] <jamespage> that will up the debug level across the environment
[09:21] <jamespage> freak__, and then ssh to one of the nodes and delete the lxc container
[09:22] <jamespage> freak__,
[09:22] <jamespage> sudo lxc-destroy --name juju-trusty-lxc-template
[09:22] <jamespage> and then have another go add adding a lxc container to that machine
[09:23] <jamespage> freak__, juju add-machine lxc:X (where X is the machine id of the server you just deleted the template from)
[09:23] <freak__> ok..right now there is some power issue .they are doing maintenance .so nodes are off..i can perform these steps after 40mins..
[09:23] <jamespage> freak__, okies
[09:23] <jamespage> lemme know how that goes
[09:23] <freak__> ok i will definitely inform you after performing these steps
[09:23] <jamespage> specifically looking for messages from machine-X.log around problems with lxc and specific error messages
[09:24] <freak__> jamespage ok. i will
[09:25] <jamespage> gnuoy, gerrit is foobar by the way - apparently no new jobs are being processed...
[09:26] <gnuoy> oh
[09:38] <jamespage> gnuoy, infra team are working on it
[09:38] <gnuoy> kk
[10:08] <jamespage> bbaqar, when you do appear - could you confirm what testing the updates for the plumgrid charms have had; I don't intened to exercise them myself so dependent on your test results :-)
[10:09] <jamespage> bbaqar, you also asked me about migration of the plumgrid charms under the openstack project for development
[10:10] <freak__> jamespage i executed the commands as you mentioned
[10:11] <freak__> upon running  juju add-machine lxc:0 it showed msg created container 0/lxc/3
[10:11] <freak__> but in juju status
[10:12] <freak__> http://paste.ubuntu.com/15846755/
[10:13] <jamespage> bbaqar, https://review.openstack.org/#/c/232705/ is the change we made to push the core charms under the openstack project
[10:13] <freak__> jamespage here are machine 0 logs http://paste.ubuntu.com/15846774/
[10:14] <jamespage> bbaqar, I'd suggest that you follow the same route - I suspect that you will want the group for core-reviewers to be a little different tho
[10:15] <jamespage> freak__, need a bit more log I think
[10:15] <freak__> ok
[10:15] <freak__> which one.tell me the command i will share
[10:21] <jamespage> freak__, the machine-0 log
[10:21] <freak__> ok i will take the complete log and share
[10:25] <freak__> jamespage any website like paste.ubuntu where i can share the file of log i have taken using securecrt
[10:26] <freak__> coz the file is too long and paste.ubuntu got hung
[10:26] <jamespage> freak__, a grep for 'container' might be helpful to filter things out
[10:28] <freak__> u mean cat /var/log/juju/machine0.log | grep container
[10:29] <freak__> jamespage here is the output http://paste.ubuntu.com/15847017/
[10:33] <jamespage> freak__, ok
[10:34] <jamespage> freak__, apparently Invalid argument - setting cmdline failed is a warning only
[10:34] <jamespage> freak__, lets try starting that container
[10:34] <freak__> how to start
[10:35] <jamespage> freak__, lxc-start --name juju-trusty-lxc-template
[10:35] <freak__> ok
[10:35] <jamespage> sudo lxc-start --name juju-trusty-lxc-template
[10:35] <jamespage> that will happen in the foreground - hopefully that might give us a clue
[10:36] <freak__> jamespage here is the issue http://paste.ubuntu.com/15847100/
[10:37] <jamespage> freak__, yeah still not much info
[10:38] <jamespage> freak__, try again with "-l DEBUG"
[10:38] <jamespage> that might give us more
[10:38] <sparkiegeek> and -F for foreground starting?
[10:38] <jamespage> all I can think is the cached image in juju is foobar
[10:39] <jamespage> sparkiegeek, I thought that was the default but I might be wrong
[10:39] <jamespage> freak__, add "-F" as well to be sure...
[10:39] <sparkiegeek> jamespage: nah, default is daemon
[10:39] <jamespage> sparkiegeek, oh
[10:40] <freak__> jamespage check this http://paste.ubuntu.com/15847157/
[10:40] <bbaqar> jamespage: Thanks for the help. Bundles in all the charms tests deploy smoothly.
[10:40] <jamespage> freak__, needs to be -F not -f
[10:40] <freak__> ok
[10:41] <jamespage> freak__, and DEBUG not debug apparently...
[10:41] <bbaqar> jamespage: have not ran the amulet test though in the last two weeks .. but they run the same bundle that i deploy every day
[10:41] <jamespage> bbaqar, ok
[10:41] <bbaqar> jamespage: and test for the same things i test every day
[10:41] <jamespage> bbaqar, do you have a bundle in the charm-store for plumgrid?
[10:42] <jamespage> gnuoy, https://review.openstack.org/#/c/304668/ could you review please
[10:42] <jamespage> finally passing amulet tests...
[10:42] <freak__> http://paste.ubuntu.com/15847193/
[10:42] <bbaqar> jamespage: yes we do .. but it has to be updated as soon as we land the charm MPs https://jujucharms.com/plumgrid-ons/bundle/9
[10:43] <jamespage> bbaqar, yah - I see some of the config options are changing names - that will break upgraders but I suspect your install base is know right now :-)
[10:43] <gnuoy> jamespage, will do
[10:44] <freak__> jamespage while bootstrapping there is the option disable juju network management i checked this option do you think this bridge issue is appearing to that
[10:44] <jamespage> freak__, right - that's usefull
[10:44] <jamespage> freak__, hmmm
[10:44] <jamespage> freak__, and you do 'ip addr' on that unit please
[10:44] <jamespage> freak__, yes I suspect that is breaking things badly...
[10:44] <bbaqar> jamespage: no one is on those revision .. so we are good
[10:45] <jamespage> bbaqar, okay - next on my list
[10:45] <freak__> so do you suggest to bootstrap again and enable that option
[10:45] <jamespage> freak__, yes
[10:45] <freak__> i think that will work
[10:45] <freak__> ok i will try and then get back to you
[10:46] <jamespage> freak__, could you raise a bug against juju for this as well - it really should tell you that you can't have lxc containers if that option is enabled
[10:46] <jamespage> https://bugs.launchpad.net/juju-core/+filebug
[10:46] <jamespage> that would have saved us 2 hours of debug...
[10:46] <freak__> ok i will
[10:47] <jamespage> freak__, thankyou :-)
[10:47] <jamespage> ping me the link once raised and I'll mark it as effects me tooo...
[10:48] <freak__> thanks to you as well for strong support..ok i will share link here with you
[10:49] <bbaqar> jamespage: appreciate the help.
[10:50] <jamespage> freak__, no problem - just as a heads up we're a week off  the next charm release that will support 16.04 and the openstack mitaka release
[10:50] <jamespage> freak__, so if you're planning ahead something to think about
[10:50] <jamespage> freak__, you can upgrade liberty->mitaka but not in-place 14.04 -> 16.04
[10:50] <jamespage> using the charms that is
[10:56] <jamespage> bbaqar, for migration under the openstack project, you'll want to add tox configurations for all of your charms...
[10:56] <jamespage> bbaqar, look at any of the core charms for hints on that
[10:57] <jamespage> bbaqar, any general summary for the commit messages on these?
[10:57] <jamespage> bbaqar, and remind me to talk to you about direct charm store publishing soon....
[10:57] <bbaqar> #let me add a commit message right now.
[10:58] <bbaqar> jamespage: I ll add a commit message right now
[10:58] <freak__> jamespage here is the bug link https://bugs.launchpad.net/juju-core/+bug/1570796
[10:58] <mup> Bug #1570796: container startup issue when juju network management disabled <juju-core:New> <https://launchpad.net/bugs/1570796>
[10:58] <jamespage> bbaqar, ta
[10:58] <jamespage> bbaqar, here is fine - vim is open waiting for me to type...
[10:58] <bbaqar> jamespage: just one mine
[10:59] <jamespage> gnuoy, nearly have odl-controller passing on xenial
[10:59] <jamespage> soooo close
[11:00] <bbaqar> jamespage
[11:01] <bbaqar> jamespage: support added for plumgrid 4.1.3 and 5.0 releases | support added for configurable external interfaces | support added for separate fabric network (os-data-network)
[11:01] <bbaqar> jamespage . use this for plumgrid-director, plumgrid-edge, plumgrid-gateway
[11:01] <gnuoy> jamespage, excellent
[11:02] <bbaqar> jamespage: for neutron-api-plumgrid: support added for plumgrid 4.1.3 and 5.0 releases
[11:05] <jamespage> bbaqar, as a future improvement, you might have external-interfaces be a list of mac addresses to use across the deployment
[11:05] <jamespage> bbaqar, there is code in charm-helpers to resolve mac -> interface
[11:09] <bbaqar> jamespage: haha ... i wish i had known this earlier ..
[11:09] <jamespage> bbaqar, I suspect some of the challenges we have across SDN solutions are common
[11:10] <bbaqar> jamespage: i have seen the function actually .. might be difficult for the users to collect all mac-addresses for each interface on scale deployments
[11:10] <jamespage> bbaqar, well maas has them all :-)
[11:11] <jamespage> bbaqar, as a future feature, juju may grow support for presenting the interface directly via network spaces
[11:12] <bbaqar> jamespage: You are right. and yes i saw some development on spaces .. will rethink this before pushing xenial charms
[11:12] <jamespage> bbaqar, sure
[11:12] <jamespage> it might be good to schedule a general MAAS 2.0/juju 2.0 update for your team
[11:13] <jamespage> there will be alot of docs being updated - prob best to wait for that
[11:13] <jamespage> bbaqar, ok all landed...
[11:14] <jamespage> lazyPower, ^^
[11:14] <jamespage> fyi
[11:17] <jamespage> gnuoy, "Controller configuration on bridge br-int incorrect: ![u'tcp:172.17.115.171:6653']! != !tcp:172.17.115.171:6633!"
[11:17] <bbaqar> jamespage: thanks alot.
[11:22] <bbaqar> jamespage: For the commit into openstack project. What upstream location should we use? I see all openstack charms are in https://github.com/openstack-charmers/ ... should i keep them in our plumgrid github space?
[11:41] <jamespage> bbaqar, that was just a staging area
[11:42] <jamespage> any git location for the source of the charms is fine
[12:06] <bbaqar> jamespage:got it
[12:38] <freak__> jamespage are you there?
[12:40] <freak__> jamespage i bootstrapped the environment again and enabled the option juju network management ..this time the lxc issue resolved
[12:40] <freak__> this is the current status some components are struck http://paste.ubuntu.com/15848673/
[12:42] <jamespage> freak__, looks like lxc containers might be still coming up
[12:42] <freak__> ok. i will wait
[12:46] <jamespage> freak__, whats the disk io like on your servers?
[12:53] <jamespage> tinwood, your proposed fix for n-ovs looks good to me - is that testing ok in the dvr spec for you?
[12:53] <tinwood> jamespage, I'm just getting it sorted now - let you know when it's done xenial/mitaka?
[12:54] <jamespage> tinwood, okies
[12:54] <freak__> jamespage its /dev/sda
[12:54] <jamespage> tinwood, cause I know the amulet tests won't exercise that stuff at-all
[12:54] <tinwood> jamespage, indeed.
[12:54] <freak__> jamespage  here is the detail http://paste.ubuntu.com/15848759/
[12:55]  * lazyPower read backscroll
[12:56] <lazyPower> jamespage niiiiceee!
[12:57] <webscholar> ..
[12:57] <lazyPower> jamespage - we threw down some docs about that as well https://jujucharms.com/docs/devel/authors-charm-store
[12:57] <lazyPower> re: publishing
[13:02] <jamespage> lazyPower, awesome
[13:05] <freak__> jamespage still the status is same ...lxc are in allocating state
[13:22] <freak__> jamespage here is the current status http://paste.ubuntu.com/15849141/
[13:22] <freak__> is it normal to take so much time allocating?
[13:22] <jamespage> freak__, not quite sure whats happening tbh
[13:23] <jamespage> freak__, no - i suspect something else
[13:23] <jamespage> freak__, can you check the status of the lxc containers on the machines?
[13:23] <jamespage> sudo lxs-ls
[13:23] <jamespage> sudo lxs-ls -f actuall is better
[13:23] <freak__> ok
[13:24] <freak__> jamespage   http://paste.ubuntu.com/15849161/
[13:25] <jamespage> freak__, sudo !!
[13:25] <jamespage> needs root
[13:26] <freak__> ohh...right   http://paste.ubuntu.com/15849174/
[13:27] <jamespage> freak__, thats a good start
[13:28] <freak__> yes that alright... but have you noticed template at the end is stopped
[13:31] <freak__> jamespage what you think could be the issue in allocation of lxc
[13:32] <jamespage> freak__, yeah - the template being stopped is fine
[13:36] <freak__> my current status
[13:36] <freak__> http://paste.ubuntu.com/15849258/
[13:40] <freak__> jamespage i found this bug
[13:40] <freak__> https://bugs.launchpad.net/juju/+bug/998238
[13:40] <mup> Bug #998238: local provider unit agents get stuck in pending state because of host firewall blocking communication <firewall> <local-provider> <pyjuju:Triaged> <juju-core:Triaged> <https://launchpad.net/bugs/998238>
[13:41] <freak__> they are saying disable ufw
[13:41] <freak__> and then destroy environment and build again
[13:41] <freak__> http://askubuntu.com/questions/134977/juju-stuck-in-pending-state-when-using-lxc
[13:42] <jamespage> freak__, I doubt its enabled if the physical machines are maas deployed
[13:43] <freak__> how to check ?
[13:43] <freak__> whether its enabled or not
[13:44] <sparkiegeek> freak__:  can you SSH on to the machines that are still pending and paste /var/log/cloud-init-output.log and /var/log/juju/*
[13:44] <freak__> sparkiegeek , ok i will
[13:48] <freak__> sparkiegeek , here is the output http://paste.ubuntu.com/15849429/
[13:49] <sparkiegeek> freak__: that looks like it's all healthy - how about /var/log/juju/all-machines.log ?
[13:50] <freak__> sparkiegeek, ok i will share
[13:51] <jamespage> tinwood, recheck-full not really required for the dpdk ports fix
[13:51] <tinwood> jamespage, I guess I'm just a bit paranoid.  Sorry.
[13:52] <tinwood> One of the other charms broke on wily/liberty because it wasn't enabled when I did pause/resume.
[13:52] <jamespage> tinwood, np
[13:53] <jamespage> freak__, sorry - doing about 5 different things at once so apologies
[13:53] <jamespage> freak__, thats the juju machine 0 cloud-init output
[13:54] <tinwood> jamespage, xenial/mitaka works with the ovs change.  Just checking trusty/kilo now. (for dvr).
[13:54] <freak__> jamespage , no issue.. you guys at canonical are very supportive.. salute you
[13:54] <jamespage> freak__, you should be able to ssh directly to the lxc units  - say ssh ubuntu@192.168.6.164
[13:54] <beisner> cholcombe, yah, ceph-radosgw amulet full is failing @ master in the same way as on your review.   http://pastebin.ubuntu.com/15849481/   got ideas?
[13:54] <freak__> ok. let me ssh
[13:54] <jamespage> freak__, you might not be able to
[13:54] <jamespage> lets see
[13:57] <cory_fu> aisrael: Thanks for charm-tools#182!  I had one review comment / request, but awesome that you took that on.  :)
[13:58] <freak__> jamespage i was able to do ssh to lxc here is the output http://paste.ubuntu.com/15849549/
[13:59] <jamespage> freak__, is 192.168.11.193 the ip address of machine 0?
[14:00] <freak__> jamespage yes its the ip on machine 0 vlan 11
[14:00] <jamespage> freak__, oh wait - thats a different subnet to the lxc containers? can they actually access that IP ?
[14:01] <freak__> jamespage , they are on same machine
[14:02] <jamespage> freak__, can you explain your networking a bit please
[14:03] <aisrael> cory_fu: My pleasure. I just updated the pull request. I'm thinking I should also update the proof command to do similar wrt colourized output
[14:03] <freak__> on machine 0 i have given ip 192.168.6.193 on eth 0 in maas, on eth1 no ip ,, i have created vlans/subinterfaces
[14:03] <freak__> from vlan 11-16
[14:03] <freak__> for update :: from lxc on machine 0 i cannot ping 192.168.11.193
[14:04] <cory_fu> aisrael: I think that would be nice, but also a somewhat larger undertaking
[14:04] <freak__> but on machine 0 i also have the ip 192.168.6.193
[14:04] <freak__> so lxc should communicate through that
[14:04] <freak__> i mean 192.168.6.193 on machine 0 can communicate to 192.168.6.164 on lxc
[14:05] <jamespage> freak__, yeah - I see what you mean
[14:06] <jamespage> freak__, so the vlan interfaces are all trunked in over eth0 on machine 0 right?
[14:06] <jamespage> and you did that via MAAS I'm guessing...
[14:06] <freak__> eth1 is trunk
[14:06] <jamespage> oh right - sorry
[14:06] <freak__> and vlans are configure on eth1
[14:06] <jamespage> okies...
[14:07] <jamespage> dimitern, hey - need some support here ^^ how does juju decide which IP address of machine 0 to use for machine agents to communicate with?
[14:07] <jamespage> context here is that the lxc containers being deployed are trying to address an IP address of machine 0 which they can't actually route to
[14:08] <jamespage> despite the fact that machine 0 has an IP on the same subnet
[14:08] <jamespage> dimitern, 1.25.5 juju release - freak__: MAAS 1.9?
[14:08] <freak__> jamespage maas version is 1.9
[14:08] <jamespage> ta
[14:09] <jamespage> freak__, bear with us on this one
[14:09] <freak__> jamespage ,  no issue i will wait
[14:10] <cory_fu> aisrael: Oh, I actually missed that was proof and not lint (a separate issue I created) and thought it would just be a blanket colorization.  Hrm.  I just realized that, technically, the intention of INFO in proof vs build is different and green might not be the best color for I from proof.  But I don't see another, better alternative
[14:10] <jamespage> tinwood, ok - thats good enough for me - pushing that through
[14:11] <jamespage> freak__, can you check for me what 'node0.maas' resolves to please
[14:12] <freak__> jamespage , here is the output http://paste.ubuntu.com/15849691/
[14:13] <jamespage> freak__, ack thanks - that looks right to me
[14:13] <jamespage> .6 not .11
[14:15] <freak__> jamespage the ip of region controller is 192.168.6.11 and of cluster controller is 192.168.6.12
[14:15] <freak__> and then the node0 ip is 192.168.6.193
[14:15] <jamespage> freak__, +1
[14:15] <freak__> if i run dig node0.maas on machine 0 for that output is this http://paste.ubuntu.com/15849691/
[14:16] <freak__> if you want dig on region or cluster controller i can also share that if you say
[14:16] <tinwood> jamespage, yep, kilo passed too.  Good call. :)
[14:16] <cory_fu> aisrael: Merged.  :)
[14:17] <aisrael> cory_fu: <3
[14:40] <freak__> jamespage 192.168.11.193 ip should be reachable from lxc .here is the snip of routing table http://paste.ubuntu.com/15850132/
[14:41] <jamespage> freak__, 192.168.6.1 can route between .6 and .11 ?
[14:41] <freak__> i think i should change the gateway ip to 192.168.6.193
[14:42] <freak__> that would be much better
[14:44] <freak__> jamespage i changed the default gw from 6.1 to 6.193
[14:44] <freak__> now from lxc i can ping to 11.193
[14:45] <jamespage> freak__, I suspect that's not a great idea
[14:45] <jamespage> they might be able to get to the bootstrap node, but I suspect the rest of the world is not inaccessible
[14:46] <freak__> jamespage you are right but in that case lxc should choose 6.193 ip to go to outside world
[14:46] <jamespage> freak__, not really
[14:46] <freak__> do not choose 11.193
[14:46] <jamespage> a default gateway should be enough most of the time
[14:47] <jamespage> the problem is the way the machine agent on the physical machine is configuring the machine agents in the lxc containers to get their tools
[14:49] <icey> with juju2, how do I setup an apt-http-proxy for an openstack cloud? I have it configured in my cloud.yaml that I imported the cloud settings with but it doesn't seem to be using it
[14:51] <freak__> jamespage how can i force lxc to resume its process of downloading tools which was interrupted to inaccessible ip 11.193
[14:52] <tvansteenburgh> cory_fu: when creating a layer, when should one create a config.yaml, versus just exposing options in layer.yaml? is that documented somewhere?
[14:52] <jamespage> freak__, hmm
[14:52] <jamespage> freak__, restarting cloud-init might work
[14:52] <jamespage> my other suggestion was to reboot the container - but that might reset your temp route
[14:54] <freak__> jamespage if we make the route permanent by modifying networks file
[14:54] <freak__> then restart the container
[14:54] <freak__> btw how we will restart container
[14:54] <cory_fu> tvansteenburgh: No, I don't think layer options are well documented yet.  Basically, layer options are a replacement for, e.g., apache.yaml from the apache-php layer, so that we don't have an explosion of .yaml files.  So, they're intended for a charm layer to influence what a base layer does, whereas config.yaml is for user-facing options
[14:54] <jamespage> freak__, well maybe but I'm concerned that will then just break something else
[14:54] <jamespage> freak__, reboot inside the container...
[14:55] <freak__> nice :P
[14:55] <tvansteenburgh> cory_fu: oh, right :)
[14:55] <tvansteenburgh> cory_fu: i forgot that config.yaml was just part of the charm :P
[14:55] <cory_fu> :)
[15:03] <shruthima> Hi All,We have developed IBM-Installation Manager in bash and   i have declared ibm_im_package option in layer.yaml but iam unable to fetch it ?   can you please suggest any command is there to fetch layer options ??
[15:05] <lazyPower> shruthima - layer options are documented here https://jujucharms.com/docs/devel/reference-layer-yaml
[15:05] <lazyPower> ensure you've implemented them as defined in that reference guide, you can then fetch the layer options like we do in this example: https://github.com/mbruzek/layer-storage/blob/master/reactive/storage.py#L113
[15:07] <lazyPower> shruthima - in addition to that guide, ensure you're also running the latest version of charm-tools (2.1.2) so you've got hte required builder modifications to support options in layer.yaml
[15:11] <shruthima> we have written code in bash ? so any bash example can you provide if available ?
Can you please provide any example written in bash code ?
[15:17] <lazyPower> shruthima - ah good point i'm not sure if thats exposed via the bash CLI
[15:18] <lazyPower> cory_fu i'm pretty certain it is, do you happen to know if that was added to the bash helpers?
[15:19] <aisrael> jcastro: ping
[15:21] <cory_fu> lazyPower, shruthima: Actually, layer options aren't actually exposed by bash CLI. :(  It shouldn't be too hard to add, and it would be in the base layer, so won't require much to get it released.
[15:21] <lazyPower> oh, good to know!
[15:21] <lazyPower> thanks cory_fu
[15:21] <cory_fu> However, I'm pretty busy today, with the last day of the big data team sprint, so I'm not sure if I'll be able to get it done today
[15:22] <shruthima> oh k thanku lazyPower cory_fu
[15:23] <cory_fu> shruthima: I will send out an email to the juju list when I can get that done
[15:24] <shruthima> cory_fu : Thanku :)
[15:32] <bdx> hows it going everyone? I've a few jaas/charmstore questions for anyone listening .... 1. How can I delete stale charms that I don't want to show up in the charmstore anymore (ones in the legacy charmstore that got pulled in from my lp code, and new jaas namespace charms)?  2. How can I create a channel ?  3. (juju2) When I add users with write access to a model, they don't seem to be able to `juju ssh` into
[15:32] <bdx> any deployed machines; do I need to each new users ssh key, if so, which key?
[15:33] <lazyPower> bdx - you were asking about channels - have a look at the docs over the charm store + channels here https://jujucharms.com/docs/devel/authors-charm-store
[15:34] <bdx> lazyPower: perfect, thx
[15:34] <lazyPower> bdx - regarding removing of charms - you can only remove charms that have been uploaded to the new store. The old store is like an icebox, think of those charms as being in stasis.
[15:41] <bdx> I'll offer an award of $50 and a bucket of beer to charmstore admin who can remove some old, stale, failed charm attempts for me :-)
[15:43] <magicaltrout> i'll give them some pork scratchings and a pint of ale
[15:46] <lazyPower> magicaltrout - hows session planning going for apachecon?
[15:46] <bdx> who could resist? someone will break .... just give them time
[15:47] <lazyPower> bdx - good things come to those who are patient
[15:47] <magicaltrout> bleh in between contract work on saiku, contract work for nasa and apachecon my life is a big mush of loads to do
[15:47] <lazyPower> magicaltrout - Fair enough :) was poking as a leading question to offer eyeballs for review/help if any of that would be helpful to your goals there
[15:48] <magicaltrout> its coming on, the Juju Data Management talk will be pretty straight forward (famous last words) I'm working on the tutorial content and presentation slides for all of them at the mo
[15:48] <lazyPower> ack, just lmk when/if i can be of help
[15:48] <magicaltrout> my plan is to get the planning and presentation stuff done betwen now and the 29th which is dealing for my real job, and after that I should have 2 weeks to get all the technical stuff done for apachecon
[15:49] <magicaltrout> transpires Q1 2016 is pretty chaotic ;)
[15:57] <magicaltrout> lazyPower: last year I was out at 2am playing very drunk beach volleyball, went to bed at 5 got up at 9 and wrote my presentation for 11
[15:57] <magicaltrout> ever the professional.....
[15:58] <magicaltrout> wont be happening this year with my tutorial load
[16:04] <tinwood> gnuoy, interesting.  The amulet for wily/liberty isn't stopping apache2
[16:05] <gnuoy> oh, well that's be it then
[16:06] <tinwood> gnuoy, except now it has.
[16:06]  * tinwood thinks this is weird.
[16:07] <tinwood> gnuoy, might be finger trouble on my side.  More investigation.
[16:07] <gnuoy> good luck
[16:07] <tinwood> gnuoy, and just to verify, you were just doing amulet tests with a bootstrapped juju only?
[16:08] <gnuoy> tinwood, yep
[16:09] <tinwood> gnuoy, kk, ta
[16:13] <freak_> jamespage i made the default gw updated route to 6.193 permanent
[16:13] <freak_> and restarted the lxc
[16:13] <freak_> now when i see the cloud-init-output.log
[16:14] <freak_> here is the output http://paste.ubuntu.com/15852704/
[16:14] <freak_> it updated the route info only but not resumed the process
[16:29] <beisner> icey, cholcombe - bug 1570960
[16:29] <mup> Bug #1570960: ceph-osd stuck in a mon-relation-changed infinite loop <uosci> <ceph-osd (Juju Charms Collection):New> <https://launchpad.net/bugs/1570960>
[16:31] <icey> that is not stuck... or in a mon relation changed loop
[16:31] <icey> it's in an update-status loop, which is by design?
[16:32] <beisner> icey, well it goes on and on back to mon-relation-changed then apt installs again and again
[16:34] <beisner> icey, yah so my quick assessment may not be right on the actual issue.  the symptom is solid though:  ceph-osd blocks forever on trusty-icehouse
[16:37] <beisner> icey, bug updated
[16:37] <icey> beisner: I can look after lunch
[16:52] <cmars> icey, cholcombe question about the ceph charm.. should I be able to deploy it to lxd controller? anything special that needs to be done to get it working in containers?
[16:52] <cholcombe> cmars, it should just work.  are you running into issues?
[16:52] <cmars> i've tried using directories for the osds, but they always seem to be stuck in HEALTH_WARN
[16:53] <cholcombe> can you paste the warning for me?
[16:53] <cmars> cholcombe, yep, i'll try again and get you an error message from a fresh deploy
[16:53] <cholcombe> ok thanks
[17:18] <cmars> cholcombe, here's what I'm seeing: https://paste.ubuntu.com/15854608/
[17:19] <cholcombe> cmars, i've seen that before with instances that  have disks that are too small.  your ceph osd tree will show that all the osds are weighted at 0 instead of 1 like they should be
[17:21] <cmars> cholcombe, they're all running in containers, so they all think they have the same usage & free space as the host
[17:21] <cmars> cholcombe, is that the problem, perhaps?
[17:22] <cholcombe> could be.  what does your ceph osd tree look like?
[17:22] <cmars> cholcombe, how do I show that?
[17:23] <cholcombe> just type `ceph osd tree` :)
[17:45] <webscholar> Hi dimiter
[17:45] <webscholar> are you around?
[17:45] <webscholar> james how are you?
[17:46] <webscholar> jamespage need some help
[17:56] <c0s> bdx: I am sorry - I just seen your PR for the puppet layer, which I have essentially implemented after talking to you here yesterday
[17:57] <c0s> Wasn't trying to steal your idea, really.
[17:58] <beisner> thedac, can you cr+2 wf+1 this?  neutron-api-odl unit and lint were failing @master.  fyi, our ci fails b/c this charm has no amulet test yet.  https://review.openstack.org/#/c/306552/
[17:58] <thedac> beisner: I'll take a look
[18:01] <beisner> thx thedac
[18:02] <beisner> thedac, for context:  https://review.openstack.org/#/q/topic:pbr-reqs
[18:04] <cory_fu> Is it true that local provider doesn't work on centos?  I didn't think that was the case, but had someone say that it was
[18:04] <thedac> beisner: approved
[18:33] <beisner> cholcombe, do we have a bug opened for the cache tier failure?
[18:33] <cholcombe> beisner, not yet i think
[18:33] <beisner> cholcombe, ok i'll raise
[18:42] <beisner> cholcombe, is this the --yes-i-really-mean-it thing? ;-)
[18:48] <bbaqar> jamespage: is the next branch of keystone merged into stable yet, for mitaka? I would like to get a small commit in. Am I in time?
[18:50] <beisner> hi bbaqar - charm feature freeze was last week.  we'll be releasing next to stable late next week.  the only things we can land into next before then are critical bugfixes and test updates.
[18:51] <bbaqar> jamespage: okay no worries.
[19:39] <jamespage> beisner, https://review.openstack.org/#/c/305065/
[19:39] <jamespage> UOSCI says go...
[19:46] <freak_> hi everyone
[19:46] <freak_> need help regarding lxc containers
[19:52] <cholcombe> beisner, yeah it's the --yes-i-really-mean-it bs
[20:10] <beisner> cholcombe, bug 1571050
[20:10] <mup> Bug #1571050: remove-cache-tier action failing @mitaka <uosci> <ceph (Juju Charms Collection):New for xfactor973> <ceph-mon (Juju Charms Collection):New for xfactor973> <https://launchpad.net/bugs/1571050>
[20:11] <cholcombe> beisner, yeah i'm on it :)
[20:11] <beisner> sweet thx sir
[20:14] <cholcombe> beisner, the --yes-i-really-mean-it flag fixes it.  i'll have a patch up soon
[20:14] <beisner> cholcombe, awesome
[20:43] <cholcombe> beisner, https://code.launchpad.net/~xfactor973/charm-helpers/ceph-jewel-flag/+merge/292049
[20:44] <cholcombe> we'll have to resync the charms again :-/
[20:56] <beisner> cholcombe, c-h merged.   on these 2, i'd say just do a resync as a new patchset:
[20:56] <beisner> https://review.openstack.org/#/c/305922/
[20:56] <beisner> https://review.openstack.org/#/c/305933/
[20:56] <beisner> cholcombe, then new reviews for any others, if any
[21:06] <cholcombe> beisner, good idea
[21:08] <cholcombe> beisner, i think ceph-mon and ceph are the only ones that need it since they actually run the commands
[21:09] <beisner> woot
[21:10] <cholcombe> i have a new patchset up for ceph-mon
[21:12] <cholcombe> beisner, for the future i'm pondering pulling out the cli calls and making api calls instead
[21:13] <cholcombe> so we can get out of this every iteration breaks things loop
[21:13] <beisner> but you just made your own api!  :-)
[21:13] <cholcombe> hehe
[21:13] <cholcombe> i mean swapping out the cli calls for librados calls
[21:14] <beisner> yah i'm just giving you shenanigans
[21:14] <cholcombe> it's not hard but it'll require lots of typing :)
[21:14] <beisner> ha!
[21:14] <cholcombe> and a massive refactor which i'll have to hold off till 16.10 for
[21:14] <beisner> ok so, gonna do a charm-ceph review too cholcombe ?
[21:14] <cholcombe> yeah
[21:15] <cholcombe> it's up
[21:15] <beisner> cool.  i think this should 'just land' as its the same result as master:    https://review.openstack.org/#/c/305922/   <- cholcombe ?
[21:16] <cholcombe> yeah
[21:16] <beisner> boom
[21:17] <cholcombe> damn it's a merge frenzy
[21:26] <beisner> thedac, dang and we just revalidated amulet-full rmq @master.  well you know you'll have a good baseline  ;-)
[21:28] <thedac> yeah, I suspect few people were doing ssl or we would have heard the yelling on this one
[21:33] <beisner> thedac, odd though, the rmq amulet test flips ssl on and off several times then sends/check amqp messages
[21:34] <thedac> beisner: subsequent to install though.
[21:34] <beisner> ah but it has first settled in a non-ssl config, so everything is installed by the time we flip it
[21:34] <beisner> yeah
[21:34] <thedac> With the bundle it is set before install
[21:37] <cholcombe> haha beisner i love your --yes-i-really-approve-it
[21:38] <beisner> lolz
[22:07] <beisner> thedac, cholcombe - amulet-smoke is clear on rmq, ceph, ceph-mon.  imho, land-worthy
[22:08] <cholcombe> sweet!
[22:09] <beisner> nothin like landing after 5p on a fri, yah?
[22:10] <thedac> beisner: thanks. I'll wait for a review Monday unless you are handing out +2s
[22:10] <beisner> thedac, did you exercise that in the ssl mojo spec?
[22:10] <thedac> beisner: a version of that yes
[22:10] <thedac> ddellav: actually this would help you. Do you want to test it out? https://review.openstack.org/#/c/306628/
[22:11] <ddellav> ah nice thedac
[22:12] <beisner> thedac, ddellav - yah the mojo spec is really our only mechanism to exercise that.   it lgtm though!
[22:12] <beisner> thedac, i'd be inclined to land her now tbh
[22:13] <thedac> ddellav: I'll leave it to you. We'll land it after you test it
[22:13] <ddellav> thedac whats the best way to incorporate that fix into my mojo spec?
[22:14] <beisner> i don't think a refspec is consumable in mojo, though it is consumable in juju-deployer
[22:14] <thedac> oooh, good question. Because we need to grab the ref specs.
[22:14] <thedac> Yeah, not sure it is doable in any easy kind of way
[22:16] <beisner> ddellav, thedac - looks like it'd take a fork, refspec fetch, merge, push, and repoint the spec's collect at the fork
[22:17] <ddellav> beisner ew
[22:17] <thedac> beisner: ddellav this is what I tested with. http://pastebin.ubuntu.com/15860862/ That both produced the problem and showed that it was fixed.
[22:17] <thedac> honestly I think that is enough
[22:17] <ddellav> thedac ok, ill run with that
[22:17] <thedac> with a local copy
[22:18] <beisner> thedac, me too.   the only hold up i've got is:    is the ctl file always /usr/sbin/rabbitmqctl, from precise --> xenial?
[22:19] <thedac> as far as I know. Also we use the same test elsewhere in the charm
[22:19] <beisner> i'm sold
[22:54] <cholcombe> i'm thinking of adding librados to charmhelpers.  Is it a bad idea to import python libraries that require an apt-get install ?
[22:55] <cholcombe> looks like the README.test already contains a bunch of libraries.  Seems like it's ok