Friday, 2018-06-01

*** inara has quit IRC00:03
*** shaohe_feng has quit IRC00:05
*** shaohe_feng has joined #openstack-nova00:06
*** amotoki has quit IRC00:15
*** shaohe_feng has quit IRC00:15
*** inara has joined #openstack-nova00:15
*** hiro-kobayashi has joined #openstack-nova00:18
*** shaohe_feng has joined #openstack-nova00:20
*** r-daneel has joined #openstack-nova00:23
*** r-daneel has quit IRC00:23
*** cdent has quit IRC00:23
*** shaohe_feng has quit IRC00:25
*** shaohe_feng has joined #openstack-nova00:26
*** tianhui_ has joined #openstack-nova00:27
*** tianhui has quit IRC00:29
*** shaohe_feng has quit IRC00:36
*** masuberu has quit IRC00:37
*** amotoki has joined #openstack-nova00:38
*** shaohe_feng has joined #openstack-nova00:38
*** r-daneel has joined #openstack-nova00:42
openstackgerritwanghongtao proposed openstack/nova master: Fix the metadata re to match the unicode  https://review.openstack.org/53623600:43
*** links has joined #openstack-nova00:44
*** shaohe_feng has quit IRC00:46
*** shaohe_feng has joined #openstack-nova00:47
*** amotoki has quit IRC00:47
*** Dinesh_Bhor has joined #openstack-nova00:50
*** shaohe_feng has quit IRC00:56
*** shaohe_feng has joined #openstack-nova00:57
*** liuyulong has joined #openstack-nova00:58
*** harlowja has quit IRC00:58
*** phuongnh has joined #openstack-nova00:59
*** slaweq has joined #openstack-nova01:01
*** slaweq has quit IRC01:06
*** masber has joined #openstack-nova01:06
*** shaohe_feng has quit IRC01:06
*** jichen has joined #openstack-nova01:09
*** shaohe_feng has joined #openstack-nova01:09
*** tiendc has joined #openstack-nova01:09
*** r-daneel has quit IRC01:09
*** zhaochao has joined #openstack-nova01:14
*** lifeless has quit IRC01:15
*** shaohe_feng has quit IRC01:17
*** gyankum has joined #openstack-nova01:18
*** masuberu has joined #openstack-nova01:18
*** trungnv_ has quit IRC01:20
*** trungnv has joined #openstack-nova01:20
*** masber has quit IRC01:22
*** Tom-Tom has joined #openstack-nova01:23
*** shaohe_feng has joined #openstack-nova01:27
*** Tom-Tom has quit IRC01:28
*** Tom-Tom has joined #openstack-nova01:29
*** itlinux has joined #openstack-nova01:30
*** shaohe_feng has quit IRC01:37
*** itlinux has quit IRC01:38
*** shaohe_feng has joined #openstack-nova01:38
*** itlinux has joined #openstack-nova01:42
*** markvoelker has joined #openstack-nova01:44
*** itlinux has quit IRC01:45
*** shaohe_feng has quit IRC01:47
*** markvoelker has quit IRC01:49
*** shaohe_feng has joined #openstack-nova01:49
*** itlinux has joined #openstack-nova01:52
*** edmondsw has quit IRC01:54
*** edmondsw has joined #openstack-nova01:55
*** shaohe_feng has quit IRC01:58
*** hongbin has joined #openstack-nova01:58
*** lifeless has joined #openstack-nova01:58
*** shaohe_feng has joined #openstack-nova01:59
openstackgerrittianhui proposed openstack/nova master: Fix bug to api-ref  https://review.openstack.org/57137501:59
*** edmondsw has quit IRC01:59
*** amotoki has joined #openstack-nova02:02
*** shaohe_feng has quit IRC02:08
*** shaohe_feng has joined #openstack-nova02:09
*** lifeless_ has joined #openstack-nova02:14
*** lifeless has quit IRC02:14
*** suresh12 has joined #openstack-nova02:17
*** shaohe_feng has quit IRC02:18
*** shaohe_feng has joined #openstack-nova02:20
*** fragatina has quit IRC02:21
*** suresh12 has quit IRC02:22
*** fragatina has joined #openstack-nova02:24
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Fix invalid raise in test_compute_mgr  https://review.openstack.org/57161002:25
*** fragatin_ has joined #openstack-nova02:26
*** fragatin_ has quit IRC02:27
openstackgerritMerged openstack/nova stable/queens: libvirt: Skip fetching the virtual size of block devices  https://review.openstack.org/57142502:27
*** fragatina has quit IRC02:28
*** shaohe_feng has quit IRC02:28
*** shaohe_feng has joined #openstack-nova02:29
*** yamahata has quit IRC02:35
*** psachin has joined #openstack-nova02:36
*** fragatina has joined #openstack-nova02:38
*** shaohe_feng has quit IRC02:39
*** shaohe_feng has joined #openstack-nova02:41
*** mordred has quit IRC02:41
*** fragatina has quit IRC02:42
*** vladikr has quit IRC02:47
*** shaohe_feng has quit IRC02:49
*** shaohe_feng has joined #openstack-nova02:52
*** mordred has joined #openstack-nova02:54
*** vladikr has joined #openstack-nova02:59
*** janki has joined #openstack-nova02:59
*** shaohe_feng has quit IRC02:59
*** shaohe_feng has joined #openstack-nova03:01
*** annp has joined #openstack-nova03:03
*** nicolasbock has quit IRC03:04
*** itlinux has quit IRC03:06
*** shaohe_feng has quit IRC03:09
*** masuberu has quit IRC03:12
*** shaohe_feng has joined #openstack-nova03:13
*** fragatina has joined #openstack-nova03:16
*** fragatina has quit IRC03:16
*** fragatina has joined #openstack-nova03:17
*** shaohe_feng has quit IRC03:20
*** shaohe_feng has joined #openstack-nova03:23
*** shaohe_feng has quit IRC03:30
*** shaohe_feng has joined #openstack-nova03:31
*** zcorneli is now known as zcorneli_afk03:34
*** larsks has quit IRC03:34
*** tiendc has quit IRC03:35
*** larsks has joined #openstack-nova03:35
*** tiendc has joined #openstack-nova03:35
*** slaweq has joined #openstack-nova03:38
*** vladikr has quit IRC03:38
*** vladikr has joined #openstack-nova03:39
*** Tom-Tom_ has joined #openstack-nova03:39
*** edmondsw has joined #openstack-nova03:40
*** obre_ has joined #openstack-nova03:40
*** shaohe_feng has quit IRC03:40
*** shaohe_feng has joined #openstack-nova03:41
*** Tom-Tom has quit IRC03:42
*** EmilienM_ has joined #openstack-nova03:43
*** edmondsw has quit IRC03:44
*** lifeless_ has quit IRC03:44
*** sq4ind_ has quit IRC03:44
*** dtruong_ has quit IRC03:44
*** ircuser-1 has quit IRC03:44
*** aloga has quit IRC03:44
*** tommylikehu has quit IRC03:44
*** obre has quit IRC03:44
*** idlemind has quit IRC03:44
*** McNinja has quit IRC03:44
*** StevenK has quit IRC03:44
*** betherly has quit IRC03:44
*** andrewbogott has quit IRC03:44
*** coreycb has quit IRC03:44
*** ajo has quit IRC03:44
*** jbryce has quit IRC03:44
*** icey has quit IRC03:44
*** karlamrhein has quit IRC03:44
*** EmilienM has quit IRC03:44
*** tristanC has quit IRC03:44
*** EmilienM_ is now known as EmilienM03:44
*** EmilienM has quit IRC03:46
*** EmilienM has joined #openstack-nova03:46
*** slaweq has quit IRC03:47
*** toabctl has quit IRC03:47
*** udesale has joined #openstack-nova03:48
*** toabctl has joined #openstack-nova03:49
*** shaohe_feng has quit IRC03:50
*** shaohe_feng has joined #openstack-nova03:54
*** fragatina has quit IRC03:57
*** shaohe_feng has quit IRC04:01
*** shaohe_feng has joined #openstack-nova04:01
*** vladikr has quit IRC04:03
*** vladikr has joined #openstack-nova04:03
*** hongbin has quit IRC04:09
*** shaohe_feng has quit IRC04:11
*** shaohe_feng has joined #openstack-nova04:12
*** harlowja has joined #openstack-nova04:17
*** masber has joined #openstack-nova04:18
openstackgerritMerged openstack/nova master: libvirt: configure trust mode for vfs  https://review.openstack.org/45851404:19
*** harlowja has quit IRC04:20
*** itlinux has joined #openstack-nova04:20
*** shaohe_feng has quit IRC04:21
*** shaohe_feng has joined #openstack-nova04:22
*** vladikr has quit IRC04:23
*** vladikr has joined #openstack-nova04:23
openstackgerritVishakha Agarwal proposed openstack/python-novaclient master: No requirement of –all-tenants while listing servers  https://review.openstack.org/56909004:23
openstackgerritVishakha Agarwal proposed openstack/python-novaclient master: No requirement of –all-tenants while listing servers  https://review.openstack.org/56909004:25
*** shaohe_feng has quit IRC04:31
*** shaohe_feng has joined #openstack-nova04:33
*** shaohe_feng has quit IRC04:42
*** shaohe_feng has joined #openstack-nova04:42
*** abhishekk has joined #openstack-nova04:48
*** AlexeyAbashkin has joined #openstack-nova04:49
*** gyee has quit IRC04:51
*** shaohe_feng has quit IRC04:52
*** Alexey_Abashkin has joined #openstack-nova04:52
*** shaohe_feng has joined #openstack-nova04:53
*** AlexeyAbashkin has quit IRC04:53
*** Alexey_Abashkin is now known as AlexeyAbashkin04:53
*** liuyulong_ has joined #openstack-nova04:56
*** liuyulong has quit IRC04:59
*** Dinesh_Bhor has quit IRC05:00
*** shaohe_feng has quit IRC05:02
*** shaohe_feng has joined #openstack-nova05:03
*** zcorneli_afk has quit IRC05:08
*** slaweq has joined #openstack-nova05:11
*** itlinux has quit IRC05:11
*** shaohe_feng has quit IRC05:12
*** masber has quit IRC05:13
*** shaohe_feng has joined #openstack-nova05:14
*** slaweq has quit IRC05:15
*** sridharg has joined #openstack-nova05:15
*** suresh12 has joined #openstack-nova05:18
*** masber has joined #openstack-nova05:18
*** masuberu has joined #openstack-nova05:19
*** AlexeyAbashkin has quit IRC05:22
*** suresh12 has quit IRC05:23
*** shaohe_feng has quit IRC05:23
*** masber has quit IRC05:23
*** markvoelker has joined #openstack-nova05:24
*** shaohe_feng has joined #openstack-nova05:25
*** edmondsw has joined #openstack-nova05:28
*** moshele has joined #openstack-nova05:28
*** slaweq has joined #openstack-nova05:31
*** Dinesh_Bhor has joined #openstack-nova05:31
*** shaohe_feng has quit IRC05:33
*** edmondsw has quit IRC05:33
*** shaohe_feng has joined #openstack-nova05:34
*** slaweq has quit IRC05:35
*** liuyulong_ is now known as liuyulong05:40
*** shaohe_feng has quit IRC05:43
*** shaohe_feng has joined #openstack-nova05:44
*** moshele has quit IRC05:49
*** kholkina has joined #openstack-nova05:50
*** fragatina has joined #openstack-nova05:52
*** shaohe_feng has quit IRC05:53
*** kholkina has quit IRC05:54
*** shaohe_feng has joined #openstack-nova05:54
*** liuyulong has quit IRC05:55
*** liuyulong_ has joined #openstack-nova05:55
*** shaohe_feng has quit IRC06:04
*** shaohe_feng has joined #openstack-nova06:05
*** ratailor has joined #openstack-nova06:07
*** mikal has quit IRC06:11
*** shaohe_feng has quit IRC06:14
*** shaohe_feng has joined #openstack-nova06:15
*** imacdonn has quit IRC06:17
*** imacdonn has joined #openstack-nova06:17
*** tiendc has quit IRC06:18
*** annp has quit IRC06:18
*** tiendc has joined #openstack-nova06:18
*** annp has joined #openstack-nova06:18
*** hiro-kobayashi has quit IRC06:19
*** lpetrut has joined #openstack-nova06:20
*** slaweq has joined #openstack-nova06:21
*** do3meli has joined #openstack-nova06:22
*** shaohe_feng has quit IRC06:24
*** shaohe_feng has joined #openstack-nova06:24
*** slaweq has quit IRC06:26
*** kholkina has joined #openstack-nova06:26
*** shaohe_feng has quit IRC06:34
*** shaohe_feng has joined #openstack-nova06:37
*** ttsiouts has joined #openstack-nova06:37
*** pcaruana has joined #openstack-nova06:40
*** alexchadin has joined #openstack-nova06:44
*** shaohe_feng has quit IRC06:45
*** shaohe_feng has joined #openstack-nova06:45
*** tiendc has quit IRC06:51
*** tiendc has joined #openstack-nova06:51
*** shaohe_feng has quit IRC06:55
*** ttsiouts has quit IRC06:55
*** shaohe_feng has joined #openstack-nova06:56
*** slaweq has joined #openstack-nova06:58
*** ttsiouts has joined #openstack-nova06:59
*** slaweq has quit IRC06:59
*** slaweq has joined #openstack-nova07:00
*** sahid has joined #openstack-nova07:01
*** damien_r has joined #openstack-nova07:04
*** jpena|off is now known as jpena07:04
*** shaohe_feng has quit IRC07:05
*** shaohe_feng has joined #openstack-nova07:06
*** lifeless has joined #openstack-nova07:07
*** tssurya has joined #openstack-nova07:07
*** rcernin has quit IRC07:08
*** amoralej|off is now known as amoralej07:09
*** alexchadin has quit IRC07:11
*** alexchadin has joined #openstack-nova07:13
*** liuyulong_ has quit IRC07:15
*** shaohe_feng has quit IRC07:15
*** liuyulong_ has joined #openstack-nova07:15
*** ccamacho has quit IRC07:16
*** ccamacho has joined #openstack-nova07:16
*** shaohe_feng has joined #openstack-nova07:17
*** yamahata has joined #openstack-nova07:18
*** ttsiouts has quit IRC07:19
*** edmondsw has joined #openstack-nova07:20
*** mvk has joined #openstack-nova07:24
*** edmondsw has quit IRC07:24
*** tesseract has joined #openstack-nova07:25
*** shaohe_feng has quit IRC07:26
*** shaohe_feng has joined #openstack-nova07:27
*** kholkina has quit IRC07:28
*** kholkina has joined #openstack-nova07:28
*** lpetrut has quit IRC07:33
openstackgerritYikun Jiang (Kero) proposed openstack/nova master: Adapt _validate_instance_group_policy to new policy model  https://review.openstack.org/57146507:34
*** Tom-Tom has joined #openstack-nova07:34
*** shaohe_feng has quit IRC07:36
*** shaohe_feng has joined #openstack-nova07:37
*** Tom-Tom_ has quit IRC07:37
*** zhaochao has quit IRC07:39
*** zhaochao has joined #openstack-nova07:40
*** icey has joined #openstack-nova07:40
*** yamahata has quit IRC07:41
*** yamahata_ has joined #openstack-nova07:41
*** shaohe_feng has quit IRC07:46
*** sq4ind_ has joined #openstack-nova07:47
*** dtruong_ has joined #openstack-nova07:47
*** ircuser-1 has joined #openstack-nova07:47
*** aloga has joined #openstack-nova07:47
*** ajo has joined #openstack-nova07:47
*** tommylikehu has joined #openstack-nova07:47
*** idlemind has joined #openstack-nova07:47
*** McNinja has joined #openstack-nova07:47
*** StevenK has joined #openstack-nova07:47
*** betherly has joined #openstack-nova07:47
*** andrewbogott has joined #openstack-nova07:47
*** coreycb has joined #openstack-nova07:47
*** jbryce has joined #openstack-nova07:47
*** karlamrhein has joined #openstack-nova07:47
*** tristanC has joined #openstack-nova07:47
*** shaohe_feng has joined #openstack-nova07:47
*** shaohe_feng has quit IRC07:56
*** shaohe_feng has joined #openstack-nova07:57
*** slaweq has quit IRC07:58
*** slaweq has joined #openstack-nova07:59
*** AlexeyAbashkin has joined #openstack-nova08:03
*** shaohe_feng has quit IRC08:07
*** shaohe_feng has joined #openstack-nova08:08
*** yamahata_ has quit IRC08:11
*** alexchadin has quit IRC08:13
*** alexchadin has joined #openstack-nova08:14
*** ttsiouts has joined #openstack-nova08:14
*** ttsiouts has quit IRC08:17
*** shaohe_feng has quit IRC08:17
*** dpawlik has joined #openstack-nova08:18
*** dpawlik has quit IRC08:18
*** gcb has quit IRC08:19
*** dpawlik has joined #openstack-nova08:19
*** shaohe_feng has joined #openstack-nova08:19
*** ttsiouts has joined #openstack-nova08:22
openstackgerritElod Illes proposed openstack/nova stable/pike: placement: Fix HTTP error generation  https://review.openstack.org/57121808:23
*** shaohe_feng has quit IRC08:27
*** liuyulong__ has joined #openstack-nova08:28
*** liuyulong_ has quit IRC08:29
*** mvk has quit IRC08:29
*** lpetrut has joined #openstack-nova08:31
*** shaohe_feng has joined #openstack-nova08:31
*** lifeless has quit IRC08:37
*** shaohe_feng has quit IRC08:37
*** mvk has joined #openstack-nova08:37
*** shaohe_feng has joined #openstack-nova08:39
*** armaan has joined #openstack-nova08:39
*** lpetrut has quit IRC08:40
*** lifeless has joined #openstack-nova08:44
*** test_ has quit IRC08:47
*** test_ has joined #openstack-nova08:47
*** vivsoni has quit IRC08:47
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: Initial change set of z/VM driver  https://review.openstack.org/52338708:47
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: Spawn and destroy function of z/VM driver  https://review.openstack.org/52765808:47
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add snapshot function  https://review.openstack.org/53424008:47
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add power actions  https://review.openstack.org/54334008:47
openstackgerritjichenjc proposed openstack/nova master: z/VM Driver: add get console output  https://review.openstack.org/54334408:48
*** shaohe_feng has quit IRC08:48
*** shaohe_feng has joined #openstack-nova08:49
*** lifeless_ has joined #openstack-nova08:52
*** lifeless has quit IRC08:52
*** phuongnh has quit IRC08:57
*** dpawlik has quit IRC08:58
*** shaohe_feng has quit IRC08:58
*** phuongnh has joined #openstack-nova08:58
*** shaohe_feng has joined #openstack-nova09:00
*** dpawlik has joined #openstack-nova09:00
*** belmoreira has joined #openstack-nova09:01
*** gongysh has joined #openstack-nova09:04
*** edmondsw has joined #openstack-nova09:08
*** shaohe_feng has quit IRC09:08
*** shaohe_feng has joined #openstack-nova09:09
*** phuongnh has quit IRC09:12
*** tidwellr has joined #openstack-nova09:13
*** edmondsw has quit IRC09:13
*** do3meli has left #openstack-nova09:14
*** janki has quit IRC09:17
*** tidwellr has quit IRC09:18
*** shaohe_feng has quit IRC09:18
openstackgerritjichenjc proposed openstack/nova master: not reraise DiskNotFound if instance is resized  https://review.openstack.org/57141009:19
*** vivsoni has joined #openstack-nova09:20
*** gongysh has quit IRC09:22
*** shaohe_feng has joined #openstack-nova09:23
*** Dinesh_Bhor has quit IRC09:25
sahidjaypipes: hello, if I can ask you, I think we made with matt some good progress with the trsuted-vf feature09:26
sahidhttps://review.openstack.org/#/q/topic:bp/sriov-trusted-vfs+(status:open+OR+status:merged)09:26
sahidcan you have a look when you have a moment09:26
*** yamamoto has quit IRC09:27
*** udesale_ has joined #openstack-nova09:28
*** shaohe_feng has quit IRC09:29
*** Dinesh_Bhor has joined #openstack-nova09:29
*** liuyulong_ has joined #openstack-nova09:30
*** shaohe_feng has joined #openstack-nova09:30
*** udesale has quit IRC09:30
*** udesale_ has quit IRC09:31
*** udesale has joined #openstack-nova09:32
*** liuyulong_ has quit IRC09:33
*** liuyulong__ has quit IRC09:33
*** yamamoto has joined #openstack-nova09:33
*** ttsiouts has quit IRC09:33
*** lpetrut has joined #openstack-nova09:33
*** mvk has quit IRC09:33
*** corvus has quit IRC09:33
*** corvus has joined #openstack-nova09:34
*** liuyulong has joined #openstack-nova09:34
*** mvk has joined #openstack-nova09:34
*** Luzi has joined #openstack-nova09:35
*** alexchadin has quit IRC09:38
*** shaohe_feng has quit IRC09:39
*** shaohe_feng has joined #openstack-nova09:40
*** Dinesh_Bhor has quit IRC09:40
*** mvk has quit IRC09:42
openstackgerritStephen Finucane proposed openstack/nova-specs master: Add 'numa-aware-vswitches' spec  https://review.openstack.org/54129009:42
*** mvk has joined #openstack-nova09:42
*** ttsiouts has joined #openstack-nova09:44
*** shaohe_feng has quit IRC09:49
*** shaohe_feng has joined #openstack-nova09:50
*** ispp has joined #openstack-nova09:54
*** damien_r has quit IRC09:55
*** mgoddard has joined #openstack-nova09:56
*** damien_r has joined #openstack-nova09:56
*** jpena is now known as jpena|off09:58
sahidjangutter: if you can address the last comment https://review.openstack.org/#/c/570959/ I will +2 your patch so when sean is comming back that will be approved09:58
*** liuyulong_ has joined #openstack-nova09:59
*** shaohe_feng has quit IRC09:59
*** liuyulong has quit IRC10:00
*** udesale_ has joined #openstack-nova10:01
*** ttsiouts has quit IRC10:01
janguttersahid: thanks! I'm happy to whack that. But, check the nova patches out for another wrinkle, it seems this route might only be useful for some very esoteric cases and not be needed after all.10:02
*** shaohe_feng has joined #openstack-nova10:03
*** udesale has quit IRC10:03
*** jichen has quit IRC10:04
*** annp has quit IRC10:08
*** dpawlik has quit IRC10:09
*** shaohe_feng has quit IRC10:10
sahidjangutter: ok will look at that10:10
*** shaohe_feng has joined #openstack-nova10:11
*** ispp has quit IRC10:16
*** shaohe_feng has quit IRC10:20
*** shaohe_feng has joined #openstack-nova10:21
*** amoralej is now known as amoralej|off10:29
*** yamamoto has quit IRC10:30
*** shaohe_feng has quit IRC10:30
*** abhishekk has quit IRC10:31
*** shaohe_feng has joined #openstack-nova10:32
*** Tom-Tom has quit IRC10:38
*** Tom-Tom has joined #openstack-nova10:38
*** bkopilov_ has quit IRC10:39
*** lpetrut has quit IRC10:40
*** shaohe_feng has quit IRC10:40
*** shaohe_feng has joined #openstack-nova10:41
*** Tom-Tom has quit IRC10:43
*** janki has joined #openstack-nova10:49
*** yamamoto has joined #openstack-nova10:49
*** tbachman has quit IRC10:51
*** shaohe_feng has quit IRC10:51
*** shaohe_feng has joined #openstack-nova10:53
*** nicolasbock has joined #openstack-nova10:55
*** edmondsw has joined #openstack-nova10:56
*** Tom-Tom has joined #openstack-nova10:57
*** edmondsw has quit IRC11:01
*** shaohe_feng has quit IRC11:01
*** Tom-Tom has quit IRC11:02
*** shaohe_feng has joined #openstack-nova11:03
*** vivsoni has quit IRC11:03
*** markvoelker has quit IRC11:05
*** armaan has quit IRC11:06
*** ttsiouts has joined #openstack-nova11:06
*** armaan has joined #openstack-nova11:06
*** armaan has quit IRC11:09
*** armaan has joined #openstack-nova11:09
*** yamamoto has quit IRC11:10
*** khappone has joined #openstack-nova11:11
*** khappone_ has quit IRC11:11
*** shaohe_feng has quit IRC11:11
*** markvoelker has joined #openstack-nova11:11
*** shaohe_feng has joined #openstack-nova11:12
*** janki has quit IRC11:12
*** yamamoto has joined #openstack-nova11:12
*** udesale__ has joined #openstack-nova11:12
*** udesale_ has quit IRC11:15
*** ispp has joined #openstack-nova11:15
*** brad[] has quit IRC11:15
*** armaan has quit IRC11:15
*** yamamoto has quit IRC11:16
*** brad[] has joined #openstack-nova11:16
*** armaan has joined #openstack-nova11:16
*** ttsiouts has quit IRC11:16
*** bkopilov_ has joined #openstack-nova11:16
*** ttsiouts has joined #openstack-nova11:18
*** udesale__ has quit IRC11:18
*** shaohe_feng has quit IRC11:21
*** shaohe_feng has joined #openstack-nova11:24
openstackgerritChen proposed openstack/nova master: WIP  https://review.openstack.org/57147211:25
*** tiendc has quit IRC11:29
*** test_ has quit IRC11:30
*** GonZo2000 has joined #openstack-nova11:31
*** GonZo2000 has quit IRC11:31
*** GonZo2000 has joined #openstack-nova11:31
*** shaohe_feng has quit IRC11:32
*** shaohe_feng has joined #openstack-nova11:33
*** GonZo2000 has quit IRC11:39
*** GonZo2000 has joined #openstack-nova11:42
*** GonZo2000 has quit IRC11:42
*** GonZo2000 has joined #openstack-nova11:42
*** shaohe_feng has quit IRC11:42
*** shaohe_feng has joined #openstack-nova11:44
*** markvoelker has quit IRC11:48
*** markvoelker_ has joined #openstack-nova11:48
*** bnemec has quit IRC11:50
*** bnemec has joined #openstack-nova11:51
*** shaohe_feng has quit IRC11:52
*** shaohe_feng has joined #openstack-nova11:53
*** slaweq has quit IRC11:53
*** slaweq has joined #openstack-nova11:54
*** GonZo2000 has quit IRC12:01
*** shaohe_feng has quit IRC12:02
*** shaohe_feng has joined #openstack-nova12:04
*** tbachman has joined #openstack-nova12:04
*** do3meli has joined #openstack-nova12:05
*** ttsiouts has quit IRC12:05
*** do3meli has left #openstack-nova12:07
*** ispp has quit IRC12:07
*** jmlowe has quit IRC12:08
*** tbachman has quit IRC12:09
*** ispp has joined #openstack-nova12:10
*** edmondsw has joined #openstack-nova12:11
openstackgerritMerged openstack/nova master: libvirt:  add vf_trusted field for network metadata  https://review.openstack.org/56634312:12
*** armaan has quit IRC12:12
*** shaohe_feng has quit IRC12:13
*** armaan has joined #openstack-nova12:13
*** edleafe is now known as figleaf12:14
*** yamamoto has joined #openstack-nova12:14
*** shaohe_feng has joined #openstack-nova12:15
openstackgerritMerged openstack/nova master: metadata: add vf_trusted field to device metadata  https://review.openstack.org/56634412:16
*** tssurya is now known as sususuryashines12:16
*** tbachman has joined #openstack-nova12:17
*** hoonetorg has quit IRC12:18
*** mriedem has joined #openstack-nova12:22
*** shaohe_feng has quit IRC12:23
*** markvoelker_ has quit IRC12:23
*** slaweq has quit IRC12:25
*** markvoelker has joined #openstack-nova12:25
*** slaweq has joined #openstack-nova12:25
*** shaohe_feng has joined #openstack-nova12:26
*** dpawlik has joined #openstack-nova12:28
*** dpawlik has quit IRC12:32
*** shaohe_feng has quit IRC12:33
*** shaohe_feng has joined #openstack-nova12:37
*** alexchadin has joined #openstack-nova12:38
*** ratailor has quit IRC12:38
*** zhaochao has quit IRC12:38
*** lyan_ has joined #openstack-nova12:39
*** dpawlik has joined #openstack-nova12:42
*** dpawlik has quit IRC12:42
*** dpawlik has joined #openstack-nova12:43
*** shaohe_feng has quit IRC12:43
*** shaohe_feng has joined #openstack-nova12:44
mriedemthe trusted vf series just has one remaining patch https://review.openstack.org/#/c/458820/12:44
mriedemand it's pretty simple12:45
*** slaweq has quit IRC12:47
*** slaweq has joined #openstack-nova12:47
*** slaweq has quit IRC12:48
*** slaweq has joined #openstack-nova12:49
*** wolverineav has joined #openstack-nova12:51
*** shaohe_feng has quit IRC12:54
*** shaohe_feng has joined #openstack-nova12:54
*** eharney has joined #openstack-nova12:56
*** munimeha1 has joined #openstack-nova12:59
mriedemstephenfin: artom: i've got some questions in the numa-aware vswitch, new ones about live migration support https://review.openstack.org/#/c/541290/13:00
artommriedem, dammit, I was hoping I'd get to avoid that massive thing ;)13:03
artomNah, I'll check it out, see if I can be useful13:03
mriedemstephenfin: i think for any move operation, we'll have to modify the request spec to include the current numa-aware interface information from the instance info cache so the NUMATopologyFilter can pick a proper destination host13:04
*** shaohe_feng has quit IRC13:04
stephenfinmriedem: Yeah, I was planning to just build one of those InstanceNUMANetworks objects from instance info cache13:04
mriedemwhich kind of makes me wonder, if you can't attach numa-aware interfaces to a running instance, then the instance info_cache should match the original request spec's requested_networks, and then i wonder why we wouldn't persist it for move operations13:04
mriedemdansmith: ^13:05
stephenfinmriedem: You can attach them - you just won't get NUMA affinity13:05
mriedemare you guys all on happy time red hat meeting fun hour right now?13:05
mriedemstephenfin: ok so if i want to attach new numa-aware instances with affinity, i'd have to do that and then resize my instance to get it to move13:05
stephenfinI mean, I guess we could enforce that if we wanted to but the spec is already too big for its own good. I want to land _something_ :)13:06
*** shaohe_feng has joined #openstack-nova13:06
stephenfinmriedem: At present, yes13:06
* stephenfin thinks he said "this will be addressed in the future"13:06
*** gibi is now known as giblet13:06
stephenfinmriedem: https://review.openstack.org/#/c/541290/15/specs/rocky/approved/numa-aware-vswitches.rst@40513:06
stephenfingiblet: Thanks for the reminder13:06
*** stephenfin is now known as finucannot13:06
* giblet lost this week on corporate downstream crazyness13:07
mriedemfinucannot: yeah i know it says that13:07
mriedemfinucannot: i know you want to land something,13:07
mriedembut i also don't want to land a gaping hole that we don't fix for 4 years like the existing numa stuff13:08
mriedemso what does the "claim" actually do?13:09
*** pchavva has joined #openstack-nova13:09
*** trozet has joined #openstack-nova13:09
mriedemsince we won't have a claim during live migration13:09
finucannotmriedem: The claim builds the guest's NUMA topology13:09
finucannotFor that to happen, I need to have information about the networks attached to the guest13:09
finucannotFar as I can see, for a new instance the info cache is not yet populated13:10
finucannotfinucannot: Agreed on not having a gaping hole. The approach artom takes for solving live migration for NUMA should get us this almost for free, I'm guessing13:11
finucannot*mriedem:13:11
artomPassing IntanceNUMATopology as part of live_migrate_data?13:11
mriedemfinucannot: so this spec depends on artom's bp for live migration then?13:11
finucannotmriedem: Kind of but not really13:12
mriedemso you guys might want to talk about this....13:13
finucannotIt needs that spec for live migration to work, but so does everything that involves NUMA and CPU pinning13:13
mriedemi'm not familiar enough with artom's spec yet13:13
mriedemright, ok,13:13
mriedemso i think we call that out as a dependency for live migration to work, that's fine,13:13
finucannotSeeing as they're currently very much tied, much to jaypipes chagrin13:13
mriedemthe rest could go ahead with that caveat13:13
finucannotack13:13
*** shaohe_feng has quit IRC13:14
gibletfinucannot, mriedem: very similar thing will happen with the bandwidth. We need to regenerate the bandwidth request part of the request spec for all the VM move operations13:15
*** pcaruana has quit IRC13:15
mriedemgiblet: yup, i think that was called out in your spec13:16
*** shaohe_feng has joined #openstack-nova13:16
mriedemfinucannot: ok so i left some targeted things to update in your spec, then i think i'm +213:16
mriedemi just want to make sure it's written down because it's a lot of churn and w/o the list of work items we're likely to forget something13:16
finucannotYup, that's fair13:16
gibletmriedem: yes, it was13:17
mriedemgiblet: hopefully the internal churn doesn't negatively impact you13:17
gibletmriedem: and now have some TODOs in the currently proposed patches where to do those. I.e. https://review.openstack.org/#/c/567268/9/nova/compute/api.py@423413:17
*** jaypipes is now known as leakypipes13:18
gibletmriedem: there will be nice rebases I'm sure. But that is life :)13:18
mriedemgiblet: request spec tinkering should happen in conductor13:18
gibletmriedem: OK, then 'badly placed TODOs' :) I can push those up in the call chain13:18
leakypipesfinucannot: well remembered.13:18
gibletmriedem: thanks for the comments in that bwm patch about my TODOs. Thanks for the pointer like 'reset_request_destinations'13:23
mriedemgiblet: i might have gotten that method name wrong13:23
gibletmriedem: I can apply AI to find the right one :)13:23
mriedemreset_forced_destinations13:23
gibletmriedem: ty13:24
mriedemha13:24
mriedemis that your new job now? AI master?13:24
mriedemtrain the machine to write your bw-aware series13:24
gibletmriedem: it is more like a wanabe hobby13:24
mriedemwell at least you have a hobby13:24
gibletmriedem: but it would be so easy just to push it to an AI13:24
*** shaohe_feng has quit IRC13:24
bauzaswarning, I'm changing my Friday nick13:25
*** bauzas is now known as PapaOurs13:25
*** mriedem is now known as hansmoleman13:25
PapaOursleakypipes: thanks for having reviewed https://review.openstack.org/#/c/557065/13:25
*** efried is now known as fried_rice13:26
*** tbachman_ has joined #openstack-nova13:26
*** shaohe_feng has joined #openstack-nova13:26
PapaOursleakypipes: as far as I understand, your strong -1 is related to the fact it's about traits and nvidia13:26
*** READ10 has joined #openstack-nova13:26
PapaOursleakypipes: but look at https://github.com/intel/gvt-linux/wiki/GVTg_Setup_Guide#51-check-mdev-module-kvmgt-only13:27
PapaOursleakypipes: mdev's supported_types is a kernel's VFIO feature13:27
*** brtknr has joined #openstack-nova13:27
sususuryashineshansmoleman: you finally got your friday nick!? :D13:27
PapaOursleakypipes: so even if only nvidia uses it, why the spec should be about nvidia ?13:27
*** armaan has quit IRC13:28
*** armaan has joined #openstack-nova13:28
*** tbachman has quit IRC13:29
*** lyan_ has quit IRC13:29
*** tbachman has joined #openstack-nova13:31
*** tbachman_ has quit IRC13:31
openstackgerritStephen Finucane proposed openstack/nova-specs master: Add 'numa-aware-vswitches' spec  https://review.openstack.org/54129013:31
*** armaan has quit IRC13:32
fried_riceWhat's ironic's nova CI called?13:33
*** markvoelker_ has joined #openstack-nova13:34
*** markvoelker has quit IRC13:34
leakypipesPapaOurs: that mdev_supported_types is nothing more than a reference to NVIDIA's product names.13:34
sususuryashinesdansmith, hansmoleman: would like your opinion on https://review.openstack.org/#/c/560042/ whenever you have the time.13:34
*** shaohe_feng has quit IRC13:35
dansmiththis sounds like a job for...13:35
*** dansmith is now known as superdan13:35
jrollfried_rice: something-ironic-something :P13:35
jrollironic-tempest-dsvm-ipa-wholedisk-bios-agent_ipmitool-tinyipa13:36
*** leakypipes is now known as MurderTheLeafBlo13:36
fried_riceoh, there it is.13:36
fried_ricethanks jroll13:36
*** jcarpentier has joined #openstack-nova13:36
jrollnp13:36
MurderTheLeafBlodamn restrictions on nick length.13:36
jrollheh13:36
*** MurderTheLeafBlo is now known as leakypipes13:36
*** jroll is now known as jrollinhatin13:36
*** shaohe_feng has joined #openstack-nova13:36
fried_riceleakypipes: DieLeafBlowerDie ought to fit13:37
*** lbragstad is now known as elbragstad13:37
*** links has quit IRC13:37
*** tbachman_ has joined #openstack-nova13:37
leakypipesfried_rice: oooh, nice.13:37
*** tbachman has quit IRC13:38
*** tbachman_ is now known as tbachman13:38
*** ispp has quit IRC13:38
*** throwsb1 has joined #openstack-nova13:39
*** armaan has joined #openstack-nova13:40
hansmolemansususuryashines: only temporary13:40
hansmolemani'm actually allergic to fun13:40
openstackgerritTsuyoshi Nagata proposed openstack/nova master: nova improvement of maximum attach volumes more than 26 vols  https://review.openstack.org/56747213:40
sususuryashineshansmoleman: :P13:41
*** jcarpentier has left #openstack-nova13:41
*** awaugama has joined #openstack-nova13:42
hansmolemanfinucannot: thanks, +213:42
hansmolemansuperdan: +2 on finucannot's numa-aware vswitch spec now https://review.openstack.org/#/c/541290/13:43
*** trozet_ has joined #openstack-nova13:43
*** dpawlik has quit IRC13:43
*** mlavalle has joined #openstack-nova13:43
finucannothansmoleman: Thanks, appreciate it13:43
PapaOursleakypipes: "you make sure the "mdev_supported_types" node with differenct vgpu type  existed(The "V#ID" represent the corresponding platform, "V4" means it  is "Broadwell" platform, "V5" means it is "Skylake" or "Kabylake"  platform)"13:45
*** shaohe_feng has quit IRC13:45
PapaOursleakypipes: unless I'm misunderstanding the above, but it's related to an Intel thing, right?13:45
*** trozet has quit IRC13:45
*** shaohe_feng has joined #openstack-nova13:46
PapaOursleakypipes: and yet again, it's a VFIO abstraction13:46
*** vladikr has quit IRC13:47
PapaOursleakypipes: why should we call it 'nvidia' even if the nvidia folks provided it ?13:47
*** vladikr has joined #openstack-nova13:47
PapaOursit's like if we would say that a libvirt feature supported by the Nova API is only a 'libvirt' one13:47
PapaOursit could be a Xen or VMWare feature if the virt driver supports it13:47
*** esberglu has joined #openstack-nova13:48
leakypipesPapaOurs: they *are* the libvirt ones.13:48
leakypipesPapaOurs: I'm not saying we should be leaking vendor details out of the user-facing API. I'm just saying when referring to "vGPU types", we should be honest about it and say what we mean, which is "the NVIDIA vendor model for this NVIDIA pGPU".13:49
hansmolemanis cdent out this week?13:49
leakypipeshansmoleman: I'm not sure. I've seen him on ML off and on. not much on IRC.13:49
figleafhansmoleman: he's at the vmware mother ship, so I'm sure his attention is spread thin13:49
hansmolemanah ok13:50
hansmolemangonna setup a 100 node fake devstack env for some scheduler perf testing, i knew he did something like this before13:50
leakypipesPapaOurs: btw, where is Bauwser? :)13:51
leakypipeshansmoleman: placecat.13:51
hansmolemani don't need to test placement13:51
leakypipeshansmoleman: https://github.com/cdent/placecat/ maybe what you were thinking?13:51
fried_ricehansmoleman: He has some fairly detailed step-by-step on his blog.  Let me know if you want me to dig that up.13:51
hansmolemanfried_rice: yeah i've seen that one before, i think i've got this, it's basically (1) fake virt driver (2) noop quota and (3) NUMBER_FAKE_NOVA_COMPUTE=x13:52
hansmolemani'm going to try and test before and after https://review.openstack.org/#/c/569247/13:52
hansmolemanwith 100 nodes, 1000 instances, 10 per node13:52
PapaOursleakypipes: but again, looks like Intel have multiple types, where each of them about an Intel platform13:53
leakypipesPapaOurs: show me. everything I see in their docs refers to NVIDIA vGPU types.13:53
superdanhansmoleman: finucannot I still have questions in there, maybe hansmoleman can clear it up for me if he gets it and I'm just slow13:53
*** artom is now known as ralphlaurent13:53
leakypipesPapaOurs: and GVT-g, GVT-d, GVT-s are not different vGPU typoes.13:54
*** ralphlaurent is now known as ralphlauren13:54
PapaOursleakypipes: tbh, I need to get an Intel GVT-g hardware13:54
ralphlaurenLook up his real name13:54
PapaOursleakypipes: GVT-g is for vGPUs13:54
PapaOursGVT-d and GVT-s are different features13:54
*** ttsiouts has joined #openstack-nova13:54
leakypipesPapaOurs: yes, I know. and I don't see any evidence that they use vGPU types for aniything other than referencing NVIDIA's vendor model names.13:54
PapaOursand Intel GVT-g for KVM is also called KVMGT13:54
leakypipesyes, I know that.13:55
*** shaohe_feng has quit IRC13:55
PapaOursleakypipes: you've seen my link ? https://github.com/intel/gvt-linux/wiki/GVTg_Setup_Guide#51-check-mdev-module-kvmgt-only13:55
*** ttsiouts has quit IRC13:56
*** r-daneel has joined #openstack-nova13:56
leakypipesPapaOurs: yes.13:56
*** shaohe_feng has joined #openstack-nova13:56
openstackgerritJan Gutter proposed openstack/os-vif master: Add multiqueue port profile for VIFGeneric  https://review.openstack.org/57095913:56
*** ttsiouts has joined #openstack-nova13:56
PapaOursPapaOurs: so, looks like to me there are multiple types for each pGPU13:57
PapaOurseven for an Intel's one13:57
leakypipes915-GVTg_V5_4 is a driver.13:57
PapaOursbecause when creating the mdev, you need to tell which type to use13:57
leakypipesIt's Not A Tumor!13:57
openstackgerritJan Gutter proposed openstack/nova master: Use vif.vif_name in _set_config_VIFGeneric  https://review.openstack.org/57146113:57
openstackgerritJan Gutter proposed openstack/nova master: Convert vrouter legacy plugging to os-vif  https://review.openstack.org/57132513:57
openstackgerritJan Gutter proposed openstack/nova master: Pass virtio multiqueue info to os-vif plugins  https://review.openstack.org/57146213:57
PapaOursleakypipes: i915-GVTg_V5_1 is one type, i915-GVTg_V5_2 is another type13:58
*** trozet_ is now known as trozet13:58
leakypipesPapaOurs: it isn't though...13:59
PapaOursfrom a VFIO arch, it is13:59
leakypipesPapaOurs: they are just trying to pidgeonhole their driver info into the NVIDIA mdev framework :(13:59
PapaOursLOL13:59
*** markvoelker_ has quit IRC14:00
superdanmdev is a linux kernel abstraction, right?14:00
leakypipesit's all a load of hardware-specific bullshit, IMHO.14:00
leakypipessuperdan: some call it that.14:00
* superdan eyerolls14:00
* leakypipes eyerolls back14:00
*** belmorei_ has joined #openstack-nova14:00
PapaOursleakypipes: I mean, I understand your point14:01
*** r-daneel has quit IRC14:01
*** ttsiouts_ has joined #openstack-nova14:01
PapaOursI'm not saying vendors don't do bullshit14:01
*** ttsiouts has quit IRC14:01
PapaOurs(heh, use of a double negative /o\)14:01
PapaOursbut, the fact is, for the good or worst, they use the VFIO mdev abstraction exactly like nvidia does14:02
*** belmoreira has quit IRC14:02
leakypipesPapaOurs: "better or worse" :)14:02
openstackgerritAndrey Volkov proposed openstack/nova master: Test Compute API in multiple cells  https://review.openstack.org/54727314:03
PapaOursleakypipes: I'm now called PapaOurs, it's making clear that I'm French now :p14:03
leakypipeswell, I can agree with you on at least one thing, PapaOurs...14:03
cfriesenPapaOors:  I thought AMD used SRIOV14:03
leakypipesPapaOurs: it certainly would be nice to afford to play with some of these things in real life.14:04
PapaOursleakypipes: that's in my todo list :)14:04
leakypipescfriesen: oh, hai Chris. welcome to our own private hell.14:04
PapaOurscfriesen: excellent point14:05
PapaOurscfriesen: if an hardware vendor doesn't use the VFIO mdev interface with its kernel driver, then sure, vGPUs aren't supported14:05
*** shaohe_feng has quit IRC14:05
*** salv-orlando has joined #openstack-nova14:06
PapaOurscfriesen: they can use a different arch, like SR-IOV, but then it's very different14:06
leakypipesI'm a mushroom cloud layin' motherf**ker.14:06
*** shaohe_feng has joined #openstack-nova14:07
* elbragstad hands leakypipes the "quote of the day" award :)14:07
cfriesenI've been following the vGPU stuff only casually, but it sure looks like a pain. :)14:07
*** alexchadin has quit IRC14:08
*** melwitt is now known as jgwentworth14:09
leakypipeselbragstad: just sayin' Vincent, I'm Superfly TNT.14:10
*** alexchadin has joined #openstack-nova14:10
*** pcaruana has joined #openstack-nova14:10
*** salv-orlando has quit IRC14:11
gibletfried_rice: I've fixed as much as I can from your comments in https://review.openstack.org/#/c/56941714:11
PapaOurscfriesen: the real question is, why a separate vendor doesn't use the kernel interface for that ?14:11
leakypipescfriesen: here's the thing... it actually *wouldn't* be a pain, IMHO, if we just called a spade a spade and carved out a vendor-specific part of the codebase for Intel and NVIDIA to dump their code into and then we required them to simply hand us a library whose sole purpose was to contain a dict, keyed by their product IDs, containing a list of standardized capabilitiies for each of their products.14:11
leakypipescfriesen: oh, and have them write meaningful, understandable documentation for their products *before* releasing them.14:12
fried_ricegiblet: ack14:12
hansmolemansuperdan: good questions, i dropped my +2 and left some replies, finucannot fyi14:12
PapaOursleakypipes: that was your second concern in my spec, and we could somehow *do* that, but looks to me that's just going to be a hecking thing to update14:12
finucannothansmoleman: (y)14:12
leakypipesPapaOurs: "heck of a thing"? :)14:12
PapaOursleakypipes: I can imagine a shit number of nvidia folks coming by nova and asking us to merge their change just for updating that module14:13
* jrollinhatin prefers hecking14:13
leakypipeshehe14:13
PapaOursleakypipes: we could do a lib tho14:13
PapaOursbut the problem remains14:13
leakypipesPapaOurs: I hope you know I'm just "pulling your chain" on your English phrases. :)14:13
leakypipesit's Friday after all.14:13
PapaOursleakypipes: and yeah, I don't disagree with you on the poor abstraction that only relies on strings that are defined by the vendor, hence not versioned14:13
PapaOursleakypipes: I don't take any offense here, no worries ;)14:14
PapaOursand again, I now officially claim the French verbage14:14
leakypipes:)14:14
PapaOursleakypipes: so, yeah, I can't argue with you on the fact types are just poorly defined by vendors14:15
*** Guest25886 has quit IRC14:15
PapaOursthe best of that is that's a mandate for keeping those type names identical across releases14:15
PapaOursso, say, if nvidia wants to rename nvidia-35 type name into something like "M60-8G-MY_SUPER-TYPE", they would be able14:16
*** shaohe_feng has quit IRC14:16
leakypipesPapaOurs: well, since they only started doing any of this back in like April last year, we'll just have to wait and see if they completely change the interface here in the next year or so. My bet is, of course they will.14:16
PapaOursbecause the kernel directly takes the names straight for the kernel module...14:16
PapaOursfroù14:16
PapaOursfrom*14:16
leakypipesI liked frou better.14:16
*** shaohe_feng has joined #openstack-nova14:16
PapaOursso, yeah, you can see me sometimes ranting on that btw.14:17
PapaOursbut back to the spec, the only abstraction we have is that poorly-defined-tho-mandatory-and-alone interface that we call 'mdev_supported_types'14:17
PapaOursgood luck with that14:17
leakypipes"standardized pointer to randomness".14:18
*** kholkina has quit IRC14:18
*** gyankum has quit IRC14:18
* leakypipes is reminded of hansmoleman's random bag of dicts.14:19
PapaOursleakypipes: that quote is awesome14:19
fried_ricegiblet: +1, nice.14:19
gibletfried_rice: thanks14:19
ralphlaurenWhere did I see a hard_dict?14:19
PapaOursleakypipes: and now, you guess why QEMU folks push back the nvidia implementation for live migration14:20
ralphlaurenI definitely saw a hard_dict somewhere14:20
PapaOursleakypipes: b/c nvidia just wants to live migrate based on foobar capabilities they solely define and expose14:20
*** tidwellr has joined #openstack-nova14:20
*** gbarros has joined #openstack-nova14:21
*** tidwellr has quit IRC14:22
PapaOursanyway, I need to drop14:22
*** tidwellr has joined #openstack-nova14:22
*** jiteka has joined #openstack-nova14:24
*** markvoelker has joined #openstack-nova14:24
*** shaohe_feng has quit IRC14:26
*** jmlowe has joined #openstack-nova14:26
*** shaohe_feng has joined #openstack-nova14:27
*** zcorneli has joined #openstack-nova14:27
*** armaan has quit IRC14:27
*** Guest25886 has joined #openstack-nova14:29
hansmolemanleakypipes: dan akroyd had a bag-o-glass, i've got a bag-o-dicts14:30
*** hoonetorg has joined #openstack-nova14:31
openstackgerritMerged openstack/nova master: network: update pci request spec to handle trusted tags  https://review.openstack.org/45882014:32
*** shaohe_feng has quit IRC14:36
*** shaohe_feng has joined #openstack-nova14:38
*** alexchadin has quit IRC14:46
*** Luzi has quit IRC14:46
*** alexchadin has joined #openstack-nova14:46
*** shaohe_feng has quit IRC14:46
*** shaohe_feng has joined #openstack-nova14:47
*** yamamoto has quit IRC14:48
*** alexchadin has quit IRC14:50
*** markvoelker has quit IRC14:52
*** yamamoto has joined #openstack-nova14:56
openstackgerritTsuyoshi Nagata proposed openstack/nova master: nova improvement of maximum attach volumes more than 26 vols  https://review.openstack.org/56747214:56
*** shaohe_feng has quit IRC14:57
*** shaohe_feng has joined #openstack-nova14:59
*** yamamoto has quit IRC15:00
*** hongbin has joined #openstack-nova15:02
*** markvoelker has joined #openstack-nova15:03
*** bpoulos has joined #openstack-nova15:04
PapaOursleakypipes: hmmm, so I looked at some GVT-g links and that one looks good https://01.org/igvt-g/blogs/wangbo85/2017/gvt-g-new-architecture-introduction-update15:05
PapaOursthey say they still use "mdev_supported_types"15:05
PapaOursleakypipes: so, I'll modify my spec for saying which hardware vendors support mdevs15:06
hansmolemanwoot another one bites the dust https://blueprints.launchpad.net/nova/+spec/sriov-trusted-vfs15:06
PapaOursie. Intel and Nvidia15:06
*** salv-orlando has joined #openstack-nova15:07
*** shaohe_feng has quit IRC15:07
fried_riceDo "we" have any interest in, or strong objections to, allowing unicode characters in metadata/extra_specs keys?15:07
*** shaohe_feng has joined #openstack-nova15:09
*** fragatina has quit IRC15:11
*** salv-orlando has quit IRC15:11
*** yamamoto has joined #openstack-nova15:11
*** fragatina has joined #openstack-nova15:12
fried_ricehansmoleman, superdan: ^  ?15:12
*** moshele has joined #openstack-nova15:13
*** liuyulong_ has quit IRC15:13
leakypipesfried_rice: 💩15:13
superdanI thought we already said no unicode there,15:13
*** liuyulong_ has joined #openstack-nova15:13
superdanbut allowed it in things like name and tag15:13
fried_ricesuperdan: Okay, where did we say that?15:13
superdanlong ago15:13
superdanduring the post-v3 API strictification15:14
superdanaka "the nova dark ages"15:14
fried_ricesuperdan: I just reviewed https://review.openstack.org/#/c/536236/ (bug 1737711).  It's not right atm, but if we're never going to allow it, I'd like to be able to shut it down so they don't go off and do a bunch of work to get it right.15:15
openstackbug 1737711 in OpenStack Compute (nova) "nova boot failed when use the chinese metadata key and value" [Undecided,In progress] https://launchpad.net/bugs/1737711 - Assigned to wanghongtao (hongtao.wang)15:15
fried_ricesuperdan: But to get it shut down, I'd like to be able to point to something that says we don't want it, and ideally, why.15:15
superdanfried_rice: ask hansmoleman I bet he remembers more (correctly) than I do15:15
superdanor maybe leakypipes does15:15
superdanhence my "I thought" hedging15:16
*** yamamoto has quit IRC15:16
*** itlinux has joined #openstack-nova15:16
*** shaohe_feng has quit IRC15:17
leakypipessuperdan: unfortunately, I don't remember much about that decision either, sorry :(15:18
*** shaohe_feng has joined #openstack-nova15:18
*** felipemonteiro_ has joined #openstack-nova15:19
hansmolemani don't either15:20
*** moshele has quit IRC15:20
hansmolemansdague likely might, but15:20
superdanyeah15:21
hansmolemanor alex or ken'ichi15:21
hansmolemanor gmann15:21
superdanam I remembering correctly that we made a point of not allowing unicode there though?15:21
*** ttsiouts_ has quit IRC15:21
openstackgerritBalazs Gibizer proposed openstack/nova master: Add bandwidth related standard resource classes  https://review.openstack.org/57084715:22
*** felipemonteiro__ has joined #openstack-nova15:22
openstackgerritBalazs Gibizer proposed openstack/nova master: Transfer port.resource_request to the scheduler  https://review.openstack.org/56726815:22
openstackgerritBalazs Gibizer proposed openstack/nova master: Send resource allocations in the port binding  https://review.openstack.org/56945915:22
superdanor do ya'll not remember one way or the other?15:22
hansmolemani don't really remember15:23
hansmolemancould have been related to how we stored that stuff in the db, but not sure15:23
*** lifeless_ has quit IRC15:23
hansmolemani'm not sure why we'd have unicode in flavor extra specs,15:24
*** lifeless has joined #openstack-nova15:24
hansmolemanthose are system-defined things that the code needs to understand15:24
hansmolemanuser metadata is fuzzy15:24
*** sususuryashines has quit IRC15:24
hansmolemanauggy had a spec related to this also i think...15:25
hansmolemanmaybe that was just case sensitivity in the db15:25
*** ttsiouts has joined #openstack-nova15:25
*** yamamoto has joined #openstack-nova15:25
*** yamamoto has quit IRC15:25
*** felipemonteiro_ has quit IRC15:25
*** suresh12 has joined #openstack-nova15:26
hansmolemanhttps://review.openstack.org/#/c/350843/15:26
hansmolemanthat was case, not unicode15:26
*** felipemonteiro__ has quit IRC15:26
*** felipemonteiro__ has joined #openstack-nova15:26
hansmolemansmcginnis: does cinder allow unicode in volume type extra specs?15:26
hansmolemanor volume metadata?15:27
smcginnishansmoleman: Hmm, I believe the values but not the keys that are set in the extra specs.15:27
smcginnishansmoleman: And I believe it is fine the the volume metadata.15:27
*** shaohe_feng has quit IRC15:27
*** sapd has joined #openstack-nova15:28
*** gbarros has quit IRC15:28
hansmolemanare you sure? https://github.com/openstack/cinder/blob/master/cinder/api/validation/parameter_types.py#L14715:29
hansmolemandoesn't look like it does15:29
*** ctrath_ has joined #openstack-nova15:29
hansmolemanhttps://github.com/openstack/cinder/blob/master/cinder/api/schemas/volume_metadata.py#L3515:29
fried_ricehansmoleman: The *key* doesn't, but the *value* does.15:29
*** shaohe_feng has joined #openstack-nova15:30
hansmolemanoh right yeah15:30
hansmolemanjust a 255 character string15:30
*** ttsiouts has quit IRC15:30
fried_riceokay, so cinder is using the same regex as nova for the key.15:30
*** ttsiouts has joined #openstack-nova15:30
*** ttsiouts has quit IRC15:31
*** sridharg has quit IRC15:31
fried_riceI don't have a sense of how these things get sprayed around in a real deploy.  Does this mean that we can't have one of those regexes be a superset of the other, because chars outside the smaller set would then break when they cross that boundary?15:31
hansmolemanfor extra specs, i would ask which specific flavor extra specs do they need unicode values15:31
hansmolemanor is it just out of tree enablement15:31
hansmolemanif it's the latter, then i care much less about this15:31
*** rajinir has joined #openstack-nova15:32
jgwentworthfwiw I don't remember any discussion about unicode metadata keys15:32
openstackgerritArtom Lifshitz proposed openstack/nova master: Refactor _build_device_metadata  https://review.openstack.org/53380415:32
openstackgerritArtom Lifshitz proposed openstack/nova master: Consider hostdev devices when building metadata  https://review.openstack.org/53380515:32
superdanfor extra_specs I think the case to be made is super weak regardless of what they way15:33
ralphlaurenfinucannot, ^^^ if you want to re-review15:33
superdanfor metadata I can imagine more realistic scenarios15:33
jgwentworthit makes sense to me that someone might want that, to be able to set keys/names in their own language15:34
*** gbarros has joined #openstack-nova15:34
jgwentworthbut yeah, not sure if there's some other gotcha that we'd hit somewhere by changing it to allow unicode15:34
fried_ricesuperdan: The bug isn't real specific about why they want it.  But jgwentworth yeah, that.15:34
superdannot sure how we signal it appropriately either.. a microversion will be frustrating as older ones would have to just omit pairs that use unicode15:35
hansmolemanfried_rice: likely because they have out of tree code that's busted15:35
superdanyup15:35
hansmolemanso i'd nack until they can give specifics15:35
*** damien_r has quit IRC15:35
fried_riceRoger wilco.15:36
fried_ricethanks guys15:36
hansmolemani'd be willing to bet Kevin_Zheng knows if we (huawei) have a need for this15:37
hansmolemanlike, maybe i need to get my chinese unicode name passed through user metadata to config drive for something running in the image15:37
hansmolemanto register with some internal system15:37
hansmolemanidk15:37
*** shaohe_feng has quit IRC15:38
PapaOurssilly question but... does cloud-init support unicode ?15:39
*** shaohe_feng has joined #openstack-nova15:39
*** belmorei_ has quit IRC15:40
*** jaosorior has quit IRC15:41
hansmolemanhttps://cloudinit.readthedocs.io/en/latest/search.html?q=unicode&check_keywords=yes&area=default15:42
hansmolemanthe answer is, shrug15:42
fried_riceMarked Incomplete asking for details: https://bugs.launchpad.net/nova/+bug/173771115:43
openstackLaunchpad bug 1737711 in OpenStack Compute (nova) "nova boot failed when use the chinese metadata key and value" [Undecided,Incomplete] - Assigned to wanghongtao (hongtao.wang)15:43
SpamapSPapaOurs: it should, if it doesn't that's a bug.15:43
*** suresh12 has quit IRC15:43
openstackgerritMatt Riedemann proposed openstack/nova master: Restrict CONF.quota.driver to DB and noop quota drivers  https://review.openstack.org/41099615:44
hansmolemanfinucannot: i made that release note update you wanted ^ if you want to just fast approve15:45
finucannothansmoleman: Done and done15:46
hansmolemanthanks15:46
mnaserso wild Friday cells v2 question: how much does latency affect operations overall?15:46
superdanmnaser: latency to the cell db? no more or less than with one cell15:47
*** jangutter has quit IRC15:47
*** jangutter has joined #openstack-nova15:47
*** ctrath_ has quit IRC15:47
mnasersuperdan: well, say you have your api in NA and a cell in .. say.. thailand.15:47
*** suresh12 has joined #openstack-nova15:47
superdanmnaser: that's probably not the best plan15:48
mnaser(nfv use case, and company has world wide presence, so i suggested 4 regions with a single cell split geographically)15:48
mnaserbut i was thrown "cells v2" at me15:48
*** shaohe_feng has quit IRC15:48
SpamapSmnaser: you'll always get the latency of the slowest round trip from api->cellbits .. so it will suffer as much as your latency varies15:48
jgwentworthmnaser: the api connects directly to cell databases, so that scenario would be slow15:48
superdanmnaser: if unified control plane is what you care about the most, then...15:48
superdanSpamapS: that's not true15:48
*** tbachman has quit IRC15:48
mnaserso the thing is, api operations isn't a big deal for them, but i don't know how much slower they'd be15:49
jgwentworthsuperdan: I think he means for a scatter-gather, yeah?15:49
mnaseraka if the value of having a unified control plane is enough to take that performance hit15:49
SpamapSWell, worst latency that has instances in the project you're listing I suppose15:49
superdanSpamapS: if you spread things evenly across cells then it will, but if you have a tenant per cell (as one example) then you'll get normal performance if you're not in one of theother cells15:49
superdanjgwentworth: yes15:50
*** shaohe_feng has joined #openstack-nova15:50
superdanmnaser: right, so relatively static workload, they just want a unified view of it, even if operations take a while, because they're infrequentish?15:50
SpamapSI didn't mean to say all operations will suffer that much15:50
mnasersuperdan: according to them, correct15:50
*** markvoelker has quit IRC15:51
superdanmnaser: yeah, so if that's the preference, that's cool. we're not as good as we should be on tolerating faults in the remote links right now,15:51
superdanmnaser: which means you're increasing your chances for things not working if one link is down, but that's on the books to improve15:51
mnaseri guess that's for them to understand as a limitation if we do take this path15:52
mnasermaybe good feedback to bring back :p15:52
superdanat least the story is on the path to improve, but yeah15:52
mnaseri'm suggesting 4 regions instead (na-east, na-west, europe, asia).. sure its not a unified control plane but still a lot better in terms of surprises we'll run into15:52
superdanyep, that's a better approach if they can tolerate it15:53
*** chyka has joined #openstack-nova15:53
hansmolemanthere are projects meant to abstract the multi-region thing https://wiki.openstack.org/wiki/Kingbird15:54
* mnaser is still waiting for fiber to be setup to get playing with cells v215:54
hansmolemanbut no idea how good those are15:54
SpamapSmnaser: those are the 4 regions we have, and we do not have a unified control plane. It's nice that they're isolated from eachother.15:54
mnaseryeah i've heard of kingbird before but it's a bit scary as a concept :p15:54
SpamapSThe only thing they share is LDAP.15:54
mnaseryeah, i was thinking share a single keystone, multiple regions in the catalog15:55
*** tbachman has joined #openstack-nova15:55
mnaserif this works out, hopefully we can share the story, what they're doing with nova is really, really cool.15:55
hansmolemanthat would be great15:56
jgwentworthbpoulos: just fyi cert validation is back in a review runway, so be on the lookout for reviews https://etherpad.openstack.org/p/nova-runways-rocky15:56
*** tbachman_ has joined #openstack-nova15:57
mnaserjgwentworth: superdan SpamapS thanks for the input15:58
*** sahid has quit IRC15:58
*** shaohe_feng has quit IRC15:58
*** jangutter has quit IRC15:58
*** tbachman has quit IRC15:59
*** tbachman_ is now known as tbachman15:59
*** r-daneel has joined #openstack-nova16:00
*** shaohe_feng has joined #openstack-nova16:00
*** tesseract has quit IRC16:01
openstackgerritLee Yarwood proposed openstack/nova stable/ocata: libvirt: handle DiskNotFound during update_available_resource  https://review.openstack.org/57143216:02
openstackgerritLee Yarwood proposed openstack/nova stable/ocata: libvirt: Skip fetching the virtual size of block devices  https://review.openstack.org/57143316:02
superdanmnaser: since you're around, and since you do upgrades a lot, let me ask...16:03
mnaseri'm always around :p what's up?16:04
superdanmnaser: when you do an upgrade from say pike to queens, do you move everything off of every compute node before you do anything to that node, or do you just stop compute services, upgrade packages, and then re-start services?16:04
mnaserwe have the ability to live migrate everything because of ceph, but i've never needed to do that, my thought process is -- services are control plane and they don't affect vms16:04
mnaserso it's always been in place upgrades16:05
superdanmnaser: right okay, that's what I'd expect16:05
jgwentworthit was in place upgrades when I was at yahoo too16:05
mnasersuperdan: and that's also a lot of what 99% of deployment tools do as well, afaik16:05
superdanmnaser: if we forced you to migrate every instance in your cloud to roll to rocky, that would be a big deal right?16:06
superdanjgwentworth: yeah, I think it's the only case for very large clouds because it's not feasible to move everything, so that's good data16:06
superdanpretty sure I can say RAX didn't either16:06
jgwentworthyep, that16:06
mnasersuperdan: uh, very big, and id hope its <blink> bright red in the release notes16:07
mnaserand also the problem is that it's not possible for some other users which don't have the infrastructure to do migrations16:07
hansmolemansuperdan: i want to say huawei public cloud does a lot of live migrations, but Kevin_Zheng would know better than me on their upgrade strategy16:07
jgwentworthyeah, I think penick would have a problem with that too16:07
superdanmnaser: what about when you need to patch hypervisors or kernels? you do full slide puzzle to prevent any instance downtime?16:07
*** salv-orlando has joined #openstack-nova16:07
mnaseryes, hypervisor and kernel patching (as well as ceph for customers who we do hyperconverged deployments) all get emptied out first16:08
mnaserreasoning is: hypervisor and kernel touches something that affects the actual running vm, nova-compute does not16:08
superdanmnaser: okay, you never schedule downtime per instance? my cloud provider does it that way16:08
mnasernope, since we have ceph everywhere, live migrations are easy and function extremely well16:08
*** shaohe_feng has quit IRC16:08
mnaser10g network + ceph = no problems16:09
superdanmnaser: yeah, so what if you didn't have that? I know it's a bit theoretical but,16:09
superdanwhat if you had to transfer the entire disk and memory across the network for every migration?16:09
hansmolemanwe know that would kill NTT..16:09
hansmolemanat least16:09
superdanwould that change the calculus?16:09
mnaseryeah, big time, it would make the upgrade a huge pain16:10
superdanack, okay thanks16:10
mnaserespecially in a public cloud, you have to coordinate across so many customers..16:10
*** bnemec is now known as beekneemech16:10
hansmolemanis there something specifically up for review or being debated that would require us to move all instances to migrate to rocky?16:10
superdanyeah, the NRP allocation conversion thread16:10
*** harlowja has joined #openstack-nova16:11
hansmolemanok i figured16:11
hansmolemani've been blissfully ignorant on that so far16:11
mnaser^^ me too16:11
superdanI don't think forcing operators to migrate all instances to convert their allocations to nested is reasonable16:11
mnaserbecause i don't particularly understand it that much :)16:11
*** shaohe_feng has joined #openstack-nova16:11
mnaserbut maybe i should chime in, because i don't know all that much about the whole story16:11
SpamapSWe have 20gbit networking for migrations, and we're not ceph based. We aren't going to do a full migration for kernel/kvm updates, we'll schedule downtime. Reboot time is about 8 minutes.16:11
*** lifeless_ has joined #openstack-nova16:11
SpamapSWe do AZ's, and make sure to complete one AZ before doing the next.16:12
superdanSpamapS: ah sweet, that's a data point I was looking for16:12
*** lifeless has quit IRC16:12
superdanmy cloud provider does the same16:12
superdanbasically tells me that my instances will reboot on X at Y hour, downtime is minutes16:12
mnaseri think in subjects like this, it would be helpful if operators can get a much more simple question like the one superdan asked rather than having to understand whats going on with nested resource providers16:12
superdanand lets me do it early if I want16:12
*** salv-orlando has quit IRC16:12
jgwentworthmy cloud provider does that too16:12
*** felipemonteiro__ has quit IRC16:13
hansmolemancan't we have an allocation transformer tool or something for NRP?16:13
superdanmnaser: right, knowing if you're affected by the NRP change, or how, is also something I don't want to mix into the upgrade decision for them either16:13
SpamapSAnd when people are sad because their one pet VM was down for 10 minutes causing their service to be down, we definitely pat them on the back and say "there there". https://vignette.wikia.nocookie.net/glee/images/7/7a/Sheldon-leonard-there-there.gif/revision/latest?cb=2014090804560916:13
superdanhansmoleman: that's what I'm saying we owe to the users16:13
superdanSpamapS: ++16:13
* penick perks up16:13
superdanoh shit16:13
hansmolemannova-manage placement heal_allocations --fix-nrp16:13
superdanyou woke the bear16:13
hansmoleman--easy-button16:14
superdanhansmoleman: unfortunately, we can't really do it completely outside with a tool I think, because we need info from the compute node16:14
SpamapSsuperdan: the "lets me do it early" is interesting. So you're saying that if you hard reboot your instance, you don't get a downtime during the window?16:14
hansmolemansuperdan: maybe on restart of the compute service then? like we did for ironic instance flavors?16:14
superdanSpamapS: I can opt to take the downtime early, which is just them (cold) migrating me to another node that is already fixed, but on my schedule instead of theirs, yeah16:15
hansmolemanand we'll be doing for legacy bdm attachments16:15
SpamapSAH16:15
superdanhansmoleman: right, that's what I think we need to do16:15
SpamapSthat's neat16:15
SpamapSI think I'm going to put that on our todo list.16:15
superdanSpamapS: sometimes I opt fo that so I can check the health ofmy pet immediately, and sometimes I don't care, depending on which instance it is16:15
jgwentworthsuperdan, hansmoleman: ++ cause that also works with FFU16:15
hansmolemanwell,16:15
superdanjgwentworth: well, actually it doesn't16:15
hansmolemanright16:16
hansmolemanthere was that big stink about pci stuff in one of the upgrades16:16
mnaserok so really silly could a rocky nova-compute check if it's running for the first time and do the migrations?16:16
superdanjgwentworth: we have to provide them a way to do it outside too16:16
superdanhansmoleman: right16:16
superdanmnaser: yes16:16
jgwentworthoh, right... depending on where the startup code is during the fast-forward. I see16:16
hansmolemanwhich is why there was a migration CLI for the ironic flavor stuff as well16:16
openstackgerritMatt Riedemann proposed openstack/nova master: Trim the fat on HostState.instances  https://review.openstack.org/56924716:17
jgwentworthyeah. as long as there's a way we can, just worried about stuff like the PCI thing that required a pause in a fast forward16:17
*** armaan has joined #openstack-nova16:17
*** shaohe_feng has quit IRC16:19
bpoulosjgwentworth: thank you for the heads up! I'll keep my eye on the cert validation patches16:19
hansmolemansob, oom with the fake virt driver in devstack after 26 computes out of 10016:20
*** shaohe_feng has joined #openstack-nova16:20
jgwentworthbpoulos: awesome, thanks16:20
mnaserwell it could be an upgrade note where "if you're doing ffu, run this nova-manage thing, if you're doing a normal upgrade, nova will fix things on start"16:20
jgwentworthyeah, it could be that (and is how we've done previous things). provide a way to do an offline batch migration16:21
superdanmnaser: we _have_ to provide that yeah16:22
jgwentworthbeing able to do offline batch is useful in other ways too, for example the flavor migration from (was it kilo?) where instead of having flavors migrated on-the-fly while things are running, an operator could choose to do them in a batch via nova-manage during off peak time16:23
superdanmnaser: what I want to avoid is you having to do N manual conversions for N compute nodes, when you're not FFUing and upgrading in place16:23
superdanjgwentworth: yeah that was much easier because it didn't require knowledge of resource topologies16:23
* jgwentworth nods16:23
mnasersuperdan: well, maybe i'm over simplifying things but if there is some function of fix_nested_resource_providers() and that same one can either be called from nova-manage or on start up16:23
superdanmnaser: yeah, totes, I'm saying we should do it automatically if we can, fall back to manual if you are FFUing or want to do it while stuff is offline16:24
*** yamamoto has joined #openstack-nova16:25
mnaserthe reason i like it being done online is that it simplifies life for those doing normal upgrades16:25
mnaserand while i'm not implying lets make life hard for fast forward upgrades16:26
mnaserbut i assume they operate with the infrastructure needed to do this per-compute-node task etc16:26
openstackgerritSylvain Bauza proposed openstack/nova-specs master: Proposes Multiple GPU types  https://review.openstack.org/55706516:26
mnaserwhile most other deployment tools that don't do ffu don't have to add too much wild logic16:26
PapaOursleakypipes: hope my new revision addressed most of your concerns https://review.openstack.org/55706516:26
superdanmnaser: yep16:26
PapaOurscalling it a day now16:26
PapaOursbye, folks16:26
*** PapaOurs is now known as bauzas16:27
superdanmnaser: I'm asserting that for larger clouds, the in-place upgrade case is more common,16:27
*** r-daneel_ has joined #openstack-nova16:27
superdanand I think there is some perception that the common case is always to evacuate a compute node before upgrading nova-compute on it16:27
mnasersuperdan: i think i agree with you on that because usually they have more resources to keep them maintained16:27
*** fragatina has quit IRC16:27
superdanwhich works for 100 nodes, but not for 10,00016:27
jgwentworthmnaser: to be clear, doing online is the standard and the offline batch is an additional tool provided for those who prefer to leverage it or are doing FFU16:28
*** r-daneel has quit IRC16:28
*** r-daneel_ is now known as r-daneel16:28
*** fragatina has joined #openstack-nova16:28
mnaserjgwentworth: yep, i agree with that16:28
mnaserso if this 'process' doesnt run, what are the consequences?16:28
mnaserlike will the scheduler be weird? instances wont spawn?16:28
superdanmnaser: the NRP conversion? it can't not run16:28
superdanit's a pivot of all the resource accounting we do16:29
mnaseri'm just wondering what will happen with the inevitable cloud which will skip running them :p16:29
*** shaohe_feng has quit IRC16:29
*** gyee has joined #openstack-nova16:29
*** fried_rice is now known as fried_rolls16:29
superdanif they were manual only,16:30
superdanthen compute would have to refuse to start if the conversion hadn't been run16:30
*** shaohe_feng has joined #openstack-nova16:31
*** mxevgenis has joined #openstack-nova16:31
*** yamamoto has quit IRC16:32
mxevgenishi everyone! i have deployed an openstack cloud via ansible deployment and although i have 6 compute node in the nova availability zone all my instances are launched on the first 2 nodes. As a result the resources of the 4 nodes are not in use. Any idea what is going wrong?16:33
hansmolemanscheduler defaults to pack first16:34
hansmolemanrather than spread across all hosts16:34
jgwentworthyep that16:35
hansmolemanmxevgenis: see https://docs.openstack.org/nova/latest/configuration/config.html#filter_scheduler.host_subset_size16:35
mxevgenisthanks a lot. However when i launched many instances in order to consume all the available resources and force it to use the rest node, i got the error no valid host. Which means there are no extra resources. Is it normal considering the problem you mentioned?16:38
hansmolemanlow-hanging-fruit for someone https://bugs.launchpad.net/nova/+bug/177467616:39
openstackLaunchpad bug 1774676 in OpenStack Compute (nova) "Confusing usage information in max_instances_per_host config option" [Medium,Triaged]16:39
hansmolemanmxevgenis: then there is likely something wrong with those other hosts, not reporting inventory properly or something16:39
*** shaohe_feng has quit IRC16:39
hansmolemanyou'd probably have to dig into what those are reporting for inventory, via the os-hypervisors API and checking in placement (using the osc-placement plugin)16:39
*** shaohe_feng has joined #openstack-nova16:39
hansmolemanhttps://developer.openstack.org/api-ref/compute/#hypervisors-os-hypervisors16:39
*** gbarros has quit IRC16:39
hansmolemanhttps://docs.openstack.org/osc-placement/latest/index.html16:40
*** hansmoleman is now known as hans_lunch16:40
*** EmilienM is now known as EvilienM16:40
jgwentworthmxevgenis: what version of nova are you using? do you mean that you launch N instances at the same time and you expect some to go to the rest of the nodes once the first nodes are full? by default, nova will try to reschedule to another host when one is full https://docs.openstack.org/nova/latest/configuration/config.html#scheduler.max_attempts16:40
mxevgenisi deployed the ocata version of openstack using the openstack-ansible project. I launched many instances not simultaneously until all of my resources (of the first two nodes) where reserved. The n+1 instance which should be launched on one of the rest nodes failed16:43
mxevgeniswith no valid host error16:43
mxevgenisThe wired thing is that in the compute nodes tab the hosts are displayed as active16:43
jgwentworthand any subsequent separate attempt to boot an instance is resulting in NoValidHost even though the rest of the nods are available? in that case, like hans_lunch mentioned, something else is wrong and you need to take a look at your nova-scheduler and nova-compute logs to see why it's being rejected16:45
jgwentworth*nodes16:45
mxevgenisthanks a lot. i appreciate your help!!!16:45
*** esberglu has quit IRC16:45
jgwentworthprior to pike, it was possible for parallel requests to race in a way that even with reschedules, some requests could fail with NoValidHost as nodes filled up. but it sounds like that's not what you're hitting16:46
mxevgenisi should take a look on the logs and see what happens16:46
jgwentworthyeah, agreed. good luck16:47
mxevgenisthe wired thing is that the nodes which are working fine are different in terms of hardware to the rest servers16:47
mxevgenisthanks a lot for your help again16:48
*** mxevgenis has quit IRC16:48
jgwentworthyeah, there might be some host aggregate metadata mismatch going on (which if so, you will see in the logs) if you have things set differently depending on the hardware config of the servers. so yeah, have to check the logs to find out what's happening16:49
*** shaohe_feng has quit IRC16:49
*** armaan has quit IRC16:50
*** cdent has joined #openstack-nova16:50
*** shaohe_feng has joined #openstack-nova16:51
*** gbarros has joined #openstack-nova16:51
*** nicolasbock has quit IRC16:56
*** shaohe_feng has quit IRC17:00
openstackgerritDan Smith proposed openstack/nova master: Use oslo.messaging per-call monitoring  https://review.openstack.org/56669617:02
*** AlexeyAbashkin has quit IRC17:02
*** nicolasbock has joined #openstack-nova17:03
*** shaohe_feng has joined #openstack-nova17:04
*** mgoddard has quit IRC17:04
*** psachin has quit IRC17:08
*** salv-orlando has joined #openstack-nova17:08
*** markvoelker has joined #openstack-nova17:08
*** shaohe_feng has quit IRC17:10
*** shaohe_feng has joined #openstack-nova17:12
*** salv-orlando has quit IRC17:12
*** suresh12 has quit IRC17:19
*** shaohe_feng has quit IRC17:20
*** slunkad has quit IRC17:21
*** shaohe_feng has joined #openstack-nova17:22
*** harlowja has quit IRC17:22
openstackgerritMerged openstack/nova master: libvirt: place emulator threads on CONF.compute.cpu_shared_set  https://review.openstack.org/51089717:25
*** ispp has joined #openstack-nova17:25
*** yamamoto has joined #openstack-nova17:27
*** shaohe_feng has quit IRC17:30
*** shaohe_feng has joined #openstack-nova17:31
*** ispp has quit IRC17:33
*** fried_rolls is now known as fried_rice17:33
cfriesenmnaser: for what it's worth I've played with kingbird a bit and it's somewhat useful but lacking robustness and functionality.   (It only supports specific quotas for example.)17:33
*** gbarros has quit IRC17:33
*** yamamoto has quit IRC17:34
*** Swami has joined #openstack-nova17:34
*** gbarros has joined #openstack-nova17:36
*** shaohe_feng has quit IRC17:41
*** shaohe_feng has joined #openstack-nova17:41
*** gbarros has quit IRC17:43
fried_ricesuperdan, mnaser, SpamapS, jgwentworth: I think I'm providing a way to do it live without the operator/admin having to do anything or even know it's happening.17:43
superdanfried_rice: yeah I think I acknowledged that you may be in my reply, but -EFRIDAY on processing it17:44
fried_ricesuperdan: ack17:45
jgwentworthkewl17:45
*** gbarros has joined #openstack-nova17:46
*** mvk has quit IRC17:46
*** suresh12 has joined #openstack-nova17:47
*** suresh12 has quit IRC17:49
*** yamahata has joined #openstack-nova17:49
*** suresh12 has joined #openstack-nova17:49
SpamapSwas hoping to discuss https://review.openstack.org/#/c/568953/ and https://bugs.launchpad.net/nova/+bug/1742102 today17:49
openstackLaunchpad bug 1742102 in OpenStack Compute (nova) "Simple user can disable compute" [High,In progress] - Assigned to Matt Riedemann (mriedem)17:49
SpamapSbut I don't see a mriedem so maybe will have to wait until next week17:50
SpamapSI'm a little concerned that it may be very easy to DoS clouds that are set up to "pack" instead of "spread".17:50
superdanSpamapS: so turn it off17:50
*** ttsiouts has joined #openstack-nova17:51
*** shaohe_feng has quit IRC17:51
superdanSpamapS: mriedem is hans_lunch today, btw17:51
*** jmlowe has quit IRC17:51
*** shaohe_feng has joined #openstack-nova17:52
SpamapSsuperdan: yes I"m suggesting that telling people to turn it off should be a CVE17:52
jgwentworthdefault is "pack", so this is a problem out-of-the-box17:52
SpamapSsince the default is to have it turned on17:52
superdancalling it a CVE is way overblown, IMHO17:52
SpamapSand one basically just has to get nova to try and send a bunch of broken image+flavor reqs to a single compute node to disable it... and then keep doing that until they're all disabled.17:53
SpamapSIf a regular user can disable your compute nodes, that rises to CVE IMO.17:53
jgwentworthmnaser: I think you hit this too, right? ^17:53
SpamapSThere are a lot of examples of advisory CVE's where certain configurations are vulnerable, and no code fix is available because it requires heavy refactoring.17:54
SpamapSI don't really want to write an exploit for this17:54
SpamapSbut if you guys want to suggest it's not feasible.. we can go down that road, and maybe disprove it is feasible and forget about a CVE.17:54
SpamapSBut we already had our stage cloud get all of its compute nodes disabled because of a bad image.17:55
mnaseryes i ran into this too17:55
jgwentworthfwiw, I think it's feasible and I think it's a serious problem. I'm just not so experienced with CVEs17:55
mnaserum one second17:55
superdanSpamapS: that feature was specifically requested by a bunch of ops in Boston, you know17:56
*** yamamoto has joined #openstack-nova17:56
SpamapSFeature is great! Implementation, not so much.17:56
superdanum17:56
mnasersometimes it would be like17:56
mnasernova-compute tries to create volume, user hit their quota, volume create fails, that gets labeled as a failed deploy17:56
*** gbarros has quit IRC17:56
mnaserdo enough of that and you'll start disabling everything, for us, we kinda just disabled that for now17:57
SpamapSThough IMO it should have included a back-off re-enabler too since, presumably, a disabled compute node may recover on its own and be able to serve traffic again. It's worth it to retry nodes that were in bad shape before.17:57
superdanmnaser: right, but that's just because volume create shouldn't be included in the list of disable-able things17:57
superdanit was intended to only be things that were obviously fatally broken17:57
SpamapSmnaser: yeah we're disabling the feature, and likely won't re-enable it until it also re-enables compute nodes automatically. But I figure there are likely Nova users out there that have it enabled, and are vulnerable to a malicious or even just poorly-configured user disabling all their compute nodes.17:58
superdanSpamapS: well, we could do that, but when I brought it up in the room, nobody wanted it to re-enable17:58
mnasersuperdan: agreed, it includes things like ports, i think i worked partially on this but i forgot what progress i had :(17:58
*** esberglu has joined #openstack-nova17:58
superdanfor what it's worth,17:59
*** gbarros has joined #openstack-nova17:59
jgwentworthmnaser: yeah. I think we saw that it would quickly become whack-a-mole, so we didn't have a straightforward way to solve it. trying to whitelist a bunch of things is a mess17:59
superdananything that accidentally falls into the disable bucket are also things that generate retries,17:59
superdanso a user that can abuse that can also generate a ton of extra churn in the system, being DoSish on its own18:00
*** mgoddard has joined #openstack-nova18:00
superdanshould we CVE for having max_attempts>1?18:00
SpamapSAnyway, there are two things I'd like to see happen and I'm happy to drive either or both. (1) Fix it so that it only increments on *specific* faults that are permanent failures on the compute node, instead of just a whitelist for exceptions to ignore. And (2) inform the user community of the danger they may be in.18:00
superdanSpamapS: it already only increments for specific things18:00
superdanSpamapS: it's just that set needs tweaking18:00
SpamapSdid you see the list harlowja made?18:00
mnasersuperdan:, SpamapS: http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2018-04-12.log.html18:01
mnaserbrief discussion there18:01
*** yamamoto has quit IRC18:01
SpamapSThose don't seem well thought out.18:01
SpamapSAnd aren't explicitly listed.18:01
SpamapSmnaser: indeed, I found that yesterday.18:01
*** gbarros has quit IRC18:01
superdanwell, part of the problem is that we convert stupid exceptions to stupid build results18:01
*** shaohe_feng has quit IRC18:01
superdanand it operates on the latter18:01
SpamapShttps://bugs.launchpad.net/nova/+bug/177452718:02
openstackLaunchpad bug 1742102 in OpenStack Compute (nova) "duplicate for #1774527 Simple user can disable compute" [High,In progress] - Assigned to Matt Riedemann (mriedem)18:02
SpamapShas Josh's list18:02
mnaserand then previous discussion here too http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2018-01-23.log.html#t2018-01-23T19:36:4118:02
*** shaohe_feng has joined #openstack-nova18:02
mnaserbut i have to get back to doing some $work stuff but yeah, we disabled it on ourside18:02
SpamapSsuperdan: perhaps we shouldn't disable on stupid things?18:02
superdanSpamapS: I think I've said I agree with that statement :)18:02
SpamapSindeed18:02
superdanhow come you guys think this is CVEish and just filed a non-security bug for it?18:03
superdanthat kinda eliminates the supposed desire to make a big deal over it :)18:03
*** klindgren has joined #openstack-nova18:03
jgwentworthsuperdan: they filed it as security but it's already known18:03
jgwentworthso I'm not sure how that works.18:03
superdanit's public, so not a security bug18:03
SpamapSand agreed that if you can cause a bunch of retries you are already causing the cloud some slowness. But the compute nodes disable somewhat silently, and permanently, creating a far worse situation than just "it's slow now"18:04
jgwentworthwell, IMHO it should have been a security bug from the start, but the original bug reporter reported it as public18:04
SpamapSWe didn't actually think it was a security bug, just reporting "hey this broke our cloud"18:04
SpamapSand then we debugged more and were like "zomg security"18:04
SpamapSand then we found out there was already public knowledge18:04
superdanSpamapS: you're going to DoS the first three nodes in your pack scenario18:05
superdanif you're just hitting those18:05
superdanso, anyway,18:05
mnaserexcept if you boot with --num-instances 10018:05
superdanmnaser: well, true, but you're going for DoS so you don't do that if you're an attacker, right?18:05
superdananyway, I'd really like to fix the thing and not rip it out,18:05
superdanbut if people want to disable it by default for now, that's cool18:06
superdanalthough I think that means we'll never fix it18:06
mnasermaybe i should hush but nova doesn't even let us control the # to provide in --num-instances (and i'm agreeing that we clean it up rather than remove it)18:06
mnaserso if you have enough quota you can --num-instances one-zillion18:06
SpamapSI think the right fix is to pick *specific* build results that have high or absolute confidence are the fault of the compute node.18:06
*** gbarros has joined #openstack-nova18:06
superdanmnaser: OMG CVE! :)18:06
mnasershhh its friday18:06
mnaserwe don't want that18:06
superdanSpamapS: we do pick specific build results, that's the thing18:06
superdanSpamapS: we convert _exceptions_ to build results in not the right way18:07
mnaseranything that results in a rescheduled build will trigger that counter to increase i think18:07
SpamapSHow does an image too big for flavor failure land in that bucket then?18:07
SpamapSOr a "failure to download image"18:07
mnaseri think that's a bug that nova considers that a reschedule-able failure18:07
SpamapSyeah see re-schedulable doesn't mean it's the compute node's fault.18:08
jgwentworthI dunno, I do think it's worth an advisory to call this out because if any ol user could disable a lot of compute nodes by just making normal requests, it's a major problem18:08
mnaserfailure to download image could be that specific compute node cannot talk to glance18:08
mnaserbut it's a tricky weird thing to balance18:08
SpamapScould be18:08
SpamapSbut you don't *know*18:08
mnaserbut if your glance is down then18:08
mnaserall your compute nodes are going disabled18:08
jrollinhatinSpamapS: looks like two members from the VMT are already aware of this bug and triaging how we notify about it; if you're looking to have it tagged with a CVE perhaps engage them instead (since they're the people that do that thing)?18:08
*** suresh12 has quit IRC18:09
SpamapSyeah if glance is down or just partitioned from 1/3 of your cloud for right now, you don't want that to take that entire part of the cloud down without also re-enabling it when it comes back or unpartitions.18:09
superdanSpamapS: failure to download an image is pretty legit to disable, no? not flavor too small though, obviously18:09
superdanyeah, if glance is down that's fair I guess18:09
SpamapSjrollinhatin: ah good point. K, I've not actually driven a CVE before.18:09
SpamapSsuperdan: failure to download an image is pretty ambiguous.18:09
SpamapSAnd very likely to be temporary.18:10
superdanSpamapS: it's easy for some computes to be unable to download images, partition like you said18:10
SpamapSLike, to be able to really know where the fault is, you need something like Vitrage.18:10
superdanSpamapS: so this came up as one compute node being unable to do basic stuff like that can _also_ take down your whole cloud because it attracts all new builds and fails them18:10
superdanscientific cloud with no reschedules, pack mode, one compute node takes the whole thing down with it18:10
SpamapSRight, so maybe the right thing is to split into two categories.18:11
SpamapSThings to disable permanently for, and things to drop from retry list.18:11
superdanmaybe what we should have done is just make a weigher or filter based on the fail score18:11
SpamapSor.. not retry18:11
mnaseri like that idea18:11
SpamapSbut things to stop scheduling for18:11
superdanmnaser: that's a fairly easy iteration from where we are18:11
*** shaohe_feng has quit IRC18:11
SpamapSThis is where k8s's scheduler does something smarter. If they get a failure on a node, they retry for a while on that node, and then they start backing off from it.. scheduling less and less frequently to it.18:12
SpamapSIt's not disabled.. they keep trying it.. but less and less often.18:12
SpamapSA weighter would be perfect.18:13
SpamapSJust expose the consecutive failures counter and have a coeficient based on that.18:13
SpamapSSo as it gets higher, the node gets less and less attempts.18:13
*** throwsb1 has quit IRC18:13
jgwentworthmakes sense18:14
SpamapSArguably it should not reset to 0 on success, but just decrement.18:14
superdanSpamapS: why?18:14
SpamapSFlapping.18:14
*** harlowja has joined #openstack-nova18:14
*** shaohe_feng has joined #openstack-nova18:14
superdanSpamapS: you end up with a pretty hard to explain situation for why some compute nodes rarely get used,18:14
SpamapSIf you reset it to 0, you start dumping lots on it again, which may make it start failing again.18:14
superdanwhich boils down to "it was partitioned for a long time a month ago and hasn't recovered"18:14
SpamapSYeah maybe there needs to be a time based decrementer too.18:15
superdanso decrement by ten on each success18:15
SpamapSLike, decrement by 1 every x seconds, and 1 every success.18:15
superdancounter = min(0, counter - 10)18:15
superdanSpamapS: you're building a complicated thing that generates DB traffic18:15
SpamapSYeah or you could weight heavily toward successes.18:15
SpamapSam I? I was thinking this number lives in the compute node and just goes along with ram/cpu/etc. stats?18:16
superdanSpamapS: we're trying to get rid of those stats that get reported all the time for no reason18:16
SpamapSand thus gets included in the current weighters?18:17
SpamapSOh, how are we going to schedule without them? (Sorry for the basic questions, I'm not up to speed on current refactors)18:17
superdanwe report resources in different ways now, and we don't constantly report "yep, the compute node still has a total of 192G of ram, same as last minute"18:18
SpamapSYeah we just report on changes or something, yes?18:18
SpamapSso could be the same for this score, no?18:18
superdanwell, we do via the old mechanism, but that's what we want to remove, and eventually hopefully the need to even run periodically18:18
*** READ10 has quit IRC18:18
SpamapScan you point me at a description of those different ways? I want to understand. :)18:19
superdanthe thing that is responsible for checking resources has nothing to do with this either18:19
*** jmlowe has joined #openstack-nova18:19
superdaneverything we've done with placement lately?18:19
superdanI can't point you at one thing18:19
SpamapSI don't want you to have to type it all into IRC.. if there's just a description, I can think more clearly about how to make a weighter based on the scheduling health, which I think might be a nice way to evolve this feature.18:20
superdanit's not the weigher that's a problem, of course,18:20
superdanit's just more complicated if you have a periodic, which has a decay interval (config) and runs either independently (we have so many) or glommed onto something else like resource audit, which it has nothing to do with18:21
superdanand a successful boot either zeroing or aggressively decrementing the value is semantically closer to what we implemented initially, which people liked18:21
SpamapSI think it makes sense to decay it based on time, but maybe there are better ways. I like the idea of just having a coeficient to pull the fail counter down faster than it rises.18:22
*** shaohe_feng has quit IRC18:22
*** shaohe_feng has joined #openstack-nova18:22
*** jmlowe has quit IRC18:23
superdanthe less we change the behavior, the more likely we are to be able to maybe backport something too18:23
jgwentworthSpamapS: coincidentally I happened upon this earlier today when trying to answer a different question, might be a good starting point for learning more if you're interested https://docs.openstack.org/nova/latest/reference/scheduling.html18:23
SpamapSYeah, I think we'd just have to tell people to turn it off if they're in a situation where they might get DoS'd.18:24
SpamapSjgwentworth: thanks, was just reading that! :)18:24
jgwentworthoh, heh18:24
*** suresh12 has joined #openstack-nova18:24
SpamapSlike, 30s before you sent, so, we're on the same page. Literally.18:25
jgwentworthhaha18:25
*** jmlowe has joined #openstack-nova18:25
SpamapSThe thing is, it would have to go down over time or nodes that got way off the rails might never see activity again.18:26
superdanif you're packing, you're opting into empty nodes right?18:26
SpamapSlike if some aggregate got really full and a poorly weighted HV that is unhealthy gets scheduled and fails a lot for a while.. its score gets really high, then you add capacity somehow.. that node may never get any attempts unless you decrement or reset the counter.18:26
superdanI'm just trying to think about how we can do this initially with minimal change (config, code) and minimal semantic difference18:27
superdanfor the purposes of applying to to existing stuff18:27
superdanif we're not interested in backporting it (backporting a weigher would be a first I bet) then maybe it doesn't matter18:27
*** fragatina has quit IRC18:27
SpamapSYeah I'm not sure. Still thinking through what might be a more self-managing place for the feature is all.18:27
SpamapSGood chat. I'll give it some thought, and see if we can also help the VMT determine if we should notify users about the potential for DoS.18:29
*** suresh12 has quit IRC18:29
*** shaohe_feng has quit IRC18:32
*** suresh12 has joined #openstack-nova18:33
*** shaohe_feng has joined #openstack-nova18:34
superdanI just looked over all our periodics and I don't think it fits with any of the existing ones18:35
superdanthere are a couple that would be closeish, but would still look really random to just do this other thing in the middle,18:35
harlowjapeople can if they want try http://paste.openstack.org/show/722481/ on some public openstack cloud, though i'd recommend u communicate with their operators before doing it at any scale18:35
superdanplus you probably want to be able to control the interval of this, which means it needs its own knob18:36
harlowjawe ran that on one of our idle clouds and it was able to knock off 2 compute nodes in about 15 minutes18:36
harlowjaafaik because of https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L1804-L181018:36
harlowjaline 81 -> 85 are the 'triggers'18:36
harlowjaboot faster than nova can build18:37
jrollinhatinprobably best not to post a working exploit for a security bug in an irc channel this large :|18:37
harlowja*boot and delete18:37
superdanjrollinhatin: yeah nfs18:37
*** tbachman has quit IRC18:37
*** tbachman has joined #openstack-nova18:37
penickharlowja dude18:39
harlowjai'd have kept it on https://bugs.launchpad.net/nova/+bug/1774527 but that is already public as well18:41
openstackLaunchpad bug 1742102 in OpenStack Compute (nova) "duplicate for #1774527 Simple user can disable compute" [High,In progress] - Assigned to Matt Riedemann (mriedem)18:41
SpamapSCat's been out of the bag since January guys. That's not exactly rocket science.18:41
*** itlinux has quit IRC18:42
*** shaohe_feng has quit IRC18:42
superdanwe've discussed it in public many times before then,18:43
superdanbut if ya'll are so concerned about disclosure.. seems weird to argue for that and posting exploits :)18:43
*** mgoddard has quit IRC18:44
*** tbachman has quit IRC18:44
*** shaohe_feng has joined #openstack-nova18:45
*** itlinux has joined #openstack-nova18:46
*** itlinux has quit IRC18:46
hans_lunchjgwentworth: i think this bp is probably also done now https://review.openstack.org/#/q/topic:bp/overhead-pin-set+(status:open+OR+status:merged)18:47
*** bkopilov_ has quit IRC18:48
jgwentworthhans_lunch: awesome thanks. maybe I'll double check with sahid before closing it out18:49
*** felipemonteiro_ has joined #openstack-nova18:51
*** pchavva has quit IRC18:51
*** shaohe_feng has quit IRC18:52
*** shaohe_feng has joined #openstack-nova18:54
*** suresh12 has quit IRC18:56
*** suresh12 has joined #openstack-nova18:57
*** yamamoto has joined #openstack-nova18:58
*** hans_lunch is now known as mriedem18:59
*** ttsiouts has quit IRC19:00
mriedemso it seems some fun times were had while i was eating bbq19:01
mriedemmnaser: btw, https://review.openstack.org/#/c/510235/ was a brain dump on the "limit --min-count during server create" issue19:02
mriedemit's really weird though19:02
mriedemfrom what i remember (of me writing the thing) is proposing a per-request limit19:02
mriedemconfigurable like quotas19:03
*** shaohe_feng has quit IRC19:03
*** yamamoto has quit IRC19:03
superdanjust like max_results, but inbound yeah? seems to make sense to me19:03
*** Guest25886 has quit IRC19:03
mriedemright it's the exact same idea as metadata_items and injected_files quotas19:03
mriedemthose are purely rate limiting19:04
*** shaohe_feng has joined #openstack-nova19:04
mriedemhttps://review.openstack.org/#/c/510235/1/specs/queens/approved/instance-max-count-limit.rst@9419:04
superdanwell, I wouldn't call them quotas since they're per-request and not per-tenant, but yeah19:04
superdanbeing a loaded term and all19:04
mriedemright19:04
*** openstackgerrit has quit IRC19:04
mriedemyour rpc heartbeat thing solves part of this also19:05
mriedemwith the select_destinations retry thing19:05
mnasera per request limit is really what's needed because i can add some middleware to limit # of api requests easily19:05
mnaserbut min_servers=999999999999999 isn't something i can control much19:05
mriedemright, well, it sounds like there is interest in this :)19:05
superdanmnaser: yeah19:05
superdanmriedem: if we enable it for select_destinations yeah19:06
mriedemi currently seem to have too many spinning plates19:06
mriedemi could probably get yikun to work on this though...19:06
*** felipemonteiro__ has joined #openstack-nova19:08
*** tianhui has joined #openstack-nova19:08
*** tbachman has joined #openstack-nova19:09
*** tianhui_ has quit IRC19:10
*** trungnv has quit IRC19:10
*** trungnv_ has joined #openstack-nova19:10
*** felipemonteiro_ has quit IRC19:11
*** obre_ has quit IRC19:12
*** toabctl has quit IRC19:12
*** shaohe_feng has quit IRC19:13
*** obre has joined #openstack-nova19:13
*** shaohe_feng has joined #openstack-nova19:14
*** toabctl has joined #openstack-nova19:16
*** Guest25886 has joined #openstack-nova19:18
*** shaohe_feng has quit IRC19:23
*** mike99201 has joined #openstack-nova19:24
*** shaohe_feng has joined #openstack-nova19:25
*** gbarros has quit IRC19:29
*** tbachman has quit IRC19:29
*** itlinux has joined #openstack-nova19:30
*** shaohe_feng has quit IRC19:33
*** shaohe_feng has joined #openstack-nova19:34
*** itlinux has quit IRC19:35
*** jlvillal is now known as jlvacation19:43
*** shaohe_feng has quit IRC19:44
*** openstackgerrit has joined #openstack-nova19:44
openstackgerritKashyap Chamarthy proposed openstack/nova master: libvirt: Remove usage of migrateToURI{2} APIs  https://review.openstack.org/56725819:44
*** shaohe_feng has joined #openstack-nova19:46
*** mike99201 is now known as mike99201-gone19:46
*** Guest25886 has quit IRC19:51
*** felipemonteiro__ has quit IRC19:52
*** felipemonteiro__ has joined #openstack-nova19:52
*** shaohe_feng has quit IRC19:54
*** shaohe_feng has joined #openstack-nova19:57
*** lifeless_ has quit IRC20:00
*** suresh12 has quit IRC20:00
*** lifeless has joined #openstack-nova20:01
*** pcaruana has quit IRC20:03
*** suresh12 has joined #openstack-nova20:04
*** shaohe_feng has quit IRC20:04
*** shaohe_feng has joined #openstack-nova20:05
*** Guest25886 has joined #openstack-nova20:06
*** itlinux has joined #openstack-nova20:08
*** suresh12 has quit IRC20:08
*** shaohe_feng has quit IRC20:14
*** shaohe_feng has joined #openstack-nova20:16
*** throwsb1 has joined #openstack-nova20:16
*** tidwellr has quit IRC20:21
*** tidwellr has joined #openstack-nova20:23
*** shaohe_feng has quit IRC20:25
*** tbachman has joined #openstack-nova20:25
*** yamamoto has joined #openstack-nova20:25
cfriesenkashyap: are the valid "param" keys for20:25
cfriesenPersonally I'd replace the first sentence with something like "Thanks for checking out the StarlingX codebase."  I think we'd want to make inclusion in the community an explicit opt-in thing rather than making assumptions.  Sounds like Matt's got the technical details covered though so maybe it's a moot point.20:25
cfriesenI don't think there's any chance Kashyap would be interested in doing the actual work.  He (and others) have already expressed skepticism at the idea that anyone outside of Intel/Wind River would ever contribute to StarlingX.20:25
cfriesenChris20:25
*** shaohe_feng has joined #openstack-nova20:25
cfriesenwell that's embarassing20:26
*** suresh12 has joined #openstack-nova20:27
*** tidwellr has quit IRC20:28
cfriesenwhat I was trying to say, was are the valid "param" keys for the migrateToURI3() function documented somewhere?  I didn't see them on the Libvirt API docs.20:29
*** yamamoto has quit IRC20:31
*** suresh12 has quit IRC20:32
*** suresh12 has joined #openstack-nova20:33
*** shaohe_feng has quit IRC20:35
*** shaohe_feng has joined #openstack-nova20:35
*** fragatina has joined #openstack-nova20:37
*** suresh12 has quit IRC20:37
*** klindgren_ has joined #openstack-nova20:38
*** klindgren has quit IRC20:41
*** tidwellr has joined #openstack-nova20:42
*** vladikr has quit IRC20:42
*** suresh12 has joined #openstack-nova20:45
*** moshele has joined #openstack-nova20:45
*** shaohe_feng has quit IRC20:45
*** tidwellr_ has joined #openstack-nova20:46
*** tidwellr has quit IRC20:46
*** shaohe_feng has joined #openstack-nova20:46
*** moshele has quit IRC20:48
*** lifeless has quit IRC20:50
*** lifeless has joined #openstack-nova20:51
*** tidwellr_ has quit IRC20:51
*** shaohe_feng has quit IRC20:55
*** vladikr has joined #openstack-nova20:56
openstackgerritMerged openstack/nova master: Restrict CONF.quota.driver to DB and noop quota drivers  https://review.openstack.org/41099620:56
openstackgerritMerged openstack/nova master: Fix invalid raise in test_compute_mgr  https://review.openstack.org/57161020:56
*** ispp has joined #openstack-nova20:57
*** jmlowe has quit IRC20:57
*** ispp has quit IRC20:58
*** shaohe_feng has joined #openstack-nova20:58
*** shaohe_feng has quit IRC21:06
*** wolverineav has quit IRC21:06
openstackgerritMerged openstack/nova master: Implement granular policy rules for placement  https://review.openstack.org/52442521:06
*** shaohe_feng has joined #openstack-nova21:06
*** wolverineav has joined #openstack-nova21:07
*** bpoulos has quit IRC21:10
*** esberglu has quit IRC21:11
*** wolverineav has quit IRC21:12
openstackgerritJay Pipes proposed openstack/nova master: Add a microversion for consumer generation support  https://review.openstack.org/56560421:12
*** shaohe_feng has quit IRC21:16
*** mchlumsky has quit IRC21:17
*** shaohe_feng has joined #openstack-nova21:17
*** EvilienM has quit IRC21:18
*** EmilienM has joined #openstack-nova21:19
*** yamamoto has joined #openstack-nova21:19
*** EmilienM is now known as EvilienM21:19
*** edmondsw has quit IRC21:25
*** superdan is now known as dansmith21:25
*** dave-mcc_ has quit IRC21:25
*** shaohe_feng has quit IRC21:26
*** shaohe_feng has joined #openstack-nova21:28
*** yamamoto has quit IRC21:29
*** munimeha1 has quit IRC21:30
openstackgerritJay Pipes proposed openstack/nova master: placement: always create consumer records  https://review.openstack.org/56767821:31
openstackgerritJay Pipes proposed openstack/nova master: add consumers generation field  https://review.openstack.org/55795821:31
openstackgerritJay Pipes proposed openstack/nova master: placement: Allocation.consumer field  https://review.openstack.org/56540521:31
openstackgerritJay Pipes proposed openstack/nova master: rework allocation handler _allocations_dict()  https://review.openstack.org/56540721:31
openstackgerritJay Pipes proposed openstack/nova master: Add a microversion for consumer generation support  https://review.openstack.org/56560421:31
*** shaohe_feng has quit IRC21:36
*** shaohe_feng has joined #openstack-nova21:40
*** itlinux_ has joined #openstack-nova21:41
mriedemwoot 20 fake compute nodes in devstack single node, time for some fun21:41
*** mriedem has quit IRC21:42
*** lyan has quit IRC21:43
* cdent thinks mriedem broke it21:43
*** itlinux has quit IRC21:44
openstackgerritMerged openstack/nova master: [placement] default to accept of application/json when */*  https://review.openstack.org/56863021:45
*** tidwellr has joined #openstack-nova21:46
*** shaohe_feng has quit IRC21:47
*** wolverineav has joined #openstack-nova21:48
*** felipemonteiro__ has quit IRC21:48
*** tidwellr has quit IRC21:51
*** esberglu has joined #openstack-nova21:51
*** slaweq has quit IRC21:52
openstackgerritChris Dent proposed openstack/nova master: Extract part of PlacementFixture to placement  https://review.openstack.org/56835921:53
*** shaohe_feng has joined #openstack-nova21:54
*** tbachman has quit IRC21:55
*** esberglu has quit IRC21:57
*** shaohe_feng has quit IRC21:57
*** shaohe_feng has joined #openstack-nova21:58
*** burt has quit IRC22:00
*** gbarros has joined #openstack-nova22:01
*** shaohe_feng has quit IRC22:07
*** shaohe_feng has joined #openstack-nova22:09
*** slaweq has joined #openstack-nova22:10
*** yamamoto has joined #openstack-nova22:15
openstackgerritkarim proposed openstack/nova master: Handle rebuild of instances with image traits  https://review.openstack.org/56949822:16
*** shaohe_feng has quit IRC22:17
*** shaohe_feng has joined #openstack-nova22:19
*** figleaf is now known as edleafe22:20
*** slaweq has quit IRC22:21
*** yamamoto has quit IRC22:22
*** tbachman has joined #openstack-nova22:24
*** dabo has joined #openstack-nova22:26
*** markvoelker has quit IRC22:27
*** markvoelker has joined #openstack-nova22:28
*** shaohe_feng has quit IRC22:28
*** edleafe has quit IRC22:28
*** dabo is now known as edleafe22:28
*** shaohe_feng has joined #openstack-nova22:29
openstackgerritEric Fried proposed openstack/nova master: Test for multiple limit/group_policy qparams  https://review.openstack.org/56871322:29
*** tbachman_ has joined #openstack-nova22:31
*** tbachman has quit IRC22:31
*** tbachman_ is now known as tbachman22:31
*** rajinir has quit IRC22:31
*** markvoelker has quit IRC22:33
*** slaweq has joined #openstack-nova22:36
*** tbachman has quit IRC22:36
*** shaohe_feng has quit IRC22:38
*** lifeless has quit IRC22:38
*** shaohe_feng has joined #openstack-nova22:39
*** slaweq has quit IRC22:39
*** lifeless has joined #openstack-nova22:40
*** Sukhdev has joined #openstack-nova22:47
openstackgerritMatt Riedemann proposed openstack/nova master: Add nova-manage placement heal_allocations CLI  https://review.openstack.org/56588622:47
*** jmlowe has joined #openstack-nova22:47
*** hongbin has quit IRC22:48
*** shaohe_feng has quit IRC22:48
*** leakypipes has quit IRC22:50
*** shaohe_feng has joined #openstack-nova22:50
*** shaohe_feng has quit IRC22:58
*** shaohe_feng has joined #openstack-nova22:59
*** Swami has quit IRC23:04
openstackgerritChris Dent proposed openstack/nova master: Optional separate database for placement API  https://review.openstack.org/36276623:07
openstackgerritChris Dent proposed openstack/nova master: Isolate placement database config  https://review.openstack.org/54143523:08
openstackgerritChris Dent proposed openstack/nova master: Ensure that os-traits sync is attempted only at start of process  https://review.openstack.org/55385723:08
*** shaohe_feng has quit IRC23:09
openstackgerritChris Dent proposed openstack/nova master: Add PLACEMENT_DB_ENABLED=True to the nova-next job  https://review.openstack.org/56406723:09
*** shaohe_feng has joined #openstack-nova23:10
openstackgerritChris Dent proposed openstack/nova master: Use nova.db.api directly  https://review.openstack.org/54326223:10
*** fried_rice is now known as efried23:12
*** salv-orlando has joined #openstack-nova23:13
*** salv-orlando has quit IRC23:17
*** harlowja has quit IRC23:18
*** yamamoto has joined #openstack-nova23:18
*** shaohe_feng has quit IRC23:19
*** throwsb1 has quit IRC23:21
*** shaohe_feng has joined #openstack-nova23:22
*** yamamoto has quit IRC23:24
*** chyka has quit IRC23:27
*** shaohe_feng has quit IRC23:29
*** shaohe_feng has joined #openstack-nova23:30
*** wolverineav has quit IRC23:33
*** wolverineav has joined #openstack-nova23:33
*** lifeless has quit IRC23:36
*** shaohe_feng has quit IRC23:39
*** shaohe_feng has joined #openstack-nova23:40
*** lifeless has joined #openstack-nova23:43
*** wolverineav has quit IRC23:45
*** suresh12 has quit IRC23:49
*** shaohe_feng has quit IRC23:50
*** shaohe_feng has joined #openstack-nova23:50

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