| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2020-02-05 | |||
| 12:45:07 | sean-k-mooney | ya so windows will see that as 8 to 12 cpu sockets with out default setting | |
| 12:45:30 | sean-k-mooney | the next thing to look at would be the graphics device model | |
| 12:45:38 | sean-k-mooney | you said you were on queens | |
| 12:45:41 | mriosfer | yes | |
| 12:45:59 | mriosfer | our nodes dont have pcie addtional graphic card just the integrated one by Dell | |
| 12:46:09 | sean-k-mooney | ya that is ok | |
| 12:46:44 | sean-k-mooney | on train+ would suggest using the virtio gpu but on queens you should set hw_video_model=qxl | |
| 12:47:18 | sean-k-mooney | i belive qxl is the best performing graphic device that qemu can emulate prior to support for virtio | |
| 12:47:28 | sean-k-mooney | https://github.com/openstack/glance/blob/master/etc/metadefs/compute-libvirt-image.json#L71-L84 | |
| 12:47:47 | sean-k-mooney | you could also use the hw_video_ram element to increase that | |
| 12:47:57 | sean-k-mooney | i belive it default to 64mb | |
| 12:48:07 | mriosfer | thath ram uses the instance ram no? | |
| 12:48:13 | sean-k-mooney | no | |
| 12:48:16 | sean-k-mooney | its addtional host ram | |
| 12:48:24 | mriosfer | oh , ok | |
| 12:48:41 | sean-k-mooney | it can only be set on the image if the flavor allows it by setting hw_video:ram_max_mb | |
| 12:49:25 | sean-k-mooney | i would start with the qxl video model and then if that is not enough after the cpu changes then increae the ram to say 128 or 256 | |
| 12:49:46 | mriosfer | sean do you know why error? https://gyazo.com/10156259f833a20decbdce821ef8e31b | |
| 12:50:06 | sean-k-mooney | yes | |
| 12:50:18 | sean-k-mooney | this is one of the model that is in the metadefs | |
| 12:50:24 | sean-k-mooney | so there is a drop down for it | |
| 12:50:32 | sean-k-mooney | use the filter box above | |
| 12:50:37 | sean-k-mooney | instead of a custom filed | |
| 12:51:21 | sean-k-mooney | our you can scoll down there should be a libvirt dropdown in the availabel metadata | |
| 12:51:47 | mriosfer | oh | |
| 12:51:56 | mriosfer | im fuck*** noob | |
| 12:52:09 | sean-k-mooney | the gui is "trying" to be help full | |
| 12:52:26 | sean-k-mooney | it actully really annoyed me when they added that "feature"] | |
| 12:52:46 | mriosfer | rebooting instance will apply the new changes? | |
| 12:52:52 | sean-k-mooney | no | |
| 12:52:55 | sean-k-mooney | unfortunetly not | |
| 12:53:05 | sean-k-mooney | you can only update the instnace with a rebuild | |
| 12:53:13 | sean-k-mooney | which would loose data on the root disk | |
| 12:53:18 | mriosfer | oh fuck | |
| 12:54:03 | sean-k-mooney | we make a copy of the data in the vm when we boot it so that it intentionall will not be affected by change in glance | |
| 12:54:19 | sean-k-mooney | if we did not you could break all your deployed vms with a typo | |
| 12:54:24 | sean-k-mooney | which would be bad | |
| 12:54:49 | sean-k-mooney | in your case once you are happy with the final image and its performace | |
| 12:55:02 | mriosfer | mmm maybe i can do a workarround at ceph level :) | |
| 12:55:04 | sean-k-mooney | you could do a db update to add the missing keys to the copy | |
| 12:55:42 | sean-k-mooney | then a hard reboot of the vm would fix it | |
| 12:56:20 | sean-k-mooney | i belive we store the instance image keys in the system_metadata table prefixed with img_ | |
| 12:56:28 | mriosfer | now looks much better the image : https://gyazo.com/cacf129fc79e2f1b23b607704b645d71 | |
| 12:56:59 | sean-k-mooney | yes but you will need to update the flaovr to have the hw_video_ram work | |
| 12:58:20 | sean-k-mooney | the reason being we did not want tenant to be abel to upload there own image and request 256GB of video ram | |
| 12:59:08 | mriosfer | do you also setup the Max vCPU threats and vCpu Cores at flavor level? | |
| 12:59:39 | sean-k-mooney | you dont need too but can | |
| 12:59:49 | sean-k-mooney | for the video ram it will hit this code https://github.com/openstack/nova/blob/a948a803b561606a892133940915caae610c080b/nova/virt/vmwareapi/vmops.py#L334-L338 | |
| 13:00:16 | mriosfer | that just for vmware no? | |
| 13:00:32 | sean-k-mooney | oh wrong file let me check the libvirt driver | |
| 13:00:43 | sean-k-mooney | vmware would reject it if the flavor is not set | |
| 13:01:44 | sean-k-mooney | ya its the same https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L5057-L5063 | |
| 13:01:57 | sean-k-mooney | i would just lave that out for now | |
| 13:02:21 | sean-k-mooney | as you would also have to update the embeded copy of the flavor or do a resize to pick up the change | |
| 13:02:56 | mriosfer | yes i will do for sure | |
| 13:02:58 | sean-k-mooney | if you find qxl and the toplogy chagne are not enough the try the ram change | |
| 13:03:14 | mriosfer | if it works i will send you a pack a beers! | |
| 13:03:59 | sean-k-mooney | ha :) well on other question is the slowness you are finding with the horizon console or do you still see that with rdp in the guest | |
| 13:04:13 | mriosfer | i see in the rdp guest | |
| 13:04:25 | stephenfin | bauzas: Assuming efried and dansmith aren't online yet, I think you ought to look at this and send it through so we can unblock neutron | |
| 13:04:26 | mriosfer | i dont recomend users work through horizon | |
| 13:04:29 | sean-k-mooney | right ok then ya this shoudl help | |
| 13:04:42 | stephenfin | We can use a follow-up if dansmith isn't happy with any of my answers | |
| 13:05:03 | sean-k-mooney | i have seen issue with novnc adding lag in the past | |
| 13:05:05 | bauzas | stephenfin: which change do you want me ? | |
| 13:05:12 | stephenfin | bauzas: oh, whoops https://review.opendev.org/#/c/705760 | |
| 13:05:20 | sean-k-mooney | not in recent times but i had to swap to spice at one point to work around it | |
| 13:05:41 | bauzas | ah | |
| 13:05:47 | bauzas | will look at it in 30 mins | |
| 13:05:53 | stephenfin | perfect, thanks :) | |
| 13:05:56 | sean-k-mooney | mriosfer: anyway hopefully that will help | |
| 13:06:12 | sean-k-mooney | im going to go get lunch | |
| 13:07:26 | mriosfer | yes be sure that yes at least much more than google | |
| 14:15:24 | gibi | stephenfin: I have a question in https://review.opendev.org/#/c/705784/1/nova/network/neutron.py@2662 | |
| 14:24:26 | bauzas | sean-k-mooney: efried: I'm currently writing a new revision for https://review.opendev.org/#/c/552924 given https://etherpad.openstack.org/p/mem_page_size_and_placement | |
| 14:24:40 | bauzas | sean-k-mooney: efried: and I'm a bit afraid about a possible issue | |
| 14:25:13 | bauzas | should we always ask for MEMORY_PAGE_SIZE_SMALL ? | |
| 14:25:37 | bauzas | I mean, if so, we won't get hosts not having NUMA topogilies | |
| 14:25:42 | bauzas | topologies | |
| 14:26:45 | bauzas | eg. a flavor with VCPU=2 and MEMORY_MB=4096 | |
| 14:27:24 | bauzas | (see https://etherpad.openstack.org/p/mem_page_size_and_placement L62) | |
| 14:31:04 | stephenfin | gibi: replied | |
| 14:31:16 | stephenfin | gibi: tl;dr: in theory yes, but I don't think we need to worry about it | |
| 14:31:22 | stephenfin | cos quotas | |
| 14:32:25 | dansmith | stephenfin: bauzas: replied in the neutron fix thing.. I didn't -1 and there was no need to hold it for me, I was just unsure (still am a little) but if it's right and works... | |
| 14:32:29 | gibi | stephenfin: OK, thanks | |
| 14:34:10 | efried | bauzas: Remember, these queries are only for flavors that *do* request a NUMA topology. | |
| 14:34:33 | bauzas | efried: ok, if so I was confused by L62 | |
| 14:34:45 | bauzas | and I agree with you | |
| 14:34:52 | efried | in the spec or the etherpad? | |
| 14:35:01 | bauzas | in the etherpad like I said | |
| 14:35:26 | bauzas | dansmith: ack, like I said, I'm not really a network expert so I was afraid you should have concerns | |
| 14:35:51 | efried | bauzas: Yeah, so best to confirm with sean-k-mooney, but I think if no page size is requested, you want to add MEMORY_PAGE_SIZE_SMALL, because that's the default today. | |
| 14:35:53 | bauzas | you at least know it better than me :) | |
| 14:36:04 | bauzas | efried: that's my point | |
| 14:36:15 | efried | bauzas: And no, you won't land on a host that doesn't have the NUMA split. But you weren't going to land there anyway, because segregation. | |
| 14:36:19 | bauzas | efried: if you don't ask for page sizes, we should call placement with this trait | |
| 14:36:30 | bauzas | we shouldn't* grah | |
| 14:36:30 | efried | yes | |
| 14:36:36 | efried | we *should* | |