Earlier  
Posted Nick Remark
#openstack-nova - 2018-02-23
08:23:12 sahid https://review.openstack.org/#/c/539605/
08:24:00 sahid they address important use cases related to NFV
08:57:07 bauzas good morning Nova
08:57:16 Spazmotic Morning bauzas
08:57:38 Spazmotic Any cores that could pu this on their radar for this week? https://review.openstack.org/#/c/538415/ Been sitting for about 3 weeks now.
08:59:16 Spazmotic I am back from Korea btw, good to see you all again.
08:59:55 bauzas Spazmotic: most of the folks are preparing to travel for the PTG
09:00:08 bauzas maybe you could ask for reviewing after the next week ?
09:00:12 Spazmotic Yeah I know it, just hoping to get some eyes on it I guess
09:00:17 bauzas today, I'll look at specs
09:03:44 Spazmotic But asking is about all that I can do for now, and would remiss if I didn't do it :)
09:07:51 bauzas sure, just explaining
09:08:54 Spazmotic Yeah I understand of course :D
09:39:09 openstackgerrit Lajos Katona proposed openstack/nova master: WIP: ServerMovingTests with custom resources https://review.openstack.org/497399
09:44:56 ttsiouts johnthetubaguy: Goodmorning, are you around?
09:48:35 johnthetubaguy ttsiouts: I am
09:48:52 openstackgerrit Arvind Nadendla proposed openstack/nova-specs master: Support traits in Glance https://review.openstack.org/541507
09:51:12 ttsiouts johnthetubaguy: Hello! :) we were thinking about the second call to placement
09:51:38 johnthetubaguy ttsiouts: what was the plan before, just returning what you had previously fetched from placement?
09:52:40 ttsiouts johnthetubaguy: hmmm if the freeing of the resources is successful then we can call placement for a second time.
09:53:00 ttsiouts we chose to form the response in the service just to save time
09:53:15 ttsiouts and not having to trigger placement again..
09:53:31 johnthetubaguy ttsiouts: I think that proxy is bad really, you don't know what microversion nova wants to ask for, etc
09:53:48 johnthetubaguy ttsiouts: simpler to tell Nova if you were successful or not
09:54:39 ttsiouts johnthetubaguy: Great. I'll do that.
09:55:14 johnthetubaguy ttsiouts: I think its worth doing a cheaky import of your client in there for now, or a link to the code at least, just so its possible to follow the breadcrumbs
09:56:04 ttsiouts johnthetubaguy: yes, seems better
09:56:44 ttsiouts johnthetubaguy: what do you think is better? an api call or importing the service?
09:56:53 johnthetubaguy ttsiouts: cool, getting back to the spec updates (oils delete key)
09:57:06 johnthetubaguy ttsiouts: I quite like the API call, copying vendor data
09:57:35 openstackgerrit Surya Seetharaman proposed openstack/nova-specs master: Support disabling a cell https://review.openstack.org/546684
09:57:37 ttsiouts johnthetubaguy: Great!! thanks John, I'll follow that up
09:58:10 johnthetubaguy ttsiouts: traditionally any cross service communication in OpenStack is via a REST API, so good not to break that rule
09:58:33 johnthetubaguy ttsiouts: being an API on the other end will making caching easier anyways
10:00:53 ttsiouts johnthetubaguy: cool! thanks John!
10:01:02 johnthetubaguy no worries
10:04:20 bauzas oh man, FF
10:07:16 openstackgerrit Arvind Nadendla proposed openstack/nova-specs master: Support traits in Glance https://review.openstack.org/541507
10:47:11 openstackgerrit Hironori Shiina proposed openstack/nova-specs master: Ironic: Instance switchover https://review.openstack.org/449155
11:00:42 redondo-mk Hi. Is there anyone there that would be willing to give me some info how nova compute pulls NUMA memory info...would save me some time just trying to figure it out from nova codebase...
11:02:31 redondo-mk I'm looking at info that I get in `at /proc/meminfo | grep Huge` and `grep Huge /sys/devices/system/node/node*/meminfo` and I see numbers adding up...what I don't get is the following....Total-Free should give you Used, right but then I see different numbers for used in compute_nodes db table (`select numa_topology from compute_nodes`)?
11:04:39 openstackgerrit Hironori Shiina proposed openstack/nova master: ironic: Support resize and cold migration https://review.openstack.org/500677
11:41:20 openstackgerrit John Garbutt proposed openstack/nova-specs master: Spec on preemptible servers https://review.openstack.org/438640
11:43:58 johnthetubaguy ttsiouts: got a first go at the updates to the spec done: ^
12:01:35 strigazi johnthetubaguy: thanks for the update
12:16:32 srf Hello i want to ask when i install devstack i meet nova error
12:17:35 Spazmotic Feel free to let us know the error and i'm sure someone has seen it before, or you may also want to try in #openstack for deployment help if you don't get any help as many people are preparing to travel to Irelund
12:24:14 srf I want to send but i can't paste or copy or send the pic
12:25:54 Spazmotic Well devstack is a command line installer so many copy and paste the error from terminal into a github gist :)
12:27:02 openstackgerrit Elod Illes proposed openstack/nova master: Functional test: cold migrate to compute down https://review.openstack.org/496280
12:29:52 srf Oke i'll try.
12:56:27 jaypipes bauwser: is sahid going to PTG?
13:00:53 bauwser leakypipes: no, mostly all our team but him :)
13:03:18 leakypipes bauwser: shame :( there's a bunch of specs I wanted to discuss with him.
13:05:27 leakypipes dansmith: still around?
13:05:39 leakypipes dansmith: question for you on that IO thread vs vCPU thread thing...
13:06:15 sean-k-mooney leakypipes: e.g. qemu emulator treads?
13:06:28 sean-k-mooney they are the ones that od io right?
13:07:05 leakypipes sean-k-mooney: are you making fun of me? :)
13:07:54 sean-k-mooney haha no it geunely works differently depend on kernel vs dpdk vhost or kvm vs qeum with tci backend so it never keep this strait in my head
13:08:12 leakypipes sean-k-mooney: no, AFAIK, the emulator threads are the QEMU control process threads -- they send communication events to the guest I think?
13:08:54 leakypipes sean-k-mooney: the I/O threads are for doing device read/write operations on behalf of the guest. And the vCPU threads are for the guest's userspace code to run.
13:09:45 leakypipes sean-k-mooney: but I had a question about whether libvirt allows each of those three types of threads to be pinned to a specific pCPU or whether only emulator and vCPU threads were possible to pin...
13:10:15 johnthetubaguy you know I assumed it pinned them all together, but that is a good question
13:10:33 leakypipes sean-k-mooney: and further to that, can you pin the emulator thread(s) to the same pCPU as the I/O threads...
13:12:34 sahid leakypipes: you can pin i/o threads with emulator threads on a same pCPUs but it can have bad effects, and increase I/O lantency
13:12:57 leakypipes sahid: ok, cool. thanks :)
13:13:15 leakypipes sahid: the emulator thread doesn't get a whole lot of control process "traffic" though, right?
13:13:26 leakypipes sahid: pretty minimal compared to IO or vCPU threads, yeah?
13:14:05 leakypipes sahid: I mean, I understand for RT environments wanting to have guaranteed execution and all that, I'm just curious about the internals of it all, nothing more.
13:15:35 sahid honnestly i don't know exaclty, it's just that we know the emulator threads can lock the full CPU so we want avoid to have vCPUs running sensitive apps
13:16:12 sahid i would say we want the same for i/o threads so it's probably better to avoid to pin them together
13:16:43 leakypipes got it.
13:16:46 leakypipes thanks :)
13:21:04 srf i'll try to install devstack in my computer but always error in nova http://paste.openstack.org/show/682946/ anybody can help me what wrong this
13:24:53 hshiina leakypipes: hi, i have a question about your note at https://github.com/openstack/nova/blob/master/nova/scheduler/client/report.py#L855
13:25:19 hshiina InventoryInUse exception is periodically logged with stacktrace in ironic job: http://logs.openstack.org/19/546919/2/check/ironic-tempest-dsvm-ipa-partition-pxe_ipmitool-tinyipa-python3/2737ab0/logs/screen-n-cpu.txt.gz?level=ERROR
13:25:45 hshiina is there anything to fix here?
13:33:32 leakypipes hshiina: one sec, reading :)
13:35:38 leakypipes hshiina: no, that looks to be a different scenario than the one described in that comment. lemme dig some more into the log there.
13:37:30 hshiina leakypipes: sure, thanks.
13:37:45 leakypipes hshiina: if I had to guess, what is happening in your case is the following:
13:37:57 leakypipes 1) nova boots an Ironic flavor
13:38:37 leakypipes 2) nova-scheduler finds an available Ironic compute node that has CUSTOM_BAREMETAL inventory of 1, used of 0.
13:38:52 leakypipes 3) nova-compute calls the Ironic virt driver to launch the instance
13:39:09 leakypipes 4) Ironic virt driver launches the instance. All good.
13:39:24 leakypipes 5) At some point, the Ironic node goes into an "unavailable" status
13:39:36 leakypipes 6) The resource tracker in nova-compute runs update_available_resource()
13:39:56 leakypipes 7) the Ironic virt driver returns an inventory total of 0 CUSTOM_BAREMETAL for the unavailable node
13:40:12 leakypipes 8) The nova-compute resource tracker dutifully tries to remove the inventory for that node
13:40:31 leakypipes 9) the Placement API returns an InventoryInUse exception because there is an instance running on that Ironic node
13:41:09 leakypipes hshiina: so what I would check in your job logs is whether that Ironic node that the instance ended up on was set to unavailable at some point between 11:17:05 and 11:18:13
13:41:57 leakypipes hshiina: from what I can tell, the resource tracker and placement API are doing "the right thing" and preventing inventory from being deleted when there is an active instance on that Ironic node.
13:43:30 hshiina leakypipes: thank you. i will dig it later.
13:43:50 hshiina leakypipes: i am interested in. but, i have to leave office shortly.
13:43:59 leakypipes np
13:50:58 srf i'll try to install devstack in my computer but always error in nova http://paste.openstack.org/show/682946/ anybody can help me, ?
13:54:03 openstack Launchpad bug 1726260 in devstack "devstack fails while running ./stack.sh in master/queens in ubuntu 16.04 while starting n-cpu" [Undecided,New]
13:54:03 Spazmotic srf: Quick google revealed this.. did you try to search around a bit? https://bugs.launchpad.net/devstack/+bug/1726260
13:54:26 Spazmotic Give that a try :)

Earlier   Later