mupBug #1544796 opened: Backup restore fails: upgrade in progress <backup-restore> <blocker> <ci> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1544796>00:45
perrito666sinzui: when did that start?00:53
sinzuiperrito666: in the past hour, and niether master or maas-spaces ever exhibted this00:53
perrito666sinzui: tried another provider?00:55
sinzuiperrito666: I haven't yet00:55
perrito666I believe juju declares "upgrading" while checking for upgrades, if machine is slow this could be the cause00:56
sinzuiperrito666: cherylj: think we lost commits in master!!  Our last success on master, earlyier today points to a commit I don't see in https://github.com/juju/juju/commits/master?page=1, but  http://reports.vapour.ws/releases/3595 does link the the last good version of master.01:02
sinzuinm, fins failure01:03
davecheneycherylj: https://bugs.launchpad.net/juju-core/+bug/1544796 is another manifestation of the issue that you and thumper were talking about yesterday01:04
mupBug #1544796: Backup restore fails: upgrade in progress <backup-restore> <blocker> <ci> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1544796>01:04
davecheneyalmost certainly the same underlying cause as https://bugs.launchpad.net/juju-core/+bug/154336201:05
mupBug #1543362: juju debug-log returns error if run too early in bootstrap <juju-core:Triaged> <https://launchpad.net/bugs/1543362>01:05
perrito666sinzui: eod, if there is anything urgent mail me01:06
sinzuiperrito666: have a good evening01:08
menn0thumper: I'ved replied to your comments for http://reviews.vapour.ws/r/3839/. Can you PTAL?01:25
thumperjust done01:26
menn0thumper: thanks01:26
menn0thumper: another look at http://reviews.vapour.ws/r/3839/ please02:03
davecheneyjuju bootstrap -> https://likelockedrooms.files.wordpress.com/2013/03/mad-as-hell.jpg02:20
thumperdavecheney: take a deep breath, and think to yourself "it is Friday..."02:21
natefinchug, I think my displayport cable died... using HDMI->DVI instead, but it can't push the native res, so everything's fuzzy.  and of course it's my center monitor, so I can't just stop using it.  Feh.02:23
axwanastasiamac: would you be so kind to review http://reviews.vapour.ws/r/3841/ for me?02:26
anastasiamacaxw: of course!02:26
=== natefinch is now known as natefinch-afk
anastasiamacaxw: anything to have a break from fighting import cycle :D02:27
anastasiamacaxw: LGTM02:35
axwanastasiamac: thanks02:36
axwanastasiamac: that range-over-map thing is only ok if there's one element in the map02:36
anastasiamacoh :(02:36
axwanastasiamac: the order is is non-deterministic02:36
anastasiamacbut i can have a break in there \o/02:36
axwanastasiamac: (unless there's only one element, obviously)02:36
axwanastasiamac: sure, just as long as you don't expect a particular order to the range02:37
anastasiamacaxw: awesome \o/02:37
davecheneythumper: it takes 33 minutes to bootstrap02:42
davecheneyi'm using the sydney ec2 datacenter02:42
thumperthat is slow02:43
axwunusually slow, I use ap-southeast-2, never that slow02:45
davecheneyit sits there for minutes at a time squeezing data up to the client02:48
davecheneylucky(~) % ls -lah $(!!)02:49
davecheneyls -lah $(which jujud)02:49
davecheney-rwxrwxr-x 1 dfc dfc 82M Feb 12 13:43 /home/dfc/bin/jujud02:49
davecheneythis probably isn't helping02:49
axwI've got a PR up for the ssh thing, might help?02:49
davecheneyoh, this time it was WAY faster03:00
thumperwatched that mad has hell thing03:01
davecheneythat was 1976, the same year I was born03:03
davecheneycan you tell me it couldn't apply to today ?03:04
thumperok... time to go04:40
thumperhave a good weekend folks04:40
axwanastasiamac: another small one please: http://reviews.vapour.ws/r/3843/04:58
mupBug #1544838 opened: suite.TestPprofStartWithExistingSocketFile unit test failure <ci> <test-failure> <unit-tests> <juju-core:New> <https://launchpad.net/bugs/1544838>06:09
mupBug #1544838 changed: suite.TestPprofStartWithExistingSocketFile unit test failure <ci> <test-failure> <unit-tests> <juju-core:New> <https://launchpad.net/bugs/1544838>06:12
mupBug #1544838 opened: suite.TestPprofStartWithExistingSocketFile unit test failure <ci> <test-failure> <unit-tests> <juju-core:New> <https://launchpad.net/bugs/1544838>06:15
anastasiamacaxw: looking now06:25
mupBug #1544846 opened: restore fails with could not exit restoring status <nil> <backup-restore> <ci> <test-failure> <juju-core:New> <https://launchpad.net/bugs/1544846>06:28
mupBug #1544846 changed: restore fails with could not exit restoring status <nil> <backup-restore> <ci> <test-failure> <juju-core:New> <https://launchpad.net/bugs/1544846>06:37
mupBug #1544846 opened: restore fails with could not exit restoring status <nil> <backup-restore> <ci> <test-failure> <juju-core:New> <https://launchpad.net/bugs/1544846>06:40
mupBug #1544853 opened: unit-test failure MachineSuite.TestManageModelRunsInstancePoller <ci> <intermittent-failure> <test-failure> <unit-tests> <juju-core:New> <https://launchpad.net/bugs/1544853>07:37
mupBug #1544855 opened: unit-test failure ClientOperationSuite.TestCannotExpireUnheldLease <ci> <intermittent-failure> <test-failure> <unit-tests> <juju-core:New> <https://launchpad.net/bugs/1544855>07:37
mupBug #1544890 opened: "ERROR the name of the model must be specified" when 'juju init' required <juju-core:New> <https://launchpad.net/bugs/1544890>09:43
frobwarevoidspace, dooferlad: might miss standup/planning. helping out with customer issue and otp atm09:49
voidspacefrobware: ok09:51
voidspacedooferlad: my parents are paying a surprise visit (driving past on their way up north)09:57
voidspacedooferlad: so we can have a short standup09:58
dooferladvoidspace: am in the hangout now10:02
voidspacecherylj: ping10:51
voidspacedooferlad: gah, gomaasapi test server *does* support spaces endpoint13:08
voidspacedooferlad: so long as you've registered some spaces...13:08
voidspacedooferlad: if there aren't any spaces registered it pretends not to support it to mimic older versions of maas13:08
voidspacedooferlad: and my tests don't register any spaces13:08
voidspacedooferlad: well, the preexisting tests don't - because they didn't need to13:08
voidspaceah well, less work13:09
voidspacedooferlad: cherylj merged maas-spaces yesterday by the way13:11
frobwaredooferlad, ping13:15
voidspacedooferlad: hmm... not convinced there is a way to populate spaces now, may still need to implement it13:20
dooferladfrobware: hi13:20
frobwaredooferlad, see email. sorry! :)13:23
voidspacedooferlad: looks like the spaces stuff is untested and there's no way to add a space! Probably because you started implementing it and then we decided we didn't need that endpoint after all13:24
dooferladvoidspace: sounds about right13:24
voidspaceWe were doing everything space related through the subnets endpoints13:24
voidspaceAh well, so I need to add a new test server method for adding spaces and some tests.13:25
dooferladvoidspace: I hope it is at least clear code and won't take long to do.13:26
cheryljvoidspace: pong13:30
voidspacecherylj: I wanted to ask about maas-spaces13:30
voidspacecherylj: but I see you merged it last night13:30
voidspacecherylj: \o/13:30
cheryljah, yes :)13:31
dooferladfrobware: bug #1543770 is a bit light on details. Doesn't help that the network tests are spitting out 'The old local provider is not supported by 2.0-alpha2' and saying they passed!13:31
mupBug #1543770: Juju 2.0alpha1 does not assign a proper netmask for LXC containers <cpe-critsit> <cpe-sa> <dhcp> <lxc> <maas> <network> <juju-core:Triaged> <https://launchpad.net/bugs/1543770>13:31
frobwaredooferlad, you read what I read. :)13:31
frobwaredooferlad, this is in alpah1 - not sure whether we should say use beta1.13:32
frobwaredooferlad, but /32 seems the right netmask to me13:32
dooferladfrobware: Yea, it is fine.13:32
frobwaredooferlad, otp13:32
dooferladfrobware: sure.13:32
cheryljfrobware, dooferlad, if it's not clear what the issue is in the bug, definitely press for more details13:33
frobwarevoidspace, http://pastebin.ubuntu.com/15024080/13:41
voidspacefrobware: thanks13:44
dooferladfrobware, cherylj: Just so you know, I would expect container networking to work in the beta if it was this build: http://reports.vapour.ws/releases/3595/job/functional-container-networking/attempt/17013:47
dooferladi.e. the maas-spaces branch being merged in13:48
* voidspace lunches13:57
cheryljdooferlad: so, it's expected that it doesn't work in alpha1?14:20
=== cherylj_ is now known as cherylj
frobwarecherylj, not sure about that. I'm sure I tried alpha1 this morning and it was OK. but I got sidetracked with the other issue...14:41
dooferladcherylj: http://reports.vapour.ws/releases/3525 didn't run the container networking tests, so I don't know if it would have worked or not.14:48
cheryljok, thanks14:49
katcocherylj: sinzui: what do i need to do to bootstrap a beta1 controller? i'm setting the agent-metadata-url to "https://streams.canonical.com/juju/tools" and agent-stream to "devel". no bueno15:23
sinzuikatco: beta1 is not released. use --upload-tools or publish your own streams15:24
katcok ty15:25
mupBug #1544847 opened: unit-test failure: configSuite.TestNewModelConfig test failure <ci> <regression> <test-failure> <unit-tests> <juju-core:Incomplete> <juju-core lxd-container-type:Triaged> <https://launchpad.net/bugs/1544847>15:32
mupBug #1544849 opened: unit-test loop with juju.worker.uniter.remotestate retry hook timer triggered <ci> <intermittent-failure> <ppc64el> <unit-tests> <juju-core:Incomplete> <juju-core maas-spaces:Triaged> <https://launchpad.net/bugs/1544849>15:32
mupBug #1544850 opened: unit-test failure: cloudImageMetadataSuite.TestFindMetadata <ci> <intermittent-failure> <test-failure> <unit-tests> <juju-core:Incomplete> <juju-core upgrade-mongodb3:Triaged> <https://launchpad.net/bugs/1544850>15:32
mupBug #1544847 changed: unit-test failure: configSuite.TestNewModelConfig test failure <ci> <regression> <test-failure> <unit-tests> <juju-core:Incomplete> <juju-core lxd-container-type:Triaged> <https://launchpad.net/bugs/1544847>15:35
mupBug #1544849 changed: unit-test loop with juju.worker.uniter.remotestate retry hook timer triggered <ci> <intermittent-failure> <ppc64el> <unit-tests> <juju-core:Incomplete> <juju-core maas-spaces:Triaged> <https://launchpad.net/bugs/1544849>15:35
mupBug #1544850 changed: unit-test failure: cloudImageMetadataSuite.TestFindMetadata <ci> <intermittent-failure> <test-failure> <unit-tests> <juju-core:Incomplete> <juju-core upgrade-mongodb3:Triaged> <https://launchpad.net/bugs/1544850>15:35
mupBug #1544847 opened: unit-test failure: configSuite.TestNewModelConfig test failure <ci> <regression> <test-failure> <unit-tests> <juju-core:Incomplete> <juju-core lxd-container-type:Triaged> <https://launchpad.net/bugs/1544847>15:44
mupBug #1544849 opened: unit-test loop with juju.worker.uniter.remotestate retry hook timer triggered <ci> <intermittent-failure> <ppc64el> <unit-tests> <juju-core:Incomplete> <juju-core maas-spaces:Triaged> <https://launchpad.net/bugs/1544849>15:44
mupBug #1544850 opened: unit-test failure: cloudImageMetadataSuite.TestFindMetadata <ci> <intermittent-failure> <test-failure> <unit-tests> <juju-core:Incomplete> <juju-core upgrade-mongodb3:Triaged> <https://launchpad.net/bugs/1544850>15:44
mupBug #1545040 opened: TestLoginsDuringUpgrade fails on go1.5/6 <ci> <gccgo> <go1.5> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1545040>15:50
mupBug #1545045 opened: TestNotAllContainersAreDeleted: can't get info for image <ci> <lxd> <regression> <juju-core:Incomplete> <juju-core lxd-container-type:Triaged> <https://launchpad.net/bugs/1545045>15:50
mupBug #1545046 opened: TestNewContainerManage executed but not supported by gccgo-go <ci> <gccgo> <ppc64el> <regression> <test-failure> <juju-core:Incomplete> <juju-core lxd-container-type:Triaged> <https://launchpad.net/bugs/1545046>15:50
mupBug #1545040 changed: TestLoginsDuringUpgrade fails on go1.5/6 <ci> <gccgo> <go1.5> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1545040>15:53
mupBug #1545045 changed: TestNotAllContainersAreDeleted: can't get info for image <ci> <lxd> <regression> <juju-core:Incomplete> <juju-core lxd-container-type:Triaged> <https://launchpad.net/bugs/1545045>15:53
mupBug #1545046 changed: TestNewContainerManage executed but not supported by gccgo-go <ci> <gccgo> <ppc64el> <regression> <test-failure> <juju-core:Incomplete> <juju-core lxd-container-type:Triaged> <https://launchpad.net/bugs/1545046>15:53
mupBug #1545040 opened: TestLoginsDuringUpgrade fails on go1.5/6 <ci> <gccgo> <go1.5> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1545040>15:59
mupBug #1545045 opened: TestNotAllContainersAreDeleted: can't get info for image <ci> <lxd> <regression> <juju-core:Incomplete> <juju-core lxd-container-type:Triaged> <https://launchpad.net/bugs/1545045>15:59
mupBug #1545046 opened: TestNewContainerManage executed but not supported by gccgo-go <ci> <gccgo> <ppc64el> <regression> <test-failure> <juju-core:Incomplete> <juju-core lxd-container-type:Triaged> <https://launchpad.net/bugs/1545046>15:59
mupBug #1545050 opened: TestSubordinateDying is not dying <ci> <intermittent-failure> <ppc64el> <juju-core:Triaged> <https://launchpad.net/bugs/1545050>16:05
mupBug #1545055 opened: TestManageModelRunsUndertaker timed out <ci> <intermittent-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1545055>16:05
mupBug #1545057 opened: TestWorkerDiscoversSpaces no subnets found <ci> <go1.5> <intermittent-failure> <race-condition> <juju-core:Triaged> <https://launchpad.net/bugs/1545057>16:05
cheryljhey tych0!  Looks like we got on run on your branch and the results are in!  The bugs opened are here: https://bugs.launchpad.net/juju-core/lxd-container-type16:12
natefinchkatco, ericsnow: tests added, tweaks made, rebase successful with minimal problems... code is merging16:24
katconatefinch: rock!16:24
ericsnownatefinch: great!16:24
katconatefinch: we're still in moonstone16:24
natefinchkatco: ok, coming16:25
dooferladfrobware, voidspace: calling it a day. It has been a long week and thinking straight has become an issue!16:27
frobwaredooferlad, did you come to any conclusion on the netmask bug?16:28
dooferladfrobware: only that I need more information.16:28
frobwaredooferlad, did you ask in the bug?16:29
dooferladfrobware: yes16:29
frobwaredooferlad, ah...sorry I see it now.16:29
voidspacenatefinch: question - if I want to test a synchronous function that may deadlock (block) what's the right way to test it without blocking the test16:29
voidspacenatefinch: just fire it off on a goroutine with a signal method and wait for a LongAttempt for the signal?16:30
voidspaceShortAttempt would do actually16:30
voidspacegiven that my current synchronous test - without the fix in place - hasn't returned after about five minutes16:30
voidspaceI think I can safely say I've found the deadlock...16:31
natefinchvoidspace: leaving dead goroutines hanging around in your tests is bad, but I guess as long as that's the failure condition, I guess that's ok16:32
voidspacenatefinch: yeah, it shouldn't fail!16:32
natefinchvoidspace: yeah, a simple goroutine that sends on a channel when it's finished and then you can do a select on that channel and time.After(shortwait)16:33
katcosinzui: cherylj: hey, i aborted a merge job w/o thinking... will that leave cruft around?16:48
sinzuikatco: thanks for pinging me I will check for an instance16:48
katcosinzui: sorry =|16:48
sinzuikatco: I have done the same16:50
katcosinzui: can natefinch do another $$merge$$ in the meantime?16:59
voidspacenope, no way to test without a failing deadlock - the call that actually deadlocks does asserts so can't be on a different goroutine17:01
voidspaceat least a deadlocking test will tell us something is wrong17:01
voidspacehmmm... we shouldn't be deadlocked, it should timeout after LongAttempt17:03
voidspacedammit, the test is nonsense17:05
voidspacebut it shouldn't pass17:05
voidspaceand it does17:05
cheryljkatco: are there any other commits coming for your resources branch?17:13
katcocherylj: we're just tryinf to land the 1 more now17:14
katcocherylj: but we received a time-out and that's when i aborted the job17:14
katcocherylj: trying to re-$$merge$$ but natefinch says the bot isn't picking it up yet17:14
sinzuiperrito666: Your upgrade-mongo3 branch needs the latest master for CI to test. There is no rush. CI will be starting a test of the cloud-credentials branch first17:18
frobwareinteresting! - https://medium.com/vijay-pandurangan/linux-kernel-bug-delivers-corrupt-tcp-ip-data-to-mesos-kubernetes-docker-containers-4986f88f7a19#.ojo3f9ww317:28
natefinchsinzui: can you help my branch? I think katco aborting the merge meant that it won't pick up me re-$$merge$$ing it17:29
natefinchsinzui: https://github.com/juju/juju/pull/437417:29
sinzuinatefinch: oh. I will attempt a delete of the aborted job17:30
sinzuinatefinch: I will check back in 5 minutes to see if it is accepted17:30
sinzuikatco: natefinch: the only reason feature-resouces didn't get a bless from CI is that it has a regression from master.17:32
sinzuinatefinch: I have a cunning plan to hand type the aborted build into jenkins to run the tests and hopefully convice the lander to send to the results back to the PR.17:35
voidspacefrobware: http://reviews.vapour.ws/r/3848/17:37
katcosinzui: nice! we still need to run ci 1 more time with the branch natefinch is trying to land17:38
katcosinzui: tbh i'd be fine merging w/o a bless because it's just a new command-flag17:39
frobwarevoidspace, otp17:39
voidspacefrobware: ok17:39
frobwarevoidspace, so the first part of that diff is what we were trying yesterday?17:41
voidspacefrobware: yes, I got bogged down trying to construct a test17:47
voidspacefrobware: in the end I concluded it was already tested and the existing tests pass17:47
=== akhavr1 is now known as akhavr
katcocherylj: ok, the feature-resources branch is ready for another ci run18:06
katcocherylj: or if you're ok with it, we can just merge into master. only patch not tested is a new command flag18:07
* cherylj looks18:09
sinzuikatco: natefinch: the aborted merge is now merged. It is okay to abort, but if we do want to merge, we can use the rebuild link on the aborted job to try again.18:10
katcosinzui: tyvm18:10
katcocherylj: here's the diff to help you make the call: https://github.com/juju/juju/commit/f0e1848aca595b35d6483f75a909c38b204eee5a18:11
cheryljsinzui: did you want to prepare the PR to merge their branch?18:15
katcocherylj: sinzui: i can do it if you like; it's just a few clicks18:16
sinzuicherylj: I will do it and explain the two faiures are from the master.18:16
katcosinzui: cherylj: great, cheers to both of you :)18:17
cheryljkatco: thanks to you and your team for pulling off this amazing feat!18:17
cheryljkatco: now can someone look at the restore failures being seen on master?  :)18:17
katcocherylj: surely you jest! ;)18:17
katcocherylj: this doesn't mean the feature is done lol18:18
cheryljheh, well I can hope right?  I mean, we do need it fixed to ship beta118:19
perrito666sinzui: ok, ill merge it18:25
sinzuicherylj: http://reviews.vapour.ws/r/3849/18:26
lazyPowercherylj - question for you regarding https://bugs.launchpad.net/juju-core/+bug/1535165 - is this fix present in 2.0-alpha1?18:48
mupBug #1535165: Unable to create hosted models with MAAS provider <juju-release-support> <maas-provider> <juju-core:Fix Released by waigani> <https://launchpad.net/bugs/1535165>18:48
cheryljlazyPower: no, just alpha218:49
lazyPowerits tagged alpha2 - but i've got fingers crossed18:49
lazyPowerwah wahhhh18:49
lazyPowerok :D thanks for confirmation18:49
cheryljsorry :(18:49
cheryljnp :)18:49
lazyPowernot even upset :D i'll be patient18:49
lazyPoweror i'll build a container w/ nightly18:49
lazyPowereither way18:49
rick_h__lazyPower: alpha2 is out though?18:54
rick_h__lazyPower: /me is missing the wah wahhhhh18:54
lazyPowerrick_h__ - wait it is?18:54
* lazyPower pulls latest charmbox:devel18:54
rick_h__lazyPower: https://launchpad.net/~juju/+archive/ubuntu/devel18:55
lazyPowerwoo hot diggity dog, i'm behind the times18:55
rick_h__lazyPower: turn that frown upside down18:56
rick_h__and run along the razor's edge18:56
katcoericsnow: natefinch: babam https://github.com/juju/juju/pull/440818:56
ericsnowkatco: sweet!18:58
lazyPowerkatco great success!18:58
lazyPowerdevops borat approves of this PR18:58
rick_h__katco: natefinch ericsnow <318:58
rick_h__katco: natefinch ericsnow looking forward to demo time18:59
lazyPowerrick_h__ you beautiful man you - that release snuck by me, and was available in the latest devel image. man i love automation18:59
katcorick_h__: demo/status update to follow18:59
katcoericsnow: natefinch: i'm just in moonstone w/e you're ready18:59
lazyPowerkatco can i be a fly on the wall?19:00
katcolazyPower: for?19:00
lazyPowerdemo / status19:00
katcolazyPower: you want to watch the demo you mean?19:00
lazyPoweryes :D19:01
katcolazyPower: sure i'll ping you when we're recording19:01
mupBug #1545116 opened: When I run "juju resources <service>" after a service is destroyed, resources are still listed. <resources> <juju-core:Confirmed> <https://launchpad.net/bugs/1545116>19:18
mupBug #1545126 opened: juju/maas do not create ptr reccords for bare metal servers with multiple networks <juju-core:New> <https://launchpad.net/bugs/1545126>19:51
mupBug #1545126 changed: juju/maas do not create ptr reccords for bare metal servers with multiple networks <juju-core:New> <https://launchpad.net/bugs/1545126>19:54
mupBug #1545126 opened: juju/maas do not create ptr reccords for bare metal servers with multiple networks <juju-core:New> <https://launchpad.net/bugs/1545126>19:57
lazyPoweromg relations in tabular status? you really DO love us! <320:24
perrito666lazyPower: :)20:28
lazyPowerperrito666 best valentines day gift ever20:28
perrito666lazyPower: I am romantic like that20:28
katcofor anyone who's interested, going to be demoing resources here in a bit: http://youtu.be/SS3AQO3ZN9Y20:37
TheMue did I miss something?20:38
marcoceppiericsnow:  list-resources --details is awesome21:21
marcoceppiI like that you all took into consideration resource delivery mismatch21:21
ericsnowmarcoceppi: glad you noticed :)21:22
marcoceppiericsnow: is there a resource-updated hook?21:22
ericsnowmarcoceppi: definitely something we could have easily missed21:22
ericsnowmarcoceppi: nope21:22
marcoceppiso we have to use update-status to check if a new resources is available?21:22
ericsnowmarcoceppi: we're using upgrade-charm21:22
marcoceppioh, okay21:22
ericsnowmarcoceppi: (the hoook)21:22
marcoceppiso an upload-resource call will invoke an upgrade-charm event?21:23
ericsnowmarcoceppi: yeah, both "juju push-resource" and "juju upgrade-charm"21:24
marcoceppiinteresting. is there a way to tell what verion of a resource I have in a charm without running resource-get?21:24
rick_h__marcoceppi: e.g. if you publish a new combo of charm revision, resource revision, etc in the charmstore. Upgrade charm will get triggered for all of them since they're published as one working set21:24
marcoceppiI guess upgrade-charm would basically just trigger an "upgrade"21:25
ericsnowmarcoceppi: juju charm list-resources <charm>21:25
marcoceppiericsnow: from within the charm21:25
ericsnowmarcoceppi: not really21:25
ericsnowmarcoceppi: you either have the one of the controller or you don't (and resource-get fixes that)21:26
rick_h__ericsnow: it is interseting in that I don't want to rerun the code that comes after a resource-get if that resource hasn't been updated21:26
ericsnowmarcoceppi: there is no concept of multiple revisions of the same resource (for a given service) on the controller21:26
rick_h__ericsnow: we'll have to think of how to tell resource-get it's not changed ?21:27
ericsnowmarcoceppi: it's binary21:27
marcoceppiericsnow: well, there is implicitly, if a unit needs to know that it needs to do somethign because it has a new resource21:27
ericsnowrick_h__: good point21:27
ericsnowrick_h__: I suppose you could compare checksums21:27
marcoceppisomething like resource-list inside a hook21:28
marcoceppior resource-get --checksum21:28
rick_h__marcoceppi: I think as it stands it reruns and expects the charms to be idempotent, but you're right we should enable an effeciency bump there21:28
ericsnowrick_h__: but having juju do that for the charm may be good21:28
rick_h__ericsnow: right, the charm author may want to rerun, we should enable them to handle it how they wish21:28
marcoceppithat way a charm could just track the checksum it's got21:28
rick_h__ericsnow: can you take that feedback back to the team please?21:29
ericsnowrick_h__: will do21:29
rick_h__ty and ty for the feedback marcoceppi, good stuff21:30
ericsnowrick_h__, marcoceppi: +10021:30
marcoceppilove it so far, compiling from master now to update a few charms21:49
perrito666weeee I did it, I didi it, I finally removed the status duplication :D22:12
perrito666just took me 3 days :p22:12
* perrito666 dances22:12
marcoceppihey party people22:34
marcoceppianyone around to answer a quick question about the new juju deploy in 2.0?>22:34
marcoceppiI guess it is pretty late22:39
perrito666what is juju romulus??22:52
rick_h__marcoceppi: maybe?22:53
mupBug #1545196 opened: Juju claims AWS ap-northeast-2 not found <ec2-provider> <juju-core:Incomplete> <juju-core cloud-credentials:Triaged> <https://launchpad.net/bugs/1545196>23:33
mupBug #1545196 changed: Juju claims AWS ap-northeast-2 not found <ec2-provider> <juju-core:Incomplete> <juju-core cloud-credentials:Triaged> <https://launchpad.net/bugs/1545196>23:36
mupBug #1545196 opened: Juju claims AWS ap-northeast-2 not found <ec2-provider> <juju-core:Incomplete> <juju-core cloud-credentials:Triaged> <https://launchpad.net/bugs/1545196>23:45

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