Earlier  
Posted Nick Remark
#openstack-nova - 2020-10-23
08:50:09 deke997 anyone know more on this?
10:13:01 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Liberty database migrations https://review.opendev.org/758397
10:13:02 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Mitaka database migrations https://review.opendev.org/758398
10:13:02 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Newton database migrations https://review.opendev.org/759085
10:13:03 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Ocata database migrations https://review.opendev.org/759086
10:13:03 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Pike database migrations https://review.opendev.org/759087
10:13:04 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Queens database migrations https://review.opendev.org/759088
10:13:04 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Rocky database migrations https://review.opendev.org/759089
10:13:05 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Stein database migrations https://review.opendev.org/759090
10:13:05 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Train database migrations https://review.opendev.org/759091
10:32:56 recyclehero hey guys, I was referred here from my deploment method team OSA
10:33:15 recyclehero there is a problem with cpu allocation ratio
10:34:38 recyclehero at first as OSA was templating xxx_allocation_ratio it was normal that subsequent changes to aloocation ratio via palcement api get discarded
10:34:48 recyclehero but we did this patch
10:35:10 recyclehero https://review.opendev.org/#/c/758029/
10:36:07 recyclehero so we let xxx_allocation_ratios to be None
10:36:44 recyclehero then I have set inital_xxx_allocation_ratio to a floating number and did a clean deploy
10:37:26 recyclehero 1- in horizon I am seeing again the actual PCPU instead of VCPU. some people say this is the way it is and I am okay with that
10:38:13 recyclehero 2- using openstack resource cli I see the allocation ratio for cpu is equal to number tht I have set for initial_cpu_allocation_ratio
10:38:22 recyclehero but the problem is with *total*
10:38:56 recyclehero total is eqaul to 1*PCPU
10:41:14 recyclehero 3-I tried palcement api to put the inventory for the resource provider. its sucsess as I check just after with openstack resource provider inventory show. resource_provider_generation is also ++. then in a minute it gets overwritten and another generation++
10:41:52 recyclehero curl -XPUT -H 'X-Auth-Token: gAAAAABfkgravKJ1xAyjbHjY3hTy4wOMfufVKfafIIb5KUqcJufJ82mEIorUC_FwnOgHWX4uLDr_W22PHc28JouKhIknGkSJyP0dAPYa3DwFNA5dRgugMi9DcycwUPqLYoBQ3h6zv8M-VWCFFEJAuc-9ggV5ZTfkkB_vvXYDdd5dc765WhLZr2s' -H "Content-type: application/json" -d '{"inventories": {"MEMORY_MB": {"allocation_ratio": 2.0,"reserved": 1024,"total": 24014},"VCPU": {"allocation_ratio": 16.0,"reserved":
10:41:58 recyclehero 0,"total": 128}},"resource_provider_generation": 4}' 'http://172.29.236.11:8780/resource_providers/c8ac01e1-0b52-41f0-bd52-484070ea3aa9/inventories'
11:07:58 stephenfin recyclehero: 'cpu_allocation_ratio' applies only to VCPU; you can't overcommit PCPU
11:10:42 stephenfin Assuming you're talking about the different resource classes?
11:11:35 stephenfin To be clear, VCPU and PCPU are resource classes, along with DISK_GB, MEMORY_MB etc. Maybe you meant "total is equal to 1 * host CPUs?"
11:12:55 stephenfin recyclehero: the way that's supposed to work is that 'initial_*_allocation_ratio' will be used to set the initial ratios, allowing a user to overrides them manually using e.g. osc-placement. By comparison, '*_allocation_ratio' (no 'initial_' prefix) will always override whatever the user sets
11:14:35 stephenfin recyclehero: e.g. https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.cpu_allocation_ratio
11:34:43 stephenfin gibi: https://review.opendev.org/#/c/759114/ failed but it doesn't seem related; I guess we're good to remove that?
11:35:11 stephenfin assuming so, could you revisit https://review.opendev.org/#/c/749312/ and we can address the comments in a follow-up?
11:35:15 stephenfin *the follow-up
11:40:19 openstackgerrit Stephen Finucane proposed openstack/nova master: api-ref: Move 'os-agents' API to obsolete section https://review.opendev.org/755729
11:40:55 stephenfin lyarwood: Any chance you could close out the last two xenapi changes? https://review.opendev.org/#/c/749315/ https://review.opendev.org/#/c/755729/
11:41:25 stephenfin There's one more, but I think I've been too eager in removing stuff with it https://review.opendev.org/#/c/749316/
11:42:18 openstackgerrit Stephen Finucane proposed openstack/nova master: apidb: Compact Liberty database migrations https://review.opendev.org/759399
11:42:19 openstackgerrit Stephen Finucane proposed openstack/nova master: apidb: Compact Mitaka database migrations https://review.opendev.org/759400
11:42:19 openstackgerrit Stephen Finucane proposed openstack/nova master: apidb: Compact Newton database migrations https://review.opendev.org/759401
11:42:20 openstackgerrit Stephen Finucane proposed openstack/nova master: apidb: Compact Ocata database migrations https://review.opendev.org/759402
11:42:20 openstackgerrit Stephen Finucane proposed openstack/nova master: apidb: Compact Pike database migrations https://review.opendev.org/759403
11:42:21 openstackgerrit Stephen Finucane proposed openstack/nova master: apidb: Compact Queens database migrations https://review.opendev.org/759404
11:42:21 openstackgerrit Stephen Finucane proposed openstack/nova master: apidb: Compact Rocky database migrations https://review.opendev.org/759405
11:42:22 openstackgerrit Stephen Finucane proposed openstack/nova master: apidb: Compact Stein database migrations https://review.opendev.org/759406
11:47:00 lyarwood stephenfin: ack will try today, trying to finish some PoC stuff for the PTG next week
12:30:17 recyclehero stephenfin: its obvious one could not overcommit PCPUs.though I have problems with overcommiting vcpus
12:31:02 recyclehero and yes total is 1 * host cpus
12:31:44 recyclehero we have not defined cpu_allocation_ration which is equall to it being None.
12:32:06 recyclehero and set initial_cpu_allocation_ratio: 16
12:32:24 recyclehero I even used the api as I mentioned above.
12:32:46 recyclehero to be clear what is the value that is shown in horizon hypervisor dashboard?
12:34:48 sean-k-mooney recyclehero:are you using any falvor extra spec
12:35:37 sean-k-mooney recyclehero: also people have proposed overcommiting PCPUs in the past but we have rejected it so its obvious but not to eveyone :)
12:36:13 recyclehero i have 1000 cpus, deal with it nova! :D
12:36:44 sean-k-mooney :)
12:37:08 recyclehero I didnt understnd the flavor part? how is it related with me not having allocation_ratio*PCPU=VCPUs?
12:37:36 sean-k-mooney i was wondering was this related to schduling but your actully asking about horizon right
12:37:51 sean-k-mooney horizon pull its infor from the hypervios api
12:38:28 recyclehero aha so if I even be successful with overcommiting via placement I dont get to see it in horizon
12:39:59 sean-k-mooney https://docs.openstack.org/api-ref/compute/?expanded=list-hypervisors-details-detail,show-hypervisor-statistics-detail#list-hypervisors-details
12:40:21 sean-k-mooney so it s either hitting the details endpoint or the stats endpoint
12:40:35 sean-k-mooney in both cases it just reports the vcpus i belive
12:41:11 sean-k-mooney that value is not multiplied by the allocation ratio
12:41:27 recyclehero so its actually PCPUs right?
12:41:40 sean-k-mooney well no PCPUs are a different thing
12:41:45 recyclehero The number of vcpu in this hypervisor. This does not take allocation ratios used for overcommit into account so there may be disparity between this and the used count.
12:42:33 recyclehero "VCPU = PCPU - reserverd" or am I completely wrong
12:42:39 sean-k-mooney it either the number of cpus on the host or it the number of cpu in the host defined by the vcpu_pin_set or cpu_shared_set
12:42:58 sean-k-mooney recyclehero: its not calulated that way
12:43:39 sean-k-mooney if you use cpu_dedicated_set and dont defien cpu_shared_set then vcpu=0
12:44:33 sean-k-mooney if you use cpu_shared_set or vcpu_pin_set and dont use cpu_dedicated_set then pcpus are 0
12:45:59 recyclehero sean-k-mooney: aha, but actually I dont care what I see in horzion. I have 8 cores which I am seeing in horizon. I need 128 cores ready for allocation.
12:46:01 recyclehero https://docs.openstack.org/placement/latest/user/index.html
12:46:03 sean-k-mooney recyclehero: stephenfin has a short blog on the topic https://that.guru/blog/cpu-resources-redux/
12:46:42 sean-k-mooney recyclehero: by the way we normally don suggest setting allocation raitos over 4
12:46:59 sean-k-mooney im planning to push a patch to change the inital allcoation ration to 4 next week
12:47:14 sean-k-mooney ill be bringin it up at the ptg
12:47:21 sean-k-mooney but back to your issue
12:47:28 sean-k-mooney can you check what is set in placment
12:47:33 recyclehero ok 4 will even do. but I will be rather be typing virt command with allocation ratio 1
12:47:56 recyclehero how? api cli?
12:48:06 sean-k-mooney you can do it either way
12:48:16 sean-k-mooney there is an osc-placment plugin for the openstack client
12:48:23 sean-k-mooney so you can pip install that
12:48:56 sean-k-mooney openstack --os-placement-api-version 1.18 resource provider list
12:49:17 recyclehero openstack resource provider inventory show c8ac01e1-0b52-41f0-bd52-484070ea3aa9 VCPU
12:49:17 sean-k-mooney then openstack --os-placement-api-version 1.18 resource provider inventory show <uuid of host> VCPU
12:49:27 recyclehero allocation_ratio | 16.0
12:49:36 recyclehero total | 8
12:49:40 sean-k-mooney there you go
12:49:50 noonedeadpunk sean-k-mooney: oh, btw, if we're talking about this:) Is usage of initial_*_allocation_ratio can be considered as unified and recommended approach instead of *_allocation_ratio?
12:50:27 sean-k-mooney noonedeadpunk: it depends on if you want to manage it via config or api
12:50:54 sean-k-mooney noonedeadpunk: some operators like to commit there configuration to git so want to use *allocation_ratio
12:51:09 sean-k-mooney other want to manage it via the api so shoudl use initail_*
12:51:13 sean-k-mooney to set the defualt
12:51:29 sean-k-mooney that basically how you chose between them
12:51:38 noonedeadpunk sean-k-mooney: just of the docs it seems that the idea of initial was thet it can be stored in git but can be overriden in api?
12:51:54 noonedeadpunk ah, I guess I see what you mean...
12:52:14 sean-k-mooney noonedeadpunk: yes it will set the inital value in the config and then over write it
12:52:22 recyclehero noonedeadpunk: https://review.opendev.org/#/c/758029/ we have takeled with jrosser and came to this. there are 2 refrence to related documentaion part.
12:52:26 sean-k-mooney inital is only used when creating an inventory for the first time

Earlier   Later