Monday, 2018-01-29

*** tetsuro has joined #openstack-nova00:00
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Parameter verification for servers.inc  https://review.openstack.org/52820100:01
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Example verification for servers.inc  https://review.openstack.org/52952000:02
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Fix parameter order in rebuild  https://review.openstack.org/52971800:02
openstackgerritTetsuro Nakamura proposed openstack/nova master: trivialfix: cleanup _pack_instance_onto_cores()  https://review.openstack.org/53869800:04
openstackgerritTetsuro Nakamura proposed openstack/nova master: Add unit tests for EmulatorThreadsTestCase  https://review.openstack.org/53869900:04
openstackgerritTetsuro Nakamura proposed openstack/nova master: Not use thread alloc policy for emulator thread  https://review.openstack.org/53870000:04
*** liverpooler has joined #openstack-nova00:13
*** lbragstad has joined #openstack-nova00:14
openstackgerritOpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements  https://review.openstack.org/53847300:21
SpazmoticMorning00:27
*** salv-orlando has quit IRC00:29
*** yangyapeng has quit IRC00:29
*** yangyapeng has joined #openstack-nova00:30
*** hiro-kobayahsi has joined #openstack-nova00:34
*** yangyapeng has quit IRC00:34
*** sorrison_laptop has joined #openstack-nova00:42
*** zhaochao has joined #openstack-nova00:49
*** gcb has joined #openstack-nova00:53
*** hemna has quit IRC00:55
*** hieulq__ has quit IRC00:55
*** tuanla____ has joined #openstack-nova01:00
*** hemna has joined #openstack-nova01:01
*** phuongnh has joined #openstack-nova01:03
SpazmoticOff to the gym.  Back in a bit01:04
*** hoangcx has joined #openstack-nova01:05
*** tiendc has joined #openstack-nova01:07
*** hieulq__ has joined #openstack-nova01:11
*** yangyapeng has joined #openstack-nova01:16
*** tovin07 has joined #openstack-nova01:16
*** Efried_ has joined #openstack-nova01:18
Efried_Is there a core in the house?01:19
*** gcb has quit IRC01:21
Efried_Could please get re+Ws on six previously-approved patches series starting01:21
Efried_at https://review.openstack.org/#/c/533808/01:21
Efried_Wow, freenode webchat is hard on teeny iPhone.01:22
Efried_Anyway, trivial manual rebases on a couple of those kicked out my +Ws01:23
*** gongysh has joined #openstack-nova01:29
*** salv-orlando has joined #openstack-nova01:29
*** Efried_ has quit IRC01:32
*** salv-orlando has quit IRC01:35
*** mriedem has quit IRC01:37
*** hiro-kobayahsi has quit IRC01:39
*** yikun_jiang has quit IRC02:01
*** yikun has joined #openstack-nova02:02
*** hiro-kobayashi has joined #openstack-nova02:05
*** hongbin has joined #openstack-nova02:06
*** sapcc-bot1 has quit IRC02:11
*** sapcc-bot has joined #openstack-nova02:12
*** armax has joined #openstack-nova02:14
*** phuongnh has quit IRC02:15
*** phuongnh has joined #openstack-nova02:15
SpazmoticMan that poor patchset still struggling its way through the gate efried ?02:18
*** tbachman_ has joined #openstack-nova02:20
*** tbachman has quit IRC02:21
*** tbachman_ is now known as tbachman02:21
*** tuanla____ has quit IRC02:27
*** tuanla____ has joined #openstack-nova02:28
*** salv-orlando has joined #openstack-nova02:31
*** salv-orlando has quit IRC02:35
*** huanxie has joined #openstack-nova02:38
*** sdague has quit IRC02:52
*** Tom-Tom has joined #openstack-nova02:55
*** yamamoto has joined #openstack-nova02:58
openstackgerritSpencer Yu proposed openstack/nova master: Use defusedxml.ElementTree function instead of lxml.etree  https://review.openstack.org/51929103:02
*** gongysh has quit IRC03:03
*** rcernin has quit IRC03:08
*** harlowja has joined #openstack-nova03:11
*** xinliang has quit IRC03:16
*** xinliang has joined #openstack-nova03:16
Spazmoticjianghuaw, huanxie I'll be on vacation after this week, so we should find some time before the weekend to have a group chat.03:16
huanxiesure Spazmotic03:17
SpazmoticIt's monday so i won't bother you two with it today and it's not something we need to push hard on at the moment yet anyway03:17
*** harlowja has quit IRC03:18
SpazmoticBut I think we're closing in one a solution here that we can all agree on03:18
*** dave-mccowan has quit IRC03:20
*** yikun_jiang has joined #openstack-nova03:20
*** stakeda has joined #openstack-nova03:21
*** yikun has quit IRC03:23
*** jgwentworth is now known as melwitt03:26
*** salv-orlando has joined #openstack-nova03:31
*** salv-orlando has quit IRC03:36
*** annp has joined #openstack-nova03:40
huanxieAgree with you Spazmotic03:45
jianghuawSpazmotic, huanxie Looked at the patch. I have the same concerns as Huan. I think the point to use XCP version than product version is because the there is some other variants basing on Xen which will have the same issue.03:53
*** Tom-Tom has quit IRC03:54
jianghuawIt looks good to me if we can change to use "XCP version" for a quick fix. Later we need check if we can prepare the volume SR earlier in the dest host.03:54
jianghuawPreparing the SR earlier requires much refactor work to make it looks reasonable. But I think that's the right way which is worthy for us to look at.03:56
*** elmaciej has quit IRC03:57
*** blkart_ has joined #openstack-nova03:59
*** sapcc-bot has quit IRC04:04
*** sapcc-bot has joined #openstack-nova04:04
*** rcernin has joined #openstack-nova04:04
*** hongbin has quit IRC04:04
*** owalsh_ has joined #openstack-nova04:13
openstackgerritMerged openstack/nova master: libvirt: don't attempt to live snapshot paused instances  https://review.openstack.org/53221404:13
openstackgerritDao Cong Tien proposed openstack/nova master: virt/ironic: Implement rescue and unrescue  https://review.openstack.org/41648704:15
*** owalsh has quit IRC04:17
*** psachin has joined #openstack-nova04:17
*** hiro-kobayashi has quit IRC04:18
*** sree has joined #openstack-nova04:19
*** hiro-kobayashi has joined #openstack-nova04:19
*** Tom-Tom has joined #openstack-nova04:21
*** hoangcx has quit IRC04:21
*** bhagyashris has quit IRC04:22
*** Tom-Tom has quit IRC04:26
*** blkart has joined #openstack-nova04:29
*** blkart has quit IRC04:30
*** salv-orlando has joined #openstack-nova04:32
*** bhagyashris has joined #openstack-nova04:33
*** liuyulong has joined #openstack-nova04:33
*** hoangcx has joined #openstack-nova04:34
*** salv-orlando has quit IRC04:37
*** hoangcx has quit IRC04:38
*** hoangcx has joined #openstack-nova04:40
openstackgerritChen Hanxiao proposed openstack/nova master: libvirt: add Linux distribution guest only description for inject_xxx options  https://review.openstack.org/52844104:41
*** armax has quit IRC04:49
*** abhishekk has joined #openstack-nova05:04
*** AlexeyAbashkin has joined #openstack-nova05:06
*** claudiub|2 has joined #openstack-nova05:07
*** hongbin has joined #openstack-nova05:09
*** AlexeyAbashkin has quit IRC05:10
*** abhishekk has quit IRC05:15
*** Tom-Tom has joined #openstack-nova05:19
*** diga has joined #openstack-nova05:21
*** ratailor has joined #openstack-nova05:24
*** hongbin has quit IRC05:28
*** AlexeyAbashkin has joined #openstack-nova05:31
*** salv-orlando has joined #openstack-nova05:33
*** janki has joined #openstack-nova05:37
*** salv-orlando has quit IRC05:37
*** moshele has joined #openstack-nova05:38
*** sridharg has joined #openstack-nova05:39
*** pooja_jadhav has joined #openstack-nova05:45
*** AlexeyAbashkin has quit IRC05:46
*** mdnadeem has joined #openstack-nova05:59
*** xinliang has quit IRC06:02
*** mdnadeem has quit IRC06:04
*** diga has quit IRC06:05
*** xinliang has joined #openstack-nova06:14
*** xinliang has joined #openstack-nova06:14
*** mdnadeem has joined #openstack-nova06:16
*** AlexeyAbashkin has joined #openstack-nova06:17
*** MikeG451 has quit IRC06:26
*** syjulian has quit IRC06:27
*** Eran_Kuris has joined #openstack-nova06:30
openstackgerritHoang Trung Hieu proposed openstack/python-novaclient master: Zuul: Remove project name  https://review.openstack.org/53877706:30
*** salv-orlando has joined #openstack-nova06:34
*** ameeda has quit IRC06:35
*** ameeda has joined #openstack-nova06:36
*** phuongnh has quit IRC06:37
*** Dinesh_Bhor has joined #openstack-nova06:37
*** salv-orlando has quit IRC06:38
*** salv-orlando has joined #openstack-nova06:38
*** lajoskatona has joined #openstack-nova06:43
openstackgerritJianghua Wang proposed openstack/nova master: xenapi: Support live migration in pooled multi-nodes environment  https://review.openstack.org/48945106:44
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove unnecessary arguments in notification methods  https://review.openstack.org/53559906:48
*** sorrison_laptop has quit IRC06:57
*** Tengu has quit IRC06:58
*** hiro-kobayashi has quit IRC07:02
*** Dinesh_Bhor has quit IRC07:10
*** MikeG451 has joined #openstack-nova07:10
*** rcernin has quit IRC07:11
*** Dinesh_Bhor has joined #openstack-nova07:11
Spazmoticjianghuaw,  I think you're right, that was my first attempt, getting the SR prepped earlier, but would definately take some refactor and thought07:20
SpazmoticWill look at your multinode env later tonight :)07:20
*** namnh has joined #openstack-nova07:21
SpazmoticAh looks like you already got the whole gang to +1 it, not much for me to do there hehe07:21
*** Dinesh_Bhor has quit IRC07:23
SpazmoticAlso, what version of XCP would you say to target for this?07:24
openstackgerritTuan Luong-Anh proposed openstack/nova master: Fix some reST field lists in docstrings  https://review.openstack.org/53880907:24
Spazmotichuanxie, could use your input on that one too, since you two are tied in closer to the XCP versioning then I am07:25
*** Dinesh_Bhor has joined #openstack-nova07:25
*** kevinz has joined #openstack-nova07:29
*** andreas_s has joined #openstack-nova07:32
*** salv-orlando has quit IRC07:33
*** slaweq has joined #openstack-nova07:34
*** Dinesh_Bhor has quit IRC07:34
*** hoonetorg has quit IRC07:35
*** Dinesh_Bhor has joined #openstack-nova07:36
*** slaweq has quit IRC07:38
*** Dinesh_Bhor has quit IRC07:38
*** slaweq has joined #openstack-nova07:38
*** gcb has joined #openstack-nova07:39
*** Dinesh_Bhor has joined #openstack-nova07:39
*** slaweq has quit IRC07:40
*** slaweq has joined #openstack-nova07:40
*** moshele has quit IRC07:41
*** pcaruana has joined #openstack-nova07:44
*** fragatina has joined #openstack-nova07:44
*** Dinesh_Bhor has quit IRC07:45
*** belmoreira has joined #openstack-nova07:47
jianghuawSpazmotic, the platform version is 2.1.0 for XS 7.0.07:48
SpazmoticThanks sir07:49
*** Dinesh_Bhor has joined #openstack-nova07:50
jianghuawnp:-)07:50
*** hoonetorg has joined #openstack-nova07:52
*** salv-orlando has joined #openstack-nova07:55
*** AlexeyAbashkin has quit IRC07:55
*** sahid has joined #openstack-nova07:55
*** sahid has joined #openstack-nova07:55
*** gongysh has joined #openstack-nova08:03
*** kholkina has joined #openstack-nova08:07
*** gongysh has quit IRC08:08
*** links has joined #openstack-nova08:09
*** zhenguo has joined #openstack-nova08:16
*** ralonsoh has joined #openstack-nova08:20
*** tssurya has joined #openstack-nova08:23
*** alexchadin has joined #openstack-nova08:25
*** tesseract has joined #openstack-nova08:26
*** hrw has joined #openstack-nova08:28
*** Dinesh_Bhor has quit IRC08:29
*** AlexeyAbashkin has joined #openstack-nova08:35
ameedaMorning08:39
*** AlexeyAbashkin has quit IRC08:40
ameedawhen I try to alter sqlite column data type I got error "mismatch models and migration script", Please check this to see the details http://paste.openstack.org/show/656589/08:40
ameedawhat should I do with this case ?08:40
*** Dinesh_Bhor has joined #openstack-nova08:41
ameedaSpazmotic: can you please help ?08:41
*** masber has quit IRC08:41
ameedajianghuaw: what do you think sir ?08:42
*** masber has joined #openstack-nova08:42
*** ttsiouts has joined #openstack-nova08:44
*** salv-orlando has quit IRC08:45
*** mgoddard_ has joined #openstack-nova08:45
*** Dinesh_Bhor has quit IRC08:46
ameedaOk , thanks I fix the issue, I have to use reference to instances(uuid) rather than compute_node(id)08:46
*** ttsiouts has quit IRC08:46
*** ttsiouts has joined #openstack-nova08:47
*** jpena|off is now known as jpena08:48
*** aloga has quit IRC08:49
*** aloga has joined #openstack-nova08:49
*** Dinesh_Bhor has joined #openstack-nova08:50
*** Dinesh_Bhor has quit IRC08:52
*** belmorei_ has joined #openstack-nova08:52
*** amoralej|off is now known as amoralej08:53
*** belmoreira has quit IRC08:53
*** fragatina has quit IRC08:55
*** alexchadin has quit IRC08:58
*** alexchadin has joined #openstack-nova08:58
openstackgerritMaciej Jozefczyk proposed openstack/nova master: Do not normalize allocation_ratios  https://review.openstack.org/53292408:59
maciejjozefczykKevin_Zheng: thx for review :)09:00
*** salv-orlando has joined #openstack-nova09:02
openstackgerritAmeed Ashour proposed openstack/nova master: change instance_system_metadata column type  https://review.openstack.org/52690009:04
Kevin_Zhengmaciejjozefczyk YW :)09:04
*** hrw has quit IRC09:04
*** saulo has joined #openstack-nova09:04
gibletefried: I shoveled the nrp patches back to the gate as your rebase looks clean09:04
*** Dinesh_Bhor has joined #openstack-nova09:06
*** giblet is now known as gibi_09:07
*** mgoddard_ has quit IRC09:07
*** saulo is now known as saugusto09:07
openstackgerritsahid proposed openstack/nova master: libvirt: disconnect volume from host during detach  https://review.openstack.org/51500809:08
*** saugusto is now known as sauloaugusto09:08
*** finucannot is now known as sfinucan09:12
*** sfinucan is now known as stephenfin09:12
sauloaugustoHi , anyone can help me with "ERROR nova.api.openstack.extensions TypeError: Can't upgrade a READER transaction to a WRITER mid-transaction"09:16
sauloaugustoafter pike upgrade procedure09:16
*** hrw has joined #openstack-nova09:16
sauloaugustoI saw that discussion at history logs , but I did not find out the solution .09:16
sauloaugustoI am using centos 709:16
*** jafeha has joined #openstack-nova09:17
*** owalsh_ has quit IRC09:17
*** owalsh has joined #openstack-nova09:17
sauloaugustosame error occurs with 'openstack server list --all-projects' command09:19
hrwcan someone take a look at https://review.openstack.org/#/c/538003 and tell me is it proper way?09:21
*** AlexeyAbashkin has joined #openstack-nova09:22
hrwthis code takes care of usb host being present if usbtablet is requested (not all archs have usb host by default)09:22
*** derekh has joined #openstack-nova09:23
bauzasgood morning novaers09:24
bauzasback from organizing the SnowCamp :)09:25
gibi_bauzas: welcome back09:28
*** yamahata has quit IRC09:28
bauzassaw the gate problems and the milestone delay09:29
maciejjozefczykbauzas: heyho09:30
*** yamamoto has quit IRC09:30
*** takashin has left #openstack-nova09:31
openstackgerritBalazs Gibizer proposed openstack/nova master: reno for notification-transformation-queens  https://review.openstack.org/51801809:31
*** hrw has quit IRC09:32
*** kholkina has quit IRC09:35
*** hrw has joined #openstack-nova09:36
*** liuyulong has quit IRC09:39
*** Dinesh_Bhor has quit IRC09:42
*** hrw has quit IRC09:42
*** mgoddard_ has joined #openstack-nova09:43
*** yamamoto has joined #openstack-nova09:47
*** elmaciej has joined #openstack-nova09:48
openstackgerritClaudiu Belu proposed openstack/nova master: tests: refactors and cleans up test_rbd.py  https://review.openstack.org/53802209:49
openstackgerritClaudiu Belu proposed openstack/nova master: tests: fixes mock autospec usage  https://review.openstack.org/44750509:49
openstackgerritClaudiu Belu proposed openstack/nova master: tests: autospecs all the mock.patch usages  https://review.openstack.org/47077509:49
*** hrw has joined #openstack-nova09:50
*** aloga has quit IRC09:52
*** aloga has joined #openstack-nova09:52
*** hrw has quit IRC09:55
*** sree has quit IRC10:01
*** sree has joined #openstack-nova10:02
*** tuanla_____ has joined #openstack-nova10:03
*** hrw has joined #openstack-nova10:03
*** moshele has joined #openstack-nova10:03
*** tuanla____ has quit IRC10:05
*** hrw has quit IRC10:08
*** namnh has quit IRC10:09
*** namnh has joined #openstack-nova10:09
*** sree has quit IRC10:11
*** elmaciej has quit IRC10:12
*** AlexeyAbashkin has quit IRC10:13
*** AlexeyAbashkin has joined #openstack-nova10:13
*** stakeda has quit IRC10:21
*** hrw has joined #openstack-nova10:25
*** lpetrut has joined #openstack-nova10:26
*** gcb has quit IRC10:29
*** hrw has quit IRC10:30
*** threestrands_ has joined #openstack-nova10:33
*** sdague has joined #openstack-nova10:35
*** threestrands has quit IRC10:36
*** Tom-Tom has quit IRC10:36
*** lucas-afk is now known as lucasagomes10:37
*** tiendc has quit IRC10:37
*** jappleii__ has joined #openstack-nova10:37
*** jappleii__ has quit IRC10:38
*** jappleii__ has joined #openstack-nova10:39
*** Tom-Tom has joined #openstack-nova10:40
*** threestrands_ has quit IRC10:41
*** Tom-Tom has quit IRC10:44
*** belmorei_ has quit IRC10:46
*** danpawlik has quit IRC10:46
*** hrw has joined #openstack-nova10:50
*** jaosorior has joined #openstack-nova10:52
*** namnh has quit IRC10:52
*** gcb has joined #openstack-nova10:53
*** alexchadin has quit IRC10:55
*** alexchadin has joined #openstack-nova10:55
*** gszasz has joined #openstack-nova10:57
*** Efried_ has joined #openstack-nova10:57
*** elmaciej has joined #openstack-nova10:58
ameedawhen I try "self.main_db = self.useFixture(fixtures.Database(database='main'))" I got this error " .. (sqlite3.OperationalError) no such table: services ... "10:58
*** gcb has quit IRC10:59
*** alexchadin has quit IRC10:59
*** hrw has quit IRC10:59
Efried_gibi Just popping in to say thanks for shepherding my series.10:59
Efried_Be back for real in a couple hours.11:00
*** hrw has joined #openstack-nova11:01
*** annp has quit IRC11:01
-openstackstatus- NOTICE: Zuul is currently under heavy load. Do not *recheck* or *approve* any changes.11:03
*** alexchadin has joined #openstack-nova11:04
*** hrw has quit IRC11:06
*** Efried_ has quit IRC11:07
*** alexchadin has quit IRC11:07
*** Tom-Tom has joined #openstack-nova11:09
*** danpawlik has joined #openstack-nova11:13
*** Tom-Tom has quit IRC11:13
*** gcb has joined #openstack-nova11:17
*** gcb has quit IRC11:18
*** elmaciej has quit IRC11:20
*** AlexeyAbashkin has quit IRC11:23
*** sambetts|afk is now known as sambetts|11:24
*** sambetts| is now known as sambetts11:24
*** andreas_s has quit IRC11:25
*** andreas_s has joined #openstack-nova11:25
*** hrw has joined #openstack-nova11:28
*** alexchadin has joined #openstack-nova11:30
*** alexchadin has quit IRC11:33
*** andreas_s has quit IRC11:35
*** tuanla_____ has quit IRC11:36
*** andreas_s has joined #openstack-nova11:40
*** alexchadin has joined #openstack-nova11:41
*** alexchadin has quit IRC11:43
*** tetsuro has left #openstack-nova11:47
*** pooja-jadhav has joined #openstack-nova11:49
*** bhagyashri_s has joined #openstack-nova11:50
*** pooja_jadhav has quit IRC11:51
*** dklyle has quit IRC11:52
*** bhagyashris has quit IRC11:53
*** david-lyle has joined #openstack-nova11:53
*** andreas_s has quit IRC11:55
*** hrw has quit IRC11:58
*** pooja_jadhav has joined #openstack-nova11:59
*** AlexeyAbashkin has joined #openstack-nova11:59
*** pooja_jadhav has quit IRC11:59
*** andreas_s has joined #openstack-nova12:00
*** Supun has joined #openstack-nova12:01
*** bhagyashri_s has quit IRC12:01
*** pooja-jadhav has quit IRC12:01
*** pooja_jadhav has joined #openstack-nova12:01
*** bhagyashris has joined #openstack-nova12:02
*** alexchadin has joined #openstack-nova12:02
*** mvk has quit IRC12:02
*** fragatina has joined #openstack-nova12:02
*** andreas_s has quit IRC12:03
*** andreas_s has joined #openstack-nova12:03
*** ratailor has quit IRC12:05
*** belmoreira has joined #openstack-nova12:05
*** amorin has joined #openstack-nova12:08
amorinhey all12:09
amorincan someone help me with this/12:09
amorinhttps://review.openstack.org/#/c/508640/612:09
*** takashin has joined #openstack-nova12:09
*** liverpooler has quit IRC12:09
*** sree has joined #openstack-nova12:10
*** salv-orlando has quit IRC12:14
sauloaugustoSomeone can help me with this : Can't upgrade a READER transaction to a WRITER mid-transation after upgrade openstack nova .12:16
*** salv-orlando has joined #openstack-nova12:22
*** sree_ has joined #openstack-nova12:27
*** sree_ is now known as Guest4021512:27
*** salv-orlando has quit IRC12:29
*** sree has quit IRC12:30
*** salv-orlando has joined #openstack-nova12:32
*** jpena is now known as jpena|lunch12:33
*** janki has quit IRC12:48
*** moshele has quit IRC12:52
bauzasamorin: what's your problem with the above change ?12:55
bauzasamorin: that's because you recheck?12:55
bauzasthe gate has some problems atm12:55
*** mvenesio has joined #openstack-nova12:57
*** Eran_Kuris has quit IRC12:58
*** Eran_Kuris has joined #openstack-nova12:59
amorinbauzas: yes, I am rechecking13:05
amorinbut I was wondering,13:05
amorinbecause it's still failing at the same place (some kind of timeout)13:05
amorinis the solution to continue recheck?13:05
*** amoralej is now known as amoralej|lunch13:07
bauzasnot really13:07
bauzasthe gate has major performance issues AFAICS13:08
bauzasplus the fact we're close to the extended FF deadline makes a lot of changes being tested at the same time13:08
amorinok13:09
*** Guest40215 has quit IRC13:13
*** jaypipes has joined #openstack-nova13:14
*** mvk has joined #openstack-nova13:17
*** READ10 has joined #openstack-nova13:20
*** alexchad_ has joined #openstack-nova13:22
*** liverpooler has joined #openstack-nova13:23
*** vivsoni has quit IRC13:23
*** alexchadin has quit IRC13:24
*** vivsoni has joined #openstack-nova13:24
*** vladikr has joined #openstack-nova13:28
*** takedakn has joined #openstack-nova13:28
*** takedakn has quit IRC13:29
*** gszasz has quit IRC13:29
*** gszasz has joined #openstack-nova13:30
bauzaswow, the gate is really super slow13:31
bauzasmore than I thought I mean13:31
*** jpena|lunch is now known as jpena13:33
-openstackstatus- NOTICE: Zuul is currently under heavy load. Do not *recheck* or *approve* any changes until we give the go ahead.13:33
*** ChanServ changes topic to "Zuul is currently under heavy load. Do not *recheck* or *approve* any changes until we give the go ahead."13:33
*** Eran_Kuris has quit IRC13:33
*** alexchadin has joined #openstack-nova13:34
bauzasoh heh ^13:37
*** alexchad_ has quit IRC13:37
*** cleong has joined #openstack-nova13:38
gibi_this will be a slow monday13:38
*** bkopilov has quit IRC13:40
*** edmondsw has joined #openstack-nova13:41
*** gszasz has quit IRC13:41
*** alexchadin has quit IRC13:43
efriedgibi_ Howdy, thanks for "shoveling" :)13:45
*** hemna_ has joined #openstack-nova13:45
*** rmart04 has joined #openstack-nova13:46
*** moshele has joined #openstack-nova13:47
*** alexchadin has joined #openstack-nova13:47
*** Eran_Kuris has joined #openstack-nova13:48
gibi_efried: no problme. My effor might mean nothing considering the state of the gatea13:49
efriedgibi_ ikr13:49
gibi_anyhow it was a good warmup for the day :)13:49
*** Tom-Tom has joined #openstack-nova13:51
*** gszasz has joined #openstack-nova13:54
*** cdent has joined #openstack-nova13:57
edleafecrap, just rechecked a patch before I saw #topic13:58
*** sree has joined #openstack-nova13:58
bauzasedleafe: boooooooo13:58
edleafeAny way to un-recheck it?13:58
bauzasedleafe: just trigger a new patchset13:59
SpazmoticMan these XenAPI drivers just get worse the more I read13:59
edleafeWon't that start a check?13:59
SpazmoticLike that malcom in the middle gif where he goes to change the lightbulb..13:59
bauzasedleafe: ahem, you're right13:59
SpazmoticJust keep patching? hehe14:00
edleafeScheduler subteam meeting starting now in #openstack-meeting-alt14:00
bauzasedleafe: looks like per looking at -infra that they're restarting zuul anyway14:01
*** yamamoto has quit IRC14:01
bauzasedleafe: so your recheck should be harmless :p14:01
* edleafe breathes a sigh of relief14:01
*** slaweq has quit IRC14:02
*** slaweq has joined #openstack-nova14:02
*** mriedem has joined #openstack-nova14:03
*** sree has quit IRC14:03
*** artom_ has joined #openstack-nova14:04
*** artom has quit IRC14:04
andreykurilinmriedem: hi! do you know someone who use nova+openvz?14:04
mriedemhmmm14:05
SpazmoticI.. do...14:05
SpazmoticBut not really.. nevermidn i take it back don't ask me about it hehe14:05
mriedemandreykurilin: mnestratov and the vz people i guess...14:05
*** zhenguo has quit IRC14:05
mriedemi don't know about actual users14:05
SpazmoticI do know a group of folk that use it but it's fairly custom at this point as the openstack openvz drivers are long ded14:06
*** purplerbot has quit IRC14:06
*** purplerbot has joined #openstack-nova14:06
*** purplerbot has quit IRC14:07
*** purplerbot has joined #openstack-nova14:07
*** slaweq has quit IRC14:07
andreykurilinSpazmotic: ha. so nothing alive in upstream?14:09
openstackgerritBalazs Gibizer proposed openstack/nova master: DNM: test if tempest-full is triggered or not  https://review.openstack.org/53793614:09
mriedemvirtuozzo containers are supported via the libvirt driver in nova14:10
mriedemif we're talking about the same thing14:10
*** fragatina has quit IRC14:10
mriedemhttps://github.com/openstack/nova/blob/master/nova/conf/libvirt.py#L10514:11
*** fragatina has joined #openstack-nova14:11
mriedemyou'd use 'parallels' there14:11
mriedemandreykurilin: ^14:11
SpazmoticYeah mriedem is the man to know best there, I Think it used to have its own driver some time back but was deprecated by the Libvirt extension?14:11
Spazmoticsomething like that14:11
SpazmoticAny chance if some gracious core gets some free cycle they could check out this review?  I'm heading to Korea in like 5 days and don't want to let it sit for 2 weeks :) https://review.openstack.org/#/c/533168/14:12
andreykurilinso actually I do not know the "use-case". I was asked about the actual support and it looks like I found the answers. thanks mriedem and Spazmotic14:13
openstackgerritBalazs Gibizer proposed openstack/nova master: DNM: test if tempest-full is triggered or not  https://review.openstack.org/53793614:14
openstackgerritBalazs Gibizer proposed openstack/nova master: DNM: test if tempest-full is triggered or not  https://review.openstack.org/53793614:14
*** david-lyle has quit IRC14:15
*** psachin has quit IRC14:15
openstackgerritAmeed Ashour proposed openstack/nova master: change instance_system_metadata column type  https://review.openstack.org/52690014:16
mriedemandreykurilin: mnestratov is the person to ask from the vz team about their status14:17
mriedemthey are the maintainers of that support14:17
*** dmsimard is now known as dmsimard|afk14:17
mriedemmaxim nestratov14:17
andreykurilinthanks!14:17
*** yamamoto has joined #openstack-nova14:18
*** lyan has joined #openstack-nova14:19
*** r-daneel has joined #openstack-nova14:20
*** lyan has quit IRC14:24
*** edmondsw has quit IRC14:25
artom_stephenfin, kashyap, can I ask you guys to take a look at https://review.openstack.org/#/c/533805/2 when you get a chance? I *think* I got the libvirt XML part right, but would like expert second opinions :)14:28
*** artom_ is now known as artom14:28
*** superdan is now known as dansmith14:28
*** dave-mccowan has joined #openstack-nova14:28
*** edmondsw has joined #openstack-nova14:28
artomIt's a device tagging bug :(14:28
kashyapartom: Will try, "try" this week is bit stressful and jam-packed14:29
artomkashyap, no worries, appreciate it14:29
kashyapErr, /me rephrases that odd sentence14:29
kashyaps/"try"/"try" because/14:29
*** belmorei_ has joined #openstack-nova14:29
*** yikun_jiang has quit IRC14:30
-openstackstatus- NOTICE: we've been able to restart zuul, and re-enqueue changes for gate. Please hold off on recheck or approves, we are still recovering. More info shortly.14:30
*** yikun has joined #openstack-nova14:30
ameedagibi_: please check this https://review.openstack.org/#/c/526900/, I found way to get instance_system_metadata from here https://review.openstack.org/#/c/7045/5/nova/db/api.py14:31
*** ralonsoh_ has joined #openstack-nova14:32
*** belmoreira has quit IRC14:32
*** tssurya has quit IRC14:32
*** dave-mccowan has quit IRC14:33
*** dave-mccowan has joined #openstack-nova14:33
mriedemartom: how latent is that? not a regression in queens right?14:34
*** tssurya has joined #openstack-nova14:35
artommriedem, the PFs not being tagged thing?14:35
*** ralonsoh has quit IRC14:35
artommriedem, it was reported to us in Newton14:35
mriedemartom: ok14:35
mriedemjust weighing relative severity14:36
mriedem*urgency14:36
artommriedem, I don't think it was ever working14:36
artomBased on the code14:36
mriedemwas that a separate bp from tagged attach?14:37
mriedemmust have been14:37
artommriedem, it was the original device tagging14:37
mriedemoh14:37
artomWell14:37
mriedemi thought that was just ports and volumes?14:37
artomI don't think we ever explicitly decided what to do about PFs14:38
mriedemhttps://specs.openstack.org/openstack/nova-specs/specs/ocata/implemented/sriov-pf-passthrough-neutron-port-vlan.html14:38
artomBut since a PF can be a neutron port, they're implicitly taggable?14:38
mriedem^ is what i'm thinking of14:38
artomThat's vlans, slightly different14:38
artomBut... I don't think those are working either, btw14:38
mriedemgreat!14:38
artomvladikr had a thing up to fix it14:38
artomAnd his approach never made sense to me14:39
artomMaybe this is why14:39
mriedemred hat QE strikes again 2 years late14:39
artom(Speaking of QE, we found a problem with the scheduler bypass CVE fix for the fix)14:39
artom(Barely a week later!)14:39
mriedemthe error case?14:39
mriedemthat we fixed last week?14:39
artommriedem, yeah, if you rebuild again with the same image it goes through14:40
artomBecause there's a new image == old image check in the API14:40
artomI don't have an upstream bug filed yet, but here: https://bugzilla.redhat.com/show_bug.cgi?id=153970314:40
openstackbugzilla.redhat.com bug 1539703 in openstack-nova "By rebuilding twice with the same "forbidden" image one can circumvent scheduler rebuild restrictions" [Unspecified,New] - Assigned to eglynn14:40
mriedemoh b/c we didn't reset the image on failure in the scheduler14:41
artommriedem, https://review.openstack.org/#/c/468758/ vladikr's PF vlan thing14:41
mriedemwhich is what int32bit's patch was originally doing until i talked him out of it14:41
artomHis solution was to refresh info_cache, which seems weird14:41
artommriedem, well, properly rolling the changes back isn't trivial14:42
mriedemartom: yeah i know, which was my argument in the patch.14:42
mriedemlet's just revert rebuild14:42
artomOur of the nova api entirely? 100% behind you :)14:42
*** amoralej|lunch is now known as amoralej14:42
mriedemi'll add that bz to the queens rc etherpad14:43
artommriedem, I'll file a proper launchpad soon14:43
mriedemok thanks. i think this is an easy, albeit slightly ugly fix.14:44
*** Eran_Kuris has quit IRC14:44
artomWe've said that, what, 3 times now?14:44
mriedemjianghuaw: just to confirm, basic vgpu support for xenapi is merged, correct? the remaining patches are future work for integrating with nested resource providers?14:45
mriedemartom: but this time it's for real14:45
mriedemmelwitt: some updates on the cellsv1 job in stable issues over the weekend - i finally opened a bug to track it https://bugs.launchpad.net/nova/+bug/174583814:46
openstackLaunchpad bug 1745838 in OpenStack Compute (nova) "legacy-tempest-dsvm-cells constantly failing on stable pike and ocata due to libvirt connection reset" [Undecided,New]14:46
*** janki has joined #openstack-nova14:46
mriedemmelwitt: and it gets a bit messy, but we need to merge the changes to bump the nova-functional job timeouts, but for that to help, we need to drop the openstack-tox-functional jobs from running on nova, which depends on these changes in stable https://review.openstack.org/#/q/Ia684786d1622da7af31aa4479fc883a7c65848ff14:47
mriedemthose changes in stable kept failing the cellsv1 job, so i stopped running the cellsv1 job on stable: https://review.openstack.org/#/c/538619/14:47
jianghuawmriedem, yes for basic vgpu support.14:47
mriedemjianghuaw: thanks14:48
*** hoangcx has quit IRC14:49
*** salv-orlando has quit IRC14:49
*** hoangcx has joined #openstack-nova14:50
*** salv-orlando has joined #openstack-nova14:50
*** burt has joined #openstack-nova14:50
bauzasmriedem: jianghuaw: I'm working on a matrix patch that'll add the vgpu support14:51
bauzasmriedem: jianghuaw: I'll CC you the patch once I'm done14:51
jianghuawbauzas, thanks.14:51
*** lyan has joined #openstack-nova14:51
*** esberglu has joined #openstack-nova14:51
bauzasI also have in my pipe a possible functional test for testing server actions with VGPUs14:51
bauzasbut it requires me some fixture investigation14:52
jianghuawbauzas, I think display head is not in queens' plan. right? Although I have a patch for that.14:52
jianghuawhttps://review.openstack.org/#/c/52334214:52
*** sahid has quit IRC14:52
bauzasjianghuaw: Queens is done now14:52
bauzasfor features I mean14:52
*** gcb has joined #openstack-nova14:52
sauloaugustoIs there any channel for mova upgrade support ?14:53
jianghuawI see. the freeze-date has passed.14:53
jianghuawbauzas, I don't expect that can be merged:-)14:54
mriedemmelwitt: and at this point, ironically the nova-functional patches on stable are failing b/c of the openstack-tox-functional job timeouts, which we're trying to fix here, but we can't recheck anything until zuul is fixed14:54
*** salv-orlando has quit IRC14:55
*** mvenesio has quit IRC14:55
*** Eran_Kuris has joined #openstack-nova14:57
mriedemmelwitt: oh btw, the cellsv1 job failures started around 1/18 which is around the same time as that python2.7 update in xenial repos, which was causing other gate instability related to eventlet not monkey patching os.open,14:57
mriedemso i wondered if maybe there is some issue in libvirt-python or something in the older versions we're using on stable14:57
*** sahid has joined #openstack-nova15:00
*** takashin has left #openstack-nova15:00
efriedcdent You've got me confused.15:01
jaypipesefried, cdent: reading the vmware mail thread now..15:01
*** yangyapeng has quit IRC15:01
*** lucasagomes is now known as lucas-hungry15:01
cdentefried: that's my goal in life15:01
efriedjaypipes cdent Note there's a followup that did go to the -dev ML.15:01
*** gibi_ is now known as gibi15:01
efriedcdent The part I'm confused about is: where were we ever talking about "negative traits"?15:02
cdentwe weren't15:02
jaypipesefried: there's no such thing as a negative trait.15:02
*** r-daneel_ has joined #openstack-nova15:02
jaypipesefried: something either has or doesn't have a trait.15:02
*** zhaochao has quit IRC15:02
cdentwe were talking about how to not consume resources that have a trait when we don't care about that trait15:02
efriedWe were?15:03
jaypipescdent: resources don't have traits. providers have traits.15:03
cdentjaypipes: I know, but naming it hard15:03
jaypipescdent: did you mean consuming resource from a provider that doesn't have a trait?15:03
cdentjaypipes: no15:03
cdentlet me explain15:03
cdentgiven two providers with equal inventory, one has trait X15:04
jaypipesefried: do you want me to respond to the ML part and not the private email?15:04
*** r-daneel has quit IRC15:04
*** r-daneel_ is now known as r-daneel15:04
cdentwe make a query for allocation candidates that both poviders can satisfy15:04
*** slaweq has joined #openstack-nova15:05
cdenthow do we say "don't use the provider that has trait X"15:05
openstackgerritStephen Finucane proposed openstack/nova stable/pike: tests: Use correct response type in tests  https://review.openstack.org/53893815:05
efriedPerhaps it would be best if cdent replied to the ML one with whatever's still relevant from the private thread; then you can respond to that.  Keep the thread linear-ish.15:05
openstackgerritStephen Finucane proposed openstack/nova stable/pike: Handle images with no data  https://review.openstack.org/53893915:05
gibiameeda: sure, you can get sysmeta from the db, but I thought, based on the comments, that you are trying to find a way to get sysmeta via the REST API15:05
jaypipescdent: you don't. you just don't include the trait in required_traits= param.15:05
jaypipescdent: it's a sorting/weighing/preference problem, not a filtering problem.15:05
*** awaugama has joined #openstack-nova15:05
cdentjaypipes: right, that's basically what I say at the end of my message15:05
openstackgerritStephen Finucane proposed openstack/nova stable/pike: Handle images with no data  https://review.openstack.org/53893915:05
jaypipesgotcha15:05
efriedcdent But I don't see how that's relevant to the discussion15:06
efriedI totally didn't pick up on any part of rado's original note that implied we needed/wanted to do that.15:06
mriedemstephenfin: question in that backport15:07
cdentefried: rado was expressing concern about allocations being made to the wrong pool when not expressing the trait15:07
jaypipesefried: the fundamental problem with the vmware conversation is that resource pools are being represented with nested providers instead of aggregates. aggregates are the thing that provides the "grouping" concept that the resource pools represent. nested providers represent a different relationship: that of dependent trees of providers.15:07
*** mdnadeem has quit IRC15:07
cdent"is there a way to make the scheduler allocate only from one specific RP if no custom trait is specified in the request"15:07
efriedHeh.  Oh.  I took a much simpler approach to that question.  It went like this: "No."15:08
cdentThe complicating factor here is that I think nested is _exactly_ the model for how resource pool are supposed to work15:08
efriedjaypipes ++ and in fact trying to use NRP for pools will break horribly15:08
efriedoh, wow, okay, clearly starting on opposite ends of the rope.15:09
efriedcdent Can you describe that hierarchy please?15:09
cdentbecause they represent a hierarcy of containment15:09
*** slaweq has quit IRC15:10
*** yamahata has joined #openstack-nova15:10
cdentso, nrp came about in part because of numa and pci relationships, right?15:10
efriedcdent Have you seen the response I made to the ML yet?  I want to baseline and make sure I've got my idea of the hierarchy down before we go any further.15:10
cdentefried: yes, I've read it twice and still trying to make sure i understand it15:10
efriedk15:10
*** moshele has quit IRC15:11
*** r-daneel has quit IRC15:11
stephenfinmriedem: Reply left. tl;dr: I think we're fine for stable/pike15:11
*** r-daneel has joined #openstack-nova15:11
stephenfinassuming I'm reading g-r correctly15:11
mriedemwe just need 2.8.0?15:12
*** hongbin has joined #openstack-nova15:12
cdentthe thing about your model which is not necessarily desirable is the way in which esxi hosts are managed as a concrete resources. vcenter doesn't really want to do that (although it is possible and would be a reasonable fallback)15:12
stephenfinmriedem: 2.6.0+15:12
*** gus has quit IRC15:13
efriedjaypipes The aggregate model won't allow you to request a deploy to a specific resource pool.  But maybe I'm misunderstanding the original intent, which I thought was to do just that.15:13
*** Eran_Kuris has quit IRC15:13
cdentthe intent is to deploy to a specific resource pool15:13
*** eharney has joined #openstack-nova15:13
cdentif you have an aggregate for each specific resource pool, that might be workabe15:14
*** gus has joined #openstack-nova15:14
efriedBut you still can't deploy to a specific resource pool with just that.15:14
cdentbrb15:14
efriedYou would have to have some other mechanism in place.15:14
mriedemcan you add a custom filter and custom scheduler hint which is just 'make it go directly here'15:14
jaypipesefried: uhm, yeah you could request a specific aggregate...15:15
efriedjaypipes How?15:15
efriedWith some mechanism yet to be designed?15:15
jaypipesefried: we already have the member_of param. we can work that in to alloc candidates very easily.15:15
*** lajoskatona has quit IRC15:15
efriedokay, agree, but not yet designed or started.15:16
jaypipesefried: of course, that would require the users knowing about the aggregate UUID/names...15:16
jaypipesefried: which generally we have not encouraged.15:16
mriedemstephenfin: got it15:16
mriedemthanks15:16
mriedemthere is no aggregate name https://developer.openstack.org/api-ref/placement/#list-resource-provider-aggregates15:17
jaypipesmriedem: sorry, UUID...15:17
jaypipesefried: still, what is the root of the problem that is trying to be solved?15:17
cdentIt remains unclear to me why (eventually) nested isn't the ideal solution for this stuff? A compute-node is an rp, it cotains resource pool rps and maybe even some exsi rp, a hybrd representing the stuff managed by the conpute node15:18
jaypipesefried: I mean, are we doing scheduling here or are we just doing resource tracking and vcenter basically takes over the scheduling/placement decisions (that's what I *thought* the situation was currently...)15:18
mriedemsounds like the latter15:18
stephenfinmriedem: Is this something that should wait for a few weeks? https://review.openstack.org/#/c/534371/15:19
mriedemstephenfin: is that just cleanup? if so, yes15:19
efriedsorry guys, pulled into a quick meeting, back in a bit.15:19
mriedemstephenfin: we're in bug fix only mode at this point15:19
stephenfinmriedem: (y)15:19
mriedemor tests, docs, etc15:19
*** hoangcx has quit IRC15:20
*** hoangcx has joined #openstack-nova15:21
*** bhagyashris has quit IRC15:21
*** bhagyashris has joined #openstack-nova15:21
*** pooja-jadhav has joined #openstack-nova15:22
cdentjaypipes: the underlying feature that rado wants to expose here are resource pools and he wants to do it in a way that allows placement to be aware of them15:22
*** Supun has quit IRC15:22
*** awaugama has quit IRC15:22
jaypipescdent: will the *end user* be capable of a) understanding what these resource pools are and b) asking for a particular resource pool to be used by an instance?15:22
cdentjaypipes: yes. "tenant virtual data center"15:23
*** hemna_ has quit IRC15:23
*** stvnoyes has joined #openstack-nova15:23
stephenfinlyarwood (or another stable-core): fancy hitting these? https://review.openstack.org/#/c/538939/ https://review.openstack.org/#/c/538938/15:23
*** pooja_jadhav has quit IRC15:23
jaypipescdent: why not have multiple nova-compute services, each managing a single "resource pool"?15:24
*** Supun has joined #openstack-nova15:25
*** awaugama has joined #openstack-nova15:26
cdentbecause the clusters behind a nova-compute service are intentionally dynamic: it's desirable to be able to create destroy and change resource pools in the cluster without messing with the openstack control plane much15:26
*** moshele has joined #openstack-nova15:26
efriedI'm back.15:27
efriedcdent Do these clusters / resource pools (are those different things) contain single compute-ish nodes to which instances get deployed, OR do they contain some general pool of resources from which an instance could be deployed using some resource from one member and some from another?15:27
jaypipescdent: that's problematic for many reasons, as you know.15:28
*** tidwellr has joined #openstack-nova15:28
*** mlavalle has joined #openstack-nova15:28
cdentjaypipes: yes, but problematic is how we push the ball forward, no? efried cluster and resource pools are different, yes. logically an instance is deployed to a resource pool and not a specific host (although physically they are, of course)15:29
cdenta cluster contains 1 or more resource pools15:30
cdenta resource pool has access to some (dynamic) subsection of a clusters inventory15:30
efriedAre physical hosts the underlying members of a resource pool?15:31
cdentefried: that's not really the way it is modeled, no, but I'm not sure what you're actually asking15:32
efriedcdent I'm just not understanding where the physical resources are here.15:32
jaypipescdent: what does the vmware virt driver *currently* do? does it report the entire amount of VCPU, memory, etc for all resource pools and all clusters that vCenter knows about?15:32
*** liangy has joined #openstack-nova15:33
*** mylu has joined #openstack-nova15:33
jaypipescdent: and the scheduler always picks the single nova-compute service daemon and basically all scheduling/placement is simply deferred to the vCenter API?15:33
cdentright now: the vcenter represents one cluster, and reports all vcpu, memory, etc that it knows abouts15:33
cdentbut there are a multiple nova-copute services, each for a given cluster15:34
jaypipescdent: I'm not seeing the benefit of modeling things using placement's resource providers data modeling if deployments using vCenter won't actually end up using any of that information when doing placement/scheduling decisions anyway.15:34
*** lyan has quit IRC15:35
*** alexchadin has quit IRC15:37
cdentjaypipes: two reasons a) if you have multiple clusters, and thus multiple nova-compues, and those clusters differet in various ways (for example by having different tenant virtual data centers) you need to scheduler differently, b) despite our troubles, we've made a very good resource/provider/inventory/etc modelling system with placement and it is a good place to track and select where to place things15:37
cdent"this cluster over there is the one with all the GPUs"15:38
*** pooja-jadhav has quit IRC15:38
efriedcdent It'll help me a lot to understand what is underneath a resource pool.  If a resource pool reports a total of 8 VCPUs available, does that mean I am guaranteed to be able to satisfy a deploy requesting 8 VCPUs?  (All other things being available)15:38
efriedCause I got the impression that those 8 VCPUs might be spread across say four physical hosts, and an instance could only go to one of those, so the biggest one you could handle might only be 2 VCPUs or whatever.15:39
*** r-daneel_ has joined #openstack-nova15:39
*** r-daneel has quit IRC15:40
*** r-daneel_ is now known as r-daneel15:40
* efried pauses to give props to r-daneel for having an awesome nick15:40
jaypipescdent: for a) if the end user is just saying "I'm in tenant X, so launch an instance on virtual data center X", that is a stupid-simple scheduling decision that needs nothing other than a single trait (CUSTOM_TENANT_X decorates a single resource provider representing the nova-compute service that manages that tenant virtual data center). For b) again, if vCenter isn't going to use that information in its intra-cluster scheduling decisions, I15:40
jaypipesdon't see the point.15:40
*** bhagyashris has quit IRC15:40
jaypipescdent: another question for you..15:42
cdentjaypipes: can I pause you for a minute while I answer efried, then your current question?15:42
*** sree has joined #openstack-nova15:43
jaypipescdent: even if placement ended up getting proper inventory information for these vCenter clusters, would VMWare OpenStack users actually be able looking at that inventory information? Or would they be using VMWare GUIs to look at inventory information for their specific tenant virtual datacenter?15:43
*** efried1 has joined #openstack-nova15:43
jaypipescdent: of course, no worries15:43
cdentefried: a while back there were some adjustment made to the vmware driver to make sure that the max_unit was no greater than what any individual host could provide. so your second statement about "the biggest one" is an issue in some cases, but it's squishy because of the DRS (dynamic resource scheduler thing which can do unattended live migrations and what not, magic stuff I haven't dug into)15:44
efriedSo it is in fact the case that there are some number of physical hosts behind a resource pool, and an instance can only be deployed to one, not spread out across more than one.  True statement?15:46
cdentefried: so, yes, there is a fair bit of complexity which is _why_ being able to manipulate the entire provider tree from within the virt driver has been of such interest to rado (and me).15:46
*** claudiub has joined #openstack-nova15:46
jaypipesmaciejjozefczyk: you around? wanted to chat with you about https://bugs.launchpad.net/nova/+bug/174274715:46
openstackLaunchpad bug 1742747 in OpenStack Compute (nova) "RT overrides default allocation_ratios for ram cpu and disk" [Undecided,In progress] - Assigned to Maciej Jozefczyk (maciej.jozefczyk)15:46
cdentefried: it can move and you can never know that it did15:46
efried"it" the physical host? "can move" to another resource pool? and "you" the virt driver or you the operator?15:47
*** gcb has quit IRC15:47
jaypipescdent: with the shared-memory solution, can't VMs literally be on multiple hypervisor hosts at once?15:48
maciejjozefczykjaypipes: yes, hey!15:48
jaypipesmaciejjozefczyk: you see my note on that bug?15:48
*** claudiub|3 has joined #openstack-nova15:48
*** esberglu has quit IRC15:48
*** pooja_jadhav has joined #openstack-nova15:49
*** moshele has quit IRC15:49
*** hemna_ has joined #openstack-nova15:49
*** claudiub|2 has quit IRC15:49
maciejjozefczykjaypipes: reading15:49
*** esberglu has joined #openstack-nova15:49
cdentjaypipes: I've done my damnedest thus far to stay out of the guts of what vcenter gets up to, but there's plenty of magical knobs, but I'm trying to avoid knowing about them. there's already too many things to know15:49
*** namnh has joined #openstack-nova15:49
jaypipescdent: ack15:49
cdentefried: it is the instance15:50
*** bhagyashris has joined #openstack-nova15:50
efriedokay.  "move" where, inter-pool or just intra-pool?15:50
efriednot that it actually matters.15:50
*** salv-orlando has joined #openstack-nova15:51
*** claudiub has quit IRC15:51
maciejjozefczykjaypipes: so we should also check aggregation metadatas if there is already definition of allocation ratio defined?15:51
maciejjozefczykif zeros are in config?15:51
jaypipesmaciejjozefczyk: yeah. check out that operators mailing list thread I linked in there...15:51
cdentefried: intra-cluster.15:52
efriedcdent So the thing is, we didn't have a way to model multiple providers before.  Now we do.  But it sounds to me like nested is *not* the multiple-provider model we want to use here.  It just doesn't make sense in light of recently-merged capabilities for a single provider *or* tree to "own" inventory spanning more than one actual compute host.  (Unless, as jaypipes implies, there's a memory sharing thing - we can talk abou15:52
efriedt that later.)15:52
openstackgerritMatt Riedemann proposed openstack/nova master: WIP: Add regression test wrinkle for rebuilding twice with invalid image  https://review.openstack.org/53895515:52
mriedemartom: ^15:52
*** mylu has quit IRC15:53
efriedcdent If you do it in a single provider OR a tree, you'll always have to reconcile a request for some subset of the total resources that you can't actually satisfy from any one host.15:54
artommriedem, I think you'd have to get the server out of ERROR first15:54
*** hemna_ has quit IRC15:54
* artom files the launchpad15:54
*** mylu has joined #openstack-nova15:55
efriedcdent With the single-provider model, which I gather is how it has needed to be done to this point, it sounds like some of that reconciliation was that max-unit hack.15:55
jaypipesefried: yeah. I think it's a much better solution for vCenter to model their resource tracking in the vCenter virt driver in a similar fashion to how Ironic's virt driver works.15:55
*** salv-orlando has quit IRC15:55
cdentefried: I have no issue with the inventory for hardware things being pushed all the way down the real hardware, but I _do_ think that representing the hierarchical relationships between things using a tool we've created that has hierarchy makes sense (in this case cluster->resource-pool->physical host)15:55
jaypipesefried: that wouldn't *preclude* using nested providers if, say, certain compute nodes had PCI devices or NUMA nodes, etc. But I would use a new root provider for each compute node in the cluster and represent the cluster as a placement aggregate, not as a child node under a "fake root"15:56
efriedjaypipes ++ exactly15:56
*** david-lyle has joined #openstack-nova15:56
jaypipescdent: I think we're mostly agreeing. just disagreeing on the "single root vs multiple roots" thing.15:57
*** sree_ has joined #openstack-nova15:57
gibimriedem: quick question: There is a bugfix https://review.openstack.org/#/c/525242 that needs rpc version bump. Is it something that needs to wait for Rocky?15:57
*** felipemonteiro has joined #openstack-nova15:57
efriedcdent A placement tree is more than just a way to represent a hierarchy.  It is also allows resource requests to span a tree.  Which doesn't make sense in the vcenter model as I'm undestanding it.15:57
*** sree_ is now known as Guest6445615:57
mriedemartom: you can rebuild an ERROR server15:57
cdentefried: then I think it probably hasn't been explained well enough15:58
*** eharney has quit IRC15:58
artommriedem, hah, that makes it even easier to hit15:58
mriedemgibi: that doesn't necessarily mean it has to wait for rocky,15:58
mriedemgibi: but it does mean we wouldn't backport it15:58
maciejjozefczykjaypipes: I'm ok with the idea to check aggregation metadatas first15:58
*** ircuser-1 has joined #openstack-nova15:58
gibimriedem: OK. Then I'm going to rebase the above patch15:59
gibimriedem: the backport impossibility was agreed earlier so that is clear15:59
jaypipesmaciejjozefczyk: ok. with your operator hat on, what do you think about my proposal, considering it involves a technically not backwards-compatible behaviour change?15:59
*** sree has quit IRC15:59
*** belmorei_ has quit IRC15:59
efriedcdent I think I get that logically, conductor < cluster <=> n-cpu < resource pool < compute hosts (right?) and from that perspective you want to be able to "model" that structure as a tree.15:59
*** lucas-hungry is now known as lucasagomes15:59
cdentefried, jaypipes: I'd be much better at this conversation if I wasn't still fighting off this cold, but it's not just the desired to model, there's also a desire to do some accounting16:00
* cdent tries to decode efried's symbols16:00
*** moshele has joined #openstack-nova16:00
* cdent fails16:00
efriedcdent    1 < many    and 1 <=> 116:00
*** eharney has joined #openstack-nova16:01
*** tidwellr has quit IRC16:01
maciejjozefczykjaypipes: From my perspective it would not change anyting, I set allocation_ratio per host not per aggregate, so my opinion seems not be helpful16:01
*** felipemonteiro has quit IRC16:01
jaypipesmgagne: hey! :)16:01
mgagnejaypipes: hi!16:02
jaypipesmgagne: we're talking about your favorite new anti-feature regarding host aggregates and allocation ratios :)16:02
mgagnejaypipes: I just saw your email =)16:02
jaypipesmgagne: cool. I'm hoping to commandeer maciejjozefczyk's patch to add this fix for you.16:02
jaypipesof course, I'm trying to convince maciejjozefczyk that this would be of benefit ;)16:03
mgagnejaypipes: I have yet to properly analyze your suggestion and related bug report.16:03
jaypipesmgagne: no worries, would be good to get your feedback some time today.16:03
*** tidwellr has joined #openstack-nova16:03
jaypipesmgagne: I'm going to ping melwitt on it when she's up, too.16:03
mgagnejaypipes: sure16:03
*** tesseract has quit IRC16:03
sauloaugustoIs it possible to setup pike without cells ?16:04
openstackgerritSen Yang proposed openstack/python-novaclient master: Implement hypervisor hostname exact patten match for server cold migrate  https://review.openstack.org/52018716:04
jaypipessauloaugusto: nope.16:04
*** namnh has quit IRC16:04
efriedcdent So I think where we're getting to is this: You could have your nice satisfying model, and have to hack the inventory distribution to make it work; or you could have a flatter model that's less closely representative of the "real world", but your inventorying is simple, and accounting flows automatically from scheduling/allocations.16:04
*** jappleii__ has quit IRC16:05
efriedcdent ...except for the part where vcenter is gonna move an instance from one host to another.  Yeah, that gets a tad hairy without having done a real live migration or whatever.16:05
sauloaugustojaypipes: Is there any clue about the error when you migrate from a no cell env to pike and you can only list instances from admin tenant ?16:05
dansmithsauloaugusto: that doesn't sound like a cells-related thing16:06
*** hemna_ has joined #openstack-nova16:06
*** jmlowe_ has quit IRC16:07
dansmith(the cells code doesn't do anything special with users/tenants)16:07
cdentefried: having allocations against physical hosts (instead of the cluster) cannot work because instances move and we've declared the virt driver is not allowed to manipulate allocations16:07
efriedcdent Yeah, I see where that's a problem.  I don't have an answer for that.16:07
*** jmlowe has joined #openstack-nova16:07
cdentthus inventory on resource pools16:08
efriedand resultant hackage.16:08
efriedwhich is unfortunate.16:08
maciejjozefczykjaypipes mgagne: Need to go. Let me know in bug report about what you decided okey ;) I'll update the patch then16:08
cdentbecause that is the level at which accounting is desired16:08
*** fragatina has quit IRC16:08
jaypipesmaciejjozefczyk: will do, thanks mate :)16:08
*** lyan has joined #openstack-nova16:08
*** maciejjozefczyk is now known as maciejjozefczyk_16:08
efriedcdent Well, at the very least the resource pools should not be children in the same tree.  They should be roots.16:09
* efried1 discovers that Thunderbird has an IRC client.16:10
openstackgerritMatt Riedemann proposed openstack/nova master: Rollback instance.image_ref on failed rebuild  https://review.openstack.org/53896116:10
mriedemartom: here is the fix ^ let me know when you have an LP bug number so i can update the references in here16:10
artommriedem, yep, writing it up as we speak16:10
cdentefried: remind me (because I'm half asleep) of the mechanism to go from a root (when in nova-scheduler) to the compute node where the spawn can be called?16:11
sauloaugustodansmith: I think that is related , because the error start after I do themigration steps from nova . After that I start to see the Can't upgrade a READER transaction to a WRITER mid-transaction error on nova-api.log .16:11
cdentefried: if the root is in fact not that compute-monde16:11
artommriedem, so we're rolling back the image but not other things that could change, like keypair?16:11
openstackgerritBalazs Gibizer proposed openstack/nova master: Add regression test for bug 1735407  https://review.openstack.org/52609516:11
openstackbug 1735407 in OpenStack Compute (nova) "[Nova] Evacuation doesn't respect anti-affinity rules" [Medium,In progress] https://launchpad.net/bugs/1735407 - Assigned to Balazs Gibizer (balazs-gibizer)16:11
openstackgerritBalazs Gibizer proposed openstack/nova master: Add late server group policy check to rebuild  https://review.openstack.org/52524216:11
mriedemartom: yeah - which was my original complaint in the earlier fix16:11
dansmithsauloaugusto: the migration steps from no cells to one cell were required before pike16:12
efriedcdent Not sure we quite have that mechanism yet.16:12
mriedemartom: we can't really roll everything back with what we have today in the conductor code16:12
mriedemwe'd either have to change the rpc cast to a call, or move the code that changes the instance from the api to conductor16:12
cdentefried: indeed, thus why  I've been modelling it the way I've been16:12
efriedcdent Yeah, a way to tie these brother-roots back to the compute host for purposes of allocation and deploy.16:12
cdentif it is a child you know where to go16:12
mriedemhell, maybe we should have just moved the instance.save() from api to conductor...16:12
artommriedem, yeah... I guess it's fine as a bandaid for now? Ideally we need to come back to this and fix it properly, maybe like what Andrey was proposing16:12
cdentbecause16:12
cdentit is a child16:12
mriedemartom: yes this is a "tactical fix"16:13
cdenta resource provider withing a compute-node is _obviously_ a child16:13
efriedcdent But if it's a child, the scheduler will happily deploy an instance with VCPU from pool1, MEMORY_MB from pool2, and DISK_GB from pool3.16:13
cdentand it seems to me that the ironic model might be the thing that's weird16:13
artommriedem, heh, code for "someone else can deal with it once I'm retired" ;)16:13
efriedcdent Unless you *always* use a numbered granular group.  Which doesn't seem like the right answer.16:13
mriedemmaybe - it's just something one of my old managers at ibm always said,16:13
cfriesenjaypipes: for https://bugs.launchpad.net/nova/+bug/1742747 do we look at the cpu_allocation_ratio of the first host aggregate, or do we look for the first host aggregate that has cpu_allocation_ratio set?16:13
openstackLaunchpad bug 1742747 in OpenStack Compute (nova) "RT overrides default allocation_ratios for ram cpu and disk" [Undecided,In progress] - Assigned to Maciej Jozefczyk (maciej.jozefczyk)16:13
mriedem"do we have a tactical fix while we work on the long-term strategic fix"16:13
*** slaweq has joined #openstack-nova16:14
artommriedem, not a bad way of thinking16:14
efriedI was doing a word puzzle the other day where the clue was "strategic" and the answer was "tactical".  I thought how the IBM ppt-jockeys would flip out at that.16:14
*** slaweq has quit IRC16:14
artomawaugama, you around? Since you're the cause of all this, if we build you our proposed tactical fix, you want to try and break it again?16:14
sauloaugustodansmith: Yes I did that, and I get get list o admin instances , and also create new instances at that . The problem that I can not do nothing at all other tenants .16:14
artomMaybe if we let QE loose on it *before* merging it, we'll avoid the pain?16:14
awaugamaartom: I can do some sanity checks on it16:15
mriedemartom: that never seems to happen16:15
mriedemuntil it's in product16:15
*** ircuser-1 has quit IRC16:15
awaugamaartom, and *Technically* I'm just the warning light, i'm not the cause of the issue16:15
artomawaugama, hah, sorry, should have added a ;) or /s in there somewher e:)16:15
awaugama;)16:15
cdentefried: these issues are why I pressed rado to start talking about and experimenting with this stuff. I think the sort of gravitational mechanics of nested providers is going to have lots of weird16:15
cdentand I'd much prefer to see us working from concrete situations then not16:16
efriedcdent Agree.  At the moment I'm actually leaning towards the thing I originally said was the worst idea: always using a single numbered request group.16:16
*** mylu has quit IRC16:17
SpazmoticAlways good when the best idea is your worst idea16:17
*** felipemonteiro has joined #openstack-nova16:18
*** links has quit IRC16:20
cdentefried: I guess we have time to experiement...16:21
*** felipemonteiro_ has joined #openstack-nova16:21
*** 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/Queens_Release_Schedule"16:21
-openstackstatus- NOTICE: zuul.o.o is back online, feel free to recheck / approve patches.16:21
*** moshele has quit IRC16:22
*** chyka has joined #openstack-nova16:22
*** chyka has quit IRC16:22
*** chyka has joined #openstack-nova16:23
*** felipemonteiro has quit IRC16:25
artommriedem, https://bugs.launchpad.net/nova/+bug/174603216:25
openstackLaunchpad bug 1746032 in OpenStack Compute (nova) "By rebuilding twice with the same "forbidden" image one can circumvent scheduler rebuild restrictions" [Undecided,New]16:25
*** pcaruana has quit IRC16:25
mriedemartom: L145 https://etherpad.openstack.org/p/nova-ptg-rocky16:27
*** yamamoto has quit IRC16:28
artommriedem, oh hey and I'll actually be there this time :)16:28
mriedemwe can finally meet, face to face, and settle all the scores16:28
openstackgerritBalazs Gibizer proposed openstack/nova master: Enhance service restart in functional env  https://review.openstack.org/51255216:28
openstackgerritBalazs Gibizer proposed openstack/nova master: Reproduce bug 1724172 in the functional test env  https://review.openstack.org/51255316:28
openstackbug 1724172 in OpenStack Compute (nova) "Allocation of an evacuated instance is not cleaned on the source host if instance is not defined on the hypervisor" [Undecided,In progress] https://launchpad.net/bugs/1724172 - Assigned to Balazs Gibizer (balazs-gibizer)16:28
openstackgerritBalazs Gibizer proposed openstack/nova master: cleanup evacuated instances not on hypervisor  https://review.openstack.org/51262316:28
mriedemthere can be only one16:28
artom... one of *what*?16:28
mriedemidk, i'm just thinking about the quickening16:29
mriedemeven though that was scotland16:29
artomMan, your references are out of control!16:29
*** yangyapeng has joined #openstack-nova16:30
*** rmcall has joined #openstack-nova16:31
edleafecdent: I've been following along, but don't have a clear picture of how things are arranged. Is there a diagram or something that would illustrate this?16:31
cdentedleafe: a) which "this"?, b) I wish I never showed up today because I simply don't have the capacity to actual engage well with this topic16:32
openstackgerritMatt Riedemann proposed openstack/nova master: Rollback instance.image_ref on failed rebuild  https://review.openstack.org/53896116:32
mriedemartom: ok here we go, single patch ^16:32
edleafecdent: the arrangement of entities in vmware16:32
edleafeand which is the "root" that placement would be selecting16:33
mriedemstable/newton is still open....but not sure we want to hold up EOL for this fix16:34
*** yangyapeng has quit IRC16:34
*** slaweq has joined #openstack-nova16:34
SpazmoticKorea in.. 6 days16:35
SpazmoticWhew16:35
dansmithman, newton is like the undead release16:36
efriededleafe I was considering drawing that up, along with an executive summary of this conversation, and putting it all in a response to the ML thread.16:36
artomCan we call U 'undead'? As an hommage?16:36
cdentedleafe: not that I'm aware of at this time, but I'll check with rado. if efried is able to do something (even if it has errors), that provides at least a starting point16:36
*** sahid has quit IRC16:37
cdentthe "root" I was thinking of was "compute-node"16:37
mriedemi'll say it again, the path to LTS upstream is just never EOL'ing anything16:37
edleafecdent: ok, thanks. I assumed that there must be some internal documentation that would be helpful16:37
*** sahid has joined #openstack-nova16:37
*** andreas_s has quit IRC16:37
*** andreas_s has joined #openstack-nova16:38
cdentedleafe: could very well be, but if there are pretty pictures I haven't seen them. That doesn't mean it doesn't exist. I interact _very_ little on that side of things.16:38
SpazmoticAnyone know any of the cores familiar with XenAPI drivers?  Besides Garbutt that is, I got his attention on but was curious if any others were familiar that I could poke :D16:38
openstackgerritStephen Finucane proposed openstack/nova master: mypy: Add type annotations to 'nova.pci'  https://review.openstack.org/53822416:39
openstackgerritStephen Finucane proposed openstack/nova master: mypy: Add 'types' module  https://review.openstack.org/53822516:39
edleafecdent: ok, cool. If you come across something, post it so we can all better understand what is needed16:39
*** felipemonteiro_ has quit IRC16:40
efriedSpazmotic Maybe bauzas ?16:41
artomWasn't Bob Ball xenapi? Is he still around?16:41
SpazmoticI know the driver isn't looked at too frequently by folks, so just didn't want to bark up the wrong trees wwhen I had questions or was looking for some eyeballs.16:41
SpazmoticYeah bob's still around but he's no longer core16:41
*** andreas_s has quit IRC16:41
SpazmoticHe always gives me good ideas though so.. love me some Bob16:42
*** andreas_s has joined #openstack-nova16:42
*** andreas_s has quit IRC16:42
*** jose-phillips has quit IRC16:43
*** andreas_s has joined #openstack-nova16:43
*** yamamoto has joined #openstack-nova16:43
*** jose-phillips has joined #openstack-nova16:44
*** jpena is now known as jpena|brb16:44
openstackgerritMatt Riedemann proposed openstack/nova master: Rollback instance.image_ref on failed rebuild  https://review.openstack.org/53896116:47
mriedemartom: jaypipes: added a variable for the original image ref and a comment about CastAsCall16:47
*** slaweq_ has joined #openstack-nova16:47
*** tesseract has joined #openstack-nova16:47
mriedemSpazmotic: johnthetubaguy knows the xenapi stuff16:47
mriedemand is still core, but not working as much upstream these days16:48
*** burt has quit IRC16:48
artommriedem, and defiantly ignored my grammar nit ;)16:48
SpazmoticYeah he's been busy with family stuff.. I got in touch with him the other day though, but figured i'd ask since we need 2 cores16:48
*** yamamoto has quit IRC16:48
johnthetubaguyyeah, I am around for some questions, much of the time16:48
openstackgerritMatt Riedemann proposed openstack/nova master: Rollback instance.image_ref on failed rebuild  https://review.openstack.org/53896116:48
mriedemartom: there you go16:48
SpazmoticNow look what you did16:48
johnthetubaguy(still trying to juggle back more reviewing time)16:48
mriedemit's is always something i'll think of since school as a possessive16:49
artommriedem, cheers :)16:49
Spazmotichehe spend time with your family john, more important than reviews :D16:49
jaypipesmriedem: danke16:49
*** sahid has quit IRC16:50
mriedemjohnthetubaguy: if you are around, i'll badger you about https://review.openstack.org/#/c/527541/16:51
*** salv-orlando has joined #openstack-nova16:51
*** yamamoto has joined #openstack-nova16:51
*** yamamoto has quit IRC16:51
johnthetubaguymriedem: sure thing16:51
*** slaweq_ has quit IRC16:52
*** andreas_s has quit IRC16:52
*** Guest64456 has quit IRC16:53
johnthetubaguymriedem: is the TODO about jay's join magic important?16:53
mriedemno16:54
*** salv-orlando has quit IRC16:54
*** salv-orlando has joined #openstack-nova16:54
jaypipesquoi?16:54
*** eharney_ has joined #openstack-nova16:54
johnthetubaguyhttps://review.openstack.org/#/c/527541/4/nova/cmd/status.py@41316:54
mriedemhttps://review.openstack.org/#/c/527541/4/nova/cmd/status.py@41316:54
mriedemyeah16:54
Spazmoticsomeone owes someone a coke dependant upon latency and such16:55
mriedemjaypipes: it's a nova-status check for ironic / instance flavor migration16:55
mriedemsomething we should have done in pike, so i plan on backporting16:55
*** sauloaugusto has quit IRC16:55
jaypipesah, k16:56
*** andreas_s has joined #openstack-nova16:57
*** rmart04 has quit IRC16:58
*** eharney has quit IRC16:58
mriedemgibi: speaking of things i don't think we want to backport if we can help it https://review.openstack.org/#/c/522112/16:59
mriedem^ adds the ability to specify service/admin user creds for cinder operations,16:59
mriedemlike neutron16:59
mriedemso things like periodic tasks can actually detach/delete volumes once the user token is gone16:59
*** andreas_s has quit IRC17:01
*** fragatina has joined #openstack-nova17:01
*** janki has quit IRC17:04
*** janki has joined #openstack-nova17:05
*** janki has quit IRC17:09
*** eharney_ is now known as eharney17:12
*** armax has joined #openstack-nova17:14
*** Supun has quit IRC17:20
stephenfinjaypipes: Any chance you could take a look at this today? https://review.openstack.org/#/c/537363/17:21
*** Supun has joined #openstack-nova17:21
*** r-daneel_ has joined #openstack-nova17:21
*** r-daneel has quit IRC17:23
*** r-daneel_ is now known as r-daneel17:23
cfriesenmriedem: is there a reason not to use a service token here?  (other than that they're experimental)17:24
melwittmriedem: I wondered about that too (the eventlet os.open thing). I didn't realize the timing coincided with that update17:25
melwitt*the timing of the constant fails17:26
*** lpetrut has quit IRC17:27
*** gyee has joined #openstack-nova17:29
Spazmoticaigoo.. that's enough computers for today17:31
SpazmoticHave a good night everyone.17:31
*** jpena|brb is now known as jpena17:31
*** lyan has quit IRC17:31
*** yangyapeng has joined #openstack-nova17:31
*** mgoddard_ has quit IRC17:33
*** AlexeyAbashkin has quit IRC17:34
*** yangyapeng has quit IRC17:36
*** slaweq_ has joined #openstack-nova17:36
*** AlexeyAbashkin has joined #openstack-nova17:37
mriedemcfriesen: are you conflating the service user thing here?17:40
mriedemcfriesen: different issues17:40
*** slaweq_ has quit IRC17:40
*** mgoddard_ has joined #openstack-nova17:40
mriedemthe service user thing is for re-auth if a user token expires17:40
mriedemthis is different, it's just creds to be able to have nova do stuff when there is no user token17:41
mriedemthe service user token stuff for re-auth should probably no longer be called experimental17:41
*** AlexeyAbashkin has quit IRC17:41
*** Supun has quit IRC17:41
mriedemi don't know of anyone that's done performance testing with it at scale, but haven't heard anyone complain about it either, and it's optional17:41
*** mvenesio has joined #openstack-nova17:42
*** Supun has joined #openstack-nova17:42
mriedemcfriesen: speaking of performance, did you ever get any updates on the perf regression you reported last week/17:42
mriedem?17:42
jaypipesstephenfin: on it.17:43
melwittmriedem: this looks good, but are we supposed to not approve things yet because of zuul? https://review.openstack.org/#/c/53896117:47
*** fragatina has quit IRC17:47
cfriesenmriedem: we've got some additional data, but no smoking guns.  the cpu usage just seems higher overall, with the cpu usage of most services looking more spread-out and less spiky.17:48
Spazmoticzuul is all better ap parently17:48
SpazmoticWas restarted and caught up17:48
SpazmoticWas it's zuul so all better is relative.. but yeah anyway17:48
melwittSpazmotic: ah, thanks. I see the status alert now in the backscroll17:49
*** sridharg has quit IRC17:49
Spazmoticnp melwitt.  johnthetubaguy if you can get a cahhance to review my notes on that commit today i'd appreciate it, but don't stress over it if not.  If you decide to +2 it i'll see if some of the other UK guys can take a look tomorrow to finish it off :)17:51
SpazmoticNight folks, have a good rest of your day17:51
*** sree has joined #openstack-nova17:51
*** yamamoto has joined #openstack-nova17:52
*** yangyapeng has joined #openstack-nova17:52
*** slaweq_ has joined #openstack-nova17:55
*** sree has quit IRC17:55
*** mvk has quit IRC17:56
*** yangyapeng has quit IRC17:56
cfriesenmriedem: when authenticating a token, is it possible for services to explicitly check whether a valid service token was attached?  (This is related to the "glance won't allow update of ceph image location during nova snapshot" issue.)17:58
*** slaweq_ has quit IRC17:59
*** JunOcataGuy is now known as penick18:00
*** derekh has quit IRC18:00
*** yamamoto has quit IRC18:01
*** ircuser-1 has joined #openstack-nova18:01
mriedemcfriesen: that sounds like a question for edmondsw or lbragstad18:01
*** sambetts is now known as sambetts|afk18:01
cfriesenmriedem: cool, will ping them18:02
edmondswcfriesen not sure I understood the question18:02
cfriesenedmondsw: there's an issue (https://bugs.launchpad.net/openstack-ansible/+bug/1639940) where with ceph-backed instances/images nova tries to make a new image and then update the location later18:03
openstackLaunchpad bug 1639940 in openstack-ansible "Snapshots of instances launched from images fails with Ceph as storage." [Medium,Incomplete] - Assigned to Logan V (loganv)18:03
cfriesenedmondsw: this used to work with glance v1, but with v2 it fails because glance doesn't allow updating the image location18:03
cfriesenedmondsw: we were wondering whether we could use service tokens to allow glance to determine that the request is coming from another openstack service rather than a "normal" user18:03
*** sree has joined #openstack-nova18:04
edmondswah, I see18:04
edmondswtoday, service tokens are only used re: expirations18:04
edmondswi.e., if the user token has expired, it'll still allow the operation if the service token isn't expired18:04
edmondswwe have talked about going beyond that, and actually checking policy/RBAC based on service token instead of user token, but that has not been implemented18:05
*** mgoddard_ has quit IRC18:07
*** slaweq has quit IRC18:07
cfriesendo the APIs exist to allow glance to extract/validate the user token separately?  or is that something that would need to be added in keystone?18:07
cfriesenbah, service token, not user token18:07
*** slaweq has joined #openstack-nova18:08
edmondswcfriesen looking18:08
melwittcfriesen: it still fails after setting 'show_multiple_locations = True' as mentioned in comment 7?18:08
cfriesenmelwitt: presumably it works, but there are big security warnings about not setting that to True18:08
*** sree has quit IRC18:09
mriedemcfriesen: this sounds very similar to a bug we have with glance v2 and shelve where the shelved snapshot image has a different set of project_id/user_id than the admin token that tries to get the image when unshelving,18:09
mriedemand i thought we could use the member stuff with glancev218:09
*** weshay|ruck is now known as weshay|ruck|brb18:09
cfriesenmelwitt: the current recommendation from the glance people was to have a whole separate glance node with a different config file just for nova to talk to it.18:09
mriedemhttps://bugs.launchpad.net/nova/+bug/167579118:09
openstackLaunchpad bug 1675791 in OpenStack Compute (nova) "Instance created by demo user(non-admin), shelved by admin and unshelved by demo user --> ends up in error state " [Medium,Triaged] - Assigned to Damini Chopra (damini)18:09
melwittcfriesen: yeah. from what I understand, the fast clone has the caveat of the security issues18:09
*** david-lyle has quit IRC18:09
*** yamahata has quit IRC18:10
melwittthat is, you have to be in an environment where exposure of the image location urls isn't a problematic in order to use COW clone18:11
mriedemerr in the case of shelve, the elevated admin context creates the snapshot, and when the user goes to unshelve the instance, it fails b/c the non-admin user doesn't have access to the image created for them18:11
*** ralonsoh_ has quit IRC18:12
*** tidwellr has quit IRC18:12
openstackgerritMatt Riedemann proposed openstack/nova master: Check for leaked server resource allocations in post_test_hook  https://review.openstack.org/53851018:12
mriedemgibi: cdent: ^ hark back to an old conversation about testing for allocation cleanups18:12
* cdent has a flash back18:13
mriedemdansmith: ^ we talked about that in denver i think18:15
*** rmcall has quit IRC18:17
*** Swami has joined #openstack-nova18:17
dansmithI believe you18:18
*** fragatina has joined #openstack-nova18:18
*** jpena is now known as jpena|off18:18
*** rmcall has joined #openstack-nova18:18
edmondswcfriesen looks like the context object should have info about the service_token if one was used18:18
edmondswthough I think you're probably treading on thin ice trying to use those in a way that they were not really intended to be used18:19
edmondswbetter run what you are thinking by lbragstad18:19
*** weshay|ruck|brb is now known as weshay18:20
*** weshay is now known as weshay|ruck18:20
*** slaweq has quit IRC18:23
*** slaweq has joined #openstack-nova18:23
*** felipemonteiro has joined #openstack-nova18:24
*** felipemonteiro_ has joined #openstack-nova18:25
*** cdent has quit IRC18:26
efriededleafe Be careful what you ask for.  See -dev ML.18:27
*** felipemonteiro has quit IRC18:29
*** efried is now known as efried_hexchat18:29
*** efried1 is now known as efried18:29
* efried is gonna try this Thunderbird client for a while...18:29
*** tidwellr has joined #openstack-nova18:31
lbragstadcfriesen: edmondsw summed it up pretty well, the service token work is kind of a long road.. it sounds like you want to use service tokens to validation/determine more than just a "yes, this token is valid" or "no, it isn't"?18:31
*** r-daneel_ has joined #openstack-nova18:33
*** r-daneel has quit IRC18:34
edleafeefried: thanks for that. So if I'm understanding things correctly, the "res.pool" is the root RP that placement would return18:35
*** mvk has joined #openstack-nova18:35
efriededleafe: Depends which model we're going with.18:35
efriededleafe: That would be model (C)18:36
*** burt has joined #openstack-nova18:37
*** r-daneel has joined #openstack-nova18:37
*** r-daneel_ has quit IRC18:38
edleafeefried: (C) makes the most sense to me, based on my limited familiarity18:39
efriededleafe: But it suffers from at least two drawbacks.18:39
edleafeefried: we don't want to fall into the trap of making everything fit the Nova model18:39
*** jose-phillips has quit IRC18:40
efriededleafe: What do you mean?  This *is* nova.18:40
efriededleafe: You mean the libvirt model?18:40
edleafeefried: yeah, like we tried to do with ironic18:41
edleafeefried: from a placement POV, all we care about are the things that the consumer wants us to track. For generic libvirt nova, that would be compute nodes. For vmware nova, it would be resource pools18:42
efriedDig.  So we should look toward closing those gaps.  In general, we should be working to make nova + placement + <virt> work smoothly, for all values of <virt>.18:44
edleafeyeah18:44
edleafePlacement should always be returning the thing that the consumer needs to proceed with a request18:45
*** mgoddard_ has joined #openstack-nova18:46
efriedI need to close the time box on this.  I'm going to make sure the PTG etherpad has an entry for this, and then get back to my regularly-scheduled programming.18:46
edleafeefried: cool. Thanks for writing up that email18:46
efriedyahyoubetcha18:46
*** jaosorior has quit IRC18:48
*** hemna_ has quit IRC18:52
*** yamahata has joined #openstack-nova18:53
*** yangyapeng has joined #openstack-nova18:54
*** gjayavelu has joined #openstack-nova18:56
*** yangyapeng has quit IRC18:58
mriedemjaypipes: melwitt: i'm going to undo the exception code handline refactor in https://review.openstack.org/#/c/538961/ - didn't mean to include that in this patch and it muddies the backpot19:00
mriedem*backport19:00
*** Tom-Tom has quit IRC19:00
melwittack19:01
*** slaweq_ has joined #openstack-nova19:01
openstackgerritSen Yang proposed openstack/python-novaclient master: Implement hypervisor hostname exact pattern match  https://review.openstack.org/52018719:04
*** slaweq_ has quit IRC19:05
*** tbtestaccount has joined #openstack-nova19:06
openstackgerritMatt Riedemann proposed openstack/nova master: Rollback instance.image_ref on failed rebuild  https://review.openstack.org/53896119:07
openstackgerritMatt Riedemann proposed openstack/nova master: Collapse duplicate error handling in rebuild_instance  https://review.openstack.org/53900119:07
*** lucasagomes is now known as lucas-afk19:08
*** rmcall has quit IRC19:08
*** AlexeyAbashkin has joined #openstack-nova19:11
jaypipesmriedem: +Wallaby'd19:11
mriedemthanks19:12
*** rmcall has joined #openstack-nova19:13
efriedjaypipes: Can we continue the discussion as to whether or not we should in fact be requiring update_provider_tree to return True/False?19:14
*** yangyapeng has joined #openstack-nova19:14
*** mgariepy has quit IRC19:15
*** tbtestaccount has quit IRC19:16
openstackgerritMatt Riedemann proposed openstack/nova stable/pike: Rollback instance.image_ref on failed rebuild  https://review.openstack.org/53900319:18
cfriesenlbragstad: just back from lunch.  yes, there's a scenario where we would like to answer the question "did this request come from another openstack service, not a 'normal' user".  was hoping to use service tokens for this.19:18
*** fragatina has quit IRC19:18
*** fragatina has joined #openstack-nova19:18
*** yangyapeng has quit IRC19:19
jaypipesefried: sure19:20
*** arvindn051 has quit IRC19:21
efriedjaypipes: So first off, it's trivial and inexpensive for report client to figure it out, so there's no real *need* for virt to tell us.19:21
efriedjaypipes: And after talking through a couple of potential impls from VMWare, it became clear that there's certainly the possibility that it would be awkward for the virt driver to figure it out.19:22
efriedjaypipes: For example, one viable implementation is to say, "I don't care what you gave me, I'm going to delete everything and build the ProviderTree as I know it from scratch"19:23
*** edmondsw has quit IRC19:23
lbragstadcfriesen: that kinda sounds like federation?19:23
openstackgerritmelanie witt proposed openstack/nova stable/pike: Stop globally caching host states in scheduler HostManager  https://review.openstack.org/53900519:23
*** mgariepy has joined #openstack-nova19:24
efriedjaypipes: Softer than that, it's IMO a source of extra unnecessary bugs to ask the virt driver to make sure they get that bool return correct.19:24
cfriesenlbragstad: not sure federation applies since it's all within the same cloud.  We just want glance to be able to special-case a request to change an image location if it comes from nova, but not if it comes from a regular user.19:25
ameedagibi: now its okay, can you please merge the bug ? or it need something else ?19:25
*** harlowja has joined #openstack-nova19:25
efriedjaypipes: Put another way: why have two chunks of code doing the same thing when one will do?19:25
jaypipesefried: ok19:26
jaypipesefried: I just thought it would make the RT's life easier if it could say "ok, no changes from virt driver... just move on"19:27
lbragstadcfriesen: oh - sorry, for some reason i was thinking of different services19:27
efriedjaypipes: Definitely could have worked out that way.19:27
*** david-lyle has joined #openstack-nova19:27
lbragstadcfriesen: that sounds like new territory for service tokens, the first thing we started working on with them was the whole long running operation issue.. it'd be good to sync with jamielennox though19:29
lbragstadcfriesen: he was one of the original people driving the effort, so i wouldn't be surprised if he's ventured down a couple different paths similar to what you're describing19:30
*** john51 has quit IRC19:30
*** tesseract has quit IRC19:31
*** john51 has joined #openstack-nova19:31
cfriesenlbragstad: move it over to the keystone channel?19:31
lbragstadcfriesen: sure19:31
*** yangyapeng has joined #openstack-nova19:35
openstackgerritMatt Riedemann proposed openstack/nova stable/ocata: Rollback instance.image_ref on failed rebuild  https://review.openstack.org/53900819:36
*** mgoddard_ has quit IRC19:39
*** yangyapeng has quit IRC19:40
*** tidwellr has quit IRC19:41
ameedais this error caused by me ? "http://logs.openstack.org/00/526900/26/check/openstack-tox-functional/c777a93/testr_results.html.gz"19:51
ameedafrom this gerrit "https://review.openstack.org/#/c/526900/"19:51
openstackgerritMatt Riedemann proposed openstack/nova master: Remove redundant call to add_instance_fault_from_exc in rebuild_instance  https://review.openstack.org/53901119:51
*** mriedem1 has joined #openstack-nova19:52
ameedajaypipes: please check this for me when you available https://review.openstack.org/#/c/526900/19:52
*** mriedem has quit IRC19:52
*** yangyapeng has joined #openstack-nova19:56
mriedem1ameeda: instance_system_metadata is a table where one row is a key/value pair for a single instance, and we can have a lot of sysmeta per instance, and a ton of instances,19:56
mriedem1in what world do we have a system metadata value that needs to be length TEXT?19:57
*** mriedem1 is now known as mriedem19:57
ameeda mriedem: so I did something wrong ?19:58
*** jose-phillips has joined #openstack-nova19:59
mriedemno, it's just, this is potentially a very large change in storage for that talbe19:59
mriedem*Table19:59
mriedemi see you're trying to match the nova table to glance https://github.com/openstack/glance/blob/master/glance/db/sqlalchemy/models.py#L15920:00
mriedemcorrect ^ ?20:00
*** yangyapeng has quit IRC20:00
mriedeman alternative solution would be to add an image_props column to the instance_extra table and just store the serialized image properties in there, rather than the instance_system_metadata table20:02
mriedembut then we could have n * TEXT entries in that json blob20:02
mriedemjaypipes: TEXT is not preallocated right?20:03
ameeda mriedem: I am new  on openstack , I just follow the bug to fix it, I need to merge this bug. I worked on it a lot as you see :(20:04
*** pramodrj07 has joined #openstack-nova20:04
jaypipesmriedem: correct.20:04
mriedemameeda: do you have a customer hitting htis?20:05
mriedem*this20:05
jaypipesameeda: reviewed.20:06
ameedaI am working at local company here, and the customer ask us to fix bugs in openstack. so I have to get points20:07
ameedajaypipes: Thank you20:07
*** slaweq_ has joined #openstack-nova20:08
mriedemameeda: hmm, well, there are probably less controversial bugs to fix :)20:08
mriedemif you're just looking for something to get into stackalytics20:08
*** Swami has quit IRC20:09
*** eharney has quit IRC20:09
mriedemreading the history on this bug, from lbragstad - probably due to some issue with storing powervc configuration strategy xml in image metadata back in 2013 - it sounds like the 255 length restriction was from when the image service was passing properties as http headers20:10
ameedamriedem: I still learn about nova and try to find medium bugs to fix . if my current opened bugs not merged , they will fire me :(20:10
mriedemameeda: sounds like a terrible employer20:10
ameedamriedem: yes it was sending by header and now sending on body, so the limitation is gone20:11
ameedamriedem: no comments ...20:11
openstackgerritmelanie witt proposed openstack/nova stable/ocata: Stop globally caching host states in scheduler HostManager  https://review.openstack.org/53901320:12
*** slaweq_ has quit IRC20:12
*** Swami has joined #openstack-nova20:15
*** yangyapeng has joined #openstack-nova20:16
*** tidwellr has joined #openstack-nova20:20
ameedamriedem: regarding to your last comment, is this something should I do ?20:21
*** yangyapeng has quit IRC20:21
mriedemameeda: up to you, it could be done in devstack if you use the nova fake virt driver ,and then just create 1000 instances20:22
mriedemthen apply your change and run the migration and see how long it takes20:22
*** eharney has joined #openstack-nova20:22
ameedasure that will take long time for large data, but what I should I do after what I have done until now :(20:23
*** AlexeyAbashkin has quit IRC20:25
*** jose-phillips has quit IRC20:25
*** amoralej is now known as amoralej|off20:26
openstackgerritAmeed Ashour proposed openstack/nova master: change instance_system_metadata column type  https://review.openstack.org/52690020:27
*** gszasz has quit IRC20:28
ameedajaypipes: I uploaded the patch set20:28
*** edmondsw has joined #openstack-nova20:30
*** Swami has quit IRC20:31
*** edmondsw has quit IRC20:32
*** edmondsw_ has joined #openstack-nova20:32
ameedajaypipes mriedem, kindly, can you please review those also https://review.openstack.org/#/c/528069/ and https://review.openstack.org/#/c/528385/20:34
ameedaand please let me know what do you think about this bug "https://bugs.launchpad.net/nova/+bug/1737708"20:35
openstackLaunchpad bug 1737708 in OpenStack Compute (nova) "create instance failed when the userdata size is larger than 64k" [Undecided,New] - Assigned to Deepak Mourya (mourya007)20:35
*** namnh has joined #openstack-nova20:35
ameedasorry for inconvenience, Thank you for your time20:36
*** yangyapeng has joined #openstack-nova20:37
*** jose-phillips has joined #openstack-nova20:38
mriedemameeda: melwitt has been working on a duplicate of one of those for a long time https://review.openstack.org/#/c/340614/20:39
*** READ10 has quit IRC20:40
melwittyeah, took many iterations to get it right back when the earlier versions caused gate failures in the postgres job. looks like it needs another rebase20:41
*** yangyapeng has quit IRC20:41
*** namnh has quit IRC20:41
melwittwe still have customers that need a fix for it20:43
ameedamriedem: yes, but my bug scenario doesn't hit _local_delete, so we have to cover all the cases, right ?20:43
mriedemmelwitt's patch is fixing a local delete case20:44
mriedemwhere the instance isn't on a compute host,20:44
mriedemso it is either shelved offloaded or failed during scheduling20:44
melwittit is on a compute host, it's just in ERROR state20:44
mriedem'local delete' == delete from the API, not compute20:44
melwittthere's code in compute manager that sets host = None while setting to ERROR state if something fails. IIRC20:45
*** tssurya_ has joined #openstack-nova20:45
melwittlike this https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L1941-L194320:46
ameedaI am not sure about the case , but what about this fix https://review.openstack.org/#/c/528385/20:48
ameedathis detach volume when instance creation fails20:49
*** jose-phillips has quit IRC20:50
mriedemameeda: -1 on that one too20:51
mriedemameeda: we already attempt to detach volumes when deleting a server20:51
mriedemso if that's failing, i don't think your patch is going to fix it20:51
ameedawhat is the case !, I just follow the bugs to fix them , after that I found that the bug is invalid ?20:53
*** Swami has joined #openstack-nova20:53
mriedemameeda: well, you could be trying to fix a very old bug that's already been fixed20:54
mriedemor the recreate scenario from the bug is not clear20:54
mriedemso the thing to do here, is probably go through the recreate steps in the bug (which are pretty clear) and see if you can reproduce it20:55
mriedemand if so, see where things are failing20:55
mriedemthe bug report was written over a year ago and doesn't say which version of nova they were using when they hit this,20:56
mriedemso it might be fixed20:56
mriedemi'm sorry that you invested time in a patch, but we need to make sure it's still a valid bug first20:56
ameedamriedem: but I reproduce the bug and fix it , then test it again to make sure that I fix the issue, and there are reviewers ask me to make changes on it :(20:56
ameedaI am sure that the bug is still valid , I reproduce it20:57
mriedemok, so then why is the original detach failing in _shutdown_instance?20:58
mriedembecause that's what should be detaching the volume20:58
*** yangyapeng has joined #openstack-nova21:01
melwittmriedem: I think it's the same bug I'm fixing. I think he means volume quota was exceeded (it's checked in compute). compute catches the exceptions, nulls out the instance.host, then sets it to ERROR state21:02
melwittthen when you go to delete the instance, because compute nulled out the host, the compute api thinks there's no resources to free up because it assumes instance.host = None means failed to schedule21:03
melwittso I think my patch will take care of it. I'm rebasing it now and rewriting the commit message to be clearer21:03
ameedamy case when vm creations fails when there are no enough quota for volumes. as this https://review.openstack.org/#/c/528069/ scenario.21:03
melwittI know, that's what I just said21:03
ameedamelwitt: you fix solve the issue when there is no hosts, my fix solve the issue in another case !21:05
ameedamriedem: what do you think ?21:05
*** yangyapeng has quit IRC21:05
melwittit's not another case. compute will set instance.host = None because of the volume quota exceeded21:05
*** Sukhdev_ has joined #openstack-nova21:07
ameedaok great !!21:07
ameedaduplicated bugs , and my work and time have gone in vain21:08
*** liverpooler has quit IRC21:10
*** mvenesio has quit IRC21:11
*** mvenesio has joined #openstack-nova21:12
*** mvenesio has quit IRC21:16
*** Supun has quit IRC21:18
*** yangyapeng has joined #openstack-nova21:22
*** slaweq_ has joined #openstack-nova21:22
*** yangyapeng has quit IRC21:26
*** slaweq_ has quit IRC21:27
efriedmriedem: Any tips for how I can check in nova.tests.functional.test_servers that a particular exception got raised up from _update() ?21:29
*** READ10 has joined #openstack-nova21:29
efriedSo far my mechanism for getting _update() to run is self._run_periodics()21:30
*** r-daneel has quit IRC21:33
*** r-daneel has joined #openstack-nova21:33
*** vivsoni has quit IRC21:36
*** vivsoni has joined #openstack-nova21:36
melwittefried: I think that's the usual way to run it21:37
efriedmelwitt: I think I'm going to have to deconstruct it a bit and run rt.update_available_resource directly.21:38
*** cleong has quit IRC21:38
melwittefried: any reason you're trying to verify that in a func test instead of a unit test?21:38
efriedmelwitt: A reasonable question.21:39
melwittif there's no way to detect what you expect from the instance or other things you can inspect in the func test21:39
efriedmelwitt: I was hoping to avoid unit test altogether.21:39
melwittso there's an existing func test and you want to add an assertion to it?21:39
efriedmelwitt: I'm writing a new func suite.  Stand by, I'll put up what I've got.21:40
*** eharney has quit IRC21:43
openstackgerritEric Fried proposed openstack/nova master: New-style _set_inventory_for_provider  https://review.openstack.org/53764821:43
openstackgerritEric Fried proposed openstack/nova master: SchedulerReportClient.update_from_provider_tree  https://review.openstack.org/53382121:43
openstackgerritEric Fried proposed openstack/nova master: WIP: Use update_provider_tree from resource tracker  https://review.openstack.org/52024621:43
openstackgerritEric Fried proposed openstack/nova master: Fix nits in update_provider_tree series  https://review.openstack.org/53126021:43
openstackgerritEric Fried proposed openstack/nova master: Move refresh time from report client to prov tree  https://review.openstack.org/53551721:43
*** takashin has joined #openstack-nova21:43
efriedmelwitt: Right here is where I want to make sure that exception happened: https://review.openstack.org/#/c/520246/41/nova/tests/functional/test_servers.py@161521:44
efriedmelwitt: And similar for other kinds of error conditions.21:44
efriedmelwitt: I mean, I'm at least proving the whole thing doesn't blow up when I inject error conditions, which is good.21:44
*** moshele has joined #openstack-nova21:47
melwittI see. I suppose you could monkey patch _update (or whatever) to call the real _update inside self.assertRaises. I wonder if that would work21:49
efriedmelwitt: Well, I don't see _run_periodicals really doing anything that adds value to my narrow little test case.21:51
melwittso you don't want to assert a particular exception is raised? I'm confused :)21:52
efriedI do, and the only reason I can't do assertRaises(self._run_periodicals) is because _run_periodicals invokes x, which invokes y, which invokes z, which swallows exceptions.21:53
efriedSo I'm going to dig in and invoke z directly, so I can assertRaises(z)21:53
efried...which I just did, and it seems to work a treat!  melwitt thanks for sounding boarding :)21:53
efriedNow everyone will want to do what I just did21:54
melwittyeah, that's what I was trying to say, monkey patch the method that will raise it and just call the real method inside self.assertRaises21:54
efriedThe monkey patching isn't needed21:56
melwittoh, so run that instead of periodics21:56
melwittI see21:56
efriedjust so.21:56
efriedJust needed a few extra LOC to dig into the call stack a couple more levels.21:57
*** burt has quit IRC22:04
*** threestrands has joined #openstack-nova22:05
*** threestrands has quit IRC22:05
*** threestrands has joined #openstack-nova22:05
*** threestrands_ has joined #openstack-nova22:07
*** threestrands has quit IRC22:08
*** threestrands_ has quit IRC22:08
*** threestrands has joined #openstack-nova22:08
openstackgerritJay Pipes proposed openstack/nova master: tests for alloc candidates with nested and traits  https://review.openstack.org/53189922:09
openstackgerritJay Pipes proposed openstack/nova master: add test for scenario with sum of child resources  https://review.openstack.org/53433922:09
openstackgerritJay Pipes proposed openstack/nova master: _get_trees_matching_all_resources() sum children  https://review.openstack.org/53486622:09
openstackgerritJay Pipes proposed openstack/nova master: add _get_usages_from_trees() function  https://review.openstack.org/53496722:09
openstackgerritJay Pipes proposed openstack/nova master: validate provider summary structure  https://review.openstack.org/53651622:09
openstackgerritJay Pipes proposed openstack/nova master: WIP - populate alloc cands for trees  https://review.openstack.org/53496822:09
*** dtruong has quit IRC22:13
*** threestrands_ has joined #openstack-nova22:21
*** jaypipes has quit IRC22:21
*** felipemonteiro_ has quit IRC22:22
*** tidwellr has quit IRC22:23
*** threestrands has quit IRC22:23
*** tidwellr has joined #openstack-nova22:24
*** edmondsw_ is now known as edmondsw22:26
openstackgerritMatt Riedemann proposed openstack/nova master: reno for notification-transformation-queens  https://review.openstack.org/51801822:26
*** tssurya_ has quit IRC22:27
*** tidwellr has quit IRC22:29
mriedemdansmith: want to hit this pike backport? https://review.openstack.org/#/c/536981/22:30
mgagnewhat's the use case for aggregates in Placement API?22:30
*** dave-mccowan has quit IRC22:31
*** rmcall has quit IRC22:31
mriedemmgagne: the primary one is modeling things where one provider shares a resource with another, like a shared storage pool22:32
mgagnemriedem: thanks for the clarification, I tried to read/understand https://developer.openstack.org/api-ref/placement/#resource-provider-aggregates22:33
mgagneand I'm not sure the doc fully explain its purpose, I would have never guess what you said from the doc, it mainly explains how it's not nova aggregates22:34
mriedemmgagne: is the spec that talks about aggregates the most i think https://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/generic-resource-pools.html22:34
mriedemmgagne: heh yeah that's what i was thinking22:34
mgagnehow is Generic Resource Pools == aggregates? =)22:34
*** namnh has joined #openstack-nova22:35
*** jappleii__ has joined #openstack-nova22:35
mgagnewill read and see if I can get more answers22:35
*** jappleii__ has quit IRC22:36
*** jappleii__ has joined #openstack-nova22:37
mgagnethanks for the link btw ;)22:37
*** threestrands_ has quit IRC22:37
*** namnh has quit IRC22:40
openstackgerritMatt Riedemann proposed openstack/nova master: api-ref: provide more detail on what a provider aggregate is  https://review.openstack.org/53903322:41
mriedemmgagne: see if ^ helps wording-wise22:41
*** jose-phillips has joined #openstack-nova22:41
mriedemsorry about ending on a preposition22:41
*** mylu has joined #openstack-nova22:42
mriedemmaybe it's not, me fail english22:42
mgagnemriedem: I think it's enough to give a hint that aggregates do have a purpose other than not being nova aggregates =)22:42
mgagneI'm still trying to digest the spec you linked above.22:43
mgagnewould it be ok to update past spec to reflect current implement? Ex.: openstack resource-provider is now openstack resource provider22:45
*** mylu has quit IRC22:46
*** rcernin has joined #openstack-nova22:46
*** mylu has joined #openstack-nova22:46
*** liangy has quit IRC22:49
*** mylu has quit IRC22:50
mriedemmgagne: if it's not too invasive, then that's probably fine22:52
mriedemespecially for CLI examples22:52
openstackgerritMathieu Gagné proposed openstack/nova-specs master: Update references to OSC resource provider command  https://review.openstack.org/53903822:55
*** liangy has joined #openstack-nova22:56
*** liverpooler has joined #openstack-nova22:59
efriedmgagne mriedem Sharing providers aren't the only use case FWIW.23:00
*** slaweq_ has joined #openstack-nova23:00
mriedemefried: i'm not up to date on the new aggregate hotness23:00
*** moshele has quit IRC23:00
mriedembut yes i know sean-k-mooney has a thing23:00
mgagneefried: please let me know if there is a doc I can read =)23:00
mriedemmgagne: left some comments in there23:00
mriedemmgagne: that spec was written in i think mitaka or newton, so the cli stuff was all future ideas23:01
efriedmgagne: Not really a single doc, no.  But as an example, see this ML thread...23:01
mgagnemriedem: and now I find that aggregates ARE nova aggregates but not totally :O23:01
mgagnemriedem: yea found the Other end user impact section23:01
efriedmgagne: http://lists.openstack.org/pipermail/openstack-dev/2018-January/126685.html23:01
mriedemit might be easier to just add a note that any CLIs are subject to change and the definitive CLI guide is in the osc-placement docs <link>23:01
mgagneefried: ok, I'm a n00b when it comes to placement, I'm trying to catch up very fast so I can answer to jaypipes but it isn't easy to find all the relevant info23:02
efriedmgagne: Specifically (6) and its subsequent references in the models23:02
efriedmgagne: Answer what from jaypipes?23:02
mgagnemriedem: if there is no doc, I read specs, they often contain more info although some bit might be outdated.23:02
mgagneefried: http://lists.openstack.org/pipermail/openstack-dev/2018-January/126283.html23:03
efriedmgagne: Yeah, had a feeling it was that :)23:03
*** slaweq_ has quit IRC23:04
*** awaugama has quit IRC23:04
*** dtruong has joined #openstack-nova23:04
*** awaugama_ has joined #openstack-nova23:04
mgagneefried: so English is not my first language and I often have a hard time to grasp new concepts without visual aids. But once I understand, it's all fine =)23:05
efriedJe pourrais t'aider en français si tu veux, mais je crois que la langue n'est pas la problème :)23:05
efriedSauf, la langue naturelle...23:06
*** edmondsw has quit IRC23:06
mgagnehehe, c'est quoi l'affaire de placement :O ;)23:06
efriedSeulement pour enregistrer les resources, rien d'autre23:07
efried(pas vraiement)23:07
*** weshay|ruck is now known as weshay|ruck|afk23:07
*** yangyapeng has joined #openstack-nova23:07
mgagneyea, I got the idea. just trying to understand all the fine prints23:07
*** liangy has quit IRC23:08
*** salv-orlando has quit IRC23:08
efriedDefinitely.  I admit I haven't kept thoroughly updated with that particular ML thread, but if you have a couple of minutes to hang about while I read it, I may be able to answer your questions more easily.23:08
mriedemmaciejjozefczyk_: looks like your change https://review.openstack.org/#/c/529236/23:08
*** salv-orlando has joined #openstack-nova23:09
efriedThe problem I have (and the reason I wasn't following to closely) is that I don't really know about this Filter business, or what compute aggregates are/do (just that they aren't placement aggregates).23:09
efrieds/to/too/23:09
mgagneefried: I'm trying to finish my email now. I do have some questions but tbh, it's mostly missing bits so one could transition from an aggregate based solutions to placement23:09
*** claudiub|3 has quit IRC23:10
*** namnh has joined #openstack-nova23:11
efriedmgagne: Are you trying to make an existing deployment work on a particular version of openstack?23:11
*** yangyapeng has quit IRC23:12
mgagneefried: yes, you guessed right. in fact, it has been my job for the last year, upgrading, discovering major changes, cursing and adapting =)23:13
*** salv-orlando has quit IRC23:13
efriedmgagne: Okay, which version of openstack?23:13
mgagneefried: We are running Mitaka, trying to move to Newton (currently on pause due to our friends meltdown and spectre)23:15
*** namnh has quit IRC23:15
mgagneefried: but I'm still monitoring ML and now I'm answering the email because I discovered the mentioned change that would break/change our current flow/ways of doing thing.23:15
efriedOh, okay, wow.  And Jay is talking about implementing these hacks all the way back to Newton?  (which we're trying to EOL afaik)23:16
mgagneefried: so I'm not ready for Ocata yet but I know I will have to cross that river someday23:16
mgagneefried: no ^23:16
*** yangyapeng has joined #openstack-nova23:16
*** Sukhdev_ has quit IRC23:16
mgagneefried: but the challenge is that once I'm ready to cross that river, it will be too late to complain about changes in Ocata I wasn't aware about. I'm playing catch up here.23:17
*** felipemonteiro_ has joined #openstack-nova23:18
mgagneefried: I don't know if you understand in what kind of boat I'm in.23:18
efriedmgagne: Well, I think the first thing that'll help you is to get placement aggregates out of your head.  They're not related to host aggregates, and they're not fully implemented in Newton (or Ocata, or Pike, or Queens).23:18
*** namnh has joined #openstack-nova23:19
efriedIt sounds to me like all you need is a way to customize allocation ratios.  Which can be done via placement calls, as long as there's *some* switch to turn off the automatic setting from the conf, as Jay suggests.23:19
mgagneefried: ok, I found that it's not the answer to my problem. But I still need to educate myself on the concept23:19
*** bnemec has quit IRC23:20
*** mlavalle has quit IRC23:20
mgagneefried: yes, that's the conclusion I ended up with too23:20
*** bnemec has joined #openstack-nova23:20
efriedmgagne: Has anyone proposed a patch that would do that yet?23:20
*** READ10 has quit IRC23:20
mgagnenot that I'm aware of23:20
*** edmondsw has joined #openstack-nova23:20
*** yangyapeng has quit IRC23:21
mriedemefried: this? https://review.openstack.org/#/c/532924/23:22
efriedmriedem: Certainly looks related, at a glance.23:23
*** namnh has quit IRC23:23
*** namnh has joined #openstack-nova23:24
efriedmgagne: Have you tried patching ^ in?23:25
mgagneefried: I'm not running master23:26
efriedmgagne: Yeah, I get that, I'm asking if you've tried patching that into your running environment to see if it resolves the issue.23:27
efriedor rather, allows you to resolve it via conf.23:27
mgagneI'm not sure I understand what you are asking23:27
*** yangyapeng has joined #openstack-nova23:29
*** stakeda has joined #openstack-nova23:30
efriedmgagne: IIUC, the point of that patch will be to backport it to where you can use it (which I guess would be Newton?  Though again, I thought we were EOLing that guy)23:31
*** awaugama_ has quit IRC23:31
efriedmgagne: So I'm suggesting you could do that backport locally and see if it works for you.23:31
mgagneI'm really confused. what's "it" ? =)23:31
efriedThough I suppose things have probably changed quite a bit in those areas, so the backport may not be trivial.23:32
mgagnethe bug is very technical and I don't fully understand the problem and proposed solution23:32
efriedSorry, the patch mriedem mentioned above - https://review.openstack.org/#/c/532924/23:32
efriedThe proposed solution would allow you to set your allocation ratios via conf, end of story.23:32
efriedNothing else would change; in particular, you would continue to be able to use your filtery thingies as you did before.23:33
mriedemefried: we don't backport config option default changes23:33
efriedoh23:33
*** yangyapeng has quit IRC23:33
mriedemsince, you know, changing defaults on people in stable is kind of mean23:34
efriedwhat about the rest of that patch?23:34
efriedyeah, makes sense when you put it like that.23:34
mriedem:)23:34
mriedemi haven't looked at the rest of the patch in a few weeks23:34
mgagneefried: what's via conf for you? Isn't already the case where you can provide allocation ratio on compute node in nova.conf? I'm totally lost23:34
mriedemand i don't think i have the brain power to do so right now23:34
efriedmgagne: Yeah, you're right.  And I'm probably just confusing the issue even more.  I should stop.23:35
mgagneefried: my issue is I'm being told to stop using aggregates (and allocation ratio in metadata) because they are broken.23:35
mgagneefried: and to use nova.conf itself on compute node because "Config management is the solution to your problem"23:36
efriedI can understand where that's a problem.23:36
mgagneefried: that's not what I want, this is not my flow, far from it.23:37
*** namnh has quit IRC23:38
mgagneefried: so that's basically it. Something I could do through an API now needs to be done through our config system and the person performing this task might not have access to our config system.23:38
mgagneand you lose "agility" in your operations23:39
*** namnh has joined #openstack-nova23:42
*** ekhugen- has joined #openstack-nova23:44
mgagnetime to leave for me, thanks for the talk ;)23:44
*** mhenkel_ has joined #openstack-nova23:45
*** NightKhaos has quit IRC23:45
*** mhenkel has quit IRC23:45
*** ekhugen_alt has quit IRC23:45
*** raorn has quit IRC23:45
*** logan- has quit IRC23:45
*** Oku_OS-away has quit IRC23:45
*** StevenK has quit IRC23:45
*** jlvillal has quit IRC23:45
*** fnordahl has quit IRC23:45
*** jistr has quit IRC23:45
*** dtantsur|afk has quit IRC23:45
*** r-daneel has quit IRC23:45
*** edmondsw has quit IRC23:46
*** edmondsw has joined #openstack-nova23:47
*** mgoddard has quit IRC23:48
*** yangyapeng has joined #openstack-nova23:49
*** NightKhaos has joined #openstack-nova23:51
*** raorn has joined #openstack-nova23:51
*** logan- has joined #openstack-nova23:51
*** Oku_OS-away has joined #openstack-nova23:51
*** StevenK has joined #openstack-nova23:51
*** jlvillal has joined #openstack-nova23:51
*** fnordahl has joined #openstack-nova23:51
*** jistr has joined #openstack-nova23:51
*** dtantsur|afk has joined #openstack-nova23:51
*** mylu has joined #openstack-nova23:51
*** edmondsw has quit IRC23:51
*** dave-mccowan has joined #openstack-nova23:53
*** yangyapeng has quit IRC23:53
openstackgerritEric Fried proposed openstack/nova master: Use update_provider_tree from resource tracker  https://review.openstack.org/52024623:54
openstackgerritEric Fried proposed openstack/nova master: Fix nits in update_provider_tree series  https://review.openstack.org/53126023:54
openstackgerritEric Fried proposed openstack/nova master: Move refresh time from report client to prov tree  https://review.openstack.org/53551723:54
openstackgerritHongbin Lu proposed openstack/nova master: Handle IpAddressAlreadyAllocated exception  https://review.openstack.org/53553223:55
openstackgerritHongbin Lu proposed openstack/nova master: Use revision_number on adding/removing security group  https://review.openstack.org/53551023:56
*** mgoddard has joined #openstack-nova23:56
*** sapd_ has quit IRC23:57
*** hongbin has quit IRC23:57
*** _pewp_ has quit IRC23:58
*** namnh has quit IRC23:58
*** namnh has joined #openstack-nova23:59

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