=== scuttlemonkey is now known as scuttle|afk [00:08] Are there any plans for an official trove charm? [00:11] :jamespage - I would like to know if there are future plans for a trove charm? If not, I would like to request an official trove charm....I am willing to help out in anyway possible. === kadams54-away is now known as kadams54 === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [02:06] marcoceppi_: i just had a thought - and it might be completely ludacris.. but what if we had a pattern as follows === TheRealMue is now known as TheMue [02:06] lazyPower: go on [02:07] if we deploy a charm that requires a build environment to assemble itself from code (in teh instance of flannel for docker) - what if it added container on the host, fetched the build env + source code, ran the buidl routine, and then the artifacts were pulled from the container, and the container destroyed leaving only a job log of the build process - to prevent polluting the host with the build tools [02:08] i could get arm64/ppc64el/x86 artifacts in the host (assuming it has net access) - and not leave build tools on the machine.. it does add some layers for failure in there.. but i think it has interesting possibilities. [02:08] (and those arch targets are respective to what environment i'm deploying to - as this is a golang bin artifact thats produced) [02:08] lazyPower: how quickly could you create a container? [02:09] seems like a good idea, but only if you could prevent having to spin up a build container for each unit [02:09] Depends, am i fetching a bin image from dockerhub or am i fetching a cloud image and using LXC [02:09] I was considering shipping a dockerfile with a base ubuntu 14.04 image to run the trial on this [02:10] as flannel-docker wont be deployed to a non-docker host. that much is specific in the relationship [02:10] i mean, you can co-lo it on one, but it noops [02:14] I'll run this by whit and mbruzek tomorrow to see if they think its interesting enough to devote a couple hours to prototyping the process. Thanks for being a sounding board === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [03:50] lazyPower: you still around? === kadams54 is now known as kadams54-away === zz_CyberJacob is now known as CyberJacob [08:07] bdx, no plans for a trove charm from my team === cmars` is now known as cmars === CyberJacob is now known as zz_CyberJacob === scuttle|afk is now known as scuttlemonkey [14:02] marcoceppi_: back now === smoser_ is now known as smoser [15:52] tvansteenburgh: there's a thread going on the list right now about makefile targets that i think you had cautioned me about before wrt bundletester behavior and running integration tests multiple times [15:52] tvansteenburgh: might want to poke your head in and take a look and give a quick reply on behavior here. Thread name is: Makefile target names [15:57] lazyPower: yeah that was started at my suggestion :) i'll comment, just wanted to see others' ideas [16:05] gnuoy`, pushed rabbitmq charm up for next branch and merged wolsen's changes [16:05] jamespage, tip top, thanks [16:27] thanks jamespage [16:35] marcoceppi_, hey around? [16:35] jamespage: o/ [16:36] marcoceppi_, sooooo [16:36] mysql charm [16:37] marcoceppi_, how would you feel about putting that under the three month release cycle alongside the openstack charms? [16:37] jamespage: Sounds like a great idea [16:37] I want todo the same with rabbitmq and percona-cluster as well - but I feel os-charmers already has quite a bit of ownership their [16:38] marcoceppi_, OK so we are about to finish up a cycle - 15.01 release is out next week - I suggest that we create the next branch then and switch all merges to the next branch for the 15.04 release [16:39] jamespage: sounds good, if it makes iterating quicker, next branch should live under os-charmers [16:39] jamespage: then just perform merges to ~charmers branch per typical? [16:42] marcoceppi_, that sounds good to me [16:43] marcoceppi_, we need a good way to signal to contributors where they should propose merges against - I'd like that to be the next branch [16:43] marcoceppi_, I thought maybe a README.dev or HACKING.md [16:43] jamespage: either sounds fine, README probably has the most exposure [16:44] marcoceppi_, OK - sounds good to me [16:44] jamespage: how does this problem handle patches for bugs to released version? [16:44] should they still land in /next ? [16:44] s/problem/process/ [16:45] marcoceppi_, next first and then cherry pick to the stable branch [16:45] so that we don't regress on the next release of next [16:46] jamespage: okay, lmk when you've got that setup, we should mail the list on this change so it's documented and reviewers know what's up [16:46] marcoceppi_, ack will do [17:31] tvansteenburgh: on the subject of bundletester, do you have a second to help me debug some weirdness? its failing on a charm for no lint target, yet the makefile has one implicitly [17:32] http://paste.ubuntu.com/9822358/ <-- traceback [17:32] lazyPower: looking [17:32] http://paste.ubuntu.com/9822371/ [17:32] makefile for flannel-docker [17:33] lazyPower: does `make lint` succeed on its own? [17:33] sure does [17:34] http://paste.ubuntu.com/9822406/ [17:34] what about `make -s lint` [17:35] same output [17:36] tvansteenburgh: i think i see the problem, i have a sudo apt-get install python-virtualenv in the venv target, and i bet its hanging on that sudo and failing the test [17:42] lazyPower: i see it's bundle, i wonder if the cwd is wrong at the time lint is called [17:42] possible, is there a debug trace i can spit out that would be helpful? [17:43] -l DEBUG -v [17:43] already doing that :( [17:43] yeah figured [17:44] I'll circle back to this - right now i'm interested in making sure the tests i have in the bundle are passing. Its going to fail in CI though with this. its a consistent result when running bundletester [17:45] lazyPower: i'm occupied at the moment but will take a look as soon as i can [17:45] np, just a heads up really :) [17:45] cheers [17:45] cheers man === kadams54 is now known as kadams54-away === jhobbs_ is now known as jhobbs === Tug_ is now known as ichbinary === mattgrif_ is now known as mattgriffin === zz_CyberJacob is now known as CyberJacob === liam_ is now known as Guest65443 [22:33] whit: https://bugs.launchpad.net/charms/+bug/1413775 [22:33] Bug #1413775: New Charm - Docker [22:33] lazyPower, w00t [22:36] whit: ready for number 2? https://bugs.launchpad.net/charms/+bug/1413776 [22:36] Bug #1413776: New Charm: flannel-docker [22:36] :D [22:40] The final keystone to those charms: https://bugs.launchpad.net/charms/+bug/1413779 [22:40] Bug #1413779: New Bundle: docker-core === CyberJacob is now known as zz_CyberJacob === zz_CyberJacob is now known as CyberJacob