| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2019-04-15 | |||
| 15:53:31 | sean-k-mooney | adrianc: if we did we would not need to heal the info cache | |
| 15:55:03 | openstackgerrit | Dan Smith proposed openstack/nova master: Add image type capability flags and trait conversions https://review.openstack.org/652710 | |
| 15:55:46 | openstackgerrit | Balazs Gibizer proposed openstack/nova-specs master: Server move operations with ports having resource request https://review.openstack.org/652608 | |
| 16:07:27 | openstackgerrit | Stephen Finucane proposed openstack/nova-specs master: Standardize CPU resource tracking https://review.openstack.org/555081 | |
| 16:07:47 | mriedem | bauzas: could take a look at these backports? https://review.openstack.org/#/q/topic:bug/1821594+branch:stable/rocky | |
| 16:11:33 | openstackgerrit | Merged openstack/nova stable/ocata: Update port device_owner when unshelving https://review.openstack.org/626413 | |
| 16:23:58 | sean-k-mooney | the periodic task is ment to heal all instance that need to be healed on each invocation right? | |
| 16:24:26 | sean-k-mooney | because if it is, that is not what it actully does | |
| 16:25:30 | sean-k-mooney | oh actully reading the doc string that was intentional? | |
| 16:31:11 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Enable test_volume_backed_live_migration in tempest https://review.openstack.org/528104 | |
| 16:37:58 | openstackgerrit | Merged openstack/nova stable/queens: Ignore VolumeAttachmentNotFound exception in compute.manager https://review.openstack.org/637391 | |
| 16:53:37 | tssurya | dansmith: about the power update event spec (https://review.openstack.org/#/c/636132/4/specs/train/approved/nova-support-instance-power-update.rst) whenever you have the time could you confirm the things discussed at L77 and L74 ? main concern being the notifications/action record requirement | |
| 16:53:43 | tssurya | thanks! :) | |
| 17:22:03 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Remove ComputeDriver.macs_for_instance method https://review.openstack.org/652737 | |
| 17:30:27 | pacharya | a quick question, does creation of a batch instance delete API fall under https://docs.openstack.org/nova/latest/contributor/project-scope.html#no-more-orchestration ? | |
| 17:31:45 | _erlon_ | Folks, Im trying to debug a failure on the instance creation on Nova, on a Pike release, but all I get is " Got no allocation candidates from the Placement API" and no explanation on what resource is lacking: | |
| 17:31:51 | _erlon_ | http://paste.openstack.org/show/749318/ | |
| 17:32:02 | _erlon_ | look at the placement API logs also does not help | |
| 17:32:53 | _erlon_ | I didn't had this problem before the placement API was introduced | |
| 17:32:53 | _erlon_ | what is the procudure now? | |
| 18:07:24 | mriedem | there was debug logging added to the placement GET /allocation_candidates code but i'm not sure it made it back to pike | |
| 18:07:38 | mriedem | jaypipes: ^? | |
| 18:10:22 | mriedem | _erlon_: https://review.openstack.org/#/q/If9ddb8a6d2f03392f3cc11136c4a0b026212b95b | |
| 18:10:42 | mriedem | and https://review.openstack.org/#/q/status:merged+project:openstack/nova+branch:master+topic:one-resource-per-query | |
| 18:10:48 | mriedem | that would take some work to get back to pike | |
| 18:11:12 | mriedem | _erlon_: how many computes do you have? | |
| 18:11:54 | mriedem | first thing to do would be to make sure there is a resource provider for each compute node | |
| 18:22:28 | openstackgerrit | Merged openstack/python-novaclient stable/rocky: Revert "Fix crashing console-log" https://review.openstack.org/650364 | |
| 18:22:29 | openstackgerrit | Merged openstack/python-novaclient stable/rocky: Add test for console-log and docs for bug 1746534 https://review.openstack.org/652033 | |
| 18:22:31 | openstack | bug 1746534 in python-novaclient "encoding error when doing console-log" [High,Fix released] https://launchpad.net/bugs/1746534 - Assigned to Thomas Goirand (thomas-goirand) | |
| 18:28:21 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Remove macs kwarg from allocate_for_instance https://review.openstack.org/652749 | |
| 18:33:08 | edleafe | vim | |
| 18:33:12 | edleafe | doh! | |
| 18:34:26 | sean-k-mooney | edleafe: password: | |
| 18:34:38 | sean-k-mooney | :) | |
| 18:35:43 | edleafe | too many windows open - now *that* would make an easy-to-remember password | |
| 18:37:27 | sean-k-mooney | im kind of sad the cirros passward is nolonger "cubswin:)" | |
| 18:37:45 | sean-k-mooney | anyway time for dinner | |
| 18:37:47 | sean-k-mooney | o/ | |
| 18:58:33 | _erlon_ | mriedem: only 1 | |
| 18:58:40 | _erlon_ | its a devstack node | |
| 19:00:02 | mriedem | _erlon_: oh, well, make sure it's reporting into placement with the correct inventory | |
| 19:00:15 | mriedem | https://docs.openstack.org/osc-placement/latest/cli/index.html#resource-provider-list | |
| 19:00:20 | mriedem | https://docs.openstack.org/osc-placement/latest/cli/index.html#resource-provider-inventory-list | |
| 19:00:34 | _erlon_ | mriedem: its a devstack node and should be working fine | |
| 19:00:46 | _erlon_ | I can like create up to 3 instances | |
| 19:00:59 | _erlon_ | the 4th fails for some reason | |
| 19:02:25 | mriedem | well, you can use ^ to see the inventory of the provider, | |
| 19:02:32 | mriedem | and https://docs.openstack.org/osc-placement/latest/cli/index.html#resource-usage-show to see the usage of the project which you used to create instances | |
| 19:02:42 | mriedem | and then see if there is any remaining capacity for the 4th instance you're trying to create | |
| 19:34:57 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Handle unsetting '[DEFAULT] dhcp_domain' https://review.openstack.org/652662 | |
| 19:34:57 | openstackgerrit | Matt Riedemann proposed openstack/nova master: conf: Undeprecate and move the 'dhcp_domain' option https://review.openstack.org/480616 | |
| 19:49:32 | mriedem | edleafe: error response status code question! https://review.openstack.org/#/c/645458/17/specs/train/approved/add-host-and-hypervisor-hostname-flag-to-create-server.rst@141 | |
| 19:50:01 | mriedem | do those still exist? | |
| 19:50:08 | edleafe | jink | |
| 19:50:11 | edleafe | jinx | |
| 19:50:16 | aspiers | we still have some | |
| 19:50:21 | aspiers | but I don't think they tend to work | |
| 19:50:30 | aspiers | unless you're a timelord | |
| 19:50:37 | jaypipes | _erlon_: did you find the answer to your query? | |
| 19:52:25 | artom | Just quick sanity check to be 100% sure, but the resource stats we provide in https://developer.openstack.org/api-ref/compute/?expanded=show-hypervisor-details-detail#show-hypervisor-details come from the resource tracker via the ComputeNode object, right? And specifically, not from placement? | |
| 19:52:31 | edleafe | mriedem: that's not really a response code question, is it? If the app logic is to let the scheduler pick, then 2xx. If you treat the value as missing, then 400 | |
| 19:53:02 | mriedem | edleafe: this one? "The new (``host`` and/or ``hypervisor_hostname``) and the old | |
| 19:53:02 | mriedem | (``az:host:node``) mechanisms are mutually exclusive. If both are specified | |
| 19:53:02 | mriedem | in the same request, the API will return a 409 HTTP Conflict error." | |
| 19:53:11 | mriedem | they are saying the api will return an error and we don't get to the scheduler | |
| 19:53:16 | mriedem | i'm just saying that's not a 409 | |
| 19:53:49 | edleafe | mriedem: huh, I clicked that link and L125 was front and center | |
| 19:54:01 | mriedem | artom: everything in the hypervisors api comes from the compute node yeah | |
| 19:54:08 | artom | mriedem, cheerS! | |
| 19:54:27 | edleafe | Yeah, that's not a 409. There's nothing conflicting about the state of the system and the request. It's just a bad request | |
| 19:55:41 | mriedem | artom: interestingly that API doesn't use the ComputeNode.stats object https://github.com/openstack/nova/blob/78e742662edd164c46382c31e106884762fed029/nova/db/sqlalchemy/api.py#L730 | |
| 19:55:58 | mriedem | https://github.com/openstack/nova/blob/78e742662edd164c46382c31e106884762fed029/nova/objects/compute_node.py#L81 | |
| 19:56:46 | mriedem | which is this happy thing https://github.com/openstack/nova/blob/78e742662edd164c46382c31e106884762fed029/nova/compute/stats.py | |
| 19:56:52 | artom | mriedem, should it? Looks like stats is an aggregate, while the hypervisors API is per node | |
| 19:57:41 | mriedem | i'd say my default answer to "should the hypervisors api have more detail in it" is "probably not' | |
| 19:58:22 | mriedem | https://developer.openstack.org/api-ref/compute/?expanded=#show-hypervisor-statistics is an aggregate yes | |
| 19:58:30 | artom | I meant "should it" as more of a "why would you expect it to?" | |
| 19:59:58 | artom | Oooo I know, let's have NUMA nodes as REST resources and provide an API to access /sys/devices/system/node/node0/meminfo | |
| 20:00:23 | mriedem | from the outside i'd expect an api that is called "statistics" to leverage a 'stats' field on that resource in the db | |
| 20:00:49 | mriedem | artom: i'm pretty sure there is an intel spec for that | |
| 20:00:59 | artom | *snerk* | |
| 20:03:17 | artom | "efried pto" Aha, that explains it ;) | |
| 20:04:18 | mriedem | mnaser: i saw you abandoned https://review.openstack.org/#/c/577933/ - is that because you don't need it anymore, or just don't have time to work on it? because i think a couple of people asked for the same thing and it's reasonable imo, probably just needs paperwork done and such (which someone could help with) | |
| 20:04:56 | mnaser | mriedem: I still think it's useful but I don't think I have the time to work on the paperwork and what not honestly | |
| 20:05:05 | mnaser | not right now, anyways | |
| 20:05:25 | mnaser | maybe I can restore and leave it with a "hey if you wanna pick this up, feel free to?" | |
| 20:06:10 | mriedem | i think the only question is about a stale hostId value in the config drive on an instance that is live migrated around | |
| 20:07:04 | mriedem | but for that matter the az value in the config drive could already be stale for the same reason | |
| 20:07:08 | artom | mriedem, didn't we specifically make a point of not updating device tag information on the config drive? | |
| 20:07:23 | artom | hostId could fall under the same argument - "if you need up to date info, use the API" | |
| 20:07:45 | mriedem | artom: i vaguely recall talking about punting on updating tags in the config drive because we just don't refresh the thing | |
| 20:08:02 | mriedem | we rebuild it in some cases (rebuild w/o shared storage, unshelve) | |
| 20:08:33 | artom | I believe we settled on something like "we won't update it for you, it'll get rebuilt when it gets rebuilt" | |
| 20:08:48 | mriedem | you get what you get and you don't throw a fit? | |
| 20:11:00 | mriedem | mnaser: i'll reach out to our downstream product team and see if they have a similar need for this | |
| 20:11:06 | artom | mriedem, basically - https://github.com/openstack/nova/blob/master/releasenotes/notes/virt-device-tagged-attach-53e214d3b3fdd183.yaml | |
| 20:11:38 | mnaser | mriedem: cool, want me to restore it? | |
| 20:11:52 | mriedem | mnaser: i can if i'm going to work on it | |
| 20:11:56 | mriedem | so don't bother | |