Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-11-30
00:23:49 mriedem with cells v2 yeah there is just a flat scheduler
00:23:55 mriedem which is multi-cell aware starting in pike
00:25:11 mriedem my brain is getting fried and i can already hear my wife getting mad because i'm in my office after 6pm,
00:25:30 mriedem but i'm not sure if https://review.openstack.org/#/c/436648/ makes a significant difference in the decision to run per-cell placement or not in ocata
00:25:50 mriedem because the nova-scheduler in each cell in ocata would only query computes from the cell db it's configured for
00:26:06 mriedem so placement might say there are 1000 computes that could satisfy a request, but only 100 of those might be in the cell db that that cell knows about
00:26:16 mriedem which is this https://github.com/openstack/nova/blob/stable/ocata/nova/scheduler/host_manager.py#L579
00:26:46 mriedem so i think global placement is still ok in ocata (still not sure why belmiro wanted per-cell placement, would have to read the notes again)
00:28:03 mgagne alright, I guess it addresses my concern. would need to test for sure but I get the idea
00:29:01 mriedem i put more notes about this in https://etherpad.openstack.org/p/cellsv1-to-v2-migration
00:29:09 mriedem would need dansmith to confirm my thinking, but i think global placement would be fine
00:29:58 dansmith we get the host list from placement in ocata IIRC, so I think its' the same as pike
00:30:01 mriedem given that plus the catalog issue, i think global placement would be the way to go unless i'm missing something
00:30:10 dansmith but I am also rather fried for the day
00:30:14 mriedem right, we get the host list from placement in ocata,
00:30:23 mriedem and then get the compute nodes from the uuids placement returned https://etherpad.openstack.org/p/cellsv1-to-v2-migration
00:30:25 mriedem oops
00:30:28 mriedem https://github.com/openstack/nova/blob/stable/ocata/nova/scheduler/host_manager.py#L579
00:30:36 mriedem which in ocata are just for the cell that the scheduler has access to
00:30:43 mriedem but, that's fine, it's just an IN query
00:30:50 mriedem yo'ud get the subset that the child cell db knows about
00:31:13 mriedem the inefficiency would be on the placement side
00:31:18 dansmith it's still going to return all the nodes in the system from the placement call
00:31:22 dansmith and make a massive SQL query
00:31:39 mriedem that's no different in pike though
00:31:45 dansmith that's what I said
00:31:58 mriedem heh, yeah
00:32:14 mriedem well, shit, let's just add a cell mapping to placement, i'm sure cdent and edleafe and jaypipes would be on board with that
00:32:54 mriedem with a grenade, we're both going to die right?
00:32:58 mriedem in close proximity
00:33:05 dansmith if I let go
00:33:07 dansmith that's the idea
00:33:26 mgagne can those details be added to the etherpad? like you should be running global placement. it will return all UUIDs of all compute nodes but scheduler will filter them out. And there are plans to optimize that.
00:33:46 mriedem mgagne: i added something along those lines in the pros/cons sections for global vs local placement
00:33:51 mriedem might not be coherent at this point
00:33:59 mgagne ok, I didn't fully understand what it meant ^^'
00:34:01 mriedem dansmith: i just like the idea of saying we should do that and watching heads explode
00:35:00 mriedem mgagne: probably need some kind of summary section
00:35:10 mgagne yea
00:35:44 mgagne perfect
00:36:51 mgagne I think we should make it clear which use case is addressed: placement with cellsv1 vs cellsv2
00:38:02 mgagne I think the summary section is good. does it apply to newton too?
00:38:23 mriedem newton scheduler didn't talk to placement
00:38:28 mriedem i think, have to check
00:38:32 mgagne oooooh
00:38:34 mgagne so...
00:39:14 mgagne placement in newton, compute reports resources but nothing is consuming from placement?
00:39:32 mriedem mgagne: correct
00:39:44 mriedem https://docs.openstack.org/releasenotes/nova/ocata.html
00:39:44 mgagne holy cow
00:39:50 mriedem "The Nova FilterScheduler driver is now able to make scheduling decisions based on the new Placement RESTful API endpoint that becomes mandatory in Ocata. "
00:40:10 mriedem and in ocata, the scheduler only starts asking placement once all compute are upgraded
00:40:16 mriedem knowing they are reporting in to placement
00:40:25 mgagne well, if i'm upgrading to newton, I might not read ocata release notes (yet) =)
00:40:27 mriedem mgagne: it's done that way for rolling upgrades
00:40:38 mriedem that's why we do a min service version check
00:40:48 mgagne awesome news then
00:41:00 mriedem dansmith: yeah she poked her head in here about 2 minutes after i said htat
00:41:06 mgagne finally understood something today :D
00:41:30 dansmith mriedem: mmhmm, I can hear her from oregon
00:41:34 mriedem mgagne: https://github.com/openstack/nova/blob/stable/ocata/nova/scheduler/filter_scheduler.py#L169
00:42:04 mriedem she sent our daughter in to yell at me
00:42:10 mriedem so ttyl
00:42:40 mgagne I'm off for today too, have a good one. thanks for all the explanations!
01:04:25 openstackgerrit Jackie Truong proposed openstack/python-novaclient master: Microversion 2.56 - Add trusted_image_certificates https://review.openstack.org/500396
01:08:16 openstackgerrit Jackie Truong proposed openstack/python-novaclient master: Microversion 2.56 - Add trusted_image_certificates https://review.openstack.org/500396
01:30:30 Kevin_Zheng mriedem, Hi, what is the -1 for in https://review.openstack.org/#/c/523653/ ? I saw that you are suggesting to make change on manager.py in a follow up patch
01:30:41 mriedem not a follow up patch,
01:30:44 mriedem a preceeding patch
01:30:53 mriedem your patch introduces a bug
01:32:13 Kevin_Zheng Ah, OK, got it.
01:37:06 openstackgerrit Matt Riedemann proposed openstack/nova master: Assert that we restrict cold migrations to the same cell https://review.openstack.org/524035
01:38:17 mriedem takashin: i split this test out into it's own patch https://review.openstack.org/#/c/524027/
01:38:24 mriedem and added this https://review.openstack.org/#/c/524035/1
01:44:36 openstackgerrit Matt Riedemann proposed openstack/nova master: Enable cold migration with target host(2/2) https://review.openstack.org/408964
01:44:37 openstackgerrit Matt Riedemann proposed openstack/nova master: Assert that we restrict cold migrations to the same cell https://review.openstack.org/524035
01:44:37 openstackgerrit Matt Riedemann proposed openstack/nova master: Add multi-cell negative test for cold migration with target host https://review.openstack.org/524027
01:45:07 openstackgerrit Naichuan Sun proposed openstack/nova master: xenapi(N-R-P):Get vgpu info from `allocations` https://review.openstack.org/521717
01:56:04 openstackgerrit Matt Riedemann proposed openstack/nova master: Enable cold migration with target host(2/2) https://review.openstack.org/408964
01:56:05 openstackgerrit Matt Riedemann proposed openstack/nova master: Assert that we restrict cold migrations to the same cell https://review.openstack.org/524035
01:56:05 openstackgerrit Matt Riedemann proposed openstack/nova master: Add multi-cell negative test for cold migration with target host https://review.openstack.org/524027
02:00:57 openstackgerrit Andreas Karis proposed openstack/nova master: Fixes 'Not enough available memory' log message https://review.openstack.org/524038
02:01:39 Kevin_Zheng mriedem: for your comment on https://review.openstack.org/#/c/523653/ , we have a instance uuid lock here, if directly call _shelve_offload_instance might be a problem ? https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L4637
02:03:27 mriedem Kevin_Zheng: that was added for a race tempest was hitting https://github.com/openstack/nova/commit/e285eb1a382e6d3ce1cc596eeb5cecb3b165a228
02:03:37 mriedem Kevin_Zheng: you could do the same instance lock in the periodic task when calling _shelve_offload_instance
02:04:04 Kevin_Zheng Ah, right, I'm so stupid...
02:16:25 openstackgerrit Takashi NATSUME proposed openstack/nova master: [placement] Fix foreign key constraint error https://review.openstack.org/516880
02:19:14 openstackgerrit Naichuan Sun proposed openstack/nova master: xenapi(N-R-P):Get vgpu info from `allocations` https://review.openstack.org/521717
02:25:15 openstackgerrit Huan Xie proposed openstack/nova master: XenAPI: Don't use nicira-iface-id for XenServer VIF https://review.openstack.org/451641
02:46:16 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Modify _poll_shelved_instances periodic task call _shelve_offload_instance() https://review.openstack.org/524047
03:26:22 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Modify _poll_shelved_instances periodic task call _shelve_offload_instance() https://review.openstack.org/524047
05:23:37 openstackgerrit Naichuan Sun proposed openstack/nova master: xenapi(N-R-P):Get vgpu info from `allocations` https://review.openstack.org/521717
06:36:35 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Modify _poll_shelved_instances periodic task call _shelve_offload_instance() https://review.openstack.org/524047
07:03:26 Guest72929 >>> youtube.com/watch?v=X8qL6cAI0zQ
07:34:35 openstackgerrit Takashi NATSUME proposed openstack/nova master: [placement] Fix an error message in API validation https://review.openstack.org/524088
07:38:05 openstackgerrit Merged openstack/nova master: Enable cold migration with target host(2/2) https://review.openstack.org/408964
08:32:48 openstackgerrit Takashi NATSUME proposed openstack/nova master: [placement] Add functional tests for traits API https://review.openstack.org/524094
08:34:56 openstackgerrit Takashi NATSUME proposed openstack/nova master: Fix 500 error while passing 4-byte unicode data https://review.openstack.org/407514
08:35:15 openstackgerrit Takashi NATSUME proposed openstack/nova master: [cellv2] Improve getting BDMs in multiple cells https://review.openstack.org/521400
08:35:57 openstackgerrit Takashi NATSUME proposed openstack/nova master: Fix missing marker functions https://review.openstack.org/514579

Earlier   Later