| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-08-29 | |||
| 11:58:23 | kosamara | jaypipes: I think a sentence spilled over | |
| 11:58:35 | jaypipes | kosamara: crap. | |
| 11:58:45 | kosamara | I'm doing a change inline | |
| 11:59:53 | openstackgerrit | Jay Pipes proposed openstack/os-traits master: clean up CUDA traits https://review.openstack.org/597170 | |
| 12:00:00 | jaypipes | kosamara: done :) | |
| 12:03:57 | openstackgerrit | Konstantinos Samaras-Tsakiris proposed openstack/os-traits master: clean up CUDA traits https://review.openstack.org/597170 | |
| 12:04:20 | kosamara | jaypipes: ok? | |
| 12:05:11 | jaypipes | kosamara: ty sir! | |
| 12:05:25 | jaypipes | kosamara: I must have badly fat-fingered the copy-paste in vim! :) | |
| 12:06:40 | kosamara | haha! | |
| 12:42:08 | openstackgerrit | Chris Dent proposed openstack/nova master: DNM: [placement] Make _ensure_aggregate context not independent https://review.openstack.org/597486 | |
| 12:53:40 | moshele | mriedem: can you review https://review.openstack.org/#/c/595592/ ? we update the macvtap and SR-IOV CIs with the rx_queue_size/tx_queue_size and they both passing with this patch | |
| 12:56:45 | zigo | I'm currently trying to validate Rocky Debian packages. | |
| 12:57:09 | zigo | Got no allocation candidates from the Placement API. This could be due to insufficient resources or a temporary occurrence as compute nodes start up. select_destinations /usr/lib/python3/dist-packages/nova/scheduler/manager.py:150 | |
| 12:57:09 | zigo | When I try to boot a new instance, I got the scheduler spitting in the logs: | |
| 12:57:15 | zigo | What should I look into then? | |
| 12:57:29 | zigo | I normally do have enough resources on that machine ... | |
| 12:57:39 | zigo | jaypipes: ^ Help ? :) | |
| 12:58:15 | zigo | Is there a placement client somehow? | |
| 13:04:17 | openstackgerrit | Chen proposed openstack/nova master: Fix filter server list with SOFT_DELETED status https://review.openstack.org/597443 | |
| 13:15:26 | cdent | zigo: there's an osc-placement plugin for the openstack client | |
| 13:15:43 | cdent | zigo: did you do a discover_hosts? | |
| 13:16:18 | cdent | but more likely it sounds like your compute node hasn't reported resources yet | |
| 13:16:40 | cdent | 'openstack resource provider list' might work | |
| 13:16:46 | zigo | cdent: It's puppet-openstack that I'm running, so normally, yeah ... | |
| 13:16:48 | cdent | s/work/provide some insight/ | |
| 13:16:54 | zigo | Thanks, trying. | |
| 13:17:03 | zigo | cdent: So, I should package that osc-placement in Debian then? | |
| 13:17:04 | mriedem | https://docs.openstack.org/osc-placement/latest/cli/index.html#resource-provider-list | |
| 13:17:21 | mriedem | packaging osc-placement would be nice for anyone that wants to deploy nova yeah | |
| 13:17:36 | mriedem | scheduling in nova has been critically dependent on placement since ocata | |
| 13:18:05 | mriedem | if this is a single-node setup, there should be 1 resource provider for the compute node | |
| 13:18:14 | zigo | discover_host was ran, so that's not the issue. | |
| 13:18:37 | zigo | I'm doing the packaging right away for placement client. | |
| 13:19:20 | zigo | Why was it called osc-placement, rather than python-placementclient btw? | |
| 13:19:40 | mriedem | b/c it's an openstack client plugin | |
| 13:19:43 | mriedem | and that's the naming convention | |
| 13:19:50 | mriedem | it's not a python API binding / sdk type thing like novaclient | |
| 13:20:11 | zigo | mriedem: So it will be renamed once placement is extracted from Nova? | |
| 13:20:15 | mriedem | no | |
| 13:20:22 | mriedem | it's only cli, not any python bindings | |
| 13:20:48 | zigo | ok | |
| 13:20:50 | mriedem | there is no python binding client for placement, maybe openstacksdk is working on one, would have to ask mordred or edleafe | |
| 13:24:11 | mriedem | i don't see a placement dir in the sdk yet https://github.com/openstack/openstacksdk/tree/master/openstack | |
| 13:24:15 | mriedem | not sure about plans for one though | |
| 13:26:02 | zigo | FYI, I don't bother doing py2 clients anymore. :) | |
| 13:27:46 | zigo | sphinx>=1.2.1,!=1.3b1,<1.4 # BSD <--- test-requirements.txt needs upgrade ... | |
| 13:27:47 | zigo | :P | |
| 13:36:20 | mriedem | test-reqs in osc-placement? | |
| 13:36:52 | zigo | yep | |
| 13:37:18 | mriedem | please report a bug https://bugs.launchpad.net/placement-osc-plugin | |
| 13:38:02 | edleafe | mriedem: AFAIK that is not being worked on | |
| 13:38:27 | mriedem | edleafe: yeah i didn't see any open reviews | |
| 13:43:20 | openstackgerrit | Matt Riedemann proposed openstack/osc-placement master: Random names for functional tests https://review.openstack.org/542745 | |
| 13:45:48 | openstack | Launchpad bug 1789649 in placement-osc-plugin "test-requirements out of date" [Undecided,New] | |
| 13:45:48 | zigo | https://bugs.launchpad.net/placement-osc-plugin/+bug/1789649 | |
| 13:45:56 | mriedem | zigo: thanks | |
| 13:46:59 | zigo | mriedem: Now that I have the package built and installed, how do I test if placement has resources ? | |
| 13:47:14 | mriedem | as an admin, | |
| 13:47:17 | mriedem | openstack resource provider lst | |
| 13:47:18 | mriedem | *list | |
| 13:47:56 | zigo | Ok, found my host, then? | |
| 13:48:00 | zigo | Show it? | |
| 13:48:24 | mriedem | inventory is more useful | |
| 13:48:25 | zigo | Hum... not much thing shows up then... | |
| 13:48:36 | mriedem | openstack resource provider inventory show <rp_uuid> | |
| 13:48:40 | mriedem | oh wait | |
| 13:48:46 | mriedem | openstack resource provider inventory list <rp_uuid> | |
| 13:48:52 | mriedem | https://docs.openstack.org/osc-placement/latest/cli/index.html#resource-provider-inventory-list | |
| 13:49:06 | mriedem | you should see VCPU, MEMORY_MB and DISK_GB | |
| 13:49:40 | zigo | http://paste.openstack.org/show/729051/ | |
| 13:49:40 | zigo | It works... | |
| 13:49:52 | zigo | But then? How come placement didn't find resources? | |
| 13:50:08 | mriedem | let's make sure the compute node in nova is matching that same uuid | |
| 13:50:13 | mriedem | from nova cli, | |
| 13:50:15 | mriedem | as admin, | |
| 13:50:20 | mriedem | nova hypervisor-list | |
| 13:50:51 | zigo | I see my host, and it's up and enabled. | |
| 13:50:59 | zigo | I did all this before asking! :P | |
| 13:51:03 | mriedem | does it's id equal f9716941-356f-4a2e-b5ea-31c3c1630892 ? | |
| 13:51:10 | zigo | Yup. | |
| 13:51:29 | mriedem | ok what type of flavor did you use when you tried creating the server? | |
| 13:51:32 | zigo | Is it normal that I get allocation_ratio 0.0 for all resources? | |
| 13:51:41 | mriedem | so, | |
| 13:51:54 | mriedem | that sounds exactly like the same problem the xenserver CI guys are having in the ML right now | |
| 13:51:57 | mriedem | and no, | |
| 13:52:01 | mriedem | cpu should be 16.0, | |
| 13:52:02 | zigo | 256 RAM, 5 GB HDD, 1 VCPU | |
| 13:52:05 | mriedem | ram and disk should also be > 0 | |
| 13:52:14 | mriedem | jaypipes: efried: naichuans: ^ | |
| 13:53:49 | mriedem | zigo: using libvirt right? | |
| 13:54:24 | zigo | mriedem: Yeah, normal qemu in a virtualbox right now. | |
| 13:54:38 | zigo | mriedem: Also using it in the OpenStack CI with puppet-openstack stuff ... | |
| 13:55:15 | zigo | mriedem: Is there a way to force something in the allocation_ratio to fix things? | |
| 13:55:36 | mriedem | yes via osc-placement, but i'd have to look it up quick | |
| 13:56:10 | mriedem | https://docs.openstack.org/osc-placement/latest/cli/index.html#resource-provider-inventory-class-set | |
| 13:56:57 | mriedem | so: openstack resource provider inventory class set --allocation_ratio 16.0 --total 4 f9716941-356f-4a2e-b5ea-31c3c1630892 VCPU | |
| 13:57:45 | mriedem | cdent: ever remember talking about making allocation_ratio a minimum of 1.0 in placement? | |
| 13:57:52 | mriedem | allowing anything to set that to 0.0 seems like a bad idea | |
| 13:59:00 | gibi | mriedem: having < 1.0 could make sense for handling overhead, but I agree that 0.0 doesn't make sense | |