Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2019-02-15
09:27:12 gibi efried: I can add another note to the definition of the field but that note will be in a place that doesn't need to be changed when the actuall refactor adds the unnumbered group to the list so that note will be subject to drift
10:52:56 openstackgerrit Sylvain Bauza proposed openstack/nova master: WIP: Use the correct mdev allocated from the pGPU https://review.openstack.org/636591
10:52:56 openstackgerrit Sylvain Bauza proposed openstack/nova master: libvirt: implement reshaper for vgpu https://review.openstack.org/599208
10:52:57 openstackgerrit Sylvain Bauza proposed openstack/nova master: Add functional test for libvirt vgpu reshape https://review.openstack.org/631559
11:13:39 gibi jaypipes, efried: responded in https://review.openstack.org/#/c/616239 . I will respin the patch with some fixes you suggested
11:21:40 rha Is anybody here who could to a review on: https://review.openstack.org/#/c/420026 please?
12:58:37 openstackgerrit hyunsik Yang proposed openstack/nova stable/pike: Manage Compute services in nova manual typos https://review.openstack.org/637178
13:03:37 openstackgerrit Andrey Volkov proposed openstack/nova master: Check hosts have no instances for AZ rename https://review.openstack.org/509206
13:22:42 jaypipes rha: wow, >2 year old patch... sure, I'll take a look.
13:24:19 openstackgerrit Balazs Gibizer proposed openstack/nova master: Calculate RequestGroup resource provider mapping https://review.openstack.org/616239
13:24:20 openstackgerrit Balazs Gibizer proposed openstack/nova master: Fill the RequestGroup mapping during schedule https://review.openstack.org/619528
13:24:20 openstackgerrit Balazs Gibizer proposed openstack/nova master: Pass resource provider mapping to neutronv2 api https://review.openstack.org/616240
13:24:21 openstackgerrit Balazs Gibizer proposed openstack/nova master: Recalculate request group - RP mapping during re-schedule https://review.openstack.org/619529
13:24:21 openstackgerrit Balazs Gibizer proposed openstack/nova master: Send RP uuid in the port binding https://review.openstack.org/569459
13:24:22 openstackgerrit Balazs Gibizer proposed openstack/nova master: Test boot with more ports with bandwidth request https://review.openstack.org/573317
13:24:22 openstackgerrit Balazs Gibizer proposed openstack/nova master: Remove port allocation during detach https://review.openstack.org/622421
13:24:23 openstackgerrit Balazs Gibizer proposed openstack/nova master: Record requester in the InstancePCIRequest https://review.openstack.org/625310
13:24:23 openstackgerrit Balazs Gibizer proposed openstack/nova master: Add pf_interface_name tag to passthrough_whitelist https://review.openstack.org/625311
13:24:24 openstackgerrit Balazs Gibizer proposed openstack/nova master: Ensure that bandwidth and VF are from the same PF https://review.openstack.org/623543
13:24:24 rha jaypipes: Yeah, it has quite a history already :). Thanks!
13:24:24 openstackgerrit Balazs Gibizer proposed openstack/nova master: Support server create with ports having resource request https://review.openstack.org/636360
13:25:25 openstackgerrit Surya Seetharaman proposed openstack/nova master: API microversion 2.69: Handles Down Cells https://review.openstack.org/591657
13:25:26 openstackgerrit Surya Seetharaman proposed openstack/nova master: API microversion 2.69: Handles Down Cells Documentation https://review.openstack.org/635147
13:25:26 openstackgerrit Surya Seetharaman proposed openstack/nova master: Add context.target_cell() stub to DownCellFixture https://review.openstack.org/637182
13:25:58 jangutter rha: Ah, SIGHUP and how it seems to screw everyone over....
13:27:44 jaypipes gibi: ok, cool. my recommendation made sense then?
13:28:09 gibi jaypipes: renaming and func docing for sure, the actual algo change not so much
13:37:44 fried_rice o/
13:38:11 fried_rice gibi: I agree about the drift in that comment, but I feel like it's a chance worth taking, since it's SO non-obvious.
13:38:17 openstackgerrit Balazs Gibizer proposed openstack/nova master: Calculate RequestGroup resource provider mapping https://review.openstack.org/616239
13:38:17 openstackgerrit Balazs Gibizer proposed openstack/nova master: Fill the RequestGroup mapping during schedule https://review.openstack.org/619528
13:38:18 openstackgerrit Balazs Gibizer proposed openstack/nova master: Pass resource provider mapping to neutronv2 api https://review.openstack.org/616240
13:38:18 openstackgerrit Balazs Gibizer proposed openstack/nova master: Recalculate request group - RP mapping during re-schedule https://review.openstack.org/619529
13:38:19 openstackgerrit Balazs Gibizer proposed openstack/nova master: Send RP uuid in the port binding https://review.openstack.org/569459
13:38:19 openstackgerrit Balazs Gibizer proposed openstack/nova master: Test boot with more ports with bandwidth request https://review.openstack.org/573317
13:38:20 openstackgerrit Balazs Gibizer proposed openstack/nova master: Remove port allocation during detach https://review.openstack.org/622421
13:38:20 openstackgerrit Balazs Gibizer proposed openstack/nova master: Record requester in the InstancePCIRequest https://review.openstack.org/625310
13:38:21 openstackgerrit Balazs Gibizer proposed openstack/nova master: Add pf_interface_name tag to passthrough_whitelist https://review.openstack.org/625311
13:38:21 openstackgerrit Balazs Gibizer proposed openstack/nova master: Ensure that bandwidth and VF are from the same PF https://review.openstack.org/623543
13:38:22 openstackgerrit Balazs Gibizer proposed openstack/nova master: Support server create with ports having resource request https://review.openstack.org/636360
13:38:27 gibi fried_rice: I've added a NOTE :)
13:38:31 fried_rice thank you
13:38:36 fried_rice Did you rebase on latest master by chance?
13:39:02 gibi fried_rice: yes
13:39:05 fried_rice nice
13:39:16 gibi fried_rice: there was some merge conflict in the middle due to os-resource-classes
13:39:36 gibi now everything is shiny
13:39:42 fried_rice Sundar and I are working on cyborg stuff, and need to base it on your bottom couple of patches, and there was merge conflict on exactly that, so that'll clear it up for us. Thanks.
13:40:47 gibi fried_rice: yeah I saw that cyborg patches appeared on top of my series hope you can reuse some of my stuff
13:41:20 fried_rice gibi: that's the plan. I'm really glad you led the charge with that.
13:45:30 gibi fried_rice: cool
13:46:34 cdent feels like a nice rush of progress lately. exciting.
13:50:00 gibi let's break nova before the feature freeze ;)
13:50:21 cdent \o/
13:50:34 cdent breaking things is a great way to make things beter
13:55:26 bauzas please, no.
13:55:35 bauzas I was off most of this cycle because $bugs
13:56:03 gibi bauzas: we making your job security better :)
13:56:11 bauzas remember, when you say "it's good to merge first and then see bugs", some people are actually doing bugs
13:56:31 bauzas gibi: well, no
13:56:40 bauzas gibi: being off upstream is bad for me :(
13:56:59 bauzas of course, it's nice for our customers
13:57:36 bauzas but tbh, I prefer to be conservative and not have bugs because we tried to merge very quickly without verifying
13:57:53 bauzas so customers would be happy and *I* would be happy
13:57:56 gibi bauzas: do you have an overall feeling that openstack produced more bugs lately than before? or what changed is that you are more involved with customer support
13:58:21 bauzas for placement and instance groups ? surely
13:59:05 bauzas what folks don't know if that most of our customers were using Newton until 6 months ago
13:59:12 bauzas now they use Queens
13:59:21 cdent so clearly any changes we are making now aren't really all that relevant
13:59:36 bauzas cdent: until the next year, for sure
13:59:39 bauzas but then ?
13:59:59 bauzas unless you want me going to another company... /o\
14:01:34 gibi bauzas: do you see some missing test coverage what OpenStack should add to avoid some of your painfull bugs?
14:01:52 bauzas good question
14:02:37 bauzas what I know is that we have less people working on OpenStack
14:03:06 bauzas so, for example, if we have a problem, only a few from our team could help to fixing it
14:03:25 bauzas also, we have less operators testing OpenStack
14:03:44 bauzas so, somehow, it means that when we merge something, we discover bugs later
14:03:58 bauzas than previously
14:04:35 bauzas now, the real question is : if we were having better test coverage, would that be better ? oh yes, of course
14:04:42 bauzas but
14:04:50 bauzas we would still miss bugs
14:05:07 bauzas so at the end of the day, that would still impact us
14:06:24 gibi yeah, I feel the less people part too. Unfortunately half of the reason I'm paid to work on OpenStack is doing features, so I cannot just say no to feature work :/
14:07:06 bauzas of course
14:07:15 bauzas we're all paid by customers
14:07:26 bauzas I'm not saying no to features
14:08:28 bauzas tbc, I just provided my opinion now because it was looking that we were not thinking about what means us quickly merging things
14:08:41 kashyap bauzas: Not quite; less features, more on: maintainability, stability, robustness, performance (a feature)
14:08:43 bauzas the reshape series is a good example
14:08:55 bauzas I wish I could have worked earlier on it
14:08:56 kashyap And ... "don't fall apart if you sneeze", so on
14:09:25 bauzas so, now, I'm just triying to test a lot of things
14:09:41 bauzas to make sure we don't have problems
14:09:55 cdent I reckon things could be improved quite a bit if there was a closer tie between the code being worked on now and people using it so that there were more people making sure it was okay
14:09:58 bauzas anyway, back to https://review.openstack.org/#/c/636591/3/nova/virt/libvirt/driver.py
14:10:02 cdent that time-related disconnect is a problem
14:10:09 bauzas cdent: I agree with you
14:10:14 gibi cdent: true
14:10:23 cdent but it is also a problem that our systems are so complex (much of the time) that they are hard to test and experiment with

Earlier   Later