Earlier  
Posted Nick Remark
#openstack-nova - 2018-10-08
10:33:17 vrobert Hi, I realized my nova-api-os-compute (17.04.dev1) uwsgi processes are slowing down if I get the console logs from a VM in horizon for example or running tempest test: tempest.api.compute.admin.test_hypervisor.HypervisorAdminTestJSON.test_get_hypervisor_uptime. I found that nova-compute process on my compute nodes just doing epoll: do_poll (eventlet/hubs/epolls.py:62). Is it a normal behavior?
10:33:34 vrobert http://paste.openstack.org/show/731677/
11:08:47 openstackgerrit Merged openstack/os-traits master: Removed older version of python added 3.5 https://review.openstack.org/606370
11:10:06 openstackgerrit sean mooney proposed openstack/os-vif master: Add abstract OVSDB API https://review.openstack.org/476612
11:16:25 mdbooth_ I'm seeing a weird py35 db migrations failure in unit tests. Is everybody else seeing it, too?
11:31:18 openstackgerrit Merged openstack/python-novaclient master: Update the contributor guide https://review.openstack.org/606926
11:38:43 sean-k-mooney mdbooth: havnt run them lately. i can try check what tests?
11:47:15 sean-k-mooney damb moxs is kindof obnoxious when it comes to letting you know its depercated in the tox output.
11:47:51 sean-k-mooney mdbooth: i dont have py35 installed but tox -e py36 -- db passed with master
11:57:36 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/os-vif master: Add native implementation OVSDB API https://review.openstack.org/482226
12:09:30 mdbooth sean-k-mooney: Sorry, disconnected. Failures in CI. I can't reproduce locally.
12:09:42 mdbooth My guess is upstream pip snafu
12:10:02 sean-k-mooney ah ok
12:18:07 mdbooth So, 158 hits on that error in the last 2 days
12:18:44 mdbooth Nothing before Saturday
12:19:55 mdbooth sean-k-mooney: I added you to https://review.openstack.org/#/c/608416/1 btw ;)
12:20:03 mdbooth As it was your recommendation
12:21:12 mdbooth Oh, ^^^ is not true. Kibana was just being slow. There have been a steady stream of hits on that error.
12:23:37 sean-k-mooney nice to have a backup power supply for your house for such things
12:24:15 mdbooth bauzas: Cool
12:24:35 bauzas the previous meter wasn't counting the electricity :p
12:24:36 mdbooth Ah, so it seems I can't reproduce that error locally because it's auto skipped if mysql isn't configured
12:24:45 jangutter_ is there a way to obtain a permalink to a particular comment in gerrit?
12:24:47 mdbooth bauzas: Why would you want to change that?
12:25:06 bauzas mdbooth: because I don't want to pay a lot :p
12:25:15 mdbooth jangutter_: I think so, yes.
12:25:31 bauzas mdbooth: now the meter is connected https://www.enedis.fr/linky-communicating-meter
12:25:33 mdbooth jangutter_: I believe you can link to a particular line of code in a particular patch, anyway.
12:25:45 mdbooth jangutter_: So if the comment is against a line of code then I think you can link to that
12:25:51 bauzas mdbooth: so my electrical provider knew that since 23/08 there were 0 Kwh :p
12:26:05 mdbooth bauzas: That's just because you were so thrifty
12:26:27 bauzas :)
12:26:34 bauzas I wanted to run a local DC
12:26:38 bauzas but meh
12:26:44 bauzas I don't have A/C
12:26:55 jangutter_ mdbooth: thanks, that's good enough for now, I'll see if I can find out if there's a way to link to a particular message.
12:27:48 sean-k-mooney jangutter: i dont think there is
12:28:13 stephenfin jangutter: If there is, let us know
12:28:27 jangutter sean-k-mooney, in fact, I wanted to ask you about this: https://review.openstack.org/#/c/567148/7/specs/rocky/approved/vrouter-hw-offloads.rst@127 :-p
12:28:49 mdbooth So, it looks to me as though the db sync unit test is just occasionally taking too long and timing out
12:28:56 mdbooth So a non-deterministic unit test failure
12:29:11 sean-k-mooney jangutter: im reviewing https://review.openstack.org/#/c/607610/1/specs/stein/approved/generic-os-vif-offloads.rst currently but happy to talk about that
12:29:38 jangutter sean-k-mooney, no worries, when you're done, we can discuss.
12:29:57 sean-k-mooney jangutter: im just starting so easy to context switch now
12:30:14 mdbooth The test is taking at least 11 minutes
12:30:22 mdbooth Anybody know what the timeout is on a single unit test?
12:30:46 mdbooth http://logs.openstack.org/17/608417/4/check/openstack-tox-py35/5bffa0f/job-output.txt.gz#_2018-10-07_19_04_19_880167
12:31:56 openstackgerrit Merged openstack/python-novaclient master: Follow up "Fix up userdata argument to rebuild" https://review.openstack.org/607800
12:31:57 openstackgerrit Merged openstack/python-novaclient master: Update the CLI reference https://review.openstack.org/606871
12:32:09 sean-k-mooney jangutter: so the VIFPortProfileOVSRepresentor port profile you wanted to disucss its future?
12:32:25 stephenfin ralonsoh: One nit in https://review.openstack.org/#/c/605422/, if you're working on stuff
12:33:06 jangutter sean-k-mooney: yeah, basically the "option 2". I.e. what do you think should the abstraction layer be for offloads.
12:33:17 ralonsoh stephenfin: I'll submit the modified patch in 5 mins
12:33:40 sean-k-mooney jangutter: well for a start VIFPortProfileOVSRepresentor today does not contain any offload metadata at all
12:33:41 jangutter sean-k-mooney: the current review might be "option 3" then :-p
12:34:19 jangutter sean-k-mooney: it contains the PCI address of the repr?
12:34:23 sean-k-mooney jangutter: it contins info for how to attach the datapane to ovs but no info about offloads
12:34:37 sean-k-mooney jangutter: that is not offload metadata as far as im concserned
12:34:43 jangutter sean-k-mooney: yeah, "plugging" more than "hey set these TC flows".
12:35:03 sean-k-mooney jangutter: right so is your intent to enable the later or the former
12:35:28 jangutter sean-k-mooney: the former, this is to make plugging more generic.
12:35:35 sean-k-mooney well tc flows is also wrong
12:36:02 jangutter sean-k-mooney: been staring at the words "offload" too long so it kinda lost its meaning in my mind.
12:36:03 sean-k-mooney enable TSO or LSO is a offload
12:36:32 sean-k-mooney * offload metadata
12:36:53 jangutter sean-k-mooney: You can also enable or disable TC offloads (and if you want to be really specific, choosing the TC dataplane for OVS, with the offloaded option and then plugging into the resulting SR-IOV VF).
12:37:32 sean-k-mooney jangutter: yes but TC offloads are not flows e.g. they do not change where a packet is sent
12:37:43 jangutter sean-k-mooney: na-ah, they can.
12:38:22 sean-k-mooney tc flows can but its not an offload if send the packet to new york instad of sydney
12:39:34 sean-k-mooney jangutter: that is what i ment by choosing where its send not is this done in software or hadware
12:39:43 jangutter sean-k-mooney: it is an offload if the packet is encapped in a vxlan tunnel before it goes to NY :-p
12:39:51 mdbooth Folks, when running gertty for the first time, how many years should you wait for the UI to become responsive?
12:40:10 openstackgerrit Yikun Jiang proposed openstack/nova master: Remove the allocation ratios adjusting logic https://review.openstack.org/602805
12:40:10 openstackgerrit Yikun Jiang proposed openstack/nova master: Use new ``initial_xxx_allocation_ratio`` CONF https://review.openstack.org/602804
12:40:20 sean-k-mooney jangutter: no it would have been encapulated in software without the offload and set there in ether case
12:40:21 jangutter sean-k-mooney: but yeah, I take your point, my semantics is all wrong.
12:41:50 jangutter sean-k-mooney: so, I guess there's at least one action point for me: at least s/offloads/plugging modes/ in many respects on the spec.
12:42:03 sean-k-mooney jangutter: so back to what you acatully want to achive. im fine with haveing a generic port forifle that carries the data plane info for represntors
12:42:28 jangutter sean-k-mooney: and keep the OVS representor profile as is?
12:42:29 sean-k-mooney if we want to allow offload config the it has to be at the port level only.
12:42:51 sean-k-mooney jangutter: well that depend on if you want to do offload config
12:42:57 sean-k-mooney or how
12:43:20 sean-k-mooney the thing is the generic represtor port profile should not know anything about ovs
12:43:47 sean-k-mooney so if we have to enable an offload in a ovs specific way then that should not be in the generic profile
12:44:12 jangutter sean-k-mooney: yep.... you do realise it's making more of Jay's case for him :-p
12:44:33 sean-k-mooney if we have some traits like thing we can use as an indirection and have the driver interperate that then thats fine
12:45:12 jangutter sean-k-mooney: but I understand what you mean, the distinction between offload metadata and plugging modes should be separate.
12:45:19 sean-k-mooney jangutter: not really i just said storing backend sepcific metadata in the generic represtor profile would not be ok
12:45:27 sean-k-mooney that include via compostion
12:45:39 sean-k-mooney jangutter: ya
12:46:30 jangutter sean-k-mooney: cool, so you had in mind "add one more class" not "convert one more class to a random bag of dicts"...
12:46:48 sean-k-mooney yes
12:47:21 sean-k-mooney random bag of dicts that will some day be sent over api is less then ideal
12:47:37 jangutter sean-k-mooney: verily.
12:48:35 jangutter sean-k-mooney: thanks very much, will archive this review as a warning to future developers.
12:48:56 sean-k-mooney im fine with VIFPortProfileOVSRepresentor having no addtional field and inheriting from VIFPortProfileRepresentor by the way
12:49:28 jangutter sean-k-mooney: that won't work, unfortunately, will have to be multiple inheritance.
12:49:37 sean-k-mooney the thing is right now we dont have any offload metadata that we are sending so the pluggins modes info is all that class contains
12:49:44 fried_rice mdbooth: I set up gertty during the PTG and it took like three days before it finished loading everything down.
12:49:54 sean-k-mooney jangutter: oh why?

Earlier   Later