/srv/irclogs.ubuntu.com/2015/05/14/#juju.txt

=== wgrant_ is now known as wgrant
=== ahasenac` is now known as ahasenack
rick_h_lazyPower: hey there00:44
lazyPowero/00:44
lazyPowerrick_h_: pong00:44
rick_h_lazyPower: ty email away :)00:55
lazyPowerjrwren: ping - just got a big MP from foli w/ nagios bits targeted at my namespace charm of logstash02:16
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
blahdeblahAny charmers stil awake?  aisrael tells me that as long as "python tests/20-mytest" runs, then any test code should work.  But 20-mytest relies on python modules elsewhere in the charm tree; what's the correct method for including it in the python module path?04:39
=== kadams54 is now known as kadams54-away
marcoceppiblahdeblah: still around?11:06
blahdeblahmarcoceppi: Sort of; past EOD & dealing with a broken machine at the moment11:10
marcoceppiyou can import sys and patch the pythonpath at the top of the test file if you're unable to import it by normal means11:11
blahdeblahmarcoceppi: Yeah - found that in the latest unit_tests template and used that in my unit_tests.11:12
blahdeblahDo we have any documentation about the preferred best practice for unit tests at present?11:13
marcoceppiah, I figured 7 hours of searching must have yeilded something, sorry we couldn't get you an answer sooner11:13
marcoceppiblahdeblah: not entirely, no11:13
blahdeblahnp - I know I'm on the wrong side of the planet. :-)11:13
marcoceppihas anyone run into an issue with local provider and 1.24?12:05
=== beuno_ is now known as beuno
aisraelmarcoceppi: The only problem I had was it wasn't a clean upgrade. I had to destroy and bootstrap my env12:54
aisrael(1.24-beta1)12:54
aisraelblahdeblah: Glad you found a solution!12:55
=== msbrown-afk is now known as msbrown
aisraelThe upgrade from 1.24-beta1 to beta2 went smooth13:00
aisraelANd we have service-status and workload-status!13:00
lazyPowerwoot14:06
=== ericsnow is now known as ericsnow_afk
=== kwmonroe_ is now known as kwmonroe
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
=== ericsnow_afk is now known as ericsnow
=== scuttlemonkey is now known as scuttle|afk
jose'ello guys, having some troubles over here15:24
jose`juju bootstrap --constraints "cpu-power=0 mem=512M"` is trying to launch a t2.micro instead of a t1.micro15:24
joseany idea why?15:25
jrwren"The t1.micro is a previous generation instance and it has been replaced by the t2.micro"15:28
jrwrenhttp://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts_micro_instances.html15:29
josejrwren: I've continued using t1.micro instances because they suit me for charming, has the core team decided to deprecate them?15:33
joset1.micros can still be launched from the aws console and everything15:34
stokachusinzui: have you guys noticed issues with juju trying to create vivid containers?16:17
* sinzui gets bug16:17
sinzuistokachu, bug 1442308 is our nemesis16:18
mupBug #1442308: Juju cannot create vivid containers <ci> <local-provider> <lxc> <ubuntu-engineering> <vivid> <juju-core:Triaged by cherylj> <juju-core 1.24:Triaged by cherylj> <https://launchpad.net/bugs/1442308>16:18
stokachusinzui: thanks!16:18
sinzuistokachu, in the details of the bug, I think we see that the container logic is using upstart :(16:18
* sinzui high fixes Core for getting every branch blessed16:20
sinzuihi ses16:43
sinzuiI can discuss compatibility tests now16:43
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
lukasaQuick question: what's the incantation for deploying the /next branch of a charm?17:31
lukasaOr do I have to check it out in bzr and deploy it locally?17:31
marcoceppilukasa: the latter17:32
lukasaOk. =)17:33
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
=== kadams54 is now known as kadams54-away
=== kadams54 is now known as kadams54-away
=== kadams54 is now known as kadams54-away

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