=== scuttlemonkey is now known as scuttle|afk
bdxAre there any plans for an official trove charm?00:08
bdx: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.00:11
=== kadams54-away is now known as kadams54
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
lazyPowermarcoceppi_: i just had a thought - and it might be completely ludacris.. but what if we had a pattern as follows02:06
=== TheRealMue is now known as TheMue
marcoceppi_lazyPower: go on02:06
lazyPowerif 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 tools02:07
lazyPoweri 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
lazyPower(and those arch targets are respective to what environment i'm deploying to - as this is a golang bin artifact thats produced)02:08
marcoceppi_lazyPower: how quickly could you create a container?02:08
marcoceppi_seems like a good idea, but only if you could prevent having to spin up a build container for each unit02:09
lazyPowerDepends, am i fetching a bin image from dockerhub or am i fetching a cloud image and using LXC02:09
lazyPowerI was considering shipping a dockerfile with a base ubuntu 14.04 image to run the trial on this02:09
lazyPoweras flannel-docker wont be deployed to a non-docker host. that much is specific in the relationship02:10
lazyPoweri mean, you can co-lo it on one, but it noops02:10
lazyPowerI'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 board02:14
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
marcoceppi_lazyPower: you still around?03:50
=== kadams54 is now known as kadams54-away
=== zz_CyberJacob is now known as CyberJacob
jamespagebdx, no plans for a trove charm from my team08:07
=== cmars` is now known as cmars
=== CyberJacob is now known as zz_CyberJacob
=== scuttle|afk is now known as scuttlemonkey
lazyPowermarcoceppi_: back now14:02
=== smoser_ is now known as smoser
lazyPowertvansteenburgh: 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 times15:52
lazyPowertvansteenburgh: might want to poke your head in and take a look and give a quick reply on behavior here. Thread name is: Makefile target names15:52
tvansteenburghlazyPower: yeah that was started at my suggestion :) i'll comment, just wanted to see others' ideas15:57
jamespagegnuoy`, pushed rabbitmq charm up for next branch and merged wolsen's changes16:05
gnuoy`jamespage, tip top, thanks16:05
wolsenthanks jamespage16:27
jamespagemarcoceppi_, hey around?16:35
marcoceppi_jamespage: o/16:35
jamespagemarcoceppi_, sooooo16:36
jamespagemysql charm16:36
jamespagemarcoceppi_, how would you feel about putting that under the three month release cycle alongside the openstack charms?16:37
marcoceppi_jamespage: Sounds like a great idea16:37
jamespageI want todo the same with rabbitmq and percona-cluster as well - but I feel os-charmers already has quite a bit of ownership their16:37
jamespagemarcoceppi_, 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 release16:38
marcoceppi_jamespage: sounds good, if it makes iterating quicker, next branch should live under os-charmers16:39
marcoceppi_jamespage: then just perform merges to ~charmers branch per typical?16:39
jamespagemarcoceppi_, that sounds good to me16:42
jamespagemarcoceppi_, we need a good way to signal to contributors where they should propose merges against - I'd like that to be the next branch16:43
jamespagemarcoceppi_, I thought maybe  a README.dev or HACKING.md16:43
marcoceppi_jamespage: either sounds fine, README probably has the most exposure16:43
jamespagemarcoceppi_, OK - sounds good to me16:44
marcoceppi_jamespage: how does this problem handle patches for bugs to released version?16:44
marcoceppi_should they still land in /next ?16:44
jamespagemarcoceppi_, next first and then cherry pick to the stable branch16:45
jamespageso that we don't regress on the next release of next16:45
marcoceppi_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 up16:46
jamespagemarcoceppi_, ack will do16:46
lazyPowertvansteenburgh: 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 implicitly17:31
lazyPowerhttp://paste.ubuntu.com/9822358/ <-- traceback17:32
tvansteenburghlazyPower: looking17:32
lazyPowermakefile for flannel-docker17:32
tvansteenburghlazyPower: does `make lint` succeed on its own?17:33
lazyPowersure does17:33
tvansteenburghwhat about `make -s lint`17:34
lazyPowersame output17:35
lazyPowertvansteenburgh: 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 test17:36
tvansteenburghlazyPower: i see it's bundle, i wonder if the cwd is wrong at the time lint is called17:42
lazyPowerpossible, is there a debug trace i can spit out that would be helpful?17:42
tvansteenburgh-l DEBUG -v17:43
lazyPoweralready doing that :(17:43
tvansteenburghyeah figured17:43
lazyPowerI'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 bundletester17:44
tvansteenburghlazyPower: i'm occupied at the moment but will take a look as soon as i can17:45
lazyPowernp, just a heads up really :)17:45
tvansteenburghcheers man17:45
=== 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
lazyPowerwhit: https://bugs.launchpad.net/charms/+bug/141377522:33
mupBug #1413775: New Charm - Docker <Juju Charms Collection:New> <https://launchpad.net/bugs/1413775>22:33
whitlazyPower, w00t22:33
lazyPowerwhit: ready for number 2?   https://bugs.launchpad.net/charms/+bug/141377622:36
mupBug #1413776: New Charm: flannel-docker <Juju Charms Collection:New> <https://launchpad.net/bugs/1413776>22:36
lazyPowerThe final keystone to those charms: https://bugs.launchpad.net/charms/+bug/141377922:40
mupBug #1413779: New Bundle: docker-core <Juju Charms Collection:New> <https://launchpad.net/bugs/1413779>22:40
=== CyberJacob is now known as zz_CyberJacob
=== zz_CyberJacob is now known as CyberJacob

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