Monday, 2018-03-12

*** claudiub|2 has quit IRC00:01
*** yangyapeng has joined #openstack-nova00:01
*** Guest27 has joined #openstack-nova00:04
*** Guest27 has quit IRC00:05
*** yangyapeng has quit IRC00:06
*** salv-orlando has joined #openstack-nova00:06
*** salv-orlando has quit IRC00:11
*** stakeda has joined #openstack-nova00:17
*** sapd has quit IRC00:19
*** hshiina has joined #openstack-nova00:24
SpazmoticMorning again00:26
*** yassine has joined #openstack-nova00:26
*** slaweq has joined #openstack-nova00:28
*** edmondsw has joined #openstack-nova00:31
*** slaweq has quit IRC00:33
*** edmondsw has quit IRC00:35
*** slaweq has joined #openstack-nova00:38
*** itlinux has quit IRC00:39
*** BrinZhang has joined #openstack-nova00:39
*** slaweq has quit IRC00:43
*** tbachman has quit IRC00:44
*** slaweq has joined #openstack-nova00:49
*** slaweq has quit IRC00:54
*** hongbin has joined #openstack-nova00:54
*** jichen has joined #openstack-nova00:58
*** phuongnh has joined #openstack-nova00:58
*** zhaochao has joined #openstack-nova00:59
*** tiendc has joined #openstack-nova01:01
*** salv-orlando has joined #openstack-nova01:06
*** salv-orlando has quit IRC01:11
*** amodi has joined #openstack-nova01:15
*** liuzz has joined #openstack-nova01:17
*** artom has quit IRC01:21
*** suresh12 has joined #openstack-nova01:23
*** suresh12 has quit IRC01:28
*** pengdake has joined #openstack-nova01:30
*** yangyapeng has joined #openstack-nova01:32
*** tbachman has joined #openstack-nova01:34
*** pengdake has quit IRC01:38
*** pengdake has joined #openstack-nova01:38
*** amodi has quit IRC01:40
*** lei-zh has joined #openstack-nova01:40
*** amodi has joined #openstack-nova01:48
*** tiendc has quit IRC01:48
*** tiendc has joined #openstack-nova01:49
*** slaweq has joined #openstack-nova01:50
*** hiro-kobayashi has joined #openstack-nova01:50
*** slaweq has quit IRC01:54
*** vladikr has joined #openstack-nova01:56
*** sapd has joined #openstack-nova01:58
*** slaweq has joined #openstack-nova02:00
*** Dinesh_Bhor has joined #openstack-nova02:03
*** slaweq has quit IRC02:05
openstackgerritJake Yip proposed openstack/nova master: Update deprecated log-config option in docs  https://review.openstack.org/55182502:07
*** salv-orlando has joined #openstack-nova02:07
*** gcb has joined #openstack-nova02:08
*** hoangcx has joined #openstack-nova02:11
*** salv-orlando has quit IRC02:12
*** edmondsw has joined #openstack-nova02:19
*** edmondsw has quit IRC02:24
*** namnh has joined #openstack-nova02:28
*** amodi has quit IRC02:34
*** slaweq has joined #openstack-nova02:40
*** pengdake has quit IRC02:43
*** psachin has joined #openstack-nova02:44
*** amodi has joined #openstack-nova02:45
*** jichen has quit IRC02:45
*** slaweq has quit IRC02:45
*** jichen has joined #openstack-nova02:45
*** vladikr has quit IRC02:50
*** vladikr has joined #openstack-nova02:51
*** slaweq has joined #openstack-nova02:51
*** sapd has quit IRC02:55
*** sapd has joined #openstack-nova02:55
*** slaweq has quit IRC02:56
*** vladikr has quit IRC02:59
*** vladikr has joined #openstack-nova02:59
*** salv-orlando has joined #openstack-nova03:08
*** licanwei has joined #openstack-nova03:10
*** salv-orlando has quit IRC03:12
*** sapd1 has joined #openstack-nova03:15
*** psachin has quit IRC03:18
*** BrinZhang has quit IRC03:31
*** BrinZhang has joined #openstack-nova03:31
*** psachin has joined #openstack-nova03:33
*** zhangbailin_ has joined #openstack-nova03:34
*** BrinZhang has quit IRC03:38
*** dave-mccowan has quit IRC03:38
*** pooja_jadhav has joined #openstack-nova03:40
*** vladikr has quit IRC03:45
*** vladikr has joined #openstack-nova03:45
*** _pewp_ has quit IRC03:48
*** _pewp_ has joined #openstack-nova03:49
*** vivsoni has quit IRC03:51
*** vivsoni_ has joined #openstack-nova03:51
*** suresh12 has joined #openstack-nova04:01
*** slaweq has joined #openstack-nova04:02
*** hongbin has quit IRC04:02
*** zhurong has joined #openstack-nova04:06
*** suresh12 has quit IRC04:06
*** slaweq has quit IRC04:07
*** udesale has joined #openstack-nova04:07
*** edmondsw has joined #openstack-nova04:07
*** salv-orlando has joined #openstack-nova04:09
*** suresh12 has joined #openstack-nova04:09
*** amodi has quit IRC04:09
*** edmondsw has quit IRC04:12
*** slaweq has joined #openstack-nova04:12
*** salv-orlando has quit IRC04:14
*** slaweq has quit IRC04:17
*** stakeda has quit IRC04:21
*** jmlowe_ has joined #openstack-nova04:21
*** gjayavelu has joined #openstack-nova04:22
*** suresh12 has quit IRC04:23
*** jmlowe has quit IRC04:24
*** lpetrut has joined #openstack-nova04:24
*** jmlowe_ has quit IRC04:26
*** wolverineav has joined #openstack-nova04:27
*** wolverineav has quit IRC04:27
*** wolverineav has joined #openstack-nova04:28
*** wolverineav has joined #openstack-nova04:28
*** wolverineav has quit IRC04:30
*** wolverineav has joined #openstack-nova04:31
*** wolverineav has quit IRC04:35
*** suresh12 has joined #openstack-nova04:35
*** lei-zh has quit IRC04:35
*** slaweq has joined #openstack-nova04:43
*** slaweq has quit IRC04:48
*** suresh12 has quit IRC04:49
*** lpetrut has quit IRC04:51
*** suresh12 has joined #openstack-nova04:58
*** Dinesh_Bhor has quit IRC04:59
*** lei-zh has joined #openstack-nova05:04
*** suresh12 has quit IRC05:04
*** germs has joined #openstack-nova05:06
*** germs has quit IRC05:06
*** germs has joined #openstack-nova05:06
*** zhurong has quit IRC05:09
*** salv-orlando has joined #openstack-nova05:10
*** sridharg has joined #openstack-nova05:10
*** germs has quit IRC05:11
*** sridharg has quit IRC05:11
*** sridharg has joined #openstack-nova05:13
*** salv-orlando has quit IRC05:15
*** yangyapeng has quit IRC05:21
*** janki has joined #openstack-nova05:22
*** fragatina has quit IRC05:30
*** fragatina has joined #openstack-nova05:31
*** Dinesh_Bhor has joined #openstack-nova05:35
*** sidx64 has joined #openstack-nova05:38
*** sridhargaddam has joined #openstack-nova05:40
*** sridharg has quit IRC05:41
*** mdnadeem has joined #openstack-nova05:43
*** deepak_ has joined #openstack-nova05:44
*** yangyapeng has joined #openstack-nova05:45
*** claudiub|2 has joined #openstack-nova05:50
*** yangyapeng has quit IRC05:51
*** suresh12 has joined #openstack-nova05:51
*** sapd1 has quit IRC05:52
*** edmondsw has joined #openstack-nova05:55
*** suresh12 has quit IRC05:56
*** ratailor has joined #openstack-nova05:57
*** yamahata has quit IRC05:59
vivsoni_Hi Team, tempest.api.volume.test_volumes_extend.VolumesExtendAttachedTest.test_extend_attached_volume is failing06:00
vivsoni_we already have a launchpad bug raised for it06:00
vivsoni_https://bugs.launchpad.net/nova/+bug/173219906:00
openstackLaunchpad bug 1732199 in OpenStack Compute (nova) "test_extend_attached_volume fails with Unexpected compute_extend_volume result 'Error'" [Medium,Confirmed]06:00
*** david-lyle has quit IRC06:00
*** edmondsw has quit IRC06:00
*** annp has joined #openstack-nova06:01
*** yangyapeng has joined #openstack-nova06:03
*** jaosorior has joined #openstack-nova06:06
*** zhurong has joined #openstack-nova06:06
*** david-lyle has joined #openstack-nova06:07
*** yangyapeng has quit IRC06:07
*** yangyapeng has joined #openstack-nova06:07
*** salv-orlando has joined #openstack-nova06:11
*** slaweq has joined #openstack-nova06:15
*** salv-orlando has quit IRC06:15
openstackgerritOpenStack Proposal Bot proposed openstack/nova master: Imported Translations from Zanata  https://review.openstack.org/54877206:18
*** slaweq has quit IRC06:20
*** moshele has joined #openstack-nova06:21
*** salv-orlando has joined #openstack-nova06:23
*** slaweq has joined #openstack-nova06:25
*** udesale has quit IRC06:25
*** ratailor_ has joined #openstack-nova06:26
*** threestrands_ has joined #openstack-nova06:26
*** amotoki_ has joined #openstack-nova06:27
*** hoangcx_ has joined #openstack-nova06:29
*** alexchadin has joined #openstack-nova06:29
*** slaweq has quit IRC06:29
*** BlackDex_ has joined #openstack-nova06:30
*** andymccr_ has joined #openstack-nova06:33
*** lei-zh has quit IRC06:33
*** lei-zh has joined #openstack-nova06:34
*** ratailor has quit IRC06:34
*** hoangcx has quit IRC06:34
*** gcb has quit IRC06:34
*** threestrands has quit IRC06:34
*** xinliang has quit IRC06:34
*** NostawRm has quit IRC06:34
*** andymccr has quit IRC06:34
*** mdrabe has quit IRC06:34
*** BlackDex has quit IRC06:34
*** amotoki has quit IRC06:34
*** hemna has quit IRC06:34
*** NostawRm has joined #openstack-nova06:35
*** hemna has joined #openstack-nova06:35
*** slaweq has joined #openstack-nova06:35
*** mdrabe has joined #openstack-nova06:35
*** tuanla____ has joined #openstack-nova06:38
*** slaweq has quit IRC06:40
*** gcb has joined #openstack-nova06:40
*** xinliang has joined #openstack-nova06:40
*** sridhargaddam has quit IRC06:40
*** sridharg has joined #openstack-nova06:41
*** lajoskatona has joined #openstack-nova06:43
*** phuongnh has quit IRC06:44
*** phuongnh has joined #openstack-nova06:45
*** Dinesh_Bhor has quit IRC06:45
*** slaweq has joined #openstack-nova06:45
*** hoangcx_ is now known as hoangcx06:47
*** sar has quit IRC06:47
*** gjayavelu has quit IRC06:47
*** bauwser has quit IRC06:48
*** Dinesh_Bhor has joined #openstack-nova06:49
*** slaweq has quit IRC06:50
*** Shilpa has joined #openstack-nova06:50
*** Dinesh_Bhor has quit IRC06:51
*** sidx64 has quit IRC06:51
*** sidx64 has joined #openstack-nova06:53
*** tiendc has quit IRC06:55
*** tiendc has joined #openstack-nova06:55
*** slaweq has joined #openstack-nova06:55
*** namnh has quit IRC06:57
*** tuanla____ has quit IRC06:57
*** annp has quit IRC06:57
*** tuanla____ has joined #openstack-nova06:57
*** namnh has joined #openstack-nova06:57
*** annp has joined #openstack-nova06:57
*** Dinesh_Bhor has joined #openstack-nova06:59
*** slaweq has quit IRC07:00
*** tuanla____ has quit IRC07:04
*** Eran_Kuris has joined #openstack-nova07:05
*** slaweq has joined #openstack-nova07:06
*** germs has joined #openstack-nova07:07
*** germs has quit IRC07:07
*** germs has joined #openstack-nova07:07
*** rcernin has quit IRC07:09
*** slaweq has quit IRC07:10
*** germs has quit IRC07:11
*** sidx64_ has joined #openstack-nova07:13
*** threestrands_ has quit IRC07:13
*** sidx64 has quit IRC07:14
*** gjayavelu has joined #openstack-nova07:14
*** gjayavelu has quit IRC07:16
*** slaweq has joined #openstack-nova07:16
*** sidx64 has joined #openstack-nova07:16
*** sar has joined #openstack-nova07:17
*** sidx64_ has quit IRC07:17
*** lpetrut has joined #openstack-nova07:20
*** slaweq has quit IRC07:21
*** Dinesh_Bhor has quit IRC07:22
*** Dinesh_Bhor has joined #openstack-nova07:25
*** slaweq has joined #openstack-nova07:26
*** trinaths has joined #openstack-nova07:29
*** slaweq has quit IRC07:31
*** trinaths has quit IRC07:33
*** phuongnh has quit IRC07:33
*** maciejjozefczyk has joined #openstack-nova07:35
*** slaweq has joined #openstack-nova07:36
*** jafeha__ is now known as jafeha07:37
*** udesale has joined #openstack-nova07:40
*** pasuder has joined #openstack-nova07:40
*** slaweq has quit IRC07:40
*** sahid has joined #openstack-nova07:42
*** phuongnh has joined #openstack-nova07:43
*** edmondsw has joined #openstack-nova07:44
*** sidx64 has quit IRC07:47
*** ttsiouts has joined #openstack-nova07:47
*** edmondsw has quit IRC07:48
*** slaweq has joined #openstack-nova07:53
*** migi has joined #openstack-nova07:54
*** alexchadin has quit IRC07:55
*** pcaruana has joined #openstack-nova07:56
*** slaweq__ has joined #openstack-nova07:56
*** migi has quit IRC07:57
*** Dinesh_Bhor has quit IRC07:57
*** migi has joined #openstack-nova07:58
*** AlexeyAbashkin has joined #openstack-nova07:59
*** slaweq__ has quit IRC08:01
*** migi has quit IRC08:02
*** alexchadin has joined #openstack-nova08:05
*** migi has joined #openstack-nova08:05
*** slaweq__ has joined #openstack-nova08:07
*** Dinesh_Bhor has joined #openstack-nova08:08
*** Dinesh_Bhor has quit IRC08:09
*** tesseract has joined #openstack-nova08:10
*** tianhui_ is now known as tianhui08:11
*** slaweq__ has quit IRC08:11
*** kaisers has quit IRC08:13
*** jpena|off is now known as jpena08:14
*** slaweq__ has joined #openstack-nova08:17
*** ccamacho has joined #openstack-nova08:18
*** ShilpaSD has joined #openstack-nova08:19
*** bhagyashri_s has joined #openstack-nova08:19
*** pooja-jadhav has joined #openstack-nova08:19
*** kaisers has joined #openstack-nova08:19
*** Shilpa has quit IRC08:21
*** pooja_jadhav has quit IRC08:21
*** bhagyashris has quit IRC08:21
*** slaweq__ has quit IRC08:22
*** Dinesh_Bhor has joined #openstack-nova08:23
*** slaweq__ has joined #openstack-nova08:27
*** ispp has joined #openstack-nova08:27
*** salv-orlando has quit IRC08:28
*** slaweq__ has quit IRC08:31
*** hoonetorg has quit IRC08:36
*** slaweq__ has joined #openstack-nova08:37
*** trinaths has joined #openstack-nova08:38
*** slaweq__ has quit IRC08:42
*** slaweq__ has joined #openstack-nova08:47
*** amoralej|off is now known as amoralej08:49
*** damien_r has joined #openstack-nova08:49
*** hoonetorg has joined #openstack-nova08:50
*** slaweq__ has quit IRC08:52
*** sidx64 has joined #openstack-nova08:57
*** slaweq__ has joined #openstack-nova08:58
openstackgerritMichael Still proposed openstack/nova master: Move configurable mkfs to privsep.  https://review.openstack.org/55192109:01
*** tssurya has joined #openstack-nova09:01
*** hiro-kobayashi has quit IRC09:02
*** slaweq__ has quit IRC09:03
openstackgerritClaudiu Belu proposed openstack/nova master: compute: Adds instance live-resize  https://review.openstack.org/24858109:03
openstackgerritClaudiu Belu proposed openstack/nova master: db: Adds live-resize to Migration model migration_type  https://review.openstack.org/18596109:03
openstackgerritClaudiu Belu proposed openstack/nova master: conductor: add live_resize task  https://review.openstack.org/24857909:03
*** salv-orlando has joined #openstack-nova09:04
*** lucas-afk is now known as lucasagomes09:07
*** germs has joined #openstack-nova09:08
*** germs has quit IRC09:08
*** germs has joined #openstack-nova09:08
*** slaweq__ has joined #openstack-nova09:08
*** sridharg has quit IRC09:08
*** sridharg has joined #openstack-nova09:08
*** germs has quit IRC09:12
*** alexchadin has quit IRC09:13
*** slaweq__ has quit IRC09:13
*** slaweq__ has joined #openstack-nova09:18
*** hshiina has quit IRC09:22
*** slaweq__ has quit IRC09:22
openstackgerritdo3meli proposed openstack/nova-specs master: Adds resize on shared storage without ssh keys  https://review.openstack.org/55192709:26
*** slagle has quit IRC09:26
*** lyarwood is now known as lyaaaaaaaarwood09:27
*** finucannot is now known as stephenfin09:28
*** slaweq__ has joined #openstack-nova09:28
openstackgerritdo3meli proposed openstack/nova-specs master: Adds resize on shared storage without ssh keys  https://review.openstack.org/55192709:29
*** mgoddard_ has joined #openstack-nova09:31
*** giblet is now known as gibi09:31
gibimorning09:32
*** edmondsw has joined #openstack-nova09:32
*** Dinesh_Bhor has quit IRC09:32
*** ralonsoh has joined #openstack-nova09:33
*** slaweq__ has quit IRC09:33
*** Dinesh_Bhor has joined #openstack-nova09:33
*** salv-orlando has quit IRC09:34
*** edmondsw has quit IRC09:36
*** salv-orlando has joined #openstack-nova09:36
*** slaweq__ has joined #openstack-nova09:38
openstackgerritAlex Xu proposed openstack/nova-specs master: Report CPU features to placement service by traits API  https://review.openstack.org/49773309:38
*** lyaaaaaaaarwood is now known as lyarwood09:38
*** slaweq__ has quit IRC09:43
*** danpawlik has joined #openstack-nova09:44
*** mgoddard_ has quit IRC09:47
*** bauzas has joined #openstack-nova09:47
*** sambetts_ is now known as sambetts09:48
*** ragiman has joined #openstack-nova09:48
bauzasgood morning Nova09:48
bauzasjust spent 2 hours of investigation because had a severe network outage09:48
bauzasfound the root cause https://twitter.com/sylvainbauza/status/97312705107403161609:48
*** slaweq__ has joined #openstack-nova09:49
*** oanson has quit IRC09:51
*** fragatina has quit IRC09:51
*** slaweq__ has quit IRC09:53
*** mgoddard_ has joined #openstack-nova09:53
*** oanson has joined #openstack-nova09:57
*** jichen has quit IRC09:57
*** slaweq__ has joined #openstack-nova09:59
gibibauzas: nice start for a Monday09:59
bauzasyeah, it just killed my morning :(09:59
bauzasin general, I always walk the dog in the mornings10:00
bauzasbut today, I was wanting to work earlier10:00
gibibauzas: but you solved a hard problem already so you were productive10:00
bauzasmeh10:01
bauzasI haven't understood why the Vera Plus is saturing the switch10:01
*** pasuder has quit IRC10:02
*** yamamoto has quit IRC10:02
openstackgerritsahid proposed openstack/nova-specs master: virt: allow instances to be booted with trusted VFs  https://review.openstack.org/48552210:03
*** udesale has quit IRC10:03
*** slaweq__ has quit IRC10:04
openstackgerritsahid proposed openstack/nova-specs master: virt: allow instances to be booted with trusted VFs  https://review.openstack.org/48552210:04
*** pasuder has joined #openstack-nova10:05
*** annp has quit IRC10:05
*** hrw has left #openstack-nova10:07
*** slagle has joined #openstack-nova10:08
*** slaweq__ has joined #openstack-nova10:09
*** udesale has joined #openstack-nova10:12
*** udesale has quit IRC10:13
*** udesale has joined #openstack-nova10:14
*** slaweq__ has quit IRC10:14
*** slagle has quit IRC10:14
*** lei-zh has quit IRC10:16
*** dtantsur|afk is now known as dtantsur10:16
openstackgerritLee Yarwood proposed openstack/nova stable/queens: Avoid exploding if guest refuses to detach a volume  https://review.openstack.org/55194810:16
SpazmoticWell that sounds like a gross start to the week.10:19
*** slaweq__ has joined #openstack-nova10:19
*** namnh has quit IRC10:20
openstackgerritLee Yarwood proposed openstack/nova stable/pike: Avoid exploding if guest refuses to detach a volume  https://review.openstack.org/55195010:21
*** zhangbailin_ has quit IRC10:21
*** jangutter has joined #openstack-nova10:22
*** alexchadin has joined #openstack-nova10:23
SpazmoticHmm there's a similar event for that in the XenAPI Drivers that I should add that into10:24
*** slaweq__ has quit IRC10:24
*** jangutter_ has joined #openstack-nova10:26
openstackgerritSurya Seetharaman proposed openstack/nova master: Marker reset option for nova-manage map_instances  https://review.openstack.org/53950110:26
*** jangutter has quit IRC10:29
*** slaweq__ has joined #openstack-nova10:29
*** mgoddard_ has quit IRC10:29
openstackgerritsahid proposed openstack/nova-specs master: libvirt: add support for virtio-net rx/tx queue sizes  https://review.openstack.org/53960510:31
*** slaweq__ has quit IRC10:34
*** zhurong has quit IRC10:37
*** phuongnh has quit IRC10:39
*** slaweq__ has joined #openstack-nova10:39
*** trinaths has quit IRC10:43
openstackgerritSurya Seetharaman proposed openstack/nova master: Marker reset option for nova-manage map_instances  https://review.openstack.org/53950110:43
*** slaweq__ has quit IRC10:44
*** sdague has joined #openstack-nova10:45
*** slaweq__ has joined #openstack-nova10:50
*** slaweq__ has quit IRC10:54
*** slaweq__ has joined #openstack-nova11:00
*** yamamoto has joined #openstack-nova11:03
*** slaweq__ has quit IRC11:04
*** pasuder has quit IRC11:05
*** germs has joined #openstack-nova11:08
*** germs has quit IRC11:08
*** germs has joined #openstack-nova11:08
*** slaweq__ has joined #openstack-nova11:10
*** yamamoto has quit IRC11:11
*** germs has quit IRC11:13
*** yamamoto has joined #openstack-nova11:14
*** slaweq__ has quit IRC11:15
*** pasuder has joined #openstack-nova11:18
*** mgoddard_ has joined #openstack-nova11:18
*** slaweq__ has joined #openstack-nova11:20
*** yikun has joined #openstack-nova11:22
*** slaweq__ has quit IRC11:25
*** BlackDex_ is now known as BlackDex11:30
*** slaweq__ has joined #openstack-nova11:30
johnthetubaguyjaypipes: I am wondering about traits on glance images, should the flavor be allowed to deny some / give permission for some (thinking of billing being linked to flavors really) Maybe it goes back to that forbidden traits configuration idea?11:31
SpazmoticGlance Metadata already has restrictions built into its metadata such as minRam, MinDisk.  Any reason to duplicate that?11:34
johnthetubaguywell it has protected properties, its just you likely want that per flavor11:34
SpazmoticThat's true enough, they are the protected ones11:35
johnthetubaguywell, or rather you want a whitelist not a blacklist I think11:35
*** slaweq__ has quit IRC11:35
*** lajoskatona has quit IRC11:35
SpazmoticI see, I guess I could see the useful ness for that on some image types.  Was just curious mostly :)11:36
*** takedakn has joined #openstack-nova11:37
*** ratailor_ has quit IRC11:38
*** lucasagomes is now known as lucas-hungry11:39
*** slaweq__ has joined #openstack-nova11:41
*** tiendc has quit IRC11:41
*** danpawlik has quit IRC11:42
*** slaweq__ has quit IRC11:45
openstackgerritMerged openstack/nova-specs master: Return Generation from Resource Provider Creation  https://review.openstack.org/54890311:48
*** lajoskatona has joined #openstack-nova11:49
*** slaweq__ has joined #openstack-nova11:51
*** stvnoyes1 has left #openstack-nova11:53
stephenfingibi, jaypipes: Can we jump on a Hangout sometime later this afternoon when you're both about? I'd like to hash out [1] before I write anything more for it [1] https://review.openstack.org/#/c/541290/11:54
gibistephenfin: sure, we can11:55
gibistephenfin: after the scheduler meeting maybe?11:55
*** slaweq__ has quit IRC11:56
*** danpawlik has joined #openstack-nova11:58
*** yikun has quit IRC11:59
*** cdent has joined #openstack-nova11:59
*** yikun has joined #openstack-nova11:59
*** slaweq__ has joined #openstack-nova12:01
*** tssurya has quit IRC12:02
*** janki has quit IRC12:02
*** jmlowe has joined #openstack-nova12:03
*** slaweq__ has quit IRC12:06
johnthetubaguystephenfin: just spotted some changes left in limbo, I am tempted to push these forward for you, but should it say rocky now? https://review.openstack.org/#/c/499179/12:06
*** jmlowe has quit IRC12:08
*** jmlowe has joined #openstack-nova12:10
*** slaweq__ has joined #openstack-nova12:11
*** edmondsw has joined #openstack-nova12:13
*** alexchadin has quit IRC12:15
openstackgerritMerged openstack/nova-specs master: Re-propose convert consoles code to use objects framework  https://review.openstack.org/54366212:15
openstackgerritZhenyu Zheng proposed openstack/nova-specs master: Add request_id filed to InstanceAction versioned notifications  https://review.openstack.org/55198212:15
*** slaweq__ has quit IRC12:15
*** tssurya has joined #openstack-nova12:15
openstackgerritMerged openstack/nova-specs master: Add support for certificate validation  https://review.openstack.org/54087912:18
*** mvk has quit IRC12:21
*** slaweq__ has joined #openstack-nova12:21
*** salv-orlando has quit IRC12:23
*** pasuder has quit IRC12:24
*** yamamoto has quit IRC12:26
*** slaweq__ has quit IRC12:26
*** Eran_Kuris has quit IRC12:28
openstackgerritClaudiu Belu proposed openstack/nova master: db: Adds live-resize to Migration model migration_type  https://review.openstack.org/18596112:30
*** slaweq__ has joined #openstack-nova12:32
*** efried has joined #openstack-nova12:32
*** salv-orlando has joined #openstack-nova12:33
* efried waves12:33
* edleafe waves back12:33
*** slagle has joined #openstack-nova12:34
*** janki has joined #openstack-nova12:34
efriededleafe: Before I start filtering through a week worth of emails, anything earth-shattering I should know about from last week?12:35
Spazmoticjohnthetubaguy,  thanks sir :)12:36
efriedThis is literally the first time I've booted up my computer since the PTG12:36
*** slaweq__ has quit IRC12:36
edleafeefried: glad to hear you know how to do PTO12:37
efried~800 unread emails.  Sigh.12:37
edleafeefried: but no, nothing other than the usual12:37
*** mvk has joined #openstack-nova12:37
efriededleafe: Cool, thanks.12:37
*** lei-zh has joined #openstack-nova12:39
* gibi waves to efried 12:40
jaypipesstephenfin: sure. after scheduler meeting works for me.12:40
efriedHi gibi12:40
*** slaweq__ has joined #openstack-nova12:42
jaypipesjohnthetubaguy: currently, we have nothing in the os-traits library or in nova that identifies "conflicting" traits. for example, there's nothing preventing an admin from decorating a compute node with both the STORAGE_DISK_HDD and STORAGE_DISK_SSD traits at the same time. We will need some logic somewhere (not in the virt driver I would hope) to process conflicts in requested traits between the flavor and image I would think?12:42
openstackgerritsahid proposed openstack/nova-specs master: libvirt: add support for virtio-net rx/tx queue sizes  https://review.openstack.org/53960512:43
cdentcan we call that rope? If you try it, it doesn't work, you investigate, you see why, don't do that again12:44
*** Eran_Kuris has joined #openstack-nova12:44
cdentputting _meaning_ into the traits (rather than just beign symbols) will get messy12:44
cdentjaypipes: ^12:44
efriedjaypipes, cdent: Yeah, I agree we don't want to try to get too clever - *especially* outside of virt driver - about inter-trait semantics like that.12:44
efriedFor the SSD/HDD example, if I'm not using trees, and I have both kinds of disk on my compute host, that could be a valid configuration.12:45
cdentwelcome back efried12:45
efriedEven if I am using trees, it's not certain I would split the local disk out from the compute node RP12:46
efriedThanks cdent!12:46
efriedoh, you mean in the request12:46
efriedSo if I make a resource request that has both of those traits, in one request group, it doesn't make sense.12:46
*** slaweq__ has quit IRC12:47
efried...and would *usually* fail in GET /a_c.  Unless you've got the aforementioned host with both kinds of disk on it.12:47
* efried stops blathering and goes back to deleting emails.12:48
jaypipesefried: for sure.12:50
*** slaweq__ has joined #openstack-nova12:52
*** mgoddard_ has quit IRC12:53
edleafeI agree that there shouldn't be meaning in traits. If there needs to be logic added, it should be in the layer that is applying the traits, not in the trait API.12:54
efriedWhat we NEED is trait metadata12:55
efriedAnd aggregate metadata.12:55
edleafesomebody shoot that guy12:55
*** pasuder has joined #openstack-nova12:56
*** slaweq__ has quit IRC12:56
jaypipesheh12:57
cdentactually, I'd prefer trait traits12:58
*** gcb has quit IRC12:59
jaypipescdent: lol13:00
edleafethat's silly. What we need are aggregates of traits13:01
edleafewith metadata, of course13:01
*** slaweq__ has joined #openstack-nova13:02
cdentwhy have aggregates when we can have trait traits traits?13:03
*** yangyapeng has quit IRC13:03
cdent(I actually do think it would be much more easy to reason about the world if we only had traits and not aggregates)13:04
cdentbut I'm a faceted classification kind of guy13:04
edleafewe've been through this. There really is no difference. I prefer traits because it's shorter to type13:04
jaypipesbuffalo buffalo buffalo buffalo buffalo buffalo buffalo13:05
*** yangyapeng has joined #openstack-nova13:05
*** trozet has quit IRC13:05
cdentparkay13:06
cdentIf traits is shorter than aggregates and that's good, then _clearly_ tags are the way to go13:07
* cdent pulls up his trouser legs13:07
*** READ10 has joined #openstack-nova13:07
*** slaweq__ has quit IRC13:07
arvindn05continue the discussion on #openstack-meeting-alt ?13:07
jaypipeshehe13:07
jaypipesarvindn05: in 55 minutes, no?13:08
*** trozet has joined #openstack-nova13:08
edleafearvindn05: in 52 minutes, sure13:08
edleafejinx13:08
jaypipesarvindn05: daylight savings... :)13:08
arvindn05ah...DST  :)13:08
jaypipesyup13:08
jaypipesgets me every time.13:08
*** mgoddard_ has joined #openstack-nova13:08
*** yangyapeng has quit IRC13:09
arvindn05would have thought outlook adjusted...oh well...extra hour for me :)13:09
arvindn05edleafe: cdent: latest patch set on https://review.openstack.org/#/c/541507/ addresses other concerns..can you add your review and original +1's?13:11
edleafearvindn05: I have that and a bunch of others open for review today.13:11
cdentyup, already have that open in tab13:12
arvindn05great...thanks.13:12
*** slaweq__ has joined #openstack-nova13:12
*** salv-orlando has quit IRC13:13
arvindn05i think i need a workflow +1...i am guessing that should come from matt?13:13
*** liverpooler has joined #openstack-nova13:14
*** dtantsur is now known as dtantsur|brb13:16
*** slaweq__ has quit IRC13:17
*** slagle has quit IRC13:18
*** amoralej is now known as amoralej|lunch13:19
*** slaweq__ has joined #openstack-nova13:22
*** yamamoto has joined #openstack-nova13:23
*** lyan has joined #openstack-nova13:23
*** lyan is now known as Guest1843413:24
stephenfinjohnthetubaguy: They should. I'll fix them up and ping you then, if that's OK?13:24
*** slagle has joined #openstack-nova13:24
SpazmoticWelcome home, BTW, efried13:25
efriedSpazmotic: Thanks!13:25
openstackgerritStephen Finucane proposed openstack/nova master: conf: Remove '[conductor] topic' opt  https://review.openstack.org/49917913:26
stephenfinjohnthetubaguy: Actually, it was just the commit message so I stripped out that line (there's no rocky equivalent) and sent it through. Fancy hitting https://review.openstack.org/#/c/508487 though?13:27
*** slaweq__ has quit IRC13:27
*** yamamoto has quit IRC13:28
Spazmoticc'mon tempest-full.. don't play with me13:30
*** awaugama has joined #openstack-nova13:31
SpazmoticMy achey breaky heart and all that.13:31
*** slagle has quit IRC13:31
*** dave-mccowan has joined #openstack-nova13:31
sahidjaypipes: we have some kind of agrements on this spec: https://review.openstack.org/#/c/539605/ if we can have you to make a first +213:32
*** slaweq__ has joined #openstack-nova13:33
sahidcfriesen: any chance you have a look at this https://review.openstack.org/#/c/511188/ ?13:33
*** burt has joined #openstack-nova13:33
*** yangyapeng has joined #openstack-nova13:33
*** salv-orlando has joined #openstack-nova13:35
*** yangyapeng has quit IRC13:35
*** yangyapeng has joined #openstack-nova13:36
openstackgerritMerged openstack/nova master: Raise a proper exception in unit test  https://review.openstack.org/55091413:37
johnthetubaguystephenfin: I think all the others need the same treatment?13:37
johnthetubaguystephenfin: happy to hit the whole chain though, all seem like good tidy ups13:37
*** slaweq__ has quit IRC13:37
*** efried has quit IRC13:39
*** esberglu has joined #openstack-nova13:40
*** READ10 has quit IRC13:41
*** READ10 has joined #openstack-nova13:41
*** slaweq__ has joined #openstack-nova13:43
*** gongysh has joined #openstack-nova13:44
ShilpaSDstephenfin: Hi13:44
*** jackie-truong has joined #openstack-nova13:45
*** gouthamr has joined #openstack-nova13:45
*** mriedem has joined #openstack-nova13:46
*** tianhui has quit IRC13:46
jaypipessahid: done13:46
kashyapjaypipes, johnthetubaguy: Does this require a specification?  Also a config change: https://review.openstack.org/#/c/511188/13:47
*** tianhui has joined #openstack-nova13:47
kashyapErr, wrong link13:47
sahidjaypipes: thanks13:47
kashyapjaypipes: johnthetubaguy Correct one: https://review.openstack.org/#/c/534384/ ("Allow to specify granular CPU feature flags")13:48
*** slaweq__ has quit IRC13:48
*** Eran_Kuris has quit IRC13:48
johnthetubaguyjaypipes: +1 on the conflict resolution, I was more thinking about operator per flavor restrictions, like allow trait overrides on a specific flavor13:48
johnthetubaguykashyap: that is libvirt only, and via config, I think, so you could argue it was a specless blueprint13:49
jaypipeskashyap: I prefer https://review.openstack.org/#/c/497733/.13:49
kashyapjohnthetubaguy: Right; I'll go file that spec-less Blueprint13:49
*** r-daneel has joined #openstack-nova13:50
kashyapjaypipes: Hi, this is a bit more imminent, the commit message gives the rationale: https://review.openstack.org/#/c/534384/13:50
kashyapjaypipes: I see the spec you linked to is the long-term solution13:50
kashyapBut to solve the immediate performance problems for all the users, I'd argue the above config approach is the cleanest13:51
johnthetubaguynot sure, there is make available to guest and require from guest so restrict to hosts that have it13:51
johnthetubaguyI guess its just two sides of the problem?13:51
kashyapjohnthetubaguy: Can you expand on this: "require from guest so restrict to hosts that have it"13:52
jaypipeskashyap: adding yet more configuration options to nova.conf? that is specific to a single virt driver and doesn't solve the problem for the rest of them?13:52
johnthetubaguyan image or flavor might "require" pcid13:52
johnthetubaguyregardless the operator might want to provide pcid to the guest13:52
johnthetubaguyseems like two different things13:53
kashyapjaypipes: I'm with you on not sleep-walking into adding more and more config options.13:53
kashyapjaypipes: But ...13:53
*** slaweq__ has joined #openstack-nova13:53
*** yamamoto has joined #openstack-nova13:53
kashyapjaypipes: This is an exceptional scenario.  The executive summary is: In light of applying the "Meltdown" CVE fixes, those guests using custom CPU models will incur 30% additional performance penalty!13:53
kashyapjaypipes: So, I don't take the adding a new config option approach very lightly13:54
*** beagles is now known as beagles|brb13:54
kashyapjaypipes: Yeah, there is a case to be made for that, too: allowing operators to configure _per_ flavor13:54
kashyap(But that's a different problem.  I wanted to address this immediate isolated problem.)13:54
jaypipeskashyap: it's more of an image thing than a flavor thing, right?13:55
johnthetubaguyneither, its an operator problem here13:55
johnthetubaguykashyap: you need more context in the git commit message, and less about those additional use cases13:55
dansmithyeah, this is a pretty important one, IMHO13:55
johnthetubaguyideally we would turn it on everywhere to avoid the performance issue, but its not available everywhere, and that would break live-migrate13:55
dansmithand on par with other virt conf options we have13:55
*** takedakn has quit IRC13:56
johnthetubaguydansmith: +113:56
*** eharney has joined #openstack-nova13:56
kashyapjohnthetubaguy: I wrote additional context in my first commit message.13:56
kashyapjohnthetubaguy: Here's all the additional context: https://review.openstack.org/#/c/534384/2//COMMIT_MSG13:56
kashyap(But I was asked to remove it from the commit by mdbooth.)13:56
kashyapDamned if I did, damned if I didn't13:56
johnthetubaguykashyap: maybe somewhere in between, without the sub headings13:57
*** yamahata has joined #openstack-nova13:58
*** slaweq__ has quit IRC13:58
kashyapjohnthetubaguy: Can modify it; I used sub headings just to make it more readable.  Wonder if you think the core content is okay?13:58
*** yamamoto has quit IRC13:58
stephenfingibi, jaypipes: Cool. Ping me whenever that is :)13:59
stephenfinShilpaSD: Hey, what's up?13:59
kashyapdansmith: Since you also seem to be amenable to the idea, mind adding an Acked-By or some such in the review?14:00
gibistephenfin: scheduler meeting starts now, I will ping you when it is over14:00
dansmithkashyap: I have it open, I'll look at it after I dig out from the morning14:00
*** Eran_Kuris has joined #openstack-nova14:00
dansmithjohnthetubaguy: you gonna hit it first?14:00
edleafeScheduler subteam meeting running now in #openstack-meeting-alt14:00
kashyapdansmith: Sure, take your sweet time.  I need to rework the unit tests anyway.14:00
dansmithkashyap: it would really help if it was passing unit tests :)14:01
kashyapdansmith: Also, additional context (that I cut down) is here: https://review.openstack.org/#/c/534384/2//COMMIT_MSG14:01
dansmithhah, yeah14:01
kashyapdansmith: Sure, don't open it until I fix the unit tests :-)14:01
*** pcaruana has quit IRC14:01
ShilpaSDStephenfin: hi, actually want to inform you that i am working on issue https://github.com/novnc/noVNC/issues/967, and for this updating nova\compute\manager.py for path as suugested on github issue14:02
ShilpaSDso is it okay to chang path in such way? or is there any way around?14:02
*** mgoddard_ has quit IRC14:02
johnthetubaguydansmith: yeah, looking at it now14:03
*** slaweq__ has joined #openstack-nova14:03
ShilpaSDhttps://github.com/openstack/nova/blob/d7c46b279686308f5431410bfccb3e40031e380a/nova/compute/manager.py#L505814:03
kashyapjohnthetubaguy: Many thanks.  ACK / NACK on the core change in driver.py would be useful.  (I'm still looking at what tests got broken & a new unit test.)14:04
*** amoralej|lunch is now known as amoralej14:04
stephenfinShilpaSD: Yeah, I tried to reproduce that and couldn't. I only needed to make one change to the configuration. See my notes here https://review.openstack.org/#/c/483994/14:05
*** efried has joined #openstack-nova14:05
stephenfinShilpaSD: It's the comments from March 6th14:06
kashyapjohnthetubaguy: But you're right that I should've retained the URL to the perf degradation analysis.  Feel free to call that out, I'm fixing it locally14:06
stephenfinShilpaSD: Perhaps I missed something though. Could you provide compare my steps to yours to see if this is the case?14:06
stephenfinjohnthetubaguy: Sure, that would be great. I'll go through and fix all those up now :)14:07
*** tianhui has quit IRC14:07
*** yassine has quit IRC14:07
*** tianhui has joined #openstack-nova14:07
*** slaweq__ has quit IRC14:08
openstackgerritMerged openstack/nova master: XenAPI: XCP2.1+ Swallow VDI_NOT_IN_MAP Exception  https://review.openstack.org/53841514:08
openstackgerritMerged openstack/nova master: Make nova build reproducible  https://review.openstack.org/55126914:08
ShilpaSDstephenfin: hi, i have gone through https://review.openstack.org/#/c/483994/9/nova/conf/vnc.py14:09
*** slagle has joined #openstack-nova14:09
ShilpaSDwe need to use vnc_lite.html14:09
ShilpaSDi have verified using vnc.html14:10
ShilpaSDand there we have issue14:10
stephenfinShilpaSD: Oh, ok. So if you use 'vnc_lite.html', it works as expected?14:10
stephenfinShilpaSD: Does 'vnc.html' work with noVNC < 1.0.0? If so, we might have a migration path to avoid people breaking when they upgrade to noVNC 1.014:11
ShilpaSDnot tested with vnc_lite.html yet14:11
ShilpaSDi have gone through your changes, and from there i thought you verified for vnc_lite.html, wait will check with vnc_lite and get back to you.14:12
*** slaweq__ has joined #openstack-nova14:13
stephenfinShilpaSD: So they renamed 'vnc_auto.html' to 'vnc_lite.html' in 1.0. Other than the rename, it works exactly the same as before14:13
*** jangutter has joined #openstack-nova14:14
stephenfinShilpaSD: However, if 'vnc.html' works for both 0.6 and 1.0, we might need your fix and then we can change the default from 'vnc_auto.html' to 'vnc.html'14:14
*** jpena is now known as jpena|lunch14:14
stephenfinThat means people could use either noVNC 0.6 or 1.0 with no other config changes, which would make upgrading much easier14:14
stephenfinLet me know what you find :)14:14
ShilpaSDstephenfin: okay, will test and get back to you14:15
*** pcaruana has joined #openstack-nova14:15
*** jangutter_ has quit IRC14:17
*** slaweq__ has quit IRC14:18
*** esberglu_ has joined #openstack-nova14:19
*** esberglu has quit IRC14:21
*** salv-orlando has quit IRC14:22
*** lei-zh has quit IRC14:24
*** slaweq__ has joined #openstack-nova14:24
*** amodi has joined #openstack-nova14:25
openstackgerritStephen Finucane proposed openstack/nova master: conf: Remove deprecated 'multi_instance_display_name_template' opt  https://review.openstack.org/49961214:27
sean-k-mooneystephenfin: is novnc running under a webserver? if so adding a redirect from vnc_auto.html to vnc_lite.html should be pretty simple14:27
*** moshele has quit IRC14:28
stephenfinsean-k-mooney: That...is not a bad idea14:28
stephenfinLemme have a look at how DevStack is deploying it14:28
arvindn05mriedem: https://review.openstack.org/#/c/541507/ - can you take a look at the latest patchset? I think it should address your concerns14:28
*** slaweq__ has quit IRC14:29
*** pcaruana has quit IRC14:30
*** beagles|brb is now known as beagles14:32
*** mlavalle has joined #openstack-nova14:33
*** slaweq__ has joined #openstack-nova14:34
*** tidwellr has joined #openstack-nova14:36
*** yamamoto has joined #openstack-nova14:38
*** slaweq__ has quit IRC14:39
*** sridharg has quit IRC14:39
openstackgerritStephen Finucane proposed openstack/nova master: conf: Remove deprecated 'allow_instance_snapshots' opt  https://review.openstack.org/49962114:40
*** jangutter has quit IRC14:40
openstackgerritStephen Finucane proposed openstack/nova master: conf: Remove 'db_driver' config opt  https://review.openstack.org/50848714:41
*** sridharg has joined #openstack-nova14:41
*** sahid has quit IRC14:41
cdentstephenfin++++++++++14:41
* bauzas raises fist at Credit Innovation Recherche14:41
openstackgerritStephen Finucane proposed openstack/nova master: conf: Fix indentation of database options  https://review.openstack.org/44309714:42
openstackgerritStephen Finucane proposed openstack/nova master: conf: Resolve TODOs in 'database'  https://review.openstack.org/39369514:42
openstackgerritStephen Finucane proposed openstack/nova master: conf: Resolve TODOs in 'database'  https://review.openstack.org/39369514:42
openstackgerritStephen Finucane proposed openstack/nova master: conf: Remove 'db_driver' config opt  https://review.openstack.org/50848714:42
bauzasheh, Credit Impot Recherche, rather14:43
*** jackie-truong has quit IRC14:43
*** yamamoto has quit IRC14:43
*** pcaruana has joined #openstack-nova14:43
stephenfinjohnthetubaguy: I think I've most of those rebased and the out-of-date blueprint line removed. If you fancy pushing them through, that would be appreciated :)14:44
*** slaweq__ has joined #openstack-nova14:44
*** gongysh has quit IRC14:44
johnthetubaguystephenfin: on a call, but will try hit those, do they still have some shared topic?14:44
stephenfinjohnthetubaguy: Sure. I kept the topic the same https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/centralize-config-options-queens14:44
edmondswstephenfin I had to manually rebase after you +Wd... can you take another look at https://review.openstack.org/#/c/539314/ ?14:45
*** mgoddard_ has joined #openstack-nova14:46
stephenfinedmondsw: Sure14:47
*** esberglu_ is now known as esberglu14:47
efriedmelwitt: The "runways" thing - is that going to be tracked on https://etherpad.openstack.org/p/rocky-nova-priorities-tracking or is there a separate etherpad?14:47
*** hongbin has joined #openstack-nova14:47
edmondswstephenfin ty sir14:47
* johnthetubaguy wonders about using storyboard for runways, and then runs away14:48
ShilpaSDstephenfin: Hi, tested vnc console access using 'vnc_lite.html' for version 1.0, its working without any changes at nova-compute services, and able to access console14:48
stephenfinShilpaSD: Excellent. So there's nothing more needed, if we decide to use that?14:49
ShilpaSDbut if configured 'vnc.html' for version 1.0, then require changes at nova-compute service14:49
stephenfinWhat about version 0.6?14:49
*** slaweq__ has quit IRC14:49
*** sar has quit IRC14:49
ShilpaSD0.6 not yet checked, will do that in next 5 min and get back to you14:49
stephenfin(y)14:49
ShilpaSDshould i use v v0.6.1 or v0.6.2?14:50
*** mdnadeem has quit IRC14:53
*** yamamoto has joined #openstack-nova14:53
*** yamamoto has quit IRC14:53
*** yamamoto has joined #openstack-nova14:53
ShilpaSDstephenfin: actually earlier we had 'vnc_auto.html', and that removed in currunt vnc 1.0 release, so we have to make configuration chnages14:53
*** slaweq__ has joined #openstack-nova14:54
stephenfinShilpaSD: Yup, that what's I found. What I'm suggesting is that maybe 'vnc.html' works in both 0.6 and 1.0. If so, we might start using that instead of 'vnc_auto' or 'vnc_lite'14:55
stephenfinAlso, use 0.6.2 I guess. Either would be OK though14:55
ShilpaSDokay, will check on 0.6.0 with 'vn.html' and get back to you with outcome14:56
ShilpaSD'vnc.html'*14:56
*** yamamoto has quit IRC14:58
*** slaweq__ has quit IRC14:59
*** lucas-hungry is now known as lucasagomes15:00
jaypipesbauzas, cdent: can you guys give me 45 minutes?15:01
bauzasefried: I don't see why it could be "madness" to accept operator's defined traits15:01
cdentjaypipes: you mean before continuing this topic? I can, sure15:01
bauzasthe munging logic should be very explicit15:01
jaypipesyes15:01
bauzasjaypipes: yup, I can hold15:01
* bauzas goes back to paper filling of shit15:01
* cdent makes coffee and snack15:02
gibijaypipes, stephenfin: so the scheduler meeting is over. I have about two hours left from my workday to jump on a hangouts about the numa aware vswitches15:03
stephenfingibi: I think jaypipes is busy for a bit so maybe once he's free? I've no other meeting scheduled for the day15:04
gibistephenfin: OK. I just noted down my boundaries :)15:04
*** slaweq__ has joined #openstack-nova15:04
stephenfingibi: Sure, we'll fit it in in that time :)15:05
*** jpena|lunch is now known as jpena15:09
*** jackie-truong has joined #openstack-nova15:09
*** slaweq__ has quit IRC15:09
ShilpaSDstephenfin: Hi, for 'vnc.html' with noVnc version 0.6.2 and websockify-0.8.0, it failed to access, error at do_handshake()15:12
stephenfinShilpaSD: Is that the same issue you saw with 1.0?15:12
openstackgerritStephen Finucane proposed openstack/nova master: Standardize '_get_XXX_constraint' functions  https://review.openstack.org/38507115:13
*** sidx64 has quit IRC15:13
openstackgerritStephen Finucane proposed openstack/nova master: conf: Move availability zones opts to a group  https://review.openstack.org/46246915:13
*** slaweq__ has joined #openstack-nova15:15
*** psachin has quit IRC15:16
*** tbachman has quit IRC15:17
ShilpaSDfor 1.0, https://github.com/novnc/noVNC/issues/96715:17
*** gjayavelu has joined #openstack-nova15:17
ShilpaSDactually issue for noVNC=v1.0.0-testing.215:17
openstackgerritStephen Finucane proposed openstack/nova master: objects: remove pagesize from __init__ of InstanceNUMATopology  https://review.openstack.org/48555315:19
ShilpaSDfor 1.0, token is not available as query parameter as well as it is not set in cookie.15:19
openstackgerritStephen Finucane proposed openstack/nova master: objects: remove related pinning from __init__ of InstanceNUMATopology  https://review.openstack.org/48555415:19
openstackgerritStephen Finucane proposed openstack/nova master: objects: remove cpuset_reserved from __init__ of InstanceNUMATopology  https://review.openstack.org/46603015:19
*** slaweq__ has quit IRC15:19
*** Nil_ has joined #openstack-nova15:19
ShilpaSDand if we configure 'vnc.html'15:20
*** READ10 has quit IRC15:20
stephenfinShilpaSD: So they're different issues?15:22
*** salv-orlando has joined #openstack-nova15:22
*** chyka has joined #openstack-nova15:23
*** slaweq__ has joined #openstack-nova15:25
*** yamamoto has joined #openstack-nova15:26
ShilpaSDstephenfin: No, its same. token is not getting as query parameter as well as it is not set in cookie.15:26
ShilpaSDfor vnc.html configuration15:26
ShilpaSDstephenfinr: please firstly confirm me that are we going to use vnc_lite.html or vnc_html for version 1.0?15:27
ShilpaSDtoken unavailable issue is with vnc.html only15:28
*** salv-orlando has quit IRC15:28
*** hemna_ has joined #openstack-nova15:28
*** sahid has joined #openstack-nova15:29
*** zhaochao has quit IRC15:29
*** slaweq__ has quit IRC15:30
*** yikun has quit IRC15:30
*** felipemonteiro has joined #openstack-nova15:31
*** yikun has joined #openstack-nova15:31
openstackgerritStephen Finucane proposed openstack/nova master: doc: Don't use single backticks in man pages  https://review.openstack.org/54088715:33
openstackgerritStephen Finucane proposed openstack/nova master: doc: Start using openstackdoctheme's extlink extension  https://review.openstack.org/54088815:33
stephenfinShilpaSD: So, this is my idea. We fix the issue you're seeing and change the default to 'vnc.html'. That means people can use the same configuration file with both 0.6 and 1.015:33
*** yamamoto has quit IRC15:34
stephenfinI don't know if that's a good idea but, in my mind, this would make for the easiest upgrade path for operators15:34
*** eharney has quit IRC15:35
*** slaweq__ has joined #openstack-nova15:35
*** tbachman has joined #openstack-nova15:36
sean-k-mooneystephenfin: since upgrades of openstack servers are supposed to be doable without any config changes from n to n+1 i think it makes sense15:36
*** yangyapeng has quit IRC15:36
stephenfinsean-k-mooney: Right. We could conceivably backport that fix too to make things even easier for the N to N+M cases15:37
*** yangyapeng has joined #openstack-nova15:37
ShilpaSDstephenfin: but earlier its 'vnc_auto.html' for 0.6, so configuration file changes are require with my fixes too15:37
sean-k-mooneystephenfin: well for n to n+2 it is expect that config change could be required but that should be achive via an itermediate change during n+115:38
*** eharney has joined #openstack-nova15:38
stephenfinShilpaSD: True. However, operators could make that change incrementally and keep noVNC versions the same. When they do decide to update noVNC, the same config file will work with both15:38
*** oanson has quit IRC15:38
stephenfinOtherwise they need to both update the config file and noVNC version in lockstep15:38
stephenfinThen again, maybe I'm overthinking this and the operator could just place a redirect in place, as sean-k-mooney suggested :)15:39
*** Eran_Kuris has quit IRC15:39
* stephenfin wonders what the difference between (vnc_auto|vnc_lite).html and vnc.html is15:39
*** slaweq__ has quit IRC15:39
sean-k-mooneystephenfin: redirect for appache/nginx or simlink for python webserver "should" work15:40
*** tbachman has quit IRC15:41
*** gyee has joined #openstack-nova15:41
*** yangyapeng has quit IRC15:42
*** eharney has quit IRC15:42
*** lpetrut has quit IRC15:44
*** eharney has joined #openstack-nova15:44
*** slaweq__ has joined #openstack-nova15:45
*** dtantsur|brb is now known as dtantsur15:45
*** tbachman has joined #openstack-nova15:46
sean-k-mooneystephenfin: looking at the two i think the lite version just uses less css/javascript effects15:47
stephenfinsean-k-mooney: So maybe the redirect is the best option?15:48
stephenfini.e. leave it to the deployment tool15:48
*** READ10 has joined #openstack-nova15:48
*** jackie-truong has quit IRC15:49
*** claudiub|2 has quit IRC15:49
*** slaweq__ has quit IRC15:50
*** slaweq has quit IRC15:50
ShilpaSDstephenfin: understood what you want to mentioned here, so for fix i am updating access URL at https://github.com/openstack/nova/blob/d7c46b279686308f5431410bfccb3e40031e380a/nova/compute/manager.py#L505815:50
ShilpaSDas below15:50
ShilpaSDaccess_url = '%s?path=websockify?token=%s' % (CONF.vnc.novncproxy_base_url, token)15:50
*** gjayavelu has quit IRC15:50
*** amotoki_ is now known as amotoki15:50
sean-k-mooneystephenfin: perhaps. the vnc.html seams to support audio and addtional key bindings + some transitions.15:50
ShilpaSDstephenfin: adding '?path=websockify', in access URL, is it okay?15:51
sean-k-mooneystephenfin: also i think it adds copy past support15:51
*** fragatina has joined #openstack-nova15:51
ShilpaSDits resolve my issue with 'vnc.html'15:51
*** gcb has joined #openstack-nova15:51
stephenfinShilpaSD: If that works, push up a patch and I can review15:52
stephenfinShilpaSD: Does that also work with 'vnc_lite.html'?15:53
stephenfinIf so, we could make it the default15:53
stephenfinnoVNC 0.6 is quite old. We could say we require it15:53
sean-k-mooneystephenfin: at least in devstack the version of novnc is set here https://github.com/openstack-dev/devstack/blob/master/stackrc#L606 so you could add a new config option that would set the defualt html file based on this15:54
*** slaweq has joined #openstack-nova15:55
jaypipescdent, bauzas: hey, back now. thanks for your patience.15:56
cdenthola15:56
jaypipesstephenfin, gibi: we could discuss stephenfin's thing tomorrow my morning if that works for you15:56
stephenfinsean-k-mooney: I had a patch up to change the devstack default but it's failing for reason's I haven't investigated15:56
ShilpaSDstephenfin: yes, it works with 'vnc_lite.html' also, will upload patch for you review and get back to you on same ASAP15:57
gibijaypipes: it works for me15:57
stephenfinjaypipes: Works for me too. Wanna stick something in someone's calendar15:58
*** damien_r has quit IRC15:58
* stephenfin is eager to write code that won't be immediately discarded :)15:58
jaypipesstephenfin: go for it.15:59
jaypipesstephenfin: jaypipes@gmail.com15:59
gibistephenfin: gibizer@gmail.com15:59
stephenfinTa!16:00
*** slaweq has quit IRC16:00
*** pasuder has quit IRC16:01
cdentjaypipes: was the stuff you wanted to talk with me about on friday eve this traits stuff, or something else?16:02
jaypipescdent: yeah16:02
ShilpaSDstephenfin: bye, leaving for the day16:02
stephenfinShilpaSD: Ciao. Let me know when you have that review up and I can review it16:03
ShilpaSDstephenfin: yes sure, working on TOX, once done, will do so16:03
*** karimull1 has quit IRC16:04
gibiKevin_Zheng: I just noticed that you published a spec https://review.openstack.org/#/c/551982/ for add-request-id-to-instance-action-notifications I think the bp is already approved as specless so we don't need to have a spec16:05
gibiKevin_Zheng: you can go for the implementation16:05
*** karimull has joined #openstack-nova16:05
*** slaweq has joined #openstack-nova16:05
*** udesale_ has joined #openstack-nova16:06
*** udesale has quit IRC16:06
cdentjaypipes: I guess bauzas is still in his pile of paperwork. I don't really have much to add to the topic than what was said on Friday and in those comments I menionted in the meetings.16:07
bauzascdent: well, I can stop paperworking, y'know16:07
jaypipescdent: my primary concern is how do we prevent situations where different actors are constantly overwriting each other...16:08
bauzashonestly, in between writing silly stuff and discussing with you folks, you got my opinion I guess16:08
bauzasMHO is that I agree with jaypipes and dansmith, I'd like to see the compute service reconciling traits provided by operators with traits set by the virt driver16:09
bauzasif that's the question16:09
cdentjaypipes: are we able to enumerate who the legit actors are?16:09
dansmithI thought we were going to have a hangout about this?16:09
jaypipescdent: for both traits and allocation ratios. either we have some agreement about what is always the source of truth for certain attributes, or we never have the automated agents (like resource tracker in compute manager) ever *delete* things... only add them. and then rely on manual deletes to remove things. but then we still need to solve the case of an agent continually adding some trait or setting some allocation ratio when it's been16:10
jaypipesoverridden or deleted by an external actor.16:10
dansmithIMHO, if the operator removes a trait owned by the virt driver directly in placement, the proper thing to do is overwrite that change16:10
dansmiththe operator has configured the virt driver with details about the supported cpu model, for example, and it makes no sense for her to then go tweak placement after the fact16:10
*** slaweq has quit IRC16:10
efriedMeaning the trait gets restored, yes?16:10
jaypipesdansmith: so the virt driver should know not to write CPU traits in that case, yes?16:11
*** udesale_ has quit IRC16:11
bauzasI was only thinking about additive traits16:11
dansmithjaypipes: no, the virt driver should be authoritative for cpu flag traits16:11
efriedNo, the opposite.  The virt driver is the Source of Truth for CPU traits.16:11
*** oanson has joined #openstack-nova16:11
efried(and others, for that matter)16:11
dansmithefried: right16:11
jaypipesdansmith, efried: ok. fair enough about cpu traits. what about allocation ratios?16:11
bauzasif the operator wants to remove a trait, why shouldn't we not accepting that ?16:12
bauzasit's his responsibility16:12
dansmithjaypipes: today, compute owns those, but I think who owns it in the future depends on what we do with our current config16:12
jaypipesbauzas: dansmith and efried are saying that the virt driver should own the cpu traits. and I don't disagree with that, BTW.16:12
bauzasthe compute service *is* the source of truth, not the virt driver IMHO16:12
*** pcaruana has quit IRC16:12
bauzasthat's where I see the difference16:13
dansmithbauzas: compute does not own cpu flag traits16:13
bauzasmeaning that some operator could want to hide a trait if they'd like16:13
jaypipesdansmith: right, and aggregate stuff complicates that a bit, too.16:13
dansmithbauzas: it does the setting based on what virt says, but it doesn't own the decision about which ones to set16:13
efried++16:14
bauzasdansmith: the problem I see with that approach is that we have different traits16:14
dansmithjaypipes: yup, but the ratio thing is pretty straightforward I think.. we just decide what we're going to do at first startup, and what to do on subsequent ones16:14
bauzasdansmith: some that we don't want the operator to modify, some we accept that16:14
jaypipesdansmith: ack. and I'm cool with your default_xxx_allocation_ratio suggestion.16:14
bauzasanyway, it's a set, right16:14
bauzas?16:14
dansmithbauzas: I don't understand what you're saying16:14
bauzasso, it's either an additive or a removal operation for a trait16:15
jaypipesdansmith: do you think the default_xxx_allocation_ratio solution warrants a spec?16:15
dansmithjaypipes: I bet mriedem does16:15
jaypipesyeah, makes sense16:15
jaypipesI'll hack one together quick.16:15
jaypipesscoped only to this narrow use case.16:16
dansmithmaybe it would help if I wrote some example code for how I think we should handle the trait thing?16:16
*** slaweq has joined #openstack-nova16:16
bauzasdansmith: the point I'm saying is that if we don't accept operators to remove a trait for a specific usecase (here a CPU feature), we shouldn't accept that for *any* trait too16:16
dansmithbetween virt traits, compute traits, and operator-set traits?16:16
dansmithbauzas: that makes no sense to me16:16
jaypipesdansmith: sure, that would help16:16
efriedIt seems to be a requirement for the admin to be able to set/unset at least *certain* traits.  And I personally don't want to get into a situation where we treat some traits differently from others.  Having to figure out and enforce which is which == nightmare.  So we need the admin-override mechanism to be generic.  And if they want to remove something that clearly should be owned by the virt driver (like a CPU trait), th16:16
jaypipes(the sample code)16:16
dansmithbauzas: virt can be authoritative for TRAIT_VMX and not be involved in TRAIT_SOMETHINGELSE16:16
bauzasdansmith: so the compute would know which resource is authoritative for a trait, then ?16:17
jaypipesefried: did you cut off that last sentence?16:17
efrieddansmith: IMO that's crazypants, to try to make lists of traits that can or can't be controlled by the admin, or are "owned" by virt vs. not, etc.16:17
dansmithbauzas: does't need to be by any set of complex rules, IMHO16:17
dansmithefried: I don't think we need a set of rules16:17
dansmithefried: I think the virt driver and compute services can just be authoritative for the ones they need to care about, and any others will be left alone16:18
edleafeefried: if the virt driver sets traits A,B,C, and the admin sets traits X,Y,Z, there is no problem, right? It's only when the admin wants to set/clear one of A, B, or C16:18
bauzasdansmith: I mean, how the compute can know whether it can accept an operator's defined list of traits to remove if one of those traits is TRAIT_VMX for example ?16:18
jaypipesefried: dansmith is saying "whatever the virt driver returns as traits should be authoritative for *those* traits"16:18
dansmithjaypipes: exactly16:18
efriedI don't see how that can work in practice.16:18
edleafejaypipes: yes16:18
efriedThinking about how the virt driver is going to discover traits...16:18
efriedIn the general case, it gets its info from the platform and translates to trait strings.16:19
dansmithefried: the virt driver is write-only for traits, right? it doesn't care what traits are currently set, it only generates a list of traits that *should* be set based on talking to the hypervisor16:19
efriedYes, but we're talking about the virt driver having to *know* about things it simply doesn't get from the platform as still being under its control.16:19
dansmithI'm not sure I understand what you mean, but.. I don't think I agree16:20
bauzasdansmith: so, if we accept some mechanism for the operator to remove some trait, it would just be a conditional in the compute service that would say 'don't touch what the virt driver returns", right?16:20
jaypipesefried: but dan isn't suggesting that the virt driver overwrite the complete set of traits, only that it will ensure that some traits are added to the provider16:20
efriedEspecially if some new CPU trait (or whatever) comes into existence that the platform didn't know about, but is still expected to be the authority on.16:20
bauzascan I backup for a second ?16:20
*** slaweq has quit IRC16:20
jaypipesefried: and if the admin added such a trait, the virt driver wouldn't remove it.16:20
bauzasafter all, do we need to provide some mechanism for an operator to *remove* a trait from what the compute service will report ?16:21
dansmithefried: are you concerned about the operator adding that new cpu trait to the compute node thinking it will magically make it work?16:21
dansmithbecause that's not a problem we need to solve, IMHO16:21
bauzasif we only allow the operator to give a list of human-defined traits, I don't see the problem16:21
efrieddansmith: No16:21
jaypipesbauzas: I believe what dansmith is saying is "no, we don't need such functionality".16:21
bauzasjaypipes: then, I agree16:21
cdentjust to repeat my concern, so it's on the table, before I forget: The thing that I wonder being a problem is if the virtdriver reports too many traits. Is that ever going to be an issue?16:21
bauzasadding a possibility to remove a trait opens a lot of problems16:22
efrieddansmith: But traits don't always equate to CPU features.16:22
bauzas(17:11:22) bauzas: I was only thinking about additive traits16:22
jaypipescdent: I don't think so, no.16:22
bauzasdefined by the operator16:22
jaypipesefried: yes, traits aren't always CPU features. and nobody is saying that the only thing the virt driver would return is CPU features.16:23
efriedIt sounds like dansmith is simply advocating that, whatever mechanism we provide for admins to add or remove traits, they can't remove traits that the virt driver sets.  (Or rather, they'll be restored the next time u_p_t runs.)  And I'm on board with that.16:23
dansmithefried: yes, that's what I'm saying16:23
dansmithbut I think that's all we need16:23
jaypipesefried: all that is being stipulated is that the virt driver will return a set of traits that it feels should always be set on the provider. it will not remove any traits manually added by an admin.16:23
dansmiththe only other interface we need for admins is placement16:23
bauzas+1 to the idea of keeping things somple16:24
bauzassimple16:24
efrieddansmith: Via osc, yah?16:24
efriedthat's sufficient?16:24
*** salv-orlando has joined #openstack-nova16:24
dansmithefried: yeah16:24
dansmithtotally sufficient, IMHO16:24
openstackgerritMatt Riedemann proposed openstack/nova-specs master: Spec for volume multiattach enhancements  https://review.openstack.org/55207816:25
jaypipesOK, I will attempt to summarize here.16:25
bauzasdansmith: but tbc, we agree on if the admin stupidely deletes a trait in the placement API, then on the next virt driver call, the compute service will add again that trait16:25
bauzasI now understand what you're saying16:25
efriedOkay, I'm on board now.  I think this works.  The stipulation that traits owned by the virt driver will magically reappear in some indeterminate amount of time - that's going to be a little weird to describe.  But if that's the only wrinkle, I can accept it.16:25
jaypipesbauzas: if it's a trait the virt driver reports, yep.16:25
bauzasjaypipes: that slight detail makes me a little wondering16:25
efriedYeah16:26
*** slaweq has joined #openstack-nova16:26
efriedIt's going to make the admin ask the question, "Okay, how do I find out which traits I'm not allowed to remove?"16:26
bauzasI don't see a reason why we shouldn't consider the compute service as the single source of truth for any compute-defined trait16:26
*** lajoskatona has quit IRC16:26
dansmithefried: I'm less worried about that,16:26
dansmithefried: because they're going to be adding some trait because a doc told them to, like "add a trait to this if it is a trusted PF"16:27
jaypipesefried: it's a valid concern but I'm not particularly worried about that either.16:27
* efried zeroes the counter of bugs opened by ops with titles like "Deleted trait reappears"16:27
efriedbut sure.16:27
dansmiththat is easy to document,16:27
bauzasdansmith: adding a trait is totally fine by me16:27
efrieddansmith: I agree it should be documented.  I don't agree it's easy to document.16:27
bauzasdansmith: that's the removal case that makes me wondering why we should special case the virt ones16:27
dansmiththe "what new stuff can I add" is a little harder, but really not a huge deal I think16:27
efriedBut we'll burn that bridge when we cross it.16:27
dansmithI'm writing a really simple example bit of code to explain what we just discussed I think16:28
jaypipesbauzas: if "special casing" == "the virt driver understands these traits should be applied to this provider", then I don't agree it's an issue.16:28
*** salv-orlando has quit IRC16:29
efriedbut wait16:29
bauzasjaypipes: no16:30
*** tssurya has quit IRC16:30
bauzasjaypipes: the special case I mentioned would be "the compute manager would see a removed trait, and only add it again to Placement API if that's coming from the virt driver"16:30
bauzasthat's the "if..." I wonder16:31
*** felipemonteiro has quit IRC16:31
*** slaweq has quit IRC16:31
*** gcb has quit IRC16:31
efriedWe still have the case where u_p_t is called, and the virt driver decides that it wants to assert a set of traits, but something has changed since the last time, and that set of traits is a *subset* of its previous.  Then it has no way to know that it should remove the extraneous traits.16:31
*** felipemonteiro has joined #openstack-nova16:31
bauzasfor me, the compute service should provide all the traits that are reported from various ways, and shouldn't care whether it's not existing in Placement or not16:31
jaypipesefried: what we're saying is that it should never "remove the extraneous traits".16:31
bauzas++16:32
efriedjaypipes: And that's a problem.16:32
dansmithefried: wait for my example code16:32
cdentjaypipes: that's difficult in the cluster virt drivers16:32
efriedBecause something may have changed that legitimately warrants the removal of such a trait.16:32
cdentwhere hardware is added on the fly, or hot pluggable hardware16:32
efriedOtherwise why would we be bothering to do this in a periodic?16:32
*** yamamoto has joined #openstack-nova16:32
efriedcdent: Yes, or *removed*16:32
cdentyes16:32
*** damien_r has joined #openstack-nova16:33
efriedSo I go back to asserting this doesn't work for the general case.16:33
jaypipesefried: "the general case" <-- what is that?16:34
efriedjaypipes: I just mean "for all cases".16:34
edleafeIf an admin wants to "remove" a trait FOO set by the virt driver, she could add a CUSTOM_FOO_BAD trait, and then make that a forbidden trait16:34
efriededleafe: I think we're past that one.  It doesn't have a realistic use case, most likely.16:35
edleafeefried: good16:35
*** slaweq has joined #openstack-nova16:36
*** yangyapeng has joined #openstack-nova16:37
efrieddansmith, jaypipes: Specifically the case I'm talking about is, for example, hot-pluggable storage.  Let's say you start with some disk.  Virt driver presents inventory of DISK_GB and trait STORAGE_DISK_SSD.  Then you pull out the disk.  The next u_p_t needs to be able to remove the DISK_GB inventory *and* remove the STORAGE_DISK_SSD trait.  With this design, it can't do the latter.  The admin would have to do it manually.16:37
jaypipesefried: it's not that I don't see your use case (for example, dynamically marking some child providers representing a PF with a CUSTOM_TRUSTED trait or something). But I also don't necessarily think that what dansmith is proposing would *preclude* us from moving in a more complicated direction if and when such a direction was determined to be required.16:37
*** yamamoto has quit IRC16:38
dansmiththis is what I think we need: https://pastebin.com/mM6NMzQ416:39
*** ragiman has quit IRC16:39
dansmithnote the operator's traits are untouched, yet the virt and compute-owned traits are asserted or de-asserted as things change16:40
*** slaweq has quit IRC16:41
cdentoh that's interesting16:41
*** yangyapeng has quit IRC16:41
efrieddansmith: What I'm asserting is that the virt driver has no way of knowing it wants to -SOMETHING16:41
cdentbut can/does that interop with how u_p_t is planned to behave16:42
*** chyka has quit IRC16:42
*** ygl has joined #openstack-nova16:42
yglhi all16:42
dansmithefried: it totally does16:42
*** chyka has joined #openstack-nova16:42
efriedcdent: What we decided on DublinFriday is that we're going to merge u_p_t as currently written and then bolt this on after.16:42
*** jpena is now known as jpena|brb16:42
jaypipesdansmith: that's essentially what my traits:always and traits:ignore in the provider config file format were doing. :)16:42
*** tssurya has joined #openstack-nova16:42
dansmithefried: I assert we don't have to worry about cases where the operator adds a trait to an x86 compute node of TRAIT_CPU_POWER7_THINGY16:43
ygli want to launch a vm with a dummy nic interface without an IP assigned to it . can someone help me how to do it please16:43
jaypipesdansmith: but clearly I don't segregate between what the compute and the virt think of as asserted/removed16:43
efriedygl: Try #openstack16:43
dansmithjaypipes: this is not always and ignore, this is always and remove, or something16:43
jaypipesdansmith: understood.16:43
dansmithjaypipes: and this is exposed from the virt driver, not encoded in a separate editable file16:44
jaypipesdansmith: would this be exposed as a config option (or 2 options)?16:44
dansmithjaypipes: no16:44
efrieddansmith: I'm not talking about the admin adding traits - we already decided she gets to do that.  I'm talking about a trait the virt driver needs to remove because e.g. someone hot-unplugged a disk.16:45
dansmithjaypipes: the virt driver would return things like this, which may vary based on virt driver config and talking to the hypevisor16:45
efriedThe virt driver operates by discovering what it has and asserting inventory/traits accordingly.16:45
jaypipesk16:45
efriedIf it discovers at time T and has a disk, it will assert some DISK_GB inventory and the STORAGE_DISK_SSD trait.16:45
jaypipesdansmith: a perfectly satisfactory solution.16:46
dansmithjaypipes: this is what I was describing from my corner on friday while we were discussing this16:46
*** slaweq has joined #openstack-nova16:46
efriedThen it discovers at time T+1 and it doesn't have a disk; it will not assert DISK_GB inventory (which works, because it's the only source of inventory info) and it will not assert the STORAGE_DISK_SSD trait.16:46
efriedBut it *doesn't* know that it needs to *de*assert the STORAGE_DISK_SSD trait.16:46
efriedBecause it has no memory that it asserted it at time T.  It just knows it isn't there now.16:47
*** chyka has quit IRC16:47
dansmithefried: I completely don't understand that16:47
jaypipesdansmith: yes, I recognize the +/- syntax now. just didn't have in my mind how the virt driver would expose this (automatically vs. config-based)16:47
dansmithjaypipes: ack16:47
dansmithefried: if you as a virt driver ever expose trait FOO, then you need to de-assert FOO if you determine there is no reason to assert it, right?16:47
efriedThat goes exactly back to my earlier statement about how the virt driver would have to know the full set of traits it *might* be responsible for, and then what subset of those it thinks should be set, so that it can explicitly deassert the remainder.16:49
dansmithwhy is that unreasonable?16:49
dansmithit doesn't have to be the full set of traits that any virt driver might expose,16:49
dansmithjust the ones _it_ might expose16:49
dansmithwe could make a turbo simple data structure that they all use, which requires them to declare any traits they may want to use, then assert the ones it finds, and the rest will be de-asserted16:50
dansmithto avoid leaking some asserted ones that are never de-asserted16:50
dansmithI must be missing why this is a hard problem16:50
bauzasdansmith: so the virt driver would provide all the possible CPU traits, either with a "+" or a "-" prefix, depending on what it knows to support ?16:50
dansmithbauzas: all the cpu traits it knows about yeah16:50
bauzasthat would work then16:51
bauzasokay, I see your idea16:51
dansmithbauzas: it doesn't need to worry about traits for PPC processors, for example16:51
*** fragatina has quit IRC16:51
*** slaweq has quit IRC16:51
dansmithif the operator added one of those then, sucks for that operator16:51
bauzasyeah, but it would still report "negative" traits16:51
dansmithyeah16:51
bauzascool with me then16:51
dansmithso if you changed the cpu_model later, it would sync up with all the flags that are now legit16:52
bauzasbased on the specific compute version it runs16:52
yglbauzas: can you help me with my issue please if you can16:52
dansmithsure, but as time goes forward, the cpu flag set only grows16:52
bauzasthat's a reasonable assumption16:52
dansmithand for non-cpu flag things,16:52
yglbauzas: i want to launch a vm with a dummy nic interface without an IP assigned to it16:53
dansmithit becomes a compatibility thing kinda like our db schema,16:53
bauzasand honestly, who cares if the operator sets a trait that the virt driver doesn't know ?16:53
dansmithwhere you need to not just add/remove traits willy-nilly over releases without doing some cleanup16:53
dansmithygl: this channel is for development, see topic please16:53
bauzasthe operator would suck less if they would use a custom trait for that16:53
bauzasyeah, I like that idea actually16:53
ygldansmith: i tried other channels but they r not responding16:53
bauzasbecause we explicitly then provide what the virt driver knows16:53
dansmithbauzas: yup, we could have an audit mode where the compute node logs any traits it didn't calculate, which should ideally be just the ones the operator set16:53
*** tssurya has quit IRC16:54
dansmithso any that got leaked over time would be easy to identify16:54
*** chyka has joined #openstack-nova16:56
*** chyka has quit IRC16:56
yglbauzas: sorry to disturb you. can you help me with my issue, if you can16:56
*** slaweq has joined #openstack-nova16:56
*** chyka has joined #openstack-nova16:57
efriedNote that the ironic virt driver is gleaning traits from inspector.  So that interface will need to change: either to support +/-; or to add a separate "get all the traits I might care about" call.16:57
*** oanson has quit IRC16:57
*** awaugama has quit IRC16:57
dansmithefried: the interface from the ironic driver to ironic?16:57
efriedyeah16:57
sean-k-mooneydansmith: the cpu traits would be reported on the CPU resouce providers not the compute node correct nulless the cpu inventory is under the compute node. just thinking of the numa case where the inventory would be per numa node16:57
dansmithefried: depends on the traits I guess, and what is going on right now.. if the ironic driver is exposing traits that don't need to be deleted later, then it won't really matter16:58
dansmithsean-k-mooney: yeah, that doesn't change this though16:58
sean-k-mooneydansmith: yep just checking. i would expect most operator traits to be applied to the compute node RP but they may want to tag sub resouce providres also.16:59
dansmithsean-k-mooney: yeah, network-related traits will need to be below compute node17:00
dansmithefried: ah, looks like we're just proxying any trait they want?17:00
efriedyup.17:00
*** admin__ has joined #openstack-nova17:00
dansmithefried: yeah, well, that kinda sucks, but it's resolvable I think17:00
efriedAssuming we go forward with this, all the merge logic needs to be handled by the individual virt drivers.  Unless we're going to invent some interface outside of u_p_t.17:00
efriedexcept for get_traits, which I freakin knew was going to bite us in the ass.17:00
dansmithI guess we could also provide the current set of traits to the virt driver so it gets to decide if it thinks any of the ones set are important to ack or nak17:01
*** slaweq has quit IRC17:01
*** salv-orlando has joined #openstack-nova17:01
efrieddansmith: That's what we do.17:01
efriedin u_p_t17:01
dansmithefried: I don't think the virt drivers should be doing merging in the general case17:02
*** lpetrut has joined #openstack-nova17:02
dansmithefried: just being write-only for the majority of things, this ironic thing notwithstanding17:02
efrieddansmith: Then we need nontrivial redesign of u_p_t.17:02
dansmithwell I dunno what to say dude.. this is clearly a thing we missed in the design :)17:02
efriedThe way it's currently designed: The resource tracker builds the ProviderTree, which includes all the providers' traits as known by placement, and passes that to u_p_t.  The virt driver mungs the ProviderTree as it sees fit and then returns.  Then resource tracker flushes those changes back to placement.17:03
*** moshele has joined #openstack-nova17:03
dansmithyeah, well, we can provide merging routines to the virt drivers to use on the tree,17:03
*** yamahata has quit IRC17:03
dansmithand expect that most just use those17:04
efriedSure we can.  But the merging still has to be the responsibility of the virt driver.17:04
sean-k-mooneyefried: perhaps but it would be nicer if it was the respociblity of the compute manager or some other componet just above the virt driver so it could be shared acrosss all virtdirvers17:05
dansmithsean-k-mooney: yeah, that's what I'd like, to expose some augmented topology from the virt driver so the compute can update the tree,17:05
efriedsean-k-mooney: And I'm saying that would require some semantic that's not compatible with u_p_t as designed.17:05
efriedThe ProviderTree business was so we didn't have to have separate virt driver methods for get_inventory, get_traits, get_aggregates, and (this is the main one) somehow_structure_the_provider_tree_hierarchy17:05
dansmithbut it sounds like we've already exposed this all the way down17:05
*** damien_r has quit IRC17:06
bauzasefried: dansmith's proposal patch is simple17:06
dansmithso, whatever, we can argue about cleaning that up later if we want, unrelated to fixing this merging thing17:06
efrieddansmith: The code isn't merged.  We could still rip it all out and change our minds.  But I believe we'd be getting a lot more complicated.17:06
admin__mridem: http://logs.openstack.org/24/550324/2/gate/legacy-tempest-dsvm-neutron-full/211271c/job-output.txt.gz#_2018-03-12_16_02_09_694703 failed17:06
bauzasit doesn't require to modify what we currently have17:06
bauzasit's just a convention17:06
dansmithefried: oh, I thought you meant they're already getting the tree17:06
*** slaweq has joined #openstack-nova17:07
*** admin__ has quit IRC17:07
dansmithI dunno, exposing that all the way down isn't my preference, but if that's what we've agreed on so far, I wouldn't hold it up because I don't like it17:07
bauzaslike, in a nested RP world, I'd just see the tree with the root RP having a set of traits, each of those be ether prefixed by plus or minus17:07
bauzasor, say a NUMA node17:07
dansmithwe just need to integrate this wrinkle at least17:07
*** vivsoni has joined #openstack-nova17:07
dansmithbauzas: it's more complicated than that17:07
efrieddansmith: The code was written in Q, but the series didn't merge in time.  So we wrote and approved the spec for R (it didn't have a bp/spec in Q - was just kinda folded into the NRP work).  The series starts here: https://review.openstack.org/#/c/537648/17:07
dansmithwe need a full topology back from the virt driver with traits at every level It hink17:08
dansmithack17:08
bauzasmmm17:08
bauzasIIRC, the proposal is the virt driver that passes a tree that has RPS with traits attached, right?17:08
efrieddansmith: Yes, the full topology.  Does that topology include +/- prefixes?  In which case it's not a ProviderTree but something different (ProviderTreeDelta?)17:08
*** damien_r has joined #openstack-nova17:08
bauzasa trait is attached to a RP, right?17:09
dansmithefried: in the model you have proposed,17:09
sean-k-mooneydansmith: you may not have traits at all levels but there is noting preventing that either. it just depends on the resouces but in all likely hood most RPs will have traits17:09
efrieddansmith: Otherwise, like I say, we have to have granular methods that return deltas for traits, inventories, aggregates, and (somehow) the tree structure itself.17:09
bauzasthe fact that the RP is a child or a root RP, is just a detail17:09
dansmithefried: we just need a provider.merge_traits(my_assertions) method that takes the +/- things right?17:09
bauzasyeah17:09
bauzasthat's a compute method17:10
jaypipesefried: we would want to change the ProviderTree.set_traits() stuff to use the merge traits +/- approach17:10
bauzasno need to change the virt driver interface17:10
efrieddansmith: Yes.  And virt drivers have to use it.  Which is okay with me.17:10
dansmithefried: where provider would be any element in the tree17:10
jaypipesdoh, jinx17:10
dansmithefried: yeah, I think that's fine17:10
bauzasthe merge_traits() thing is a compute manager method, right?17:10
efrieddansmith: But to clarify, it still means the virt driver is responsible for merging traits.17:10
dansmithbauzas: no17:10
jaypipesbauzas: no. ProviderTree17:10
efried^17:10
bauzasmeh to that17:11
dansmithefried: understood, and I don't like that as much, but I'm willing to defer that argument until later :)17:11
*** felipemonteiro_ has joined #openstack-nova17:11
bauzasI mean, the caller would be the compute manager ?17:11
dansmithefried: so I still don't think this is a major disruption, just a change in protocol a little bit17:11
dansmithbauzas: in some cases17:11
*** slaweq has quit IRC17:11
dansmithbauzas: but not the ones we're talking about here17:11
*** lucasagomes is now known as lucas-afk17:11
bauzasI'm missing some cases then17:11
efrieddansmith: Not really even that.  The only thing we would need to change about what's proposed is the u_p_t docstring.17:11
bauzasbut I don't want to rathole17:11
efriedAdding the ProviderTree.merge_traits method is a nice-to-have, but until then, u_p_t could still do that manually.17:12
bauzasoh, unrelated, I'll take a couple of days off17:12
dansmithefried: um, not sure about that17:12
*** Swami has joined #openstack-nova17:12
jaypipesbauzas: technically, the resource tracker is the caller of update_provider_tree() on a virt driver, but the goal is to have update_provider_tree() API be what other agents (including Neutron) use for managing their hierarchy of providers, inventories, and traits.17:12
dansmithefried: but get some code up so we can argue over that, which will be more clear right?17:12
bauzasjaypipes: dansmith: cdent: mriedem: others: I'll be on PTO thursday to monday included17:12
openstackgerritMatthew Edmonds proposed openstack/nova master: Fix N358 hacking check  https://review.openstack.org/54767017:12
* dansmith has a call in a few minutes17:12
jaypipesbauzas: ack17:12
bauzasdisneyland...17:12
bauzasnot for the dog this time17:13
efrieddansmith: I'm rebasing the u_p_t series now.  I'll throw a comment in the appropriate spot.  And then at some point I guess I can propose the ProviderTree.merge_traits method.17:13
dansmithokay17:13
bauzasjaypipes: ack, yeah, makes sense17:13
* efried 's cup runneth over17:13
bauzasit's 6:13pm here, my stomatch starts to tell me it's time to hang off17:14
bauzasbut I'll be back tonight17:14
bauzas\o17:14
jaypipesciao17:14
*** felipemonteiro has quit IRC17:14
* bauzas has a couple of specs to review tonight17:14
*** edmondsw has quit IRC17:15
*** edmondsw has joined #openstack-nova17:15
*** felipemonteiro_ has quit IRC17:17
*** slaweq has joined #openstack-nova17:17
*** felipemonteiro_ has joined #openstack-nova17:17
*** moshele has quit IRC17:17
*** pcaruana has joined #openstack-nova17:18
*** edmondsw has quit IRC17:19
*** slaweq has quit IRC17:20
*** slaweq has joined #openstack-nova17:21
*** AlexeyAbashkin has quit IRC17:23
openstackgerritEric Fried proposed openstack/nova master: New-style _set_inventory_for_provider  https://review.openstack.org/53764817:23
openstackgerritEric Fried proposed openstack/nova master: SchedulerReportClient.update_from_provider_tree  https://review.openstack.org/53382117:23
openstackgerritEric Fried proposed openstack/nova master: Use update_provider_tree from resource tracker  https://review.openstack.org/52024617:23
openstackgerritEric Fried proposed openstack/nova master: Fix nits in update_provider_tree series  https://review.openstack.org/53126017:24
openstackgerritEric Fried proposed openstack/nova master: Move refresh time from report client to prov tree  https://review.openstack.org/53551717:24
openstackgerritEric Fried proposed openstack/nova master: Make generation optional in ProviderTree  https://review.openstack.org/53932417:24
openstackgerritEric Fried proposed openstack/nova master: WIP: Add nested resources to server moving tests  https://review.openstack.org/52772817:24
*** jpena|brb is now known as jpena17:24
*** ygl has quit IRC17:24
efried^ rebase.  The first patch should still be good to go regardless.  The next one still needs some work.17:26
*** pcaruana has quit IRC17:27
mriedemis someone going to summarize all of the 'merge traits' discussion/decisions/etc from today into the ML per the retrospective at the ptg?17:28
*** fragatina has joined #openstack-nova17:28
*** sridharg has quit IRC17:29
openstackgerritChris Dent proposed openstack/nova master: Move resource class fields  https://review.openstack.org/54004917:29
openstackgerritChris Dent proposed openstack/nova master: Move resource provider objects into placement hierarchy  https://review.openstack.org/55152817:29
openstackgerritChris Dent proposed openstack/nova master: Reparent placement objects to oslo_versionedobjects  https://review.openstack.org/55152917:29
openstackgerritChris Dent proposed openstack/nova master: Optional separate database for placement API  https://review.openstack.org/36276617:29
openstackgerritChris Dent proposed openstack/nova master: Isolate placement database config  https://review.openstack.org/54143517:29
openstackgerritChris Dent proposed openstack/nova master: Move placement exceptions into the placement package  https://review.openstack.org/54986217:29
*** damien_r has quit IRC17:30
*** sahid has quit IRC17:30
efriedmriedem: Well, I was planning to propose an update to the update-provider-tree spec.17:30
openstackgerritEd Leafe proposed openstack/nova master: Add 'member_of' param to GET /allocation_candidates  https://review.openstack.org/55209817:31
edleafedansmith: ^^17:31
edleafedansmith: Still have to do tests, but I wanted jaypipes to review the SQL join code17:31
efriedmriedem: Once I've put that up, I can write something up for the ML.17:31
*** eharney has quit IRC17:33
*** oanson has joined #openstack-nova17:35
*** slaweq__ has joined #openstack-nova17:37
*** slaweq__ has quit IRC17:37
*** yamahata has joined #openstack-nova17:43
*** wolverineav has joined #openstack-nova17:43
*** imacdonn has quit IRC17:43
*** yamahata has quit IRC17:44
*** imacdonn has joined #openstack-nova17:44
*** yamahata_ has joined #openstack-nova17:44
*** oanson has quit IRC17:44
*** chyka has quit IRC17:44
*** oanson_ has joined #openstack-nova17:44
*** chyka has joined #openstack-nova17:45
*** oanson_ is now known as oanson17:46
efrieddansmith: Are we going to have this same issue for aggregates?17:47
*** deepak_ has quit IRC17:47
efriedRephrase: We're going to have this same issue for aggregates.17:47
efriedI hesitate to wonder if we've got the same issue for inventories.17:47
efriedGolly, yes, allocation_ratio...17:47
*** slaweq__ has joined #openstack-nova17:48
*** slaweq__ has quit IRC17:48
sean-k-mooneyefried: same issue?17:48
*** slaweq has quit IRC17:49
*** itlinux has joined #openstack-nova17:49
*** chyka has quit IRC17:49
efriedsean-k-mooney: Yeah; does the operator get to make changes to a provider's aggregates?17:49
*** edmondsw has joined #openstack-nova17:49
efriedSince we're mirroring host aggregates, the answer is clearly yes; though those are going to be funneled through the compute service somehow.17:50
sean-k-mooneyefried: they get to create new ones. not sure they are allowed to modify existing ones17:50
efriedsean-k-mooney: Then we have exactly the same problem - how does the virt driver know it gets to remove an aggregate association?17:50
sean-k-mooneyit cant unless it created it17:51
*** suresh12 has joined #openstack-nova17:51
*** slaweq has joined #openstack-nova17:51
sean-k-mooneyother service can create aggregates also not just the operator17:51
*** slaweq__ has joined #openstack-nova17:51
*** slaweq___ has joined #openstack-nova17:52
arvindn05mriedem: https://review.openstack.org/#/c/541507/ - can you take a look at the latest patchset? I think it should address your concerns17:52
*** r-daneel has quit IRC17:52
*** pcaruana has joined #openstack-nova17:53
*** slaweq__ has quit IRC17:54
*** slaweq__ has joined #openstack-nova17:54
*** slaweq has quit IRC17:56
*** vivsoni has quit IRC17:57
*** slaweq__ has quit IRC17:58
*** felipemonteiro__ has joined #openstack-nova17:58
*** deepak_ has joined #openstack-nova17:59
*** chyka has joined #openstack-nova17:59
*** RaoulHC has joined #openstack-nova18:00
*** dave-mccowan has quit IRC18:00
*** dtantsur is now known as dtantsur|afk18:01
*** felipemonteiro_ has quit IRC18:02
*** dave-mccowan has joined #openstack-nova18:04
openstackgerritHongbin Lu proposed openstack/nova master: Skip placement on rebuild in same host  https://review.openstack.org/54635718:04
*** slaweq has joined #openstack-nova18:05
*** slaweq has quit IRC18:06
*** tesseract has quit IRC18:06
efriedI don't suppose there's a way to permalink an etherpad line18:06
*** suresh12 has quit IRC18:07
*** slaweq has joined #openstack-nova18:07
*** slaweq has quit IRC18:07
sean-k-mooneyefried: i dont think the lines have css id so no18:07
efriedsean-k-mooney: Or even permalink the etherpad as a whole at a point-in-time.18:08
*** suresh12 has joined #openstack-nova18:08
edmondswefried I wouldn't think so18:08
sean-k-mooneyefried: you could use http://archive.org/web/18:08
efriedmmm, nice18:08
sean-k-mooneyefried: make a snap shot of the doc then link to the snap shot and give the line number18:09
*** sambetts is now known as sambetts|afk18:09
efriedsean-k-mooney: Yeah, I'll pastebin just the relevant section.18:09
efriedI guess.18:09
sean-k-mooneyefried: you can create readonly share links in etherpad like this one https://etherpad.openstack.org/p/r.2bb9e3053658b6ddf5e73d31045dcfba18:11
*** Swami has quit IRC18:11
*** Swami_ has joined #openstack-nova18:11
*** Swami_ has quit IRC18:11
*** Swami has joined #openstack-nova18:12
efriedsean-k-mooney: That doesn't actually freeze it.  Just makes it so you can't edit.18:13
efriedsean-k-mooney: Changes still show up.18:13
*** slaweq has joined #openstack-nova18:13
sean-k-mooneyefried: ah ok ya maybe with the version specified https://etherpad.openstack.org/p/r.2bb9e3053658b6ddf5e73d31045dcfba/timeslider#4330218:14
sean-k-mooneystill pastbin might be cleaner18:14
efriedaha, #timeslider is probably what I want.18:14
*** slaweq has quit IRC18:14
efried'cept no line numbers!18:14
efriedgaaahhh!18:14
*** gjayavelu has joined #openstack-nova18:15
*** felipemonteiro__ has quit IRC18:15
*** yangyapeng has joined #openstack-nova18:16
*** felipemonteiro__ has joined #openstack-nova18:16
sean-k-mooneyefried: ya all the etherpads are version controled but yes the etherpad line number are added with javascipt renderer and are not part of the document18:16
*** gouthamr has quit IRC18:16
openstackgerritJay Pipes proposed openstack/nova-specs master: Support default allocation ratios  https://review.openstack.org/55210518:18
jaypipesdansmith: ^18:18
-openstackstatus- NOTICE: Most jobs in zuul are currently failing due to a recent change to zuul; we are evaluating the issue and will follow up with a recommendation shortly. For the moment, please do not recheck.18:18
*** ChanServ changes topic to "Most jobs in zuul are currently failing due to a recent change to zuul; we are evaluating the issue and will follow up with a recommendation shortly. For the moment, please do not recheck."18:18
*** ralonsoh has quit IRC18:20
dansmithefried: I don't see the same problem with aggregates18:20
dansmithefried: and aggregate changes wouldn't go through the compute service18:20
*** gouthamr has joined #openstack-nova18:21
dansmithefried: adds or removes would get mirrored to placement,m18:21
*** yangyapeng has quit IRC18:21
dansmithbut if the operator changed them in placement, we wouldn't necessarily un-do that with a sync based on what jaypipes has proposed as I understand it18:21
*** slaweq has joined #openstack-nova18:22
*** eharney has joined #openstack-nova18:22
*** slaweq has quit IRC18:23
efrieddansmith: I think, as with the "driver capabilities" traits, the mirrored host aggregates will be a special case controlled by compute manager (!virt).  But I mean in general.  If an admin adds/removes an aggregate in placement directly, how does virt know not to remove/restore that aggregate association?18:23
sean-k-mooneydansmith: i thikn efried main concern was how does nova know if it is allowed to remove a RP it created from an aggregate. my answer would be unless it created the aggregate it should not add or remove RPs from it18:23
*** janki has quit IRC18:23
*** slaweq has joined #openstack-nova18:24
*** slaweq has quit IRC18:24
dansmithefried: the compute manager can't know what aggregate it's in18:24
dansmithefried: it can't even access the database that has those details, nor talk to conductors that can18:25
*** amoralej is now known as amoralej|off18:25
efriedokay, sorry, "...special case controlled by conductor".  But the point about the general case remains.18:25
dansmithefried: I'm missing something18:26
efrieddansmith: I.e. do we need to implement ProviderTree.merge_aggregates ?18:26
dansmithefried: at steady state, nova wouldn't add or remove providers from aggregates18:26
sean-k-mooneyefried: in the general case nova cant assume it own RPs or Aggregate in placement18:26
dansmithsean-k-mooney: agree18:26
efriedsean-k-mooney: Disagree.  Sigh.18:26
sean-k-mooneyefried: well the simple case would be that neutron may want to add compute nodes to a aggregate to model there availablity zones which do not have to map direclty to novas18:27
dansmithefried: can you state that disagreement as a full statement? like, you disagree that...18:27
sean-k-mooneysame for cinder18:27
dansmithsean-k-mooney: yep18:27
dansmithsean-k-mooney: or the operator may do so for any other reason18:27
*** moshele has joined #openstack-nova18:28
*** mgoddard_ has quit IRC18:28
dansmithefried: I just wonder which part you disagree with18:28
sean-k-mooneydansmith: yes for failure domains suchs as power or ha failover or other usecse that openstck can discover18:28
dansmithsean-k-mooney: yup18:28
sean-k-mooneys/ can discover/ can't discover/18:29
*** RaoulHC has quit IRC18:29
efriedThe virt driver knows of a certain set of aggregates of which its providers (the ones it "owns") are members.  What it does not necessarily know about is the set of aggregates of which its providers are *not* members.  Today, as designed, u_p_t is supposed to just overwrite aggregate associations.  So there's no affordance for outside agents to manipulate them.18:29
*** dtruong has joined #openstack-nova18:30
efriedThe question is: do we need such affordance?  At least for the host agg mirroring, it sounds like it.18:30
dansmithefried: ah are you talking about an aggregate around a compute node and its children, for example?18:30
dansmithefried: not equal to nova's host aggregates?18:30
sean-k-mooneyefried: yes we do for the neutron/cinder case and for failure domains. the virt driver should simple add/remove aggregates it owns but not overrite all aggregates for a RP18:31
dansmithright18:31
efrieddansmith: Could be intra-tree; could also be inter-tree (e.g. a shared storage pool).  The argument applies to the host agg mirrors as well as whatever else we want to do with aggs.18:31
efriedI.e. if the virt driver is not the single SoT for agg associations of the RPs it "owns", we have to have the exact same discussion as we just did with traits.18:32
sean-k-mooneyefried: for a shared storage pool nova does not really own that RP cinder likely does18:32
efriedsean-k-mooney: Sometimes.  PowerVM SSPs will be (co-)owned by the virt driver(s).18:32
dansmithefried: well, I agree the virt driver can draw its own aggregates around things and manage those itself, and maybe tell compute that it should join an aggregate for some shared storage it's connected to,18:32
dansmithbut nothing more authoritative than that18:32
efrieddansmith: In which case we need to amend the u_p_t charter for aggregates in the same way we just did for traits.  Because as currently designed, virt just overwrites the aggregates.18:34
dansmithefried: okay I'm not sure how that was ever considered a reasonable thing to do, but.. yes, agree it needs to not do that :)18:34
efriedAnd we have the same quandary as to which aggregates the virt driver "owns", so it knows which ones to de-assert.18:34
*** lbragstad has quit IRC18:35
sean-k-mooneyefried: this feels like a case of placement is used almost entirely by nova today and we need to make it support other services.18:35
efriedAnd I contend that that's a much stickier problem than the traits one.  Because we don't have a static list of agg UUIDs that virt "might" use.18:35
sean-k-mooneyefried: that said we should have hit this already with routed networks in neutron18:35
dansmithefried: okay, I guess I'm surprised that aggregate membership is part of provider tree, but fair eough18:35
*** jackie-truong has joined #openstack-nova18:35
efriedsean-k-mooney: We're not talking about changing anything on the placement side.  Just nova's consumption thereof.18:35
dansmithefried: right, if it's doing that, then it's going to need some persistence to keep track of which ones it has created18:36
dansmithsean-k-mooney: right his point is that we need to not be so aggressive in nova,18:36
dansmither, efried :18:36
dansmithbecause we can't trample what other users would have done, human or otherwise18:36
sean-k-mooneyefried: yes but neutron is modeling routed netwoks in placement today using aggreagtes to express what node can connet to routed subnets correct?18:36
efriedI don't know that answer.  (But probably not "today" if you mean "code that's merged".)18:37
dansmithit doesn't matter,18:37
dansmiththat's a thing that will happen18:37
dansmithneutron, cinder, et al18:38
*** awaugama has joined #openstack-nova18:38
sean-k-mooneyefried: well neutorn has been tracking routed network in placement since pike i think18:38
efriedsean-k-mooney: By creating placement aggregates around compute node resource providers?18:38
sean-k-mooneyefried: i think so im currently checking18:39
dansmithit doesn't matter, that's a thing we must support18:39
jaypipesefried: how about just relaxing the aggregate overwrite thing to instead just add aggregates (and potentially remove aggregates that the virt driver is 100% sure it owns fully)?18:39
*** moshele has quit IRC18:40
efriedjaypipes: Which is exactly what we're doing for traits.  The difference is that knowing that second thing is way harder for aggs.18:40
*** tssurya has joined #openstack-nova18:40
*** ChanServ changes topic to "This channel is for Nova development. For support of Nova deployments, please use #openstack. Please see: https://wiki.openstack.org/wiki/Nova/Rocky_Release_Schedule"18:41
-openstackstatus- NOTICE: Zuul has been restarted without the breaking change; please recheck any changes which failed tests with the error "Accessing files from outside the working dir ... is prohibited."18:41
efriedjaypipes: Kinda one step harder than the trait thing will be for the ironic case...18:41
jaypipesefried: if the virt driver created the agg, then it knows that, no?18:42
efriedjaypipes: No.18:42
efriedjaypipes: u_p_t has no memory.18:42
jaypipesefried: right, but the virt driver could persist that data somewhere itself..18:42
efriedjaypipes: Would have to be a file; else this doesn't work across compute restarts.18:42
efriedAre we in the practice of letting virt drivers write arbitrary files??18:43
jaypipesefried: IMHO, the virt drivers can do whatever they want w.r.t. persisting local information.18:43
efriedeek18:44
jaypipesefried: hell, that's pretty much what the libvirt XML files are ;)18:44
cdentexcept write allocations! )18:44
dansmithwell,18:44
* cdent runs away18:44
jaypipescdent: well... good point :)18:44
*** felipemonteiro_ has joined #openstack-nova18:44
dansmithanything we do in that regard has to *really* be sure that it supports upgrade properly,18:44
dansmithand we don't have a lot of tooling around that18:44
dansmithso I would be hesitant to approve any new things around that without a plan18:44
dansmithright now, all the data we store is managed by nova and tested (to the limit it's possible) by our upgrade tooling18:45
jaypipesdansmith: agreed. but, if powervm wants to use etcd running on a mainframe in a datacenter in Cambodia, I honestly couldn't care less. :)18:45
sean-k-mooneyefried: this covers the aggregate usecase for neutron reouted networks. https://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/neutron-routed-networks.html#proposed-change18:45
dansmithjaypipes: well, I care, because I care about users' experience with nova being positive when possible18:45
sean-k-mooneyefried: the first paragrph directly covers the use of aggregated to model network segments18:45
dansmithjaypipes: which is why I care about virt drivers merging random crap that affects that view18:45
jaypipesdansmith: I, of course, *would* care about the libvirt driver doing such a thing.18:45
dansmithjaypipes: it's hard to explain why we hold libvirt to a different standard once we let things like that into other drivers, but anyway..18:46
jaypipesfair enough.18:46
sean-k-mooneyjaypipes: well libvirt xmls are generated at runtime so they are not really persiting state18:47
*** felipemonteiro__ has quit IRC18:48
sean-k-mooneyjaypipes: we can recompute them form info in the nova db if they were deleted18:48
dansmithsean-k-mooney: their compatibility is also managed by libvirt18:48
*** claudiub|2 has joined #openstack-nova18:49
sean-k-mooneydansmith: yes that too. we did discuss brefily that we could add a table to the nova db for virt dirvers to store instance specific info. provided we used ovo or something similar to version the data they stored for upgrades18:49
dansmithyep, that would be better from an upgrade point of view18:50
*** harlowja has joined #openstack-nova18:50
sean-k-mooneyin this case we would have to simple presetit a list of virt_driver owned aggregats or something along those lines?18:50
sean-k-mooneypersonally i dislike storing json blobs in the db but if its somting we will never query against and is just used as a keyvalue store for the virt dirver then as long as its versioned in some way i personally dont care as much18:52
dansmiththat's pretty specific to this case18:52
dansmithI'm not opposed to virt drivers storing things locally, I just think we need a plan to avoid letting it get out of hand and breaking during an upgrade18:52
jaypipesdansmith: I don't disagree with you. I was being a bit tongue in cheek earlier about the datacenter in Cambodia.18:54
*** lbragstad has joined #openstack-nova18:55
*** AlexeyAbashkin has joined #openstack-nova18:56
*** sar has joined #openstack-nova18:59
*** AlexeyAbashkin has quit IRC19:00
*** moshele has joined #openstack-nova19:01
*** openstackgerrit has quit IRC19:04
*** openstackgerrit has joined #openstack-nova19:05
openstackgerritJay Pipes proposed openstack/nova-specs master: Support default allocation ratios  https://review.openstack.org/55210519:05
cfriesendansmith: as per discussion at PTG: https://bugs.launchpad.net/nova/+bug/1754782    I won't have any time to work on it till next week at the earliest.19:06
openstackLaunchpad bug 1754782 in OpenStack Compute (nova) "we skip critical scheduler filters when forcing the host on instance boot" [Undecided,New]19:07
*** salv-orlando has quit IRC19:08
*** moshele has quit IRC19:11
*** jpena is now known as jpena|off19:12
melwittjaypipes: thanks for writing up the PTG summary for placement, good stuff19:13
jaypipesmelwitt: no prob. thanks to mriedem and gibi who double-checked stuff on it.19:14
melwittmriedem++ gibi++19:14
sean-k-mooneyQQ just working on https://bugs.launchpad.net/nova/+bug/1747496 did we remove the old default config values from MTU when not set on the port from nova? i think we did but just setting19:16
openstackLaunchpad bug 1747496 in OpenStack Compute (nova) "MTUs are not set for VIFs if using kernel ovs + hybrid plug = false" [Medium,Confirmed] - Assigned to sean mooney (sean-k-mooney)19:16
sean-k-mooney*checking19:16
*** suresh12 has quit IRC19:17
*** suresh12 has joined #openstack-nova19:17
openstackgerritEric Fried proposed openstack/nova-specs master: Allow for merging traits  https://review.openstack.org/55212219:20
efrieddansmith, jaypipes, cdent, sean-k-mooney, edleafe: ^19:20
sean-k-mooneyhum it does appare to be in https://github.com/openstack/nova/blob/master/nova/conf/network.py or in .../neutron.py so i guess they are gone and were move to os-vif https://github.com/openstack/os-vif/search?utf8=%E2%9C%93&q=network_device_mtu&type=19:20
efriedI didn't make any changes for aggregates.19:20
cdentefried: thanks, in the queue19:21
*** maciejjozefczyk has quit IRC19:21
sean-k-mooneyefried: im just heading home but i addem myself to the review and ill leave it open in a tab for tomorow. ill give it a quick skim before i leave however19:23
dansmithefried: looks okay to me19:24
*** gouthamr has quit IRC19:25
sean-k-mooneyefried: why did you start with "Traits are special.  Rather than overwriting the entire set of traits" this statement also applies to RPs and Aggregates19:25
efriedsean-k-mooney: Because I wrote this before it occurred to me that we should be doing the same for the other bits.19:26
sean-k-mooneyefried: the compute node RP is not owned by nova so nova cant override all child RPs of the compute node either19:26
sean-k-mooneyefried: ah ok19:26
efriedsean-k-mooney: But I also wanted to do this one isolated because I don't think we're done discussing the others.19:26
*** suresh12 has quit IRC19:27
efriedThe compute node RP *is* owned by nova.19:27
efriedsean-k-mooney: And *some* of its children may also be.19:27
dansmithyeah, the compute node RP is _definitely_ owned by nova :)19:27
efriedIn general virt needs to be smart enough not to muck with stuff it doesn't own.  But originally we *thought* that meant virt owns everything about the RPs it owns.19:28
sean-k-mooneyefried: that has issues wich other services want to tag it with traits19:28
dansmithagreed nova can't blow away all the providers underneath, unless it's deleting the compute node19:28
*** gouthamr has joined #openstack-nova19:28
sean-k-mooneydansmith: well event then i dont think it can19:28
efriedWhich is why we already have ProviderTree methods to add/remove providers in the tree.19:28
efried...individually.19:28
dansmithsean-k-mooney: it has to be able to delete it and the subtree, IMHO19:28
sean-k-mooneydansmith: if i have a converged deployment where my compute nodes are also cinder storage pool providers the the root node of the tree would be a parent of the nova resources and the cinder resouces19:29
efriedAgree.  E.g. if neutron created bandwidth RPs under a PF, and compute removes the PF, the bandwidth providers are no longer relevant.19:29
sean-k-mooneywhich is why i dont think the root node can be owned by nova19:30
efriedsean-k-mooney: I don't think that's a model we should support.19:30
dansmithsean-k-mooney: in that case the cinder providers are not servicing other computes, right? then it's okay to delete it19:30
dansmithsean-k-mooney: if they are servicing others, then the cinder pool should not be a child of the compute node19:30
sean-k-mooneydansmith: no the could be and associated with other computes via a sharing aggregate19:30
dansmithsean-k-mooney: if they are, they should not be a child of the compute IMHO19:30
jaypipesefried: I agree with both edleafe and dansmith on that update to the u-p-t spec19:31
dansmithsean-k-mooney: the compute node RP is not the physical computer, it's the nova service and the hypervisor/virt driver underneath19:31
sean-k-mooneydansmith: perhaps i had always just envisioned that the server itself was a resouce provider all services could create childeren under without having to worry about it beeing deleted by e.g. nova19:32
*** READ10 has quit IRC19:32
dansmithsean-k-mooney: not, IMHO.. if we need to model that relationship then the compute node RP would be a child to "the computer" I think19:32
jaypipesdansmith: well, in the case of a hypervisor host, yes. :) for ironic, of course, that's different.19:32
dansmithbut I hope we don't need to do that19:32
sean-k-mooneydansmith: yes well that has some advantages19:32
dansmithjaypipes: yeah I know, but thats special19:32
jaypipesack19:33
dansmithjaypipes: ironic nodes wouldn't be cinder providers in the same hierarchy, and even better, the computer running the nova service for those, if it were a cinder pool shared with other nodes, should be modeled peer to the compute service's RP I think19:34
sean-k-mooneydansmith: the only issue i have really with saying that nova owns the root RP is that we may need to have multiple root nodes for the same server depending on the service19:34
dansmithsean-k-mooney: no, nova owns the compute RP.. if you decide to make that the root of your cinder provider, then it is a root :)19:34
dansmithand you get what's coming to you in that case :)19:34
dansmithwhich is nova may delete the root that it owns19:35
sean-k-mooneydansmith: yes but the we have too trees for the same phyical server and we dont currently have a way to model that they are the same server19:35
sean-k-mooneyi guess maybe with an aggregate19:35
dansmithsean-k-mooney: they're not the same server,19:35
sean-k-mooneydansmith: why not?19:36
dansmithsean-k-mooney: they represent services that happen to be on the same box.. if we need to model that they're on the same box (i.e. below a parent provider) then that's a thing19:36
efrieddansmith, jaypipes: Please confirm: you want two separate methods, with *traits args19:36
dansmithefried: that's fine19:36
jaypipesefried: yes please19:36
efriedight19:36
jaypipesadd_traits() and remove_traits() would be my preference.19:36
jaypipesefried: ^19:36
dansmithefried: btw, excellent job not having your head explode here. kudos :)19:36
efriedjaypipes: Cool, swhere I was gonna go.  dansmith: ack, thx; head may yet explode over aggregates thing, but so far so good.19:37
dansmithefried: on friday of PTG, I thought maybe your eyeballs were about to shoot from your head at lethal velocity, which scared me when they were pointed at me19:37
sean-k-mooneydansmith: ok anyway thats a little off topic. i do think we may want to have a parent of the compute node RP at some point then but let cross that bridge only when we need too19:37
dansmithsean-k-mooney: we may and that would solve the problem of this ownership of the tree for deletes problem, that's what I'm saying :)19:38
dansmithuntil that point, if you create a provider underneath someone else's provider, I think you need to know that you're at the other's mercy19:38
efrieddansmith: It ain't my eyeballs that should worry you :P  FWIW, I'm still uncomfortable with this, but I don't see a better alternative.19:38
dansmithum.19:38
* dansmith thinks about other body parts19:38
* efried 's whole body is a lethal weapon19:39
* dansmith calls HR to report a threat19:39
* efried chokes out HR too19:39
dansmithoof19:39
sean-k-mooneydansmith: oh yes it would solve that issue. it would raise the question of which tree i shoudl create the resouce other for thinks like bandwith. anyway i better run before the stores close at 819:40
dansmithyeah19:41
* sean-k-mooney rereads my last sentence and think my dyslxia is getting worse. littrally types different words /other/under /thinks/things then i taught in my head...19:43
*** suresh12 has joined #openstack-nova19:47
*** slaweq has joined #openstack-nova19:47
*** slaweq has quit IRC19:49
*** slaweq has joined #openstack-nova19:50
*** r-daneel has joined #openstack-nova19:50
mnaserhm, does anyone have any idea behind the historical reason why ComputeCapabilitiesFilter is hard-coded to use instancetypes (not taking image properties into consideration?)19:52
mnasercontext: customer *needs* instances with a specific cpu flag, i'd like to minimize the number of flavors so i was hoping i can have a image flag requesting that cpu flag19:52
mnaservs having to create a new instance type for this use case specifically19:53
efriedjaypipes: Considering removing ProviderTree.set_traits/set_aggregates entirely.19:53
*** danpawlik has quit IRC19:54
*** gouthamr has quit IRC19:54
*** moshele has joined #openstack-nova19:55
*** suresh12 has quit IRC19:57
openstackgerritEric Fried proposed openstack/nova-specs master: Allow for merging traits and aggregates  https://review.openstack.org/55212220:00
efrieddansmith, jaypipes, cdent, edleafe: ^ with changes as requested, plus for aggregates20:00
*** r-daneel_ has joined #openstack-nova20:00
*** mvk has quit IRC20:01
*** r-daneel has quit IRC20:02
*** r-daneel_ is now known as r-daneel20:02
*** slaweq___ has quit IRC20:02
cdent20:03
*** Sukhdev has joined #openstack-nova20:04
*** salv-orlando has joined #openstack-nova20:08
*** jackie-truong has quit IRC20:09
*** slaweq has quit IRC20:09
*** slaweq has joined #openstack-nova20:10
*** esberglu_ has joined #openstack-nova20:10
*** tssurya has quit IRC20:11
*** lpetrut has quit IRC20:11
*** liverpooler has quit IRC20:12
*** esberglu has quit IRC20:12
*** tssurya has joined #openstack-nova20:12
*** salv-orlando has quit IRC20:13
*** jackie-truong has joined #openstack-nova20:15
jaypipesefried: +2 from me. thx20:16
efriedthx20:16
*** suresh12 has joined #openstack-nova20:16
*** tidwellr has quit IRC20:19
*** tidwellr_ has joined #openstack-nova20:19
*** mgoddard_ has joined #openstack-nova20:21
edleafeefried: a little late, but added my +1 for good measure :)20:21
efriedthx20:22
dansmithefried: consider me suitably thrown under the bus for my method naming20:23
efrieddansmith: You're not held accountable for sample code in pastebin.  Else I would have griped at you about having the + case first and the - case the default.20:24
dansmithelse should have raised20:25
mriedemefried: with ^ how can i integrate that with https://review.openstack.org/#/c/538498/ where i'm not in a virt driver with a provider tree - or will that RT code eventually have the provider tree object so i can call add_traits there?20:26
mriedemalternatively, if the RT isn't the place to do that and the virt driver is, i could add a generic method in the base ComputeDriver class that handles adding traits from the capabilities dict20:28
dansmithmriedem: virt driver can do that from u_p_t he's describing here20:28
mriedemright, but i don't want to copy the same thing in all virt drivers20:28
dansmithbut better for compute to do it right where it's calling into the virt driver20:28
mriedemso RT or base class, i'm ok with either20:28
dansmithcall the capabilities compute-owned20:28
efriedmriedem: I'm glad you asked.  I believe you should get the traits from placement and add in those you got from _get_traits (which is the union of those from virt & capabilities).20:29
mriedemthe compute isn't calling this, the RT is20:29
dansmithyeah, wherever we call that in the virt driver from20:29
mriedemi don't know what the RT will have the UPT20:29
dansmithefried: eh?20:29
*** Sukhdev has quit IRC20:29
mriedemmaybe it will and i'm just behind20:29
*** nicolasbock has joined #openstack-nova20:29
mriedemefried: i'm not sure why i need to call placement,20:29
dansmithefried: we get them from the virt driver structure, we can just generate the traits that go with them and tack them onto the provider tree for the compute node RP20:29
mriedemi want to *always* report these capabilities20:29
dansmithmriedem: you wouldn't20:29
dansmithright20:29
dansmiththese are compute-asserted traits, IMHO20:30
mriedemtelling me, "go look at the UPT series of changes and figure it out" is acceptable also20:30
efriedmriedem: If we can slot your change into the UPT series, that would make things easier to reason about.  Having to decide what it would look like in all three possible permutations is harder.20:31
*** slaweq has quit IRC20:31
*** slaweq has joined #openstack-nova20:32
openstackgerritEric Berglund proposed openstack/nova master: PowerVM Driver: Network interface attach/detach  https://review.openstack.org/54681320:32
dansmithmriedem: https://review.openstack.org/#/c/520246/52/nova/compute/resource_tracker.py L884 there I think20:32
dansmithlogically it's compute, but mechanically it's RT because that's what owns the compute node RP20:32
mriedemok that works for me, i can rebase on top of that20:32
efriedmriedem: If we do your change *after* https://review.openstack.org/#/c/520246/ then you can use the prov_tree to merge in the capability traits and then call update_from_provider_tree.20:32
mriedemyeah i'll plan on that,20:33
mriedemno rush20:33
*** yangyapeng has joined #openstack-nova20:34
*** esberglu_ has quit IRC20:34
*** esberglu has joined #openstack-nova20:35
*** moshele has quit IRC20:35
efriedmriedem: I'm about to do some ka-shuffle-fu.  Want me to fold that in?20:35
mriedemno leave it to me20:36
mriedemplease20:36
mriedemthat also leaves you on the hook for reviewing it when i do it20:37
*** felipemonteiro_ has quit IRC20:37
*** felipemonteiro_ has joined #openstack-nova20:37
mikalDeleted nova-net yet?20:38
*** esberglu_ has joined #openstack-nova20:38
*** yangyapeng has quit IRC20:39
*** esberglu has quit IRC20:39
*** prateek has quit IRC20:41
*** salv-orlando has joined #openstack-nova20:42
mriedemno20:48
mriedemworking on it20:48
mriedemneed to get https://review.openstack.org/#/c/549789/ going20:48
mriedembut i have to go through the test failures there and figure out what (and how) to blacklist20:49
*** hoangcx has quit IRC20:49
mriedemmikal: ^20:49
mriedemthe failures are mostly just due to stuff like not supporting security groups in the cells v1 api20:49
*** hoangcx has joined #openstack-nova20:49
mriedemhttps://review.openstack.org/#/c/225199/ would have handled that nicely but it got bogged down in committee20:50
*** burt has quit IRC20:50
*** wolverineav has quit IRC20:51
*** wolverineav has joined #openstack-nova20:52
*** amodi has quit IRC20:56
*** wolverineav has quit IRC20:56
*** itlinux has quit IRC20:57
*** tblakes has joined #openstack-nova21:00
*** mvk has joined #openstack-nova21:03
*** tblakes has quit IRC21:05
edmondswdoes tagged_attach require the metadata service? Because cloud-init would only be an option during boot, not after, right?21:06
*** amodi has joined #openstack-nova21:08
*** ameeda has joined #openstack-nova21:08
ameedaHi, I try to call heat template by rest api, when I try to do GET http://<IP>:<PORT>/v1/<Tenent_ID>/stacks, I got this message HTTP request sent, awaiting response... 401 Unauthorized21:10
edmondswand by cloud-init I should have said config drive...21:10
*** gouthamr has joined #openstack-nova21:12
*** r-daneel_ has joined #openstack-nova21:14
*** suresh12 has quit IRC21:15
*** suresh12 has joined #openstack-nova21:15
*** suresh12 has quit IRC21:15
*** mgoddard_ has quit IRC21:15
*** suresh12 has joined #openstack-nova21:16
*** r-daneel has quit IRC21:16
*** r-daneel_ is now known as r-daneel21:16
*** artom has joined #openstack-nova21:18
*** sar has quit IRC21:19
*** ameeda has quit IRC21:19
*** Sukhdev has joined #openstack-nova21:20
mriedemedmondsw: tagged attach does not require the metadata service, the tagged devices will show up in the metadata blob in the config drive21:21
mriedemthe config drive will only have the create-time tagged devices, correct21:21
mriedemif you need on-the-fly changes to tagged devices then you'd need the metadata service21:22
edmondswmriedem config drive is available beyond the first boot?21:22
mriedemno it's not21:22
edmondswok, that's what I was thinking21:22
edmondswboo... but tx for confirming21:23
mriedemnow if you're using configuration strategy,21:23
mriedemwho knows21:23
mriedem:)21:24
edmondsw"configuration strategy"?21:24
mriedemhttps://www.ibm.com/developerworks/community/forums/html/topic?id=1918efbc-ae12-44a3-8075-a6023831d334&ps=10021:27
mriedemhttps://www.ibm.com/support/knowledgecenter/en/SST55W_4.2.0/liaca/liacaimportingstrategy.html is better21:28
mriedemi.e. config-drive for ibm i and aix images right?21:29
*** gouthamr has quit IRC21:30
mriedemboot me an ibm i guest with 500 volumes attached in a single call please21:30
*** wolverineav has joined #openstack-nova21:32
*** Guest18434 has quit IRC21:33
*** jackie-truong has quit IRC21:34
*** pcaruana has quit IRC21:36
*** wolverineav has quit IRC21:36
*** wolverineav has joined #openstack-nova21:39
openstackgerritMerged openstack/nova-specs master: Report CPU features to placement service by traits API  https://review.openstack.org/49773321:39
*** gouthamr has joined #openstack-nova21:40
openstackgerritEric Berglund proposed openstack/nova master: PowerVM Driver: Snapshot  https://review.openstack.org/54302321:41
*** felipemonteiro__ has joined #openstack-nova21:43
*** yangyapeng has joined #openstack-nova21:43
*** liusheng has quit IRC21:45
*** liusheng has joined #openstack-nova21:46
*** edmondsw has quit IRC21:46
*** suresh12 has quit IRC21:46
*** felipemonteiro_ has quit IRC21:46
*** edmondsw has joined #openstack-nova21:46
*** suresh12 has joined #openstack-nova21:47
*** Sukhdev has quit IRC21:47
*** liusheng has quit IRC21:48
*** tbachman has quit IRC21:48
*** yangyapeng has quit IRC21:48
*** liusheng has joined #openstack-nova21:49
*** salv-orlando has quit IRC21:49
*** blkart has quit IRC21:49
*** krtaylor has quit IRC21:49
*** kashyap has quit IRC21:50
*** Swami has quit IRC21:50
*** Swami has joined #openstack-nova21:51
*** blkart has joined #openstack-nova21:52
*** kashyap has joined #openstack-nova21:52
*** krtaylor has joined #openstack-nova21:53
*** salv-orlando has joined #openstack-nova21:55
*** cdent has quit IRC21:56
openstackgerritMerged openstack/nova-specs master: Express forbidden traits in placement API  https://review.openstack.org/54891522:03
*** gouthamr has quit IRC22:03
*** esberglu_ has quit IRC22:04
*** esberglu has joined #openstack-nova22:05
*** tbachman has joined #openstack-nova22:08
*** esberglu has quit IRC22:09
*** suresh12 has quit IRC22:10
*** tbachman_ has joined #openstack-nova22:10
*** tasker has joined #openstack-nova22:11
openstackgerritMatt Riedemann proposed openstack/nova-specs master: Fix spec name for "report CPU features to as traits"  https://review.openstack.org/55215922:12
taskertrying to instruct tox to run "nova.tests.unit.compute.test_compute_api" and it fails, complaining about being unable to import "nova.tests.unit.network.test_neutronv2", "nova.tests.unit.virt.test_block_device", and "nova.tests.unit.virt.test_imagecache". any quick thoughts on what I've done wrong?22:12
openstackgerritMatt Riedemann proposed openstack/nova-specs master: Fix spec name for "report CPU features as traits"  https://review.openstack.org/55215922:13
taskerI've rebased my work on master a few minutes ago and still getting the above.22:13
*** tbachman has quit IRC22:13
*** tbachman_ is now known as tbachman22:13
mriedemtasker: did you rebuild the tox venv?22:13
*** gouthamr has joined #openstack-nova22:13
mriedemtox -r -e py2722:13
taskerno. i was unaware of that. doing so now.22:13
mriedemtox -r -e py27 -- nova.tests.unit.compute.test_compute_api22:14
*** suresh12 has joined #openstack-nova22:14
edleafe /away evening22:14
edleafedoh!22:14
*** tssurya has quit IRC22:15
*** idlemind has joined #openstack-nova22:17
*** mlavalle has quit IRC22:18
*** tidwellr_ has quit IRC22:21
*** tidwellr has joined #openstack-nova22:21
*** edmondsw has quit IRC22:24
*** rcernin has joined #openstack-nova22:24
*** edmondsw has joined #openstack-nova22:24
*** tidwellr has quit IRC22:25
taskermriedem: that did the trick. thanks!22:26
taskernow I just need to fix my test.22:27
*** edmondsw has quit IRC22:29
*** yangyapeng has joined #openstack-nova22:32
*** hongbin has quit IRC22:33
*** Sukhdev has joined #openstack-nova22:33
*** yangyapeng has quit IRC22:36
openstackgerritMerged openstack/nova master: Make the nova-next job voting and gating  https://review.openstack.org/54989322:38
*** AlexeyAbashkin has joined #openstack-nova22:38
*** elmaciej has joined #openstack-nova22:41
*** AlexeyAbashkin has quit IRC22:42
*** suresh12 has quit IRC22:48
openstackgerritMatt Riedemann proposed openstack/nova master: WIP: libvirt: use dest host vif migrate details for live migration  https://review.openstack.org/55137022:50
openstackgerritMatt Riedemann proposed openstack/nova master: Port binding based on events during live migration  https://review.openstack.org/43487022:50
openstackgerritMatt Riedemann proposed openstack/nova master: compute: use port binding extended API during live migration  https://review.openstack.org/55137122:50
openstackgerritMatt Riedemann proposed openstack/nova master: conductor: use port binding extended API in during live migrate  https://review.openstack.org/52253722:50
openstackgerritMatt Riedemann proposed openstack/nova master: Add "delete_port_bindings" network API method  https://review.openstack.org/55217022:50
*** felipemonteiro__ has quit IRC22:54
*** amodi has quit IRC22:56
*** elmaciej has quit IRC22:56
*** yamamoto has joined #openstack-nova22:57
openstackgerritMerged openstack/nova master: setup.cfg: Explicitly set [build_sphinx] builder  https://review.openstack.org/50848322:59
openstackgerritMerged openstack/nova master: Check the return code when forcing TCG mode with libguestfs  https://review.openstack.org/52472722:59
openstackgerritMerged openstack/nova master: Remove vestigial extra_info update in PciDevice.save()  https://review.openstack.org/52391922:59
openstackgerritMerged openstack/nova master: conf: Deprecate 'keymap' options  https://review.openstack.org/48399422:59
openstackgerritEric M Gonzalez (tasker) proposed openstack/nova master: unquiesce instance after quiesce failure  https://review.openstack.org/55086523:01
taskerwith tests this time!23:02
*** suresh12 has joined #openstack-nova23:03
*** tidwellr has joined #openstack-nova23:04
*** chyka_ has joined #openstack-nova23:05
*** suresh12_ has joined #openstack-nova23:07
*** suresh12 has quit IRC23:07
openstackgerritGiridhar Jayavelu proposed openstack/nova-specs master: VMware: place instances on resource pool  https://review.openstack.org/54906723:08
*** chyka has quit IRC23:08
*** chyka_ has quit IRC23:09
openstackgerritEric Fried proposed openstack/nova-specs master: Allow for merging traits and aggregates  https://review.openstack.org/55212223:10
openstackgerritMatt Riedemann proposed openstack/nova master: WIP: Turn on new port binding extended live migrate flow  https://review.openstack.org/55217323:10
*** r-daneel has quit IRC23:12
*** germs has joined #openstack-nova23:14
*** germs has quit IRC23:14
*** germs has joined #openstack-nova23:14
*** tidwellr has quit IRC23:15
*** tidwellr has joined #openstack-nova23:15
*** tidwellr has quit IRC23:16
*** germs has quit IRC23:18
*** yassine has joined #openstack-nova23:19
cfriesenis it possible to query reviews that haven't been merged based on Change-Id?23:20
*** Sukhdev has quit IRC23:20
cfriesennever mind, figured it out.  works every time, post a question after digging for a while, then find it immediately after posting.23:20
*** salv-orlando has quit IRC23:29
*** tidwellr has joined #openstack-nova23:30
*** yangyapeng has joined #openstack-nova23:32
*** yangyapeng has quit IRC23:36
*** artom has quit IRC23:37
*** r-daneel has joined #openstack-nova23:39
*** edmondsw has joined #openstack-nova23:41
*** tidwellr has quit IRC23:42
*** liverpooler has joined #openstack-nova23:44
*** r-daneel has quit IRC23:44
SpazmoticMorning friends23:45
*** r-daneel has joined #openstack-nova23:46
*** edmondsw has quit IRC23:46
Spazmoticjianghuaw_, you home? :D I'm going to head to the gym, would like to talk to ya later!  Has been too long!23:46
*** yassine has quit IRC23:46
Spazmoticcfriesen, you figure everything out? i've been digging Gerritt api all week so I feel pretty strong it lol23:47
Spazmoticon it*23:47
*** yassine has joined #openstack-nova23:48
*** wolverineav has quit IRC23:50
*** itlinux has joined #openstack-nova23:51
*** sdague has quit IRC23:51
*** wolverineav has joined #openstack-nova23:52
*** tbachman has quit IRC23:56
*** liusheng has quit IRC23:59

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