Tuesday, 2018-02-06

*** jaypipes_ is now known as jaypipes00:04
*** jaypipes has quit IRC00:05
*** yassine has joined #openstack-nova00:05
*** yassine is now known as Guest5729200:05
*** acormier has joined #openstack-nova00:08
*** mtreinish has quit IRC00:12
*** edmondsw has joined #openstack-nova00:21
*** gongysh has joined #openstack-nova00:21
*** acormier has quit IRC00:24
*** yangyapeng has joined #openstack-nova00:25
*** edmondsw has quit IRC00:25
*** r-daneel has quit IRC00:29
*** yangyapeng has quit IRC00:30
*** amodi has quit IRC00:33
*** sdague has quit IRC00:36
*** hoangcx has quit IRC00:37
*** mtreinish has joined #openstack-nova00:37
*** hiro-kobayashi has joined #openstack-nova00:37
*** hoangcx has joined #openstack-nova00:37
*** chyka has quit IRC00:37
*** dave-mccowan has joined #openstack-nova00:42
*** lei-zh has quit IRC00:45
*** slaweq has joined #openstack-nova00:46
*** edleafe has quit IRC00:48
ameedajaypipes: are you around ?00:50
*** edleafe has joined #openstack-nova00:51
*** slaweq has quit IRC00:51
*** Swami has quit IRC00:53
*** Dinesh_Bhor has joined #openstack-nova00:54
*** edleafe has quit IRC00:55
openstackgerritAmeed Ashour proposed openstack/nova master: detach instance volumes when VM creation fails  https://review.openstack.org/52838500:56
*** Dinesh_Bhor has quit IRC00:56
*** claudiub has quit IRC00:58
*** chyka has joined #openstack-nova01:01
*** acormier has joined #openstack-nova01:04
*** acormier has joined #openstack-nova01:04
*** chyka has quit IRC01:06
*** Dinesh_Bhor has joined #openstack-nova01:07
*** gongysh has quit IRC01:09
*** edleafe has joined #openstack-nova01:11
*** Dinesh_Bhor has quit IRC01:17
*** Dinesh_Bhor has joined #openstack-nova01:18
*** Dinesh_Bhor has quit IRC01:21
*** yangyapeng has joined #openstack-nova01:22
*** stakeda has joined #openstack-nova01:22
*** liverpooler has joined #openstack-nova01:23
*** acormier has quit IRC01:28
mriedemefried: there will be the normal project update which will talk about some placement stuff done in queens but not a deep dive01:30
*** zhaochao has joined #openstack-nova01:31
mriedemmgagne: you know this whole aggregate core/ram/disk filter thread? if you're using the CachingScheduler, it doesn't affect you01:31
mriedemmelwitt: can you take another pass on the luks fix? https://review.openstack.org/#/c/539739/01:32
mriedemwe need that in before rc101:32
melwittmriedem: sure01:32
openstackgerritMatt Riedemann proposed openstack/nova master: DNM: debug nova-api service version check during boot from volume  https://review.openstack.org/54099201:34
openstackgerritMatt Riedemann proposed openstack/nova master: DNM: debug nova-next image not found failures  https://review.openstack.org/54100801:37
openstackgerritZhenyu Zheng proposed openstack/nova master: nova-manage db archive_deleted_rows is not multi-cell aware  https://review.openstack.org/50748601:43
*** naichuans_ has joined #openstack-nova01:44
openstackgerritmelanie witt proposed openstack/nova master: Store a RequestContext on service to reuse for periodic tasks  https://review.openstack.org/52430601:44
openstackgerritmelanie witt proposed openstack/nova master: Improve the CellDatabases test fixture and usage  https://review.openstack.org/50843201:44
*** naichuans_ has quit IRC01:44
*** salv-orlando has joined #openstack-nova01:45
*** Dinesh_Bhor has joined #openstack-nova01:47
openstackgerritHironori Shiina proposed openstack/nova master: virt/ironic: Implement rescue and unrescue  https://review.openstack.org/41648701:48
*** hongbin has joined #openstack-nova01:49
*** Dinesh_Bhor has quit IRC01:50
*** chyka has joined #openstack-nova01:50
*** slaweq has joined #openstack-nova01:50
*** gjayavelu has quit IRC01:52
*** hiro-kobayashi has quit IRC01:54
*** slaweq has quit IRC01:55
*** chyka has quit IRC01:55
openstackgerritbaiwenteng proposed openstack/nova-specs master: modify spelling error  https://review.openstack.org/54109001:57
*** sapd__ has quit IRC02:04
mriedemKevin_Zheng: yikun: easy docs bug to fix https://bugs.launchpad.net/nova/+bug/174756202:05
openstackLaunchpad bug 1747562 in OpenStack Compute (nova) "CPU topologies in nova - wrong link for "Manage Flavors"" [Medium,Triaged]02:05
*** awaugama has quit IRC02:05
*** sapd has joined #openstack-nova02:06
Kevin_Zhengmriedem can you check https://review.openstack.org/#/c/540796/ ? Seems your idea in original patch is incorrect02:07
mriedemwhat was my idea in what original patch?02:07
mriedemi guess you mean https://review.openstack.org/#/c/330285/02:09
*** edmondsw has joined #openstack-nova02:09
*** acormier has joined #openstack-nova02:09
mriedemanyway +W02:10
Kevin_Zhenghttps://review.openstack.org/#/c/330285/173/nova/compute/manager.py yeah02:10
Kevin_Zhenghere02:10
Kevin_Zhengseems you were wrong and here response was correct but somehow the result is wrong :)02:11
mriedemyeah i guess i had a typo; reviewing a change with 176 patch sets will do that02:12
Kevin_Zhengheh02:12
*** Dinesh_Bhor has joined #openstack-nova02:12
*** itlinux has joined #openstack-nova02:13
*** edmondsw has quit IRC02:14
*** esberglu has quit IRC02:14
*** Dinesh_Bhor has quit IRC02:15
*** gongysh has joined #openstack-nova02:18
*** harlowja has quit IRC02:18
*** markvoelker has joined #openstack-nova02:22
*** slaweq has joined #openstack-nova02:24
*** markvoelker has quit IRC02:24
*** mriedem has quit IRC02:25
*** acormier has quit IRC02:26
*** acormier has joined #openstack-nova02:27
*** mriedem has joined #openstack-nova02:28
*** slaweq has quit IRC02:29
*** markvoelker has joined #openstack-nova02:31
*** Dinesh_Bhor has joined #openstack-nova02:31
*** salv-orlando has quit IRC02:33
*** lyan has joined #openstack-nova02:33
*** salv-orlando has joined #openstack-nova02:33
yikunmriedem, OK, thanks, I will try to fix. :D02:35
Kevin_Zhengyikun already assigned to you :)02:35
mriedemgood luck02:36
*** salv-orlando has quit IRC02:38
yikunhttps://review.openstack.org/#/c/522161/02:39
yikun: ), ^^ and this is a issue make us can't create vm with unicode server name.02:39
yikunI update the patch again~02:39
*** masahisa has quit IRC02:40
yikuntake a look if you have time, :)02:40
openstackgerritTakashi NATSUME proposed openstack/nova master: Transform servergroup.addmember notification  https://review.openstack.org/54110102:41
*** itlinux has quit IRC02:43
*** Tom-Tom has joined #openstack-nova02:45
*** dave-mccowan has quit IRC02:48
openstackgerritpangliye proposed openstack/nova master: fix misspelling of 'projectUser'  https://review.openstack.org/54110802:49
*** bkopilov has quit IRC02:50
*** tuanla____ has joined #openstack-nova02:53
*** markvoelker has quit IRC02:56
*** markvoelker has joined #openstack-nova02:59
*** slaweq has joined #openstack-nova03:00
*** slaweq has quit IRC03:04
*** dave-mccowan has joined #openstack-nova03:08
*** gjayavelu has joined #openstack-nova03:09
*** markvoelker has quit IRC03:11
*** mriedem has quit IRC03:14
*** markvoelker has joined #openstack-nova03:14
*** lyan has quit IRC03:14
*** gjayavelu has quit IRC03:22
*** acormier_ has joined #openstack-nova03:23
*** markvoelker has quit IRC03:25
*** gcb has joined #openstack-nova03:26
*** liverpooler has quit IRC03:27
*** acormier has quit IRC03:27
*** gyee has quit IRC03:29
*** markvoelker has joined #openstack-nova03:30
*** dave-mccowan has quit IRC03:33
*** gongysh has quit IRC03:33
openstackgerritChangBo Guo(gcb) proposed openstack/nova master: Use check_string_length from oslo_utils  https://review.openstack.org/28639003:34
openstackgerritLiChunlin proposed openstack/nova master: update the description of hypervisor statistics response  https://review.openstack.org/46235503:35
*** masahisa has joined #openstack-nova03:35
*** acormier_ has quit IRC03:37
*** chyka has joined #openstack-nova03:39
*** slaweq has joined #openstack-nova03:40
*** markvoelker has quit IRC03:42
*** chyka has quit IRC03:44
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Fix wrong link for "Manage Flavors" in CPU topologies doc  https://review.openstack.org/54111603:44
*** slaweq has quit IRC03:44
*** crushil has joined #openstack-nova03:48
*** sree has joined #openstack-nova03:50
*** jdurgin has quit IRC03:50
*** jdurgin has joined #openstack-nova03:52
*** hongbin has quit IRC03:55
*** edmondsw has joined #openstack-nova03:58
*** gongysh has joined #openstack-nova04:01
*** edmondsw has quit IRC04:02
openstackgerritMerged openstack/nova master: [placement] Add sending global request ID in post  https://review.openstack.org/52682304:05
openstackgerritMerged openstack/nova master: Trivial fix a missleading comment  https://review.openstack.org/54079604:05
*** bkopilov has joined #openstack-nova04:08
*** pooja_jadhav has joined #openstack-nova04:11
*** gongysh has quit IRC04:11
*** udesale has joined #openstack-nova04:13
*** gongysh has joined #openstack-nova04:14
*** abhishekk has joined #openstack-nova04:21
*** ratailor has joined #openstack-nova04:22
openstackgerritTakashi NATSUME proposed openstack/nova master: Adds view builders for keypairs controller  https://review.openstack.org/34728904:22
*** psachin has joined #openstack-nova04:26
*** hiro-kobayashi has joined #openstack-nova04:29
*** gongysh has quit IRC04:30
*** yamamoto has joined #openstack-nova04:35
*** Tom-Tom has quit IRC04:36
*** Tom-Tom has joined #openstack-nova04:36
*** crushil has quit IRC04:38
*** lpetrut has joined #openstack-nova04:41
*** Tom-Tom has quit IRC04:41
*** crushil has joined #openstack-nova04:42
*** slaweq has joined #openstack-nova04:44
*** harlowja has joined #openstack-nova04:46
*** slaweq has quit IRC04:48
*** sree_ has joined #openstack-nova04:53
*** sree_ is now known as Guest7719404:54
*** sree has quit IRC04:57
*** trinaths has joined #openstack-nova05:02
*** zhurong has quit IRC05:07
*** lpetrut has quit IRC05:08
*** Tom-Tom has joined #openstack-nova05:10
*** harlowja has quit IRC05:11
*** links has joined #openstack-nova05:12
*** janki has joined #openstack-nova05:15
*** lpetrut has joined #openstack-nova05:16
*** itlinux has joined #openstack-nova05:17
*** gongysh has joined #openstack-nova05:19
*** chyka has joined #openstack-nova05:22
*** lyan has joined #openstack-nova05:22
*** tuanla____ has quit IRC05:23
*** hoangcx has quit IRC05:26
*** moshele has joined #openstack-nova05:27
*** sdake_ is now known as sdake05:30
*** moshele has quit IRC05:30
*** sree has joined #openstack-nova05:31
*** lpetrut has quit IRC05:32
*** Guest77194 has quit IRC05:34
*** acormier has joined #openstack-nova05:38
*** acormier has quit IRC05:42
*** mdnadeem has joined #openstack-nova05:44
*** edmondsw has joined #openstack-nova05:46
*** andrewbogott has quit IRC05:49
*** andrewbogott has joined #openstack-nova05:49
*** edmondsw has quit IRC05:50
*** sree_ has joined #openstack-nova05:54
*** sree_ is now known as Guest5425305:54
*** itlinux has quit IRC05:55
*** sree has quit IRC05:58
*** gcb has quit IRC06:00
*** slaweq has joined #openstack-nova06:02
*** Dinesh_Bhor has quit IRC06:04
*** Dinesh_Bhor has joined #openstack-nova06:05
*** jchhatbar has joined #openstack-nova06:06
*** janki has quit IRC06:06
*** slaweq has quit IRC06:07
*** Dinesh__Bhor has joined #openstack-nova06:09
*** Dinesh_Bhor has quit IRC06:10
*** lpetrut has joined #openstack-nova06:11
*** hiro-kobayashi has quit IRC06:12
*** chyka has quit IRC06:15
*** takedakn has joined #openstack-nova06:18
*** lpetrut has quit IRC06:18
*** takedakn has quit IRC06:19
*** moshele has joined #openstack-nova06:20
jianghuawbauzas, you're right. XenServer has the same problem for VM resizing and migration. The new VM has no vGPU after these operations. We need fix that in Rocky.06:33
*** lyan has quit IRC06:35
jianghuawbauzas, for "rescue VM", the instance being rescued won't have vGPU. But after unrescue it, it will get the vGPU again. Also placement will hold the allocation. So I think it's not a problem.06:36
jianghuawI guess there is no need to use workaround to rebuild an instance after rescue.06:36
*** ratailor_ has joined #openstack-nova06:36
*** claudiub has joined #openstack-nova06:37
jianghuawMaybe kvm is different for this item. Need you help to clarify.06:37
*** crushil has quit IRC06:38
*** ratailor has quit IRC06:38
*** threestrands has quit IRC06:40
*** kholkina has joined #openstack-nova06:49
*** sridharg has joined #openstack-nova06:53
*** Dinesh__Bhor has quit IRC06:57
openstackgerritjichenjc proposed openstack/nova master: Avoid raise InstanceNotFound exception  https://review.openstack.org/54115207:00
*** Eran_Kuris_ has joined #openstack-nova07:02
*** sree has joined #openstack-nova07:04
*** Eran_Kuris_ has quit IRC07:05
*** Guest54253 has quit IRC07:07
*** josecastroleon has quit IRC07:08
*** Dinesh__Bhor has joined #openstack-nova07:08
*** zhurong has joined #openstack-nova07:09
*** Dinesh__Bhor has quit IRC07:10
*** gcb has joined #openstack-nova07:13
*** andreas_s has joined #openstack-nova07:14
*** khappone has quit IRC07:17
*** crushil has joined #openstack-nova07:19
*** jchhatba_ has joined #openstack-nova07:20
*** jchhatbar has quit IRC07:23
*** lpetrut has joined #openstack-nova07:24
openstackgerritNakanishi Tomotaka proposed openstack/nova master: Test Compute API in multiple cells  https://review.openstack.org/53411607:25
*** AlexeyAbashkin has joined #openstack-nova07:32
*** rcernin has quit IRC07:37
*** AlexeyAbashkin has quit IRC07:39
*** khappone has joined #openstack-nova07:39
*** bhagyashris has quit IRC07:42
*** AlexeyAbashkin has joined #openstack-nova07:48
*** slaweq has joined #openstack-nova07:49
*** jpena|off is now known as jpena07:53
*** sree has quit IRC07:59
*** slaweq has quit IRC08:02
*** alexchadin has joined #openstack-nova08:02
*** takashin has left #openstack-nova08:03
*** slaweq has joined #openstack-nova08:03
*** ilyashakhat has quit IRC08:08
*** jchhatba_ has quit IRC08:12
*** jchhatba_ has joined #openstack-nova08:12
*** ccamacho has joined #openstack-nova08:13
*** pcaruana has joined #openstack-nova08:14
openstackgerritJianghua Wang proposed openstack/nova master: XenAPI: Provide support matrix and doc for VGPU  https://review.openstack.org/54080808:19
*** abhishekk has quit IRC08:21
*** tesseract has joined #openstack-nova08:22
openstackgerritMerged openstack/nova master: [placement] Add sending global request ID in put (1)  https://review.openstack.org/53125808:23
*** sahid has joined #openstack-nova08:23
*** ralonsoh has joined #openstack-nova08:23
hrwmorning08:25
*** bhagyashris has joined #openstack-nova08:25
*** damien_r has joined #openstack-nova08:26
*** lajoskatona has joined #openstack-nova08:32
*** zhurong has quit IRC08:38
*** yamahata has quit IRC08:38
*** Dinesh__Bhor has joined #openstack-nova08:39
*** abhishekk has joined #openstack-nova08:41
*** rodolof has joined #openstack-nova08:47
*** crushil has quit IRC08:49
*** gjayavelu has joined #openstack-nova08:49
*** tssurya has joined #openstack-nova08:51
*** hiro-kobayashi has joined #openstack-nova08:53
*** gongysh has quit IRC08:53
*** mgoddard_ has joined #openstack-nova08:54
*** amoralej|off is now known as amoralej08:56
*** priteau has joined #openstack-nova08:56
*** alexchadin has quit IRC08:57
*** rodolof has quit IRC08:58
*** alexchadin has joined #openstack-nova08:58
*** Dinesh__Bhor has quit IRC09:00
*** cdent has joined #openstack-nova09:02
*** zhurong has joined #openstack-nova09:03
*** gongysh has joined #openstack-nova09:04
*** Dinesh__Bhor has joined #openstack-nova09:04
*** threestrands has joined #openstack-nova09:06
*** jaosorior has quit IRC09:06
*** ragiman has joined #openstack-nova09:08
*** sree has joined #openstack-nova09:12
*** masahisa_ has joined #openstack-nova09:15
*** masahisa has quit IRC09:16
*** threestrands has quit IRC09:21
*** edmondsw has joined #openstack-nova09:22
*** wxy has quit IRC09:22
openstackgerritZhenyu Zheng proposed openstack/nova master: nova-manage db archive_deleted_rows is not multi-cell aware  https://review.openstack.org/50748609:25
stephenfino/09:25
*** edmondsw has quit IRC09:27
*** masahisa has joined #openstack-nova09:28
*** hoonetorg has quit IRC09:28
*** jaosorior has joined #openstack-nova09:29
*** masahisa_ has quit IRC09:30
openstackgerritMarcin Juszkiewicz proposed openstack/nova master: Make sure that we have usable input for graphical console  https://review.openstack.org/53800309:32
*** pooja_jadhav is now known as neha_alhat09:32
bauzasgood morning09:35
bauzasstephenfin: could you please give me again the change you want me to review ?09:35
stephenfinbauzas: It was that backport patch from mdbooth, but I'm told there's a small issue with it that should be resolved on master first09:36
stephenfinbauzas: I'll ping you if/when it's ready to go again :)09:36
bauzask09:38
hrw14th version pushed. hope that it will be final ;D09:38
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Fix wrong link for "Manage Flavors" in CPU topologies doc  https://review.openstack.org/54111609:40
*** hoonetorg has joined #openstack-nova09:41
*** derekh has joined #openstack-nova09:45
*** takedakn has joined #openstack-nova09:49
hrwlovely comment from sahid ;)09:52
*** stakeda has quit IRC09:54
*** takedakn has quit IRC09:54
*** Dinesh__Bhor has quit IRC09:57
*** rmart04 has joined #openstack-nova09:58
*** hiro-kobayashi has quit IRC10:02
*** trinaths has quit IRC10:05
*** janki has joined #openstack-nova10:06
*** jchhatba_ has quit IRC10:07
gibiameeda: hi! Thanks for updating the cleanup patch. I have one small nit: https://review.openstack.org/#/c/528385/17/nova/compute/manager.py@250810:12
*** gjayavelu has quit IRC10:13
ameedagibi: I will add it now, Thank you !!10:13
*** sree has quit IRC10:13
*** sree has joined #openstack-nova10:14
*** jaianshu has joined #openstack-nova10:14
*** sree has quit IRC10:18
*** nmathew has joined #openstack-nova10:19
*** sree has joined #openstack-nova10:19
gibiameeda: I like the fact that the current patch does not change the notification functional tests :)10:21
vivsoni_Hi Team, i have just now created devstack newton10:21
vivsoni_cinder service-list works fine10:22
vivsoni_but nova service-list10:22
vivsoni_gives error10:22
vivsoni_ERROR (ClientException): Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.10:22
vivsoni_<type 'exceptions.ImportError'> (HTTP 500) (Request-ID: req-8d0cdb9c-4ae4-4544-9368-7934404aac53)10:22
*** trinaths has joined #openstack-nova10:22
*** alexchadin has quit IRC10:22
vivsoni_not nova service-list... but it faild while creating nova boot10:22
vivsoni_command failed : nova boot --image cirros-0.3.4-x86_64-uec --flavor m1.tiny inst_110:23
*** sree has quit IRC10:23
*** artom has quit IRC10:24
*** artom has joined #openstack-nova10:24
*** dtantsur|afk is now known as dtantsur10:25
*** alexchadin has joined #openstack-nova10:25
ameedagibi: it's my pleasure to do thing which keeps openstack stable :)10:26
*** azaid__ has joined #openstack-nova10:26
*** bkopilov has quit IRC10:27
openstackgerritAmeed Ashour proposed openstack/nova master: detach instance volumes when VM creation fails  https://review.openstack.org/52838510:27
ameedagibi: patch uploaded ^ :)10:27
*** abhishekk has quit IRC10:27
*** alexchadin has quit IRC10:30
azaid__ameeda: Okay i will check it10:30
-openstackstatus- NOTICE: Our Zuul infrastructure is currently experiencing some problems and processing jobs very slowly, we're investigating. Please do not approve or recheck changes for now.10:30
*** alexchadin has joined #openstack-nova10:30
*** alexchadin has quit IRC10:30
stephenfinvivsoni_: You need to provide more detailed, debug-level logs, for us to have any hope with that10:31
stephenfinvivsoni_: Looks like you're missing some Python package though10:31
*** alexchadin has joined #openstack-nova10:31
stephenfinvivsoni_: Report the bug as requested and we will take a look10:31
*** alexchadin has quit IRC10:31
hrwvivsoni_: newton?10:32
bauzasvivsoni_: stephenfin: that really looks like a packaging issue, hence not something we should mark a bug10:32
*** alexchadin has joined #openstack-nova10:32
bauzasas*10:32
*** alexchadin has quit IRC10:32
bauzasfor the first resolution stage, I'd discuss that in #openstack or ask.openstack.org10:32
gibiameeda: looking10:32
stephenfinbauzas: Good point10:33
*** alexchadin has joined #openstack-nova10:33
*** alexchadin has quit IRC10:33
* bauzas really trying to reduce the open backlog :)10:33
vivsoni_hrw: yes newton10:33
*** azaid__ has quit IRC10:33
vivsoni_stephenfin: sure i am logging a bug10:33
vivsoni_will share the launchpad bug ID10:34
stephenfinvivsoni_: Before you do, maybe see bauzas' suggestion above10:34
hrwI hope to be able to forget about <queens in 2-3 months10:34
vivsoni_stephenfin: ok10:34
stephenfinvivsoni_: Someone on #openstack would be able to help. Also note that 'newton' is unsupported now so, unless it's still an issue with recent releases, your best bet would be your vendor10:34
*** dtruong has quit IRC10:35
*** dtruong has joined #openstack-nova10:35
vivsoni_stephenfin: ok10:35
gibiameeda: +2, thank you for the work and the perseverance :)10:36
* gibi is off to the pool and then to lunch10:37
hrwcan someone tell me at which moment instance xml is passed to libvirt?10:39
*** trinaths has quit IRC10:42
ameedagibi: thank you very much !!10:42
bauzashrw: in a shit number of places :p10:43
*** andreas_s has quit IRC10:43
bauzasin spawn() you mean ?10:43
hrwbauzas: sort of, yes10:43
*** trinaths has joined #openstack-nova10:43
hrwbauzas: I would like to add few pcie-root-port entries but they should be added after libvirt creates own xml10:43
ameedagibi: I have another bug which has some problem , please note this https://review.openstack.org/#/c/526900/28/nova/tests/functional/db/test_archive.py. this caused after I wrote sqlite migration script https://review.openstack.org/#/c/526900/29/nova/db/sqlalchemy/migrate_repo/versions/378_instance_system_metadata_sqlite_upgrade.sql10:43
bauzashrw: _get_guest_config() is where we build the XML IIRC10:44
hrwbauzas: too early10:44
hrwbauzas: I am adding usb host controller and usb keyboard in _get_guest_config() already10:44
hrwbut pci(e) is added by libvirt not nova ;(10:45
bauzasI need to disappear because $gym10:45
bauzasbut let's wrap that up when I'm back10:45
*** andreas_s has joined #openstack-nova10:47
*** abalutoiu__ has joined #openstack-nova10:49
*** cdent has quit IRC10:49
* hrw off for ~2h10:51
*** chyka has joined #openstack-nova10:52
*** lucas-afk is now known as lucasagomes10:52
*** abalutoiu_ has quit IRC10:52
*** sambetts|afk is now known as sambetts10:54
*** chyka has quit IRC10:56
*** Tom-Tom has quit IRC10:57
*** andreas_s has quit IRC10:57
*** Tom-Tom has joined #openstack-nova10:58
*** andreas_s has joined #openstack-nova10:58
*** yamamoto has quit IRC10:59
*** Tom-Tom has quit IRC11:02
*** yamamoto has joined #openstack-nova11:03
*** Tom-Tom has joined #openstack-nova11:04
openstackgerritnalini proposed openstack/nova master: Modify show aggregate to display 'updated_at' value  https://review.openstack.org/53733411:04
*** andreas_s has quit IRC11:07
*** andreas_s has joined #openstack-nova11:08
*** Tom-Tom has quit IRC11:08
*** edmondsw has joined #openstack-nova11:10
*** alexchadin has joined #openstack-nova11:11
openstackgerritJianghua Wang proposed openstack/nova master: XenAPI: Provide support matrix and doc for VGPU  https://review.openstack.org/54080811:12
*** edmondsw has quit IRC11:15
*** udesale has quit IRC11:22
*** cdent has joined #openstack-nova11:22
*** andreas_s has quit IRC11:22
*** andreas_s has joined #openstack-nova11:23
*** nicolasbock has joined #openstack-nova11:26
*** andreas_s has quit IRC11:27
*** andreas_s has joined #openstack-nova11:27
openstackgerritChris Dent proposed openstack/nova-specs master: Add generation support in aggregate association  https://review.openstack.org/54044711:29
stvnoyesmriedem: ok I'll look into it. Have you seen any problems or is your concern theoretical at the moment?11:30
*** nmathew has quit IRC11:38
*** trinaths has quit IRC11:40
*** links has quit IRC11:41
openstackgerritChris Dent proposed openstack/nova master: Remove microversion fallback code from report client  https://review.openstack.org/52879411:42
openstackgerritSurya Seetharaman proposed openstack/nova master: Make bdms querying in multiple cells use scatter-gather  https://review.openstack.org/54124611:43
*** Tom-Tom has joined #openstack-nova11:47
*** sdague has joined #openstack-nova11:51
*** sree has joined #openstack-nova11:51
*** sree_ has joined #openstack-nova11:51
*** sree_ is now known as Guest6131011:52
*** links has joined #openstack-nova11:54
*** sree has quit IRC11:55
*** Eran_Kuris has quit IRC11:56
*** tbachman has quit IRC11:56
*** gongysh has quit IRC11:57
*** Eran_Kuris has joined #openstack-nova11:57
*** Eran_Kuris has quit IRC12:01
*** Eran_Kuris has joined #openstack-nova12:02
*** moshele has quit IRC12:03
*** acormier has joined #openstack-nova12:03
*** masahisa has quit IRC12:04
*** moshele has joined #openstack-nova12:04
*** acormier has quit IRC12:04
*** fyxim has quit IRC12:11
*** fyxim has joined #openstack-nova12:11
*** Guest61310 has quit IRC12:14
*** sree has joined #openstack-nova12:15
*** sree has quit IRC12:19
*** ragiman has quit IRC12:24
*** vladikr has joined #openstack-nova12:31
*** ragiman has joined #openstack-nova12:31
*** ratailor_ has quit IRC12:33
*** nsingh has joined #openstack-nova12:36
*** cdent has quit IRC12:36
nsinghandymccr: is there any framework to develop ansible plugin???12:39
*** jaianshu has quit IRC12:50
*** jpena is now known as jpena|lunch12:51
*** yangyapeng has quit IRC12:52
nsinghevrardjp:is there any framework to develop ansible plugin???12:52
*** moshele has quit IRC12:53
*** yangyapeng has joined #openstack-nova12:53
evrardjpwhat do you mean?12:53
evrardjpnsingh: ^12:53
*** moshele has joined #openstack-nova12:53
*** yangyapeng has quit IRC12:53
evrardjpansible is the framework, you can simply use it for writing your own plugins...12:54
evrardjpif you need stuff to be included in ansible and/or openstack-ansible, we can help you indeed12:54
evrardjpdepending on the time ofc12:54
*** yangyapeng has joined #openstack-nova12:54
openstackgerritBalazs Gibizer proposed openstack/nova master: Add regression test for bug 1735407  https://review.openstack.org/52609512:54
openstackbug 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:54
openstackgerritBalazs Gibizer proposed openstack/nova master: Add late server group policy check to rebuild  https://review.openstack.org/52524212:54
*** gongysh has joined #openstack-nova12:54
*** links has quit IRC12:55
nsinghevrardjp:ok.. https://github.com/ansible/ansible is this the frmework you talking about?12:55
gibialex_xu, mriedem: I've fixed your comments ^^12:56
evrardjpnsingh: what are you trying to achieve?12:56
*** takamatsu has joined #openstack-nova12:57
nsinghevrardjp: i am new to ansible. i want to develop ansible plugin for project(masakari).12:58
*** eharney has joined #openstack-nova12:58
evrardjpto do what?12:58
evrardjpI think we are probably not on the right channel :)12:59
*** AlexeyAbashkin has quit IRC12:59
nsinghok.. thanks12:59
*** zhurong_ has joined #openstack-nova13:01
*** AlexeyAbashkin has joined #openstack-nova13:01
*** yangyapeng has quit IRC13:02
*** udesale has joined #openstack-nova13:02
*** liverpooler has joined #openstack-nova13:04
*** links has joined #openstack-nova13:08
*** zhurong has quit IRC13:08
*** tbachman has joined #openstack-nova13:10
*** jaypipes has joined #openstack-nova13:10
*** pchavva has joined #openstack-nova13:12
sean-k-mooneyo/ jaypipes  how is your new laptop treating you?13:12
sean-k-mooneyjaypipes: its rather early for you no?13:13
*** edmondsw has joined #openstack-nova13:13
jaypipessean-k-mooney: no, 8am. new lappie is fantastic. :)13:17
sean-k-mooneylet me know how the battery life is that the main thing that has been putting me off getting one.13:18
*** cdent has joined #openstack-nova13:19
*** amoralej is now known as amoralej|lunch13:19
sean-k-mooneyim looking at the new lg gram mainly for battery but i like system76 as a company so plus the galago looks like the perfect dev laptop if you travel even a little13:20
*** acormier has joined #openstack-nova13:20
*** udesale has quit IRC13:21
*** udesale has joined #openstack-nova13:22
*** alexchadin has quit IRC13:22
*** Eran_Kuris has quit IRC13:22
*** alexchadin has joined #openstack-nova13:23
jaypipessean-k-mooney: it is excellent. and the damn keys are in the right place! /me shakes fist at Macbook.13:23
*** jaosorior has quit IRC13:23
jaypipessean-k-mooney: also, the screen is fantastic.13:24
jaypipessean-k-mooney: and for $1100 including a 3-year warranty, you can't beat the price IMHO.13:24
*** acormier has quit IRC13:25
*** AlexeyAbashkin has quit IRC13:25
hrwzuul... 4h from sending patch and still no results ;(13:25
*** rodolof has joined #openstack-nova13:26
*** AlexeyAbashkin has joined #openstack-nova13:27
sean-k-mooneyjaypipes: well not haveing to pay 23% vat on import certenly helps13:27
*** bkopilov has joined #openstack-nova13:27
jaypipessean-k-mooney: heh, well I can't help you with that :)13:29
*** dave-mccowan has joined #openstack-nova13:29
jaypipeshrw: your patch hasn't even made it to the zuul birthing canal yet.13:29
jaypipeshrw: contractions will likely begin in about another hour.13:30
*** yangyapeng has joined #openstack-nova13:30
hrwjaypipes: looks like13:32
*** dave-mccowan has quit IRC13:35
*** dave-mcc_ has joined #openstack-nova13:35
*** hemna_ has joined #openstack-nova13:36
*** acormier has joined #openstack-nova13:37
*** yangyapeng has quit IRC13:38
*** AlexeyAbashkin has quit IRC13:38
*** acormier_ has joined #openstack-nova13:41
*** acormier has quit IRC13:42
*** janki has quit IRC13:44
*** yangyapeng has joined #openstack-nova13:44
*** acormier_ has quit IRC13:46
*** jpena|lunch is now known as jpena13:47
bauzashrw: so you had a point13:47
bauzasabout when nova is passing the XML to libvirt13:47
hrwbauzas: yes13:47
bauzasdid you found it ?13:47
hrwnot yet. digged in other stuff13:48
*** yangyapeng has quit IRC13:50
*** masahisa has joined #openstack-nova13:50
hrwbauzas: _create_domain() :D13:50
bauzasthere is another method AFAIR13:50
hrwthis one calls libvirt_guest.Guest13:51
bauzasat least _create_domain_and_network() AFAIK13:51
hrw_create_domain_and_network calls _create_domain13:52
*** READ10 has joined #openstack-nova13:52
*** zhurong_ has quit IRC13:52
bauzasoh my bad yeah13:52
bauzasfor spawn at leasy13:52
hrwbauzas: that's the only point I need :)13:52
*** esberglu has joined #openstack-nova13:53
bauzask13:53
*** masahisa_ has joined #openstack-nova13:54
*** masahisa has quit IRC13:55
*** Sukhdev_ has joined #openstack-nova13:55
*** jmlowe has quit IRC13:55
openstackgerritJacek Tomasiak proposed openstack/python-novaclient master: Fix listing of instances above API max_limit  https://review.openstack.org/53422213:56
ericyoungWe have started to see failures in the tempest.scenario.test_encrypted_cinder_volume tests with the ScaleIo backend.13:58
ericyoungAny known issues with Luks encrypted volumes?13:58
*** masahisa_ has quit IRC13:59
*** hrw has quit IRC13:59
*** hrw has joined #openstack-nova14:01
ameedaHello, could you please give me another +2 here https://review.openstack.org/#/c/528385/14:01
hrwjaypipes: thanks for +2+W :)14:03
*** moshele has quit IRC14:03
*** jaosorior has joined #openstack-nova14:04
jaypipeshrw: np.14:04
*** psachin has quit IRC14:04
efriedQuick and easy approval: https://review.openstack.org/#/c/533237/ (just registering what PowerVM did in Q)14:05
jaosorioranybody knows what actions trigger the compute.instance.update notification?14:07
gibijaosorior: hi14:07
gibijaosorior: let me dig a bit14:07
jaosoriorthanks gibi!14:08
ameedaHELP: when I run .tox/functional/bin/python -m testtools.run nova.tests.functional.db.test_archive.TestDatabaseArchive.test_archive_deleted_rows14:09
ameedaI got this error esttools.matchers._impl.MismatchError: 'instances' not in {'instance_system_metadata': 11, 'instance_actions_events': 2, 'block_device_mapping': 1, 'instance_info_caches': 1, 'instance_actions': 2, 'instance_extra': 1, 'security_group_instance_association': 1}14:09
ameedathis caused after I wrote migration script for sqllite here https://review.openstack.org/#/c/526900/29/nova/db/sqlalchemy/migrate_repo/versions/378_instance_system_metadata_sqlite_upgrade.sql14:09
ameedawhat I did wrong to get that ?14:09
*** yangyapeng has joined #openstack-nova14:11
*** abhishekk has joined #openstack-nova14:13
gibijaosorior: hard to answer in general. That notification is eventually emited from https://github.com/openstack/nova/blob/2c1874a0ecdd1b5ce7670cdfc42396e90e3a55aa/nova/notifications/base.py#L23314:13
gibijaosorior: and tha is for example called for every action that changes a persistent attribute of an Instance object https://github.com/openstack/nova/blob/2c1874a0ecdd1b5ce7670cdfc42396e90e3a55aa/nova/objects/instance.py#L82614:14
jaosoriorgibi: so, from what I can gather, updates are triggered by metadata changes (which is exactly what I need). but I wanted to know what else would trigger it14:14
jaosoriorI see14:14
*** andreas_s has quit IRC14:15
gibijaosorior: yes, metadata update on the Instance also triggers this code path14:15
*** andreas_s has joined #openstack-nova14:15
efriedstephenfin or gibi, care to push this? https://review.openstack.org/#/c/533237/14:17
*** andreas_s has quit IRC14:18
stephenfinefried: Sure, done14:18
*** mriedem has joined #openstack-nova14:18
efriedThanks!14:18
*** andreas_s has joined #openstack-nova14:18
gibiefried: I missed it :014:20
gibi:)14:20
efriedgibi: Don't worry, I've got other patches to satisfy your cravings.14:21
*** chyka has joined #openstack-nova14:23
bauzasmriedem: are we considering https://bugs.launchpad.net/nova/+bug/1747582 as a Won't Fix ?14:24
openstackLaunchpad bug 1747582 in OpenStack Compute (nova) "delete a resize instance change quota_usages incorrectly" [Undecided,New] - Assigned to guolidong (guolidong)14:24
bauzasI mean, we did a huge work on quotas thanks to melwitt after Newton14:24
*** liverpooler has quit IRC14:24
*** amoralej|lunch is now known as amoralej14:24
*** liverpooler has joined #openstack-nova14:25
openstackgerritJianghua Wang proposed openstack/nova master: XenAPI: Provide support matrix and doc for VGPU  https://review.openstack.org/54080814:25
*** chyka has quit IRC14:28
jianghuawbauzas, ^14:28
bauzasjianghuaw: cool, will review it as soon as I can14:29
jianghuawbauzas, thanks.14:29
openstackgerritAmeed Ashour proposed openstack/nova master: change instance_system_metadata column type  https://review.openstack.org/52690014:34
*** lucasagomes is now known as lucas-hungry14:34
*** david-lyle has quit IRC14:34
*** AlexeyAbashkin has joined #openstack-nova14:35
*** dtantsur is now known as dtantsur|bbl14:37
*** Eran_Kuris has joined #openstack-nova14:37
*** links has quit IRC14:38
*** rodolof has quit IRC14:39
*** artom has quit IRC14:45
openstackgerritStephen Finucane proposed openstack/nova-specs master: Add 'numa-aware-vswitches' spec  https://review.openstack.org/54129014:45
stephenfinsean-k-mooney: It's very rough, but fancy taking a look at ^ at some point?14:45
stephenfinefried: You might be able to weight in from the generic device management aspect too ^14:46
mriedembauzas: depends on if it's recreatable in master14:46
efriedack14:46
bauzasmriedem: just told that actually14:46
stephenfinTry as I may, I can't think of a reason to need that, but I'm clearly missing something as both you and sean-k-mooney suggested it :)14:46
bauzashence Incomplete14:46
* stephenfin disappears for an hour14:46
*** alexchadin has quit IRC14:48
sean-k-mooneystephenfin: reason to need ?14:48
sean-k-mooneystephenfin: also first taught on https://review.openstack.org/541290 is it should proably be an neutron spec but i have only got to line 10 so ill keep reading14:50
*** mdnadeem has quit IRC14:52
*** lpetrut has quit IRC14:53
*** elod has joined #openstack-nova14:54
sean-k-mooneystephenfin: of were you refering to a need for numa-aware-vswitches when you said you can think why you need that?14:55
*** jmlowe has joined #openstack-nova14:57
*** acormier has joined #openstack-nova14:59
mriedembauzas: can you review https://review.openstack.org/#/c/539739/ please? it's an rc1 blocker due to a regression in the native encrypted luks stuff, blocking some cinder 3rd party CIs15:05
bauzasmriedem: roger.15:05
bauzasLUKS, I am your father.15:05
*** 7IZAAAWPC has joined #openstack-nova15:07
*** 17SAAOQME has joined #openstack-nova15:07
*** cdent has quit IRC15:09
edleafebauzas: <groan!>15:11
*** mnaser has quit IRC15:11
*** mnaser has joined #openstack-nova15:11
*** rodolof has joined #openstack-nova15:11
*** 7IZAAAWPC has quit IRC15:12
*** 17SAAOQME has quit IRC15:12
bauzasthat's possibly one of the top said jokes, I know15:12
*** amodi has joined #openstack-nova15:13
*** abhishekk is now known as abhishekk|meetin15:13
*** dtantsur|bbl is now known as dtantsur15:14
*** mlavalle has joined #openstack-nova15:15
openstackgerritLajos Katona proposed openstack/nova master: WIP: ServerMovingTests with custom resources  https://review.openstack.org/49739915:16
*** awaugama has joined #openstack-nova15:16
*** artom has joined #openstack-nova15:24
*** lucas-hungry is now known as lucasagomes15:30
*** Eran_Kuris has quit IRC15:30
openstackgerritEd Leafe proposed openstack/nova master: Make the InstanceMapping marker UUID-like  https://review.openstack.org/53932315:31
*** burt has joined #openstack-nova15:32
*** lpetrut has joined #openstack-nova15:34
*** sree has joined #openstack-nova15:36
*** andrewbogott has quit IRC15:36
*** andrewbogott has joined #openstack-nova15:37
*** artom has quit IRC15:38
*** med_ has quit IRC15:38
*** yamamoto has quit IRC15:39
*** sree has quit IRC15:41
stephenfinsean-k-mooney: Yup, keep reading. It seems like a nova thing in that current design :)15:41
stephenfinthough you may have left comments in the interim15:41
* stephenfin goes to check15:41
*** yamamoto has joined #openstack-nova15:42
*** karlamrhein has quit IRC15:42
*** karlamrhein has joined #openstack-nova15:42
*** andrewbogott has quit IRC15:44
*** andrewbogott has joined #openstack-nova15:44
*** kholkina has quit IRC15:48
*** yamahata has joined #openstack-nova15:48
*** dtantsur is now known as dtantsur|bbl15:49
*** david-lyle has joined #openstack-nova15:51
*** pcaruana has quit IRC15:51
*** samueldmq has quit IRC15:52
sean-k-mooneystephenfin: well im commenting back. the current design will not work unfrotunetly for example have you taught about how you handel bonds.15:52
*** samueldmq has joined #openstack-nova15:52
*** tbachman has quit IRC15:52
* stephenfin meant to note that bonding was out of scope for this15:53
*** yamamoto has quit IRC15:53
*** abalutoiu_ has joined #openstack-nova15:55
*** claudiub|2 has joined #openstack-nova15:55
*** claudiub|2 has quit IRC15:55
*** abalutoiu_ has quit IRC15:55
*** abalutoiu_ has joined #openstack-nova15:56
*** claudiub|2 has joined #openstack-nova15:56
*** jaypipes has quit IRC15:56
*** salv-orlando has joined #openstack-nova15:57
*** ragiman has quit IRC15:58
sean-k-mooneystephenfin: sorry in advance https://review.openstack.org/#/c/541290/1 comments in line15:58
*** claudiub has quit IRC15:58
stephenfinsean-k-mooney: :)15:58
*** abalutoiu__ has quit IRC15:58
sean-k-mooneystephenfin: by the way where did the 50% performanc number come from? the numa effect on ovs-dpdk should be in the singel figure if you turn on the numa support in dpdk15:59
*** lajoskatona has left #openstack-nova15:59
stephenfinsean-k-mooney: I was wondering if anyone was going to call me on that. It's been quoted numerous times to me by fbaudin, but I think it's based on internal analysis16:00
stephenfinI can root out the details and add them in some form to the spec16:00
stephenfin...which clearly needs more work :)16:00
sean-k-mooneystephenfin: ya but i have mention to him in the past that we have messured much lower numbers in the past if you turn on the numa support in dpdk/ovs which is off by default16:01
*** r-daneel has joined #openstack-nova16:01
*** salv-orlando has quit IRC16:03
*** salv-orlando has joined #openstack-nova16:03
stephenfinsean-k-mooney: Thanks, I wasn't aware of that. There's some great info in there16:03
stephenfinsean-k-mooney: You aren't, by any chance, going to be in Dublin, are you?16:03
sean-k-mooneyi proably will be. im not sure if i will be there on behalf of intel though as my travel has not been approved so i might not be the there the whole week if i go up myself16:04
*** Sukhdev_ has quit IRC16:04
*** icey has quit IRC16:05
*** icey has joined #openstack-nova16:06
*** zioproto has quit IRC16:06
*** jaosorior has quit IRC16:06
*** zioproto has joined #openstack-nova16:06
*** gjayavelu has joined #openstack-nova16:07
*** cdent has joined #openstack-nova16:09
*** trinaths has joined #openstack-nova16:10
sean-k-mooneystephenfin: just looking at the at the dpdk-devel packages for centos and fedora and they appear to have the the numa support turned on. and the ovs packages depend on libnuma so they "should" have numa support but if the testing was not done with at least 1 pmd per numa node then ovs will not be able to compensate internally if the vm and nic are not on the same numa node16:14
*** redondo-mk has quit IRC16:15
stephenfinsean-k-mooney: Could you stick that in the review too? This is all good data to use while working on this16:15
*** redondo-mk has joined #openstack-nova16:15
stephenfinsean-k-mooney: Planning on setting up an AIO deployment this evening to start hacking on this and see what I can get working16:15
efriedsean-k-mooney: Are you from Dublin originally?16:16
*** abhishekk|meetin has quit IRC16:16
sean-k-mooneystephenfin: yep will do. if you use networking-ovs-dpdk/devstack just be aware we dont acally compile in the ovs support you will have to add it in but patches are welcome.16:16
sahidmriedem can you ack this https://review.openstack.org/#/c/515008/, it's a bugfix16:16
*** andreas_s has quit IRC16:17
sean-k-mooneyefried: no i lived there for a year im on the other cost in shannon but its only about a 3 hour drive or so16:17
*** andreas_s has joined #openstack-nova16:17
efriedI thought pronouncing 'th' as 't' was a Dublin thing.16:17
stephenfinsean-k-mooney: You mean you don't compile in DPDK support...right?16:18
stephenfinIf not, what about compiling in?16:18
stephenfinefried: For example?16:18
efriedstephenfin: "taught" for "thought"16:18
*** yamamoto has joined #openstack-nova16:18
sean-k-mooneyefried: they pronounce 'th' more like a 'd' but 'th' as a 't' is more of a tipperary thing that i generally avoid doing in speach16:19
*** trinaths has quit IRC16:19
*** yamamoto has quit IRC16:19
stephenfinAh, no. My father, who's also from the west coast, does that too16:20
stephenfinOne, two, tree...16:20
*** yamamoto has joined #openstack-nova16:20
sean-k-mooneyya losing the th is a munster thing mainly16:21
sean-k-mooneyefried: also i spell phonetically not correctly so the acent i write with is not the one i speak with. at least not entirely16:22
stephenfinPronouncing 's' as 'sh' is also a thing. Fun16:22
*** damien_r1 has joined #openstack-nova16:24
*** damien_r has quit IRC16:25
*** yamamoto has quit IRC16:25
sean-k-mooneystephenfin: speaking of fun did you see this yet https://bugs.launchpad.net/nova/+bug/1747496 all those mtu patch last year and this is still a thing ...16:25
openstackLaunchpad bug 1747496 in OpenStack Compute (nova) "MTUs are not set for VIFs if using kernel ovs + hybrid plug = false" [Undecided,New] - Assigned to sean mooney (sean-k-mooney)16:25
*** zhaochao has quit IRC16:26
stephenfinOh, I saw the ping for that last night and forgot16:26
stephenfinFun indeed16:26
*** andreas_s has quit IRC16:26
sean-k-mooneyisint nice when libvirt tries to be helpful and plug vif for us to not over burden os-vif with all the work16:27
openstackgerritJames E. Blair proposed openstack/python-novaclient stable/pike: Zuul: Remove project name  https://review.openstack.org/54137016:27
*** gjayavelu has quit IRC16:28
sean-k-mooneystephenfin: i found it while i was deploying or new internal devcloud with jumbo frames and no security group dirver16:28
*** trinaths has joined #openstack-nova16:28
*** gjayavelu has joined #openstack-nova16:28
stephenfinsean-k-mooney: Oh, that crap16:29
*** artom has joined #openstack-nova16:29
stephenfinI want to remove that _entire_ code path16:29
stephenfinIn fact, I think I started on doing it about a year ago and got distracted/confused16:29
sean-k-mooneystephenfin: ya so do i but as a backportable solution first im going to set the mtu in the xml for libvirt >3.2 and then stop libvirt form helping and let os-vif do it as a followup patch16:30
stephenfinsean-k-mooney: Yup, I can get onboard with that approach16:30
*** yamamoto has joined #openstack-nova16:30
*** tbachman has joined #openstack-nova16:32
*** gjayavelu has quit IRC16:32
*** gmann has quit IRC16:33
*** gmann has joined #openstack-nova16:33
*** itlinux has joined #openstack-nova16:34
*** damien_r has joined #openstack-nova16:38
*** sahid has quit IRC16:39
cfriesensean-k-mooney: just curious, why is numa support in dpdk off by default?  seems like that'd be a good thing.16:39
*** damien_r1 has quit IRC16:39
mriedemmelwitt: comments in https://review.openstack.org/#/c/515008/ since sahid asked for review and left16:41
*** ccamacho has quit IRC16:41
openstackgerritChris Dent proposed openstack/nova master: Optional separate database for placement API  https://review.openstack.org/36276616:42
*** priteau has quit IRC16:42
*** hamzy has quit IRC16:43
*** brad[] has quit IRC16:45
*** damien_r has quit IRC16:45
stephenfincfriesen: I'm not sean-k-mooney, but I'm guessing it's the need for an extra dependency?16:46
*** chyka has joined #openstack-nova16:49
*** sree has joined #openstack-nova16:49
bauzasmriedem: I have a noob question, how can you know that vol.volume_id is set in https://review.openstack.org/#/c/539739/4/nova/virt/libvirt/driver.py@7430 .16:49
bauzas?16:49
mriedembauzas: because when we attach a volume to an instance, we save the volume_id on the bdm record,16:51
mriedemsee nova.virt.block_device.DriverVolumeBlockDevice.attach16:51
mriedemDriverVolumeBlockDevice wraps an proxies a BlockDeviceMapping object,16:52
mriedemand the @update_db decorator on attach() updates the wrapped bdm object16:52
*** jmlowe has quit IRC16:53
mriedemi should say that is the case for bfv with source type blank/image/snapshot where nova creates the volume and then attaches it,16:53
mriedemfor normal volume attach to an existing instance, the bdm is created in compute here https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L522016:53
bauzasok, looking at the code16:53
mriedemwith the volume_id16:53
*** jmlowe has joined #openstack-nova16:53
*** tssurya has quit IRC16:54
*** salv-orlando has quit IRC16:54
*** salv-orlando has joined #openstack-nova16:55
hrwzuul forgot about me ;( 7h since patch upload and no results16:56
*** chyka_ has joined #openstack-nova16:56
bauzashrw: you probably haven't see the gate status16:56
bauzasthey had problems in the morning with very slow processing16:56
hrwbauzas: probably16:56
kashyapdansmith: Okay, after talking to libvirt and QEMU migration maintainers, you're right in pointing out here: https://review.openstack.org/#/c/497457/18/nova/virt/libvirt/driver.py16:57
*** chyka has quit IRC16:57
kashyapThat...16:57
hrwok I see16:57
kashyapdansmith: It is an absolutely horrible hack16:57
kashyapdansmith: ...to slow down migration via by limiting the speed to 1 MiB/s16:58
dansmithkashyap: Well, I know it's a hack, but wasn't sure if there was another option :)16:58
hrwbauzas: will see. in worst case 'recheck' in the morning tomorrow16:58
bauzashrw: you know the status page or not ?16:58
kashyapdansmith: Discussing the design aspects w/ them.  I have a half-comment in draft, will complete it in a bit :-)16:59
dansmithkashyap: excellent, thanks!16:59
kashyapdansmith: Just wanted to confirm your instinct :P16:59
hrwbauzas: https://wiki.openstack.org/wiki/Infrastructure_Status one?16:59
dansmithkashyap: awesome :P16:59
*** salv-orlando has quit IRC16:59
* stephenfin awaits kashyap's findings16:59
stephenfin(I looked at the underlying bug and also assumed there wasn't an alternative)17:00
bauzashrw: http://zuul.openstack.org/ and http://status.openstack.org/openstack-health/#/17:00
hrwthx17:01
openstackgerritDan Smith proposed openstack/nova master: Bump compute RPC API to version 5.0  https://review.openstack.org/54100517:01
openstackgerritDan Smith proposed openstack/nova master: Compute RPC client bump to 5.0  https://review.openstack.org/54103517:01
kashyapdansmith: At least, QEMU migratoin upstream said: "If Nova can define a need, we can add a tunable that libvirt can use"17:01
* kashyap goes back to writing17:02
dansmith++17:02
*** gongysh has quit IRC17:02
*** gyee has joined #openstack-nova17:02
stephenfindansmith: <3 I've been waiting for RPC version bumps for aaaaages17:03
stephenfinMostly thanks to lots of comments from ndipanov saying we can cruft in virt/hardware when that happens17:03
dansmithstephenfin: don't review it yet.. still working out the bugs. I think this iteration is close, but need tempest tests17:03
dansmithstephenfin: well, then you need to look at those notes and make sure I've got the bits that need to be removed17:04
stephenfinI can do that17:04
dansmithstephenfin: I've deprecated the things I know about, but if there are others, now's the time...17:04
*** salv-orlando has joined #openstack-nova17:04
*** slaweq has quit IRC17:05
* hrw off17:05
*** slaweq has joined #openstack-nova17:05
* bauzas enjoys reading BDM code17:06
gibibauzas: could you look at https://review.openstack.org/#/c/525242 again? (and the one below)17:06
*** gongysh has joined #openstack-nova17:06
gibibauzas: mriedem is already +2 on both17:06
bauzasfortunately I have https://docs.openstack.org/nova/latest/user/block-device-mapping.html for help17:06
bauzasgibi: only if that's super quick17:07
gibibauzas: you already reviewed it :)17:07
gibibauzas: so I hope it is a quick one17:07
bauzasgibi: I'm reviewing mriedem's change https://review.openstack.org/#/c/539739/4 that requires some BDM knowledge17:07
bauzas^ RC1 blocker, your call, core17:07
mriedemdid you lay down a guantlet just now?17:08
mriedem*gauntlet even17:08
gibibauzas: sure, the LUKS patch has priority17:08
*** gongysh has quit IRC17:08
bauzashah, no17:09
bauzasfor the first time of my poor life, I have the opportunity to understand the BDM mess^H^H implementation17:09
*** slaweq has quit IRC17:10
dansmithonly 341 things in check.. I look forward to my CI results later in the week17:10
bauzasdansmith: yeah like I said to hrw, that GMT morning was awful17:12
*** jpena is now known as jpena|off17:18
kashyapstephenfin: Quickly, for your point on that live migration issue -- yeah, for the immediate term, we may have to go with the ugly hack of slowing the n/w bandwidth.  Until we figure out a way to stop migration much earlier in Nova.17:21
*** r-daneel has quit IRC17:22
bauzasmriedem: nit on https://review.openstack.org/#/c/539739/4/nova/tests/unit/virt/libvirt/test_driver.py@10523 that prevents me to +2 except if you add it in a follow-up (given the gate delays)17:22
*** slaweq has joined #openstack-nova17:22
*** r-daneel has joined #openstack-nova17:22
bauzasmriedem: do you agree with me on the fact that serial and volume_id should have the same values ?17:23
*** AlexeyAbashkin has quit IRC17:25
*** AlexeyAbashkin has joined #openstack-nova17:25
*** udesale has quit IRC17:25
*** slaweq has quit IRC17:26
*** AlexeyAbashkin has quit IRC17:29
dansmithhmm17:31
dansmithlooks like we just had a zuul reset?17:31
mriedembauzas: replied17:31
mriedemi specifically wanted those to be different17:32
mriedemso that we take volume_id over serial if both are in connection_info17:32
bauzasokay, I don't want to overthink on that17:33
bauzas+2ing17:33
*** sree has quit IRC17:33
mriedemthe DriverVolumeBlockDevice.attach code only sets the serial to the volume_id iff 'serial' isn't already in the connection_info,17:33
mriedemso once again, some cinder volume driver could theoretically be returning a 'serial' value17:34
*** sree has joined #openstack-nova17:34
bauzasyeah I saw the conditional17:34
mriedemso if volume_id, use it, else hope that serial is correct17:34
bauzasI love those conditions actually17:34
bauzastbh, the best would be to tell the cinder storage drivers "please, don't give us information, we'll find out by ourselves, it's better ;) '17:35
mriedema couple of years ago i talked about adding a versioned object for the connection_info dict to cinder,17:35
bauzassince we set the right value in serial if that's not already in there17:35
mriedemto try and normalize a lot of that stuff17:35
mriedembut, i didn't pursue it17:36
bauzasyour fault, then17:36
bauzasboooo17:36
mriedemsort of like the MigrateData thing that dansmith did for live migration17:36
bauzasyup17:36
mriedemyes it's my fault, sadly enough,17:36
mriedemit would have also meant converting like 80 volume drivers over to that new model...17:36
bauzas:)17:37
ildikovyeah, this comes up every half year and we note that harmonize the drivers is just not likely to happen17:38
*** sree has quit IRC17:38
ildikovor you end up with a free-form part where most of the info sits anyway...17:39
*** rmart04 has quit IRC17:39
bauzasmriedem: I haven't seen https://etherpad.openstack.org/p/nova-aggregate-filter-allocation-ratio-snafu somehow planned for the PTG in the PTG etherpad17:43
*** mtreinish has quit IRC17:43
bauzasmriedem: ack if I'm adding it?17:44
mriedemjaypipes had a thing in the ptg etherpad for this issue,17:45
mriedemi'll link it in17:45
mriedemstarts at L34 in https://etherpad.openstack.org/p/nova-ptg-rocky17:46
*** traskat has joined #openstack-nova17:48
bauzascool17:48
mriedemit's enchilada time!17:50
*** mtreinish has joined #openstack-nova17:50
*** jose-phillips has left #openstack-nova17:51
dansmithmriedem: remind me what the legacy-tempest job is?17:53
dansmithit's failing my service version patches for seemingly related reasons, but the regular job is fine17:53
mriedemhmm, legacy-tempest shouldn't be running on our stuff17:54
mriedemi don't think17:54
mriedemthat was replaced by tempest-full17:55
dansmithlegacy-tempest-dsvm-py35FAILURE in 1h 14m 39s17:55
*** gjayavelu has joined #openstack-nova17:55
dansmithon one of my patches17:55
dansmithhttps://review.openstack.org/#/c/539590/17:55
mriedemoh that's different17:55
mriedemit's just tempest with devstack on py3517:55
* tbachman wonders if he’s the only one who can’t access zuul status atm17:56
dansmithtbachman: no17:56
dansmithmriedem: hmm, wonder why it failed17:56
tbachmandansmith: thx17:56
mriedemdansmith: http://logs.openstack.org/90/539590/2/check/legacy-tempest-dsvm-py35/79137ee/job-output.txt.gz#_2018-01-31_19_33_29_77986117:56
mriedemlikely something in the reserve_block_device_name rpc call?17:56
dansmithmriedem: right, hence my "seemingly related reason"17:56
dansmithno, it's because we check for service version before allowing tags17:57
dansmithwhich is what that patch is doing17:57
*** NostawRm has quit IRC17:57
dansmiths/doing/changing/17:57
dansmiths/changing/touching/17:57
*** NostawRm has joined #openstack-nova17:57
bauzasmriedem: mgagne: just added a thought on a possible workaround for https://review.openstack.org/#/c/541018/17:57
bauzasmriedem: mgagne: tl;dr just set allocation ratios on every compute to be 99999.017:58
sean-k-mooneycfriesen: stephenfin yes numa support is off by default in dpdk so that libnuma can remain an optional dependecy not a required depency of dpdk17:58
mriedemdansmith: maybe "if result is" is different in py3517:58
mriedemi don't see much "foo is bar"17:58
bauzasmriedem: mgagne: that will allow Placement to accept all the hosts, and just keep the filtering logic in the appropriate AggregateRAMFilter and so on17:58
*** yamamoto has quit IRC17:59
*** yamamoto has joined #openstack-nova18:00
dansmithmriedem: um, which thing are you talking about?18:00
kashyapI'm Neutron-challenged, can anyone tell at _which_ of these points is Nova waiting (by pausing) on Neutron to let it complete things?  http://git.openstack.org/cgit/openstack/neutron/commit/?h=master&id=b7c303e  ("Notify nova with network-vif-plugged in case of live migration")18:00
dansmiththe sentinel check has to be "is"18:00
*** tesseract has quit IRC18:00
kashyap"during live migration on pre migration" is terribly unclear18:01
* kashyap goes to look at the code18:01
*** sambetts is now known as sambetts|afk18:01
*** derekh has quit IRC18:02
dansmithkashyap: nova waits when it uses the virtapi wait_for_events context manager18:02
dansmithit waits to exit the context until timeout or the event arrives18:02
kashyapI see.18:03
kashyapIs this what the Neutron events telling Nova:18:03
kashyap  "Hey, I've done with doing all the stuff I need to do, so I'm signalling that by sending out this event (from the above Neutron commit).  Over to you now."18:04
kashyapI.e. the destination Neutron has completed virtual interface plugging.18:04
dansmithyes18:04
dansmithI mean, that's what vif-plugged means18:04
kashyapNoted.18:05
stvnoyesmriedem: matt, I added a change to enable multiattach on the zfssa array, but when tempest runs during the zfssa ci, it's not running with multiattach enabled (in tempest.conf). Where would I make a change to have this enabled when running the Oracle ZFSSA CI? thanks...18:05
sean-k-mooneydansmith: actully vif-plugged has different menanings18:05
sean-k-mooneyvif-plugged in the nova-compute agent log means os-vif finisshed plugging the interface18:06
sean-k-mooneyvif-plugged event form neutron means neutron finished wireing it up18:06
dansmithsean-k-mooney: we're talking about when neutron does a POST of the event to nova's external event interface18:06
*** salv-orlando has quit IRC18:07
dansmithand it better (still) mean that the wiring is done, else we have a problem :)18:07
mriedemstvnoyes: do you have these set in devstack? https://github.com/openstack/nova/blob/master/playbooks/legacy/nova-multiattach/run.yaml#L3118:07
*** salv-orlando has joined #openstack-nova18:07
sean-k-mooneydansmith: ah then yes that is sent when neutron finishes wiring up the port that was plugged by nova/os-vif/libvirt into the network backend so your correct in what you said18:07
mriedemstvnoyes: also, is tempest running against master nova so the 2.60 microversion is available?18:08
dansmithsean-k-mooney: thanks :)18:08
kashyapsean-k-mooney: Hey, I'm about to write some questions on this change: https://review.openstack.org/#/c/497457/1818:09
kashyapsean-k-mooney: Post some design discussion w/ QEMU & libvirt folks18:09
kashyapWould appreciate if you also look at it18:09
sean-k-mooneykashyap: am i am behind in some internal paper work but ill try and take a look tomorow18:10
kashyapsean-k-mooney: Sure, tomm is fine; I'm already late for dinner by an hour18:10
kashyapJust want to 'commit this to paper' before my "cache gets flushed"18:10
kashyapAs I've spent the last 2 hours in this rabbit hole :P18:11
*** amodi has quit IRC18:11
mriedemefried: on that service user / CONF.glance.api_servers bug https://bugs.launchpad.net/nova/+bug/1747511 - it's definitely related to using a service user; i removed that code and now the nova-next job passes18:11
openstackLaunchpad bug 1747511 in OpenStack Compute (nova) "legacy-tempest-dsvm-neutron-nova-next-full fails with "Can not find requested image" since 1/31" [Undecided,New]18:11
stvnoyesmriedem: i didn't make any changes to the CI devstack (although I can run locally ok). I believe the CI is against nova master, but will check. The zfssa CI test is running for this review - https://review.openstack.org/#/c/541368/18:12
*** salv-orlando has quit IRC18:12
mriedemstvnoyes: so this job result right? https://openstackci.oracle.com/zfssa_ci/refs-changes-68-541368-1-iscsi/18:12
*** slaweq has joined #openstack-nova18:13
stvnoyesmriedem: yes. I'm seeing tempest.api.compute.volumes.test_attach_volume.AttachVolumeMultiAttachTest) ... SKIPPED: Volume multi-attach is not available.18:13
*** hamzy has joined #openstack-nova18:13
mriedemstvnoyes: that's b/c it's not set in tempest.conf18:13
mriedem2018-02-06 09:16:16.276 12703 DEBUG tempest [-] compute-feature-enabled.volume_multiattach = False log_opt_values /usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py:289818:13
mriedemhttps://openstackci.oracle.com/zfssa_ci/refs-changes-68-541368-1-iscsi/tempest.log18:13
openstackgerritDan Smith proposed openstack/nova master: Make service all-cells min version helper use scatter-gather  https://review.openstack.org/53959018:13
openstackgerritDan Smith proposed openstack/nova master: Make host_manager use scatter-gather and ignore down cells  https://review.openstack.org/53961718:13
openstackgerritPatricia Domingues proposed openstack/nova master: load up the volume drivers by checking architecture  https://review.openstack.org/54139318:13
mriedemstvnoyes: where is the code that controls the local.conf for the devstack setup in this CI?18:14
mriedemis it internal to oracle? or on github?18:14
*** hamzy_ has joined #openstack-nova18:15
*** odyssey4me has joined #openstack-nova18:15
stvnoyesmriedem: good question. idk. I haven't played with CI stuff so all this is pretty new to me. I will see if there's someone around on the zfssa team who would know.18:15
mriedemstvnoyes: https://wiki.openstack.org/wiki/ThirdPartySystems/Oracle_ZFSSA_CI18:16
odyssey4mehowdy all - we're having some trouble in the OSA deployment test for upgrades from newton (without cells v2) to ocata (with cells v2), it looks like there's some weird state which has been hit where the compute registration isn't working right any more. I'm seeing this: https://pastebin.com/C9ji6vdS18:16
odyssey4meOur last working test was the last patch we did which was in early December.18:17
*** slaweq has quit IRC18:17
odyssey4meAny idea what may have changed to cause the previously working implementation to no longer work?18:17
*** hamzy has quit IRC18:17
*** tssurya has joined #openstack-nova18:18
mriedemodyssey4me: i don't see anything related to that in https://github.com/openstack/nova/commits/stable/ocata going back to november18:19
mriedemare you sure it wasn't something that changed on the OSA side?18:19
odyssey4memriedem yep, very sure - see https://review.openstack.org/#/q/branch:stable/ocata+project:openstack/openstack-ansible-os_nova18:19
*** david-lyle has quit IRC18:20
mriedemhttps://github.com/openstack/nova/commits/stable/ocata/nova/cmd/manage.py18:21
*** brad[] has joined #openstack-nova18:21
mriedemoldest thing in stable there is from october18:21
odyssey4meyeah, I'm wondering if something has perhaps changed in the database tables either in newton (the source), or in ocata (the destination)18:22
mriedemhave you verified if the instances you're verifying actually exist?18:22
*** dtantsur|bbl is now known as dtantsur18:22
mriedemi.e. not just not mapped, but don't actually exist18:22
odyssey4mewell, I got stuck there - given that nova-manage doesn't appear to have a way to list the instances :/18:23
odyssey4meany tips for getting a listing out?18:23
odyssey4methe closest I could find is "nova-manage cell_v2 discover_hosts --verbose"18:23
*** amodi has joined #openstack-nova18:24
mriedemthat doesn't dump the instances18:24
mriedemthe api isn't up?18:25
odyssey4meit gives me a set of uuid's which look rather like they belong to instances: https://pastebin.com/mSwpZybQ18:25
mriedemGetting compute nodes from cell 'cell1': 16443e92-e33b-487e-8069-7c80e5bdbc3318:25
mriedemthat's a cell mapping uuid18:25
*** lpetrut has quit IRC18:25
mriedemChecking host mapping for compute host 'ocata-nova1': 6e6d71ab-0b18-416d-8a3a-ce713ac5963718:25
mriedemthat's a compute node uuid18:25
mriedeminstances aren't the only things that have uuids anymore18:26
odyssey4methe API is up, so I can query things that way if it helps18:26
mriedemworth a shot if you have a local recreate,18:27
mriedembut my guess is the api won't find them either if nova-manage can't18:27
odyssey4memy apologies for dumb questions - it's been a very long time since I actually worked with nova directly :)18:27
mriedemif they don't have instance_mappings in nova_api i mean18:27
mriedemtotally fine18:27
mriedemnot dumb at all18:27
mriedemif you have a local recreate, you could check the nova_api.instance_mappings table directly18:28
mriedemor the cell db instances table18:28
odyssey4mesure, can do that18:28
mriedemlooks like you have 2 cells, so you'd have to look in each18:28
mriedemso you've got 4 dbs (nova_api, nova_cell0, cell1 and then cell 9461149a-52a9-495d-8021-d2cda1645d28)18:29
odyssey4meright, so I have several DB's here: nova, nova_api, nova_cell0; nova_placement18:29
mriedemnova is likely cell118:29
mriedemyes?18:29
mriedemnova_placement isn't a thing...not sure what that is18:29
*** ralonsoh has quit IRC18:29
odyssey4meok, that's empty - I'll look into why that's there later18:31
mriedemi probably know why18:31
odyssey4meit might be some leftovers from previous work before things matured18:32
*** lpetrut has joined #openstack-nova18:33
mriedemodyssey4me: yeah https://review.openstack.org/#/q/I31293ac4689630e4113588ab2c6373cf572b8f3818:33
odyssey4mehaha, ok - thanks for the reference :)18:34
mriedemodyssey4me: so looking at https://pastebin.com/mSwpZybQ there is something screwed up with the host mappings,18:34
mriedemit looks like this compute is in two cells18:34
mriedemChecking host mapping for compute host 'ocata-nova1': 6e6d71ab-0b18-416d-8a3a-ce713ac5963718:34
*** brad[] has quit IRC18:34
odyssey4meif it'd make things simpler I can get your pub key on this host for you to poke around directly?18:35
*** harlowja has joined #openstack-nova18:35
odyssey4methe host is a temp instance, so nothing special on it18:35
mriedemi don't think our relationship has hit that level of maturity yet18:35
odyssey4mehahaha, fair enough18:35
odyssey4meotherwise, I'll need some guidance with db queries to get data out - I can gist the results as we go18:36
mriedemwell, it appears you have 2 nova_api.host_mappings entries for host "ocata-nova1"18:36
mriedemwhich would be wrong18:36
odyssey4meyeah, that seemed weird to me too18:37
cfriesenis anyone aware of an issue where running "'wget http://169.254.169.254/latest/meta-data/instance-id" in the guest gives a result that is *not* the same as that instance's OS-EXT-SRV-ATTR:instance_name in "nova show"?18:37
mriedemtssurya: dansmith: melwitt: any idea why we don't have a unique constraint across the cell_id and host colums in the host_mappings table?18:37
dansmithmriedem: I thought there was some argument about that with overlapping hostnames (which won't work anyway) ?18:38
mriedemodyssey4me: is this CI supposed to have 2 cells? because multi-cell wasn't supported in ocata18:38
odyssey4memriedem interestingly enough, I only see one entry in the DB for it18:38
odyssey4menah, it only has cell0 and cell118:39
mriedemodyssey4me: do you have a CI run with logs posted?18:39
*** stvnoyes has quit IRC18:39
mriedemhttps://pastebin.com/mSwpZybQ is saying there are 3 cell mappings18:39
mriedem"Found 3 cell mappings."18:39
mriedemselect uuid from nova_api.cell_mappings;18:39
odyssey4memriedem unfortunately our log collection is broken for ocata, so all we have is console output which only shows brokenness when tempest runs, so that's not very useful18:40
odyssey4meI can fix up the CI to collect logs, but that'll take a few days to make its way through...18:40
odyssey4mehmm, that is odd - three cells showing18:42
odyssey4meit might be my bad, I re-ran 'nova-manage cell_v2 discover_hosts' and 'nova-manage cell_v2 map_instances --cell_uuid ...' a few times18:43
*** gmann has quit IRC18:43
odyssey4mealso ran 'nova-manage cell_v2 simple_cell_setup' after the initial build18:43
odyssey4methat gave me 'Cell0 is already setup', so I don't think that broke anything18:44
mriedemdiscover_hosts is idempotent and doesn't create mappings18:45
mriedemcell mappings i mean18:45
mriedemmap_instances should also be ok18:45
mriedemmy guess is something go f'ed up when running simple_cell_setup a few times18:45
odyssey4meI only did it once :)18:46
*** brad[] has joined #openstack-nova18:46
mriedemwas create_cell ever called?18:48
odyssey4meyep - this is the basic set of steps that would have executed before the discovery: https://github.com/openstack/openstack-ansible-os_nova/blob/stable/ocata/tasks/nova_db_setup.yml#L16-L5518:48
odyssey4meso in this case, the initial api_db sync would have been skipped as this was an existing DB18:49
odyssey4methen the cell0 map done: https://github.com/openstack/openstack-ansible-os_nova/blob/stable/ocata/tasks/nova_db_setup.yml#L3118:49
odyssey4methen the creation of cell1: https://github.com/openstack/openstack-ansible-os_nova/blob/stable/ocata/tasks/nova_db_setup.yml#L3718:49
odyssey4methen the api_db sync, and db sync18:49
mriedemwhere does map_instances happen?18:50
mriedemhttps://github.com/openstack/openstack-ansible-os_nova/blob/stable/ocata/tasks/nova_db_post_setup.yml#L3818:50
*** pooja-jadhav has joined #openstack-nova18:50
mriedemfound it18:50
odyssey4mewe wait for a compute instance to be ready in the handler: https://github.com/openstack/openstack-ansible-os_nova/blob/stable/ocata/handlers/main.yml#L67-L7618:51
odyssey4methen yes, https://github.com/openstack/openstack-ansible-os_nova/blob/stable/ocata/tasks/nova_db_post_setup.yml gets run18:51
*** niraj_singh has joined #openstack-nova18:52
odyssey4meyou'll find those tasks, and their stdout/stderr in this console log: http://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/job-output.txt.gz18:53
odyssey4meit's a bit verbose, apologies in advance18:53
*** nsingh has quit IRC18:55
*** neha_alhat has quit IRC18:55
kashyapdansmith: When you get a moment, wrote this here: https://review.openstack.org/#/c/497457/1818:56
kashyapPlease correct / critique / answer as you see fit.18:56
mriedemodyssey4me: hmm, for https://github.com/openstack/openstack-ansible-os_nova/blob/stable/ocata/tasks/nova_db_post_setup.yml#L3918:57
mriedem--cell_uuid {{ cell1_uuid['stdout'].split()[3] }}"18:57
mriedemare you sure that's hitting cell1 and not cell0?18:57
mriedemoh i guess because of https://github.com/openstack/openstack-ansible-os_nova/blob/stable/ocata/tasks/nova_db_post_setup.yml#L3218:58
mriedemso nvm18:58
odyssey4meyep, exactly18:58
odyssey4meif someone names their cell "cell12" then it might not be right - but we're using safe defaults here18:58
kashyapdansmith: To finish up, for completeness' sake: The QEMU / libvirt 3.9.0 "pause-before-switchover" thing -- it won't be useful in Nova's case, as that will stop the guest CPUs, which will extend the guest down time.)18:58
odyssey4mealthough the spacing in that grep should be reasonable to protect the boundaries18:59
* kashyap goes to feed himself18:59
*** amodi has quit IRC18:59
*** AlexeyAbashkin has joined #openstack-nova19:00
*** lucasagomes is now known as lucas-afk19:02
mriedemodyssey4me: just to verify, this is running on the newton code before upgrading to ocata yes?19:03
mriedembecause http://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/job-output.txt.gz#_2018-02-05_18_10_32_079153 returns version 21 for the nova_api db which was the version in newton19:03
odyssey4meyep, the initial build from be from what was the head of stable/newton at the time the test ran19:04
odyssey4meI'll push a patch up to make it use the EOL branch now :)19:04
odyssey4meoh hang on, I think it mighth be sha pinned19:04
mriedemthere was only one nova_api db change in newton before eol https://github.com/openstack/nova/blob/newton-eol/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/022_request_specs_spec_mediumtext.py19:04
mriedemand shouldn't have anything to do with what you're seeing19:04
odyssey4meheh, that makes it even weirder that this failed: https://github.com/openstack/openstack-ansible-tests/blob/stable/newton/test-vars.yml#L15719:05
dansmithkashyap: yeah that's why I said it didn't seem like it would :)19:05
mriedemodyssey4me: so everything in that console output looks ok to me,19:06
mriedemwhere do instances actually get created in newton before the upgrade is started?19:07
dansmithkashyap: I was also really looking for you to comment on the potential race with the setting of the bandwidth limit in two places.. did you look at that at all?19:07
mriedemodyssey4me: i.e. how do you know that you've actually got instances from newton to map when map_instances runs?19:07
kashyapdansmith: No, not yet.  After I finish dinner19:07
* kashyap bbiab19:07
*** r-daneel_ has joined #openstack-nova19:08
*** david-lyle has joined #openstack-nova19:08
odyssey4memriedem by 'instances' do you mean the compute host? The terminology is confusing to me here... because in this CI run no instance (by this I mean a cloud instance, not a nova hypervisor) is created until *after* the upgrade when tempest executes.19:08
*** yamamoto has quit IRC19:08
*** david-lyle has quit IRC19:08
*** david-lyle has joined #openstack-nova19:09
*** r-daneel has quit IRC19:09
*** r-daneel_ is now known as r-daneel19:09
*** amodi has joined #openstack-nova19:09
mriedeminstances == vms19:09
mriedemodyssey4me: ok then map_instances isn't going to map anything :)19:09
mriedemmap_instances means create nova_api.instance_mappings records in the db19:10
mriedembased on VMs in the 'nova' db19:10
mriedemthe 'nova' db is the cell1 db19:10
mriedemodyssey4me: so looking at https://pastebin.com/C9ji6vdS again, when/how did either of those instances get created?19:11
mriedemthe ones passed to verify_instance19:11
odyssey4meok, btw if we're doing something dumb here then please feel free to say so with any improvement suggestions :)19:11
mriedemodyssey4me: the ansible tasks all look fine19:11
mriedemthe ansible is like a step for step copy of what's in the install guide here https://docs.openstack.org/nova/latest/user/cells.html19:11
odyssey4meok, given that I did those commands after the test failed, those instances would have been created by tempest after the upgrade completed19:11
odyssey4methe one thing that may not have run here is the online migrations19:12
dansmithkashyap: okay thanks19:12
mriedemodyssey4me: do you see any errors in the nova-api logs?19:12
mriedemor nova-conductor?19:12
mriedemalso, based on that git hash for nova, the CI isn't picking up any bug fixes since the newton GA19:13
mriedemwhich seems less than ideal19:13
odyssey4menova-conductor: No host-to-cell mapping found for selected host ocata-nova1. Setup is incomplete.19:16
odyssey4meFailed to compute_task_build_instances: Host 'ocata-nova1' is not mapped to any cell19:16
hrwhttps://marcin.juszkiewicz.com.pl/2018/02/06/graphical-console-in-openstack-aarch64/ - please read ;)19:17
*** Tom-Tom has quit IRC19:20
*** jafeha has quit IRC19:21
*** Tom-Tom has joined #openstack-nova19:22
tssuryaodyssey4me: can you check the value of the "mapped" column inside compute_nodes table of the nova db (cell1 db), ? if you have this host there, then there should be a record19:24
odyssey4mehmm, select mapped from compute_nodes; gives me an unknown column error19:26
odyssey4meyup, none of those are working19:26
odyssey4menone of the db's have that column19:27
*** Tom-Tom has quit IRC19:27
*** salv-orlando has joined #openstack-nova19:28
tssuryathere should be a table called compute_nodes only in your nova db19:29
tssuryanot in the api19:29
tssuryaodyssey4me: that is in the cell1's db19:30
*** salv-orlando has quit IRC19:30
odyssey4meyup, the nova db has that table - but the table has no 'mapped' column19:31
odyssey4metssurya here're the columns present: https://pastebin.com/grmGWEQe19:32
odyssey4metssurya in case you missed it, this is a newton build (with no cells) being upgraded to an ocata build (with cells being setup)19:33
odyssey4mecells v2 to be clear19:33
*** slaweq has joined #openstack-nova19:33
tssuryaodyssey4me: oh okay, ocata..19:35
odyssey4metssurya yep :) ye olde crusty stable code ;)19:35
*** ccamacho has joined #openstack-nova19:36
odyssey4memriedem any further thoughts or ideas? if not I'll work on fixing up the log capturing so that I can point you at a proper set of logs to peruse19:37
mriedemodyssey4me: sorry was eating lunch,19:37
mriedemi think the compute_nodes.mapped column was added in ocata19:38
mriedemthe host 'ocata-nova1' is a problem i think, since an earlier paste showed it was discovered in 2 different cell mappings19:38
*** slaweq has quit IRC19:38
mriedemhttps://pastebin.com/mSwpZybQ19:38
mriedemat this point i'd probably need the logs from an untouched env19:39
odyssey4mealright, thanks much for your time and input so far19:39
mriedemyw19:39
odyssey4meI'll work on getting the log collection fixed up so that we can debug better.19:40
*** baoli has joined #openstack-nova19:41
*** baoli has quit IRC19:42
efriedmriedem: I'm going to put up three pairs of patches to dig a bit deeper, see which part of ServiceTokenAuthWrapper is actually busted.19:44
efriedmriedem: Unless you have some other plan.19:44
mriedemso 6 patches?19:44
mriedemi don't, no :)19:45
mriedemwe might have to put this in the release notes as a known issue19:45
efriedYeah, going to pass through each of the service_auth-y bits of ServiceTokenAuthWrapper - which I have to do in ksa - and then a blank Nova patch for each that Depends-On its ksa buddy.19:45
openstackgerritMatt Riedemann proposed openstack/nova master: Create volume attachment during boot from volume in compute  https://review.openstack.org/54142019:45
mriedemildikov: ^ cleans up that bfv legacy attach stuff19:45
ildikovmriedem: tnx, looking19:47
openstackgerritMatt Riedemann proposed openstack/nova master: DNM: debug nova-api service version check during boot from volume  https://review.openstack.org/54099219:47
*** mgoddard_ has quit IRC19:47
*** lpetrut has quit IRC19:48
*** tssurya has quit IRC19:50
mriedemholy f 679 check queue length19:51
melwittI saw there was a status message about zuul from 02:30 having problems19:52
melwitt"[02:30:17] -openstackstatus-NOTICE: Our Zuul infrastructure is currently experiencing some problems and processing jobs very slowly, we're investigating. Please do not approve or recheck changes for now."19:52
mriedemyeah i knew about that19:53
mriedemmelwitt: you might want to weigh in on this https://review.openstack.org/#/c/532361/19:53
mriedemgiven you'll be the ptl of the project that ruined removing mox in rocky for all projects19:53
melwitt-_-19:53
mriedemas the lame duck ptl, i can only fire shots across the bow19:54
*** imacdonn has quit IRC19:55
mriedembauzas: don't forget https://review.openstack.org/#/c/526095/19:56
cdentmelwitt, mriedem : I recommend either lying ("yeah, sure we can will do it") or just do it19:56
*** imacdonn has joined #openstack-nova19:56
artomStrictly speaking, *removing* mox is easy19:56
mriedemcdent: i assumed we'd do what we have done in previous releases,19:56
artom*Replacing* it with mock, OTOH...19:56
mriedemwhich is we can work on it as a low priority thing19:56
mriedemso it would be what doug said, which is forward progress19:56
cdentmriedem: why not, since it is a goalâ„¢, make it higher priority and use the fact that it is a goal as an excuse to de-prioritize other stuff?19:57
mriedemi don't consider it high priority19:58
cdentisn't that what "openstack wide goals" means?19:59
melwittyeah. while I agree it's a fine thing to do, it's not trivial to review and takes away from reviewing important things like bug fixes and placement work that our users want and need19:59
cdent(to be clear, I'm not too wed to the mox thing, but I do think that the goals process should mean _something_)19:59
melwittand I personally don't get the argument of "maintaining mox3" because, what is there to maintain?19:59
mriedemright, i don't think 'retiring mox3' is a high priority20:00
* kashyap wishes there was a way to update the messy formatting in a long Gerrit comment20:00
*** jafeha has joined #openstack-nova20:00
openstackgerritEric Fried proposed openstack/nova master: DNM: Debug nova-next failure: user headers  https://review.openstack.org/54142720:00
cdentmelwitt: that seems a far more valid response to the goal process20:00
mriedemffs, sqlalchemy-migrate was forked over for openstack usage, and we're still using that gd thing forever20:00
cdentmuch to the chagrin of zzzeek20:01
mriedemthis would be like a goal to migrate every project from sqla-migrate to that other thing20:01
mriedemalembic20:01
mriedemwhich is arguably a more useful goal than removing mox tests20:01
*** owalsh has quit IRC20:02
cdentperhaps one of you should respond to zane with the real reasons you don't want to do it?20:02
*** slaweq has joined #openstack-nova20:02
dansmithdidn't mriedem already do that?20:02
*** owalsh has joined #openstack-nova20:02
*** amoralej is now known as amoralej|off20:02
cdentdansmith: I'm not entirely sure. I just read his most recent response and that doesn't seem to.20:03
*** dtantsur is now known as dtantsur|afk20:03
mriedemi did,20:03
dansmithwasn't his first resposne "because we can't possibly get it done" ?20:03
openstackgerritEric Fried proposed openstack/nova master: DNM: Debug nova-next failure: invalidate  https://review.openstack.org/54143020:03
cdentBut, dansmith, I was just trying to say "instead of talking about it here, maybe talk about it on the review"20:03
mriedemi left comments on the review20:03
cdentright, dansmith, that's not the same as "because we don't think it is worth doing because why not support mox3 forever"20:03
melwittI will be commenting on the review. I'm just talking here for now since we were talking about it20:03
mriedemi won't -1 it because i don't want to further the notion that nova is the project that blocks progress on everything in openstack20:04
cdentyeah, I'm not saying we shouldn't talk about it here too, just hoping it gets reflected there too (it's not like I'd ever want to stop talking about stuff)20:04
dansmithcdent: okay I don't see the difference between what he said (and the implications on mox3) and what we're saying here, but... that's fine20:04
cdentmriedem: but isn't that exactly what zane has implied?20:04
dansmithcdent: that nova is being a blocker on purpose?20:05
openstackgerritEric Fried proposed openstack/nova master: DNM: Debug nova-next failure: connection params  https://review.openstack.org/54143220:05
mriedemcdent: yes it is, but i don't think that means that other projects which actually can get it done and find value in doing it, can/should do it20:05
dansmithI don't think he said that20:05
*** tssurya has joined #openstack-nova20:05
*** tssurya has quit IRC20:05
cdentdansmith: I know it is stupid that for some reason the details of this stuff become such a thing, but they do. The conversations that various members of the TC have had about the goals process have been _involved_20:05
mriedem*shouldn't do it20:05
cdentdansmith: not on purpose, but sort of de facto20:05
cdentbut yeah, whatever, I personally don't really care about the mox goal (or any of them really)20:07
bauzasmriedem: +Wd, thanks20:07
efriedmriedem: It occurs to me that disabling bits of the service auth token will have impact outside of glance.20:07
bauzasoh man, mox20:07
cdentmriedem: thanks for that final explicit comment20:07
bauzaswow, https://review.openstack.org/#/c/534605/ too20:09
*** rmart04 has joined #openstack-nova20:09
mriedembauzas: that one is much more focused and easy20:09
mriedemall it is is make the debug option mutable20:09
mriedemwith a sighup20:09
mriedemit's not "make all options mutable"20:10
cdentit was initially20:10
bauzasI'm still chilling20:10
*** rmart04 has quit IRC20:10
cdentbut I nipped it20:10
bauzasanyway, time will see20:10
bauzasthe problem is not about having a mutable conf opt :)20:11
mriedemcdent: good - that's how i first read that one, until i re-read it20:11
bauzasit's rather about making sure nova can sighub20:11
kashyapdansmith: So, on that potential race-thing, did you see the comment with more Neutron-educated Sean Mooney?  He makes a good point when he says:20:11
kashyap"it would be nicer to have a solution that is always guaranteed to work but even with a race it much less likely to be noticed then the race we have today were the RARP packets from qemu are often lost as the nic is not wired up."20:11
mriedemsighub - the special interest group for github20:11
bauzasoops20:12
bauzassighup :p20:12
bauzaskill -1 :p20:12
* kashyap --> Off for the night20:12
bauzasmriedem: oh btw. why have I a plumage for our team ? :p20:13
mriedembauzas: you're the only one with a high enough plumage score20:14
mriedemfrench20:14
mriedemmandatory minimum level of plumage20:14
dansmithkashyap: that has nothing to do with the race I was asking about20:15
bauzasmriedem: because we are all cocks ? :)20:15
mriedemha20:15
* kashyap goes to re-read dansmith's comment in the scroll20:15
kashyapdansmith: Okay, I see  -- you're asking the impact of setting it in two places20:16
dansmithkashyap: yes and in two threads20:16
odyssey4memriedem actually, we have some logs from just the standard upgrade test: http://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/20:16
kashyapSo in the existing code in _live_migration(), guest.migrate() is already called with 'CONF.libvirt.live_migration_bandwidth'.  And then...20:16
openstackgerritChris Dent proposed openstack/nova master: WIP: Isolate placement database config  https://review.openstack.org/54143520:16
kashyapdansmith: A test result with log would convince you I suppose?20:16
odyssey4memriedem the 'host' folder will have the nova-compute logs, and the 'openstack' folder will have the other nova services logs20:16
*** r-daneel_ has joined #openstack-nova20:16
dansmithkashyap: no of course not..  if it's a race then a passing test means nothing :)20:17
mriedemodyssey4me: holy wingdings batman http://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/openstack/openstack1/nova/nova-api-os-compute.log.txt.gz.txt.gz20:17
odyssey4meouch20:17
mriedemoh here we go http://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/openstack/openstack1/nova/nova-api-os-compute.log.txt.gz20:17
kashyapdansmith: An automated test that repeats, say 100 times?20:17
openstackgerritKen'ichi Ohmichi proposed openstack/nova master: TrivialFix: Add a space between messages  https://review.openstack.org/54143620:17
dansmithkashyap: are you joking? I can't tell20:17
kashyap:P20:17
*** r-daneel has quit IRC20:17
*** r-daneel_ is now known as r-daneel20:17
kashyapOkay, it's clearly too late for me20:17
odyssey4melooks like we have a bug in the log collection - I'll figure that out20:17
* kashyap wil come back afresh tomm.20:17
dansmithkashyap: and if not, no. we have races that sit dormant for years until something changes in infra, things go in a different order, and we start getting breakage20:17
dansmithkashyap: ack20:18
openstackgerritKen'ichi Ohmichi proposed openstack/nova master: TrivialFix: Add a space between messages  https://review.openstack.org/54143620:18
*** slaweq has quit IRC20:18
mriedemodyssey4me: ok here was that error you mentioned http://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/openstack/openstack1/nova/nova-conductor.log.txt.gz#_2018-02-05_18_19_11_42820:18
odyssey4memriedem yep, eith the instance error state just a little later20:19
*** slaweq has joined #openstack-nova20:19
mriedemodyssey4me: i see that nova-manage cell_v2 create_cell didn't exist in newton, so when those commands run, are they against ocata?20:21
odyssey4meyes, in our newton deploy there is no cell management done20:21
kashyapdansmith: Scooping up my final active neurons: You want to see clear _functional test_ evidence that the override of CONF.libvirt.live_migration_bandwidth doesn't happen, yes?  (Though, Sahid claims it doesn't.)20:22
odyssey4memriedem newton only does these: https://github.com/openstack/openstack-ansible-os_nova/blob/stable/newton/tasks/nova_db_setup.yml20:22
dansmithkashyap: no.20:22
mriedemodyssey4me: there are a bunch of errors in the nova-compute logs http://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/host/nova/nova-compute.log.txt.gz20:22
dansmithkashyap: I want human analysis of whether or not setting the thing to 1 and 100 in two threads is asking for trouble20:23
dansmithkashyap: as far as I can tell, the migration is started with the CONF value, and then set to 1 to slow things down, but there is no locking or mechanism to ensure the slowdown call is done after the value is set to the one from conf20:23
*** guest___ has joined #openstack-nova20:24
odyssey4memriedem hmm, even late in the log, yes: http://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/host/nova/nova-compute.log.txt.gz#_2018-02-05_18_15_57_44920:24
kashyap(Okay, between the two threads where it is being set.   Needs more code reading...)20:24
odyssey4memriedem actually, that seems to recover: http://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/host/nova/nova-compute.log.txt.gz#_2018-02-05_18_15_57_46920:24
dansmithkashyap: I can ask someone else, I thought you would be able to dig into the libvirt docs and validate or discredit sahid's assertion that it doesn't matter (which doesn't make sense to me)20:24
*** guest___ has quit IRC20:24
kashyapdansmith: Yeah, it is started with the CONF value20:24
dansmithkashyap: right, but I don't think there's anything that ensures that that is set before we make the call to slow it down20:25
*** mgoddard_ has joined #openstack-nova20:25
mriedemodyssey4me: right it logs a warning on the first time it doesn't find it20:25
dansmithkashyap: so it seems to me like it could be started, not reach the point at which the conf value is used, we set the speed limit, then the conf value gets applied20:25
odyssey4methese are somewhat odd though: http://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/host/nova/nova-compute.log.txt.gz#_2018-02-05_18_14_01_86020:25
kashyapdansmith: Okay, you'd want to know how the two values that are being set are coordinated with some locking mechanism with the underlying libvirt API20:25
*** ameeda_ has joined #openstack-nova20:26
dansmithkashyap: no. nevermind, go to sleep, I'll try to dig into it20:26
* kashyap stops being stupid and goes to sleep20:26
mriedemodyssey4me: ok so in the console output, we see that compute show up in the service list here http://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/job-output.txt.gz#_2018-02-05_18_15_43_55774820:26
ameeda_mriedem: Hello :)20:27
mriedemodyssey4me: it might be worthwhile to run discover_hosts with --verbose http://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/job-output.txt.gz#_2018-02-05_18_15_48_02454320:28
mriedemto see what it dumps out20:29
mriedemodyssey4me: i do remember that with devstack-based CI, we'd have issues in grenade where nova-compute would take awhile to bring up and create the compute_nodes record, and discover_hosts would miss it20:29
*** jamesdenton has joined #openstack-nova20:29
mriedemhttps://review.openstack.org/#/c/488381/20:30
odyssey4memriedem yeah, that's why we added the wait until a compute agent was found - that seems to have worked for us so far, but perhaps we need more sheps20:30
mriedemhowever, you have that "openstack compute service list" check20:30
mordredefried: looks like you have a fun debugging task on your plate20:31
*** awaugama has quit IRC20:31
odyssey4mebut yeah, lemme add the --verbose CLI option when our debug flag is enabled, which would be very useful here20:31
efriedmordred: indeeed20:31
mriedemodyssey4me: are the /etc/ files captured?20:33
odyssey4memriedem unfortunately not - we had to turn that off 'cos we were eating up all the infra inodes :/20:33
odyssey4mewe could add that back, but tar.gz them so we eat fewer inodes :)20:33
mriedemok, i can't tell if the [database]/connection value in nova.conf that the nova-compute is using is the same database connection as the cell1 this creates20:33
*** ameeda_ has quit IRC20:36
*** vladikr has quit IRC20:36
mriedemodyssey4me: anyway i think we can see that the compute_nodes entry is created here for the compute host http://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/host/nova/nova-compute.log.txt.gz#_2018-02-05_18_15_57_46920:36
*** READ10 has quit IRC20:36
mriedemat 18:15:57.46920:36
mriedemit shows up in the service list here:20:36
mriedemhttp://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/job-output.txt.gz#_2018-02-05_18_15_43_55774820:36
mriedem"end": "2018-02-05 18:15:43.505982",20:37
odyssey4memriedem db config template is here, if that helps a bit: https://github.com/openstack/openstack-ansible-os_nova/blob/stable/ocata/templates/nova.conf.j2#L213-L23320:37
odyssey4meeach db will have a unique name, and each db user/password will also be unique20:37
*** mgoddard_ has quit IRC20:38
dansmithkashyap: I explained my concern in more detail, maybe you could dig into docs/code tomorrow with that extra info to validate one way or the other?20:38
mriedemodyssey4me: looks ok20:39
openstackgerritmelanie witt proposed openstack/nova master: Refine waiting for vif plug events during _hard_reboot  https://review.openstack.org/54144220:39
dansmithmelwitt: nice20:41
mriedemodyssey4me: also throw the --verbose option on create_cell20:41
*** sridharg has quit IRC20:42
mriedemultimately my guess is discover_hosts isn't picking up the compute host and mapping it to the cell20:43
mriedemjust not sure why20:43
mriedemcould be a timing issue, but that's what the openstack service list check is for20:43
melwittdansmith: thanks for pointing it out on the original review20:44
dansmithmelwitt: yar20:44
efriedmriedem: What's your trick for seeing those nova-new results before they're reported to gerrit?20:44
dansmithmelwitt: that race is the whole reason I wrote this eventing stuff so I get all sad when it gets broken20:44
odyssey4meyeah, that's my one suspicion... a race condition of some sort - the other is that perhaps there's an online migration required which wasn't executed20:45
mriedemefried: status.openstack.org/zuul20:45
mriedemodyssey4me: i see that the online data migrations are skipped20:45
efriedOh, look, those are links!20:45
odyssey4memriedem thanks again for looking through all that, and for sanity checking the process to verify that everything looks like it's doing what it should... I'll get a better set of test logs/configs going and we can revisit when those are good20:45
mriedemodyssey4me: http://logs.openstack.org/29/540329/5/check/openstack-ansible-upgrade-ubuntu-xenial/30ae3e2/job-output.txt.gz#_2018-02-05_18_03_50_70990420:46
mriedem<openstack1> Task "Disable the online migrations requirement" has been omitted from the job because the conditional "[u"inventory_hostname == groups['nova_conductor'][0]", u'not data_migrations | skipped', u'data_migrations | succeeded']" was evaluated as "False"20:46
odyssey4memriedem yep, they're skipped due to the check to see whether all hosts are upgraded before running them... and I don't think we have something in these role tests which actually check for that and execute them, so I think I'll patch that up20:46
*** traskat has quit IRC20:46
odyssey4meI thought we had one, but perhaps it got patched in later and not ported back20:47
efriedeff me, guess I need to wait for some of those four hundred patches to clear out of the check queue.20:47
melwittdansmith: understandable. I'm pretty new to the neutron event scene and have been learning20:47
*** vladikr has joined #openstack-nova20:49
*** chyka_ has quit IRC20:49
*** hongbin has joined #openstack-nova20:50
efriedD'oh.  The check queue seems to be smart enough not to run functional tests if no .py files were touched.20:54
mriedemsomeone want to fast approve this? https://review.openstack.org/#/c/539978/20:55
openstackgerritEric Fried proposed openstack/nova master: DNM: Debug nova-next failure: user headers  https://review.openstack.org/54142720:56
openstackgerritEric Fried proposed openstack/nova master: DNM: Debug nova-next failure: invalidate  https://review.openstack.org/54143020:56
openstackgerritEric Fried proposed openstack/nova master: DNM: Debug nova-next failure: connection params  https://review.openstack.org/54143220:56
efriedmriedem: There is no fast.  There is only zuul.20:57
sean-k-mooneyefried: zull used to be fast for small projects. now zuul is fair to all projects. as some who also works on small projects this make me sad20:58
efriedSeems snappy for nova-powervm - unless the whole world is broken.20:58
sean-k-mooneyefried: ah well the upstream zuul used to round robin taking the first job from each queue in a pipline so small pojects with short to no queue were more likely to have jobs run. now it handels jobs in the order it arrived being fair to all pojects21:00
*** takamatsu has quit IRC21:01
cdentmelwitt, mriedem: would you have any objection to me setting a little goal for myself for nova: remove code from all the __init__.py files (to avoid inadvertent imports)? That is, if I were to do it, is there a chance it would get merged.21:01
sean-k-mooneyefried: if you have your own zuul instance for thirdparty testing then it is still fast for your on defintion(policy of job selection) of fast21:01
mriedemcdent: that's somehow related to splitting out placement right?21:02
cdentmriedem: I discovered it because of that, yes, but it's also beneficial for the rest of nova: the fact that it is a common behavior means that various processes are often importing many more modules than they actually need.21:03
mriedemi'd say it has as good a chance at getting merged as anything else21:03
sean-k-mooneycdent: mriedem even if it not related to splitting out placement can we do it anyway. haveing side effect form importing moduels makes testing harder and is really unintuitive to people who have not worked with that module before21:04
cdentmriedem: for latest example see my note to self on https://review.openstack.org/#/c/541435/21:04
mriedemsean-k-mooney: you act like i said no one could push patches21:04
cdentwould a spec or blueprint be of any value?21:05
sean-k-mooneymriedem: hehe sorry i know that is not what you ment. i just hate seeing __init__.py files with anything but constants in them21:05
mriedemcdent: idk21:05
sean-k-mooneymriedem: its a pet pev of mine.21:06
mriedemcdent: if it's a non-trivial amount of work, and is a depednency for the eventual placement split, then i could see a specless bp21:06
cdentyeah, sadly it would probably be non-trivial as it often ends with wiggle here causing ripples way over there21:07
cdentI'll put it my queue, thanks.21:07
cdentand I think that can be the end of my work day21:08
sean-k-mooneycdent: that part of why i dont like that patten in python. for example import anyting in nova.cmd results in your process being monkey patched https://github.com/openstack/nova/blob/master/nova/cmd/__init__.py21:08
cdentyup21:09
cdent'night all21:09
*** cdent has quit IRC21:09
*** artom has quit IRC21:13
openstackgerritMerged openstack/nova master: Add PowerVM to feature-classification  https://review.openstack.org/53323721:16
efriededleafe: yt?21:16
*** hemna_ has quit IRC21:17
*** AlexeyAbashkin has quit IRC21:21
kashyapdansmith: Okay, after watching the Falcon launch, I came back to IRC21:21
kashyapdansmith: Saw your comment in the review.  Much clearer.21:22
kashyapSo, I asked a libvirt dev who does migration to look into it -- Will the 'bandwidth' parameter of  migrateToURI2() will be ignored if it was previously set by the API migrateSetMaxSpeed()?21:22
mriedemdansmith: i'm going to announce this here publicly, but melwitt has never been asked to give a sizing21:23
mriedemsdague: ^ is that an ibm only thing?21:23
edleafeefried: ?21:23
mriedemmelwitt: this was much more fun before you said LOEs21:24
efriededleafe: Wanted to do a quick brainstorm if you have a mo.21:24
melwittmriedem: haha, sorry21:24
sean-k-mooneymriedem: a sizing of a task? if so how, i get ask that all the time for stuff i dont even work on21:24
kashyapdansmith: Will respond on that review once I dig into the Python bindings and upstream relevant APIs to confirm what you asked.  (Also double-confirm with a libvirt upstream dev.)21:24
edleafeefried: sure21:24
* kashyap now _really_ off21:24
mriedemsean-k-mooney: of course you do, because you work at a corporation21:24
sean-k-mooneymriedem: :) ah so thats where i went wrong.21:25
efriededleafe: Trying to think through an easy way to get NUMA affinity in placement modeling.  First off, do you understand the stuff Jay has been talking about, something about aggregate "distance"?21:25
edleafeefried: vaguely21:25
efriededleafe: Can you help me understand it?21:26
openstackgerritTakashi NATSUME proposed openstack/nova-specs master: List/show all server migration types  https://review.openstack.org/54025621:26
openstackgerritTakashi NATSUME proposed openstack/nova-specs master: Abort Cold Migration  https://review.openstack.org/33473221:26
sean-k-mooneymriedem: also because of that we are ment to track everything we do upstream and in jira and in downstream tools with vendors ... corporate processes :)21:26
openstackgerritTakashi NATSUME proposed openstack/nova master: Transform live_migration_post_dest notification  https://review.openstack.org/46978421:26
edleafeefried: my weak understanding is that it would favor RAM that is associated with a given NUMA node, but that if there wasn't enough, it would use RAM that was "further away"21:27
efriededleafe: Okay, but how does this "distance" thing get defined?21:27
edleafeefried: that's the part that I don't have any clue about21:27
openstackgerritTakashi NATSUME proposed openstack/nova master: [cellv2] Improve getting BDMs in multiple cells  https://review.openstack.org/52140021:28
openstackgerritTakashi NATSUME proposed openstack/nova master: [cellv2] Improve getting BDMs in multiple cells  https://review.openstack.org/52140021:28
mriedemsean-k-mooney: do you track how much time you aren't spending working on grant requests when you should be?21:28
efriededleafe: Okay, me neither.  So starting from first principles, I was thinking about how one could model NUMA affinity.  And here's what I came up with:21:28
edleafeefried: you'd have to have Jay give a lesson on this (to all of us)21:28
efriededleafe: GET /allocation_candidates?<...the usual resource requests...>&affine_resources=<resource_class>,<resource_class>,...21:29
mriedemefried: L142 https://etherpad.openstack.org/p/nova-ptg-queens-placement21:29
sean-k-mooneymriedem: hehe if it did i would cry21:29
*** salv-orlando has joined #openstack-nova21:30
efriedmriedem: Thanks.  Will dig.21:30
efriededleafe: So first of all, it would only apply to the unnumbered request group.  Because you're already getting same-provider "affinity" in the numbered groups.21:30
*** felipemonteiro has joined #openstack-nova21:31
efriededleafe: So within the unnumbered request group, the API would force the resources from classes you list to come from either the same provider, or the same aggregate.21:31
efriededleafe: I'm not sure an anti_affine_resources makes any sense, but could be added if it does.21:32
*** threestrands has joined #openstack-nova21:32
edleafeefried: "affine"?21:32
edleafeefried: How would that specify RAM, PCI deveice, etc., associated with a given NUMA?21:33
efriededleafe: Okay, let me give a more complete example, make more sense.21:33
*** salv-orlando has quit IRC21:33
sean-k-mooneyedleafe: anti_affine_resources for nic bonding e.g. antiafintiy of the pf for the VF request21:34
sean-k-mooneyefried: ^21:34
efriedsean-k-mooney: ack21:34
efriededleafe: To start with, model NUMA nodes as subtrees under the root compute host RP (which may not in fact provide any resources).  So maybe the first tier children provide CPU & memory, and the second tier (grandchildren) are the network devices providing VFs.21:35
efriededleafe: Associate each child/grandchildren in a given NUMA node with the same aggregate UUID.21:35
efriededleafe: Then your request would be like GET /allocation_candidates?resources=VCPU:2,MEMORY_MB:2048,SRIOV_NET_VF:1,DISK_GB=2048&affine_resources=VCPU,MEMORY_MB,SRIOV_NET_VF21:36
edleafewhy can't the network devices be children of the NUMA node?21:37
efriedThey are21:37
efriedswhat I said21:37
efriedSorry, to rephrase:21:37
sean-k-mooneyefried: but the cpu and memory shoudl also be childeren of the numa node too21:37
edleafe"and the second tier (grandchildren) are the network devices providing VFs."21:37
efriedsean-k-mooney: The CPU/mem are resources provided by the numa node which is the RP.21:37
sean-k-mooneyefried: ah they are inventories of the numa node rather then sub resouce providres but that means you can have traints on the cpu and ram21:38
sean-k-mooney*can't have traits21:39
efriedSo root RP is the compute node.  It provides no resources.  It has two child RPs, representing NUMA nodes.  They provide VCPU and memory inventory.  Then those guys have child RPs representing network devices, providing VF inventory.21:39
*** pchavva has quit IRC21:39
edleafeefried: one thing we learned back in Atlanta was that this stuff was much better discussed with a drawing surface so that all could see the relationships21:39
edleafeThose of us who think visually need that for anything other than the trivial stuff21:40
mriedemhttps://awwapp.com/# ?21:40
efriedsean-k-mooney: Yeah, that would be another way to do it: model the NUMA provider as an empty child of the empty root compute host and give the NUMA provider three grandchild tiers which provide CPU, memory, and VFs.21:40
efriedBut not to get hung up on those details.21:40
edleafemriedem: sure. efried, have at it!21:40
mriedemor https://webwhiteboard.com/21:41
edleafeAnd I'm still not clear how "distance" figures into any of this21:41
mriedemi won't be joining, but just being super helpful21:41
*** dave-mcc_ has quit IRC21:41
efriededleafe: It doesn't.  This is purely one-dimensional affinity.  Either they're in the same agg or they're not.21:41
edleafeefried: ok, that's where I was not clear21:42
*** jmlowe has quit IRC21:42
*** hemna_ has joined #openstack-nova21:42
*** jafeha__ has joined #openstack-nova21:42
edleafeefried: won't the current NRP stuff handle this without additional work? IOW, the CPU,RAM,VF all have to21:43
edleafebe from the same provider21:43
efriedOnly if we can model them as belonging to the same provider.21:43
sean-k-mooneyedleafe: distance was discused in 2 forms. 1 a distance in nodes along the provider tree and 2 a distence to a shared resouce provider and an aggreate member to model things like network latency for share storage21:43
efriedWhich we can do for just CPU/memory, but not for VFs.21:44
*** jafeha has quit IRC21:44
edleafeefried: yeah, I guess it could think of the compute node as the root provider, and then stuff from different NUMA nodes would match21:44
efriedAnd also splitting things up more allows us to tie traits more specifically to their resources, if that matters.21:44
edleafesean-k-mooney: I remember the shared distance thing. I thought that was discarded as not needed, because you could just create tighter aggregates so that only "near" storage would ever be used21:45
efriedsean-k-mooney: I tried thinking about distance along a tree, but kept painting myself into a corner where that would severely restrict how things would have to be modeled.21:46
sean-k-mooneyedleafe: yes proably its been a while since denver21:46
efriedsean-k-mooney: Do you understand the concept of distance as relates to aggregates?  Cause I don't.21:46
efriedhttps://awwapp.com/b/umrhofjje/21:47
*** hemna_ has quit IRC21:48
edleafeefried: so we would use aggs to denote a NUMA node?21:49
efriedaggzactly.21:50
edleafeugh21:50
*** itlinux has quit IRC21:50
edleafeyou'd probably have to extend the aggs to include the compute node, no?21:51
efriedI don't know how we get anti-affinity with this, though.  Anything down the anti_affine_resources thought path is bringing my head crashing against a brick wall.21:51
efriedThe least of the problems being the lack of symmetry.21:52
sean-k-mooneyefried: not very well. the distance along the tree i understand. all inventoies of the same resouce provider have a distance of 0, parent/direct chile is distance or 1 and so on21:52
efriededleafe: I don't think so, in this case, since the compute node isn't providing any resources.21:52
edleafeefried: I was just thinking of the eventual monster SQL that would have to return the CN21:52
* edleafe has to step away for a few minutes21:53
efriededleafe: That's another topic, but IMO we could be doing stuff with way simpler (though possibly less efficient) SQL that would be way more flexible and provably correct.21:53
openstackgerritMatt Riedemann proposed openstack/nova master: Address comments from I51adbbdf13711e463b4d25c2ffd4a3123cd65675  https://review.openstack.org/54145521:54
efriedsean-k-mooney: Right.  And I suppose as long as the model is somewhat symmetrical (that is, all providers of a given resource are always at the same level of the tree - which shouldn't be too hard to encourage) and mutually understood by the dev and the op for a given driver (which pretty much has to be the case anyway) it could probably be made to work.21:54
*** itlinux has joined #openstack-nova21:55
sean-k-mooneyedleafe: well if recall correctly jay did not want this to be handeled in the sql code but rater in a filter due to the complexity of the sql21:55
sean-k-mooneythat said perhaps that was just for numa and not distance in general21:56
sean-k-mooneyif there is a relitivly effcient way to handel numa/distance in sql without lots of complexity and ram the sql would certenly be better.21:59
sean-k-mooneyactuly when i said filter i think i should have said python e.g. placement would still do the filting not the nova filters22:00
*** ccamacho has quit IRC22:01
efriedsean-k-mooney: I'm on board with that.22:01
openstackgerritmelanie witt proposed openstack/nova master: WIP Refine waiting for vif plug events during _hard_reboot  https://review.openstack.org/54144222:02
efriedSwhat I was hinting at earlier: we should be doing more of the processing in python, when it comes to the really complex stuff.  The SQL is too hard to understand, too hard to test/prove, and too few people grok it.22:02
* edleafe is back22:04
edleafeefried: 100% on the non-SQL processing22:04
edleafeefried: I think Jay likes the challenge. :)22:04
*** salv-orlando has joined #openstack-nova22:05
efriedNo doubt.  And no doubt when we get it right it's way more efficient.  But over this release I've come to think it's not worth the tradeoff.22:05
sean-k-mooneyedleafe: perhaps buy would you like the code review :)22:05
edleafeI'd rather review python than sqla22:06
efried++22:06
efriedOkay, well, I was coming into this thinking about proposing a spec to handle affinity in Rocky.22:07
edleafeI also think that subtle bugs are more readily spotted in code22:07
edleafeI used to be a SQL DBA, and I still can't catch all the implications of some of the sqla used in placement22:08
efried...But I don't think I have a good enough handle yet on the use cases; and I think I need to understand this idea of "aggregate distance" before putting anything on paper.22:09
edleafeat some point you have to specify NUMA in the request, no?22:09
efriedWell, no.22:09
efriedWith the model as I've described it, you would never have to say NUMA in any context.22:10
efriedYou just have to say "keep these resources together"22:10
efriedand placement understands what you mean by "together" (because that's how we design it)22:11
edleafeefried: sure, but what I meant is that you don't want to be giving out NUMA nodes to someone who just wants a basic VM22:11
efriededleafe: Totally.  In which case you don't say affine_resources=... at all.  And it operates like it does today.  You get your resources from wherever in the tree.22:11
*** hemna_ has joined #openstack-nova22:12
efriededleafe: Now it's likely I'm still completely misunderstanding how NUMA is actually wired, hardware-wise.22:12
edleafeefried: what I'm saying is that if you request NUMA, the code would ensure that all the resources are provided by a single node.22:12
efriededleafe: But I'm saying you request NUMA not by saying NUMA but by saying affine_resources=<whatever resources need to come from the same NUMA node>22:12
edleafeefried: according to the people who seemed to know more about it than I do, a machine with NUMA can be configured in a variety of ways.22:13
edleafeefried: so if all the resources were provided by a plain compute node, wouldn't that also get returned?22:14
sean-k-mooneyedleafe: yes it they can. i know more about this topic then is good for my health22:14
sean-k-mooneyedleafe: if that compute node has only one memoy controler then by definiton all resocues on that node belong to the same numa node22:15
efriededleafe: Okay, that's a fair point.  Which we could resolve, as you say, by tagging the NUMA RPs with a NUMA trait.22:15
edleafeah good. So efried, just direct your questions to sean-k-mooney22:15
sean-k-mooneyso all compute nodes always have at least 1 numa node22:15
*** openstackgerrit has quit IRC22:16
efriedOkay, so the only way to get non22:16
efriednon-NUMA-ness is to go to a system that has more than one NUMA node and get resources spread out across them.22:16
efriedIn which case we *don't* need the trait.22:17
sean-k-mooneyefried: and if you incldue a distance to restict it22:17
*** salv-orlando has quit IRC22:17
sean-k-mooneyif you have multiple numa node and put no constraitn on the distance between resocues in the tree then you get resouce from different numa nodes22:18
sean-k-mooneyyour performace will be less but it will still work22:18
sean-k-mooneyand you never asked for any afintiy so it fine22:18
efriedOkay, so this is a workable thing for NUMA affinity.  I don't think the same mechanism can be made to work for affinity in general, or for anti-affinity.22:21
*** openstackgerrit has joined #openstack-nova22:21
openstackgerritMatt Riedemann proposed openstack/nova master: Move the nova-next job in-tree and update it  https://review.openstack.org/54147422:21
sean-k-mooneyefried: if you dont have to deal with aggreates then i think it will work not sure how distance is compute for aggregates however.22:22
efriedsean-k-mooney: I'm talking about using one aggregate per NUMA node (so nothing to do with distance).22:22
sean-k-mooneywhen modeling afinity via distance affinty becoures deistnace < X and anti afinity is distance > X22:23
sean-k-mooneyefried: oh then ya if numa nodes are aggrages then that is different22:23
efriedYeah, I get that, but *modeling* and *expressing* distance seems really complicated for people to understand.22:23
cfriesenefried: one aggregate per numa node?  would you then associate a pool of RAM, CPUs, PCI devices, etc, with that aggregate?22:24
cfriesenat probably 2-4 numa nodes per compute node that seems like a lot of aggregates22:24
sean-k-mooneyyou would make the cpus/ram/pci devices resouce providers members of the aggregate22:24
efriedcfriesen: You associate the resource *providers* with the aggregate.  So whatever providers provide the resources associated with your NUMA node.22:25
efriedyeah, what sean said.22:25
efriedNo, it would be one aggregate per NUMA node, period.22:25
sean-k-mooneyefried: not one aggregate per numa node per host?22:25
efriedsean-k-mooney: Yes.22:25
efriedOne aggregate per NUMA node, in the global sense :)22:26
sean-k-mooneyoh ame that aggreate will be am large22:26
efriedIs that "a lot" of aggregates?  Meh.  Aggregates are cheap.22:26
efriedI feel like we're not talking in the same terms.  Here: If you have 10 hosts, and each host has 2 NUMA nodes, you have 20 aggregates total.22:27
sean-k-mooneyi think i would prefer lots of small aggregate then a few giant cluster wide ones22:27
sean-k-mooneyefried: ah ok that what i was thinking we should have if we used aggregates so im cool with that22:27
*** jmlowe has joined #openstack-nova22:28
*** rcernin has joined #openstack-nova22:28
sean-k-mooneywe dont have traits on aggregates but at least for numa i dont think we need them on teh aggreages so it could work22:29
cfriesenso you'd have these per-numa-node aggregates for system use, then per-host aggregates to match against flavor/image properties and act as availability zones?22:29
efriedsean-k-mooney: We can always stamp the involved providers with traits.  But not sure we need 'em.  At least to mark NUMA nodes.22:29
efriedcfriesen: I know nothing about host aggregates or availability zones.22:30
*** amodi has quit IRC22:30
sean-k-mooneycfriesen: well an aggreaget is just a bag of resouce providers nothing more or less. you can use them to group anything you want22:30
efriedcfriesen: Except that placement aggregates != host aggregates22:30
efriedcfriesen: The other main use case for aggregates is to associate sharing resource providers, like a shared storage pool.22:30
efried^ placement aggregates, that is.22:31
cfriesenefried: okay...I'm not up on the placement terminology. :)22:32
efriedcfriesen: I'm not up on... pretty much everything else.  Between the two of us, we're gonna need a pidgin.22:32
*** tbachman_ has joined #openstack-nova22:33
sean-k-mooneycfriesen: a sharing resouce provider is jsut a normal resouce provider with a trait and then its inventores are consumable by anything in the same aggreates as it22:33
cfriesenso how do we handle the idea of an instance consuming cpu/ram from one placement aggregate but a PCI device from another placement aggregate?  (for the non-strict PCI affinity case)22:34
openstackgerritMatt Riedemann proposed openstack/nova master: Test websocketproxy with TLS in the nova-next job  https://review.openstack.org/51316022:34
mriedemmelwitt: cleaned that up ^22:34
*** tbachman has quit IRC22:34
*** tbachman_ is now known as tbachman22:35
*** chyka has joined #openstack-nova22:35
sean-k-mooneycfriesen: instance consume resocues form invetories provided by resouce providers22:35
melwittmriedem: thanks. sorry I lost track of that one22:35
sean-k-mooneycfriesen: and resouce provires can be member of 0-n aggregates22:35
sean-k-mooneyso you are not consuming form the aggregates22:36
efriedcfriesen: In the design I'm strawpersoning, if you care about CPU/mem affinity and you don't care about VF affinity, you would say affine_resources=VCPU,MEMORY_MB but not SRIOV_NET_VF22:37
*** edmondsw has quit IRC22:37
efriedcfriesen: s/VF/PCI device/ if you wish.22:37
*** edmondsw has joined #openstack-nova22:38
sean-k-mooneyefried: that may break down a bit with anti afinity22:39
efriedsean-k-mooney: I'm saying we're not handling anti-affinity at all with this model.22:39
sean-k-mooneye.g. i want 2 VF whoes parent PF are anti affined22:39
sean-k-mooneyefried: ah ok22:39
efriedsean-k-mooney: Yeah, I get that.  But that's not a NUMA use case, right?22:39
efriedIt's more about HA22:40
efriedredundancy22:40
efriedpowerfail grouping22:40
efriedthat kind of thing.22:40
sean-k-mooneyya its for ha bonding so my bond dont come from the same card22:40
sean-k-mooneye.g. pulling out one cable wont bring donw the bond22:40
efriedSo yeah, this doesn't cover that.  And if there's a generic solution that encompasses both, great.  But I'm gonna have to pick Jay's brain for that.22:40
*** edmondsw has quit IRC22:42
sean-k-mooneyefried: if you can show your propasl support affinity in a clean way and does not block future addtion of anti afinity by design then its better then nothing22:42
sean-k-mooneye.g. we dont have to support everything in one go in rocky22:43
sean-k-mooneyit would be nice however22:43
efriedThat's kinda what I was thinking.  Propose it this way, show that it wouldn't prevent a more generic solution in the future, and then Jay can propose (or not) that more generic solution.22:44
cfriesenefried: what about multi-numa-node guests?  they would need to essentially do numa anti-affinity (but host affinity) between the two pools of memory22:46
efriedcfriesen: What does that mean?  Multi-numa-node guests?  You mean guests that don't care about NUMA affinity?  Or do they explicitly care about *anti* affinity?22:47
sean-k-mooneycfriesen: multi numa guest do not need to be on multiple host numa nodes22:47
cfriesenefried: no, I mean guests with multi numa nodes22:47
sean-k-mooneycfriesen: i consider that limitation in libvirt to be a bug not a feature22:47
*** salv-orlando has joined #openstack-nova22:47
sean-k-mooneylibvirt virt driver that is22:47
cfriesensean-k-mooney: one reason why you might "require" multi-numa-node guests is to get access to more memory bandwidth22:47
sean-k-mooneycfriesen: yes but there is a flavour extra spec defined for that that only the hyperv dirver support22:48
sean-k-mooneycfriesen: i think the libvirt one should too22:49
cfriesensean-k-mooney: sorry, don't follow.22:49
sean-k-mooneycfriesen: hw:numa_mempolicy22:50
cfriesensean-k-mooney: I can currently specify a multi-numa-node guest with libvirt, and I get access to that many host numa nodes, with accordingly more host memory bandwidth.  (presumably combined with dedicated cpus)22:50
cfriesennuma_mempolicy isn't mentioned anywhere in nova22:50
sean-k-mooneycfriesen: i used to be in the hyperv driver22:51
sean-k-mooneyanyway that is off topic22:52
sean-k-mooneyefried: a multi numa gues is a guest with multiple virtual numa nodes22:52
cfriesenefried: and currently they map to different physical numa nodes of the same host.22:52
sean-k-mooneyefried: you can choose what virtual cores are associated to each virtual numa node and you can device the memoy between each virtual numa node22:53
*** itlinux has quit IRC22:53
efriedWell, if you wanted to get that specific, you could probably swang something with granular request groups.22:54
efriedBut we still wouldn't be able to guarantee you anti-affinity.22:54
cfriesenif you can't guarantee numa-antiaffinity it'll change the current behaviour22:54
cfriesen(ie if both virtual numa nodes could end up on the same host numa node)22:55
sean-k-mooneyplacement does not need to give that guarentee22:55
sean-k-mooneythe virt driver can via the resouce tracker22:55
efriedsean-k-mooney: Yeahhhh, but we eventually *should* be able to implement that filter in placement.22:55
sean-k-mooneyor the nova numa topology filter22:55
*** burt has quit IRC22:55
sean-k-mooneyefried: talk to jay about that. in principal i agree22:56
*** pchavva has joined #openstack-nova22:56
sean-k-mooneyi would like placement to fully handel numa. but if it can handel 80% of numa in rocky with the rest in the filetr i would be happy with that too22:57
efriedOkay.  I'll try to put up that spec later this week.22:57
sean-k-mooneycfriesen: im sure you know this also but just requesting guest numa nodes was never ment to give any form of cpu affinity either. from an api perspcetive it does not but for libvir it pince the cores of that numa node to float over a host numa node22:59
sean-k-mooneycfriesen: similay requsting hugepage was not ment to create a numa topology for the guest and also restice the floating cores to a host numa node23:00
sean-k-mooneycfriesen: all of those implit behaviors are internal implentation behaviors of the libvirt driver23:01
cfriesensean-k-mooney: the hugepage one is a qemu limitation though since you can only point at a single backing file for memory23:01
cfriesen(on a given guest numa node)23:01
sean-k-mooneycfriesen: yes and no you numa node number is optionaly and numactl will be used to determin the optimal numa node to use of you dont specify one23:03
cfriesensean-k-mooney: how do you tell qemu to use hugepages without specifying a backing file?23:04
*** slaweq has quit IRC23:04
sean-k-mooneycfriesen: you do specify a backing file but the backing file itesf does not have numa affintiy23:05
sean-k-mooneycfriesen: when you create a hugepage backing file under /dev/hugepages/libvrt/qemu the numa node is not part of the path23:06
*** gjayavelu has quit IRC23:06
sean-k-mooneycfriesen: checkout https://libvirt.org/formatdomain.html#elementsMemoryBacking the note on the nodeset being optional23:06
*** felipemonteiro has quit IRC23:06
*** hemna_ has quit IRC23:07
*** felipemonteiro has joined #openstack-nova23:07
sean-k-mooneycfriesen: tacking hugepages per numa node made the resouce track code simpeler which is why it was doen per numa node originally23:10
*** sdague has quit IRC23:10
*** r-daneel has quit IRC23:12
*** r-daneel has joined #openstack-nova23:13
*** moshele has joined #openstack-nova23:14
*** gjayavelu has joined #openstack-nova23:15
cfriesensean-k-mooney: ah, right.  I was thinking that mapping hugetlbfs was numa-affined, but it's not necessarily.23:17
sean-k-mooneycfriesen: you might be able to do somthing via the mount options but by defualt no23:18
*** felipemonteiro has quit IRC23:18
*** Trident has quit IRC23:18
sean-k-mooneyefried: actully speaking of memory and numa we should really be tracking 4k pages e.g. non hugepage memory per numa node too23:19
sean-k-mooneythe kernel out of memory killer is triggered per numa node not gloably23:19
sean-k-mooneyso the reserved memory config option does not work properly on a numa system23:20
sean-k-mooneyvms can still be killed if a numa node has no memoy left and the kernel need to allocate some on that node but the host othersise has free ram23:20
sean-k-mooneyour just make all your vms use hugepages that works too23:21
*** Tom-Tom has joined #openstack-nova23:21
cfriesenthat's what we do by default (2M pages)23:25
*** Tom-Tom has quit IRC23:26
sean-k-mooneycfriesen: ya we spent 6 months trying to track down what was causeing OOM to kill our vms in the the intel nfv ci and it turned out to be this. hugepages fixed it23:26
sean-k-mooneythe anoying thing was it took about 2-3 weeks to start showing up as it need the memory to become fragmented enough to force it23:27
*** acormier has quit IRC23:28
*** acormier has joined #openstack-nova23:29
*** brad[] has quit IRC23:29
*** acormier has quit IRC23:30
*** acormier has joined #openstack-nova23:30
*** slaweq has joined #openstack-nova23:31
*** acormier has quit IRC23:35
*** pchavva has quit IRC23:36
*** slaweq has quit IRC23:37
*** masahisa has joined #openstack-nova23:41
openstackgerritPatricia Domingues proposed openstack/nova master: load up the volume drivers by checking architecture  https://review.openstack.org/54139323:42
*** masahisa has quit IRC23:44
openstackgerritPatricia Domingues proposed openstack/nova master: load up the volume drivers by checking architecture  https://review.openstack.org/54139323:44
*** moshele has quit IRC23:50
*** rodolof has quit IRC23:53
*** stakeda has joined #openstack-nova23:54
*** artom has joined #openstack-nova23:58
openstackgerritMatt Riedemann proposed openstack/nova master: Add a prelude release note for the 17.0.0 Queens GA  https://review.openstack.org/54149523:58

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!