| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-03-29 | |||
| 06:57:06 | openstackgerrit | jichenjc proposed openstack/nova master: z/VM Driver: add get console output https://review.openstack.org/543344 | |
| 07:22:39 | openstackgerrit | jichenjc proposed openstack/nova master: Move update_task_state out of try/except https://review.openstack.org/557152 | |
| 07:25:11 | openstackgerrit | jichenjc proposed openstack/nova master: Fix issue for pep8 on py3 https://review.openstack.org/557633 | |
| 07:36:45 | openstackgerrit | do3meli proposed openstack/nova-specs master: Adds resize on shared storage without ssh keys https://review.openstack.org/551927 | |
| 07:45:49 | bauzas | good morning stackers | |
| 07:46:33 | openstackgerrit | licanwei proposed openstack/nova master: Make nova-manage capable of syncing all cell databases https://review.openstack.org/519275 | |
| 07:47:11 | openstackgerrit | Rajesh Tailor proposed openstack/nova stable/pike: Allow force-delete even if task_state is not None https://review.openstack.org/543345 | |
| 07:47:47 | Spazmotic | Morning bauzas | |
| 08:21:01 | gibi | morning folks | |
| 08:22:35 | jichen | hi sahid: regarding https://review.openstack.org/#/c/523387/, for singleton, if we want to keep | |
| 08:22:37 | jichen | it, we need take something like 'http://127.0.0.1' as array key, do you think that's reasonable ? | |
| 08:54:00 | sahid | jichen: oh i see what you mean, that's because of the parameters | |
| 08:54:30 | jichen | sahid; yes, so that's why I want to avoid the singleton , you ok with that? | |
| 08:55:24 | sahid | jichen: but you told me that, if we don't do a singleton we are going to create multipl connection, no? | |
| 08:57:26 | sahid | jichen: so my thinking is that, only Hypervisor is handling call and you pass an instance of Hypervisor to your Guest class | |
| 08:58:12 | sahid | jichen: i will write my thinking on your patches soon | |
| 08:59:51 | gibi | jaypipes: I don't know if you saw the latest development in the bandwidth spec. I added a summary of the 3 open issues to PS22 https://review.openstack.org/#/c/502306/22 | |
| 09:03:23 | jichen | sahid: ok, got it thanks for the info and help , I will take a look at that patch :) | |
| 09:03:49 | openstackgerrit | Naichuan Sun proposed openstack/nova master: (WIP)xenapi(N-R-P): Add API to support compute node resource provider update and create https://review.openstack.org/521041 | |
| 09:03:50 | sahid | jichen: but wait i will think a bit more about all of that | |
| 09:04:27 | jichen | sure , thanks , sahid | |
| 09:07:24 | openstackgerrit | Naichuan Sun proposed openstack/nova master: (WIP)xenapi(N-R-P): Add API to support compute node resource provider update and create https://review.openstack.org/521041 | |
| 09:18:06 | openstackgerrit | Yikun Jiang (Kero) proposed openstack/nova master: [WIP] Add microversion to support extra_specs in flavor API. https://review.openstack.org/554159 | |
| 09:23:07 | sahid | jichen: what is returned by zvm when calling example 'guest_list' | |
| 09:23:20 | sahid | how zvm is representing a guest? | |
| 09:25:14 | jichen | sahid: a guest is defined by a plain text such as following (xxxx is device, memory etc) | |
| 09:25:15 | jichen | USER TEST0004 1024M 1024M | |
| 09:25:17 | jichen | xxxx | |
| 09:25:18 | jichen | xxxx | |
| 09:25:43 | jichen | guest_list will return an array such as ['test0001', 'test0002'] which is a list of guest name managed by openstack | |
| 09:26:10 | sahid | i see | |
| 09:26:58 | sahid | jichen: i commented on two of your patches | |
| 09:27:03 | sahid | let me know your thinking | |
| 09:27:13 | jichen | sahid, thank you ,let me take a look | |
| 09:37:16 | openstackgerrit | Claudiu Belu proposed openstack/nova master: vmware: Fixes _detach_instance_volumes method https://review.openstack.org/557377 | |
| 09:48:11 | openstackgerrit | Naichuan Sun proposed openstack/nova master: xenapi(N-R-P): Add API to support vgpu resource provider create https://review.openstack.org/520313 | |
| 09:51:48 | openstackgerrit | Naichuan Sun proposed openstack/nova master: xenapi(N-R-P): Add API to support vgpu resource provider create https://review.openstack.org/520313 | |
| 09:52:01 | openstackgerrit | Naichuan Sun proposed openstack/nova master: xenapi(N-R-P):Get vgpu info from `allocations` https://review.openstack.org/521717 | |
| 09:56:25 | openstackgerrit | Elod Illes proposed openstack/nova stable/ocata: Set error state after failed evacuation https://review.openstack.org/518733 | |
| 09:57:47 | openstackgerrit | Merged openstack/nova stable/queens: Handle EndpointNotFound when building image_ref_url in notifications https://review.openstack.org/554963 | |
| 09:57:53 | openstackgerrit | Merged openstack/nova stable/queens: Always deallocate networking before reschedule if using Neutron https://review.openstack.org/555418 | |
| 09:58:00 | openstackgerrit | Merged openstack/nova stable/queens: Migrate tempest-dsvm-cells job to an in-tree job definition https://review.openstack.org/556656 | |
| 11:24:25 | sean-k-mooney[m] | sahid: hi, i just saw your comments on my mtu patch. ill respin with the extra unit tests hopefully today. i have a few minutes before my next meeting so ill see how much i can get done before 1 | |
| 11:31:55 | sahid | sean-k-mooney[m]: ok, once i can see the change i will update my review | |
| 11:46:13 | openstackgerrit | Merged openstack/nova stable/pike: Allow force-delete even if task_state is not None https://review.openstack.org/543345 | |
| 12:16:25 | alex_xu_ | efried: jaypipes are you around? a question about multi-function fpga | |
| 12:22:26 | edmondsw | efried I replied to your question in https://review.openstack.org/#/c/546713 | |
| 12:49:31 | efried | alex_xu_: hello | |
| 12:52:03 | alex_xu_ | efried: good morning | |
| 12:52:31 | efried | alex_xu_: Not sure I'm the person to answer questions about FPGAs, but I'll give it a shot :) | |
| 12:52:56 | alex_xu_ | efried: in the ptg, we only think about a fpga device only has one function, then we said create resource class for a whole device | |
| 12:53:16 | alex_xu_ | efried: but now, a device can support multi funciton, and each function can be assigned to different VM | |
| 12:53:30 | alex_xu_ | efried: actually it is placement question :) | |
| 12:54:11 | alex_xu_ | efried: so we should create RP for a device, and resource class is function, just like SRIOV device, a device provides multiple function | |
| 12:54:16 | alex_xu_ | does make sense | |
| 12:56:06 | efried | alex_xu_: Yes, that is my understanding of how it will need to work. However, as you've seen from the dev ML, it can be more complicated than that. | |
| 12:57:01 | efried | alex_xu_: For example, there seem to be FPGAs where, once you decide they're going to have a particular function on them, they can no longer have a different one. bauzas is running into the same thing for his VGPUs. | |
| 12:57:58 | bauzas | right | |
| 12:59:23 | alex_xu_ | efried: bauzas yes, that is why i also think about we only support pre-programmed mode for the multi functions device | |
| 13:00:04 | alex_xu_ | and same type in the all the functions in a device | |
| 13:00:21 | alex_xu_ | if we want to support different function, we can create multiple RP for different type | |
| 13:00:53 | efried | alex_xu_: Based on a config file or a user command. You're essentially talking about preconfiguring the physical function and locking down what virtual functions it's capable of. | |
| 13:01:11 | efried | Which I think is probably an acceptable interim solution. | |
| 13:01:21 | alex_xu_ | efried: yea | |
| 13:01:22 | efried | Though ultimately it would be nice to be dynamic | |
| 13:01:36 | alex_xu_ | yes, at least for now, that is what we can have | |
| 13:02:14 | alex_xu_ | efried: bauzas another problem is cyborg want to own some inventory info in his db and has filter to second level scheduling | |
| 13:02:59 | alex_xu_ | in cyborg db, the usage of functions and the fuction is record | |
| 13:03:07 | alex_xu_ | s/fuction/function type/ | |
| 13:03:29 | alex_xu_ | for the usage of functions, that can be resolved by function as resource class | |
| 13:03:37 | alex_xu_ | for the function type we can use trait | |
| 13:04:11 | alex_xu_ | and I'm thinking tag the traits after cyborg burn bitstream to the fpga | |
| 13:04:26 | alex_xu_ | that is only support for single function device | |
| 13:08:54 | efried | alex_xu_: If we're doing that via a "preconfigure" step, I can see it being acceptable. What I'm worried about jaypipes and dansmith having a cow about is if we do it e.g. based on the first time an allocation is made against the device. | |
| 13:10:06 | alex_xu_ | efried: for single function device, we will have RP for the device, the inventory is always 1 | |
| 13:10:54 | alex_xu_ | that is different with GPU case | |
| 13:12:39 | cdent | just a heads up to anyone listening; I'm pretty sure that the move of the placement related db tests into the placement hierarchy has tweaked something with the management of trait syncing, such that sometimes (only sometimes) a databsase reset is happening but the reset of the trait sync flag is not happening | |
| 13:12:46 | openstackgerrit | Matthew Edmonds proposed openstack/nova master: PowerVM Driver: Network interface attach/detach https://review.openstack.org/546813 | |
| 13:12:49 | cdent | I'm fixing it (and will make bug etc) | |
| 13:13:03 | mriedem | cdent: thanks | |
| 13:15:19 | efried | edmondsw: Thanks for fixing that up. | |
| 13:15:21 | alex_xu_ | efried: are you saying the race case for the GPU tweak trait in the fly, just as you said in the ML. I see that case. But we won't have problem for the RP always has only 1 inventory | |
| 13:15:38 | edmondsw | efried np | |
| 13:15:43 | efried | mriedem: Sorry about that, I was in a hurry. Haste makes waist, or something. | |
| 13:16:18 | efried | alex_xu_: I don't care about the race. We can't avoid that (I'm composing an answer to Sundar on that topic). | |
| 13:16:36 | efried | alex_xu_: I don't think splitting into one RP per virtual function is going to help us. | |
| 13:16:51 | mriedem | efried: what about your size 32 waist? | |
| 13:17:17 | efried | mriedem: I haven't been a 32 since college. Probably because of haste. | |
| 13:17:26 | edleafe | alex_xu_: efried: I think that this is similar to the discussion about NUMA configuration | |
| 13:17:29 | alex_xu_ | efried: you mean you don't care the reason of two level scheduling. or you mean you don't care the race for tweak inventory/traits in the fly? | |
| 13:17:32 | efried | edleafe: Yes it is. | |
| 13:17:46 | alex_xu_ | I think sundar mix that two race in single email | |
| 13:17:49 | edleafe | IOW, decide what it will be, and set inventory appropriately | |
| 13:18:01 | efried | alex_xu_: Hold on, let me send this note, it summarizes my position. | |
| 13:18:27 | edleafe | If an FPGA can never change its functions, then the resource class is the function. The device is not inventory, it's an RP | |
| 13:18:33 | efried | edleafe: Right, decide up front how you're going to allow it to be configured. Which is limiting, but much simplifying. | |
| 13:18:38 | alex_xu_ | edleafe: right | |
| 13:18:51 | edleafe | Same as with NUMA - limiting but simplifying | |
| 13:19:12 | edleafe | If we don't set limits, we'll be back in the "nova will take care of everything for you" business | |
| 13:19:40 | edleafe | We'll spend 90% of our effort on the 5% use cases | |