| *** mcastelino has joined #kata-dev | 00:00 | |
| *** mcastelino_ has joined #kata-dev | 00:19 | |
| *** mcastelino has quit IRC | 00:23 | |
| *** mcastelino_ has quit IRC | 00:30 | |
| *** fuentess has quit IRC | 01:22 | |
| *** dlw has joined #kata-dev | 02:19 | |
| *** sameo has quit IRC | 02:32 | |
| kata-irc-bot | <xu> and rc1 is on its way :clap: | 02:40 |
|---|---|---|
| *** zerocoolback has joined #kata-dev | 03:59 | |
| *** sjas_ has joined #kata-dev | 04:21 | |
| *** sjas has quit IRC | 04:23 | |
| *** dklyle has joined #kata-dev | 04:31 | |
| *** dklyle has quit IRC | 04:36 | |
| *** dlw1 has joined #kata-dev | 04:49 | |
| *** dlw has quit IRC | 04:49 | |
| *** dlw1 is now known as dlw | 04:49 | |
| *** dlw1 has joined #kata-dev | 04:50 | |
| *** dlw has quit IRC | 04:50 | |
| *** dlw1 is now known as dlw | 04:50 | |
| *** zerocoolback has quit IRC | 04:58 | |
| *** dlw has quit IRC | 05:35 | |
| *** dlw has joined #kata-dev | 05:59 | |
| *** jodh has joined #kata-dev | 07:36 | |
| *** jodh has quit IRC | 07:36 | |
| *** jodh has joined #kata-dev | 07:36 | |
| *** gwhaley has joined #kata-dev | 07:44 | |
| *** sameo has joined #kata-dev | 07:45 | |
| *** davidgiluk has joined #kata-dev | 08:01 | |
| *** dlw has quit IRC | 08:07 | |
| *** dlw has joined #kata-dev | 08:18 | |
| *** gwhaley has quit IRC | 09:05 | |
| *** gwhaley has joined #kata-dev | 09:22 | |
| *** sameo has quit IRC | 10:16 | |
| *** zerocoolback has joined #kata-dev | 10:47 | |
| *** gwhaley has quit IRC | 11:05 | |
| *** devimc has joined #kata-dev | 12:00 | |
| *** sameo has joined #kata-dev | 12:02 | |
| *** gwhaley has joined #kata-dev | 12:29 | |
| *** eernst has joined #kata-dev | 13:29 | |
| *** devimc has quit IRC | 13:33 | |
| *** devimc_ has joined #kata-dev | 13:33 | |
| *** devimc_ is now known as devimc | 13:35 | |
| *** sameo_ has joined #kata-dev | 13:48 | |
| *** sameo has quit IRC | 13:49 | |
| kata-irc-bot | <eric.ernst> @bergwolf ping? | 13:57 |
| kata-irc-bot | <eric.ernst> Did we ever put together docs/analysis for vm templating? | 13:57 |
| kata-irc-bot | <bergwolf> pong | 13:58 |
| kata-irc-bot | <bergwolf> nop, I don't think so.. | 13:58 |
| kata-irc-bot | <eric.ernst> I'd like to see security v. density v. bootup speed analysis w/ and w/ out, and a general design / usage doc | 13:58 |
| kata-irc-bot | <eric.ernst> its a big and seemingly important feature. | 13:58 |
| kata-irc-bot | <eric.ernst> :slightly_smiling_face: | 13:58 |
| kata-irc-bot | <bergwolf> yeah, I can draft something for that | 13:59 |
| kata-irc-bot | <bergwolf> the network for vm templating is still not working, that's why I didn't try to push it to users | 13:59 |
| kata-irc-bot | <eric.ernst> know what the gap is? | 14:00 |
| kata-irc-bot | <bergwolf> there are issues with network hotplug | 14:00 |
| kata-irc-bot | <xu> actually our documentation repo is kind of chaos and I have begun to sort it this week. we should have all important features documented. | 14:00 |
| kata-irc-bot | <eric.ernst> Yes, I think this is a major missing one - we should be able to prep docs (and have numbers, perhaps as a %, available) | 14:01 |
| kata-irc-bot | <bergwolf> whenever a new nic is hotplugged, the updateinterface API fails to wait for it since the uevent listener goroutine seems not be able to pick up the event while another goroutine is waiting | 14:01 |
| kata-irc-bot | <bergwolf> right now I don't think any network hotplug usage would work unless we sort out that error. /me still looking into it. | 14:02 |
| gwhaley | heh, /me just pinged similar query on old vm template Issue - me and Eric racing there... | 14:05 |
| kata-irc-bot | <eric.ernst> :slightly_smiling_face: | 14:05 |
| gwhaley | @xu - on docs, I agree, we don't have a nice single top level sort of 'BKMs for kata', detailing things like devicemapper, device passthrough etc. The info is a bit scattered. We could do with a 'kata user guide' sort of maybe | 14:06 |
| kata-irc-bot | <bergwolf> I can think of a few docs we need: 1. vm templating 2. network hotplug subcommand 3. netns monitoring 4. vhost-user networking 5. block device passthrough -- esp. the implication of mounting a device mapper inside the guest etc. | 14:07 |
| kata-irc-bot | <eric.ernst> I had a discussion yesterday on this too; we have a lot of nobs -- perhaps need a couple of 'best configurations' | 14:07 |
| kata-irc-bot | <eric.ernst> best density, best security, etc | 14:07 |
| kata-irc-bot | <bergwolf> yeah, there are a lot of config options and we need better documentation/recommendation for users to choose right value for different use cases | 14:09 |
| kata-irc-bot | <xu> @graham.whaley Yes, we should began to improve our documents right now and I agree we should have a topdown structure of them rather than scattered and unrelated pages. | 14:11 |
| kata-irc-bot | <eric.ernst> its deep in conference season and probably have a lot of new users reading through them - probably should make this a priority (along with... every other priority :)) | 14:12 |
| *** fuentess has joined #kata-dev | 14:12 | |
| kata-irc-bot | <bergwolf> there is also an old doc issue on initrd vs. image rootfs https://github.com/kata-containers/documentation/issues/167. people are asking for comparison between different config setups and we should give them better explanation (than I did in the comments). | 14:12 |
| kata-irc-bot | <eric.ernst> (may need meta-issue to track these tasks) | 14:13 |
| kata-irc-bot | <xu> something like github project? | 14:14 |
| kata-irc-bot | <bergwolf> Right now my top priority is to make network hotplug work. After that I can push some docs for vm templating. Just don't want to scare users away by giving them a feature that's not usable. | 14:16 |
| kata-irc-bot | <eric.ernst> I'll create an issue tracking some of the doc changes we've highlighted here. | 14:16 |
| kata-irc-bot | <eric.ernst> @xu perhaps you can add to this, as you're looking at it. | 14:17 |
| kata-irc-bot | <eric.ernst> and/or come up with reorg proposal for it. | 14:17 |
| kata-irc-bot | <xu> sure | 14:19 |
| *** annabelleB has joined #kata-dev | 14:22 | |
| *** eernst has quit IRC | 14:30 | |
| kata-irc-bot | <anne> WRT Zuul, the Zuul team is wrapped up in the PTG through the end of the week, so this Monday is probably a bit ambitious (doesn't give them time to review issues), so I'll aim to get them on the call the Monday after, but please send over and or drop in the agenda items you all want to discuss about the Zuul CI transition | 14:46 |
| *** annabelleB has quit IRC | 14:48 | |
| *** marco_ has joined #kata-dev | 14:52 | |
| *** marcov__ has joined #kata-dev | 14:54 | |
| *** marcov has quit IRC | 14:54 | |
| *** marco_ has quit IRC | 14:57 | |
| *** eernst has joined #kata-dev | 14:59 | |
| *** sameo_ has quit IRC | 15:30 | |
| *** simosx has joined #kata-dev | 15:34 | |
| *** sameo_ has joined #kata-dev | 15:44 | |
| *** jodh has quit IRC | 15:56 | |
| *** dklyle has joined #kata-dev | 15:58 | |
| *** annabelleB has joined #kata-dev | 16:05 | |
| *** dklyle has quit IRC | 16:11 | |
| *** dklyle has joined #kata-dev | 16:11 | |
| *** mcastelino has joined #kata-dev | 16:25 | |
| *** zerocoolback has quit IRC | 16:31 | |
| *** zerocoolback has joined #kata-dev | 16:32 | |
| kata-irc-bot | <eric.ernst> @sebastien.boeuf ping? | 16:36 |
| kata-irc-bot | <eric.ernst> as you go through reviews this week, can you please make an effort to identify stable branch candidates (bugs/security fixes)? | 16:36 |
| *** zerocoolback has quit IRC | 16:37 | |
| *** mcastelino_ has joined #kata-dev | 16:37 | |
| kata-irc-bot | <eric.ernst> we're in a bit of a hole here. | 16:37 |
| *** sameo__ has joined #kata-dev | 16:38 | |
| *** gwhaley has quit IRC | 16:38 | |
| *** mcastelino has quit IRC | 16:39 | |
| *** sameo_ has quit IRC | 16:39 | |
| *** gwhaley has joined #kata-dev | 16:40 | |
| kata-irc-bot | <sebastien.boeuf> @eric.ernst where do I post the result of which PR I think should make it into the stable? | 16:46 |
| kata-irc-bot | <eric.ernst> in the PR itself. Either comment and ask author or duplicate the PR on the stable branches. | 16:46 |
| kata-irc-bot | <sebastien.boeuf> sounds good | 16:46 |
| kata-irc-bot | <eric.ernst> and add label bug if it makes sense (this would be the case if it is a stable candidate) | 16:47 |
| gwhaley | @eric.ernst - maybe we should have github labels for that - might make it easier to search/assess as well ^^ ;-) | 16:47 |
| kata-irc-bot | <eric.ernst> I agree. | 16:47 |
| *** dklyle has quit IRC | 16:47 | |
| kata-irc-bot | <eric.ernst> come up with a good name. | 16:47 |
| kata-irc-bot | <eric.ernst> :slightly_smiling_face: | 16:47 |
| kata-irc-bot | <eric.ernst> stable-candidate? | 16:47 |
| gwhaley | 'stable' or 'stablecan' ^^ ;-) yep | 16:48 |
| kata-irc-bot | <eric.ernst> or should it have status assocaited with it. | 16:48 |
| kata-irc-bot | <eric.ernst> ie, needs-to-be-put-to-stable-still | 16:48 |
| kata-irc-bot | <eric.ernst> or it-needed-to-be-in-stable-but-thankfully-now-it-is-there-phew. | 16:48 |
| gwhaley | we could also have a 'stable-merged', and flip the labels when it lands in stable -but, then we have multiple stables. We could have one label per-stable. I think I've seen that used in other projects | 16:48 |
| kata-irc-bot | <eric.ernst> makes sense. | 16:49 |
| *** dklyle has joined #kata-dev | 16:52 | |
| *** sameo__ has quit IRC | 17:01 | |
| kata-irc-bot | <sebastien.boeuf> @eric.ernst I need some clarifications here. When was the last wave of backporting ? I am asking because by looking at stable-1.1, it seems that we didn't backport anything since https://github.com/kata-containers/runtime/pull/449 | 17:03 |
| kata-irc-bot | <eric.ernst> correct. If you can help with ones that have been merged already, I'd be very grateful. Otherwise, and just as important, please start doing it on open PRs. | 17:03 |
| kata-irc-bot | <eric.ernst> that's the "important part" from a process POV - need to start driving it and encouraging others as well. | 17:04 |
| kata-irc-bot | <sebastien.boeuf> no problem, I can help with that, but I wanted to make sure I was looking at the right thing | 17:04 |
| kata-irc-bot | <eric.ernst> We do need to look back as well, since we didn't actively do this for open PRs over last 2 weeks. | 17:05 |
| kata-irc-bot | <eric.ernst> I can shoot you details. | 17:05 |
| gwhaley | yeah, this needs to happen at either PR time (from he authors), or review time. We can't sustain going back over merged PRs and deciding if they should have been in stable. Maybe we need some sort of 'stable check' CI event (like a specific comment a review has to make to ack/nack stable inclusion)? | 17:05 |
| kata-irc-bot | <eric.ernst> Interesting suggestion. Yeah. | 17:06 |
| gwhaley | maybe pullapprove can do something with a label check | 17:06 |
| kata-irc-bot | <sebastien.boeuf> @graham.whaley yeah we could decide from the PR itself if it should be part of the stable branch | 17:07 |
| kata-irc-bot | <eric.ernst> definitely not sustainable, 100% agree - that can never be the plan (do it after the fact once a month) | 17:07 |
| kata-irc-bot | <eric.ernst> they way I see it, the PR should be labeled with bug initially. | 17:07 |
| kata-irc-bot | <eric.ernst> or feature | 17:07 |
| kata-irc-bot | <eric.ernst> <or something between> | 17:07 |
| kata-irc-bot | <eric.ernst> we need to enforce that it can never be a PR that contains both bug and features... | 17:07 |
| gwhaley | ooh, that'd also work @eric.ernst, to make it clear what level of stable review the PR needs | 17:08 |
| kata-irc-bot | <eric.ernst> definitely need to be explicit going forward. | 17:09 |
| kata-irc-bot | <eric.ernst> (and... once we have a grasp on this - document it in review doc) | 17:09 |
| gwhaley | yep, was just thinking this needs to go in the contrib and review docs | 17:09 |
| kata-irc-bot | <raravena80> _the downsides of too many branches: backporting_ | 17:09 |
| * gwhaley has to drop in a minute | 17:10 | |
| kata-irc-bot | Action: eric.ernst has to drop in a minute. | 17:10 |
| *** gwhaley has quit IRC | 17:11 | |
| kata-irc-bot | <eric.ernst> @sebastien.boeuf as you run through PRs - can you think through each one how you'd label it, and try to do so accordingly (feature v bug). | 17:11 |
| kata-irc-bot | <eric.ernst> and let me know if you have a suggestion for the catch-all category? | 17:11 |
| *** eernst has quit IRC | 17:16 | |
| *** annabelleB has quit IRC | 17:22 | |
| *** annabelleB has joined #kata-dev | 17:26 | |
| kata-irc-bot | <raravena80> q: I guess related to the docs, do we have an on-boarding internal architecture doc? If not, I think it would be helpful for new contributors to understand the internals. This is a good example I saw from the Prometheus community: https://github.com/prometheus/prometheus/blob/master/documentation/internal_architecture.md | 17:46 |
| *** devimc_ has joined #kata-dev | 17:48 | |
| *** devimc has quit IRC | 17:50 | |
| *** sameo has joined #kata-dev | 17:51 | |
| *** eernst has joined #kata-dev | 18:18 | |
| *** annabelleB has quit IRC | 18:20 | |
| *** dklyle has quit IRC | 18:24 | |
| *** eernst has quit IRC | 18:32 | |
| *** eernst has joined #kata-dev | 18:35 | |
| *** eernst has quit IRC | 18:57 | |
| *** davidgiluk has quit IRC | 19:18 | |
| *** devimc_ has quit IRC | 19:36 | |
| *** devimc has joined #kata-dev | 19:36 | |
| *** jugs has quit IRC | 19:38 | |
| *** jugs has joined #kata-dev | 19:39 | |
| *** annabelleB has joined #kata-dev | 19:40 | |
| *** simosx has quit IRC | 19:53 | |
| *** dklyle has joined #kata-dev | 19:59 | |
| *** annabelleB has quit IRC | 20:22 | |
| *** annabelleB has joined #kata-dev | 20:25 | |
| *** annabelleB has quit IRC | 20:26 | |
| *** annabelleB has joined #kata-dev | 20:31 | |
| *** annabelleB has quit IRC | 21:20 | |
| *** annabelleB has joined #kata-dev | 21:20 | |
| *** annabelleB has quit IRC | 21:25 | |
| *** annabelleB has joined #kata-dev | 21:36 | |
| *** annabelleB has quit IRC | 21:40 | |
| *** annabelleB has joined #kata-dev | 21:43 | |
| kata-irc-bot | <anne> @raravena80 I think that would be great! Wanna write a first draft? ;) I think between video presentations, slide decks, and docs we have all the pieces, but I think a more concise summary of the architecture (with links to dive as deep as you want over here!) would be good | 21:49 |
| *** dklyle has quit IRC | 21:54 | |
| *** annabelleB has quit IRC | 22:00 | |
| *** devimc has quit IRC | 22:04 | |
| *** annabelleB has joined #kata-dev | 22:04 | |
| *** fuentess has quit IRC | 22:29 | |
| *** dklyle has joined #kata-dev | 22:31 | |
| kata-irc-bot | <raravena80> @anne sounds good, I'll take a first stab! | 22:46 |
| *** dklyle has quit IRC | 22:47 | |
| *** dklyle has joined #kata-dev | 22:48 | |
| *** annabelleB has quit IRC | 22:58 | |
| *** dklyle has quit IRC | 23:03 | |
| *** dklyle has joined #kata-dev | 23:04 | |
| *** fuentess has joined #kata-dev | 23:29 | |
| *** dklyle has quit IRC | 23:30 | |
| *** sameo has quit IRC | 23:30 | |
| *** sameo has joined #kata-dev | 23:44 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!