| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2019-04-24 | |||
| 14:06:24 | efried | edleafe: cool, gtk | |
| 14:13:14 | mriedem | efried: want to hit the easy gerrit cherry pick button to put this in stable/stein? https://review.opendev.org/#/c/654457/ | |
| 14:13:19 | openstackgerrit | Rodolfo Alonso Hernandez proposed openstack/os-vif master: Prevent "qbr" Linux Bridge from replying to ARP messages https://review.opendev.org/655332 | |
| 14:13:43 | efried | mriedem: I'm 42 minutes ahead of you. | |
| 14:13:51 | mriedem | ah didn't notice b/c the tb changed | |
| 14:13:57 | efried | tb? | |
| 14:14:02 | mriedem | topic branch | |
| 14:14:19 | mriedem | the gerrit ui appends an annoying branch specifier in the backports | |
| 14:14:21 | efried | oh. That's weird | |
| 14:14:36 | efried | I'll pay attention to that from now on and fix it. | |
| 14:24:14 | openstackgerrit | Eric Fried proposed openstack/nova master: Fix mock specs set to strings https://review.opendev.org/655455 | |
| 14:24:14 | openstackgerrit | Eric Fried proposed openstack/nova master: Hacking N363: Don't use spec[_set]='string' https://review.opendev.org/650370 | |
| 14:24:32 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Prepare _heal_allocations_for_instance for nested allocations https://review.opendev.org/637954 | |
| 14:24:33 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: pull out functions from _heal_allocations_for_instance https://review.opendev.org/655457 | |
| 14:24:33 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: nova-manage: heal port allocations https://review.opendev.org/637955 | |
| 14:24:34 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: pull out put_allocation call from _heal_* https://review.opendev.org/655459 | |
| 14:24:34 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: reorder conditions in _heal_allocations_for_instance https://review.opendev.org/655458 | |
| 14:24:46 | efried | melwitt: FYI since we talked about this a couple weeks ago: I fixed the Mock(spec='string') things ---^ and put the patch for the hacking rule on top of it | |
| 14:30:25 | efried | kashyap: You have a lot of support for https://review.opendev.org/#/c/645814/ -- if you add some words about when/how you're going to use the information (which I still don't know from outside conversations - fail spawn? fail to start n-cpu?) I'll fast approve if that's okay with sean-k-mooney | |
| 14:31:20 | efried | aspiers: I'm removing SEV from the PTG agenda, since it's approved \o/ | |
| 14:31:21 | sean-k-mooney | ya im fine with that. | |
| 14:31:28 | efried | thx | |
| 14:31:42 | kashyap | efried: Yeah, it's the top-2 item on my TODO, will add it by tomm, that okay? | |
| 14:31:49 | kashyap | If not for this traits yak, I would have done it today | |
| 14:31:57 | efried | kashyap: wfm | |
| 14:32:07 | efried | kashyap: IMO more important than traits yak | |
| 14:32:18 | efried | but of course I would say that because it eases my PTG schedule pain :P | |
| 14:32:29 | sean-k-mooney | ideally it would be nice to log the cpu basleing that was calulated + the flags form the cpu model and config and indicate what flag was incompatable. then kill the agent but we can discus that in the implementation | |
| 14:32:45 | kashyap | efried: Yesterday, I was about to add a quick note that: "Ack, will address this once I finish addressing the Secure Boot comments" | |
| 14:32:59 | kashyap | (The SB spec took a lot more time, too) | |
| 14:33:13 | sean-k-mooney | effectivly if nova can detect via libvirt that its incomatible we shoudl also tell the operator why so that they dont need to figure it out themselves | |
| 14:33:21 | kashyap | sean-k-mooney: Yeah. Let's hash it out when I actually get to implement it | |
| 14:33:27 | jaypipes | efried: ack, got it. thx! | |
| 14:33:56 | efried | jaypipes: Since parlayed into a draft agenda, see ML. | |
| 14:34:06 | efried | (which may be where you were coming from in the first place) | |
| 14:37:22 | kashyap | efried: On your question on that spec about 'where to fail' -- I'm thinking currently 'spawn'. Will add words to the spec | |
| 14:37:32 | efried | kashyap: Perfect, thanks. | |
| 14:37:44 | efried | I don't actually have a stake in what the answer is - I just want to see one :) | |
| 14:39:03 | efried | So it be like, "Before this wonderful feature, the instance might fail to come alive, but nova wouldn't know anything was wrong. Now we can fail the spawn operation, putting the instance in ERROR state, with a helpful log message indicating which bits are a problem." | |
| 14:44:12 | openstackgerrit | Stephen Finucane proposed openstack/nova-specs master: Standardize CPU resource tracking https://review.opendev.org/555081 | |
| 14:46:48 | kashyap | efried: Hehe, noted | |
| 15:04:24 | melwitt | efried: ack | |
| 15:24:43 | mriedem | lyarwood: re getting the ceph job voting, we might consider disabling the ssh validation (which is on by default in tempest) to avoid spurious failures http://logs.openstack.org/06/641806/12/check/devstack-plugin-ceph-tempest/7fc39ec/testr_results.html.gz - ssh failing is something with networking breaking down, not really anything that should be a result of a ceph backend for storage | |
| 15:24:47 | mriedem | it'd also make the job fast | |
| 15:24:48 | mriedem | *faster | |
| 15:25:32 | mriedem | lyarwood: i also posted https://review.opendev.org/#/c/655452/ earlier today | |
| 15:30:20 | openstackgerrit | Stephen Finucane proposed openstack/nova-specs master: Standardize CPU resource tracking https://review.opendev.org/555081 | |
| 15:31:30 | lyarwood | mriedem: ack sounds and looks good, where's the best place to track devstack-plugin-ceph-tempest result trends btw? | |
| 15:31:57 | mriedem | here is a patch to disable the ssh validation https://review.opendev.org/655472 | |
| 15:32:05 | mriedem | there is a graph that is out of date, sec | |
| 15:32:17 | mriedem | http://grafana.openstack.org/d/-iKINcImz/ceph-failure-rate?orgId=1 | |
| 15:32:39 | mriedem | https://opendev.org/openstack/project-config/src/branch/master/grafana/ceph.yaml needs fixing to fix that graph | |
| 15:32:51 | mriedem | otherwise i think melwitt might be tracking ceph job failure rates somewhere | |
| 15:33:53 | lyarwood | kk, I can take a look at fixing the graph if there's not another way | |
| 15:34:24 | melwitt | I've been tracking via eyeball because I keep forgetting how to get the graph that shows the comparison with the tempest-full job | |
| 15:34:40 | mriedem | that's what that graph above is for, but it's broken | |
| 15:35:00 | melwitt | haha. I can also try to fix it | |
| 15:35:05 | mriedem | first it was broken by the ceph job renames, but now i think it's broken b/c of some zuulv3 thing, i had talked with corvus about it before but don't remember what needs fixing now | |
| 15:36:38 | mriedem | looking for one more core for this functional recreate test patch https://review.opendev.org/#/c/641521/ | |
| 15:37:02 | mriedem | then i can claim victory on merging 4/47 patches of my cross-cell series while it was in runways for 2 weeks | |
| 15:42:02 | stephenfin | mriedem: I thought my cells-v1 series was big... I won't get to it tonight but I can look at that tomorrow morning | |
| 15:43:07 | stephenfin | (assuming no one gets to it before me) | |
| 15:43:59 | mriedem | thanks | |
| 15:44:00 | openstackgerrit | Matt Riedemann proposed openstack/nova stable/pike: Move legacy-grenade-dsvm-neutron-multinode-live-migration in-tree https://review.opendev.org/640207 | |
| 15:44:11 | efried | I would like to get some os-traits-y people (edleafe jaypipes) to scrutinize, esp. to make a ruling on whether/how we should do the split I suggested. | |
| 15:44:11 | efried | kashyap: I just did a thorough look at https://review.opendev.org/#/c/655193/ | |
| 15:44:32 | edleafe | efried: buried in meetings etc until the afternoon | |
| 15:44:52 | kashyap | efried: /me looks; (while adding words to the other spec, so as to reduce your PTG scheduling workload :-)) | |
| 15:45:32 | openstackgerrit | Matt Riedemann proposed openstack/nova stable/pike: Move legacy-grenade-dsvm-neutron-multinode-live-migration in-tree https://review.opendev.org/640207 | |
| 15:45:58 | kashyap | efried: Eagle eyes there! On "stibp" | |
| 15:46:00 | efried | kashyap: No hurry on my end | |
| 15:46:19 | kashyap | I missed to add it, due to all these subtle acronyms | |
| 15:47:13 | efried | 171 @item @code{stibp} | |
| 15:47:13 | efried | 159 @item @code{spec-ctrl} | |
| 15:47:13 | efried | 148 @item @code{pcid} | |
| 15:47:13 | efried | 136 @node important_cpu_features_intel_x86 | |
| 15:47:13 | efried | kashyap: If it helps, I distilled that web page | |
| 15:47:14 | efried | 194 @item @code{pdpe1gb} | |
| 15:47:14 | efried | 182 @item @code{ssbd} | |
| 15:47:15 | efried | 260 @item @code{ibpb} | |
| 15:47:15 | efried | 248 @node important_cpu_features_amd_x86 | |
| 15:47:16 | efried | 283 @item @code{virt-ssbd} | |
| 15:47:16 | efried | 272 @item @code{stibp} | |
| 15:47:17 | efried | 313 @item @code{amd-no-ssb} | |
| 15:47:17 | efried | 299 @item @code{amd-ssbd} | |
| 15:47:18 | efried | 325 @item @code{pdpe1gb} | |
| 15:47:35 | kashyap | efried: You actually read the source I lnked. It makes me happy that someone actually read it :D | |
| 15:48:35 | kashyap | Thanks for the handy posting here. | |
| 15:49:32 | mgoddard | mriedem: did you see my response re placement? | |
| 15:50:00 | kashyap | efried: Ah-ha, I missed 'stibp' because it was very recently added (21 March), and it isn't present in the HTML rendering | |
| 15:50:15 | efried | oh, interesting | |
| 15:50:19 | kashyap | [https://qemu.weilnetz.de/doc/qemu-doc.html#important_005fcpu_005ffeatures_005famd_005fx86] | |
| 15:50:20 | jaypipes | efried: what does "AMD x86 hosts" mean w.r.t. Spectre/Meltdown? I thought it was an Intel-only architectural problem that was being exploited? | |
| 15:50:32 | mriedem | mgoddard: i did now, thanks | |
| 15:50:46 | efried | jaypipes: I haven't a clue. kashyap --^ | |
| 15:50:51 | mgoddard | mriedem: np | |
| 15:50:53 | kashyap | jaypipes: Not really; you fell for AMD's marketing :D | |
| 15:51:21 | kashyap | jaypipes: Meltdown is an Intel-only thing | |
| 15:51:30 | kashyap | jaypipes: Spectre affects both AMD _and_ Intel. | |
| 15:52:34 | jaypipes | kashyap: I didn't fall for anything... I was just asking a question :) | |