[00:03] <blr> Noticed when creating a new charm with the python template, charmhelpers are installed via pypi. Does that obviate the need for charm_helpers_sync and charm-helpers.yaml?
[00:19] <lazyPower> sebas538_: want to see something cool?
[01:31] <designated> According to: http://www.percona.com/doc/percona-xtradb-cluster/5.5/installation.html, percona-xtradb-cluster 5.5 does not work with app armor, yet there is an app armor profile created when deploying percona-cluster charm.  Could this possibly be the reason why my cluster is not coming up?
[01:34] <lazyPower> designated: its doubtful thats a core openstack-charmers charm
[01:39] <sarnold> designated: check for DENIED lines in the logs
[01:53] <designated> sarnold: which logs specifically?
[01:54] <sarnold> designated: /var/log/syslog or /var/log/audit/audit.log (if auditd is installed)
[01:55] <designated> also it doesn't matter what I configure ha-bindiface with, it still seems to use the addresses from a different interface when configuring wsrep_cluster_address=gcomm:// in my.cnf
[01:58] <designated> sarnold: auditd isn't running and there are no DENIED messages anywhere in /va/log/syslog
[01:58] <sarnold> designated: okay, then it's not apparmor's fault :)
[01:59] <LinstatSDR> Evening everyone.
[02:01] <designated> can anyone confirm whether the configuration of "ha-bindiface" within the charm is in any way associated with what's supposed to get configured for wsrep_cluster_address in my.cnf?
[02:02] <designated> the charm seems to be configuring wsrep_cluster_address with the addresses resolved from the hostnames, which may be a problem with the multicast requirement.
[02:05] <designated> also, should corosync_bindiface under the hacluster charm match the vip_iface for the percona-cluster charm?
[02:05] <designated> i need more documentation.
[02:08] <LinstatSDR> https://bugs.launchpad.net/charms/+bug/1245095 ???
[02:08] <mup> Bug #1245095: rabbitmq-server charm ha-bindiface default breaks rabbitmq-hacluster subordinate charm <openstack> <Juju Charms Collection:Opinion> <https://launchpad.net/bugs/1245095>
[02:08] <LinstatSDR> Maybe or not maybe?
[02:13] <designated> LinstatSDR: possibly, I'll look into that.
[02:15] <LinstatSDR> Okay. Sorry I cannot help you designated.
[07:26] <marcoceppi> .
[10:17] <mwak> hi
[10:55] <marcoceppi> hi mwak o/
[10:56] <mwak> how are you marcoceppi ?
[10:56] <marcoceppi> good, an you?
[10:58] <mwak> good
[10:58] <mwak> looking to have snappy on online labs
[13:48] <schkovich> jcastro: im going to have a conferece call with rackspace enterpise account lead on using juju for deployment on rackspace cloud. im wondering if there is any progress on that topic?
[13:49] <schkovich> jcastro: im referring to question and information you provided on askubuntu http://askubuntu.com/questions/166102/how-do-i-configure-juju-for-deployment-on-rackspace-cloud
[13:56] <marcoceppi> schkovich: Rackspaces API is still too far off trunk AFAIK
[13:56] <schkovich> marcoceppi: they are suggesting using heat instead of juju
[13:57] <schkovich> however in my understanding those are different tools
[13:57] <marcoceppi> schkovich: I'm sure they are, and it is a bit different. Heat is openstack specific for starters, it's more like cloud formations for amazon
[13:57] <schkovich> and i don't like to be pushed ;)
[13:57] <marcoceppi> there's a bit of overlap, sure, but that's because we're both operating in the orchestration name space
[13:58] <cjohnston> Is it possible to change the timestamp in Juju logs from UTC to the TZ used by the machine?
[13:59] <schkovich> yeah, there is overlap no doubt
[14:00] <schkovich> what i will try to find later today is if rackspace private cloud would play nicely with juju
[14:00] <schkovich> otherwise i will have no other option but to persue my company to move to ubuntu cloud ;)
[14:00] <rbasak> wallyworld: I'm not really convinced that https://github.com/juju/juju/pull/1323 really fixes the problem.
[14:01] <rbasak> wallyworld: the code still assumes that the ubuntu user uses /home/ubuntu, for example. It should use ~ubuntu, etc.
[14:01] <rbasak> wallyworld: and IIRC, the original issue is that the "ubuntu user" in a local environment means something completely different. It should be ignored completely in the local environment case.
[14:02] <wallyworld> rbasak: if fixes the issue of determining if the ubuntu user exists before doing a chown. in the master branch "id ubuntu" is used instead of grepping the passwd file. but i see that ~ubuntu is better than /home/ubuntu
[14:03] <rbasak> wallyworld: it should not be attempting to do a chown on anything in ~ubuntu (or /home/ubuntu) whether or not the ubuntu user exists, when in a local environment.
[14:03] <rbasak> In a local environment, the "ubuntu" user is not special. It's just another user.
[14:03] <rbasak> OTOH, in a cloud environment, the "ubuntu" user definitely is special and it's fine for Juju to use/clobber it.
[14:04] <rbasak> wallyworld: you're just swapping one failure case for another here.
[14:04] <wallyworld> i see, that does make sense. it may not be trivial to implement
[14:04] <rbasak> wallyworld: now, if I add "adduser ubuntu" on my laptop, but try a local environment from my "rbasak" user, it'll still fail.
[14:05] <wallyworld> that's sort of an edge case you think?
[14:05] <wallyworld> ie i would prefer not to block 1.21
[14:05] <rbasak> I think it's probably more common that you expect.
[14:05] <wallyworld> we can fix for 1.22
[14:05] <rbasak> For example, when running the installer for a desktop system, I might just type "ubuntu/ubuntu" to get started. I used to do that, actually.
[14:05] <rbasak> The failure case that caused people to hit this bug seems to be similar.
[14:05] <marcoceppi> schkovich: you could still use RackSpace, you'd just have to write some code around juju to talk to their API
[14:06] <marcoceppi> but that's a bit of extra work
[14:06] <rbasak> wallyworld: sure, I'm not asking you to block anything. Just please consider that patch to be a workaround that swaps one failure case for another, and not a proper fix.
[14:06] <schkovich> wallyworld: sorry to pop into conversation but perhaps uid=$(id -u ${jetty_user}) could be more suitable then to grep the passwd file
[14:06] <wallyworld> rbasak: given 1.21 is already really late, we will definitely fix properly for 1.22
[14:06] <rbasak> The standard way is "getent passwd <user>"
[14:07] <rbasak> That's quite common in maintainer scripts.
[14:07] <schkovich> marcoceppi: im using manual environment for the moment which is working
[14:07] <wallyworld> in master, i use "id ubuntu", but can change to getent
[14:07] <rbasak> I don't see an actual grep in the password file though.
[14:07] <rbasak> id should be no worse I think.
[14:07] <marcoceppi> schkovich: right, so you could build around that, there's examples of this with DigitalOcean and Online-Labs
[14:08] <marcoceppi> schkovich: https://github.com/kapilt/juju-digitalocean
[14:08] <wallyworld> schkovich: yeah, the grep passwd file is a bit hacky
[14:08] <wallyworld> rbasak: so to summarise, no chown for local provider
[14:08] <marcoceppi> schkovich: I mean, it's more work but it's possible to build on top of juju for stuff not directly supported in juju yet
[14:09] <rbasak> wallyworld: for now, that's fine. In the long term, don't touch the ubuntu user or ~ubuntu at all in the local provider.
[14:09] <schkovich> marcoceppi: i will take a look into that
[14:10] <wallyworld> rbasak: ok, will do. what will ship in 1.21 is that the chown will still be done, but based on the ubuntu user existing, not a /home/ubuntu check. agreed that's sub optimal as you say
[14:10] <rbasak> wallyworld: ack. Thank you for working on this!
[14:10] <wallyworld> will fix properly in 1.22
[14:10] <schkovich> marcoceppi: unfortunately there is a preasure to get things done :(
[14:10] <wallyworld> np, sorry for not getting it right first up
[14:10] <wallyworld> it was a last minute fix based on comments isw in the bug
[14:10] <marcoceppi> schkovich: that's understandable, I may take a look at this over the holiday break myself, but I don't ahve a rackspace account atm
[14:12] <schkovich> marcoceppi: i can't give u access to the company account but sounds as interesting project on which i could work in my free time
[14:13] <marcoceppi> schkovich: oh, I wouldn't need/want access. I'd just open an account. Simply stating it would be a learning curve
[14:14] <schkovich> marcoceppi: if i do please contact me, i would luv to get involved
[14:15] <schkovich> marcoceppi: same applies other way around, if i start working on rackspace plugin i will contact you :)
[14:15] <marcoceppi> schkovich: awesome, I'm always in here, feel free to give me a ping
[14:16] <schkovich> marcoceppi: i will, since im not regular here u can google me by nick
[14:19] <jcastro> you could do the manual provider with rackspace
[14:19] <jcastro> but then again, it's manual and that takes away like half the reason
[14:19] <schkovich> jcastro: i already did that :)
[14:20] <schkovich> jcastro: and i agreed with marcoceppi that it would be nice to have rackspace plugin
[14:21] <schkovich> jcastro: we might start the project over comming holidays
[14:22] <schkovich> jcastro: i will try to get as much information as possible later today while on call with rackspace guys
[14:22] <schkovich> jcastro: information on rackspace api of course :)
[14:24] <schkovich> brb
[14:24] <jcastro> if you need help the core guys are in #juju-dev
[14:37] <schkovich> jcastro: thank you for the tip :)
[15:49] <LinstatSDR> Morning guys.
[15:57] <marcoceppi> o/ LinstatSDR
[15:57] <LinstatSDR> hi :)
[17:54] <lazyPower> mwenning: ping
[17:55] <mwenning> lazypower, pong
[17:56] <mwenning> lazyPower, pong
[17:59] <lazyPower> ahoy mwenning, are you still working on teh dell openmanage charm?
[18:01] <mwenning> lazyPower, I've been tied up with other stuff.  When I get a chance to try it, juju usually foils my attempts :-(
[18:01] <lazyPower> aisrael: ^
[18:01] <lazyPower> thanks mwenning, was just circling back as we came across teh bug during triage
[18:02] <aisrael> mwenning: Would it be okay to assign the open MP to you in Launchpad?
[18:02] <aisrael> mwenning: if so, what's your lp name?
[18:03] <mwenning> lazyPower, understand.  I'm not happy about it, but Dell certs and bugs are 1st priority.
[18:03] <mwenning> mwenning
[18:03] <mwenning> MP?
[18:03] <lazyPower> mwenning: judgement free zone here, i completely understand priorities :)
[18:04] <mwenning> lazyPower, 1) what is MP , 2) any progress on the amulet bug?
[18:04] <lazyPower> 1) Merge Proposal - but i think aisrael meant bug.
[18:04] <lazyPower> 2) i dontrecall teh bug - can you refresh me?
[18:05] <aisrael> mwenning: lazyPower: Yes, sorry. https://bugs.launchpad.net/charms/+bug/1325700
[18:05] <mup> Bug #1325700: New Charm: Dell OpenManage Server Administrator (OMSA) <Juju Charms Collection:In Progress> <https://launchpad.net/bugs/1325700>
[18:06] <mwenning> lazyPower, https://bugs.launchpad.net/amulet/+bug/1375344
[18:07] <mup> Bug #1375344: Amulet fails to bring up a machine to run relation-sentry running openmanage charm <Amulet:New> <https://launchpad.net/bugs/1375344>
[18:07] <lazyPower> mwenning: id say so! amulet no longer uses relation sentries.
[18:07] <lazyPower> tvansteenburgh: we need to do a triage on teh launchpad bugs for amulet
[18:08] <mwenning> lazyPower, okeydokey.
[18:09] <tvansteenburgh> lazyPower: ack
[18:09] <mwenning> lazyPower, IA I can give it a try this week again.
[18:09] <lazyPower> mwenning: sorry about the lack of response on that bug - i think we moved all the bugs over to github
[18:15] <sebas5384> lazyPower: o/
[18:15] <lazyPower> sebas5384: o/
[18:16] <lazyPower> sebas5384:  did you see the video i shot to the list? Seems like its right up your alley
[18:16] <sebas5384> lazyPower: didn't see it :(
[18:16] <sebas5384> paste it here again please :)
[18:16] <lazyPower> https://www.youtube.com/watch?v=bCvl-TsxVXA&feature=gp-n-y&google_comment_id=z12rdtcw0zyxifibb04cfv0pbwq4h5jy1j4
[18:16] <sebas5384> lazyPower: oooh yes! i sow your email about it
[18:17] <sebas5384>  but didn't sow the video yet
[18:17] <sebas5384> :)
[18:17] <sebas5384> i'm gonna watch it then
[18:21] <jcastro> lazyPower, did we put your new video up on insights yet?
[18:21] <lazyPower> jcastro: not that i'm aware of
[18:26] <jcastro> lazyPower, always ping me when you push a new vid so I can add it
[18:26] <jcastro> lazyPower, any plans on adding etcd and flannel charms to proper trusty?
[18:26] <lazyPower> ack, will do jcastro. i'll add it to my workflow
[18:26] <lazyPower> yep, its part of a master plan thats brewing
[18:29] <sebas5384> lazyPower: nice!!
[18:35] <lazyPower> sebas5384: glad you liked it :)
[18:40] <sebas5384> lazyPower: do you think flannel can do the networking of the containers created by the juju in the vagrant flow ?
[18:41] <sebas5384> lazyPower: i tried some other stuff but, i can't make it work
[18:41] <sebas5384> definitively my knowledge about networking is really poor
[18:41] <lazyPower> sebas5384: it only enables private networking via the tun/tap device - it hasn't solved public-interface reachability. And its using the same basic princial you were describing to me
[18:41] <lazyPower> i think the better bet here, thats fully portable with our vagrant experience is a vpn service on the vagrant machine
[18:42] <lazyPower> aisrael: you've recently done some work on this, what do you think?
[18:42] <sebas5384> lazyPower: yeah, i installed this https://openvpn.net/index.php/access-server/download-openvpn-as-sw.html
[18:42] <lazyPower> sebas5384:  aisreal recently published an article about networkign with vagrant on yosemite, did you see it?
[18:43] <sebas5384> but i'm didn't test it yet
[18:43] <sebas5384> lazyPower: no oO !
[18:43] <sebas5384> where!?
[18:43] <lazyPower> http://www.adamisrael.com/blog/2014/12/12/sshuttle-workaround-for-os-x-10-10-yosemite-juju-and-vagrant/
[18:43] <lazyPower> looks like neither option are required on osx
[18:43] <lazyPower> its routing
[18:44] <sebas5384> hummmm
[18:45]  * sebas5384 reading
[18:48] <sebas5384> lazyPower: so after that route i can ping the private container ip ?
[18:48] <lazyPower> sebas5384: as i understand it, its setting up a route that will direct all 10.0.3.x traffic to the LXC bridge in the vagrant image
[18:49] <lazyPower> i haven't tested it myself, but its generated a bit of buzz since he published the article
[18:49] <sebas5384> lazyPower: of course!! it's what I'm looking for since i run the first vagrant up with juju in it
[18:49] <sebas5384> hehe
[18:49] <sebas5384> i'm going to test it!
[18:50]  * sebas5384 testing
[18:50] <lazyPower> let us know how it works out for you - if it performs as expected - lets get some feedback on the list :)
[18:50] <lazyPower> or maybe some of that social network lovin <3
[18:51] <sebas5384> lazyPower: yeah! sure :)
[18:55] <aisrael> lazyPower: sebas5384 Yes, please let me know if you run into any trouble with it!
[19:03] <Tug> Hi, I have an idea for a new charm
[19:05] <Tug> I'm using MMS Automation Agent to deploy and manage my mongodb cluster. juju could be providing the machines, install the mms agent and configure it
[19:06] <marcoceppi> Tug: it's completely possible
[19:06] <Tug> I was using the mongodb charm but it still isn't stable enough for me. MMS proved to work really great
[19:07] <Tug> and then I have access to the monotoring and backup services so that's a bonus
[19:10] <Tug> marcoceppi, yes and it's a really simple charm as there is a debian package for the agent. The charm could then check that each machine can communicate with each others, that the directory for the database is created etc.
[19:27] <lazyPower> Tug: that would be an excellent charm for the store, i'm sure 10gen would love to see something like that
[19:29] <Tug> the problem is on optimizing the machine power
[19:29] <lazyPower> How so?
[19:30] <Tug> config servers could be deployed on less powerful machines
[19:30] <Tug> mongod needs persistent storage and lots of RAM
[19:30] <Tug> whereas mongos might be optimized for cpu
[19:30] <lazyPower> well, thats part of the benefit of using constraints when you're deploying your machines - if you were to build the MMS Agent charm - you can then specify lower constraints for the config servers
[19:31] <lazyPower> and make that the standard by offering up a bundle of hte configuration
[19:31] <lazyPower> juju deploy my-mms-charm configsvr --constraints="Mem=1gb root-disk=8gb" is an easy way to specify this declaratively on the command line
[19:32] <Tug> ah yes you can have multiple services defined for the same charm, I forgot
[19:32] <lazyPower> you're still deploying the same charm, you just have a different name - so your peering will be different, but if you're exposing the relationships properly between the services shouldn't be an issue at all. And I do believe that MMS configures all this during runtime anyhow as they're doing a reconciler based mongo orchestration.
[19:34] <Tug> one last issue is that the type of instance that will be deployed on the machine is not configurable by the agent. It can only be done from the mms web interface at the moment.
[19:34] <Tug> maybe we should ask for this feature to mongodb first
[19:35] <lazyPower> Tug: sounds reasonable
[19:37] <Tug> lazyPower, I'm going to fill the request in mongodb's jira right now :)
[19:52] <lazyPower> hey jcastro
[19:52] <lazyPower> look at this https://github.com/rethinkdb/rethinkdb/issues/3410
[19:53] <jcastro> yeah I suggested that
[19:53] <lazyPower> oh, i thought this was organic
[19:53]  * lazyPower snaps
[19:53] <lazyPower> i got real excited there for a second
[20:03] <sebas5384> lazyPower: It Freaking Works !!
[20:03] <lazyPower> GREAT SUCCESS \O/
[20:03]  * sebas5384 excited!
[20:03] <sebas5384> now that's what i was talking about
[20:03] <sebas5384> :D
[20:04] <sebas5384> this is going to change everything around here
[20:04] <sebas5384> :)
[20:04] <aisrael> sebas5384: Excellent!
[20:04] <sebas5384> thanks aisrael !!!
[20:04] <aisrael> sebas5384: My pleasure! I love how fast it is interacting with my juju containers now, too.
[20:04] <sebas5384> that should be in the juju vagrant box
[20:05] <aisrael> sebas5384: That's something I'm going to look into.
[20:05] <sebas5384> aisrael: yeah i would love to see more love around containers with juju
[20:05] <lazyPower> sebas5384: oh yeah?
[20:05] <sebas5384> aisrael: good to know
[20:06] <lazyPower> sebas5384: hang out with us in #juju-edge, we're talking about workloads and containers and that story
[20:06] <sebas5384> lazyPower: yes! like using the lxd directly or something like that
[20:06] <sebas5384> lazyPower: done!
[20:18] <drbidwell> On a MAAS server where can I find the partman-auto/method rules referenced in /etc/maas/preseed/pressed_master?
[20:53] <marcoceppi> drbidwell: no idea, they may be stored in the datastore (postgresql)
[20:59] <sebas5384> aisrael: what would be the best approach to ssh into the containers? because the ssh keys aren't in the host :P
[21:00] <aisrael> sebas5384: I'm still doing that from inside vagrant. There might be a way of adding the ubuntu user key to your local keys, but I haven't explored that yet.
[21:01] <sebas5384> aisrael: yeah I think there's a way to add an ssh key for juju's to manage it
[21:01] <sebas5384> https://juju.ubuntu.com/docs/howto-authorised-keys.html ?
[21:06] <sebas5384> it's not clear to me how to use it
[21:09] <aisrael> I know the vagrant image uses an insecure key, so in theory you could copy the keys to your local ~/.ssh, ssh-add them, and ssh directly into the containers
[21:12] <aisrael> Yes, that'll work.
[21:12] <marcoceppi> sebas5384: you should be able to add your personal key to the deployment
[21:12] <aisrael> I copied the ssh keys from the vagrant user, renamed to id_vagrant and ssh-added them.
[21:12] <aisrael> I can then ssh ubuntu@10.0.3.x and access a container
[21:13] <sebas538_> so you are using like ssh -i .... ?
[21:14] <sebas538_> marcoceppi: yeah! but how
[21:14] <sebas538_> ?
[21:14] <aisrael> after copying and renaming the keys (id_rsa, id_rsa.pub) and copying to ~/ssh, run ssh-add id_vagrant
[21:14] <sebas538_> sorry for the noob question
[21:14] <sebas538_> aisrael: ohhh I see
[21:46] <drbidwell> marcoceppi: Any idea where I could find information about MAAS internal workings short of reading all of the code?