Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-11-27
02:56:44 openstackgerrit Yikun Jiang proposed openstack/nova master: Handle gathering exception in get_instance_sorted. https://review.openstack.org/522425
03:01:16 openstackgerrit Tao Li proposed openstack/nova master: Ignore some updates from virt driver https://review.openstack.org/523006
03:07:17 openstackgerrit Takashi NATSUME proposed openstack/nova master: [placement] Add x-openstack-request-id in API ref https://review.openstack.org/523007
03:11:37 openstackgerrit Eli Qiao proposed openstack/nova master: Api-guide: Add Block Device Mapping https://review.openstack.org/522084
03:11:38 openstackgerrit Eli Qiao proposed openstack/nova master: Api-guide: Add concept for scheduler hints https://review.openstack.org/522106
03:14:33 eliqiao @alex_xu can you help to take a quick look at https://review.openstack.org/#/c/522067/ (+2 already) when you are available ?
03:46:20 openstackgerrit Tuan Luong-Anh proposed openstack/nova master: Fix the format file name https://review.openstack.org/523010
03:52:09 openstackgerrit Zhenyu Zheng proposed openstack/nova master: nova-manage db archive_deleted_rows is not multi-cell aware https://review.openstack.org/507486
04:48:16 openstackgerrit Tuan Luong-Anh proposed openstack/nova master: Fix the format file name https://review.openstack.org/523010
05:09:14 openstackgerrit Li Xipeng proposed openstack/nova master: Fix bug case by none token context https://review.openstack.org/522112
05:47:02 openstackgerrit Naichuan Sun proposed openstack/nova master: xenapi(N-R-P): Add API to support vgpu resource provider create https://review.openstack.org/520313
05:58:30 openstackgerrit Li Xipeng proposed openstack/nova master: Fix bug as BDM failed when booting from volume https://review.openstack.org/522486
06:11:43 openstackgerrit Huan Xie proposed openstack/nova master: XenAPI: Don't use nicira-iface-id for XenServer VIF https://review.openstack.org/451641
06:56:36 pallavi Hi
06:57:59 pallavi I have installed openstack and but my VM is getting internet connection
06:58:14 pallavi please help me to fix this issue
07:03:01 eliqiao https://ask.openstack.org/ is a good place to ask questions.
07:19:32 openstackgerrit Li Xipeng proposed openstack/nova master: Fix bug as BDM failed when booting from volume https://review.openstack.org/522486
07:22:59 openstackgerrit Li Xipeng proposed openstack/nova master: Fix bug case by none token context https://review.openstack.org/522112
07:29:20 openstackgerrit Chen Hanxiao proposed openstack/python-novaclient master: inject file: add description of injecting multiple files. https://review.openstack.org/515655
07:39:51 openstackgerrit licanwei proposed openstack/nova master: cli 'nova-manage db sync' can't upgrade cell1 https://review.openstack.org/519275
07:50:56 openstackgerrit Naichuan Sun proposed openstack/nova master: xenapi: Get vgpu info from `allocations` https://review.openstack.org/521717
08:06:54 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Add instance action record for attach/detach/swap volumes https://review.openstack.org/517205
08:18:17 openstackgerrit Claudiu Belu proposed openstack/nova master: POC: tests: fixes mock autospec usage https://review.openstack.org/447505
08:18:17 openstackgerrit Claudiu Belu proposed openstack/nova master: POC: tests: autospecs all the mock.patch usages https://review.openstack.org/470775
08:32:21 khappone Hello there. I sumbitted this bug a while back, and I wondered if there could be some eyes on this. It's a possible (well, it's already happened) dataloss bug in Nova with the unshelve workflow. https://bugs.launchpad.net/nova/+bug/1732428
08:32:21 openstack Launchpad bug 1732428 in OpenStack Compute (nova) "Unshelving a VM breaks instance metadata when using qcow2 backed images" [Undecided,New]
09:44:31 openstackgerrit Claudiu Belu proposed openstack/nova master: POC: tests: autospecs all the mock.patch usages https://review.openstack.org/470775
09:59:31 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Add instance action record for attach/detach/swap volumes https://review.openstack.org/517205
10:39:20 openstackgerrit Hironori Shiina proposed openstack/nova master: Ironic: Check a last error of power action https://review.openstack.org/470754
10:46:15 openstackgerrit Claudiu Belu proposed openstack/nova master: POC: tests: autospecs all the mock.patch usages https://review.openstack.org/470775
11:28:14 openstackgerrit licanwei proposed openstack/nova master: cli 'nova-manage db sync' can't upgrade cell1 https://review.openstack.org/519275
11:36:46 openstackgerrit Naichuan Sun proposed openstack/nova master: xenapi:(WIP:need ut) Get vgpu info from `allocations` https://review.openstack.org/521717
12:23:48 efried Good morning Nova!
12:24:18 openstackgerrit Balazs Gibizer proposed openstack/nova stable/ocata: Document the real behavior of notify_on_state_change https://review.openstack.org/521871
12:31:44 openstackgerrit Balazs Gibizer proposed openstack/nova master: Transform instance.resize_revert notification https://review.openstack.org/396811
12:44:58 openstackgerrit Claudiu Belu proposed openstack/nova master: POC: tests: autospecs all the mock.patch usages https://review.openstack.org/470775
12:46:35 nkorabli Hey there! Would love to clarify Numa cpu pinning process in Openstack. I've went through all the docs I could find on that - but still one thing is not clear to me. Is that possible to assign an instance to a particular Numa cell? It seems like by default, when you launch a single CPU vm using numa, it won't be spread evenly across all numa cells, it will be pinned to the `cellid=0`.
12:47:15 nkorabli @here
12:50:11 sean-k-mooney nkorabli: that depends on your definition of assigin to a numa cell
12:50:51 sean-k-mooney nkorabli: you can request a vm to have a single virtual numa cell in which case openstack will create it and pin it to a single numa cell
12:51:30 sean-k-mooney nkorabli: you cannot however say that i want to boot this vm on numa cell 0 of host X. that would break the cloud abstration
12:57:01 openstackgerrit Claudiu Belu proposed openstack/nova master: POC: tests: autospecs all the mock.patch usages https://review.openstack.org/470775
12:59:05 nkorabli sean-k-moooney: I played a bit with that - I had single compute node with 2 numa cells(nodes). I launched a lot of VMs with a single CPU. Then checked how those VMs got distributed across those numa cells. Apparently, all of them got pinned to the first numa node and none to second.
12:59:45 sean-k-mooney are you using openstack kilo
13:00:02 sean-k-mooney or using a pci passthrough device.
13:00:03 nkorabli I used Liberty for that
13:00:10 sean-k-mooney thats your issue
13:00:26 nkorabli I also noticed this in the code: https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L4099-L4104
13:00:42 sean-k-mooney liberty had a bug where the numa virtual numa node was used to select the phyical numa node
13:00:57 sean-k-mooney that was expcitly never intended to be the behavior
13:03:11 nkorabli So, this behavior shouldn't be the same in older releases? I supposed that according to the link above - this issue hasn't been fixed yet..'
13:04:44 sean-k-mooney no you are miss understanding what i said. https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L4099-L4104 simply states that if we do not request a numa topology for a vm we leave the kernel spread the instaces.
13:05:51 sean-k-mooney by default vms created in openstack are not assumed to have memory or cpus that come from a single numa node
13:08:41 sean-k-mooney nkorabli: are several indirect ways that a numa topology can be requested on your behalf without you seting the hw:numa_nodes extra spec.
13:09:47 sean-k-mooney nkorabli: for example if you request hugepages a request for a singel numa node will implicitly be created. unless your request a numa topology via hw:numa_nodes
13:13:12 nkorabli If I specified `hw:numa_nodes=1` then it will use just one cell, right? (like `cellid=0`). I can't specify `hw:numa_nodes=2` for a single CPU instance either. So, I can't explicitly make use of both numa nodes when working with single CPU VMs?
13:15:56 sean-k-mooney nkorabli: if you specify hw:numa_nodes=1 for a single core vm flavor that vm can be placed on either of numa nodes on the host system but it will be affinitesed to which ever node it first starts on
13:16:49 sean-k-mooney nkorabli: if you dont spceify hw:numa_nodes at all it will implcitly float across all numa nodes and cores at the whim of the host kernel scheduler
13:18:28 sean-k-mooney nkorabli: to be more precise it will float across the cores specified via the vcpu_pin_set option in the nova.conf
13:19:01 sean-k-mooney nkorabli: if vcpu_pin_set is not specified it defaults to all cores
13:21:45 nkorabli alright, that's great! I was expecting behavior like this, just couldn't reproduce in Liberty. When I specified hw:numa_nodes=1, it started throwing errors like this: "No valid host was found. There are not enough hosts available." So, I thought it fills up the first node and never sees the second.
13:23:37 nkorabli This line also made me think this way: https://github.com/openstack/nova/blob/master/nova/virt/libvirt/config.py#L1976
13:24:15 nkorabli If I understand you right, this is an issue that appears in Liberty only?
13:25:32 sean-k-mooney https://github.com/openstack/nova/blob/master/nova/virt/libvirt/config.py#L1976 is referring to the virtual numa topology of the guest. not the host numa topology
13:26:32 sean-k-mooney the first release of openstack with numa support did a 1:1 mapping between the virtual cellid to the host cellid howerver that was a mistake that was correct in later releases
13:28:48 sean-k-mooney nkorabli: there is also a rather little known option hw:numa_mempolicy which defaults to strict which allows you to specify if the guest memory must come from the same numa node as the vCPUS
13:29:11 sean-k-mooney i cant find the upstream docs but its memtioned here in the redhat docs https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/6/html/Administration_Guide/section-flavors.html
13:30:12 efried edleafe Sched meeting is in half an hour, right?
13:36:04 cdent efried: appears so
13:36:25 efried cdent Takes me a couple weeks to get the time shift right. DST is stupid.
13:36:33 cdent yes and yes
13:37:01 openstackgerrit Balazs Gibizer proposed openstack/nova master: Transform instance.resize_revert notification https://review.openstack.org/396811
13:39:48 openstackgerrit Balazs Gibizer proposed openstack/nova master: Transform instance.resize_revert notification https://review.openstack.org/396811
13:43:54 nkorabli sean-k-mooney: thanks a lot! Let me test that out!
13:52:15 openstackgerrit Claudiu Belu proposed openstack/nova master: POC: tests: autospecs all the mock.patch usages https://review.openstack.org/470775
13:54:09 edleafe efried: yes, scheduler subteam meeting in 6 minutes in #openstack-meeting-alt
13:54:16 efried thx
13:56:22 openstackgerrit Balazs Gibizer proposed openstack/nova master: Transform instance.exists notification https://review.openstack.org/403660
13:56:23 openstackgerrit Balazs Gibizer proposed openstack/nova master: Add sample test for instance audit https://review.openstack.org/480955
14:18:18 openstackgerrit Balazs Gibizer proposed openstack/nova master: Transform instance.exists notification https://review.openstack.org/403660
14:18:19 openstackgerrit Balazs Gibizer proposed openstack/nova master: Add sample test for instance audit https://review.openstack.org/480955
14:41:09 alex_xu efried: looks like https://review.openstack.org/#/c/498737/2/nova/tests/functional/db/test_resource_provider.py@2981 same with https://review.openstack.org/#/c/518633/15/nova/tests/functional/db/test_allocation_candidates.py@1719
14:42:12 alex_xu efried: I didn't found one similar to this yet https://review.openstack.org/#/c/498737/2/nova/tests/functional/db/test_resource_provider.py@3207
14:46:03 mriedem gibi: are you looking for changes on this patch? https://review.openstack.org/#/c/516782/
14:46:09 mriedem i see you didn't -1 it
14:46:54 mriedem alex_xu: regarding https://review.openstack.org/#/c/522305/ i'm inclined to just fix the bug since it's an admin-only API by default, so not really an interop concern, and it's a 1-line fix which we can then backport
14:47:09 mriedem i'll need to consider updating the microversion dev ref docs on admin APIs
14:47:57 alex_xu mriedem: ok, got it
14:50:04 gibi mriedem: It would be nice to close the bug 1730730 report as well with the patch but jaypipes seems has different oppinion
14:50:04 openstack bug 1730730 in OpenStack Compute (nova) "AllocationCandidates.get_by_filters returns garbage with only sharing providers" [Undecided,Triaged] https://launchpad.net/bugs/1730730
14:52:32 gibi jaypipes: is it OK for you if I quickly resping https://review.openstack.org/#/c/516782/ and add the closes-bug tag to the commit message?
14:52:50 jaypipes gibi: go for it.
14:53:06 gibi jaypipes: OK
14:54:32 openstackgerrit Balazs Gibizer proposed openstack/nova master: finish refactor AllocCandidates._get_by_filters() https://review.openstack.org/516782
14:54:39 openstackgerrit Eric Berglund proposed openstack/nova master: PowerVM support matrix update https://review.openstack.org/523140
14:55:38 gibi mriedem, alex_xu, jaypipes: here is the quick update, i'm +2 now on https://review.openstack.org/516782
14:56:22 alex_xu gibi: done
15:00:02 openstackgerrit Takashi NATSUME proposed openstack/nova master: [placement] Add x-openstack-request-id in API ref https://review.openstack.org/523007
15:04:25 openstackgerrit Matt Riedemann proposed openstack/nova master: Fix invalid minRam error message https://review.openstack.org/523142

Earlier   Later