[00:11] <thumper> wallyworld_: want to have a quick catch up chat?
[00:11] <wallyworld_> thumper: sure, meet in our 1:1
[00:11] <thumper> k
[01:42] <thumper> anyone? http://reviews.vapour.ws/r/676/
[02:04] <axw> wallyworld_: just want some clarification on the change. AllowsSecureConnection indicates that there's a CA private key on the state servers, which allows them to generate valid certificates. without it, the certs may not have valid addresses and so the LXC code will not be told to fetch images from the API server
[02:04] <axw> instead it'll go directly to the external source
[02:04] <axw> is that right?
[02:05] <wallyworld_> axw: yes, correct
[02:29] <menn0> thumper: looking
[02:38] <menn0> thumper: done
[02:38] <thumper> ta
[02:39] <rick_h_> thumper: got a sec to chat?
[02:39] <thumper> rick_h_: sure, why not
[02:39] <rick_h_> :)
[02:40] <rick_h_> thumper:
[02:40] <rick_h_> https://plus.google.com/hangouts/_/canonical.com/daily-standup?authuser=1
[02:43] <thumper> rick_h_: you've stopped moving and making noise
[03:03] <wallyworld_> thumper: if you have a moment, here's a small, simple review http://reviews.vapour.ws/r/677/
[03:04] <thumper> wallyworld_: ship it
[03:04] <wallyworld_> ty
[03:34] <thumper> wallyworld_: is there an example somewhere in a test (and real code) of checking for the existance of tools for a particular version?
[03:34] <thumper> wallyworld_: I think the upgrade-juju command does it somewhere
[03:34] <wallyworld_> thumper: you mean seeing if the tarball exists?
[03:35] <thumper> wallyworld_: well how about I tell you what I want to do
[03:35] <wallyworld_> ok
[03:35] <thumper> wallyworld_: and you can tell me the easiest way to do it?
[03:35] <thumper> when someone says "create-environment" we want the version to default to the client version, but they should be able to specify a version to use when creating
[03:36] <thumper> the api server needs to check for tool availability
[03:36] <thumper> for created environments, we can't really support upload-tools
[03:36] <thumper> nor do I think we should
[03:36] <wallyworld_> thumper: i could be wrong, but i thought we were heading towards enforcing the same version as the client is used
[03:37] <thumper> also, we need to make sure the requested version is <= current version of the server
[03:37] <thumper> wallyworld_: for bootstrap yes
[03:37] <wallyworld_> since we have run into incompatibility issues even with minor version differences
[03:37] <thumper> wallyworld_: for 'juju create-environment' not necessarily
[03:37] <wallyworld_> ok
[03:37] <thumper> anyway
[03:37] <thumper> the client's juju version may well be different to the api server they are connecting to
[03:37] <thumper> so we need to pass an agent-version through
[03:38] <thumper> the api server then needs to check against its version, and also for tool availability
[03:38] <thumper> so two things:
[03:38] <thumper> best way to have the apiserver check
[03:38] <thumper> and
[03:38] <thumper> best way to test it (i.e. fake the tools that it thinks are available)
[03:39] <wallyworld_> so there's an apiserver ToolsFinder from memory
[03:40] <wallyworld_> i'll need to dig to find some examples, give me a sec
[03:43] <wallyworld_> thumper: if you look at line 53 in apiserver/client/machineconfig.go, you can see how you can set up to ask the tools finder for tools either matching a specific version, or major/minor match
[03:45] <axw> wallyworld_: fyi I have updated https://github.com/juju/charm/pull/77, I just need to get fwereade to PTAL since he already started reviewing
[03:45] <wallyworld_> in terms of testing, i think there's some stuff in apiserver/common/tools_test.go
[03:45] <thumper> wallyworld_: thanks
[03:45] <wallyworld_> axw: sure, ty, sounds good
[03:46] <wallyworld_> thumper: have a look, and if you need some more info, let me know; i think i've given you what you need, but ask if nt
[03:46] <thumper> cheers
[03:46] <thumper> my kids are starting to go ferel
[03:46] <thumper> ferrel?
[03:46] <thumper> anyway, screaming and fighting
[03:46] <wallyworld_> will ferrel?
[03:46] <thumper> they haven't gotten out today
[03:47] <thumper> feral
[03:47] <wallyworld_> the dog has i bet
[03:47] <thumper> nope
[03:47] <thumper> well, not for a walk
[03:47] <wallyworld_> she would be feral also then
[03:48] <thumper> hmm...
[03:48] <thumper> series...
[03:49] <thumper> I don't have a series...
[03:49] <thumper> actually I have a default-series
[03:50] <thumper> hmm... seems I can leave it blank
[04:25] <thumper> wallyworld_: is there an easy way to get a list of all the tools available?
[04:26] <wallyworld_> thumper: from memory, pass in a search params with major = minor = -1, and empty arch, series etc
[04:26] <thumper> hmm...
[04:26] <wallyworld_> but you'd normally want to filter on arch, series
[04:26] <wallyworld_> or arch at least
[04:26] <thumper> well, when we create an environment, we don't have an arch
[04:26] <thumper> as we aren't actually creating any machines
[04:27] <wallyworld_> there's no current use case apart from possibly sync tools where you need a "find all tools"
[04:27] <thumper> however we do want to use to know that there are some tools available
[04:27] <thumper> so... situation is:
[04:27] <thumper> user says create-environment --version x.y.z
[04:27] <thumper> we check and go "hmm, no tools for that version, but we do have [a,b,c,d]"
[04:28] <wallyworld_> yeah, the api doesn't work like that. you currently ask for version x.y.z and get that or nothing
[04:28] <thumper> hmm...
[04:28] <thumper> bugger
[04:28] <wallyworld_> or you can ask for all tools matching major/minor version
[04:29] <wallyworld_> of with -1 for major, minor, you get everything
[04:29] <wallyworld_> or
[04:29] <wallyworld_> and you then need to iterate the list of tools you get back to see if the version you want is there
[04:30]  * thumper hmmmms
[04:30] <thumper> I'm going to think about it over night and come back to it.
[04:30] <thumper> cheers
[04:30] <wallyworld_> ok
[04:30] <wallyworld_> we can improve the api if needed
[04:31] <wallyworld_> it fits current use cases
[04:34]  * thumper nods
[04:34] <thumper> night all
[05:56] <axw> jam: when discussing storage, did you and sabdfl talk about fallback at all? the updated spec doesn't really work with fallback in mind at all AFAICT. e.g. if you specify --storage, the spec says the pool used is the default pool, rather than any pool that will satisfy
[07:53] <jam> axw: sorry about the delay, are you still around?
[07:54] <axw> jam: hiya, yes, I am
[07:57] <jam> axw: so I believe the "default" source in MaaS was local disk (block devices coming from loop mounts, non-specified sizes just coming from /)
[08:00] <axw> jam: ok. so we're back to no notion of degrading; the user just has to be explicit if they want something better than loop-back, and if that fails then they need to try again with something else?
[08:00] <axw> *automatic degrading
[08:00] <jam> axw: I believe the spec mentioned  being able to change the default source for an environment, but otherwise yes
[08:01] <axw> jam: thanks
[08:01] <jam> axw: I hope you had good holidays
[08:01] <jam> welcome back
[08:02] <axw> jam: pretty relaxing, thanks. and you?
[08:02] <jam> axw: quite nice. Got to go visit family in Germany. And while we didn't get proper snow, it was at least cold for new years :)
[08:02] <jam> I guess that isn't how you feel about NY
[08:02] <axw> ah nice :)
[08:02] <axw> not in the slightest ;)
[08:03] <axw> I've been in the pool every day for at least the last week
[08:03] <jam> axw: I remember martin pool mentioning that to him Christmas was Mai Tai's on the beach
[08:03] <axw> we just had a barbecue with all the family round ours
[08:18] <axw> wallyworld_: I have just updated http://reviews.vapour.ws/r/589/ again, removing Minimum and Preferred. The top-level Size is minimum, and Count is just required - there's no reason for anything to over deliver on count
[08:18] <wallyworld_> sure, will look
[08:21] <axw> wallyworld_: do you know if your change has fixed the regression? it's not clear to me from the CI dashboard
[08:21] <wallyworld_> axw: yes, the previously failing local deployment CI tests pass; there's still a joyent failure though which is separate i think as all the local tests were failing before
[08:22] <axw> wallyworld_: can we flip it to released, or do you want to wait for QA to verify?
[08:23] <wallyworld_> axw: i just checked, the CI tests are almost finished again for a 2nd commit, the joynet local precise tests are pending. let's wait a bit longer to see how those pan out
[08:23] <axw> ah ok
[08:23] <axw> cool
[08:23] <wallyworld_> i'm not sure if we're supposed to flip the bug status ourselves
[08:24] <wallyworld_> or wait for the reporter to do it
[08:24] <axw> never mind, I can wait
[08:45] <jam> hi fwereade, I hope you enjoyed your break
[08:45] <fwereade> jam, heyhey
[08:46] <fwereade> jam, yes, thank you, it was quite disconcertingly peaceful -- and yourself?
[08:54] <jam> fwereade: pretty good for me. We went to Germany to spend time with relatives for the new year. Got to be properly cold for NY (well 5 on NY, but it did get below zero in Germany)
[08:56] <wallyworld_> fwereade: g'day. we missed our 1:1 earlier. can we do it a bit later
[08:56] <voidspace> morning all
[08:56] <axw> morning
[08:56] <fwereade> wallyworld_, oops, so we did, I haven't quite adjusted to a proper timetable
[08:56] <wallyworld_> np, i need to cook and eat dinner etc, can i ping you when i'm ready?
[10:01] <dimitern> voidspace, jam? standup time
[10:01] <voidspace> dimitern: omw
[10:01] <voidspace> in fact, here
[10:05] <jam> dimitern: you still there?
[10:11] <fwereade> TheMue, jam, voidspace: dimitern's internets have fallen over, he's working on it
[10:12] <TheMue> fwereade: thx for info
[10:33] <wallyworld_> fwereade: let me know when you're free to chat?
[10:33] <fwereade> wallyworld_, cleaner's in here at the moment, maybe 10 mins or something?
[10:33] <wallyworld_> fwereade: sure, np
[10:41] <axw> fwereade: would you PTAL at https://github.com/juju/charm/pull/77 ? I think/hope your previous concerns should be allayed
[10:45] <fwereade> axw, cool, will do
[11:13] <voidspace> jam: "NodeGroup is the internal name for a cluster."
[11:14] <voidspace> dimitern: jam: it looks like a nodegroup-interface represents a network interface
[11:14] <voidspace>     A NodeGroupInterface is identified by the uuid for its NodeGroup, and the name of the network interface it represents: “eth0” for example.
[11:14] <jam> voidspace: that sounds an awful lot like it would be the actual network interface for a machine. Maybe it is the Node Group controller's interface?
[11:15] <voidspace>     A NodeGroupInterface is a network interface attached to a cluster controller, with its network properties.
[11:20] <voidspace> I've asked some questions on #maas
[11:20] <voidspace> No reply yet
[11:24] <perrito666> morning
[11:25] <voidspace> jam: dimitern: an in-between approach (not too much work) is for the provider layer to choose whether it allocates or whether it lets the provider allocate
[11:25] <voidspace> jam: dimitern: so with maas we use "dynamic allocation" and with ec2 we use static allocation
[11:25] <voidspace> jam: dimitern: then we can move ec2 to dynamic allocation later if we want
[11:28] <voidspace> Our current strategy picks an unused address and attempts to allocate that. This returns an error or nil (for success).
[11:28] <voidspace> We could let the provider implementation of AllocateAddress return a *different* address if it successfully allocates one
[11:28] <voidspace> allowing it to ignore the requested address if it wants to - which the MaaS implementation always would
[11:29] <voidspace> slightly janky but flexible
[11:29] <voidspace> perrito666: morning
[12:04] <dimitern> voidspace, jam, TheMue, sorry guys I was away till now - first network issues, then the heating stopped..
[12:04] <TheMue> dimitern: heya, welcome back
[12:04] <TheMue> dimitern: oh, no heating is hard
[12:05] <TheMue> dimitern: even harder than no network, hmmmm, or ... *justKidding*
[12:06] <voidspace> dimitern: hey, hi
[12:06] <voidspace> dimitern: did you see my questions/comments above or should I repeat them?
[12:06] <dimitern> :D
[12:06] <dimitern> I can see the one about nodegroup-interfaces being NICs
[12:06] <voidspace> dimitern: right
[12:07] <voidspace> NICs on the cluster controller
[12:07] <voidspace> dimitern: is that what we want - will they correspond directly (one-to-one) with networks?
[12:07] <voidspace> dimitern: or should I switch to a hybrid approach (which I like but is admittedly slightly janky)?
[12:09] <dimitern> voidspace, AIUI networks are created when you add a NGI
[12:09] <voidspace> dimitern: so, there always should be the one-to-one correspondence we need
[12:09] <dimitern> voidspace, but you can create them manually as well, so this tells me they *might* sometimes not match 100%, but for a definite answer we should consult the maas guys or the source
[12:10] <voidspace> I've asked questions on #maas
[12:10] <voidspace> no answer yet
[12:10] <voidspace> I will proceed assuming they will match
[12:10] <voidspace> and will tweak appropriately if needed - or start again with a different approach...
[12:10] <voidspace> depending on the answer...
[12:11] <dimitern> voidspace, just a sec
[12:11] <dimitern> voidspace, it occurred to me there could be valid cases where networks != NGIs
[12:11] <dimitern> voidspace, NGI == networks only for those maas is supposed to manage dhcp, dns, or both
[12:12] <voidspace> really?
[12:12] <voidspace> ah, maybe
[12:12] <voidspace> just checking what mine is
[12:13] <voidspace> they seem to correspond and I *thought* I didn't have maas managing dhcp or dns, but I might be wrong
[12:13] <dimitern> voidspace, it seems logical - otherwise (for non-managed - i.e. vlans, etc.)
[12:13] <dimitern> voidspace, sorry, that should've been - for non-managed there's not point in having a NGI associated with the network
[12:14] <voidspace> maas is managing dhcp and dns for my cluster
[12:15] <dimitern> voidspace, but in any case we *only* care about dhcp-managed networks for the address allocation logic
[12:15] <voidspace> dimitern: so we *can't* assume a correspondence, which means (as far as I can tell) that we can't always know the static range of the subnet
[12:15] <voidspace> dimitern: ah right, so it doesn't matter - we can *ignore* networks where we don't have this information
[12:15] <voidspace> dimitern: so it's one-to-one where we care
[12:16] <dimitern> voidspace, that's correct I think and it is reasonable - if maas is not managing dhcp/static ips for that net using the net's corresponding NGI then we don't care
[12:16] <dimitern> yeah I think so
[12:16] <voidspace> dimitern: cool, thanks
[12:17] <dimitern> voidspace, I do have a few unmanaged vlans on my maas
[12:17] <dimitern> voidspace, and despite being unmanaged (by maas) I can still use them for instance selection and then configure them (presumably) myself after maas gives me the node
[12:18] <voidspace> right, but you wouldn't expect  juju to be able to use them
[12:18] <voidspace> as they require manual configuration
[12:18] <dimitern> not for allocating addresses via the maas api, no :)
[12:18] <voidspace> cool, good enough
[12:18] <dimitern> but for constrains - yes
[12:19] <voidspace> ah, so you'll want Subnets to still return those networks just with nil for the AllocatableIPLow/High
[12:19] <voidspace> meaning "no allocatable addresses"
[12:19] <dimitern> I think so
[12:20] <voidspace> so I won't ignore them then
[12:20] <voidspace> right, I'm going on lunch
[12:20] <dimitern> cheers
[12:20] <dimitern> :)
[13:13] <perrito666> is there anything like distcc for go?
[15:00] <wwitzel3> ericsnow, perrito666: having some hangout issues
[15:01] <perrito666> hangout is love
[15:02] <perrito666> wwitzel3: ericsnow helps if we push this one hour?
[15:04] <ericsnow> perrito666, wwitzel3: fine with me
[15:05] <perrito666> ok, lets push it so wwitzel3 can solve his issue without hurrying
[15:05] <wwitzel3> perrito666: it is solved
[15:05] <perrito666> wow you are good
[15:05] <wwitzel3> but if you need to push it, that's fine :)
[15:05] <perrito666> nah, I am here anyway
[15:37] <voidspace> dimitern: ping
[15:38] <dimitern> voidspace, pong
[16:05] <alexisb> wwitzel3, ping
[16:05] <voidspace> dimitern: ping
[16:06] <voidspace> dimitern: philosophical question
[16:06] <voidspace> dimitern: we've called the maas nodegroups api endpoint and got a list of nodegroups (uuids)
[16:06] <voidspace> dimitern: we now need to make a series of calls, fetching the nodegroup interfaces for each nodegroup
[16:06] <voidspace> dimitern: and pulling out of that the ip, static_range_low and static_range_high for each interface
[16:07] <dimitern> voidspace, yeah
[16:07] <voidspace> dimitern: an individual call to fetch interfaces for a nodegroup can fail, as can pulling out the details from the result
[16:07] <voidspace> dimitern: in the presence of an error should we log and continue (my current approach) or error out?
[16:07] <voidspace> dimitern: the downside of logging and continuing is that even if *every call* errors we don't fail - we just return an empty map
[16:08] <voidspace> dimitern: the downside of erroring out is that the whole call would fail just for one missing bit of information
[16:08] <voidspace> dimitern: e.g. nodegroup deleted between fetching the list of nodegroups and querying the interfaces
[16:08] <voidspace> as I said, my current approach is to log (as a Warning) and continue
[16:09] <dimitern> voidspace, +1 on logging definitely
[16:10] <dimitern> voidspace, but deciding whether to error out entirely or not at the end should be:
[16:11] <dimitern> voidspace, if we gathered enough information, despite some errors -> ok, otherwise ... hmmm possibly wrap and return the (most important?) errors
[16:11] <dimitern> niemeyer, hey
[16:11] <niemeyer> dimitern: Heya
[16:11] <voidspace> but knowing what's "enough" information or not is difficult :-)
[16:12] <voidspace> if we fail to get the information, the result will be that we decide no networks have allocatable IP addresses
[16:12] <dimitern> niemeyer, any plans for fix for that issue with gopkg.in not supporting branches like "v2-dev"  (I'll try to find the issue #..)
[16:12] <voidspace> which is perhaps an odd error to end up with when it's a transient connection failure
[16:12] <voidspace> I'll think about it
[16:12] <wwitzel3> alexisb: pong
[16:13] <alexisb> hey there wwitzel3
[16:13] <alexisb> can you please join #server
[16:13] <dimitern> voidspace, we can have a chat tomorrow perhaps? it's getting late and harder for me to not being stupid :)
[16:13] <voidspace> dimitern: ok mate, you go
[16:13] <voidspace> dimitern: speak tomorrow
[16:13] <voidspace> dimitern: I've got more stuff to do now
[16:13] <niemeyer> dimitern: Yeah, I'll work on gopkg.in this week
[16:14] <voidspace> it's an annoying little decision
[16:14] <niemeyer> dimitern: There are a couple of things to improve there
[16:14] <voidspace> dimitern: the trick is to pick the "less wrong" answer...
[16:14] <niemeyer> dimitern: The source code linking is also coming
[16:14] <dimitern> voidspace, cheers, I'm sure you'll find a nice way to solve it :)
[16:14] <dimitern> niemeyer, nice!
[16:15] <dimitern> niemeyer, but now it seems you can't import "gopkg.in/amz.v2-dev/ec2" - perhaps I should rename that branch to v2?
[16:15] <dimitern> niemeyer, until the changes happen?
[16:16] <niemeyer> dimitern: Please don't do that.. let me fix the problem
[16:16] <dimitern> niemeyer, ok, no problem - I wanted to ask first
[16:16] <niemeyer> dimitern: For the time being, just do a "git clone" locally to the right location
[16:16] <dimitern> niemeyer, yeah, that'll work
[16:16] <niemeyer> (gopkg.in/amz.v2-dev/ec2)
[16:17] <dimitern> niemeyer, thanks!
[16:17] <niemeyer> dimitern: Labeling as v2 would be advertised as a new major available
[16:17] <niemeyer> dimitern: which means you should not change it further
[16:17] <niemeyer> dimitern: in incompatible ways
[16:17] <niemeyer> dimitern: Or is that what you intend to do in fact?
[16:18] <dimitern> niemeyer, yeah, fair point
[16:18] <dimitern> niemeyer, no, I intend for it to be stable at least for a while :)
[16:18] <niemeyer> dimitern: Clarifying the question: do you have further breaking changes to do on v2-dev soon?
[16:19] <dimitern> niemeyer, I have 2-3 PRs queued up which add new API methods, but don't break (hopefully) existing ones
[16:19] <niemeyer> dimitern: Well, so you can just rename it
[16:20] <niemeyer> dimitern: The point of -dev is to prevent people from using it while in a heavy development period, readying for the release
[16:20] <niemeyer> dimitern: It sounds like what you want is to release it
[16:20] <dimitern> niemeyer, yeah, fair point
[16:21] <dimitern> niemeyer, although it's safer to do a few more changes first as I need them anyway, and rename it once v2 is more or less stable
[16:21] <dimitern> and juju needs to use v2
[16:23] <dimitern> niemeyer, we should have a call some time this week, if you don't mina and have the time to discuss the other goamz topics - contributors, merging the other forks, etc.
[16:24] <niemeyer> dimitern: Sounds good, but "stability in this case" is not "won't change", but "won't change in incompatible ways"
[16:24] <niemeyer> dimitern: Of course
[16:24] <niemeyer> dimitern: Will be a pleasure
[16:24] <dimitern> niemeyer, right, cheers!
[16:26] <dimitern> niemeyer, which of the coming days works for you? perhaps ~1h or less - also at what time?
[16:28] <niemeyer> dimitern: I suppose now is too late for you, right?
[16:28] <niemeyer> dimitern: I mean, at this time, different day
[16:28] <dimitern> niemeyer, yeah, tomorrow about this time is better for me - should I sent and invite then?
[16:29] <niemeyer> dimitern: +1
[16:29] <niemeyer> dimitern: Oh, wait
[16:29] <dimitern> niemeyer, yeah?
[16:29] <niemeyer> dimitern: I have a 30mins slot at this time
[16:30] <niemeyer> dimitern: Feel free to start 30 mins earlier, or reduce the slot
[16:30] <dimitern> niemeyer, ok, so let's say 16 UTC tomorrow for 1h?
[16:30] <niemeyer> dimitern: Sounds good
[16:31] <dimitern> niemeyer, thanks, I'll send an invite then
[17:09] <perrito666> wwitzel3: ericsnow any volunteers to answer that last email?
[17:09] <perrito666> that was fast :p
[17:12] <alexisb> wwitzel3, you when the prize for fastest status reporting :)
[17:12] <ericsnow> alexisb: we still need to verify that networking is not required (only 1(?) existing provider implements it)
[17:12] <wwitzel3> alexisb: not sure I want the prize .. lol
[17:14] <alexisb> ericsnow, same with storage?
[17:15] <ericsnow> alexisb: they all (or nearly) have storage implemented, but only because it was required for juju up until recently (yay axw)
[17:16] <alexisb> ah ok ericsnow
[17:17] <alexisb> so ericsnow, wwitzel3 what do you guys need from me to help answer what is needed for storage and network support?
[17:18] <ericsnow> alexisb: the question came up as we jumped back in yesterday and I figured we'd just ask dimitern
[17:19] <ericsnow> (looks like I missed him though)
[17:20] <ericsnow> alexisb: I do think if we still want the networking stuff now it could wait until after we land the GCE provider
[17:20] <ericsnow> alexisb: as to storage, I'm pretty confident we don't need it; I'll follow up with axw tonight
[17:21] <perrito666> ericsnow: wwitzel3 alexisb I have a decent overlap with dimitern do you need me to tackle him and ask him something?
[17:22] <ericsnow> perrito666: feel free to ask him if networking needs to be implemented for the GCE provider (basically none of the other providers have it)
[17:27] <wwitzel3> ericsnow: patch is merged, I am going to try a manual fix that smoser suggested for testing purposes
[17:27] <ericsnow> wwitzel3: great!
[17:33] <wwitzel3> ericsnow: we have a regression
[17:34] <ericsnow> wwitzel3: :(
[17:34] <wwitzel3> ericsnow: with the root disk stuff in instance.go
[17:34] <ericsnow> wwitzel3: k
[17:34] <wwitzel3> ericsnow: http://paste.ubuntu.com/9683253/
[17:35] <ericsnow> wwitzel3: want to jump into the hangout?
[17:35] <wwitzel3> ericsnow: yep
[18:18] <perrito666> is there a list for the possible agentconfig keys?=
[18:34] <voidspace> g'night all
[18:34] <wwitzel3> nn voidspace
[18:34] <voidspace> o/
[18:38] <perrito666> katco: I was really fearing that was a longer pr :p given the extensive description
[18:38] <katco> perrito666: lol glad to disappoint in that regard :)
[18:38] <katco> perrito666: i like to provide helpful commit messages if i can remember
[18:40]  * katco goes to fix lunch
[20:37] <thumper> cherylj: got a few minutes now?
[20:38] <cherylj> thumper: yes
[20:41] <thumper> niemeyer: hey, you around?
[20:58] <niemeyer> thumper: Here
[21:09] <thumper> cmars: ping
[21:10] <cmars> thumper, pong
[21:10] <thumper> cmars: 'tis our weekly chat time
[21:10] <cmars> thumper, ah right. joining
[21:15] <katco> fwereade: ping, 2015 style.
[21:34] <wallyworld_> alexisb: you free for our QA meeting?
[21:34] <alexisb> wallyworld_, no I have a conflict today
[21:35] <wallyworld_> ok
[22:46] <menn0> wallyworld_: just reviewed http://reviews.vapour.ws/r/678/
[22:46] <menn0> wallyworld_: just a few questions
[22:46] <wallyworld_> \o/ tyvm
[22:47] <wallyworld_> having breakfast, will look soon
[22:48] <menn0> wallyworld_, thumper: there's PR with fixes for the cloudsigma provider up for review. is anyone sheparding that work or should I review it?
[22:49] <thumper> menn0: I think there is someone sheparding it, but I don't recall who
[22:49] <wallyworld_> ditto
[22:49] <menn0> jam?
[22:49] <wallyworld_> wayne maybe
[22:50] <menn0> i'll ask them
[22:50] <perrito666> menn0: thumper its wayne
[22:50] <thumper> perrito666: ta
[22:50] <menn0> perrito666: thanks
[22:50]  * menn0 is glad to dodgy that large review
[22:50]  * perrito666 returned from EOD mode just for that, bye folks
[22:50] <menn0> dodge even
[22:50] <menn0> perrito666: good night