Earlier  
Posted Nick Remark
#openstack-nova - 2018-07-23
05:14:07 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Merge config drive extension response into server controller https://review.openstack.org/584223
05:22:15 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Merge config drive extension response into server controller https://review.openstack.org/584223
05:23:57 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Merge extended server attributes extension response https://review.openstack.org/584590
05:42:01 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Merge extended server attributes extension response https://review.openstack.org/584590
05:56:21 deepak_mourya takashin: Hi, What is the default direction of sort when we will do 'nova list' ?
05:56:21 deepak_mourya NovaClient : It shows default is descending https://github.com/openstack/python-novaclient/blob/master/novaclient/v2/shell.py#L1454
05:56:21 deepak_mourya Nova Sqlalchemy : It shows default is Ascending https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L2454
06:01:33 takashin deepak_mourya: In the compute API refrence, the default value of 'sort_dir' parameter is 'desc'.
06:01:51 takashin deepak_mourya: https://developer.openstack.org/api-ref/compute/#list-server-request
06:01:58 takashin deepak_mourya: https://developer.openstack.org/api-ref/compute/#id15
06:02:55 takashin deepak_mourya: So compute API and nova client have same default value.
06:04:14 deepak_mourya takashin: Ok, so when we do 'nova list' default servers should come sorted on the basis of column 'name' (sortby_index=1) in the Descending order . Isn't it ?
06:06:33 vishakha takashin : Hi, I have updated the patch https://review.openstack.org/#/c/580271/. Pls review. Thanks
06:13:54 takashin deepak_mourya: In nova, the result is sorted by 'created_at' value (descending order).
06:14:04 takashin deepak_mourya: https://github.com/openstack/nova/blob/master/nova/api/openstack/common.py#L143-L144
06:14:13 takashin deepak_mourya: I'm not sure that the server name should be sorted by descending order in novaclient.
06:14:23 takashin vishakha: okay. I will.
06:14:55 openstackgerrit jichenjc proposed openstack/nova master: add zvm into support matrix https://review.openstack.org/532720
06:14:56 openstackgerrit jichenjc proposed openstack/nova master: Add zvm admin intro and hypervisor information https://review.openstack.org/533125
06:14:57 openstackgerrit jichenjc proposed openstack/nova master: Add zvm CI information https://review.openstack.org/533512
06:17:49 vishakha takashin : Thanks
06:19:46 deepak_mourya takashin:
06:19:46 deepak_mourya Ok thanks got it, but I think result is still not sorted.
06:19:46 deepak_mourya nova list --sort created_at
06:19:46 deepak_mourya +--------------------------------------+------+--------+------------+-------------+---------------------------------+
06:19:46 deepak_mourya | ID | Name | Status | Task State | Power State | Networks |
06:19:47 deepak_mourya +--------------------------------------+------+--------+------------+-------------+---------------------------------+
06:19:47 deepak_mourya | b56b3bee-df66-43a2-90ad-a6ab522390e6 | abbc | ACTIVE | - | Running | public=2001:db8::e, 172.24.4.6 |
06:19:48 deepak_mourya | 58c19cbc-57e8-49b3-8676-54f57e7df1ab | aab | ACTIVE | - | Running | public=2001:db8::9, 172.24.4.13 |
06:19:48 deepak_mourya | d0900044-f59a-4032-8bb1-0347c2f30bae | abc | ACTIVE | - | Running | public=2001:db8::d, 172.24.4.8 |
06:19:49 deepak_mourya | 307afbb8-131f-42f0-ba96-7a6e1f4a7846 | ab | ACTIVE | - | Running | public=2001:db8::8, 172.24.4.11 |
06:19:49 deepak_mourya +--------------------------------------+------+--------+------------+-------------+---------------------------------+
06:19:50 deepak_mourya nova list
06:19:50 deepak_mourya '+--------------------------------------+------+--------+------------+-------------+---------------------------------+
06:19:51 deepak_mourya | ID | Name | Status | Task State | Power State | Networks |
06:20:20 deepak_mourya nova list
06:20:20 deepak_mourya '+--------------------------------------+------+--------+------------+-------------+---------------------------------+
06:20:20 deepak_mourya | ID | Name | Status | Task State | Power State | Networks |
06:20:20 deepak_mourya +--------------------------------------+------+--------+------------+-------------+---------------------------------+
06:20:20 deepak_mourya | 58c19cbc-57e8-49b3-8676-54f57e7df1ab | aab | ACTIVE | - | Running | public=2001:db8::9, 172.24.4.13 |
06:20:21 deepak_mourya | 307afbb8-131f-42f0-ba96-7a6e1f4a7846 | ab | ACTIVE | - | Running | public=2001:db8::8, 172.24.4.11 |
06:20:21 deepak_mourya | b56b3bee-df66-43a2-90ad-a6ab522390e6 | abbc | ACTIVE | - | Running | public=2001:db8::e, 172.24.4.6 |
06:20:22 deepak_mourya | d0900044-f59a-4032-8bb1-0347c2f30bae | abc | ACTIVE | - | Running | public=2001:db8::d, 172.24.4.8 |
06:20:22 deepak_mourya +--------------------------------------+------+--------+------------+-------------+---------------------------------+
06:20:51 gmann deepak_mourya: is it not sorted by created_at or you are checking sort with name ?
06:22:10 deepak_mourya gmann: When we do 'nova list' , it should sort on the basis of the created_at paramemter
06:22:24 gmann yea
06:22:46 deepak_mourya but what i don't think the resulted output is sorted on the same basis .
06:23:46 gmann but did you check the server create_at field for them
06:24:04 deepak_mourya gmann: http://paste.openstack.org/show/726419/
06:24:48 openstackgerrit Lei Zhang proposed openstack/nova master: Add method to get cpu traits https://review.openstack.org/560317
06:25:05 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Report 0 root_gb in resource tracker if instance is bfv. https://review.openstack.org/584204
06:29:38 openstackgerrit Lei Zhang proposed openstack/nova master: Add method to get cpu traits https://review.openstack.org/560317
06:30:16 gmann deepak_mourya: seems like it is n or sorted by default.
06:30:24 gmann deepak_mourya: let me check on my env
06:30:43 deepak_mourya gmann: ok
06:51:38 openstackgerrit jichenjc proposed openstack/nova master: add zvm into support matrix https://review.openstack.org/532720
06:51:39 openstackgerrit jichenjc proposed openstack/nova master: Add zvm admin intro and hypervisor information https://review.openstack.org/533125
06:51:40 openstackgerrit jichenjc proposed openstack/nova master: Add zvm CI information https://review.openstack.org/533512
07:00:01 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (19) https://review.openstack.org/576676
07:00:10 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (20) https://review.openstack.org/576689
07:00:24 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (21) https://review.openstack.org/576709
07:24:01 openstackgerrit jichenjc proposed openstack/nova master: Add zvm admin intro and hypervisor information https://review.openstack.org/533125
07:24:02 openstackgerrit jichenjc proposed openstack/nova master: Add zvm CI information https://review.openstack.org/533512
07:29:44 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in unit/network/test_neutronv2.py (22) https://review.openstack.org/576712
07:32:20 openstackgerrit huanhongda proposed openstack/nova master: WIP: hypervisor-stats shows wrong disk usages with shared storage https://review.openstack.org/149878
07:40:30 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Merge keypair extension response into server view builder https://review.openstack.org/584748
08:38:05 gibi good morning
08:40:03 openstackgerrit Boxiang Zhu proposed openstack/nova stable/pike: Fix "instance snap min disk size err after resize instance" https://review.openstack.org/584770
09:27:44 bauzas good morning stackers
09:31:36 gibi bauzas: welcome back
09:32:11 bauzas thanks
09:46:16 sean-k-mooney bauzas: o/
10:20:40 openstackgerrit Chris Dent proposed openstack/nova master: [placement] Add /reshaper handler for POST https://review.openstack.org/576927
10:20:46 bauzas cdent: around ?
10:20:54 cdent bauzas: yup, hi
10:20:55 bauzas cdent: can you please refresh my mind ?
10:21:13 bauzas cdent: we stopped auto-healing allocations from the RT since Queens, right?
10:21:28 cdent yes, that's how I remember it
10:21:51 bauzas cdent: on a RH BZ, some customer got some phantom allocations
10:22:12 bauzas cdent: so I wonder how their allocations were created
10:22:27 bauzas but the related instance wasn't there
10:23:51 cdent I have a vague memory of some bugs with cleaning up allocations under certain failure conditions. Do you know whether it was a normal server create or a migration?
10:24:05 bauzas no sorry
10:24:20 bauzas I think it was a server create
10:24:25 bauzas but I'm not sure
10:27:48 cdent any chance they deleted the compute service? any of these bugs look relevant?
10:27:49 cdent https://bugs.launchpad.net/nova/+bug/1756179
10:27:50 openstack Launchpad bug 1756179 in OpenStack Compute (nova) queens "deleting a nova-compute service leaves orphaned records in placement and host mapping" [Medium,Fix committed] - Assigned to Surya Seetharaman (tssurya)
10:27:54 cdent https://bugs.launchpad.net/nova/+bug/1679750
10:27:55 openstack Launchpad bug 1679750 in OpenStack Compute (nova) queens "Allocations are not cleaned up in placement for instance 'local delete' case" [Medium,Fix committed] - Assigned to Matt Riedemann (mriedem)
10:28:03 cdent https://bugs.launchpad.net/nova/+bug/1662867
10:28:04 openstack Launchpad bug 1662867 in OpenStack Compute (nova) queens "update_available_resource_for_node racing instance deletion" [Medium,Fix committed] - Assigned to Lee Yarwood (lyarwood)
10:32:57 cdent bauzas: I gotta step away, but will be back. I hope some of the above is useful
10:33:16 bauzas cdent: thanks for the help, I'll look at the bugs
10:33:35 bauzas and I'll try to discuss with the customer
11:12:07 ratailor could anybody review this https://review.openstack.org/#/c/498334/ need one more +2.
11:13:05 ratailor bauzas, ^^
11:16:20 s10 Hello. Is there any possibility to somehow optimise host_state.update(), which runs on every instance scheduling? Specifically this: https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L181
11:17:12 s10 Our tests show, that this step (load list of instances to host_state) takes ~10 seconds for deployments with thousands of instances.

Earlier   Later