| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-12-08 | |||
| 00:41:18 | openstackgerrit | Sam Morrison proposed openstack/nova master: Allow ability for non admin users to use all filters on server list. https://review.openstack.org/526558 | |
| 00:46:04 | openstackgerrit | zhangyanxian proposed openstack/nova-specs master: Sriov-bond https://review.openstack.org/463526 | |
| 01:17:33 | openstackgerrit | Tetsuro Nakamura proposed openstack/nova master: Add aggregates check in allocation candidates https://review.openstack.org/522407 | |
| 01:17:34 | openstackgerrit | Tetsuro Nakamura proposed openstack/nova master: Fix missing rps in allocation candidates https://review.openstack.org/522409 | |
| 01:17:34 | openstackgerrit | Tetsuro Nakamura proposed openstack/nova master: Add functional test for get_all_with_shared() https://review.openstack.org/522408 | |
| 01:17:35 | openstackgerrit | Tetsuro Nakamura proposed openstack/nova master: placement: func tests for multiple shared RPs https://review.openstack.org/498737 | |
| 01:52:57 | openstackgerrit | Yikun Jiang (Kero) proposed openstack/nova master: Add instance action db and obj pagination support. https://review.openstack.org/526422 | |
| 02:17:57 | openstackgerrit | wanghongxu proposed openstack/nova master: Update cinder info when attach volume that attached https://review.openstack.org/525540 | |
| 02:27:01 | openstackgerrit | Jiao Pengju proposed openstack/python-novaclient master: Fix listing available images example error in nova.rst https://review.openstack.org/526569 | |
| 02:28:17 | openstackgerrit | Yikun Jiang (Kero) proposed openstack/nova master: Add pagination and changes-since for instance-actions https://review.openstack.org/326326 | |
| 02:49:26 | openstackgerrit | Matt Riedemann proposed openstack/nova-specs master: Document Queens review priorities https://review.openstack.org/526573 | |
| 03:30:27 | openstackgerrit | Matt Riedemann proposed openstack/nova master: doc: link in some Sydney summit content https://review.openstack.org/526587 | |
| 04:13:57 | openstackgerrit | Chen Hanxiao proposed openstack/nova master: trivial: more suitable log in set_admin_password https://review.openstack.org/526592 | |
| 06:20:15 | _heena_py_ | Hi team, could anyone please help me with command where I have the server name and I need to know the floating IP | |
| 06:26:06 | openstackgerrit | jichenjc proposed openstack/nova master: deprecate fping_path config option https://review.openstack.org/526602 | |
| 06:43:17 | masber | _heena_py_, jut run ¨openstack server list¨ and it will show your server and the floating IP | |
| 06:46:10 | masber | good afternoon, I have a host which is misbehaving. How could I tell nova not to schedule new vms into that host? I tried disabling the nova service but didnt work | |
| 06:46:13 | masber | any idea? | |
| 06:47:35 | openstackgerrit | Yikun Jiang (Kero) proposed openstack/nova master: Add pagination and changes-since for instance-actions https://review.openstack.org/326326 | |
| 08:06:32 | openstackgerrit | Eric Berglund proposed openstack/nova master: WIP: PowerVM Driver: vSCSI https://review.openstack.org/526094 | |
| 08:31:07 | openstackgerrit | Eli Qiao proposed openstack/nova master: Api-guide: Add Block Device Mapping https://review.openstack.org/522084 | |
| 08:48:30 | openstackgerrit | Zhenyu Zheng proposed openstack/nova master: Add instance action record for backup instances https://review.openstack.org/523676 | |
| 10:05:06 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Add regression test for bug 1735407 https://review.openstack.org/526095 | |
| 10:05:07 | openstack | bug 1735407 in OpenStack Compute (nova) "[Nova] Evacuation doesn't respect anti-affinity rules" [Medium,In progress] https://launchpad.net/bugs/1735407 - Assigned to Balazs Gibizer (balazs-gibizer) | |
| 10:19:37 | openstackgerrit | Jiao Pengju proposed openstack/python-novaclient master: Fix listing available images example error in nova.rst https://review.openstack.org/526569 | |
| 10:21:16 | openstackgerrit | Theodoros Tsioutsias proposed openstack/python-novaclient master: CommandError is raised for invalid server fields https://review.openstack.org/525110 | |
| 12:07:00 | giblet | what a slow day | |
| 12:07:14 | cdent | gah! now you’ve done it | |
| 12:07:38 | cdent | the quiet peace will now be broken | |
| 12:08:23 | cdent | Is the gate still unhappy | |
| 12:09:38 | giblet | yeah the gate contributes a lot to the slowness of the day | |
| 12:29:19 | fried_rice | Morning folks. | |
| 12:30:00 | fried_rice | Wow, still nothing merged since last night. | |
| 12:30:07 | openstackgerrit | Merged openstack/nova master: XenAPI: update the picture in Xen hypervisor document https://review.openstack.org/523360 | |
| 12:30:51 | giblet | fried_rice: welcome in the slow Friday land :) | |
| 12:30:53 | cdent | fried_rice: gate has issues that likely won’t be resolved until morning time pst | |
| 12:31:48 | cdent | dansmith: when you come on scene can you help decide if the cells-related issue in https://bugs.launchpad.net/nova/+bug/1736101 ought to be considered a proper bug (comments welcome from everyone else too) | |
| 12:31:50 | openstack | Launchpad bug 1736101 in OpenStack Compute (nova) "nova placement resource_providers DBDuplicateEntry when name repeat" [Undecided,New] | |
| 12:36:16 | fried_rice | Just caught up on -infra, looks like they might have sorted it out around 3h ago. Now we just gotta wait for the backlog to push through. | |
| 12:39:41 | fried_rice | Sokay, I only had 17 patches in queue. | |
| 12:40:01 | cdent | clearly this is all your fault. you gotta baby the queue | |
| 12:45:03 | giblet | I hope by rechecking all the bounced patches we will DDoS the whole gate down again ;] | |
| 12:45:43 | fried_rice | I'm deliberately holding off on 10 of them. | |
| 12:46:18 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Add regression test for bug 1735407 https://review.openstack.org/526095 | |
| 12:46:20 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Add late server group policy check to rebuild https://review.openstack.org/525242 | |
| 12:46:20 | openstack | bug 1735407 in OpenStack Compute (nova) "[Nova] Evacuation doesn't respect anti-affinity rules" [Medium,In progress] https://launchpad.net/bugs/1735407 - Assigned to Balazs Gibizer (balazs-gibizer) | |
| 12:46:43 | giblet | oops, two more :) | |
| 12:47:26 | fried_rice | cdent I've got about 4-4.5h in me today, then on vacation. Were you serious in your offer to babysit my code while I'm out? | |
| 12:48:29 | cdent | fried_rice: a) yes (in part because I want to understand it better ), b) I thought you were supposed to already be gone | |
| 12:48:47 | sean-k-m2 | giblet: it wont ddos the gate. zuul will just enqueue them and run them when nodepool says there is an env availably to it | |
| 12:49:33 | giblet | sean-k-mooney: what a relief | |
| 12:50:04 | giblet | fried_rice, cdent: I'm here and active until 20th of Dec so I can offer at least my review help on those patches | |
| 12:50:19 | sean-k-mooney | cdent: im pretty sure you can by coffee enfused cold medicine | |
| 12:50:46 | fried_rice | cdent giblet Okay cool, so what I was gonna say is, if y'all got time over the next couple hours to look at those, I can answer any questions or explain any weirdness. | |
| 12:51:02 | fried_rice | sean-k-mooney Don't they call that "Irish coffee"? ;P | |
| 12:51:19 | sean-k-mooney | cdent: but if that does not work you can try the irish solution of brandy/wisky infused coffe | |
| 12:52:56 | fried_rice | cdent Can you explain this delta? https://review.openstack.org/#/c/414230/2..6/nova/scheduler/client/report.py@180 In particular, why did we feel it necessary to check for both `openstack-request-id` and `x-openstack-request-id`? | |
| 12:54:53 | cdent | sean-k-mooney: that will be later in the day, while I think a weekly resource providers update supported by whisky might be entertaining, it might not be all that useful | |
| 12:55:23 | cdent | fried_rice: because there was a brief time when both was going to be supported (as in moving to not using the x- prefix) but then that didn’t happen | |
| 12:55:36 | fried_rice | Okay, so https://review.openstack.org/#/c/523606/ is kosher? | |
| 12:56:10 | sean-k-mooney | x-openstack-request-id is the http header we use for the osprofiler stuff right? | |
| 12:56:23 | fried_rice | oh, you're saying we still might move to the non-x version at some point, whereupon the above would have to be reverted? | |
| 12:56:42 | sean-k-mooney | i taught all non standard http headers were required to have an x prefix | |
| 12:56:45 | cdent | it is kosher, as I said on my +1 on ps3 | |
| 12:57:06 | cdent | sean-k-mooney: they got rid of that requirement somewhere in the last 3 years or so | |
| 12:57:42 | fried_rice | Oh, I didn't see your review. Cool. | |
| 12:57:42 | cdent | fried_rice: even if we did move to wanting the new style, we would have to continue producing the old style, because of compatibility between version | |
| 12:57:43 | sean-k-mooney | cdent: i guess to prevent peopel from updating all there code to support both when its standariesed | |
| 12:58:02 | cdent | it’s like how the microversion headers in nova always return and support both the old and new styles | |
| 12:58:06 | cdent | sean-k-mooney: yes | |
| 13:00:59 | sean-k-mooney | in anycase key.endswith('-request-id') was a little too broad before i like the v6 version more that said wont this rais an exception if neither form are found | |
| 13:01:16 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: [placement] Add x-openstack-request-id in API ref https://review.openstack.org/523007 | |
| 13:02:04 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: List/show all server migration types (1/2) https://review.openstack.org/430608 | |
| 13:04:06 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: List/show all server migration types (2/2) https://review.openstack.org/459483 | |
| 13:05:43 | sean-k-mooney | actully never mind if .get does not find the key and no default is given it returns None instead of raising an exception | |
| 13:17:34 | openstackgerrit | Silvan Kaiser proposed openstack/nova master: Added mount fstype based validation of Quobyte mounts https://review.openstack.org/522245 | |
| 13:32:49 | giblet | fried_rice: regarding https://review.openstack.org/#/c/521605 Can we change the traits of an RP without bumping its generation? | |
| 13:33:21 | giblet | fried_rice: I wondering about having the default None in https://review.openstack.org/#/c/521605/5/nova/compute/provider_tree.py@134 is necessary | |
| 13:35:02 | fried_rice | giblet So | |
| 13:35:42 | fried_rice | IIUC, the generation is intended to be used to detect async updates when we push stuff back to placement. | |
| 13:36:00 | fried_rice | at the moment, I feel like it's not well defined how it's supposed to get used. | |
| 13:36:35 | fried_rice | I.e. who's responsible for bumping the generation, who's responsible for checking for inconsistencies, what the result of an inconsistency should be (exception? HTTP error? Retry? ...) | |
| 13:37:42 | giblet | fried_rice: I think the client should send in bumped generation and the server is responsible to reject update with outdated generation | |
| 13:37:58 | fried_rice | I think that's about the gist of it, yeah. | |
| 13:38:02 | leakypipes | fried_rice: the nova.objects.resource_provider._increment_provider_generation() function pretty well explains it. | |
| 13:39:49 | fried_rice | leakypipes So the server side is responsible for incrementing the generation. | |
| 13:40:04 | fried_rice | It should never be done by the client | |
| 13:40:45 | fried_rice | The client is supposed to take the generation from the server side, make whatever changes to the *other* fields, and push back the object with the *same* generation, which lets the server detect whether a concurrent update occurred. | |
| 13:41:11 | fried_rice | IOW, the only time we should be updating the generation in ProviderTree is when we've freshly retrieved the object from placement. | |
| 13:42:12 | giblet | leakypipes, fried_rice: thanks, now it make sense | |
| 13:43:01 | giblet | fried_rice: so the case when generation is None in https://review.openstack.org/#/c/521605/5/nova/compute/provider_tree.py@134 is when the client update the trait of the RP | |
| 13:43:43 | leakypipes | fried_rice: the client is responsible for refreshing its knowledge of the latest generation, yes. | |
| 13:44:13 | fried_rice | giblet Yeah, so the code path (in a subsequent patch in the series) is going to be a GET of the RP's traits. Uhm, I need to check whether that response includes the RP generation I suppose. | |
| 13:44:30 | leakypipes | fried_rice: it does not. | |
| 13:44:51 | fried_rice | Okay. Then we would have no way to know what to update it to. | |
| 13:45:05 | fried_rice | In fact, I'm not even sure we should have the generation arg there at all... | |
| 13:45:15 | fried_rice | Same for aggregates, I assume. | |
| 13:46:09 | leakypipes | fried_rice: changing aggregates doesn't increment the generation. | |
| 13:47:39 | leakypipes | fried_rice: because when you associate or disassociate an aggregate, you aren't changing the state of the resource provider's own attributes (like traits or inventories). there could be an argument made for incrementing the generation when aggs change on a rp, but I'm a bit skeptical about that | |
| 13:48:40 | fried_rice | leakypipes But generation would change if you update traits? | |