Friday, 2018-03-23

*** archit has quit IRC00:00
openstackgerritmelissaml proposed openstack/nova-specs master: fix typos in documentation  https://review.openstack.org/54552800:18
*** gyee has quit IRC00:21
*** masber has quit IRC00:22
openstackgerritMerged openstack/nova master: Add disabled field to CellMapping object  https://review.openstack.org/55009000:24
openstackgerritMerged openstack/nova master: Add CellMappingList.get_by_disabled() query method  https://review.openstack.org/55018800:24
*** weshay is now known as weshay_PTO00:25
*** Dinesh_Bhor has joined #openstack-nova00:28
*** hamzy has joined #openstack-nova00:30
*** danpawlik has joined #openstack-nova00:31
*** Dinesh_Bhor has quit IRC00:31
*** Dinesh_Bhor has joined #openstack-nova00:33
*** danpawlik has quit IRC00:36
*** yingjun has joined #openstack-nova00:36
*** yamahata has quit IRC00:38
*** odyssey4me has quit IRC00:38
*** odyssey4me has joined #openstack-nova00:39
*** yingjun has quit IRC00:40
*** _ix has joined #openstack-nova00:42
openstackgerritChris Dent proposed openstack/nova master: WIP: Parse placement forbidden traits query string  https://review.openstack.org/55466500:42
*** yingjun has joined #openstack-nova00:45
*** edmondsw has quit IRC00:46
*** hshiina has joined #openstack-nova00:46
*** _ix has quit IRC00:47
*** idlemind has quit IRC00:47
*** jichen has joined #openstack-nova00:48
*** oomichi has quit IRC00:50
*** sdeath has quit IRC00:57
*** hiro-kobayashi has joined #openstack-nova00:57
*** yingjun has quit IRC01:00
*** gjayavelu has quit IRC01:01
*** esberglu has joined #openstack-nova01:03
*** wolverineav has quit IRC01:04
*** tiendc has joined #openstack-nova01:06
openstackgerritMerged openstack/nova stable/queens: Make archive_deleted_rows handle a missing CONF.api_database.connection  https://review.openstack.org/55374201:07
*** esberglu has quit IRC01:08
*** danpawlik has joined #openstack-nova01:08
*** suresh12 has joined #openstack-nova01:09
*** mriedem has quit IRC01:10
*** masber has joined #openstack-nova01:12
*** harlowja_ has quit IRC01:13
*** yamahata has joined #openstack-nova01:13
*** danpawlik has quit IRC01:14
*** hongbin has joined #openstack-nova01:15
*** zhaochao has joined #openstack-nova01:17
*** licanwei has joined #openstack-nova01:23
*** Tom-Tom has quit IRC01:23
openstackgerritOpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements  https://review.openstack.org/55557601:25
*** bhagyashris has quit IRC01:26
*** germs has left #openstack-nova01:26
*** bhagyashris has joined #openstack-nova01:27
*** Zames has joined #openstack-nova01:27
*** licanwei_ has joined #openstack-nova01:28
*** licanwei has quit IRC01:30
*** sapd has quit IRC01:34
*** Zames has quit IRC01:35
*** wolverineav has joined #openstack-nova01:36
*** elmaciej has quit IRC01:41
*** Tom-Tom has joined #openstack-nova01:41
*** Tom-Tom has quit IRC01:42
*** Tom-Tom has joined #openstack-nova01:42
*** danpawlik has joined #openstack-nova01:47
openstackgerritOpenStack Proposal Bot proposed openstack/python-novaclient master: Updated from global requirements  https://review.openstack.org/55559001:50
*** danpawlik has quit IRC01:51
*** zhurong has joined #openstack-nova01:52
*** sapd has joined #openstack-nova02:01
*** sdague has quit IRC02:04
openstackgerritMerged openstack/nova stable/ocata: Don't try to delete build request during a reschedule  https://review.openstack.org/52970302:11
*** Dinesh_Bhor has quit IRC02:12
openstackgerritPatricia Domingues proposed openstack/nova master: load up the volume drivers by checking architecture  https://review.openstack.org/54139302:21
*** Dinesh_Bhor has joined #openstack-nova02:22
*** danpawlik has joined #openstack-nova02:26
*** germs has joined #openstack-nova02:28
*** danpawlik has quit IRC02:31
*** edmondsw has joined #openstack-nova02:34
*** edmondsw has quit IRC02:39
*** masber has quit IRC02:41
*** salv-orl_ has joined #openstack-nova02:47
*** andreas_s has joined #openstack-nova02:48
*** salv-orlando has quit IRC02:50
*** psachin has joined #openstack-nova02:51
*** andreas_s has quit IRC02:53
*** wolverineav has quit IRC02:54
*** wolverineav has joined #openstack-nova02:55
*** wolverineav has quit IRC02:59
*** danpawlik has joined #openstack-nova03:00
*** danpawlik has quit IRC03:05
*** tuanla____ has joined #openstack-nova03:11
*** yingjun has joined #openstack-nova03:15
*** AlexeyAbashkin has joined #openstack-nova03:15
*** masber has joined #openstack-nova03:19
*** AlexeyAbashkin has quit IRC03:20
*** fragatin_ has joined #openstack-nova03:25
*** yingjun has quit IRC03:25
*** fragatin_ has quit IRC03:27
openstackgerritjichenjc proposed openstack/nova master: remove a comment about ec2  https://review.openstack.org/55561503:28
*** fragatin_ has joined #openstack-nova03:28
*** fragatina has quit IRC03:29
openstackgerritMerged openstack/nova master: Migrate tempest-dsvm-cells job to an in-tree job definition  https://review.openstack.org/54978003:29
*** fragatin_ has quit IRC03:33
*** danpawlik has joined #openstack-nova03:36
*** hshiina has quit IRC03:41
*** danpawlik has quit IRC03:41
*** hshiina has joined #openstack-nova03:42
openstackgerritlicanwei proposed openstack/nova master: Make nova-manage capable of syncing all cell databases  https://review.openstack.org/51927503:42
*** fragatina has joined #openstack-nova03:45
*** vladikr has quit IRC03:46
*** vladikr has joined #openstack-nova03:46
*** liusheng has quit IRC03:47
*** liusheng has joined #openstack-nova03:47
*** hongbin has quit IRC03:47
*** hshiina has quit IRC03:48
*** fragatina has quit IRC03:49
*** fragatina has joined #openstack-nova03:54
*** itlinux has quit IRC03:59
*** hiro-kobayashi has quit IRC04:00
*** germs has quit IRC04:01
*** germs has joined #openstack-nova04:02
*** zhurong has quit IRC04:04
*** hshiina has joined #openstack-nova04:05
*** danpawlik has joined #openstack-nova04:11
*** hiro-kobayashi has joined #openstack-nova04:15
*** inara has quit IRC04:16
*** danpawlik has quit IRC04:17
*** harlowja has joined #openstack-nova04:19
*** inara has joined #openstack-nova04:19
*** fragatina has quit IRC04:19
*** fragatina has joined #openstack-nova04:20
*** weshay_PTO is now known as weshay04:21
*** edmondsw has joined #openstack-nova04:23
*** links has joined #openstack-nova04:26
*** edmondsw has quit IRC04:27
*** moshele has joined #openstack-nova04:29
*** gus has quit IRC04:36
*** gus has joined #openstack-nova04:37
*** abhishekk has joined #openstack-nova04:40
*** udesale has joined #openstack-nova04:41
*** neha_alhat_ has joined #openstack-nova04:44
neha_alhat_Hi All, I just want to know which ubuntu version supports libvirt version >= 3.10?04:44
*** danpawlik has joined #openstack-nova04:45
openstackgerritMerged openstack/nova master: Make nova-cells-v1 run with neutron  https://review.openstack.org/54978904:47
*** danpawlik has quit IRC04:50
*** sapd_ has joined #openstack-nova04:51
*** sapd has quit IRC04:51
*** ratailor has joined #openstack-nova04:59
*** lajoskatona has joined #openstack-nova04:59
*** Dinesh_Bhor has quit IRC05:02
*** Dinesh_Bhor has joined #openstack-nova05:05
*** harlowja has quit IRC05:12
*** lpetrut has joined #openstack-nova05:12
*** imacdonn has quit IRC05:15
*** AlexeyAbashkin has joined #openstack-nova05:15
*** imacdonn has joined #openstack-nova05:15
*** danpawlik has joined #openstack-nova05:16
*** AlexeyAbashkin has quit IRC05:19
*** moshele has quit IRC05:21
*** danpawlik has quit IRC05:22
*** gyankum has joined #openstack-nova05:23
*** neha_alhat_ has quit IRC05:28
*** mdnadeem has joined #openstack-nova05:34
*** yingjun has joined #openstack-nova05:34
*** yingjun has quit IRC05:34
*** yamahata has quit IRC05:38
*** hiro-kobayashi has quit IRC05:39
*** vks1 has joined #openstack-nova05:41
*** elmaciej has joined #openstack-nova05:43
*** suresh12 has quit IRC05:47
*** gjayavelu has joined #openstack-nova05:48
*** yingjun has joined #openstack-nova05:48
*** danpawlik has joined #openstack-nova05:50
*** hiro-kobayashi has joined #openstack-nova05:54
*** danpawlik has quit IRC05:56
*** suresh12 has joined #openstack-nova05:56
*** Tom-Tom_ has joined #openstack-nova05:57
*** suresh12 has quit IRC06:01
*** Tom-Tom has quit IRC06:01
*** Tom-Tom has joined #openstack-nova06:02
*** Tom-Tom_ has quit IRC06:02
*** yingjun has quit IRC06:02
*** neha_alhat_ has joined #openstack-nova06:08
openstackgerritOpenStack Proposal Bot proposed openstack/nova master: Imported Translations from Zanata  https://review.openstack.org/54877206:10
*** sidx64 has joined #openstack-nova06:10
*** sidx64 has quit IRC06:10
*** gjayavelu has quit IRC06:14
*** AlexeyAbashkin has joined #openstack-nova06:17
*** Dinesh_Bhor has quit IRC06:18
*** Dinesh_Bhor has joined #openstack-nova06:19
*** zhurong has joined #openstack-nova06:21
*** lpetrut has quit IRC06:22
*** AlexeyAbashkin has quit IRC06:22
*** sidx64 has joined #openstack-nova06:22
*** fragatina has quit IRC06:23
*** elmaciej has quit IRC06:23
*** neha_alhat_ has quit IRC06:24
*** danpawlik has joined #openstack-nova06:29
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Add host field to InstanceActionEvent  https://review.openstack.org/55514606:30
*** danpawlik has quit IRC06:34
*** lpetrut has joined #openstack-nova06:36
*** sidx64 has quit IRC06:40
*** vivsoni_ has quit IRC06:40
*** vivsoni_ has joined #openstack-nova06:41
*** vivsoni_ has quit IRC06:43
openstackgerritNaichuan Sun proposed openstack/nova master: xenapi(N-R-P): Add API to support vgpu resource provider create  https://review.openstack.org/52031306:43
*** vivsoni_ has joined #openstack-nova06:43
*** fragatina has joined #openstack-nova06:48
*** Tom-Tom_ has joined #openstack-nova06:49
*** alexchadin has joined #openstack-nova06:50
*** Tom-Tom__ has joined #openstack-nova06:50
*** Tom-Tom has quit IRC06:50
*** sahid has joined #openstack-nova06:53
*** Tom-Tom_ has quit IRC06:54
*** sar has quit IRC06:57
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Extract generate_hostid method into utils.py  https://review.openstack.org/55528206:59
*** maciejjozefczyk has quit IRC07:01
*** jichen has quit IRC07:03
*** jichen_ has joined #openstack-nova07:03
*** jichen_ is now known as jichen07:03
*** Tom-Tom has joined #openstack-nova07:04
*** Tom-Tom__ has quit IRC07:07
*** chyka has joined #openstack-nova07:12
*** sidx64 has joined #openstack-nova07:13
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Add host field to InstanceActionEvent  https://review.openstack.org/55514607:13
*** chyka has quit IRC07:17
*** josecastroleon has joined #openstack-nova07:17
*** pcaruana has joined #openstack-nova07:21
*** sar has joined #openstack-nova07:23
*** yingjun has joined #openstack-nova07:25
*** afaranha has joined #openstack-nova07:27
*** sidx64 has quit IRC07:28
*** Dinesh_Bhor has quit IRC07:30
*** zhurong has quit IRC07:30
*** Dinesh_Bhor has joined #openstack-nova07:30
*** sidx64 has joined #openstack-nova07:31
*** sidx64 has quit IRC07:32
*** sidx64 has joined #openstack-nova07:38
openstackgerritOpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements  https://review.openstack.org/55557607:40
*** sidx64 has quit IRC07:42
*** avolkov has joined #openstack-nova07:43
*** sidx64 has joined #openstack-nova07:44
*** Dinesh_Bhor has quit IRC07:44
*** Dinesh_Bhor has joined #openstack-nova07:48
*** damien_r has joined #openstack-nova07:54
*** maciejjozefczyk has joined #openstack-nova07:55
*** lajoskatona has quit IRC07:56
*** lpetrut has quit IRC07:56
*** danpawlik has joined #openstack-nova07:58
*** damien_r has quit IRC07:59
*** edmondsw has joined #openstack-nova07:59
*** danpawlik has quit IRC08:01
*** danpawlik has joined #openstack-nova08:01
*** ccamacho has joined #openstack-nova08:02
*** AlexeyAbashkin has joined #openstack-nova08:02
*** edmondsw has quit IRC08:03
*** lajoskatona has joined #openstack-nova08:11
*** tesseract has joined #openstack-nova08:20
*** ralonsoh has joined #openstack-nova08:34
*** hiro-kobayashi has quit IRC08:35
*** amoralej|off is now known as amoralej08:36
*** sidx64 has quit IRC08:36
*** andreas_s has joined #openstack-nova08:37
*** damien_r has joined #openstack-nova08:40
*** Tom-Tom has quit IRC08:41
openstackgerritHironori Shiina proposed openstack/nova master: ironic: Support resize and cold migration  https://review.openstack.org/50067708:41
*** Tom-Tom has joined #openstack-nova08:41
*** Tom-Tom has quit IRC08:43
*** Tom-Tom has joined #openstack-nova08:43
*** Tom-Tom_ has joined #openstack-nova08:44
openstackgerritAndrey Volkov proposed openstack/osc-placement master: Get resource provider by uuid or name  https://review.openstack.org/52779108:45
*** damien_r has quit IRC08:45
*** damien_r has joined #openstack-nova08:46
*** Tom-Tom has quit IRC08:47
*** jpena|off is now known as jpena08:49
*** sidx64 has joined #openstack-nova08:52
*** shunliz has joined #openstack-nova08:54
*** hoangcx has quit IRC08:56
*** andreas_s has quit IRC08:56
openstackgerritsahid proposed openstack/nova-specs master: libvirt: add support for virtio-net rx/tx queue sizes  https://review.openstack.org/53960508:56
*** andreas_s_ has joined #openstack-nova08:58
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: Initial change set of z/VM driver  https://review.openstack.org/52338708:59
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: Spawn and destroy function of z/VM driver  https://review.openstack.org/52765808:59
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add snapshot function  https://review.openstack.org/53424008:59
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add power actions  https://review.openstack.org/54334008:59
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add get console output  https://review.openstack.org/54334408:59
*** andreas__ has joined #openstack-nova08:59
bauzasgood morning folks08:59
*** bauzas is now known as bauwser08:59
*** andrea___ has joined #openstack-nova09:01
*** bauwser is now known as bauzas09:01
*** bauzas is now known as bauwser09:02
*** andreas_s_ has quit IRC09:02
*** andrea___ has quit IRC09:03
*** andreas_s has joined #openstack-nova09:04
openstackgerritYikun Jiang (Kero) proposed openstack/nova-specs master: Complex (Anti)-Affinity Policies  https://review.openstack.org/54692509:04
*** andreas__ has quit IRC09:04
openstackgerritjichenjc proposed openstack/nova master: Trivial fix: add a log eariler  https://review.openstack.org/55516409:10
*** andreas_s has quit IRC09:11
*** mdbooth has joined #openstack-nova09:12
*** lucas-afk is now known as lucasagomes09:13
*** alexchadin has quit IRC09:14
*** alexchadin has joined #openstack-nova09:18
*** alexchadin has quit IRC09:18
*** alexchadin has joined #openstack-nova09:18
*** alexchadin has quit IRC09:19
*** andreas_s has joined #openstack-nova09:19
*** alexchadin has joined #openstack-nova09:19
*** andreas_s has quit IRC09:19
*** alexchadin has quit IRC09:20
*** jichen has quit IRC09:20
*** alexchadin has joined #openstack-nova09:20
*** alexchadin has quit IRC09:20
*** rcernin has quit IRC09:20
*** alexchadin has joined #openstack-nova09:21
*** jichen has joined #openstack-nova09:21
*** jianghuaw has quit IRC09:22
*** andreas_s has joined #openstack-nova09:22
gibihappy Friday nova09:23
*** mgoddard has joined #openstack-nova09:23
*** gibi is now known as giblet09:23
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Add the version description for InstanceActionEventList  https://review.openstack.org/55571109:25
*** alexchadin has quit IRC09:25
*** ratailor has quit IRC09:25
*** lajoskatona has quit IRC09:26
*** lpetrut has joined #openstack-nova09:27
*** ratailor has joined #openstack-nova09:27
*** lpetrut_ has joined #openstack-nova09:28
*** lpetrut has quit IRC09:28
*** sdague has joined #openstack-nova09:34
*** derekh has joined #openstack-nova09:37
*** Tom-Tom_ has quit IRC09:40
*** Tom-Tom has joined #openstack-nova09:41
*** yingjun has quit IRC09:41
*** Dinesh_Bhor has quit IRC09:43
*** sidx64 has quit IRC09:43
*** hshiina has quit IRC09:43
*** lajoskatona has joined #openstack-nova09:44
*** licanwei_ has quit IRC09:45
*** Tom-Tom has quit IRC09:45
*** edmondsw has joined #openstack-nova09:47
*** liuzz has quit IRC09:47
* stephenfin senses a disturbance in the 'hw:cpu_thread_policy' force09:48
*** tssurya has joined #openstack-nova09:49
SpazmoticHappy friday you ridiculously smart people :p09:50
*** edmondsw has quit IRC09:51
*** lgsafety has joined #openstack-nova09:52
*** ratailor has quit IRC09:52
*** alexchadin has joined #openstack-nova09:52
*** sidx64 has joined #openstack-nova09:53
*** ratailor has joined #openstack-nova09:53
*** kalyan has joined #openstack-nova09:54
*** andreas_s has quit IRC09:57
*** alexchadin has quit IRC09:57
*** andreas_s_ has joined #openstack-nova10:00
*** tuanla____ has quit IRC10:01
*** lgsafety has quit IRC10:01
*** cdent has joined #openstack-nova10:03
kashyapdansmith: Is adjusting even one blank space change (in the same area) a strict no-no?  I was cautious while making that: https://review.openstack.org/#/c/534384/10/nova/virt/libvirt/driver.py10:04
*** yamamoto has quit IRC10:05
bauwserstephenfin: that cannot be true, my padawan10:06
*** yamamoto has joined #openstack-nova10:06
bauwserfear is the path to the dark side10:07
*** rcernin has joined #openstack-nova10:08
* bauwser starts looking at implementing nested RPs, woot10:08
*** andreas_s_ has quit IRC10:09
*** andreas_s has joined #openstack-nova10:09
*** yamamoto has quit IRC10:11
*** avolkov has quit IRC10:11
*** avolkov has joined #openstack-nova10:11
*** andreas_s has quit IRC10:14
bauwserjianghuaw_: around ?10:14
bauwserjianghuaw_: I'm starting to modeling inventories with multiple types10:14
bauwserthanks to NRP10:14
bauwserand I wonder how you modeled the tree10:14
bauwserbecause I was thinking of one child RP being the PCI device10:15
bauwserbut then, depending on the GPU type, you could have different inventories10:15
bauwserso it would be yet another tree level, with each type being a child ?10:15
*** Tom-Tom has joined #openstack-nova10:16
*** chyka has joined #openstack-nova10:16
bauwserjianghuaw_: nothing in the spec mentions what if we have multiple types per pGPU https://specs.openstack.org/openstack/nova-specs/specs/queens/implemented/add-support-for-vgpu.html10:18
kashyapdansmith: melwitt: And yes, restricting the backport to one option with the _same_ config attribute sounds list a reasonable compromise10:18
kashyap(As to the rest of the questions, answering on the review.)10:18
*** andreas_s has joined #openstack-nova10:18
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: Initial change set of z/VM driver  https://review.openstack.org/52338710:18
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: Spawn and destroy function of z/VM driver  https://review.openstack.org/52765810:18
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add snapshot function  https://review.openstack.org/53424010:18
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add power actions  https://review.openstack.org/54334010:18
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add get console output  https://review.openstack.org/54334410:18
bauwserjianghuaw_: that said, nvidia says that it can only support one type per pGPU in http://docs.nvidia.com/grid/latest/grid-vgpu-user-guide/index.html#homogeneous-grid-vgpus10:19
bauwserso I wonder if that really matteres10:19
*** stephenfin is now known as finucannot10:19
*** alexchadin has joined #openstack-nova10:20
*** liverpooler has quit IRC10:21
*** chyka has quit IRC10:21
*** Tom-Tom has quit IRC10:21
*** andreas_s has quit IRC10:23
*** alexchadin has quit IRC10:25
openstackgerritHuang Rui proposed openstack/nova master: z/VM Driver: add snapshot function  https://review.openstack.org/53424010:27
openstackgerritHuang Rui proposed openstack/nova master: z/VM Driver: add power actions  https://review.openstack.org/54334010:27
openstackgerritHuang Rui proposed openstack/nova master: z/VM Driver: add get console output  https://review.openstack.org/54334410:27
*** shunliz has quit IRC10:28
*** alexchadin has joined #openstack-nova10:28
*** andreas_s has joined #openstack-nova10:28
openstackgerritAndrey Volkov proposed openstack/osc-placement master: RP delete inventories (v1.5)  https://review.openstack.org/51464210:31
openstackgerritAndrey Volkov proposed openstack/osc-placement master: CLI for traits (v1.6)  https://review.openstack.org/51464310:31
openstackgerritAndrey Volkov proposed openstack/osc-placement master: Resource class set (v1.7)  https://review.openstack.org/51464410:31
openstackgerritAndrey Volkov proposed openstack/osc-placement master: Usages per project and user (v1.8, v1.9)  https://review.openstack.org/51464610:31
openstackgerritAndrey Volkov proposed openstack/osc-placement master: CLI allocation candidates (v1.10)  https://review.openstack.org/51464710:31
openstackgerritAndrey Volkov proposed openstack/osc-placement master: New dict format of allocations (v1.11, v1.12)  https://review.openstack.org/54281910:31
openstackgerritAndrey Volkov proposed openstack/osc-placement master: Transactionally update allocations (v1.13)  https://review.openstack.org/54667410:31
openstackgerritAndrey Volkov proposed openstack/osc-placement master: Add nested resource providers (v1.14)  https://review.openstack.org/54667510:31
openstackgerritAndrey Volkov proposed openstack/osc-placement master: Limit allocation candidates (v1.15, v1.16)  https://review.openstack.org/54804310:31
openstackgerritAndrey Volkov proposed openstack/osc-placement master: Allocation candidates parameter: required (v1.17)  https://review.openstack.org/54832610:31
*** andreas_s has quit IRC10:32
*** sambetts|afk is now known as sambetts10:32
*** andreas_s has joined #openstack-nova10:34
*** andreas_s has quit IRC10:34
kashyapsean-k-mooney: Thanks for the comment here: https://review.openstack.org/#/c/534384/10/nova/virt/libvirt/driver.py10:35
openstackgerritMerged openstack/nova master: Not use thread alloc policy for emulator thread  https://review.openstack.org/53870010:37
*** andreas_s has joined #openstack-nova10:37
*** alexchadin has quit IRC10:37
*** andreas_s_ has joined #openstack-nova10:39
*** lajoskatona has quit IRC10:40
*** dtantsur|afk is now known as dtantsur10:41
*** mdbooth has quit IRC10:41
*** andreas_s has quit IRC10:42
*** andreas_s has joined #openstack-nova10:42
*** andreas_s_ has quit IRC10:43
*** alexchadin has joined #openstack-nova10:44
*** jichen has quit IRC10:47
*** cdent has quit IRC10:48
*** alexchadin has quit IRC10:49
kashyapdansmith: melwitt: While I understand the backport stance.  FWIW, talking to danpb (who is SME on this topic) on IRC, he still thinks it's an artificial limiting for the sake of backports.10:51
kashyapI feel that we're over-evaluating.  But whatever.10:52
*** lajoskatona has joined #openstack-nova10:55
*** alexchadin has joined #openstack-nova10:55
*** alexchadin has quit IRC10:56
* kashyap goes to rework the thing10:56
*** tbachman has quit IRC10:58
*** vladikr has quit IRC10:59
*** alexchadin has joined #openstack-nova11:01
*** abhishekk has quit IRC11:03
openstackgerritYikun Jiang (Kero) proposed openstack/nova-specs master: Complex (Anti)-Affinity Policies  https://review.openstack.org/54692511:04
*** elmaciej has joined #openstack-nova11:04
*** annp has quit IRC11:06
openstackgerritsahid proposed openstack/nova-specs master: virt: allow instances to be booted with trusted VFs  https://review.openstack.org/48552211:06
*** udesale has quit IRC11:06
*** yamamoto has joined #openstack-nova11:07
*** mdbooth has joined #openstack-nova11:08
*** alexchadin has quit IRC11:10
*** josecastroleon has quit IRC11:12
*** alexchadin has joined #openstack-nova11:12
*** yamamoto has quit IRC11:13
*** moshele has joined #openstack-nova11:21
*** moshele has quit IRC11:26
*** pcaruana has quit IRC11:27
*** elmaciej has quit IRC11:27
*** vks1 has quit IRC11:38
*** cdent has joined #openstack-nova11:43
sahidjaypipes: i think we are good with the trusted vfs spec: can you have a final look? https://review.openstack.org/#/c/485522/11:47
*** maciejjozefczyk has quit IRC11:50
*** maciejjozefczyk has joined #openstack-nova11:50
*** jaosorior has quit IRC11:56
*** yamamoto has joined #openstack-nova11:56
*** yamamoto has quit IRC11:56
*** sree_ has joined #openstack-nova11:59
*** sree_ is now known as Guest1945711:59
*** edmondsw has joined #openstack-nova12:03
*** liverpooler has joined #openstack-nova12:07
openstackgerritChris Dent proposed openstack/nova master: Use microversion parse 0.2.1  https://review.openstack.org/55026512:09
*** ccamacho is now known as ccamacho|lunch12:10
*** yamamoto has joined #openstack-nova12:10
*** tbachman has joined #openstack-nova12:12
*** odyssey4me has quit IRC12:12
*** odyssey4me has joined #openstack-nova12:12
*** cdent has quit IRC12:13
*** sahid has quit IRC12:13
*** tbachman_ has joined #openstack-nova12:14
*** vladikr has joined #openstack-nova12:16
*** tbachman has quit IRC12:17
*** tbachman_ is now known as tbachman12:17
*** josecastroleon has joined #openstack-nova12:19
*** yamamoto has quit IRC12:25
*** efried is now known as fried_rice12:27
* fried_rice waves12:28
*** tovin07 has quit IRC12:29
fried_riceGate fixed?  Time to recheck-all?12:29
*** alexchadin has quit IRC12:29
*** pcaruana has joined #openstack-nova12:30
*** rcernin has quit IRC12:30
*** voelzmo has joined #openstack-nova12:31
*** alexchadin has joined #openstack-nova12:33
*** cdent has joined #openstack-nova12:37
*** lajoskatona has quit IRC12:38
*** tiendc has quit IRC12:40
openstackgerritStephen Finucane proposed openstack/nova master: Stop using mox in virt/xenapi/image/test_vdi_through_dev.py  https://review.openstack.org/34268212:41
fried_riceeric-young: I don't see the os-brick release proposed yet.  Need help?12:41
*** pchavva has joined #openstack-nova12:42
*** lucasagomes is now known as lucas-hungry12:43
*** edleafe is now known as figleaf12:46
eric-youngfried_rice, there was some talk yesterday in the cinder channel about needing one more patch merged first. was going to check on status here in a bit12:47
*** voelzmo has quit IRC12:47
fried_riceeric-young: Roger that, just checking in :)12:47
*** jaypipes is now known as leakypipes12:47
fried_rice(I'm in no hurry, just saw the nova patch go by again this morning)12:48
eric-youngfried_rice, I am in no super hurry either but it'd be good to get that patch off my plate :)12:49
eric-youngalso need to get zuul to approve it. seeing an error with tempest-full-py3 on POST_FAILURE12:50
*** lajoskatona has joined #openstack-nova12:55
*** tssurya is now known as sususuryashines12:56
*** suresh12 has joined #openstack-nova12:58
leakypipessususuryashines: welcome to Friday :)13:01
* leakypipes considering changing his nick to POST_FAILURE13:01
kashyapleakypipes: You've got one hell of a plumbing expenses there :P13:02
kashyaps/expenses/bill/13:02
*** suresh12 has quit IRC13:02
sususuryashinesleakypipes : hehe, thanks!13:03
leakypipeskashyap: indeed.13:03
*** mriedem has joined #openstack-nova13:03
*** hemna_ has quit IRC13:03
fried_riceeric-young: That one should be recheckable now.13:07
*** yamamoto has joined #openstack-nova13:08
*** yamamoto has quit IRC13:08
*** yamamoto has joined #openstack-nova13:08
*** yamamoto has quit IRC13:08
*** rubasov has joined #openstack-nova13:12
eric-youngthanks, will do13:12
*** yamamoto has joined #openstack-nova13:15
*** alexchadin has quit IRC13:15
*** lyan has joined #openstack-nova13:16
*** lyan is now known as Guest4399013:16
*** alexchadin has joined #openstack-nova13:17
sq4indhey guys, any way to recover VM which has been lost during live migration ? I cannot find it on any hypervisor13:19
sq4indtried this already: https://docs.openstack.org/nova/latest/admin/node-down.html13:19
sq4indno luck ;/13:19
*** yamamoto has quit IRC13:19
*** dtantsur is now known as dtantsur|brb13:20
openstackgerritMerged openstack/nova-specs master: virt: allow instances to be booted with trusted VFs  https://review.openstack.org/48552213:23
*** eharney has joined #openstack-nova13:24
*** Guest19457 has quit IRC13:25
*** dklyle has quit IRC13:27
openstackgerritPatricia Domingues proposed openstack/nova master: load up the volume drivers by checking architecture  https://review.openstack.org/54139313:27
*** _ix has joined #openstack-nova13:28
*** idlemind has joined #openstack-nova13:30
*** yamamoto has joined #openstack-nova13:30
*** sahid has joined #openstack-nova13:32
*** lucas-hungry is now known as lucasagomes13:32
dansmithjohnthetubaguy: https://review.openstack.org/#/c/53960513:34
*** _ix has quit IRC13:34
*** yamamoto has quit IRC13:35
gibletfried_rice, leakypipes: when placement was designed was it intentionaly decided that placement does not provide information about which part of an allocation candidate fulfills which part of the request?13:38
fried_ricegiblet: That seems like it would be a tough thing to design, implement, reason about.13:39
gibletfried_rice, leakypipes: I'm hit the issue that Neutron needs to know which part of an allocation record fulfills the original resource request of a given port13:39
bauwserfried_rice: leakypipes: I have a question for you about https://review.openstack.org/#/c/552924/13:39
leakypipesgiblet: not sure I follow you... an allocation request does indeed indicate which resources are served by which providers...13:39
*** dansmith is now known as superdan13:39
fried_ricegiblet: Ah, yes, that's legitimate, and an issue that virt drivers will also have.  It's going to come down to neutron needing to be able to map RP IDs/names to something that lets it know which real resource it corresponds to.13:40
bauwserfried_rice: leakypipes: if we split the compute resources in between NUMA nodes (like for vCPUs), if a guest is asking for 2 vCPUs, would it be possible to have one vCPU in one NUMA node and the other vCPU in a separate node ?13:40
bauwserlike we do at the moment?13:41
fried_ricebauwser: only if you specify them in separate request groups.13:41
*** esberglu has joined #openstack-nova13:41
*** yamahata has joined #openstack-nova13:41
bauwserfried_rice: that's my concern13:41
gibletleakypipes: true, the allocation request is created against an RP, but the connection between an allocation request and the original resource request of a port is missing13:41
fried_ricebauwser: ...or if the driver models them in a single RP.  I.e. the host is set up not to do NUMA at all.13:41
bauwserfried_rice: leakypipes: for the moment, say I have two NUMA nodes with 4 pCPUs each one13:42
leakypipesgiblet: I'm not following you...13:42
fried_ricegiblet: I think what we're getting at is: if you're having trouble making that connection, it's because you didn't split up your RPs enough.13:42
bauwserfried_rice: leakypipes: if 3 pCPUs are already taken, I can still have a instance using two pCPUs from two different NUMA nodes13:43
bauwserfried_rice: leakypipes: if we say we need to have a request query for that, then it would be a problem13:43
gibletfried_rice: OK that is a direction I have to investigate in the neutron port case13:43
gibletleakypipes: there is a neturon port, that will have a resource_request, that will end up as a granular resource request group in the GET allocation_candidates query13:44
gibletleakypipes: but parts of the returned allocation candidates does not mapps back to the original granular resource request group13:44
gibletleakypipes: I means placement does not specify which subset of an allocation candidate maps to a certain granular resource group13:45
fried_ricegiblet: That's correct, but it also shouldn't need to.13:45
openstackgerritBence Romsics proposed openstack/osc-placement master: RP list: member_of and resources parameters (v1.3, v1.4)  https://review.openstack.org/51118313:45
openstackgerritBence Romsics proposed openstack/osc-placement master: RP delete inventories (v1.5)  https://review.openstack.org/51464213:45
openstackgerritBence Romsics proposed openstack/osc-placement master: CLI for traits (v1.6)  https://review.openstack.org/51464313:45
openstackgerritBence Romsics proposed openstack/osc-placement master: Resource class set (v1.7)  https://review.openstack.org/51464413:45
openstackgerritBence Romsics proposed openstack/osc-placement master: Usages per project and user (v1.8, v1.9)  https://review.openstack.org/51464613:45
openstackgerritBence Romsics proposed openstack/osc-placement master: CLI allocation candidates (v1.10)  https://review.openstack.org/51464713:45
openstackgerritBence Romsics proposed openstack/osc-placement master: New dict format of allocations (v1.11, v1.12)  https://review.openstack.org/54281913:45
openstackgerritBence Romsics proposed openstack/osc-placement master: Transactionally update allocations (v1.13)  https://review.openstack.org/54667413:45
openstackgerritBence Romsics proposed openstack/osc-placement master: Add nested resource providers (v1.14)  https://review.openstack.org/54667513:45
openstackgerritBence Romsics proposed openstack/osc-placement master: Limit allocation candidates (v1.15, v1.16)  https://review.openstack.org/54804313:45
openstackgerritBence Romsics proposed openstack/osc-placement master: Allocation candidates parameter: required (v1.17)  https://review.openstack.org/54832613:45
*** yamamoto has joined #openstack-nova13:45
*** josecastroleon has quit IRC13:46
fried_ricegiblet: Because if you have two request groups that otherwise look the same, then it shouldn't matter which of those two pieces of the response you "use" for which.13:46
kashyapsuperdan: BTW, thanks for the validation question, that prompted me to file the bug that I needed to, for the new libvirt API: https://review.openstack.org/#/c/534384/10/nova/conf/libvirt.py13:46
gibletleakypipes, fried_rice: port1 and port2 both needs BW resource, an allocation candidate will have RP - BW pairs for both port1 and port2 but there is no way to tell which pair maps to which port13:46
kashyapsuperdan: And the libvirt dev already assigned it to himself and working on it :-)13:46
superdankashyap: cool13:47
fried_riceBut if the request groups were differentiated by, say, a custom trait indicating a physical network, then those traits will be in the provider summary, and you can use that to distinguish.13:47
kashyapsuperdan: Appreciate the eagle eyes.13:47
gibletfried_rice: true, the response is not ambigous. It is just haaard to make a generic code that does the mapping13:47
leakypipesgiblet: the provider_summaries section of the allocation candidates response contains all the trait and usage information that callers would need to decide that mapping, though.13:47
fried_ricegiblet: Well, you'd have to do the math, yeah.13:47
fried_ricewhich I agree is awkward13:48
gibletleakypipes, fried_rice: thanks, I understand now13:48
gibleta bit better...13:48
fried_ricebauwser: As we've currently got things conceived, if you want to do a don't-care-about-NUMA-affinity resource request on a system that's set up for NUMA, you should split your CPU resources into separate request groups.13:49
fried_ricebauwser: It's awkward, but without further invention, it's the only way to guarantee that you'd be able to get a result spread across multiple nodes if you need.13:49
bauwserfried_rice: not sure I understand the latter13:49
bauwserWDYM by splitting your resources into separate groups ?13:50
kashyapsuperdan: Do you absolutely want me to remove the white space change?  https://review.openstack.org/#/c/534384/10/nova/virt/libvirt/driver.py13:50
fried_ricebauwser: Instead of resources=VCPU:2, which would always give you both VCPUs from the same provider, you would have to say resources1=VCPU:1&resources2=VCPU:113:50
superdankashyap: I absolutely do13:50
*** yamamoto has quit IRC13:50
kashyapsuperdan: :-) Did it to keep the conditionals in line.  But where is the next chance to "fix it"?13:50
bauwserfried_rice: that looks a terrible upgrade impact for operators IMHO13:50
kashyapA separate change just to do that is overkill13:51
*** awaugama has joined #openstack-nova13:51
superdankashyap: it's not worth fixing, IMHO13:51
kashyapOkay, I'll curb my OCD there13:51
bauwseras an operator, I just want to provide flavors, either for specific NUMA calls, or just for asking resources13:51
fried_ricebauwser: Again, without further invention, that's the way it's got to be.  Think about the implications if we supported splitting a single VCPU:2 across multiple RPs.13:51
leakypipesbauwser, giblet, fried_rice: I'm almost done reworking the cpu-resources spec with all the feedback from yesterday's 6-hour sage IRC conversation. Gimme about an hour and the new spec should answer a number of your questions.13:51
*** yamamoto has joined #openstack-nova13:51
bauwserfried_rice: we haven't modeled NUMA yet, hence my questions13:52
*** sidx64 has quit IRC13:52
sean-k-mooney[m]Fried_rice thats concering as if i have a gust that can't fit on a single numa node i cant boot that anymore if i dont request a multi numa topology13:52
bauwserfried_rice: if we go sharding the resources between NUMA nodes, then that's a terrible operator impact IMHO13:52
fried_ricebauwser: The example I gave was DISK_GB.  If I say resources=DISK_GB:1024, but my compute host has multiple storage RPs (including shared), I definitely don't want GET /a_c to return me candidates where those DISK_GB are split across multiple.13:52
bauwserthat needs at least to be properly documented13:52
bauwserfried_rice: again, I understand nested RPs13:53
bauwserfried_rice: so, yeah I agree13:53
fried_ricebauwser: That goes for nested and sharing alike.13:53
bauwserfried_rice: if you shard your resources between separate nested children, then it's understandable13:53
bauwserfried_rice: but here I'm talking of NUMA13:53
sahidleakypipes: mriedem, thanks for your efforts on reviewing the trusted vfs specs13:53
fried_ricebauwser: I don't disagree that this is awkward.  But we would have to come up with some new semantic to allow spreading.  resources=VCPU:2&allow_spread=resources13:53
fried_rice(ew)13:53
bauwserthat looks to me the default behaviour to have IMHO13:54
fried_ricebauwser: You're talking about a user wanting to get a non-NUMA-affined instance on a NUMA-modeled compute host.13:54
bauwserby default, spread between NUMA nodes13:54
fried_ricebauwser: Unless we start special-casing by resource class, no can do.  Because of the DISK_GB example.13:54
bauwserfried_rice: I'm talking of a user using a flavor that doesn't ask for NUMA resources, just vCPUs, yeah13:54
fried_rice...which would be an issue *today* (whereas NUMA is a tomorrow thing)13:55
sean-k-mooney[m]bauwser: fried_rice  this will be a behaviour change form today. Today we only numa affites if you ask for it13:55
bauwserwhat sean-k-mooney[m] wrote13:55
bauwserthat would be a terrible upgrade impact13:55
mriedemsahid: np, i left some comments in the 2nd patch in the code series13:55
bauwserhence why I originally modeled my spec with vCPU resources being on the root RP13:55
bauwserand only NUMA specific resources being on the children13:56
bauwserto keep existing behaviour compatible13:56
*** yamamoto has quit IRC13:56
fried_ricebauwser: Okay, but then we would need some way to decrement the NUMA resources when the top-level resources are requested/consumed.13:56
sahidmriedem: ok i will address them, i also have noticed your comment on the first patch13:56
bauwserfried_rice: that's a separate NUMA resource class, see my spec13:56
bauwserthe terms are maybe not good13:57
leakypipessahid: np. thanks for your patience.13:57
leakypipessahid: I should have the cpu-resources next revision up shortly for your review.13:57
bauwserbut if I'm asking for resources:VCPU=2,NUMA_VCPU=2 then it'll decrement both13:57
sahidleakypipes: ok, sure i will13:58
sahidreview it13:58
sean-k-mooney[m]Well i think we need to have vcpus under numa but i think we will need something likek a grouping level attribute that defaults to host. E. G. Host, numa, rp grouping13:58
*** links has quit IRC13:58
fried_ricebauwser: yup.  But how is that better than asking for resources1:VCPU:1&resources2=VCPU:113:58
bauwserfried_rice: because existing flavors will still work for non-NUMA queries13:59
bauwserthat's all the difference13:59
sean-k-mooney[m]Fried_rice how do you know how to create the groups13:59
bauwserhere, you're asking to change all the operator's flavor to explicitly tell whether they care about NUMA sharding or not13:59
fried_ricebauwser: Existing flavors have resources:VCPU=2,NUMA_VCPU=2 ?13:59
bauwserexisting flavors just have VCPU resources13:59
fried_riceright13:59
figleaffried_rice: how could you possibly know which NUMA nodes to decrement resources from?14:00
bauwserlike I wrote, we can have Nova to ask for both resource classes if it sees that14:00
fried_riceSo look, there are ways to handle this with and without changing the placement API14:00
fried_riceyeah, that'd be one way.14:00
sean-k-mooney[m]Existing flavours without numa_nodes set dont have numa affinity for cpus14:00
fried_riceThe other way is to have nova see that the flavor doesn't care about NUMA affinity and *nova* splits up the resource requests14:00
bauwserI mean, if a flavor tells only about vCPUs, then query Placement only for that, but make allocations for both VCPU and NUMA_SOMETHING_VCPU14:00
bauwserfried_rice: that's what I wrote in the spec14:01
bauwsernova could make the translation14:01
bauwserleakypipes: ^ I hope you follow14:01
fried_ricebauwser: Cool; either way, we're having nova massage the request.  But I prefer the path where we're actually representing true inventory numbers.14:01
sean-k-mooney[m]Fried_rice how does nova know how to split it up14:01
fried_ricesean-k-mooney[m]: For VCPU, it's one per request group, plain and simple.14:02
bauwsersean-k-mooney[m]: there are two different things, the placement query and the allocation14:02
bauwserfried_rice: also, note I'd like to not depend on request groups for NUMA14:02
*** andreas_s has quit IRC14:02
fried_ricebauwser: Whyzat?14:02
*** diga has joined #openstack-nova14:02
fried_riceI don't think you can get around it, especially when you start talking about e.g. NICs.14:03
sean-k-mooney[m]Flavor has 16 vcpus and dose not care about numa. All hosts have 2 10 cpus. How does nova know it needs to split into two groups14:03
bauwseragain, that requires operators opiniating about which specific placement they should do per flavor for non-NUMA specific instances14:03
fried_ricesean-k-mooney[m]: it doesn't split into two groups.  It splits into 1614:03
bauwsersean-k-mooney[m]: my vision was that we would ask placement only for VCPUs that are on the root RP14:03
fried_riceSorry guys, got to run for a bit.14:03
bauwsersean-k-mooney[m]: but once we get a RP, we would make the allocation against a child14:04
bauwserwell, erm14:04
bauwsernevermind14:04
bauwserit's stupid14:04
sean-k-mooney[m]So 16 request of 1 cpu14:04
bauwserwhat we need is to get all the children that match the query14:04
bauwserand only consume one of those14:04
bauwserfuuu, I'm getting headaches14:04
sean-k-mooney[m]leakypipes: is this something we should cover in your spec14:05
figleafbauwser: "only in root" - that was one of the decisions we made back in Atlanta. A machine would be configured by the operator ahead of time. If a VCPU was assigned to a NUMA node, it could not be considered also to be part of the root compute node14:06
bauwsersean-k-mooney[m]: NUMA related things should be covered in https://review.openstack.org/#/c/552924/3/specs/rocky/approved/numa-topology-with-rps.rst14:06
bauwserfigleaf: I don't disagree with that statement14:07
sean-k-mooney[m]figleaf: almost all server systems are numa system even systems with one socket14:07
bauwserfigleaf: I'm just trying to evaluate the operator impact of a NoValidHost if we begin counting NUMA nodes for non-NUMA specific instances14:08
figleafsean-k-mooney[m]: sure, but the choice on how to consume them (respecting NUMA, or ignoring) is an up-front decision by the operator.14:08
*** ratailor has quit IRC14:08
sean-k-mooney[m]bauwser: i think it also needs to be in jays cpu resources spec14:08
bauwserfigleaf: so you agree with the fact that a classic flavor just asking for VCPUs shouldn't be accounting NUMA nodes, right?14:09
*** dave-mccowan has joined #openstack-nova14:09
sean-k-mooney[m]figleaf: no its a choice of the virt driver14:09
bauwserhow the inventory is modeled is one thing14:09
bauwserand I'm fine with having VCPU resources on a NUMA node if that helps14:09
figleafbauwser: of course, but it would only select a host that was configured *not* to use NUMA. IOW, the ram, vcpu, etc, was inventory of the compute14:09
bauwserbut my point is, I don't want to get a NoValidHost if that restricts my existing flavor to specific NUMA nodes14:10
openstackgerritMerged openstack/nova master: Change compute mgr placement check to region_name  https://review.openstack.org/55475914:10
bauwserfigleaf: that's super costly then14:10
openstackgerritMerged openstack/nova master: Remove translate and a TODO  https://review.openstack.org/55482714:11
figleafbauwser: if you configure all your machines not to use NUMA, and request a NUMA-specific flavor, you will get NoValidHost. The reverse would also be true14:11
bauwserfigleaf: because I want to have both compute workloads that can do NUMA affinity and regular workloads that don't care14:11
bauwserfigleaf: again, that's a huuuuuge behavioural change14:11
figleafbauwser: sure, then configure some of your machines for NUMA, and others for not-NUMA14:11
figleafThe balance is up to the operator14:11
bauwserit's suboptimal14:11
sean-k-mooney[m]figleaf: we don't have a compute node option for ignore numa14:12
cdentmaking the optimal solution is introducing an enormous amount of complexity that is making hard to finish _any_ solution14:12
bauwsersean-k-mooney[m]: I guess figleaf wants it14:12
*** jpena is now known as jpena|lunch14:12
sean-k-mooney[m]Figleaf but that is not something you can configure normally14:12
bauwserif you opt for non-NUMA, then you get a flat inventoty14:12
bauwserif you opt for NUMA topology, then you're stuck with NUMA-only workloads on that single node14:13
*** yamahata has quit IRC14:13
bauwser:/14:13
figleafsean-k-mooney[m]: it would be how resources are reported. If the virt driver reports that a NUMA node owns some inventory, then that NUMA node has to satisfy the request. There is no concept in placement for the kind of sharing you're talking about14:14
bauwsercdent: that's the whole purpose of the spec14:14
*** amoralej is now known as amoralej|lunch14:14
cdentbauwser: which "that's"?14:14
openstackgerritJay Pipes proposed openstack/nova-specs master: Standardize CPU resource tracking  https://review.openstack.org/55508114:14
bauwsercdent: to see if we can model the NUMA inventories in any other ways that would help to solve the problem without requiring too much engineering14:14
leakypipescfriesen, bauwser, sahid, sean-k-mooney[m], finucannot, fried_rice: ^^ ok, new revision pushed. lemme know if that looks a bit better.14:15
sean-k-mooney[m]figleaf: again how would yo do that. Numa is a feature of the hardware its not a software option so your talking about ordering hardware with out multiple memory controllers or configure mirrors dimms in the bios14:15
bauwserleakypipes: you missed a NUMA conversation14:15
cdentbauwser: okay. My statement was more along the lines of "trying to satisfy all this NUMA and other enhanced platform stuff, in general, is breaking the 80/20 rule"14:15
*** tidwellr has joined #openstack-nova14:15
leakypipesbauwser: not really. see the spec. :)14:15
bauwsercdent: the problem is that like sean-k-mooney[m] said, modern architectures are NUMA-based, but 80% of our workloads don't care14:16
sean-k-mooney[m]figleaf: not in placement but that is how nova works today.14:16
sean-k-mooney[m]leakypipes: cool will do14:16
bauwserleakypipes: hah, teaser!14:16
openstackgerritMerged openstack/nova master: Add the version description for InstanceActionEventList  https://review.openstack.org/55571114:16
bauwserI like that14:16
sean-k-mooney[m]Lleakypipes yes this is related to that spec too14:16
*** yamahata has joined #openstack-nova14:17
*** gouthamr has joined #openstack-nova14:17
figleafsean-k-mooney[m]: it is software that reports what hardware exists to placement. If it configure to respect the NUMA layout, it reports the inventory that NUMA nodes "own". If it is configured to sum up the resources, then it reports inventory of the compute node.14:17
* leakypipes moves on to sahid's tx/rx spec14:17
bauwserI quote "placement is the most ambitious crossover of the history"14:17
sean-k-mooney[m]cdent: well in this case we are breaking insance that dont care about numa by fitting them to numa nodes14:18
*** gus has quit IRC14:18
bauwserleakypipes: https://twitter.com/sylvainbauza/status/97718789816761139214:19
gibletbauwser: lol14:20
*** burt has joined #openstack-nova14:21
openstackgerritMerged openstack/nova master: remove _cleanup_running_deleted_instances repeat detach volume  https://review.openstack.org/55409014:21
openstackgerritMerged openstack/nova master: deprecate fping_path config option  https://review.openstack.org/52660214:21
mriedemthere is no reason we need to warn for this right? http://git.openstack.org/cgit/openstack/nova/tree/nova/compute/manager.py#n334014:22
mriedemthe user is trying to do something the api allows them to do, so the operator shouldn't be warned about it14:22
* bauwser goes reading the last iteration of leakypipes's spec14:22
mriedemhttps://git.openstack.org/cgit/openstack/nova/tree/nova/compute/api.py#n271714:22
bauwserI think it's time for me writing a new rev' for NUMA and stating the concerns in the spexc14:22
cdentmy laptop battery and my brain battery are dying14:25
bauwsercdent: take a power bank14:26
cdentbauwser: you got one for brains? hook me up14:26
bauwsercdent: that said, I can't perclue where to plug the bank14:26
bauwsers/perclue/guess14:27
*** archit has joined #openstack-nova14:27
bauwsernote for self, stop buying expensive nespresso machines that are just subject to failures14:28
bauwserand start finding other ways for making coffee14:28
*** elmaciej has joined #openstack-nova14:28
*** zhaochao has quit IRC14:29
*** dave-mcc_ has joined #openstack-nova14:29
*** cdent has quit IRC14:29
openstackgerritTyler Blakeslee proposed openstack/nova master: Add __repr__ for NovaException  https://review.openstack.org/55581214:29
*** gus has joined #openstack-nova14:30
openstackgerritSurya Seetharaman proposed openstack/nova master: Allow scheduling only to enabled cells (Filter Scheduler)  https://review.openstack.org/55052714:31
openstackgerritSurya Seetharaman proposed openstack/nova master: Modify nova-manage cell_v2 list_cells to display "disabled" column  https://review.openstack.org/55541514:31
openstackgerritSurya Seetharaman proposed openstack/nova master: Add --enable and --disable options to  nova-manage update_cell  https://review.openstack.org/55541614:31
openstackgerritSurya Seetharaman proposed openstack/nova master: Add disabled option to create_cell command  https://review.openstack.org/55541714:31
*** dave-mccowan has quit IRC14:32
*** mlavalle has joined #openstack-nova14:32
sahidleakypipes: ++ on you spec cpu-resources14:35
*** sahid has quit IRC14:36
*** sahid has joined #openstack-nova14:37
*** sree has joined #openstack-nova14:37
*** dtantsur|brb is now known as dtantsur14:37
bauwserleakypipes: time for a question ?14:38
bauwserleakypipes: about https://review.openstack.org/#/c/555081/3/specs/rocky/approved/cpu-resources.rst@249 and beyond14:39
leakypipesbauwser: sure14:39
leakypipessahid: +2 on tx/rx14:39
leakypipessahid: I will let mriedem +W it though14:39
bauwserleakypipes: just noting a few things on the spec14:39
bauwserleakypipes: sahid: the TX/RX was next in my review queue14:40
superdanleakypipes: mriedem said he was leaving it to us in the meeting, so I think you can +W14:40
bauwserI have a fucking low number of reviews this week14:40
leakypipessuperdan: got it. done.14:40
leakypipesbauwser: reading specs takes a long time...14:41
sahidsuperdan thanks for having so active on it14:41
superdansahid: s/having/being/14:41
* superdan is still in review mode :)14:41
leakypipes:)14:41
sahid:)14:41
*** psachin has quit IRC14:42
*** tidwellr has quit IRC14:43
mriedemkashyap: i updated https://wiki.openstack.org/wiki/LibvirtDistroSupportMatrix for queens and added the ubuntu 18.04 LTS package versions based on https://packages.ubuntu.com/bionic/allpackages14:44
figleafleakypipes: quick question about the spec. When there are NUMA nodes with V/PCPU inventory, and a non-granular request is received, will there be allocation candidates returned for every possible combination of NUMA providers?14:44
mriedemlooks like all of the other distros in that table are old14:44
*** r-daneel has joined #openstack-nova14:44
kashyapmriedem: Ah-ha.  I have it open in one tab14:45
kashyapAnd was reviewing your historical changes there yesterday14:45
mriedemkashyap: so since we didn't bump in queens,14:45
kashyapWill get to it, once I respond to this bug-from-hell downstream14:45
mriedemwe already have a 'next min version' in the driver, which is actually kind of old now, libvirt 1.3.114:45
leakypipesfigleaf: yes, alloc candidates would contain alloc requests against each NUMA node that had space to fit the sum amount of requested VCPU/PCPU14:45
mriedemthe question is then what will the next min version be in Solar14:45
kashyapWhat is Solar?14:45
leakypipesfigleaf: I can add a note to clarify that.14:45
kashyapA new Ubuntu version?14:45
mriedemsolar is next openstack14:46
mriedem(pending that name is approved by legal)14:46
kashyapAah, I didn't check the release naming for the next one14:46
leakypipesI guess my suggestion of "Suck It, Trebek" didn't fly.14:46
figleafleakypipes: that's what I thought. When an a-c is chosen and allocated against, is there anything that constrains the building of the VM to the particular NUMA node that was allocated against?14:46
bauwserfigleaf: leakypipes: reviewed14:47
leakypipesfigleaf: nothing besides the provider UUID, no.14:47
openstackgerritMerged openstack/nova-specs master: libvirt: add support for virtio-net rx/tx queue sizes  https://review.openstack.org/53960514:47
bauwserfigleaf: leakypipes: my main concern is that existing flavors that don't ask for NUMA specifics shouldn't be constrained on NUMA nodes14:48
figleafleakypipes: and there is no relation between the RP UUID in placement and a particular NUMA node in hardware, right?14:48
leakypipesbauwser: they aren't "constrained". they just end up on a NUMA node is the host system is NUMA..14:48
leakypipess/is/if/14:48
bauwserleakypipes: back up a second14:48
bauwserleakypipes: I'm taking the example I had previously14:49
bauwsersay I ask for two VCPUs, period.14:49
bauwserwhat if my compute only has only vCPU left on one NUMA node, but one other vCPU left on another NUMA node ?14:49
bauwserat the moment, nova will satisfy that14:49
leakypipesbauwser: if the host system is NUMA, then the VCPU inventories will be against child provider representing NUMA nodes. And the allocation candidates will contain allocation requests that consume against one of those NUMA node resource providers.14:50
bauwserbecause the strategy is "spread" between all NUMA nodes, except if you clearly ask for another strategy14:50
leakypipesbauwser: in that case, that compute node would not be returned.14:50
leakypipesbauwser: since no single provider has capacity for 2 VCPU14:50
bauwserleakypipes: that's the whole point I discussed previously14:50
bauwserleakypipes: that's a behavioural change14:51
bauwserfrom a placement perspective, what was successful before is no longer possible14:51
-openstackstatus- NOTICE: zuul.o.o has been restarted to pick up latest code base and clear memory usage. Both check / gate queues were saved, be sure to check your patches and recheck when needed.14:52
leakypipesbauwser: then don't have the host configured to create NUMA node resource providers.14:52
leakypipesbauwser: and just use a single provider for the comute node.14:52
*** yamamoto has joined #openstack-nova14:52
bauwserleakypipes: so only specific NUMA workloads would run on a NUMA-specified compute, and non-NUMA workloads would end up on the rest ?14:53
bauwserif that's a config option, the default value would be "flat topology"14:53
leakypipesbauwser: not following you... how is that different from today?14:53
bauwserleakypipes: today you can end up having non-NUMA workloads that are running on a NUMA compute14:54
*** danpawlik has quit IRC14:54
bauwseractually14:54
bauwsersec14:54
bauwserdoing huge pages and CPU pinning would be insane14:54
bauwserif some workloads would just pick any CPU14:54
leakypipesbauwser: yes, and there's nothing in the new system that would change that. the operator simply wouldn't set up the compute host to create NUMA child providers on that host (if this is really an issue that anyone is concerned about)(14:55
bauwserleakypipes: okay, I see your point, how the operator would drive whether they want a non-NUMA inventory or not ?14:55
bauwserthru a config option ?14:55
leakypipesbauwser: that's up to your spec, no? :)14:56
bauwserfair enough :)14:56
bauwserokay, I think that's a reasonable trade-off14:56
*** sar has quit IRC14:56
*** david-lyle has joined #openstack-nova14:57
* leakypipes grabs more coffee, fuels up for the day of spec reviews14:57
*** yamamoto has quit IRC14:57
figleafbauwser: that's what I meant here [t 3hcx]14:58
purplerbot<figleaf> bauwser: "only in root" - that was one of the decisions we made back in Atlanta. A machine would be configured by the operator ahead of time. If a VCPU was assigned to a NUMA node, it could not be considered also to be part of the root compute node [2018-03-23 14:06:19.844755] [n 3hcx]14:58
*** jpena|lunch is now known as jpena14:58
bauwserfigleaf: yeah, what changed now is that I think that most operators already shard their cloud in between hosts that supports NUMA workloads and others (thru aggregates I guess)15:00
bauwserbecause doing CPU pinning requires that your host is pretty dedicated for15:00
bauwserI'm not saying you were wrong :)15:00
figleafbauwser: of course not! :)15:01
*** alexchadin has quit IRC15:01
*** mdnadeem has quit IRC15:02
mlavallerybridges: hi, when you have a chance, plese look here: https://github.com/openstack/neutron/blob/stable/ocata/neutron/services/segments/plugin.py#L232. As you can see, after adding the hosts to the aggregate, it adds the IPv$ inventory to the RP. Was the inventory created?15:02
*** r-daneel has quit IRC15:04
*** pooja_jadhav has quit IRC15:05
*** ktibi has joined #openstack-nova15:06
sean-k-mooney[m]leakypipes:  so just finished the v3 of the spec. i like this much more but some nits inline15:09
*** amoralej|lunch is now known as amoralej15:09
leakypipessean-k-mooney[m]: cool, ty sir15:09
leakypipessean-k-mooney[m], cfriesen: wanted to make sure I got all the definitions crystal clear...15:09
leakypipessean-k-mooney[m], cfriesen: did I properly describe vCPU threads, emulator threads and I/O threads?15:09
*** tbachman has quit IRC15:11
ktibiHi, I try to add a compute on existing platform and compute return errors : Another thread already created a resource provider with the UUID XXXXX. I think it's because I remove this compute previously and added it with same hostname.15:11
rybridgesmlavalle: The inventory is not being created. All the resource provider tied to the segment does get created, but the inventories, usages, and aggregates associated with the resource provider are all empty15:11
sean-k-mooney[m]leakypipes:  just read them again and yes i think so. we dont support configuring io threads in nova but the definition is correct15:12
ktibiwhere do you think I need to purge or clean compute ?15:12
ktibifull log: http://paste.openstack.org/show/710134/15:13
rybridgesmlavalle: In fact, I dont even think the code gets to the line and executes it at all because the aggregate never even gets associated. I added a very simple log statement before and after this line: https://github.com/openstack/neutron/blob/stable/ocata/neutron/services/segments/plugin.py#L225  and I see the one before being printed every time, but the one after never gets printed impying that after15:13
rybridgeswe call associate_aggregates() the control never returns15:13
rybridgesI also put a log statement on this line and I never see it get printed: https://github.com/openstack/neutron/blob/stable/ocata/neutron/services/segments/placement_client.py#L16315:14
rybridgesvery strange15:14
sean-k-mooney[m]bauwser:  do you have a minute to discuss the nic feature based scheduling spec15:14
*** hongbin has joined #openstack-nova15:14
bauwsersean-k-mooney[m]: sorry I saw your pings earlier15:15
bauwsersean-k-mooney[m]: I'm currently in a team meeting but shoot15:15
leakypipesktibi: can you re-start the nova-compoute with the DEBUG level logging and pastebin the log please?15:15
ktibileakypipes, y of course15:15
leakypipesktibi: it does indeed look like you may need to issue a couple manual cleanup calls to the placement API. but tough to tell without the debug logs15:16
sean-k-mooney[m]bauwser: https://review.openstack.org/#/c/545951/, i dont know how to proceed with this.  i am only ment to be spending 10% of my time upstream this cycle.15:16
sean-k-mooney[m]bauwser: if i was to start this spec from scratch i would do it differently today but i wont have time to rewrite it this cycle15:16
bauwsersean-k-mooney[m]: opening the spec15:17
bauwserI need to reload context in my mind15:17
bauwseraaaaaah I remember15:18
ktibileakypipes, http://paste.openstack.org/show/710154/15:18
bauwsersean-k-mooney[m]: well, I don't remember the specific outcome we had during the PTG15:18
leakypipesktibi: cool. thanks. btw, is this queens?15:19
bauwsersean-k-mooney[m]: could you please refresh my mind ?15:19
bauwsersean-k-mooney[m]: IIRC, we discussed on the opportunity to move things to conductor, right?15:19
ktibileakypipes, pike with kolla15:19
bauwsernot nobody objected15:19
leakypipesktibi: if you could pastebin the placement-api logs, too, that would be great15:19
sean-k-mooney[m]bauwser: ya so rofolfo work on this for 2 cycles. i was just ment to be rebasing it an resubmitting his work this cycle. if its beyond that however i have to escalate to my managment to see if i can work on it an rewrite it to track the nic features as tratis in placement.15:20
bauwserI see15:20
bauwserokay, I don't honestly want to throw you under the bus15:20
*** itlinux has joined #openstack-nova15:21
bauwsermy only concern is that it creates more tech debt15:21
sean-k-mooney[m]bauwser:  today there is no reason we could not use nested RPs + traits to track the nic feartres for sriov device.15:21
bauwserbut I see leakypipes +2ing that spec15:21
sean-k-mooney[m]we have been storing that in the nova db since pike. the remainder of the spec is consuming it in the schduler.15:21
bauwserso I guess it's more or less a trade-off15:21
sean-k-mooney[m]bauwser:  ya that is fair15:21
bauwserwell, okay, I have to disappear in a short few because of kids, but once I'm back, I'll reevaluate the spec15:22
sean-k-mooney[m]well i can ask can i try to port this once it merges to placement15:22
ktibileakypipes, I checked placement log, i can see only info log with GET on resource_providers/705b7a45-ce71-4455-8349-6cee4c051c0e/inventories15:22
leakypipesktibi: question for you... it looks like there are no instances in the cell DB for that compute node. were there originally instances on it?15:23
sean-k-mooney[m]ok cool im technically off today but let me know what you decide and ill be back monday15:23
ktibileakypipes, no when I remove this node, I disable service, evacuate all instances, remove service and shutdown the compute15:24
*** bhagyashris has quit IRC15:24
leakypipesktibi: k. I'm wondering maybe the placement service for some reason didn't get updated with the removal of those instances...15:24
sean-k-mooney[m]bauwser: if i was able to also port to doing this in placement in rocky that would be the best outcome but im ment to work on someting else internally from april that 10%.15:24
leakypipesktibi: can you please execute the following SQL query against the nova api database?15:24
*** Shilpa has quit IRC15:25
*** cdent has joined #openstack-nova15:25
leakypipesktibi: SELECT COUNT(*) FROM allocations AS a JOIN inventories AS i ON a.resource_provider_id = i.resource_provider_id JOIN resource_providers AS rp ON i.resource_provider_id = rp.id WHERE rp.uuid = '91f9e750-351f-463e-aa00-c8843c37560e';15:25
*** melwitt is now known as jgwentworth15:26
ktibileakypipes, count : 015:26
sean-k-mooney[m]o/ ok ill stop working on my day off now... maybe...15:26
leakypipesktibi: ok, good.15:26
leakypipesktibi: what about this one? SELECT COUNT(*) FROM inventories AS i ON a.resource_provider_id = i.resource_provider_id JOIN resource_providers AS rp ON i.resource_provider_id = rp.id WHERE rp.uuid = '91f9e750-351f-463e-aa00-c8843c37560e';15:26
leakypipesktibi: oops, sorry15:26
leakypipesktibi: what about this one? SELECT COUNT(*) FROM inventories AS i JOIN resource_providers AS rp ON i.resource_provider_id = rp.id WHERE rp.uuid = '91f9e750-351f-463e-aa00-c8843c37560e';15:27
ktibileakypipes, maybe that can help you http://paste.openstack.org/show/710164/15:27
ktibileakypipes, count : 0 too15:28
leakypipesk15:28
leakypipesktibi: got it...15:28
cdentfigleaf, fried_rice, leakypipes : just to confirm: I assume we would like the forbidden traits support to show up in the same microversion for /resource_providers and /allocation_candidates, yes?15:28
leakypipesktibi: your services table has two records for compute0615:28
leakypipesktibi: delete the one where deleted_at is not NULL.15:29
ktibiyes I see :) I waiting your comfirmation to delete it ^^15:29
fried_ricecdent: Sure, unless there's some reason to split 'em.15:29
cdentfried_rice: only if we want to make the code more split into stages15:29
fried_riceno, not necessary IMO.15:29
fried_ricecdent: In fact, I find myself slightly irked that we can't include multiple features in a single microversion - for reasons of our development process, not for any technical reason.15:30
fried_ricecdent: But in this case, it's the same feature, so we can totally get away with it.15:30
cdentyes and yes15:31
leakypipesktibi: and then set disabled=0 on the other services table record with copmute06 host name.15:31
leakypipesktibi: finally, can you show me what the compute_nodes table looks like please? just do this: SELECT id, uuid, hypervisor_hostname FROM compute_nodes;15:32
ktibileakypipes, ho I can see two compute0615:33
ktibileakypipes, http://paste.openstack.org/show/710169/15:34
mlavallerybridges: in that log statement right above L225, could you log aggregate.uuid? The reason I am asking this is https://review.openstack.org/#/c/415031/, which fixes https://bugs.launchpad.net/nova/+bug/165264215:35
openstackLaunchpad bug 1652642 in OpenStack Compute (nova) "Nova API doesn't return aggregate's uuid, which is needed when using the placement API" [High,Fix released] - Assigned to Matt Riedemann (mriedem)15:35
leakypipesktibi: DELETE FROM compute_nodes WHERE id = 15;15:35
leakypipesktibi: that *should* fix things up...15:36
ktibileakypipes, ok I restart nova compute on 0615:36
openstackgerritmelanie witt proposed openstack/nova master: Move _make_instance_list call outside of DB transaction context  https://review.openstack.org/55509315:36
mlavallerybridges: this is the Nova API version you require for aggregates to have a uuid: https://review.openstack.org/#/c/415031/9/nova/api/openstack/api_version_request.py@10015:37
ktibileakypipes, same error on compute06 : Another thread already created a resource provider with the UUID 91f9e750-351f-463e-aa00-c8843c37560e. Grabbing that record from the placement API.15:37
ktibimaybe need to restart placement ?15:37
leakypipesktibi: well, that's not an error. :) the error is the "Cannot refresh inventory" thing.15:38
openstackgerritMatt Riedemann proposed openstack/nova master: Create volume attachment during boot from volume in compute  https://review.openstack.org/54142015:38
leakypipesktibi: no, no need to restart placement.15:38
leakypipesktibi: what we want to see is inventory records being created in placement.15:38
ktibileakypipes, ok I'll test to migrate instance to this host15:39
*** links has joined #openstack-nova15:40
*** gyee has joined #openstack-nova15:41
*** josecastroleon has joined #openstack-nova15:42
figleafcdent: yes, one microversion for that makes sense15:42
*** chyka has joined #openstack-nova15:43
ktibileakypipes, ok fail :/15:43
ktibileakypipes, exception thrown: No valid host was found. Unable to move instance f8e70257-244e-4fa7-b545-0a888b742b84 to host compute06. There is not enough capacity on the host for the instance.15:43
gibletmriedem, leakypipes, mlavalle: is it OK for you If I publish a new version of the bandwidth spec soon, or you are just in the middle of reviewing the current PS?15:44
mlavallegiblet: I'm good15:44
mriedemgiblet: i haven't gone back over the comments since i last reviewed it last week15:45
mriedemi could do that quick i guess...15:45
ktibileakypipes, http://paste.openstack.org/show/710182/15:46
gibletmriedem: I still need about an hour to do the update locally, if that is enough for you. Or you can go back after I published the new rev.15:46
kashyapmriedem: So just checked w/ the folks on -infra, the Gate already does have the "Bionic" (upcoming Ubuntu LTS) images.  Do we have any non-voting Nova jobs for it?15:46
kashyap(Near as see, none.)15:46
mriedemkashyap: no15:46
*** links has quit IRC15:46
mriedemkashyap: i'm just trying to get us to using the queens UCA right now15:46
mriedemhttps://review.openstack.org/#/c/554317/15:47
* kashyap clicks15:47
gibletmriedem: there will some new problems described in the update15:47
gibletmriedem: so you might want to read the new rev anyhow15:47
mriedemgiblet: i've got about 20 minutes so i'll go over the replies quick15:48
gibletmriedem: OK, cool, thanks15:48
-openstackstatus- NOTICE: Gerrit will be temporarily unreachable as we restart it to complete the rename of some projects.15:49
*** diga has quit IRC15:52
mriedemgiblet: yeah i can already see issues with https://review.openstack.org/#/c/502306/17/specs/rocky/approved/bandwidth-resource-provider.rst@10015:52
mriedemso commenting15:52
*** yamamoto has joined #openstack-nova15:53
mriedemand gerrit just shit the bed15:54
gibletgerrit: you are not helpful at all!15:56
gibletmriedem: gerrit is back15:59
*** yassine has quit IRC15:59
*** yamamoto has quit IRC15:59
mriedemhuzzah15:59
bauwsersean-k-mooney[m]: +Wd15:59
openstackgerritEric Berglund proposed openstack/nova master: PowerVM Driver: Snapshot  https://review.openstack.org/54302316:00
*** yassine has joined #openstack-nova16:00
*** gyankum has quit IRC16:00
rybridgesmlavalle: you might be on to something. When I try to print aggregate.uuid, my log message gets swallowed and i dont see anything getting printed16:01
bauwserhum16:01
bauwserhttps://review.openstack.org/#/dashboard/?foreach=(project%253Aopenstack%252Fnova-specs)+status%253Aopen+NOT+owner%253Aself+NOT+label%253AWorkflow%3C%253D-1+label%253AVerified%3E%253D1%252Cjenkins+NOT+reviewedby%253Aself+is%253Amergeable&title=Nova+Specs+Review+Inbox+&Needs+final+%252B2=NOT+label%253ACode-Review%3C%253D-1%252Cnova-core+label%253ACode-Review%3E%253D2&Small+Patches=NOT+label%253ACode-Review%3C%253D-1%252Cnova-cor16:01
bauwserdelta%253A%3C%253D10&Needs+Feedback+(Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone)=NOT+label%253ACode-Review%3C%253D2+age%253A5d&You+are+a+reviewer%252C+but+haven't+voted+in+the+current+revision=reviewer%253Aself&Passed+Jenkins%252C+No+Negative+Core+Feedback=NOT+label%253ACode-Review%3C%253D-1%252Cnova-core+NOT+message%253A%22Closes-Bug%253A+%22&Wayward+Changes+(Changes+with+no+code+review+in+the+last+5+days)16:01
bauwserabel%253ACode-Review%3C%253D2+NOT+label%253ACode-Review%3C%253D-1%252Cnova-core+age%253A5d16:01
bauwsermy gerrit dashboard is just getting me only two specs...16:02
bauwserWTF ?16:02
kashyapGive it a couple of mins to breathe16:02
*** suresh12 has joined #openstack-nova16:04
rybridgesmlavalle: I should have the right version though... Everything I am running is just stock stable/ocata built from source. dont even have any patches yet16:06
mriedemgiblet: replies in PS17 https://review.openstack.org/#/c/502306/17/16:07
*** jroll has quit IRC16:07
gibletmriedem: looking16:07
*** mriedem is now known as mriedem_afk16:09
gibletmriedem_afk: good points. I will dig it16:09
openstackgerritMerged openstack/nova-specs master: Reintroduced nic feature based scheduling for rocky  https://review.openstack.org/54595116:10
*** jroll has joined #openstack-nova16:10
*** AlexeyAbashkin has quit IRC16:14
*** josecastroleon has quit IRC16:15
*** jroll has quit IRC16:15
*** rama_y has joined #openstack-nova16:16
*** jroll has joined #openstack-nova16:16
bauwserleakypipes: just a comment on https://review.openstack.org/#/c/545057/5 preventing a +2, just add your thoughts on error handling and I'm +216:16
* bauwser disappears for a couple of hours but will be back tonight16:16
*** harlowja has joined #openstack-nova16:16
rybridgesmlavalle: One other thing to note perhaps... When I do openstack aggregate show, I see the ID, but not the uuid in the output. If I want to see the uuid I need to go to the db and look at the aggregates table.16:17
mlavallerybridges: give me a few minutes and I'll check in my dev system16:17
mlavalleI was going to propose you check with the CLI16:17
mlavalleso you got ahead of me ;-)16:17
*** danpawlik has joined #openstack-nova16:18
rybridgescool thanks! Yea i am taking a look at the CLI now. Even when I run aggregate list with the --debug option i still do not see the uuid from the db anywhere in the response. That is likely related to the problem16:19
rybridgesThe response body looks like this: {"aggregates": [{"name": "Neutron segment id b9d173e2-fff2-4a33-ac50-312e6f3be914", "availability_zone": null, "deleted": false, "created_at": "2018-03-23T15:59:51.000000", "updated_at": null, "hosts": [], "deleted_at": null, "id": 19, "metadata": {}}]}16:20
*** penick is now known as JunoMan16:22
*** danpawlik has quit IRC16:23
*** jmlowe has quit IRC16:25
*** afaranha has quit IRC16:26
*** germs has quit IRC16:26
*** germs has joined #openstack-nova16:27
*** germs has quit IRC16:27
*** germs has joined #openstack-nova16:27
*** ralonsoh has quit IRC16:30
*** josecastroleon has joined #openstack-nova16:31
*** archit has quit IRC16:32
cfriesensahid: for what it's worth, I think your short-term proposal to run isolated emulator threads on 'CONF.cpu_shared_set' is reasonable, though I have one question--what would we do if that set is empty?  Allocate a new host CPU like we do now and emit a log?16:33
openstackgerritDan Smith proposed openstack/nova master: Add request filter functionality to scheduler  https://review.openstack.org/54473016:34
openstackgerritDan Smith proposed openstack/nova master: Add aggregates list to Destination object  https://review.openstack.org/54472916:34
openstackgerritDan Smith proposed openstack/nova master: Make get_allocation_candidates() honor aggregate restrictions  https://review.openstack.org/54799016:34
openstackgerritDan Smith proposed openstack/nova master: Add AggregateList.get_by_metadata() query method  https://review.openstack.org/54472816:34
openstackgerritDan Smith proposed openstack/nova master: Add require_tenant_aggregate request filter  https://review.openstack.org/54500216:34
openstackgerritDan Smith proposed openstack/nova master: WIP: Honor availability_zone hint via placement  https://review.openstack.org/54628216:34
openstackgerritDan Smith proposed openstack/nova master: Add an index on aggregate_metadata.value  https://review.openstack.org/55585116:34
mlavallerybridges: this is what I see in my dev environment, which was built from trunk about a week ago: http://paste.openstack.org/show/710244/16:34
*** fried_rice is now known as fried_rolls16:35
openstackgerritMerged openstack/python-novaclient master: Updated from global requirements  https://review.openstack.org/55559016:35
*** josecastroleon has quit IRC16:36
leakypipesgiblet: totally cool with me if you publish a new version of the bw spec16:37
*** maciejjozefczyk has quit IRC16:37
leakypipesktibi: ok, so inventory isn't being created properly on the compute06 for some reason...16:37
*** maciejjozefczyk has joined #openstack-nova16:37
leakypipesktibi: still trying to figure out why that is.16:37
*** maciejjozefczyk has quit IRC16:37
*** tbachman has joined #openstack-nova16:38
gibletmriedem_afk: I left my view in the reply https://review.openstack.org/#/c/502306/17/specs/rocky/approved/bandwidth-resource-provider.rst@10016:38
ktibileakypipes, yes need to clean all compute06 in all DB for works.16:38
*** maciejjozefczyk has joined #openstack-nova16:38
ktibithx for your time :p16:38
leakypipesnp16:40
*** kaisers_ has joined #openstack-nova16:42
*** Tom-Tom has joined #openstack-nova16:42
rybridgesmlavalle: I did not build from trunk. I am running stable/ocata. My output looks like this: http://paste.openstack.org/show/710254/16:42
*** maciejjozefczyk has quit IRC16:43
openstackgerritKonstantinos Samaras-Tsakiris proposed openstack/nova master: Add `hide_hypervisor_id` flavor extra_spec  https://review.openstack.org/55586116:43
mlavallerybridges: run the command with --debug, so we can see the response. the client might be out of synch with the API16:43
*** Tom-Tom has quit IRC16:46
cdentleakypipes: I suspect my forbidden changes in allocation candidates are going to collide a fair bit with the stuff you are working on for nested, especially since I think both sets of work are going to reveal some necessary changes with how trait handling is desired to work. I don't think it will be dire or anything, just a heads up16:46
mlavallerybridges: I'll be away from my keyboard for a while. I have to pick up my wife. I'll ping you when I come back16:51
*** mdbooth has quit IRC16:52
*** david-lyle has quit IRC16:52
leakypipescdent: ack, you are correct.16:52
leakypipescdent: I should have the next revision of that code (https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/nested-resource-providers-allocation-candidates) pushed within the next hour.16:53
cdentcool, my stuff is very spikey at the moment but almost working16:53
leakypipescdent: just trying to get fried_rolls's update provider tree series reviewed right now16:53
leakypipescdent: coolio.16:53
*** Swami has joined #openstack-nova16:54
*** bnemec is now known as beekneemech16:54
*** yamamoto has joined #openstack-nova16:55
rybridgesmlavalle: Here is debug output http://paste.openstack.org/show/710270/16:55
*** lucasagomes is now known as lucas-afk16:57
*** yamamoto has quit IRC17:00
*** tbachman has quit IRC17:01
*** hemna_ has joined #openstack-nova17:01
cfriesenbauwser: question for you..if an operator doesn't want to expost a host as NUMA-aware, why not just reboot with "numa=off" on the kernel boot args?17:05
*** andreas_s has joined #openstack-nova17:06
*** masber has quit IRC17:06
*** sususuryashines has quit IRC17:07
openstackgerritElod Illes proposed openstack/nova stable/ocata: Functional test for regression bug #1713783  https://review.openstack.org/50516017:09
openstackbug 1713783 in OpenStack Compute (nova) ocata "After failed evacuation the recovered source compute tries to delete the instance" [High,In progress] https://launchpad.net/bugs/1713783 - Assigned to Balazs Gibizer (balazs-gibizer)17:09
*** mriedem_afk has quit IRC17:14
openstackgerritElod Illes proposed openstack/nova master: Functional test: cold migrate to compute down  https://review.openstack.org/49628017:15
*** dtantsur is now known as dtantsur|afk17:16
*** mdamkot has joined #openstack-nova17:17
*** vks1 has joined #openstack-nova17:18
*** masber has joined #openstack-nova17:18
*** damien_r has quit IRC17:22
*** pcaruana has quit IRC17:23
*** archit has joined #openstack-nova17:24
*** itlinux has quit IRC17:27
*** ktibi has quit IRC17:29
openstackgerritTyler Blakeslee proposed openstack/nova master: Add __repr__ for NovaException  https://review.openstack.org/55581217:29
*** beekneemech has quit IRC17:29
openstackgerritJay Pipes proposed openstack/nova-specs master: mirror nova host aggregates to placement API  https://review.openstack.org/54505717:30
openstackgerritBalazs Gibizer proposed openstack/nova-specs master: Network bandwidth resource provider  https://review.openstack.org/50230617:32
*** bnemec has joined #openstack-nova17:32
*** suresh12 has quit IRC17:32
*** bnemec is now known as beekneemech17:33
*** beekneemech has quit IRC17:34
*** bnemec has joined #openstack-nova17:34
gibletmriedem, leakypipes, mlavalle, rubasov: I've published a new rev from the bandwidth spec covering two new issues 1) simulating neutron backend selection with a new scheduler weigher 2) handling the mapping between physical resource consumption and the resource claim  https://review.openstack.org/#/c/50230617:35
sahidcfriesen: is the set is empty so we use the default behavior of hw:emulator_threads_policy="share"17:35
*** maciejjozefczyk has joined #openstack-nova17:35
sahidi will update the spec for monday17:35
*** suresh12 has joined #openstack-nova17:36
*** suresh12 has quit IRC17:36
*** suresh12 has joined #openstack-nova17:36
*** suresh12 has quit IRC17:36
*** mdamkot has quit IRC17:36
*** masber has quit IRC17:37
*** maciejjozefczyk has quit IRC17:39
*** gjayavelu has joined #openstack-nova17:39
*** mgoddard has quit IRC17:40
*** mriedem has joined #openstack-nova17:41
leakypipesgiblet: reviewing it as we speak...17:41
mriedemrybridges: aggregate uuids were in a later microversion, openstack CLI defaults to 2.1, so if you want the uuid in the openstack aggregate show output, you need to opt into the microversion17:42
mriedemopenstack aggregate list --openstack-compute-api-version 2.4117:42
mriedemsomething like that17:42
mriedem--os-compute-api-version i mean17:43
*** jpena is now known as jpena|off17:43
*** psachin has joined #openstack-nova17:44
rybridgesok thanks mriedem. I can try that. Is there a way to tell nova to use that microversion on the backend as well? That may work for me as a user on the CLI, but the backend also needs to be able to use that microversion as well17:45
*** derekh has quit IRC17:46
jgwentworthmaybe some progress has been made but yesterday rybridges said there weren't any hosts in the nova_api.aggregate_hosts table, proving that the request to add the host to the aggregate never made it there17:48
mriedemrybridges: i don't understand your question17:48
mriedemwhat is "the backend"?17:48
jgwentworthso not a microversion showing the uuids issue17:48
openstackgerritMerged openstack/nova master: Always deallocate networking before reschedule if using Neutron  https://review.openstack.org/52024817:49
openstackgerritMatt Riedemann proposed openstack/nova stable/queens: Always deallocate networking before reschedule if using Neutron  https://review.openstack.org/55541817:49
*** harlowja has quit IRC17:50
mriedemrybridges: specifying --os-compute-api-version 2.x on the CLI passes that in a header to the compute REST API, which then processes that single request with that microversion17:50
*** sahid has quit IRC17:51
rybridgesmriedem: What I mean is.. I need neutron to also use the correct microversion when it creates aggregates. Like in this call: https://github.com/openstack/neutron/blob/stable/ocata/neutron/services/segments/plugin.py#L22417:52
*** vks1 has quit IRC17:52
rybridgesI realize i can pass the microversion manually when I am running on the CLI, but how does neutron know to use the right microversion when it needs to create aggregates on my behalf?17:52
rybridgesI am guessing there is some configuration somewhere in neutron.conf or nova.conf where I can specify the microversion?17:53
mriedemneutron doesn't have microversions17:53
*** AlexeyAbashkin has joined #openstack-nova17:53
mriedemand nova aggregates don't have anything to do with neutron17:53
mriedemnova doesn't pass a microversion through it's compute API to neutron17:53
jgwentworthyou can pass microversions with the novaclient python bindings, so the neutron plugin could do that, I think17:53
mriedemmicroversions in config files isn't a thing17:53
mriedemneutron is a client,17:54
jgwentworthhe's talking about some kinda neutron plugin that creates nova aggregates and adds hosts to aggregates when using the routed provider network segments stuff17:54
mriedemof the placement API (and compute API?),17:54
mriedemso neutron, as a client, will need to specify a microversion when it makes its own requests17:54
mriedemif they require some minimum microversion17:54
mriedemthis is the same thing as cinder calling the compute os-server-external-events API with a microversion to pass volume-extended events17:55
mriedemhttps://github.com/openstack/cinder/blob/master/cinder/compute/nova.py#L20717:55
*** felipemonteiro has joined #openstack-nova17:55
*** yamamoto has joined #openstack-nova17:56
rybridgesya jgwentworth gets what I am doing. So in my case, the openstack network subnet create command is creating the aggregate for me. I never ask nova explicitly myself to do it, it happens in the backend as part of the subnet create command. So I need to pass the microversion into the subnet create command maybe.. I can try that17:56
*** yamahata has quit IRC17:57
*** AlexeyAbashkin has quit IRC17:57
jgwentworthrybridges: here is what I was talking about, when the client object is instantiated, a microversion can be specified, but I think there's also a way to specify per call https://docs.openstack.org/python-novaclient/pike/reference/api/index.html#usage17:57
jgwentworthnot seeing that in this doc tho17:58
*** AlexeyAbashkin has joined #openstack-nova17:58
*** david-lyle has joined #openstack-nova17:59
*** jmlowe has joined #openstack-nova18:00
jgwentworthactually, not seeing a way to specify a microversion per-call in the novaclient python API18:01
*** yamamoto has quit IRC18:02
mriedemfried_rolls: hopefully i've word-smithed this well enough https://review.openstack.org/#/c/555481/18:02
mriedemrybridges: you should not have to pass through a compute api version to neutron18:03
mriedemif neutron is going to create aggregates in nova, and needs the uuid, then it must use at least microversion 2.4118:03
*** AlexeyAbashkin has quit IRC18:03
mriedemelse it's a bug18:03
mriedemthere is not a way to specify a microversion per call in novaclient's python binding API, as it's stored on the client object when it's constructed,18:04
mriedemyou could probably mutate the internals of the client object, but we don't have a supported hook for doing that18:04
rybridgesokay thanks mriedem thtat is helpful to know18:04
*** Tom-Tom has joined #openstack-nova18:05
rybridgesThe uuid is not being returned by the python novaclient when an aggregate is created from neutron, that i know for sure18:05
leakypipesgiblet: small request in review.18:05
mriedemwhere in the neutron code does neutron create a nova host aggregate?18:06
rybridgesso maybe this code in neutron that instantiates the client is not correct and/or is not instantiating the python novaclient with the correct microversion18:06
mriedemhttps://github.com/openstack/neutron/blob/stable/ocata/neutron/services/segments/placement_client.py#L163 is NOT nova18:06
mriedemplacement aggregates != nova host aggregates18:06
mriedemcompletely different REST APIs18:06
rybridgesright here: https://github.com/openstack/neutron/blob/master/neutron/services/segments/plugin.py#L22118:06
rybridgesthis is going thru nova client, not placement client18:06
rybridgesto create the aggregate18:06
openstackgerritJay Pipes proposed openstack/nova master: tests for alloc candidates with nested and traits  https://review.openstack.org/53189918:07
openstackgerritJay Pipes proposed openstack/nova master: placement: resource requests for nested providers  https://review.openstack.org/55452918:07
*** oomichi has joined #openstack-nova18:07
leakypipesfried_rolls: ok, ready for your re-re-re-review ^^18:07
leakypipesfigleaf: you too :)18:07
mriedemrybridges: https://github.com/openstack/neutron/blob/master/neutron/services/segments/plugin.py#L4818:07
mriedemnovaclient is created with 2.4118:07
mriedemso it's using 2.4118:07
rybridgesheh yup18:08
rybridgesthats pretty strange18:08
rybridgesdoesnt make sense why the uuid is not returned. i cannot print it. and any call that references it gets swallowed18:08
mriedemthe POST /os-aggregates API ref says that uuid is returned https://developer.openstack.org/api-ref/compute/#create-aggregate18:09
mriedemso which version of novaclient are you using?18:09
*** Tom-Tom has quit IRC18:09
mriedem7.1.2? https://github.com/openstack/requirements/blob/stable/ocata/upper-constraints.txt#L33218:09
rybridges7.1.3 looks like18:10
mriedemanyway, this is the object you get in novaclient https://github.com/openstack/python-novaclient/blob/7.1.2/novaclient/v2/aggregates.py#L2118:10
mriedemit's just an object that extends dict and has the POST response body as attributes18:10
mriedemso 'uuid' should be in there18:10
*** kaisers_ has quit IRC18:11
artomcfriesen, sean-k-mooney[m], thanks for the reviews guys. Busy with some downstream stuff, so not as responsive as I'd like18:11
artomCan we settle on the scope of the spec though? Specifically, include or not PCI stuff18:12
mriedemthis is the code that returns the aggregate response body https://github.com/openstack/nova/blob/stable/ocata/nova/api/openstack/compute/aggregates.py#L20418:12
artomIf we go with EPA as sean-k-mooney[m]'s saying, we'd kinda have to, but I'm worried about scope creep, and actually finishing it this cycle18:12
mriedemand i know that works because otherwise this response, used in our testing for 2.41, would fail https://github.com/openstack/nova/blob/stable/ocata/doc/api_samples/os-aggregates/v2.41/aggregate-post-resp.json18:13
rybridgesYea that makes sense mriedem. I realize things would break in tests if the uuid actually wasnt being returned. I did just see something interested though: http://paste.openstack.org/show/710369/18:14
rybridgesLooks like maybe my nova backend does not support microversions for some reason. Perhaps that is the problem. I cannot instantiate a client with a microversion at all18:14
mriedemfirst, you don't need to specify a specific microversion on the nova CLI since the nova CLI opts into, by default, the latest available between the server and client18:15
*** maciejjozefczyk has joined #openstack-nova18:15
mriedemas for that 'does not support microversions' stuff, idk what you guys do to hack things up for your own api extensions18:15
*** tbachman has joined #openstack-nova18:15
*** slagle has quit IRC18:15
rybridgeswe have 0 patches in the environment i am using right now18:15
rybridges018:16
*** sambetts is now known as sambetts|afk18:16
rybridgesjgwentworth said earlier that i can pass the microversion into the backend as an argument so i figured i would try it. thats all.18:16
mriedem"pass the microversion into the backend" isn't a thing18:16
mriedemjust do a simple curl request to your compute endpoint URL18:17
mriedemthat will give you the version document18:17
mriedemand https://github.com/openstack/python-novaclient/blob/5af4a8edd88187e0a21c665a6e91fcdcd8ced06c/novaclient/api_versions.py#L265 is complaining that there is no min/max version in your compute endpoint version doc18:18
jgwentworthI think we're just using different words. but in the novaclient python API bindings, you *can* specify a microversion when the client object is created, in fact, I think you have to. if it allows you not to, then it will default to the lowest/base microversion18:18
cfriesenartom: no worries, I'm in the same boat18:18
mriedemjgwentworth: yes and as i pointed out above, neutron is creating novaclient with version 2.4118:19
cfriesenartom: leave PCI out for now18:19
mriedemhard-coded18:19
jgwentworthI was mistaken that there was some way to specify microversion *per call* after instantiating the client object. I am not seeing a way to do that18:19
jgwentworthokay, so that is taken care of. so rybridges that code is calling with 2.41 already18:19
cfriesenartom: there are additional complications for PCI that merit a separate spec18:19
mriedemthe novaclient python API bindings default to 2.1, the CLI defaults to the latest available between the server and what the client understands18:19
jgwentworthright18:19
*** suresh12 has joined #openstack-nova18:20
artomcfriesen, cool, good to know you'll back be on that :)18:20
artom*back me18:20
openstackgerritChris Dent proposed openstack/nova master: WIP: Support for forbidden traits in placement  https://review.openstack.org/55466518:20
mriedemfried_rolls: want to backport https://review.openstack.org/#/c/554759/ to queens?18:20
*** maciejjozefczyk has quit IRC18:21
rybridgesOk so if the CLI defaults to the latest version that the server understands, then my server does not understand 2.41. If it did, then I would see the uuid in the response body of this call: http://paste.openstack.org/show/710386/18:21
rybridgeseither that or its not defaulting to the highest version available but rather the lowest base18:23
jgwentworthyou're running ocata, yes? you should have it https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#id3718:23
mriedem{"version": {"status": "SUPPORTED", "updated": "2011-01-21T11:33:21Z", "links": [{"href": "http://XXX:8774/v2/", "rel": "self"}, {"href": "http://docs.openstack.org/", "type": "text/html", "rel": "describedby"}], "min_version": "", "version": "", "media-types": [{"base": "application/json", "type": "application/vnd.openstack.compute+json;version=2"}], "id": "v2.0"}}18:23
mriedemthat's your server's compute endpoint url version doc18:23
mriedemnote there is no min or version18:23
mriedemversion == max18:23
mriedemso yeah, your cloud is f'ed18:23
jgwentworthyeah ... you have ocata right rybridges?18:24
rybridgesyes i am running stable/ocata18:24
jgwentworthhm, wtf18:24
superdanthis seems like #openstack fodder, no?18:24
mriedemafter 2 days of debugging this issue, yes18:24
mriedemthis is BASIC stuff18:24
superdanespecially if this is just installation basically18:25
superdanyeah18:25
mriedemwhere are sean-k-mooney[m] and cfriesen around when i need to flood this channel with placement and NFV talk?18:25
*** sdeath has joined #openstack-nova18:25
figleafleakypipes: ack. Will re-review in a few18:26
*** psachin has quit IRC18:26
*** sree has quit IRC18:26
*** sree has joined #openstack-nova18:27
*** tbachman has quit IRC18:27
*** yamahata has joined #openstack-nova18:29
cdentmriedem, superdan : if you like less code, the requirements dependency for removing microversion stuff in placement to a library has been improved: https://review.openstack.org/#/c/550265/18:30
cdentsigh: s/improved/approved/18:30
mriedemi like more code on fridays18:30
openstackgerritMerged openstack/nova master: trivial: omit condition evaluations  https://review.openstack.org/54524818:31
openstackgerritMerged openstack/nova master: Stop using mox in virt/xenapi/image/test_vdi_through_dev.py  https://review.openstack.org/34268218:31
cdentmriedem: you never were any fun18:31
*** lajoskatona has quit IRC18:31
*** andreas_s has quit IRC18:31
*** sree has quit IRC18:31
*** maciejjozefczyk has joined #openstack-nova18:32
*** itlinux has joined #openstack-nova18:33
*** eharney has quit IRC18:35
*** tbachman has joined #openstack-nova18:36
cdentleakypipes you might also like https://review.openstack.org/#/c/550265/ <- placement using microversion-parse 0.2.118:36
*** chyka has quit IRC18:37
*** r-daneel has joined #openstack-nova18:37
*** chyka has joined #openstack-nova18:37
*** chyka_ has joined #openstack-nova18:41
*** chyka has quit IRC18:42
*** tssurya has joined #openstack-nova18:45
*** pchavva1 has joined #openstack-nova18:45
openstackgerritEric Fried proposed openstack/nova stable/queens: Change compute mgr placement check to region_name  https://review.openstack.org/55590118:47
*** andreas_s has joined #openstack-nova18:47
fried_rollsmriedem: Done ^18:47
fried_rollsleakypipes: ack18:47
*** itlinux has quit IRC18:47
*** maciejjozefczyk has quit IRC18:47
*** lajoskatona has joined #openstack-nova18:47
*** jmlowe has quit IRC18:47
mriedemthanks18:48
jgwentworthindeed looks like it's an installation problem. from the novaclient --debug output, it's talking to the /v2 nova endpoint which doesn't do microversions. it's supposed to be /v2.1 (in the service catalog)18:48
cdentfried_rolls: wasn't half the bug there that people should have to express either region_name or os_region_name if they are using the default? not just that they were using the wrong one?18:48
*** itlinux has joined #openstack-nova18:49
fried_rollscdent: The bug was that, if you specified os_region_name, you got a deprecation warning, but it worked.  But if you specified region_name, it just didn't work at all.18:49
fried_rollsbut yeah, pretty sure you have to specify one or the other.18:50
fried_rollswhich... is kind of a pity, really.18:50
cdentthat seems wrong18:50
*** r-daneel_ has joined #openstack-nova18:50
*** andreas_s has quit IRC18:51
*** r-daneel has quit IRC18:52
*** r-daneel_ is now known as r-daneel18:52
figleafleakypipes: can you explain what's going on in https://review.openstack.org/#/c/554529/2/nova/api/openstack/placement/objects/resource_provider.py@3055 ?18:53
*** dave-mcc_ has quit IRC18:55
figleafleakypipes: oh, never mind. I think I got it18:56
*** yamamoto has joined #openstack-nova18:58
sean-k-mooney[m]mriedem: today on vacation19:02
JunoManSorry for wasting your time with the microversion confusion y'all. We missed that in the kilo release notes.19:02
*** yamamoto has quit IRC19:02
mriedemsean-k-mooney[m]: was just joking, probably missed the context19:03
mriedemignore19:03
sean-k-mooney[m]mriedem: also after yesterday i think i need to not think about numa/nfv for at least a day or two19:03
mriedemsuperdan: the reader/writer fixes are ready to go imo https://review.openstack.org/#/q/topic:bug/1746509+(status:open+OR+status:merged)19:05
sean-k-mooney[m]mriedem:  hehe ya i know. i may have installed riot.im on my phone and now get irc routed too me now. it has its pros and cons19:06
jrollJunoMan: excellent friday nick19:06
*** itlinux has quit IRC19:08
*** lpetrut_ has quit IRC19:08
superdanmriedem: okay will look in a few19:09
*** harlowja has joined #openstack-nova19:09
openstackgerritJulia Kreger proposed openstack/nova master: WIP: Add microversion to ironic client wrapper call  https://review.openstack.org/55476219:11
jgwentworthwill superdan strike down my code comment sentence? time will tell19:11
superdansources from beyond the grave say.....PLAUSIBLE19:12
jgwentworthlol19:12
*** tssurya has quit IRC19:13
*** AlexeyAbashkin has joined #openstack-nova19:14
*** itlinux has joined #openstack-nova19:15
*** hemna_ has quit IRC19:15
*** itlinux has quit IRC19:16
*** lajoskatona has quit IRC19:17
openstackgerritEric Berglund proposed openstack/nova master: PowerVM Driver: vSCSI volume driver  https://review.openstack.org/52609419:18
*** AlexeyAbashkin has quit IRC19:19
*** tssurya has joined #openstack-nova19:22
*** felipemonteiro__ has joined #openstack-nova19:23
*** vivsoni__ has joined #openstack-nova19:23
*** suresh12 has quit IRC19:25
*** felipemonteiro has quit IRC19:26
*** vivsoni_ has quit IRC19:26
*** bkopilov has quit IRC19:27
openstackgerritMatt Riedemann proposed openstack/nova stable/pike: Always deallocate networking before reschedule if using Neutron  https://review.openstack.org/55590719:28
*** avolkov has quit IRC19:28
*** bkopilov has joined #openstack-nova19:31
*** openstackgerrit has quit IRC19:34
*** suresh12 has joined #openstack-nova19:38
*** fried_rolls is now known as fried_rice19:40
*** jmlowe has joined #openstack-nova19:43
*** openstackgerrit has joined #openstack-nova19:45
openstackgerritMerged openstack/nova master: Updated from global requirements  https://review.openstack.org/55557619:45
*** eharney has joined #openstack-nova19:49
*** fragatina has quit IRC19:52
*** lpetrut has joined #openstack-nova19:53
*** moshele has joined #openstack-nova19:55
*** yamamoto has joined #openstack-nova19:58
openstackgerritmelanie witt proposed openstack/nova stable/queens: Add functional regression test for bug 1746509  https://review.openstack.org/55591420:02
openstackbug 1746509 in OpenStack Compute (nova) "TypeError: Can't upgrade a READER transaction to a WRITER mid-transaction" [Medium,In progress] https://launchpad.net/bugs/1746509 - Assigned to melanie witt (melwitt)20:02
openstackgerritmelanie witt proposed openstack/nova stable/queens: Move _make_instance_list call outside of DB transaction context  https://review.openstack.org/55591520:02
*** gouthamr has quit IRC20:03
*** patriciadomin has joined #openstack-nova20:03
*** sidx64 has joined #openstack-nova20:04
*** yamamoto has quit IRC20:04
*** elmaciej has quit IRC20:05
openstackgerritmelanie witt proposed openstack/nova stable/pike: Add functional regression test for bug 1746509  https://review.openstack.org/55505820:06
openstackbug 1746509 in OpenStack Compute (nova) "TypeError: Can't upgrade a READER transaction to a WRITER mid-transaction" [Medium,In progress] https://launchpad.net/bugs/1746509 - Assigned to melanie witt (melwitt)20:06
openstackgerritmelanie witt proposed openstack/nova stable/pike: Move _make_instance_list call outside of DB transaction context  https://review.openstack.org/55592320:06
openstackgerritKonstantinos Samaras-Tsakiris proposed openstack/nova master: Add `hide_hypervisor_id` flavor extra_spec  https://review.openstack.org/55586120:06
*** itlinux has joined #openstack-nova20:07
*** hemna_ has joined #openstack-nova20:07
*** itlinux has quit IRC20:09
*** jroll has quit IRC20:09
*** tesseract has quit IRC20:09
*** jroll has joined #openstack-nova20:10
*** r-daneel has quit IRC20:11
*** pchavva1 has quit IRC20:13
mlavallerybridges: yeah, you are not getting the uuid attribute from the API. If you look at the response in http://paste.openstack.org/show/710244/, I get a header with the API  version:  X-OpenStack-Nova-API-Version: 2.60. Yours doesn't even have that header20:14
*** sidx64 has quit IRC20:14
*** AlexeyAbashkin has joined #openstack-nova20:14
jgwentworthmlavalle: yeah, I think they have a wrong (old) url for nova in their service catalog, /v2 (does not support microversions) where it should be /v2.120:15
jrollyep20:17
*** AlexeyAbashkin has quit IRC20:18
*** dave-mccowan has joined #openstack-nova20:19
*** yassine has quit IRC20:19
*** sidx64 has joined #openstack-nova20:20
*** pchavva has quit IRC20:20
*** yassine has joined #openstack-nova20:25
openstackgerritSurya Seetharaman proposed openstack/nova master: Add disabled option to create_cell command  https://review.openstack.org/55541720:26
openstackgerritSurya Seetharaman proposed openstack/nova master: Modify nova-manage cell_v2 list_cells to display "disabled" column  https://review.openstack.org/55541520:26
openstackgerritSurya Seetharaman proposed openstack/nova master: Add --enable and --disable options to  nova-manage update_cell  https://review.openstack.org/55541620:27
*** r-daneel has joined #openstack-nova20:29
openstackgerritSurya Seetharaman proposed openstack/nova master: Allow scheduling only to enabled cells (Filter Scheduler)  https://review.openstack.org/55052720:30
*** jmlowe has quit IRC20:31
jgwentworthfried_rice, superdan: I was looking at this review and it says that the powervm driver capabilities will be dynamic but I notice none of the other virt drivers have dynamic capabilities. would that not be problematic at all if the driver can change its capabilities on-the-fly? as far as the end user's experience/expectation? https://review.openstack.org/#/c/547169/3/nova/virt/powervm/driver.py@5520:32
*** _ix has joined #openstack-nova20:33
jgwentworthbecause I thought usually we advertise those things through the hypervisor matrix doc20:34
*** cdent has quit IRC20:35
superdanjgwentworth: I don't think it would be a problem necessarily,20:37
superdanif we're updating traits in placement20:37
openstackgerritSurya Seetharaman proposed openstack/nova master: Allow scheduling only to enabled cells (Filter Scheduler)  https://review.openstack.org/55052720:37
superdanyou restart a compute, it has a new libvirt version, exposes some new feature, tells placement, and suddenly things can boot there needing that feature20:37
jgwentworthokay, I see20:37
superdanmost of our capabilities have been rather static thus far, but that's just because they're like "have they implemented resize yet" sort of things I think20:38
*** sidx64_ has joined #openstack-nova20:38
jgwentworththanks20:40
*** sidx64 has quit IRC20:41
openstackgerritEric Berglund proposed openstack/nova master: WIP: Resize  https://review.openstack.org/55358320:47
*** jmlowe has joined #openstack-nova20:52
*** awaugama has quit IRC20:52
*** danpawlik has joined #openstack-nova20:52
*** danpawlik has quit IRC20:54
*** yassine has quit IRC20:56
*** yamamoto has joined #openstack-nova21:00
*** yamamoto has quit IRC21:06
fried_ricejgwentworth: Yuh, what superdan said.  In this case, it's "dynamic" only per start of the compute service, based on which disk driver you picked.21:10
*** fragatina has joined #openstack-nova21:11
openstackgerritJulia Kreger proposed openstack/nova master: Add microversion to ironic client wrapper call  https://review.openstack.org/55476221:11
jgwentworthfried_rice: ack21:12
*** hongbin has quit IRC21:14
openstackgerritMerged openstack/nova master: Add functional regression test for bug 1746509  https://review.openstack.org/55509221:15
openstackbug 1746509 in OpenStack Compute (nova) pike "TypeError: Can't upgrade a READER transaction to a WRITER mid-transaction" [High,In progress] https://launchpad.net/bugs/1746509 - Assigned to melanie witt (melwitt)21:15
*** edmondsw has quit IRC21:17
rybridgesmlavalle: jgwentworth: Ya it was the URL. The problem is there are no errors anywhere. The logs do not warn us about the fact that it cannot instantiate a client with a microversion b/c the url is not pointing to 2.1 (like it would on the CLI). Also there is no error or stack trace when we try to reference aggregate.uuid which does not exist. Everything just silently fails which makes it extremely21:20
rybridgesdifficult to debug. We thought it was a bug at first because this was really strange behavior21:20
*** moshele has quit IRC21:21
jgwentworthrybridges: aggregate.uuid coming back from the novaclient python bindings? yeah, I suspect that no one has run into this + proposed novaclient patches to enhance the warnings/errors21:23
*** lpetrut has quit IRC21:26
mriedempresumably there are errors in the neutron logs21:27
mriedemwhich is the client in this case21:27
*** esberglu has quit IRC21:28
mriedemcalling aggregate.uuid on the Aggregate object from novaclient would result in an AttributeError21:28
mriedemand all of that should be barfed into the neutron logs21:28
openstackgerritMerged openstack/nova master: Move _make_instance_list call outside of DB transaction context  https://review.openstack.org/55509321:29
mlavallerybridges: agree with jgwentworth, it is a bug. My assumption when writing the code was that the following was going to take care of the API version: https://github.com/openstack/neutron/blob/stable/ocata/neutron/services/segments/plugin.py#L15921:29
*** lpetrut has joined #openstack-nova21:30
*** bnemec is now known as beekneemech21:32
rybridgesmriedem: Attribute errors were not printed at all in our logs. No warnings either. Nothing. I was tailing nova-api, placement, neutron server and all of the agent logs on our hypervisors and at no point was there ever any error or anything. That is why I came here for help. If there had been anything in the logs I would have been able to solve it pretty easily i think.21:32
jgwentworthholy crap, I think that's the first time my patches have ever merged without CI issues21:32
openstackgerritSurya Seetharaman proposed openstack/nova master: Allow scheduling only to enabled cells (Filter Scheduler)  https://review.openstack.org/55052721:33
*** sidx64_ has quit IRC21:35
*** wolverineav has joined #openstack-nova21:36
mriedemrybridges: ok, i don't know how that's possible, because http://paste.openstack.org/show/710652/21:42
mriedemanywho21:43
openstackgerritmelanie witt proposed openstack/nova master: Migrate tempest-dsvm-multinode-live-migration job in-tree  https://review.openstack.org/55594521:43
openstackgerritMerged openstack/nova master: trivial: Resolve 'oslo.context' deprecation warnings  https://review.openstack.org/53282221:47
openstackgerritmelanie witt proposed openstack/nova master: Migrate tempest-dsvm-multinode-live-migration job in-tree  https://review.openstack.org/55594521:55
*** dave-mccowan has quit IRC21:57
*** burt has quit IRC22:00
*** _ix has quit IRC22:01
*** _ix has joined #openstack-nova22:02
*** yamamoto has joined #openstack-nova22:02
*** gouthamr has joined #openstack-nova22:03
jgwentworthmriedem: queens backport is ready2rock https://review.openstack.org/#/c/55591422:04
*** yamamoto has quit IRC22:08
*** tssurya has quit IRC22:10
*** tssurya has joined #openstack-nova22:12
*** tssurya has quit IRC22:12
*** tssurya has joined #openstack-nova22:12
openstackgerritMatt Riedemann proposed openstack/nova master: Teardown networking when rolling back live migration even if shared disk  https://review.openstack.org/55548122:24
openstackgerritMatt Riedemann proposed openstack/nova master: DRY up test_rollback_live_migration_set_migration_status  https://review.openstack.org/55548922:24
openstackgerritMatt Riedemann proposed openstack/nova master: Add check if neutron "binding-extended" extension is available  https://review.openstack.org/52354822:24
openstackgerritMatt Riedemann proposed openstack/nova master: Add code to bind a port against a dest host during live migration  https://review.openstack.org/52360422:24
openstackgerritMatt Riedemann proposed openstack/nova master: Add VIFMigrateData object for live migration  https://review.openstack.org/51542322:24
openstackgerritMatt Riedemann proposed openstack/nova master: WIP: libvirt: use dest host vif migrate details for live migration  https://review.openstack.org/55137022:24
openstackgerritMatt Riedemann proposed openstack/nova master: WIP: Port binding based on events during live migration  https://review.openstack.org/43487022:24
openstackgerritMatt Riedemann proposed openstack/nova master: Add "delete_port_binding" network API method  https://review.openstack.org/55217022:24
openstackgerritMatt Riedemann proposed openstack/nova master: compute: use port binding extended API during live migration  https://review.openstack.org/55137122:24
openstackgerritMatt Riedemann proposed openstack/nova master: conductor: use port binding extended API in during live migrate  https://review.openstack.org/52253722:24
openstackgerritMatt Riedemann proposed openstack/nova master: WIP: Turn on new port binding extended live migrate flow  https://review.openstack.org/55217322:24
openstackgerritMatt Riedemann proposed openstack/nova master: Add "activate_port_binding" neutron API method  https://review.openstack.org/55594722:24
*** liverpooler has quit IRC22:32
mriedemconsider them rocked22:33
*** figleaf is now known as edleafe22:34
*** EmilienM has quit IRC22:34
jgwentworth\o/22:35
*** EmilienM has joined #openstack-nova22:36
*** slagle has joined #openstack-nova22:37
* fried_rice has found superdan patches to -1^W review22:41
*** r-daneel has quit IRC22:43
jgwentworthmy patch to move the live migration job in-tree failed the in-tree job but not the legacy old same job \:|22:44
openstackgerritOpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements  https://review.openstack.org/55594922:44
jgwentworthNoValidHost22:44
*** chyka_ has quit IRC22:44
*** rama_y has quit IRC22:46
jgwentworthHost filter ignoring hosts: ubuntu-xenial-inap-mtl01-000316587922:50
jgwentworthhmm22:50
mriedemjgwentworth: add me and i can look on monday22:52
*** mriedem is now known as mriedem_afk22:52
jgwentworththank ye22:52
*** david-lyle has quit IRC22:52
*** rama_y has joined #openstack-nova22:55
*** _ix has quit IRC22:55
*** gouthamr has quit IRC23:03
*** yamamoto has joined #openstack-nova23:04
*** lpetrut has quit IRC23:05
*** claudiub has quit IRC23:08
*** artom has quit IRC23:08
SpazmoticMorning folks23:09
*** yassine has joined #openstack-nova23:09
*** yamamoto has quit IRC23:10
* fried_rice waves at Spazmotic23:14
fried_riceIs it... Saturday morning for you?23:14
SpazmoticFriday Evening.. Night shift hours :)23:14
fried_ricemm, UGT morning, mahbad.23:14
SpazmoticI wake up just in time to watch everyone head off for the weekend and I guard this room all weekend :p23:15
*** yamahata has quit IRC23:16
*** tssurya has quit IRC23:20
*** suresh12 has quit IRC23:23
*** wolverineav has quit IRC23:24
*** wolverineav has joined #openstack-nova23:24
*** wolverineav has joined #openstack-nova23:25
*** suresh12 has joined #openstack-nova23:27
*** wolverineav has quit IRC23:30
*** wolverineav has joined #openstack-nova23:32
*** liusheng has quit IRC23:32
*** liusheng has joined #openstack-nova23:33
*** david-lyle has joined #openstack-nova23:50
*** felipemonteiro__ has quit IRC23:52
*** sdague has quit IRC23:53
*** jgwentworth is now known as melwitt23:54
*** mriedem_afk has quit IRC23:56
*** Swami has quit IRC23:59

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