[01:30] <thumper> it is right about now I want a debugger with local variable introspection
[01:31] <wallyworld> thumper: use PyCharm :-D
[01:31] <thumper> for golang?
[01:31] <wallyworld> yup
[01:31] <thumper> has debugging?
[01:31] <wallyworld> yup
[01:31] <thumper> since when?
[01:31] <wallyworld> ages
[01:31] <wallyworld> you use a golang plugin
[01:32] <thumper> but... but... PyCharm
[01:32] <wallyworld> any of the IDEs work
[01:32] <wallyworld> IntelliJ etc
[01:32] <wallyworld> but i like PyCharm so I can also open the Python juju client etc
[01:32] <wallyworld> they all use the same plugin
[01:33] <wallyworld> i don't think the offical plugin has all the features, i use one that's in development which will become offical
[01:33] <wallyworld> jetbrains took it over
[01:34] <wallyworld> axw: i have to head out to take kid to movie theatre, bbiab
[01:34] <axw> wallyworld: sure, I'm half way through your review
[01:36] <wallyworld> i owe you a beer :-(
[01:51] <natefinch> ericsnow: you around?
[02:17] <davechen1y> thumper: https://github.com/juju/juju/pull/4212
[02:17] <davechen1y> ugly ass backport to 1.25
[02:18] <davechen1y> needs a lot of testing as I had to bump the version of juju/utils to pick up dependencies of the juju/juju/testing package which the state/leadership tests use
[02:20] <thumper> ugh
[02:20] <thumper> reviweed
[03:06] <thumper> fuck-a-doodle
[03:06]  * thumper bangs his head on the desk
[03:06] <thumper> just figuratively
[03:10] <thumper> oh FFS
[03:10]  * thumper takes a deep breath and dives into the code again
[03:22] <davechen1y> um
[03:22] <davechen1y> % juju bootstrap --bootstrap-series=precise --upload-tools -v
[03:22] <davechen1y> error: flag provided but not defined: --bootstrap-series
[03:22] <davechen1y> how am I supposed to test 1.25 when it doens't understand this flag ...
[03:23] <davechen1y> what's olde english for --boostrap-series
[03:23] <natefinch> --series?
[03:23] <davechen1y> i'll try it ?
[03:23] <davechen1y> i'll try it
[03:24] <natefinch> also, juju help bootstrap ;)
[03:24] <davechen1y> lucky(~/src/github.com/juju/juju) % juju bootstrap --series=precise --upload-tools -v
[03:24] <davechen1y> Use of --series is obsolete. --upload-tools now expands to all supported series of the same operating system.
[03:24] <davechen1y> WARNING ignoring environments.yaml: using bootstrap config in file ""
[03:24] <davechen1y> WARNING This juju environment is already bootstrapped. If you want to start a new Juju
[03:24] <davechen1y> environment, first run juju destroy-environment to clean up, or switch to an
[03:24] <davechen1y> alternative environment.
[03:24] <davechen1y> ERROR environment is already bootstrapped
[03:25] <davechen1y> ^ that is a lie
[03:25] <natefinch> juju destroy-environment foo --force -y
[03:25] <natefinch> already bootstrapped sometimes means "last bootstrapped failed and we didn't clean up enough" :/
[03:32] <davechen1y> thumper: did you find the details about the juju/txn bug we talked about at standup
[03:32] <davechen1y> i'd like to look into that as a priority
[03:32] <davechen1y> 'cos that is horrible
[03:35] <thumper> no, sorry
[03:37] <davechen1y> :(
[03:43] <davechen1y> wow, 1.25 is old
[03:43] <davechen1y> no --format short
[03:45] <thumper> davechen1y: juju/txn ErrExcessiveContention
[03:45] <axw> davechen1y: there was never a way to specify series for just the bootstrap machine before. you had to set preferred-series in environments.yaml
[03:45] <davechen1y> that's the one
[03:45] <davechen1y> axw: ahh
[03:45] <thumper> txn.go line 151
[03:46] <davechen1y> yeah, i know that
[03:46] <davechen1y> so we said at standup that error X is happening, which doesn't match any of the preconditions, so the errror is replaced by ErrExcessiveContention
[03:47] <davechen1y> ok, i was wrong juju status --format short is implemented
[03:47] <davechen1y> but returns nothing if you have no machines deployed
[03:47] <davechen1y> which makes sense in a "thanks, that didn't help" way
[03:48] <thumper> heh
[03:49] <davechen1y> thumper: can you find the fix that you landed last time this happened ?
[03:49] <davechen1y> which i imagine probably jiggled a transaction operation to not do something
[03:50] <thumper> let me take a quick look
[03:50] <davechen1y> ta
[04:05] <davechen1y> thumper: fix confirmed, submitting http://reviews.vapour.ws/r/3645/
[04:16] <thumper> ok
[04:16] <thumper> quick look doesn't find it I'm afraid
[04:18] <thumper> davechen1y: my test tear down is failing saying I have dirty sockets...
[04:19] <thumper> davechen1y: after more looking, I can't see what's going on
[04:19] <thumper> any hints on how to debug this?
[04:21] <davechen1y> thumper: linkage
[04:21] <thumper> wat?
[04:21] <davechen1y> link for some text of what you are seeing
[04:21] <davechen1y> please
[04:22] <thumper> davechen1y: http://paste.ubuntu.com/14676889/
[04:23] <davechen1y> ta
[04:23] <davechen1y> thumper: normally whent hat happens mongo has crapped itself waaaaaya up in the piece
[04:25] <thumper> yeah, but only running one test
[04:25] <thumper> and it is recurring
[04:25] <thumper> so I'm guessing it is me
[04:25] <davechen1y> off
[04:25] <davechen1y> odd
[04:26] <thumper> normally this is when you forget to close something
[04:26] <davechen1y> i've always seen that in big test runs when mongo poops itself and this is just the aftershock of every suite setup and tear down
[04:26] <thumper> but I have the defer close
[04:26] <davechen1y> failing
[04:37] <thumper> hmm... logging is getting me places... slowly
[04:50] <davechen1y> thumper: this merge gets worse and worse
[04:50] <davechen1y> 'cos juju/juju/testing needs a newer version of juju/utils, had to update that
[04:50] <davechen1y> and juju/utils needs yaml.v2
[04:51] <davechen1y> this is like the story about needing a nail to fix a horse shoe
[04:51] <davechen1y> to get a penny
[04:51] <davechen1y> to buy some milk
[04:51] <davechen1y> to feed a pig
[04:51] <davechen1y> to ride on sunday
[04:52] <thumper> well, at least you can see your journey...
[04:53] <thumper> my test is being torn down while running
[04:53] <thumper> beat that
[04:53] <thumper> I mean, WTF?
[04:54] <thumper> davechen1y: right now I have *no* clue as to what's going on
[04:54] <davechen1y> push it to a branch
[04:54] <davechen1y> i'll take a look
[04:55] <thumper> pushing
[04:57] <natefinch> this is (one of the reasons) why dumping a bunch of unrelated crap into juju/utils is a terrible idea.  If it was all separate repos, you could just update the one you need, and not update everything else.
[04:59] <thumper> davechen1y: https://github.com/howbazaar/juju/tree/migrate-machines
[05:00] <thumper> davechen1y: although I'm pretty much done...
[05:00] <thumper> davechen1y: let me point you at a few things:
[05:01] <thumper> state/migration_import_test.go line 185
[05:01] <thumper> that line is never reached in the test
[05:01] <thumper> state/migration_import.go line 142, both the possible return places have logging, neither happens
[05:02] <thumper> I get: [LOG] 0:00.255 DEBUG juju.state.import-model importing machine 0
[05:02] <thumper> START: <autogenerated>:784: MigrationImportSuite.TearDownTest
[05:02] <thumper> [LOG] 0:00.255 DEBUG juju.state closed state without error
[05:03] <thumper> no test assertion failed AFAICT
[05:03] <thumper> just start of tear down
[05:03] <thumper> it would be great if you figured this out, but I'm going to sleep on it
[05:03] <thumper> laters
[08:58] <frobware> dooferlad, running 10 mins late...
[08:59] <dooferlad> frobware: ack
[09:11] <frobware> dooferlad, back...
[09:12] <dooferlad> frobware: see in in a sec then
[09:22] <jam> wallyworld: I just submitted bug #1538462 about "juju bootstrap --debug" containing a lot of simplestreams "garbage"
[09:22] <mup> Bug #1538462: simplestreams debug content is useless (juju bootstrap --debug) <logging> <simplestreams> <juju-core:Triaged> <https://launchpad.net/bugs/1538462>
[09:22] <jam> specifically, it is serializing something and putting just the pointer content into the log
[09:23] <jam> 20130404:0xc8201f1e00 20130423:0xc8201f1ec0 20131123:0xc82040c0c0 20130313:0xc8201f16e0 20131022:0xc8201f18c0 20130928:0xc8201f1980
[09:23] <jam> is not particularly useful for anyone
[09:40] <mup> Bug #1538462 opened: simplestreams debug content is useless (juju bootstrap --debug) <logging> <simplestreams> <juju-core:Triaged> <https://launchpad.net/bugs/1538462>
[09:50] <jam> frobware: dimitern: I got roped into a phone call for a client, so I won't be able to make standup today.
[09:51] <frobware> jam: ack
[09:52] <frobware> dimitern, do you have an /e/n/i I could look at from your IPv6 setup?
[09:58] <dimitern> jam, np
[09:58] <dimitern> frobware, not right now, but I can get one
[09:59] <frobware> dimitern, not desperately urgent
[10:02] <frobware> dimitern, voidspace: standup
[10:03] <dimitern> sorry, omw
[10:30] <dimitern> frobware, I'm typing in the HO chat
[10:38] <voidspace> dimitern: we said don't do the hack with a yaml setting and take a couple of days to do it properly
[10:38] <frobware> dimitern, I'm confused about the proposed PR/change for default.
[10:39] <frobware> dimitern, are we going for a change that does NOT require a yaml addition?
[10:40] <dimitern> frobware, voidspace, ok, let me think for a bit to see what are the options
[10:40] <dimitern> and then we can decide?
[10:41] <frobware> dimitern, thanks. we need to convey our plans to cheryl too
[10:42] <axw> wallyworld: https://github.com/juju/juju/compare/cloud-credentials...axw:cloud-credentials-prepareforbootstrapparams  -- all tests pass, but I want to do some live tests and audit code before I propose it (tomorrow)
[10:42] <axw> wallyworld: if you want to look before then, I don't expect too much will change
[10:43] <wallyworld> axw: ok, will do
[11:41] <dimitern> frobware, I think I have a good plan for a "proper" fix
[11:41] <frobware> dimitern, great!
[11:41] <wallyworld> jam: hey, you still online? what are your issues with splitting config and dat directories?
[11:42] <dimitern> here's the gist of it: http://paste.ubuntu.com/14678495/
[11:42] <frobware> dimitern, want to HO to discuss? I can act as a sounding board.
[11:42] <jam> wallyworld: I don't have a huge problem with it, I don't know that it actually provides clarity rather than just complexity, though.
[11:42] <dimitern> frobware, I need to go out now, but let's chat when I'm back in <1h
[11:42] <jam> wallyworld: the data we have I wouldn't put into /usr/share, for example
[11:42] <frobware> dimitern, ok, but probably after that as I have a couple of back-2-back meetings.
[11:42] <jam> its not that kind of dataa
[11:42] <dimitern> frobware, np
[11:43] <wallyworld> jam: it keeps pure config data that the user can and should look at and edit separate from stuff they should not edit lest the stuff things up. and it conforms to a standard
[11:43] <wallyworld> sure not in /usr/share but ~/config/juju for clouds and credentials
[11:43] <wallyworld> and the data dir for controller cache and other runtime stuff users should not see
[11:44] <wallyworld> we don't want to put in their faces files they are not expected to look at
[11:44] <wallyworld> we tell them - anything in ~/.config/juju you can edit and look at
[11:44] <wallyworld> that makes it easy for them
[11:46] <jam> wallyworld: so can you link the actual "this is where you should put file X" stuff? The actual XDG spec just says what the variables are, but not how to pick which one
[11:47] <wallyworld> jam: i don't have the link, but perrito666 probably does
[11:48] <jam> wallyworld: so there are a couple of articles on "ploum.net" that talk about this, but actually his notes seem to say everything should be in DATA
[11:48] <jam> as they aren't just "preferences that can be reset"
[11:48] <wallyworld> everything in data makes no sense
[11:49] <wallyworld> clouds and credentials etc are definitely config
[11:49] <jam> https://ploum.net/184-cleaning-user-preferences-keeping-user-data
[11:49] <jam> wallyworld: credentials are critical information about remote systems
[11:49] <jam> not just simple config
[11:49] <jam> as in, if I lose them, I'm hosed
[11:49] <jam> vs "I want tabular by default" is config
[11:50] <jam> the pluom article at least says that you should be able to wipe config and start fresh with default settings
[11:51] <jam> and that is *not* true of credentials
[11:51] <wallyworld> so perhaps the new jenv type stuff should go in "<runtime>" not data
[11:52] <wallyworld> i'll discuss it some more
[11:53] <jam> wallyworld: runtime is for "non-essential runtime files such as sockets and named-pipes"
[11:53] <jam> and the lifetime of RUNTIME is bound to the logged in user
[11:53] <jam> definitely not what we want
[11:53] <jam> logging out shouldn't reset your credentials :)
[11:53] <wallyworld> so there be some way of separating user editable stuff from juju stuff
[11:54] <jam> wallyworld: if users are vim ~/*/juju we've probably failed our CLI UX
[11:54] <jam> as in, there may be thing they *could* edit, but we'd really be better off not suggesting they edit anything
[11:54] <jam> (vim is not typesafe)
[11:54] <wallyworld> they need to poentially edit their personal clouds.yaml
[11:54] <jam> wallyworld: we should provide CLI ways to describe a cloud instead
[11:55] <jam> wallyworld: vim won't do syntax checking that the information they type is valid
[11:56] <wallyworld> the spec has an add-cloud command that assumes that a clouds.yaml exists already. we could allow it to be edited using a schema like we will for credentials
[11:57] <wallyworld> that article does make a point that i hadn't considered
[11:58] <jam> I can't say pluom is authoritative, but the XDG spec tells you *what* the variables are, but not why to use them (at least that I've fonud)
[12:00] <wallyworld> +1 to that
[12:01] <wallyworld> ok, we'll look to see how using <data> will turn out, and treat stuff there as needing to be persistent
[13:03] <alexisb> fwereade, ping
[13:16] <perrito666> morning
[13:44] <rogpeppe1> dimitern: you might like this new proposed addition to juju/utils: https://github.com/juju/utils/pull/193/files
[14:35] <dimitern> rogpeppe1, looks nice :)
[14:35] <rogpeppe1> dimitern: thanks :)
[14:36] <dimitern> rogpeppe1, I have a growing number of things to add to juju/utils .. in my abundant free time :)
[14:36] <rogpeppe1> dimitern: :)
[14:36] <rogpeppe1> dimitern: tbh i think we should split it up
[14:36] <dimitern> rogpeppe1, subpackages or subrepos?
[14:37] <rogpeppe1> dimitern: subpackages
[14:37] <dimitern> rogpeppe1, +100
[14:38] <rogpeppe1> dimitern: and it's somewhat criminal that importing juju/utils side-effects http.DefaultClient
[14:39] <dimitern> rogpeppe1, oh.. GetNonValidating.. ?
[14:39] <rogpeppe1> dimitern: no, grep 'func init'
[14:40] <dimitern> rogpeppe1, ah, right :/
[14:41] <frobware> dimitern, dooferlad, voidspace: http://reviews.vapour.ws/r/3648/ -- will do more manual testing, and testing with stakeholders before merging. but a review would help move that forward.
[14:46] <dimitern> frobware, is this the same script as in master?
[14:47] <frobware> dimitern, yep
[14:47] <frobware> dimitern, should be 100% identical. the control happens via cli args.
[14:47] <dimitern> frobware, this line: self.is_active = self.method == "dhcp" or self.method == "static"
[14:48] <dimitern> frobware, reminded me of that case where we have a auto eth0 but manual, which has active, static vlan children
[14:48] <dimitern> frobware, did we do anything about that?
[14:49] <frobware> dimitern, do you have a node to hand that boots with that config?
[14:51] <dimitern> frobware, not now, but IIRC thedac had to deal with something similar in dellstack
[15:01] <frobware> dimitern, that case was covered by https://github.com/juju/juju/pull/4148
[15:02] <mup> Bug #1538583 opened: manual provider add-machine failed in api-command-rename <add-machine> <ci> <manual-provider> <regression> <juju-core:Incomplete> <juju-core api-command-rename:Triaged> <https://launchpad.net/bugs/1538583>
[15:02] <mup> Bug #1538589 opened: Container has different subnet <ci> <lxc> <network> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1538589>
[15:03] <dimitern> frobware, right! so we're good then - LGTM I think
[15:09] <frobware> cherylj, can we get a CI build for #1532167  https://github.com/frobware/juju/tree/1.25-lp1532167
[15:09] <mup> Bug #1532167: maas bridge script handles VLAN NICs incorrectly <addressability> <maas-provider> <network> <juju-core:Triaged> <juju-core 1.25:In Progress by frobware> <https://launchpad.net/bugs/1532167>
[15:10] <cherylj> abentley, mgz, can we get a CI run on frobware's branch ^^?
[15:10] <cherylj> this is the one that backports the maas-spaces script to 1.25
[15:11] <mgz> cherylj: I'll push it into the juju namespace
[15:11] <cherylj> mgz: thanks!
[15:50] <dimitern> frobware, can you have a look at this org draft - http://paste.ubuntu.com/14679880/
[15:51] <dimitern> frobware, so it came down to a few more things than I originally thought
[15:51] <frobware> dimitern, certainly looks like it.
[15:51] <dimitern> frobware, I can still probably do it by standup time tomorrow, but not today
[15:52] <frobware> dimitern, sure. it's important we get it right.
[15:52]  * voidspace reading
[15:52] <dimitern> voidspace, dooferlad, please have a look as well ^^
[15:52] <voidspace> dimitern: so for maas now the juju user has to tell us what space they want as default (effectively)?
[15:53] <voidspace> dimitern: what about blake's suggestion - bootstrap without constraint and then pick as default the space that we bootstrap to?
[15:53] <voidspace> to me this looks more complex than we *need*, but I'm digesting it properly
[15:53] <voidspace> *still* digesting it properly
[15:54] <dimitern> voidspace, the idea is to use environ constraints for the default, but also (in maas) discover and save the name in state for use in unspec. bindings later
[15:54] <dimitern> voidspace, so it includes what we discussed with blake
[15:55] <dimitern> voidspace, i.e. I think this is the "proper way" to do it, and it's not maas specific
[15:55] <voidspace> dimitern: why do we *need* a different default space and controller space specifications
[15:55] <voidspace> dimitern: can't we initially have just a default one
[15:56] <voidspace> dimitern: or is that just for where controller and specified default *are* different
[15:57] <dimitern> voidspace, they need to be distinct in the general case, as the controller "space" is more like a set of addresses from possibly different subnets in different spaces
[15:57] <voidspace> hmm, doesn't sound like a space at all
[15:57] <dimitern> voidspace, but in the default path, we'll set them to be the same in maas (when you don't give us anything specific)
[15:58] <dimitern> voidspace, it's a space with no subnets, just addresses
[15:58] <dimitern> voidspace, well, we can "invent" subnets like 10.20.30.44/32 strictly speaking
[15:58] <voidspace> dimitern: according to our network model that *isn't* a space, and it would probably be less confusing if we didn't call it a space
[15:58] <dimitern> but that's only internally in juju
[15:59] <dooferlad> dimitern: my problem with it is that you are asking the user for information they may not have, and don't need.
[15:59] <dooferlad> you can, at bootstrap, just get a machine and see what spaces it is in once it has been provisioned (as Blake suggested)
[15:59] <dimitern> voidspace, no, we're not :) we're doing what the user said, if they did - otherwise we pick a sane default (at bootstrap) for both names
[16:00] <voidspace> for maas, network.DefaultSpace is not necessarily a sane default
[16:04] <voidspace> dimitern: if controller space isn't a real space, what's the use case for setting it to a real space? (and your doc says it must be a real space)
[16:04] <voidspace> dimitern: what I'm really trying to say is that I don't understand why we need controller space and what it's for
[16:04] <jcastro> does anyone know where the new account/creds stuff is documented? We want to show juju 2.0 to people at the charm summit but we can't seem to find the docs about like credentials.yaml and friends
[16:04] <voidspace> dimitern: and I still don't think we need it
[16:05] <dimitern> voidspace, because it may very well be a real space, dedicated for juju controllers only, and the user has configured it so it can be accessed from all other spaces
[16:05] <voidspace> dimitern: the only place your doc mentions it being used is for selecting API endpooints
[16:05] <dimitern> and know what they are doing
[16:06] <dimitern> voidspace, that's what we need it for
[16:07] <voidspace> your implementation as described *requires* it to be a real space (we always set it to something), whereas above you stated that it was really just a list of endpoints possibly in different spaces
[16:07] <voidspace> dimitern: the implementation you describe in your doc doesn't permit that - it *must* be a real space
[16:09] <voidspace> surely the only thing we *need* to overcome the existing problem is as follows (I may be wrong):
[16:09] <voidspace> set the juju "default space" to the space from the primary nic of machine-0
[16:10] <voidspace> if the user wants to specify a default space they can, for the moment, specify that space as a bootstrap constraint
[16:10] <voidspace> later on we can add a default space setting
[16:13] <dimitern> the setting is need to store it
[16:13] <dimitern> but it can be just in state, not in env.yaml
[16:13] <voidspace> dimitern: right
[16:13] <voidspace> dimitern: we need to store it
[16:26] <mup> Bug #1538589 changed: Container has different subnet <ci> <lxc> <network> <juju-core:Invalid> <https://launchpad.net/bugs/1538589>
[16:29] <mup> Bug #1538589 opened: Container has different subnet <ci> <lxc> <network> <juju-core:Invalid> <https://launchpad.net/bugs/1538589>
[16:32] <mup> Bug #1538589 changed: Container has different subnet <ci> <lxc> <network> <juju-core:Invalid> <https://launchpad.net/bugs/1538589>
[16:35] <mup> Bug #1538589 opened: Container has different subnet <ci> <lxc> <network> <juju-core:Invalid> <https://launchpad.net/bugs/1538589>
[16:38] <mup> Bug #1538589 changed: Container has different subnet <ci> <lxc> <network> <juju-core:Invalid> <https://launchpad.net/bugs/1538589>
[16:42] <perrito666> could anyone ptal http://reviews.vapour.ws/r/3634/ ?
[16:43] <natefinch> katco, ericsnow: I have to pick up my daughter from school right when our meeting is starting today... can we start 15 minutes late?  We could meet for a while beforehand, if you think we might run out of time.
[16:43] <katco> natefinch: as long as you're available until the meeting is over, that's fine
[16:43] <katco> natefinch: i don't anticipate this one running long
[16:43] <natefinch> katco: ok
[16:45] <natefinch> katco: oh, uh, I just noticed it runs through 5:30... I really kind of have to stop at 5 so I can make dinner for the kids.
[16:45] <katco> natefinch: then we should start on time
[16:45] <natefinch> katco: ok, I'll work it out.
[16:45] <katco> natefinch: i can move it up a little as well if that works for ericsnow
[16:46] <ericsnow> katco: fine with me
[16:46] <katco> natefinch: but that puts you leaving in the middle of it?
[16:53] <katco> natefinch: well, just let me know what works for you.
[16:56] <mup> Bug #1538652 opened: MAAS doesn't assign DHCP IP to new Node and doesn't update DNS table <maas-provider> <juju-core:New> <https://launchpad.net/bugs/1538652>
[17:00] <natefinch> katco: I'll just pick up my daughter early, if I can be done at 5.
[17:01] <katco> natefinch: moved it up. we should be done by 5
[17:02] <mup> Bug #1538652 changed: MAAS doesn't assign DHCP IP to new Node and doesn't update DNS table <maas-provider> <juju-core:New> <https://launchpad.net/bugs/1538652>
[17:05] <natefinch> katco: sorry, I think I misunderstood.  I was going to pick her up early to make the 2:30 time.... is there a way we can do an hour now-ish and 2 hours from 3-5 my time?  I'm trying to avoid having to pick her up 45 minutes early from school.
[17:06] <katco> natefinch: have you guys figured out resource-get?
[17:06] <natefinch> katco: yeah, lemme give it one last test
[17:08] <mup> Bug #1538652 opened: MAAS doesn't assign DHCP IP to new Node and doesn't update DNS table <maas-provider> <juju-core:New> <https://launchpad.net/bugs/1538652>
[17:41] <natefinch> is there a way to force an update-status hook to get fired?
[17:45] <natefinch> hey! it worked
[17:46] <katco> \o/
[17:49] <natefinch> it works better when you don't forget you git stashed your previous bugfix
[17:59] <natefinch> katco: can we meet for an hour now?
[18:00] <katco> natefinch: sorry, i need to run some errands over lunch for the trip
[18:00] <katco> natefinch: this is why things go on the calendar
[18:01] <katco> natefinch: bbiab
[18:38] <voidspace> frobware: dooferlad: the good news is that *only* the maas deploy tests are failing for maas-spaces now: http://reports.vapour.ws/releases/3546
[18:40] <katco> natefinch: ok back. so do you want me to put the meeting back to the original time?
[18:50] <katco> ericsnow: i'm going to push the iteration planning back to its original time. i think natefinch is probably picking up his kiddo atm.
[18:50] <ericsnow> katco: k
[18:59] <natefinch> katco: I'm here
[18:59] <katco> natefinch: k, let's do this
[19:00] <katco> ericsnow: going now after all
[19:00] <ericsnow> katco: k
[19:54] <perrito666> cherylj: ping
[20:00] <cherylj> perrito666: pong
[20:16] <perrito666> cherylj: I have been assigned to https://bugs.launchpad.net/juju-core/+bug/1472711 and there is mention of work you are doing and I recall ian telling me too that you where doing work on this and that I was to help you
[20:16] <mup> Bug #1472711: MAAS node has "failed deployment", juju just says "pending" when using juju add-machine <cpec> <feature> <landscape> <maas-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1472711>
[20:17] <cherylj> perrito666: give me a minute, on a stand up.  I'll let you know what's up with that :)
[20:17] <perrito666> thank you
[20:30] <thumper> sinzui: why do pull requestest for machine-dep-engine keep getting opened and quickly closed?
[20:32] <perrito666> thumper: because this is the bot https://www.youtube.com/watch?v=Z86V_ICUCD4
[20:39] <mup> Bug #1538735 opened: default-series breaks --bootstrap-series <bootstrap> <ci> <juju-core:Triaged> <https://launchpad.net/bugs/1538735>
[20:45] <mup> Bug #1538735 changed: default-series breaks --bootstrap-series <bootstrap> <ci> <juju-core:Triaged> <https://launchpad.net/bugs/1538735>
[20:45] <sinzui> thumper: I open them, then github points to conflcits :(. We are blocking master so that the version the machine-dep-engine tests remain valid
[20:47] <cherylj> perrito666: the WIP I have for the machine provisioning status is here:   https://github.com/cherylj/juju/tree/new_provisioning_status
[20:48] <mup> Bug #1538735 opened: default-series breaks --bootstrap-series <bootstrap> <ci> <juju-core:Triaged> <https://launchpad.net/bugs/1538735>
[20:48]  * perrito666 compares to master
[20:49] <perrito666> cherylj:  so, if I understand this correctly I should continue that work? (I am not all that informed as you can see :p )
[20:49] <cherylj> perrito666: let me talk to wallyworld
[20:50] <perrito666> cherylj: there should be no wallyworld so early :p
[20:50] <cherylj> perrito666: if you are going to take it, I'd want to set up some time to do a walkthrough of the code
[20:50] <cherylj> perrito666: some of it is no longer relevant as we won't be using lxc for containers
[20:51] <cherylj> although, it would need to be translated into lxd since we're going to use the same broker approach
[20:51] <cherylj> so n/m
[20:51] <perrito666> hehe. yeah, so I see the task has some important amount of time assigned and the description is, and I am being literal: "finish observability"
[20:52] <perrito666> I am sure Ian was more descriptive on our meeting but this AM I was not feeling very well and my head dropped a few packages
[20:52] <cherylj> I know that feeling
[21:12] <mup> Bug #1538742 opened: lxc containers stay pending when using maas provider and juju 2.0-alpha1 <cpec> <juju-core:New> <https://launchpad.net/bugs/1538742>
[21:15] <mup> Bug #1538742 changed: lxc containers stay pending when using maas provider and juju 2.0-alpha1 <cpec> <juju-core:New> <https://launchpad.net/bugs/1538742>
[21:18] <mup> Bug #1538742 opened: lxc containers stay pending when using maas provider and juju 2.0-alpha1 <cpec> <juju-core:New> <https://launchpad.net/bugs/1538742>
[21:52] <jw4> hi juju peeps - is it a dumb question to ask if I can use juju to deploy a group of applications and databases through mesos/marathon?  Seems like juju and marathon/mesos are subtly different enough that there could be good 'synergy' there?
[22:04] <jw4> thanks lazypower
[22:04] <perrito666> cherylj: so I just synced with wallyworld lemme know when you have a moment
[22:04] <lazypower> np o/ :D
[22:06] <cherylj> perrito666: sure, give me a couple minutes to finish a review
[22:18] <marcoceppi> helloooooooooooooo core
[22:19] <marcoceppi> cherylj: is virtual services on the roadmap for 2.0?
[22:23] <alexisb> marcoceppi, no
[22:23] <marcoceppi> ok :(
[23:02] <alexisb> thumper, ping
[23:03] <cherylj> waigani: ping?
[23:03] <waigani> cherylj: pong
[23:03] <cherylj> hey waigani, would you be able to rebase machine-dep-engine?  This should be the last time as we've blocked master
[23:03] <perrito666> nice table tenis game going on here
[23:04] <waigani> cherylj: sure
[23:05] <cherylj> thanks, waigani!
[23:05] <cherylj> waigani: also let me know if it ends up being trivial.  we may be able to skip the test run if it was
[23:05] <waigani> cherylj: okay, will do