| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-02-09 | |||
| 09:36:54 | lyarwood | bauzas: I don't think it's a stable/core issue that the moment as I don't have +2 on that branch until after GA iirc ;) | |
| 09:37:12 | lyarwood | at the moment* | |
| 09:37:42 | bauzas | lyarwood: yeah, RC branch (which is not yet a stable branch) is having different gerrit permissions | |
| 09:38:20 | bauzas | nova cores can +2 on RC branch by default but not on stable branches | |
| 09:38:35 | bauzas | and that's the opposity for stable cores | |
| 09:40:54 | openstackgerrit | Lajos Katona proposed openstack/osc-placement master: Random names for functional tests https://review.openstack.org/542745 | |
| 09:44:02 | openstackgerrit | jichenjc proposed openstack/nova master: Avoid live mgirate to same host https://review.openstack.org/542689 | |
| 09:52:24 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/pike: Refine waiting for vif plug events during _hard_reboot https://review.openstack.org/542748 | |
| 09:53:11 | hrw | bauzas: thx for info. had no idea about stable|master core split | |
| 10:28:12 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/ocata: Refine waiting for vif plug events during _hard_reboot https://review.openstack.org/542767 | |
| 10:29:26 | hrw | so, anyone knows how to get service up after 'nova service-force-down' call? | |
| 10:29:45 | gibi | mriedem, gmann_: I also have some patches on the project config regarding the tempest-full job https://review.openstack.org/#/c/538908/ | |
| 10:41:16 | gibi | hrw: the API has a forced_down flag that you can set to false https://developer.openstack.org/api-ref/compute/#update-forced-down | |
| 10:41:29 | hrw | gibi: thx | |
| 10:41:57 | gibi | hrw: the nova client has a --unset flag to do that | |
| 10:42:32 | hrw | weird | |
| 10:43:00 | hrw | works ;D | |
| 10:43:09 | gibi | :) | |
| 10:43:45 | hrw | there should just be 'openstack service up' and 'openstack service down --force' ;D | |
| 10:46:33 | gibi | hrw: the service has an administrative state (enable/disable) and an operational state (up, down, forced_down) | |
| 10:47:22 | hrw | gibi: so 'openstack service up/down/enable/disable' with option --force for down? | |
| 10:48:29 | gibi | hrw: the operational state (up, down) are not settable as that is determined by the liveness of the service, except the forced_down that you can set from outside | |
| 10:56:00 | openstackgerrit | Stephen Finucane proposed openstack/nova master: TrivialFix: Add a space between messages https://review.openstack.org/541436 | |
| 10:58:29 | kashyap | stephenfin: If I may make a small nit-pick: I'd personally s/TrivialFix/"DB: sqlalchemy"/ (or some such), and call it out as a trivial fix in the commit _body_ | |
| 10:58:58 | kashyap | (Maybe you tag it as TriviaFix to prime reviewer's attention :-)) | |
| 10:59:02 | stephenfin | kashyap: Good point, but I didn't write that :) | |
| 10:59:11 | stephenfin | Just made a nit fix before merging | |
| 10:59:12 | kashyap | Ah! Gotcha | |
| 10:59:37 | kashyap | That's fine, let it merge now :-) | |
| 11:19:30 | openstackgerrit | Merged openstack/os-traits master: Updated from global requirements https://review.openstack.org/533994 | |
| 11:31:42 | hrw | http://logs.openstack.org/28/541728/10/check/build-openstack-sphinx-docs/31a2871/html/user/support-matrix.html looks nice | |
| 11:39:37 | tobasco | have an interesting issue on a mitaka cloud, doing a resize fails and os-brick runs "multipath -l" on a /dev/sdaX disk instead of a multipath so the resize fails | |
| 11:40:23 | tobasco | the instance is volume backed, has anybody seen anything similar being fixed in os-brick in newer versions? | |
| 11:41:36 | lyarwood | tobasco: `instead of a multipath so the resize fails` - I don't follow | |
| 11:42:03 | lyarwood | tobasco: and in any case the cinder folks are the best people to ask re os-brick questions like this | |
| 11:42:27 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/ocata: Refine waiting for vif plug events during _hard_reboot https://review.openstack.org/542767 | |
| 11:45:38 | tobasco | lyarwood: the argument to the multipath cmd should be a multipath device, i will take it in #cinder thanks | |
| 11:45:48 | hrw | bauzas: can you look at https://review.openstack.org/#/c/541728/ patch again? zuul generated docs already | |
| 11:46:28 | lyarwood | tobasco: iirc path devices are also valid, but yeah check with #openstack-cinder | |
| 11:48:46 | openstackgerrit | Chris Dent proposed openstack/nova master: [placement] use simple FaultWrapper https://review.openstack.org/533752 | |
| 11:49:26 | tobasco | lyarwood: ah might be true, i will investigate some more, sorry for spam | |
| 11:50:42 | openstackgerrit | Chris Dent proposed openstack/nova master: WIP: Refactor WSGI apps and utils to limit imports https://review.openstack.org/533797 | |
| 12:26:00 | openstackgerrit | Lajos Katona proposed openstack/osc-placement master: Random names for functional tests https://review.openstack.org/542745 | |
| 12:28:03 | openstackgerrit | Merged openstack/python-novaclient master: Fix crashing console-log https://review.openstack.org/541610 | |
| 12:29:26 | openstackgerrit | Merged openstack/nova master: Remove redundant call to add_instance_fault_from_exc in rebuild_instance https://review.openstack.org/539011 | |
| 13:14:15 | openstackgerrit | Merged openstack/nova master: Allow force-delete even if task_state is not None https://review.openstack.org/530879 | |
| 13:20:46 | openstackgerrit | Merged openstack/nova master: test_compute_mgr: fix couple of unit tests https://review.openstack.org/539973 | |
| 13:20:57 | openstackgerrit | Merged openstack/nova master: Remove unnecessary variables https://review.openstack.org/541964 | |
| 13:21:09 | openstackgerrit | Merged openstack/nova master: update docstring param description https://review.openstack.org/541519 | |
| 13:21:17 | openstackgerrit | Merged openstack/nova master: doc: fix the link for the evacuate cli https://review.openstack.org/542508 | |
| 13:21:26 | openstackgerrit | Merged openstack/nova master: Fix grammar error https://review.openstack.org/542733 | |
| 13:21:35 | openstackgerrit | Merged openstack/nova master: fix link https://review.openstack.org/541675 | |
| 13:21:44 | openstackgerrit | Merged openstack/nova master: trivial: Fix microversion number in test comment https://review.openstack.org/542019 | |
| 13:30:00 | openstackgerrit | Bence Romsics proposed openstack/osc-placement master: PUT dict format to /allocations (v1.11, v1.12) https://review.openstack.org/542819 | |
| 13:36:13 | fried_rice | leakypipes: Gooood morning. | |
| 13:37:28 | cdent | edleafe: a while back you were thinking hard about https://bugs.launchpad.net/nova/+bug/1719933 . Did you make any conclusions? Should we bother, or can we kill that bug? | |
| 13:37:30 | openstack | Launchpad bug 1719933 in OpenStack Compute (nova) "placement server needs to retry allocations, server-side" [Medium,Triaged] - Assigned to Jay Pipes (jaypipes) | |
| 13:37:34 | fried_rice | leakypipes: Let me know when's good to do that aggregate distance talk. I'm free for the next hour, and then from 11-4 ET | |
| 13:37:35 | cdent | I guess you left a thing on the PTG etherpad. | |
| 13:37:56 | cdent | moin | |
| 13:41:53 | leakypipes | fried_rice: let's do 11am | |
| 13:42:06 | fried_rice | leakypipes: Roger that. | |
| 13:42:42 | fried_rice | cdent, edleafe, stephenfin, cfriesen, sean-k-mooney: ^ FYI. I'll be taking notes and writing something up after the fact in any case. | |
| 13:43:22 | cdent | fried_rice++ | |
| 13:43:57 | sean-k-mooney | fried_rice: just read scoll back | |
| 13:44:16 | sean-k-mooney | * reading | |
| 13:44:48 | fried_rice | sean-k-mooney: Not much scrollback - I'm going to get a brain dump from leakypipes on "modeling [anti-]affinity via aggregate distance" in 2.25h | |
| 13:45:14 | bauzas | oh fuuuuuu | |
| 13:45:15 | sean-k-mooney | Ah ok | |
| 13:45:21 | bauzas | Friday FTW | |
| 13:45:29 | fried_rice | sean-k-mooney: This is related to our NUMA discussions the other day, so I tagged you cause you might be interested to join. But if not, I'll be producing something written for you to consume after. | |
| 13:46:50 | sean-k-mooney | i would definetly like to understand how aggregate distance works as i only understand the distance along the tree approch and dont know how to connect the 2 or even if they are compatible | |
| 13:47:23 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/pike: Encode libvirt domain XML in UTF-8 https://review.openstack.org/542831 | |
| 13:47:43 | sean-k-mooney | fried_rice: also i still own you some advanced flavours | |
| 13:48:11 | fried_rice | sean-k-mooney: Heh, yeah, that pastebin from the other day is still on my pile to look at and quiz you about. | |
| 14:05:53 | figleaf | cdent: re: https://bugs.launchpad.net/nova/+bug/1719933 - we agreed that the issue is more complex than simply retrying, hence the PTG discussion | |
| 14:05:55 | openstack | Launchpad bug 1719933 in OpenStack Compute (nova) "placement server needs to retry allocations, server-side" [Medium,Triaged] - Assigned to Jay Pipes (jaypipes) | |
| 14:07:09 | cdent | thanks figleaf. I couldn't remember if there wasn't perhaps a chance for a "meh, nevermind" | |
| 14:07:54 | figleaf | fried_rice: 10am CST? | |
| 14:08:05 | fried_rice | figleaf: Yes | |
| 14:08:11 | figleaf | cdent: it may very well end up being "meh" | |
| 14:08:35 | figleaf | fried_rice: I can join the discussion at that time | |
| 14:08:44 | fried_rice | coo | |
| 14:13:29 | figleaf | cdent: I added a comment to that bug in case anyone else has memory issues | |
| 14:13:40 | cdent | thanks | |
| 14:39:41 | finucannot | fried_rice: Sure thing. If you want, ping me beforehand so I don't forget :) | |
| 14:39:51 | openstackgerrit | Matt Riedemann proposed openstack/nova stable/pike: doc: fix the link for the evacuate cli https://review.openstack.org/542856 | |
| 14:39:54 | fried_rice | finucannot: Will do | |
| 14:42:11 | hrw | mriedem: morning | |
| 14:42:12 | fried_rice | sean-k-mooney: What's the proper terminology to say that a NIC (or pf) is "in" a given NUMA node? | |
| 14:43:03 | fried_rice | sean-k-mooney: So like, a NUMA node encompasses a certain portion of the system's CPUs and RAM, and also there's some kind of bus connection to NIC slots that makes it more efficient to use that NIC than the other. | |
| 14:45:07 | sean-k-mooney | fried_rice: generally we say the nic has a numa affinity to numa node x | |
| 14:45:16 | fried_rice | sean-k-mooney: Thanks | |
| 14:46:22 | sean-k-mooney | fried_rice: what that actully means is for a DMA or MMIO capable device the memory adress allocated to that device are from the adress range associated to numa node X | |
| 14:46:33 | fried_rice | sean-k-mooney: Dig | |
| 14:48:08 | fried_rice | Is master Rocky now? | |
| 14:48:10 | fried_rice | mriedem: ^ | |
| 14:48:23 | sean-k-mooney | cpus get numa affinity because they are phyically closer to one memory controler then the rest. so address form that controler(numa node) can be loaded into cache faster then form a remote numa node | |
| 14:48:45 | fried_rice | sean-k-mooney: Phew, that gels with my (admittedly extremely limited) understanding. | |
| 14:49:41 | fried_rice | sean-k-mooney: And for PCI devices, there's something about the bus that goes to that particular I/O slot that makes the same kind of communication faster. | |