Earlier  
Posted Nick Remark
#openstack-nova - 2018-08-03
12:13:12 openstackgerrit Merged openstack/nova master: Docs: Add Placement to Nova system architecture https://review.openstack.org/584338
12:20:48 openstackgerrit Liam Young proposed openstack/nova master: Remove Neutron MetaAPIProxy from cellsv2-layout https://review.openstack.org/588525
12:30:53 openstackgerrit Surya Seetharaman proposed openstack/nova master: Cleanup comp_node, res_prov, services, aggregate_hosts during cell deletion https://review.openstack.org/546660
12:40:26 mriedem cfriesen: what was the reason for needing a POST /os-services API to create nova-compute services on a given host? https://github.com/starlingx-staging/stx-nova/commit/71acfeae0d1c59fdc77704527d763bd85a276f9a#diff-f3afe2522f9c92f5705f0ff5cf343865R246
12:40:36 mriedem which is also, btw, not multi-cell aware since it doesn't rely on the host mapping
12:44:49 mriedem sean-k-mooney: check this out https://github.com/starlingx-staging/stx-nova/commit/71acfeae0d1c59fdc77704527d763bd85a276f9a#diff-99e4b3f7232bf35155ff8b590b0ea589R44
12:47:18 sean-k-mooney mriedem: clicking but not sure i want too
12:47:30 sean-k-mooney haha
12:48:23 sean-k-mooney mriedem: that in the api. that is not a bad idea to be honest
12:49:12 sean-k-mooney mriedem: we dont document in the api that when using the libvirt dirview we detach all pci/sriov device on suspend which is hostile to a guest application that was uing them
12:49:26 sean-k-mooney pause would not detach the devices.
12:51:06 openstack Launchpad bug 1785246 in OpenStack Compute (nova) "Compute API reference should describe pause and suspend operations" [Medium,Confirmed]
12:51:06 mriedem sean-k-mooney: i know https://bugs.launchpad.net/nova/+bug/1785246
12:51:15 sean-k-mooney mriedem: we likely can do this where i wanted too in the snapshot case after talking to dansmith due to concern about data curroption by not flushing buffers but this seams ok
12:51:44 sean-k-mooney ya i was think about that yesterday after we were talking about it.
12:52:01 mriedem windriver could have just disabled the suspend/resume apis with policy
12:52:07 mriedem rather than change the behavior
12:52:24 sean-k-mooney its an impentation detail of the libvirt driver im not sure we should be leaking it through the api
12:52:39 sean-k-mooney that said we should document it
12:53:34 bauzas mriedem: hola
12:53:59 sean-k-mooney fried_rice: any idea if the ibm drivers detach pcidevices from the guest on suspend
12:54:13 bauzas mriedem: I was thinking on cherry-picking https://review.openstack.org/#/c/584204 (I mean, the series) to Queens
12:54:38 bauzas mriedem: you okay with it ?
12:55:25 fried_rice sean-k-mooney: I would only be able to answer for PowerVM, and... It's possible suspend is an operation we don't support. /me checks support matrix...
12:55:45 sean-k-mooney fried_rice: im looking at the intree driver now.
12:55:51 mriedem bauzas: no
12:56:02 mriedem RequestSpec.is_bfv is an rpc api bump
12:56:05 mriedem so not backportable
12:56:11 bauzas oh rightg
12:56:18 mriedem dansmith and i talked about that while he was writing the patch
12:56:56 sean-k-mooney mriedem: i might start working on that docs bug by the way but ill need stephenfin ect to check it since my written expression is not always well valid english :)
12:57:06 fried_rice sean-k-mooney: https://docs.openstack.org/nova/latest/user/support-matrix.html#operation_suspend_driver_powervm
12:57:24 mriedem sean-k-mooney: sure
12:57:42 mriedem i'm also not saying we should copy the libvirt description of those operations into the api,
12:57:47 mriedem if it's not the same behavior across virt drivers
12:59:23 sean-k-mooney mriedem: i agree but we should likely add a note for the different backends. https://docs.openstack.org/nova/latest/user/support-matrix.html#operation_suspend should proably have a note too
13:00:31 bauzas mriedem: for some reason, I missed https://review.openstack.org/#/c/580720/ in the series
13:00:35 bauzas my bad
13:08:38 sean-k-mooney interesting... the xenapi appears to just suspend. both hyperv and vspher end up delegating to there repective hyperviors suspend as a result this apears to only be a thing for libvirt.
13:12:24 fried_rice Anyone from HyperV around?
13:17:13 sean-k-mooney fried_rice: i guess not
13:17:26 sean-k-mooney brb going for lunch/coffee
13:17:28 fried_rice doesn't matter, I found what I needed.
13:19:29 openstackgerrit Merged openstack/nova master: Scrub hw:cpu_model from API samples https://review.openstack.org/588371
13:20:48 fried_rice stephenfin: Any justification for something like this https://review.openstack.org/#/c/588422/ ?
13:27:25 stephenfin fried_rice: Not that I'm aware of, anyway
13:27:35 stephenfin Purely a nice to hav
13:27:57 fried_rice stephenfin: ight, thanks for the look. I'm not opposed to approving the thing once they fix it, I guess.
13:28:05 stephenfin likewise
13:28:13 fried_rice Rather than saying it's a fin u cannot do (hint)
13:28:25 finucannot noted
13:28:39 finucannot :)
13:41:48 openstackgerrit Chris Dent proposed openstack/nova stable/queens: [placement] Retry allocation writes server side https://review.openstack.org/588569
13:41:57 openstackgerrit Eric Fried proposed openstack/nova master: [placement] Debug log per granular request group https://review.openstack.org/588350
13:42:18 openstackgerrit Stephen Finucane proposed openstack/nova stable/queens: Don't filter out sibling sets with one core https://review.openstack.org/588570
13:42:19 openstackgerrit Stephen Finucane proposed openstack/nova stable/queens: Ensure emulator threads are always calculated https://review.openstack.org/588571
13:42:20 openstackgerrit Stephen Finucane proposed openstack/nova stable/queens: Always pass 'NUMACell.siblings' to _pack_instance_onto_cores' https://review.openstack.org/588572
13:42:21 openstackgerrit Stephen Finucane proposed openstack/nova stable/queens: trivialfix: cleanup _pack_instance_onto_cores() https://review.openstack.org/588573
13:42:22 openstackgerrit Stephen Finucane proposed openstack/nova stable/queens: Add unit tests for EmulatorThreadsTestCase https://review.openstack.org/588574
13:42:23 openstackgerrit Stephen Finucane proposed openstack/nova stable/queens: Not use thread alloc policy for emulator thread https://review.openstack.org/588575
13:43:15 finucannot lyarwood: Fancy sticking those on your review queue? ^
13:44:00 lyarwood finucannot: sure thing
13:44:06 openstackgerrit Balazs Gibizer proposed openstack/nova master: Use placement 1.28 in scheduler report client https://review.openstack.org/583667
14:02:33 openstackgerrit Chris Dent proposed openstack/nova master: [placement] Move resource_class_cache into placement hierarchy https://review.openstack.org/584085
14:02:34 openstackgerrit Chris Dent proposed openstack/nova master: [placement] ensure_rc_cache only at start of process https://review.openstack.org/584086
14:26:12 openstack Launchpad bug 1785235 in OpenStack Compute (nova) "metadata retrieval fails when using a global nova-api-metadata service" [Undecided,In progress] - Assigned to Liam Young (gnuoy)
14:26:12 melwitt dansmith: do you understand this bug? says guests can't retrieve metadata from the metadata API with multiple cells https://bugs.launchpad.net/nova/+bug/1785235 cc gnuoy
14:27:26 dansmith well, I understand the words in the bug
14:27:30 melwitt I had thought guests retrieved metadata over http, not the MQ
14:27:31 cfriesen mriedem_afk: I think the idea was to allow a management layer to create a new compute node in the DB so that we can "disable" it, set up system-generated host aggregates, boot the node, do some health checks, then "enable" it once everything is ready.
14:27:46 dansmith I also understand that I'm going to -2 the code change
14:27:47 dansmith melwitt: of course they do,
14:27:49 melwitt okay. I didn't understand either
14:28:03 dansmith but they're saying that metadata service then doesn't hit the right db as a result
14:28:12 gnuoy yep
14:28:26 melwitt oh, I see
14:29:39 melwitt so, this method, or another one that we missed cell targeting in? https://github.com/openstack/nova/blob/master/nova/api/metadata/base.py#L677
14:30:04 dansmith melwitt: L692
14:30:46 melwitt right
14:31:16 melwitt okay
14:31:17 dansmith commented
14:32:31 gnuoy dansmith, I see context.target_cell getting called and adding the cells mq and db endpoints to cctxt
14:32:33 melwitt cool thanks
14:32:50 gnuoy but when the request executes those endpoints are ignored
14:33:23 dansmith gnuoy: did you open this bug?
14:33:26 gnuoy I did
14:33:45 dansmith gnuoy: please show some logs and config
14:34:15 gnuoy sure
14:36:40 dansmith gnuoy: are you running a standalone metadata server with cmd/api_metadata ?
14:38:24 gnuoy I am running a standalone metadata server. I don't follow the second part of the question
14:39:08 dansmith gnuoy: okay I think I see what's going on and why you want to make the change you're making
14:39:22 gnuoy ah, cool!
14:39:37 gnuoy dansmith, that change was a starter for 10, I'm happy to update it
14:39:46 dansmith gnuoy: so there are two ways to run metadata, either part of the regular api with enabled_apis=
14:40:06 dansmith and then with the standalone cmd/api_metadata thing which just starts up a standalone metadata server
14:40:19 dansmith the latter always forces the indirection api into place,
14:40:33 dansmith which was really intended for the case where you're running metadata on each compute node
14:40:34 gnuoy yep, I saw that
14:40:48 gnuoy ah
14:40:59 dansmith for the global case, you really should be running the regular api server, and just not enable the osapi api if you want to only run metadata

Earlier   Later