Friday, 2018-05-04

*** kotra03_krk has joined #openstack-nova00:01
*** gyee has quit IRC00:02
*** markvoelker has quit IRC00:05
*** jistr has quit IRC00:07
*** hamzy has joined #openstack-nova00:09
*** jistr has joined #openstack-nova00:13
*** zhuli_ has joined #openstack-nova00:15
*** Nel1x has joined #openstack-nova00:17
*** fragatina has quit IRC00:18
*** liverpooler has joined #openstack-nova00:20
*** tbachman has joined #openstack-nova00:29
*** gouthamr has quit IRC00:30
*** hoangcx has joined #openstack-nova00:33
*** mingyu_ has joined #openstack-nova00:34
*** mingyu has quit IRC00:35
*** gouthamr has joined #openstack-nova00:38
*** suresh12 has joined #openstack-nova00:47
*** liverpooler has quit IRC00:52
*** edmondsw has joined #openstack-nova00:53
openstackgerritTetsuro Nakamura proposed openstack/nova master: Add tests for alloc_cands with member_of  https://review.openstack.org/56139900:54
openstackgerritTetsuro Nakamura proposed openstack/nova master: Fix member_of with sharing providers  https://review.openstack.org/56140000:54
openstackgerritTetsuro Nakamura proposed openstack/nova master: Expand member_of functional test cases  https://review.openstack.org/56601100:54
*** damien_r has joined #openstack-nova00:55
*** phuongnh has joined #openstack-nova00:58
*** gouthamr has quit IRC00:58
*** damien_r has quit IRC01:00
mrjazzerciseidlemind: you've got 2 cell1s, so probably drop the one with the wrong URL01:05
*** edmondsw has quit IRC01:05
mrjazzerciseand update the cell0 one using nova-manage cell_v2 update_cell01:05
*** markvoelker has joined #openstack-nova01:05
mrjazzercisesome services cache the cells so you'll have to restart some services, check the man page on update_cell01:06
mrjazzercisenova-api, nova-conductor and nova-scheduler i think01:06
*** tiendc has joined #openstack-nova01:12
*** spsurya has joined #openstack-nova01:14
*** dpawlik has joined #openstack-nova01:15
*** annp has joined #openstack-nova01:16
*** fragatina has joined #openstack-nova01:17
*** edmondsw has joined #openstack-nova01:18
*** dpawlik has quit IRC01:20
*** gjayavelu has quit IRC01:21
*** zhuli_ is now known as zhuli01:21
*** fragatina has quit IRC01:21
*** fragatina has joined #openstack-nova01:22
*** gouthamr has joined #openstack-nova01:23
*** fragatina has quit IRC01:26
*** suresh12 has quit IRC01:30
*** yamahata has quit IRC01:30
*** gouthamr has quit IRC01:32
*** fragatina has joined #openstack-nova01:35
*** mrjazzercise has quit IRC01:36
*** gaoyan has joined #openstack-nova01:37
*** gaoyan has quit IRC01:37
*** markvoelker has quit IRC01:40
*** Tom-Tom has joined #openstack-nova01:44
*** kotra03_krk has quit IRC01:46
*** fragatina has quit IRC01:46
*** fragatina has joined #openstack-nova01:47
*** hongbin has joined #openstack-nova01:51
*** kotra03_krk has joined #openstack-nova01:53
*** gouthamr has joined #openstack-nova01:56
*** zhaochao has joined #openstack-nova01:59
*** LiveOne_ has joined #openstack-nova02:00
*** r-daneel has quit IRC02:06
*** suresh12 has joined #openstack-nova02:08
idlemindmrjazzercise thx02:09
*** suresh12 has quit IRC02:12
*** armaan has joined #openstack-nova02:13
*** armaan has quit IRC02:14
*** hongbin has quit IRC02:17
*** edmondsw has quit IRC02:18
*** lei-zh has joined #openstack-nova02:18
*** rcernin has quit IRC02:19
*** lei-zh has quit IRC02:20
*** rcernin has joined #openstack-nova02:20
*** lei-zh has joined #openstack-nova02:20
*** gouthamr has quit IRC02:22
*** mingyu_ has quit IRC02:22
*** mingyu has joined #openstack-nova02:22
*** gouthamr has joined #openstack-nova02:23
*** fragatina has quit IRC02:26
*** fragatina has joined #openstack-nova02:26
*** gouthamr has quit IRC02:27
*** gouthamr has joined #openstack-nova02:32
*** markvoelker has joined #openstack-nova02:37
*** gouthamr has quit IRC02:37
*** hongbin has joined #openstack-nova02:37
*** germs has quit IRC02:39
*** gjayavelu has joined #openstack-nova02:39
*** germs has joined #openstack-nova02:40
*** psachin has joined #openstack-nova02:41
*** esberglu has quit IRC02:47
*** yamamoto has quit IRC02:51
*** yamamoto has joined #openstack-nova02:51
*** gjayavelu has quit IRC02:51
*** kotra03_krk has quit IRC02:54
*** gjayavelu has joined #openstack-nova02:55
*** damien_r has joined #openstack-nova02:55
*** yamamoto has quit IRC02:58
*** damien_r has quit IRC03:00
*** Nel1x has quit IRC03:09
*** gjayavelu has quit IRC03:10
*** markvoelker has quit IRC03:10
*** dave-mccowan has quit IRC03:14
*** dpawlik has joined #openstack-nova03:16
*** dpawlik has quit IRC03:21
*** Tom-Tom has quit IRC03:26
*** fragatina has quit IRC03:29
*** Tom-Tom has joined #openstack-nova03:29
*** fragatina has joined #openstack-nova03:29
*** andreas_s has joined #openstack-nova03:30
*** andreas_s has quit IRC03:34
*** fragatina has quit IRC03:35
*** lei-zh has quit IRC03:36
*** felipemonteiro__ has joined #openstack-nova03:36
*** gjayavelu has joined #openstack-nova03:38
*** gouthamr has joined #openstack-nova03:38
*** felipemonteiro_ has joined #openstack-nova03:39
*** lpetrut has joined #openstack-nova03:41
*** felipemonteiro__ has quit IRC03:43
*** nicolasbock has quit IRC03:44
*** felipemonteiro_ has quit IRC03:45
*** mingyu has quit IRC03:46
*** kotra03_2 has joined #openstack-nova03:46
*** mingyu has joined #openstack-nova03:48
*** gjayavelu has quit IRC03:52
*** gouthamr has quit IRC03:52
*** gjayavelu has joined #openstack-nova03:53
*** yamamoto has joined #openstack-nova03:59
*** rcernin has quit IRC03:59
*** rcernin has joined #openstack-nova04:00
*** edmondsw has joined #openstack-nova04:00
*** germs has quit IRC04:02
*** hongbin has quit IRC04:02
*** germs has joined #openstack-nova04:02
*** germs has quit IRC04:02
*** germs has joined #openstack-nova04:02
*** gyankum has joined #openstack-nova04:04
*** edmondsw has quit IRC04:05
*** yamamoto has quit IRC04:06
*** markvoelker has joined #openstack-nova04:08
*** r-daneel has joined #openstack-nova04:10
*** slaweq has joined #openstack-nova04:11
*** suresh12 has joined #openstack-nova04:11
*** Tom-Tom_ has joined #openstack-nova04:12
*** slaweq has quit IRC04:15
*** Tom-Tom has quit IRC04:15
*** janki has joined #openstack-nova04:15
*** Tom-Tom has joined #openstack-nova04:16
*** Tom-Tom_ has quit IRC04:16
*** kotra03_2 has quit IRC04:19
*** lpetrut has quit IRC04:21
*** Tom-Tom has quit IRC04:23
*** lpetrut has joined #openstack-nova04:25
openstackgerritjichenjc proposed openstack/nova master: WIP:[doc]Move configuration to admin subfolder  https://review.openstack.org/56621204:31
*** fragatina has joined #openstack-nova04:32
*** r-daneel_ has joined #openstack-nova04:35
*** r-daneel has quit IRC04:36
*** r-daneel_ is now known as r-daneel04:36
*** gouthamr has joined #openstack-nova04:40
*** markvoelker has quit IRC04:41
*** jaosorior has joined #openstack-nova04:42
*** bhagyashris has quit IRC04:43
*** bhagyashris has joined #openstack-nova04:43
*** lpetrut has quit IRC04:44
*** moshele has joined #openstack-nova04:45
*** gouthamr has quit IRC04:49
*** abhishekk has joined #openstack-nova04:49
*** gouthamr has joined #openstack-nova04:50
*** damien_r has joined #openstack-nova04:54
*** gouthamr has quit IRC04:56
*** damien_r has quit IRC04:58
*** gjayavelu has quit IRC05:01
*** ianw has quit IRC05:06
*** krtaylor has quit IRC05:09
*** NobodyCam has quit IRC05:15
*** cz2 has quit IRC05:15
*** patrickeast has quit IRC05:15
*** sdake has quit IRC05:15
*** TheJulia has quit IRC05:15
*** pas-ha has quit IRC05:15
*** hogepodge has quit IRC05:15
*** vdrok has quit IRC05:15
*** udesale has joined #openstack-nova05:15
*** sdake has joined #openstack-nova05:15
*** sdake has quit IRC05:15
*** sdake has joined #openstack-nova05:15
*** TheJulia has joined #openstack-nova05:15
*** hogepodge has joined #openstack-nova05:16
*** vdrok has joined #openstack-nova05:16
*** pas-ha has joined #openstack-nova05:16
*** NobodyCam has joined #openstack-nova05:16
*** cz2 has joined #openstack-nova05:16
*** dpawlik has joined #openstack-nova05:17
*** suresh12 has quit IRC05:20
*** dpawlik has quit IRC05:21
*** lpetrut has joined #openstack-nova05:22
*** moshele has quit IRC05:23
*** lpetrut has quit IRC05:29
*** suresh12 has joined #openstack-nova05:30
*** suresh12 has quit IRC05:34
*** Gorian has quit IRC05:34
*** markvoelker has joined #openstack-nova05:38
*** Gorian has joined #openstack-nova05:42
openstackgerritjichenjc proposed openstack/nova master: [doc]Move configuration to admin subfolder  https://review.openstack.org/56621205:43
*** Tom-Tom has joined #openstack-nova05:44
*** nsingh has joined #openstack-nova05:45
nsinghany command or way to confirm which services running on compute nodes???05:45
*** threestrands has quit IRC05:47
*** ratailor has joined #openstack-nova05:47
*** slaweq has joined #openstack-nova05:47
*** slaweq has quit IRC05:52
*** ianw has joined #openstack-nova05:55
*** sridharg has joined #openstack-nova05:58
*** hemna_ has quit IRC06:07
*** damien_r has joined #openstack-nova06:10
*** markvoelker has quit IRC06:11
*** evin has joined #openstack-nova06:12
*** trungnv has quit IRC06:20
*** damien_r has quit IRC06:20
*** lpetrut has joined #openstack-nova06:28
*** do3meli has joined #openstack-nova06:42
*** pcaruana has joined #openstack-nova06:43
*** do3meli has left #openstack-nova06:43
openstackgerritzhangyangyang proposed openstack/nova master: Remove the function get_back_port()  https://review.openstack.org/56621906:48
*** r-daneel has quit IRC06:49
*** krtaylor has joined #openstack-nova06:50
*** damien_r has joined #openstack-nova06:50
*** alex_xu has quit IRC06:50
*** alex_xu has joined #openstack-nova06:51
*** damien_r has quit IRC06:55
*** damien_r has joined #openstack-nova06:55
*** rcernin has quit IRC07:05
*** slaweq has joined #openstack-nova07:05
*** slaweq has quit IRC07:06
*** slaweq has joined #openstack-nova07:06
*** markvoelker has joined #openstack-nova07:08
*** sahid has joined #openstack-nova07:09
*** dpawlik has joined #openstack-nova07:10
*** dpawlik has quit IRC07:16
*** brault has joined #openstack-nova07:18
*** dpawlik has joined #openstack-nova07:19
*** tesseract has joined #openstack-nova07:20
*** andreas_s has joined #openstack-nova07:25
*** jaosorior has quit IRC07:25
*** alexchadin has joined #openstack-nova07:32
*** amoralej|off is now known as amoralej07:34
*** wolverineav has joined #openstack-nova07:34
*** edmondsw has joined #openstack-nova07:36
bauzasgood morning Nova07:37
openstackgerritKashyap Chamarthy proposed openstack/nova stable/ocata: libvirt: Make `cpu_model_extra_flags` case-insensitive for real  https://review.openstack.org/56567207:37
bauzaslet me put a Friday swag07:37
*** bauzas is now known as bauwser07:37
*** edmondsw has quit IRC07:41
*** markvoelker has quit IRC07:42
*** slunkad has quit IRC07:45
*** kukacz has quit IRC07:46
*** jpena|off is now known as jpena07:48
*** slunkad has joined #openstack-nova07:49
*** ccamacho has joined #openstack-nova07:51
*** kukacz_ has joined #openstack-nova07:55
*** yamahata has joined #openstack-nova07:57
*** wolverineav has quit IRC07:57
*** wolverineav has joined #openstack-nova07:57
*** janki has quit IRC07:57
*** kukacz_ has quit IRC08:01
*** kukacz_ has joined #openstack-nova08:01
*** wolverineav has quit IRC08:02
*** ttsiouts has quit IRC08:04
*** ttsiouts has joined #openstack-nova08:04
*** yassine has joined #openstack-nova08:04
*** yassine is now known as Guest3880308:05
*** lucas-afk is now known as lucasagomes08:07
*** kukacz_ has quit IRC08:07
*** mgoddard has joined #openstack-nova08:08
*** zhaochao has quit IRC08:10
*** kukacz_ has joined #openstack-nova08:11
*** kukacz_ has quit IRC08:14
*** kukacz_ has joined #openstack-nova08:14
*** salv-orlando has joined #openstack-nova08:15
*** salv-orlando has quit IRC08:15
*** salv-orlando has joined #openstack-nova08:16
openstackgerritZhenyu Zheng proposed openstack/nova master: WIP new migration threads control  https://review.openstack.org/56350508:17
*** zhaochao has joined #openstack-nova08:22
*** yamahata has quit IRC08:23
bauwserandreykurilin: remind me, if I'm using novaclient python bindings for calling Nova, if I'm not providing a specific microversion request, then I get v2.1, right?08:24
bauwsercontrary to when using the nova CLI, when we ask for nova.latest microversion, right?08:25
*** damien_r has quit IRC08:25
bauwsergibi: if you remind as well ^08:25
*** derekh has joined #openstack-nova08:25
bauwserI mean, when I do a Client('2'), I should only get v2.108:29
bauwseractually, I should get /v2 which maps to /v2.1 to be precise08:29
*** mdbooth has joined #openstack-nova08:29
*** stephenfin is now known as finucannot08:29
*** damien_r has joined #openstack-nova08:30
bauwseryeah, confirmed https://github.com/openstack/python-novaclient/blob/master/novaclient/api_versions.py#L233-L23408:31
bauwserdo we have any novaclient specialists here ?08:31
bauwserjust to confirm08:31
*** lyarwood has quit IRC08:34
*** damien_r has quit IRC08:35
*** andreas_s has quit IRC08:38
*** andreas_s has joined #openstack-nova08:39
*** markvoelker has joined #openstack-nova08:39
*** damien_r has joined #openstack-nova08:41
*** germs has quit IRC08:43
*** germs has joined #openstack-nova08:44
*** germs has quit IRC08:44
*** germs has joined #openstack-nova08:44
*** Tom-Tom has quit IRC08:44
*** lbragstad has quit IRC08:45
*** lbragstad has joined #openstack-nova08:45
openstackgerritNguyen Hai proposed openstack/nova-specs master: Follow the new PTI for document build  https://review.openstack.org/55180208:46
*** Tom-Tom has joined #openstack-nova08:47
*** gibi is now known as giblet08:47
*** Tom-Tom has quit IRC08:47
gibletbauwser: I don't know08:49
bauwserno worries, I think I have all that I want08:49
gibletOK08:49
bauwserwe discover the versions with the shell08:50
bauwserbut we don't with the python bindings directly08:50
*** salv-orlando has quit IRC08:53
*** andreas_s has quit IRC09:01
*** andreas_s has joined #openstack-nova09:02
*** janki has joined #openstack-nova09:03
*** markvoelker has quit IRC09:12
*** tssurya has joined #openstack-nova09:25
*** udesale_ has joined #openstack-nova09:29
*** udesale__ has joined #openstack-nova09:31
*** udesale has quit IRC09:32
*** dtantsur|afk is now known as dtantsur09:33
*** udesale_ has quit IRC09:34
*** yamamoto has joined #openstack-nova09:49
*** rabel_ has joined #openstack-nova09:51
rabel_hi there. I just saw that add-floating-ip action is deprecated in compute api. but how is a floating ip associated to an instance then?09:51
*** fragatina has quit IRC09:52
*** fragatina has joined #openstack-nova09:53
*** yamamoto has quit IRC09:53
*** kholkina has joined #openstack-nova09:54
*** rabel_ has left #openstack-nova09:55
*** rabel_ has joined #openstack-nova09:55
rabel_found it. network api https://developer.openstack.org/api-ref/network/v2/#floating-ips-floatingips09:55
*** rabel_ has left #openstack-nova09:55
*** salv-orlando has joined #openstack-nova09:57
*** georgk has joined #openstack-nova09:59
*** georgk has left #openstack-nova09:59
*** armaan has joined #openstack-nova10:04
*** wolverineav has joined #openstack-nova10:07
*** hoangcx has quit IRC10:08
*** markvoelker has joined #openstack-nova10:08
*** wolverineav has quit IRC10:12
*** udesale_ has joined #openstack-nova10:13
*** udesale__ has quit IRC10:16
*** tiendc has quit IRC10:17
*** andreas_s has quit IRC10:25
*** andreas_s has joined #openstack-nova10:27
*** r-daneel has joined #openstack-nova10:29
*** mvk has quit IRC10:30
*** salv-orlando has quit IRC10:31
*** andreas_s has quit IRC10:35
*** lpetrut has quit IRC10:39
*** markvoelker has quit IRC10:42
openstackgerritStephen Finucane proposed openstack/nova-specs master: Add 'numa-aware-vswitches' spec  https://review.openstack.org/54129010:48
finucannotjaypipes, giblet: OK, I think that spec is good to go now. I've clarified a lot of the physnet/provider net stuff and fixed the diagrams https://review.openstack.org/54129010:49
* finucannot goes to catch up on bandwidth-aware scheduling10:49
*** phuongnh has quit IRC10:50
*** liuzz has quit IRC10:50
gibletfinucannot: looking10:55
*** spsurya has quit IRC10:56
openstackgerritSurya Seetharaman proposed openstack/nova stable/queens: Make association_refresh configurable  https://review.openstack.org/56628811:01
*** wolverineav has joined #openstack-nova11:02
*** andreas_s has joined #openstack-nova11:03
*** alexchadin has quit IRC11:04
*** salv-orlando has joined #openstack-nova11:07
gibletfinucannot: your spec looks good to me11:08
*** tssurya is now known as sususuryashines11:09
*** lpetrut has joined #openstack-nova11:09
*** dave-mccowan has joined #openstack-nova11:14
*** abhishekk has quit IRC11:14
*** alexchadin has joined #openstack-nova11:17
*** lucasagomes is now known as lucas-pto11:17
*** udesale__ has joined #openstack-nova11:22
*** udesale__ has quit IRC11:22
*** udesale_ has quit IRC11:24
*** Eran_Kuris has quit IRC11:26
*** LiveOne_ has quit IRC11:26
*** pcaruana has quit IRC11:27
*** salv-orlando has quit IRC11:31
*** BobBall has quit IRC11:33
*** markvoelker has joined #openstack-nova11:39
*** pcaruana has joined #openstack-nova11:39
*** nicolasbock has joined #openstack-nova11:42
*** Eran_Kuris has joined #openstack-nova11:44
*** suresh12 has joined #openstack-nova11:46
*** Eran_Kuris_ has joined #openstack-nova11:47
*** Eran_Kuris has quit IRC11:49
openstackgerritBalazs Gibizer proposed openstack/nova-specs master: Placement: any traits in allocation_candidate query  https://review.openstack.org/56573011:50
openstackgerritBalazs Gibizer proposed openstack/nova-specs master: Placement: support mixing required traits with any traits  https://review.openstack.org/56574111:50
*** linkmark has quit IRC11:51
*** suresh12 has quit IRC11:51
*** edmondsw has joined #openstack-nova11:53
*** Eran_Kuris_ has quit IRC11:54
*** kaisers1 has joined #openstack-nova11:55
*** kaisers has quit IRC11:56
*** annp has quit IRC11:57
*** pcaruana has quit IRC11:59
*** Eran_Kuris_ has joined #openstack-nova12:01
*** liverpooler has joined #openstack-nova12:01
openstackgerritBalazs Gibizer proposed openstack/nova-specs master: Placement: support mixing required traits with any traits  https://review.openstack.org/56574112:02
*** jpena is now known as jpena|lunch12:03
*** jmccarthy has joined #openstack-nova12:03
jmccarthyHmm I still have this issue where after a cold migration, a disk.info file shows up in instance dir and is left on source host12:06
jmccarthyI'm using kolla stable/queens - does this log seem right ?12:06
jmccarthyhttp://paste.openstack.org/show/720358/12:06
jmccarthyIt's when the resize/migration is confirmed that it shows up12:07
jmccarthyThis part looks good CMD "rm -rf /var/lib/nova/instances/371e669b-0f15-49f2-9a84-bd1e89f34294_resize" returned: 012:09
jmccarthyBut then a lock is acquired on disk.info *after that ? and it's left there ..12:10
*** jistr is now known as jistr|mtg12:11
*** pcaruana has joined #openstack-nova12:12
*** markvoelker has quit IRC12:12
*** pchavva has joined #openstack-nova12:15
*** alexchadin has quit IRC12:15
*** dtantsur is now known as dtantsur|brb12:17
*** vladikr has joined #openstack-nova12:21
jmccarthyAfter migrating an instance, is /var/lib/nova/instances/371e669b-0f15-49f2-9a84-bd1e89f34294/disk.info supposed to written out on the source host ?12:21
jmccarthys/After/After cold-/12:21
*** markvoelker has joined #openstack-nova12:24
*** mchlumsky has joined #openstack-nova12:26
*** mchlumsky has quit IRC12:30
*** jistr|mtg is now known as jistr12:31
openstackgerritMerged openstack/nova master: libvirt: Drop BAD_LIBVIRT_CPU_POLICY_VERSIONS  https://review.openstack.org/56401212:31
openstackgerritMerged openstack/nova master: libvirt: Drop MIN_QEMU_POSTCOPY_VERSION  https://review.openstack.org/56572412:31
openstackgerritMerged openstack/nova master: libvirt: Drop MIN_LIBVIRT_REALTIME_VERSION  https://review.openstack.org/56570712:31
*** mchlumsky has joined #openstack-nova12:32
*** vivsoni_ has joined #openstack-nova12:35
*** vivsoni has quit IRC12:35
finucannotgiblet: One thought I had on numa-aware-vswitches: how do we deal with changes in the networks attached to the guest when migrating? I think you touched on that here https://review.openstack.org/#/c/541290/8/specs/rocky/approved/numa-aware-vswitches.rst@24312:37
*** armaan has quit IRC12:38
gibletfinucannot: yes. even if the network itself is not changing the NUMA affinity of the devices providing access to the given network can be different on different hosts12:38
*** armaan has joined #openstack-nova12:38
gibletfinucannot: and the actual physnet can change if we have multiprovider networks with mutliple segments having different physnets12:39
gibletfinucannot: but the later does not supported today by nova anyhow12:39
finucannotOK, I don't think that's actually an issue. In that case, we'd be regenerating the guest NUMA topology for the new host and that would use the new host's NUMA-network mapping12:39
finucannotAlso, I think we decided multi-segment is out-of-scope12:39
gibletfinucannot: multi-segment is out of scope, I agree12:39
finucannotI'm more concerned about the actual networks attached. We've said that a user has to allocate networks at instance creation time so we can do NUMA affinity12:40
finucannotHowever, you can attach/detach networks to/from a running instance, right?12:40
gibletfinucannot: could you be bit more specific how the network changes in your scenario12:40
gibletfinucannot: ahh, yes12:41
finucannotSo I boot an instance attached to network 'foo' and then, once it's running, detach from 'foo' and attach to 'bar'12:41
gibletfinucannot: when you attach a new port / network that might affect the necessary affinity12:41
finucannotYeah, exactly. We can't do anything about that while the instance is on the same host, but what about if we migrate/rebuild?12:42
gibletfinucannot: you can actually check if the port being attached creates a contradiction with the existing affinity of the instance12:42
gibletfinucannot: and you might reject the attach12:43
gibletfinucannot: but I agree that when you migrate you have to take every port / network into account12:43
gibletfinucannot: including those that was attached after the boot12:43
finucannotYeah, we could do that. I guess that could/should be a configurable policy option down the line12:44
finucannotBut yeah, I'm thinking I should regenerate the NetworkRequestList object attached to the instance/request spec when migrating to reflect the network topology pre-migration12:45
finucannotThat might even happen already. I should check12:45
*** slunkad has quit IRC12:45
*** pchavva has quit IRC12:45
*** pchavva has joined #openstack-nova12:46
gibletfinucannot: I think regenerating the information from Neutron is the safe solution12:46
*** yamamoto has joined #openstack-nova12:46
*** Nel1x has joined #openstack-nova12:46
gibletfinucannot: I would even go that far that don't persist the NetworkRequestList but simply regenerate when it is needed12:47
*** yamamoto has quit IRC12:48
*** yamamoto has joined #openstack-nova12:49
finucannotYou need to though so that you can use it during claiming. Without that we have no way to figure out what's necessary https://review.openstack.org/#/c/541290/8/specs/rocky/approved/numa-aware-vswitches.rst@24312:52
finucannotwhoops12:52
finucannothttps://review.openstack.org/#/c/564449/1/nova/compute/claims.py12:52
finucannotIt also needs to be stored in the RequestSpec object so that we don't need to query neutron from the filters (which we can't do because we don't have correct context)12:53
*** yamamoto has quit IRC12:53
*** andreas_s has quit IRC12:54
*** jpena|lunch is now known as jpena12:54
*** udesale has joined #openstack-nova12:54
*** alexchadin has joined #openstack-nova12:55
gibletfinucannot: does the RequestSpec loaded from the db in the scheduler or passed via rpc?12:55
*** felipemonteiro has joined #openstack-nova12:55
finucannotThe former, to the best of my knowledge12:55
gibletfinucannot: then I agree that you have to store the NetworkREquestList to the db along with the RequestSpec12:56
*** Nel1x has quit IRC12:56
*** andreas_s_ has joined #openstack-nova12:56
*** andreas_s_ has quit IRC12:56
*** andreas_s_ has joined #openstack-nova12:56
finucannotYeah, I mapped the whole thing here http://paste.openstack.org/show/720365/12:56
*** edleafe is now known as figleaf12:57
*** ratailor has quit IRC12:59
gibletfinucannot: I think the RequestSpec is passed to the scheduler via rpc https://github.com/openstack/nova/blob/5d97937c3c56a3e240a3350a7a9f0e3dcb954c52/nova/scheduler/rpcapi.py#L13212:59
*** yamamoto has joined #openstack-nova13:00
gibletthe spec_obj there is a RequestSpec obj13:00
*** Guest38803 has quit IRC13:01
*** efried is now known as fried_rice13:02
gibletfinucannot: also the build_and_run_instance leading to the claim gets the instance object via rpc13:03
finucannotYup, so if I wanted to, for example, pass an additional 'network_requests' parameter to 'claim()', I guess I'd have to bump the RPC version13:04
finucannotI'm pretty sure I looked at that though and it wasn't possible. Lemme look again13:05
gibletfinucannot: you can still add the network_requests as a field to the Instance ovo and to the RequestSpec ovo, but you not necessary to persist the content of that fields to the db, as the user of that field always get the object via rpc and the sender can regenerate the content of the network_request13:06
*** mriedem has joined #openstack-nova13:06
gibletso in case of boot, the conductor generates the content of the network_request field and pass it down via the ReqestSpec of the Instance object13:07
gibletsimilarly in case of a VM move operation13:07
*** awaugama has joined #openstack-nova13:07
*** dtantsur|brb is now known as dtantsur13:09
*** gyankum has quit IRC13:09
finucannotYeah, that shouldn't be an issue for RequestSpec as I don't think those are persisted. What about Instance though. Can you mark a field in a persistent object as non-persistent?13:09
gibletpersistence is itching my mind because this data is already persisted in neutron so as soon as nova also persist it we will have two possible divergent copies13:09
gibletfinucannot: there is a request_specs table in the api db so your technical problem how to not persist a field is valid for both object13:11
*** amoralej is now known as amoralej|lunch13:12
gibletfinucannot: we should ask dansmith about this persistency issue but I have an idea13:13
gibletfinucannot: make the new field lazy_loaded13:13
*** psachin has quit IRC13:13
gibletfinucannot: and try to generate the value of the field in obj_load_attr13:13
gibletfinucannot: or another idea. never set the field in _from_db_object but set it from the conductor when the data is available13:14
gibletfinucannot: also never pass this field to the db method in save()13:15
jmccarthy@jaypipes You about ?13:16
*** r-daneel has quit IRC13:16
*** andreas_s_ has quit IRC13:17
finucannotgiblet: They're all good ideas. Let me explore them and see what I can do13:18
finucannotAgreed on split brain issue too.13:18
*** eharney has joined #openstack-nova13:18
gibletfinucannot: OK. I will have same issue with the bandwidth related resource requests coming from the neutron port and going to placement a_c query via nova-conductor and nova-scheduler13:18
*** andreas_s_ has joined #openstack-nova13:19
gibletfinucannot: but you are further down the road as you already have code up13:20
finucannotYeah, I found I needed to write that so I could actually reason about stuff properly, otherwise I was guessing a lot of it :D13:20
finucannotTurns out I didn't know the scheduler all that well, heh13:21
gibletfinucannot: yeah devil is in the details and in this cases writing code means seeing the details13:24
*** sahid has quit IRC13:24
* giblet have to start coding up some PoC for the bandwidth 13:25
*** sahid has joined #openstack-nova13:25
mriedembauwser: can you get https://review.openstack.org/#/c/566161/ ?13:26
*** mingyu has quit IRC13:26
*** jaypipes is now known as pipesinpain13:27
pipesinpainjmccarthy: yes13:28
*** esberglu has joined #openstack-nova13:28
pipesinpainfinucannot: cool, will review this morning.13:28
*** gbarros has joined #openstack-nova13:28
bauwsermriedem: ack, looking13:28
jmccarthypipesinpain: Hiya ! Just wondering if you might have some insight into this bug here ? 1769131 It sounds a lot like 166683113:30
*** gouthamr has joined #openstack-nova13:30
gibletmriedem: both pipesinpain, fried_rice and mlavalle seems to be OK with the nova bandwidth spec. So if you are interested then this is a good time to look at it https://review.openstack.org/#/c/502306/13:31
fried_ricepipesinpain: elbow?13:31
pipesinpainfried_rice: yeah :(13:32
pipesinpainjmccarthy: will take a look after caffeinating.13:33
fried_riceDid you golf or something?13:33
pipesinpainfried_rice: nope. didn't do anything.13:33
fried_riceboo.  Your elbow and my knees.  No idea what happened, just swelling and pain this morning.  Hell to get old.13:33
*** jmccarthy has quit IRC13:34
gibletpipesinpain, fried_rice: I hope both of you get better soon13:35
fried_ricethanks giblet13:35
*** andreas_s_ has quit IRC13:35
pipesinpaingiblet: thx man.13:35
*** jmccarthy has joined #openstack-nova13:36
jmccarthyErg vpn blipped13:36
*** andreas_s has joined #openstack-nova13:37
jmccarthyI've been looking at driver.py but I may be misinterpreting some of the comments that are in there - this seems relevant https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L116413:37
mriedemgiblet: ok will do13:37
gibletmriedem: thanks13:37
pipesinpainjmccarthy: you are using volume-backed instances, yes?13:38
pipesinpainjmccarthy: i.e. boot-from-volume13:38
*** esberglu has quit IRC13:39
*** brault has quit IRC13:39
jmccarthyI have to check what horizon says, spawning cirros with cinder, so volume backed yep13:39
*** esberglu has joined #openstack-nova13:39
pipesinpainjmccarthy: right. so that is the behaviour by design.13:40
*** andreas_s has quit IRC13:40
*** andreas_s has joined #openstack-nova13:40
pipesinpainjmccarthy: maciej had added that code to ensure that the volume wasn't removed when resizing.13:40
pipesinpainjmccarthy: for boot-from-volume instances, you don't want to delete the original root volume, clearly :)13:40
pipesinpainjmccarthy: I'm wondering if this is because of some thin/sparse copy-on-write stuff that Docker is doing maybe..13:41
jmccarthypipesinpain: The volume itself is in cinder and seems safe enough in my case ? It's this disk.info that shows up on host that is throwing me off13:42
pipesinpainjmccarthy: but in all honesty, I'm pretty much the worst person to ask on this :) a) I have little knowledge of the block device layer, b) I don't use (or support) boot-from-volume, and c) I don't use resize ;)13:42
pipesinpainjmccarthy: good people to hit up are mriedem when he's online and maybe mdbooth13:42
jmccarthypipesinpain: Oh ok I thought you might know, since my disk.info issue sounds a lot like a bug you fixed up13:43
jmccarthypippesinpain: Ok I'll ask around - I'm just not sure why it would leave this file on the host afterwards, seems odd13:43
pipesinpainjmccarthy: that was more melwitt (soon to be jgwentworth) that fixed that bug :)13:43
openstackgerritKashyap Chamarthy proposed openstack/nova master: libvirt: Remove support for monitoring Intel CMT `perf` events  https://review.openstack.org/56524213:43
* kashyap wonders if the above requires a rel note13:43
jmccarthypipesinpain: Ok ! :) Sorry for the noise13:43
pipesinpainjmccarthy: no problem at all, man :)13:44
jmccarthyAny of those people sitting quielty by ? ;)13:44
*** andreas_s has quit IRC13:44
*** yamamoto has quit IRC13:45
pipesinpainjmccarthy: melwitt will be up in the next hour or so. mriedem will be by soon I imagine (PST and CST respectively)13:46
jmccarthyIn horizon, if it boots from image and you create a new volume at the same time in persistent storage for it, that not boot-from-volume strictly speaking, correct ?13:46
pipesinpainjmccarthy: mdbooth is in GMT so should be around (he's likely seen "boot from volume" and run screaming for the hills) :P13:46
*** andreas_s_ has joined #openstack-nova13:46
pipesinpainjmccarthy: no, that's not boot-from-volume.13:47
jmccarthypipesinpain: That is a volume backed instance, but booted off image - does that have a special name ?13:47
pipesinpainjmccarthy: boot-from-volume is when you supply a prebuilt bootable volume as your root disk (disk 0) for the instance13:47
*** slunkad has joined #openstack-nova13:47
pipesinpainjmccarthy: that's a normal instance, then13:47
jmccarthypipesinpain: I am using volumes, but nope, not boot from vol, ok normal instances13:47
pipesinpainjmccarthy: you mean you just added a non-bootable data volume to the instance, right?13:48
wolverineavhi, while working on a neutron plugin, i ran into a weird situation where nova sends multiple requests for bind_port on different hosts, before neutron has had a chance to complete the first request. i’m guessing this would be by design, since I don’t see error or warning about the first request failing. in case anyone would know where the code path for this resides, that’d be great!13:48
pipesinpainjmccarthy: good man, yes, that's not boot-from-volume :)13:48
jmccarthypipesinpain: Well not manually ? Horizon just does it .. "Instance source is the template used to create an instance. You can use an image, a snapshot of an instance (image snapshot), a volume or a volume snapshot (if enabled). You can also choose to use persistent storage by creating a new volume."13:48
pipesinpainwolverineav: ironic?13:49
wolverineavno, instance creation in overcloud13:49
mriedemjmccarthy: nova show the instance on the CLI, if the image_ref is "", it's volume-backed (boot from volume)13:49
pipesinpainjmccarthy: right. and you chose the "persistent storage by creating a new volume", yes?13:49
wolverineavpipesinpain: no, instance creation in overcloud13:49
jmccarthypipesinpain: Mine just says 'create new volume' but yep13:50
pipesinpainwolverineav: multiple requests to bind the port to different hosts for the same instance? :(13:50
jmccarthypipesinpain: Afaik this creates an instance the lives solely in the volume like, and subsequently will boot from there13:51
jmccarthypipesinpain: 'pipesinpain' sounds painful13:52
*** armaan has quit IRC13:52
*** r-daneel has joined #openstack-nova13:52
*** lyan has joined #openstack-nova13:53
*** amoralej|lunch is now known as amoralej13:53
*** lyan is now known as Guest3656613:53
pipesinpainjmccarthy: no. unless I'm mistaken (very much a possibility), "create a volume" just means the "You can also choose to use persistent storage by creating a new volume." option. In other words, it creates a data volume (non-bootable) for the instance to use.13:56
wolverineavpipesinpain: sorry about the phrasing - i'm looking at the problem completely from neutron logs - i (neutron) get port_update request with 2 different hosts in a span of less than 30secs. typically, there's about 3 port updates until its finally bound and in active state. i couldn't figure out where the aggresive timeout is, that forces a retry to another host. so i was checking in nova group if that was known :)13:56
*** rajinir has joined #openstack-nova13:57
pipesinpainwolverineav: but this is a port binding request for the *same* instance, yes?13:57
wolverineavpipesinpain: yes, correct.13:58
*** ratailor has joined #openstack-nova13:58
pipesinpainwolverineav: that is *seriously* odd...13:58
pipesinpainwolverineav: I can't understand why multiple hosts would be port-bound to the same instance at the same time13:59
*** r-daneel has quit IRC13:59
pipesinpainwolverineav: that would mean that the scheduler essentially picked multiple hosts for the same instance.13:59
*** r-daneel has joined #openstack-nova13:59
pipesinpainwolverineav: or that a retry is occurring nearly instantaneously.13:59
pipesinpainwolverineav: since the scheduler absolutely cannot simultaneously pick multiple hosts for the same instance, it must be related to the retry.14:00
jmccarthypipesinpain: Hmm ok, what would that instance be booting from for future boots like after it's created ? I thought it did stuff with the image and used it to make the vol bootable like. I only see a /dev/sda and /dev/sda1 in the instance itself (which I thought was the new volume it created, made bootable) - I could be missing something ..14:00
pipesinpainwolverineav: can you please look in the compute logs for "Retry"?14:01
pipesinpainjmccarthy: it would be booting from the same original image you selected in horizon.14:01
pipesinpainjmccarthy: and would *attach* the persistent data volume after boot.14:01
wolverineavpipesinpain: i had to follow threads to figure out what was happening. it caused some inconsistency issue between neutron and DB and backend network controller when two requests got processed in different order in neutron vs calls made to controller.14:01
wolverineavpipesinpain: yes, let me check. I did not notice anything earlier. but i'll enable debug to be sure14:02
jmccarthypipesinpain: Hmm ok that's still ok, I mean there is no other disk file for it in /var/lib/instances anywhere (at least that I could find)14:02
pipesinpainwolverineav: any chance you can upload the compute logs somewhere? or at least, a section of them around where this is happening?14:02
jmccarthypipesinpain: (of whatever the path is, I'm sure I typed that wrong)#14:02
wolverineavpipesinpain: it doesn't always happen, so i don't have debug enabled logs (first happened at a customer site). i'll ping back here (/mailing list) once i have that reproduced.14:03
pipesinpainwolverineav: ++, thank you sir! :)14:04
jmccarthypipesinpain: Sorry yes of course - I am confusing the preparation of volume to be used to boot from - nevermind :) I still think there is a bug or something strange going on :) Thanks for your help !14:06
*** armaan has joined #openstack-nova14:08
mriedemgiblet: weren't we at one point talking about the scheduler creating the allocations against the nic bw providers? now that gets passed down to neutron through port binding in the latest revision of the spec.14:10
pipesinpainjmccarthy: no problemo :)14:10
mriedemhonestly i can't remember which one i was pushing for a month ago14:10
*** mlavalle has joined #openstack-nova14:10
gibletmriedem: scheduler does the claim, but nova sends to neutron what was claimed14:10
mriedemoh, ok, that was'nt clear to me yet14:11
*** Cardoe has joined #openstack-nova14:12
*** evin has quit IRC14:12
*** jmccarthy has quit IRC14:12
gibletmriedem: please leave a comment and I will clarify that in the spec14:13
Cardoemriedem: You asked about rebooting rescued instances the other day at Rackspace here. I'm trying to find you an answer.14:13
mriedemCardoe: that would be great, thanks - also posted to the openstack-dev ML14:13
Cardoefull disclosure, I'm fairly new here and I don't have any OpenStack experience/knowledge.14:14
CardoeI'm purely a Xen hypervisor individual. But I hate hearing about downstream custom bits and fully advocate upstreaming all.14:14
CardoeHence why someone prodded me, but I'll do my best to get to the bottom of it.14:15
*** melwitt is now known as jgwentworth14:15
jgwentworthpipesinpain: just looked at those two bugs, agreed they look similar -- that is, the fix for the one should have avoided the problem in the other it seems. but I know not more than that, have to look deeper into it14:17
*** salv-orlando has joined #openstack-nova14:18
*** salv-orlando has quit IRC14:18
*** alexchadin has quit IRC14:19
*** Shilpa has quit IRC14:20
openstackgerritEric Fried proposed openstack/nova master: Base test module/class for functional placement db  https://review.openstack.org/56459014:24
openstackgerritEric Fried proposed openstack/nova master: Use test_base symbols directly  https://review.openstack.org/56459214:24
openstackgerritEric Fried proposed openstack/nova master: Use helpers in test_resource_provider (func)  https://review.openstack.org/56463814:24
mriedempipesinpain: giblet: thinking about ironic and this nw bw qos thing - in the case of ironc, if the user wants guaranteed minimum bw, do they just request that using a specific ironic flavor with a custom resource class indicating that ironic node will have that min bw?14:25
mriedemor its still tied up in the port?14:25
gibletmriedem: I don't know. How does ironic request a port today? via neutron?14:27
mriedemjroll: ^14:27
gibletmriedem, jroll: or maybe the real question is, who handles the compute side of the networking in case of ironic14:28
gibletmriedem, jroll: as the current bandwidth spec only handles the bandwidth resource on the device that is in the compute node14:29
*** artom_ has joined #openstack-nova14:29
mriedemgiblet: the reason i ask is because i was reading the "Finding the compute RP" section14:29
*** artom has quit IRC14:29
mriedemand thinking about how >1 ironic node will have the same compute 'host'14:29
kashyapmriedem: When you get a sec, does this require a release note?  Remove support for monitoring Intel CMT `perf` events  https://review.openstack.org/56524214:30
mriedemif we just can't support ironic, fine, i just want to make sure i understand it's a limitation14:30
mriedemkashyap: yes14:30
mriedemat least as an fyi14:30
mriedemkashyap: just put in an 'other' release note14:30
kashyapmriedem: Yeah, thought so.  Let me make it right away14:30
mriedemor 'update'14:30
kashyapThanks14:30
mriedem*'upgrade'14:30
kashyapYep, the 'upgrade' tag seems more applicable14:31
*** jmccarthy has joined #openstack-nova14:31
gibletmriedem: the name field of the ResourceProvider has a unique constraint in the DB so the unique compute node RP name is enforced for ironic case as well14:31
*** hemna_ has joined #openstack-nova14:31
gibletmriedem: I guess ironic uses the node name instead of the host name for the compute RP14:32
*** lpetrut has quit IRC14:34
Cardoemriedem: So vm_states.py doesn't allow rebooting from rescue either.14:35
jmccarthymriedem: Hiya, just wondering if you have any ideas maybe about this bug ? https://bugs.launchpad.net/nova/+bug/1769131 It seems like another bug that has come up before (1666831) but I'm not sure what the story is14:36
openstackjmccarthy: Error: Could not gather data from Launchpad for bug #1769131 (https://launchpad.net/bugs/1769131). The error has been logged14:36
mriedemCardoe: correct. the upstream nova api doesn't allow rebooting a rescued vm14:36
Cardoemriedem: I'm talking about the rax patched version14:36
mriedemCardoe: oh, heh14:36
CardoeI had to figure out how to get into a compute node over here.14:36
mriedemis it maybe hard-coded into the nova/compute/api.py code?14:37
mriedemthere was some refactoring done in there in the last couple of releases, and i don't think rax has updated code to match upstream in a long time14:37
Cardoechecked that too. the @check_instance_state is the same as upstream14:37
mriedemso don't check vm_states.py, check nova/compute/api.py:API.reboot()14:38
jrollmriedem: giblet: for ironic, nova creates the port and ironic updates it later in the provisioning process14:38
mriedemhmm14:38
jrollI would like to see qos be a traits thing14:38
Cardoewell not the same because yeah I see the results of a big refactor but it doesn't seem to be allowed in there.14:38
jrollfor ironic, it's just a property of the machine, not anything we can control14:38
* jroll has to step away for a bit14:39
mriedemCardoe: i don't suppose anyone still has a line to Matthew Sherborne huh14:39
gibletjroll: the current spec defines bandwidth as a resource on provided by the physical device on the compute https://review.openstack.org/#/c/502306/14:39
mriedembecause https://bugs.launchpad.net/nova/+bug/1170237 seems totally bogus14:39
openstackLaunchpad bug 1170237 in OpenStack Compute (nova) "cannot reboot instances when in rescue mode" [Medium,Fix released] - Assigned to Matthew Sherborne (msherborne+openstack)14:39
jrollhrm14:39
jrollgiblet: I'll visit it when I'm back from errands14:39
mriedemunless he just took a bunch of nova people on a wild goose chase 5 years ago14:39
*** germs has quit IRC14:39
gibletjroll: thanks14:39
Cardoemriedem: I'm lighting up some folks. I'll get you a better answer soon.14:40
*** germs has joined #openstack-nova14:40
*** germs has quit IRC14:40
*** germs has joined #openstack-nova14:40
*** andreas_s_ has quit IRC14:41
*** eharney has quit IRC14:42
*** hongbin has joined #openstack-nova14:43
*** armaan has quit IRC14:44
gibletmriedem: as far as I understand neutron only configures TOR switches for ironic and ironic does the compute side physical device handling14:45
*** armaan has joined #openstack-nova14:45
gibletmriedem: this means that neutron does not know what capabilities the physical device has14:45
*** yamamoto has joined #openstack-nova14:45
*** r-daneel has quit IRC14:45
gibletmriedem: so I think if ironic needs bandwidth handling the ironic virtdriver can create RPs with traits/resources and the user request that via flavor extra_spec14:45
openstackgerritEric Fried proposed openstack/nova master: placement: Granular GET /allocation_candidates  https://review.openstack.org/51775714:47
gibletmriedem: when (if) the bandwidth handling support is extened to TOR switches then baremetal neutron ports will have a resource request describing what the resource the port needs on the TOR switch14:47
*** jistr is now known as jistr|tpb14:49
kashyap"Lighting up some folks" brings a very strong image to the brain...14:50
*** yamamoto has quit IRC14:52
*** r-daneel has joined #openstack-nova14:52
*** andreas_s has joined #openstack-nova14:52
*** dpawlik has quit IRC14:52
mriedemjgwentworth: am i dreaming this up, or did we agree at the dublin ptg to add a type column to the consumers table in placement to be able to distinguish instance from migration consumers?14:57
*** gyankum has joined #openstack-nova14:59
jgwentworthmriedem: no, there wasn't agreement on that. but I realized what I needed it for (quotas) could be achieved with instance_mappings + queued_for_delete column + user_id column15:00
*** andreas_s has quit IRC15:00
mriedemoh i was just looking for it in your "count quotas using placement" spec15:00
mriedemah i found it here https://etherpad.openstack.org/p/nova-ptg-rocky15:01
mriedem"In Sydney we talked about tracking a 'type' in the placement allocations/consumers tab"...15:01
jgwentworthyeah, that spec has been languishing and I really needed to update it after tssurya proposed her spec for adding queued_for_delete since mine would depend on that15:01
mriedemgiblet: i dont know what "If QoS aware and non QoS aware ports are mixed on the same physical port" means15:02
*** armaan has quit IRC15:02
*** armaan has joined #openstack-nova15:02
mriedemthat's possible today? to have a port in neutron that is both qos aware and not at the same time?15:02
jgwentworthyeah, we discussed the 'type' idea a bit at the ptg but things got pretty complicated, it would not be straightforward. we may need it someday for other reasons but nothing right now really needs it. I had thought I needed it for quotas but realized I didn't if we could have two more instance_mappings columns15:03
mriedemjgwentworth: ack; it's the new bdm.uuid column - something we'll always think we need every 4 months15:03
gibletmriedem: assume there is a compute node with an SRIOV PF that provide VFs for neutron ports.15:03
jgwentworthmriedem: heh yeah15:04
gibletmriedem: after our spec that PF will also provide bandwidth as well15:04
jgwentworth(I think we do have the bdm.uuid column now tho)15:04
gibletmriedem: a neutron port might have a QoS policy rule attached15:04
mriedemjgwentworth: yes we do15:05
gibletmriedem: when we place a neutron port with QoS policy rule attached to the above PF we will consume some bandwidth as well15:05
*** jistr|tpb is now known as jistr15:05
mriedemfor mdbooth's local device serial series15:05
jgwentworthneed=TRUE15:05
jgwentworthah right15:05
jgwentworthpersistent cereal numbers15:05
gibletmriedem: but if there is two neutron port one with QoS another without QoS ends up using VFs from the same PF then the minimum bandwidth rule cannot be garanteed15:05
mriedemjgwentworth: ala https://images-na.ssl-images-amazon.com/images/I/51hDzZDOhdL.jpg ?15:06
*** r-daneel has quit IRC15:06
mriedemgiblet: ok15:06
mriedemover my head nfv isms, but ok15:06
jgwentworthhah, yup15:06
*** r-daneel has joined #openstack-nova15:06
*** eharney has joined #openstack-nova15:07
gibletmriedem: :)15:08
*** artom_ has quit IRC15:08
*** ratailor has quit IRC15:08
dansmithjgwentworth: just to be clear, avoiding the type column with mappings doesn't require joining any placement and nova-api tables right?15:10
jgwentworthdansmith: no, I was thinking a mappings query for count of instance_mappings that would be filter on project_id and user_id where queued_for_delete=015:12
openstackgerritKashyap Chamarthy proposed openstack/nova master: libvirt: Remove support for monitoring Intel CMT `perf` events  https://review.openstack.org/56524215:12
dansmithjgwentworth: okay that gets you quotas for instance count, but not the cores,ram,disk -- is that what you mean?15:12
jgwentworthdansmith: right. cores/ram would come from placement /usages query15:12
dansmithwhich still requires something like a type yeah?15:13
*** pcaruana has quit IRC15:13
dansmithlike if a tenant has some allocations for VCPU that isn't nova-related15:13
jgwentworthI was thinking it didn't. unless we're suggesting VCPU and RAM can come from things that are not instances15:13
jgwentworththat was not my understanding thus far15:14
idlemindso cisco's ftd (firepower threat defense - read new asa) virtual in openstack ... boot from image (w/o create a volume) works but when i create a volume it fails to boot ... what impact does this have? if i "upgrade" a ftd virtual machine does it write back to the image or emphereal storage? do i need to create an "image" for each unique ftdv?15:14
dansmithjgwentworth: we brought that up in dublin, if something else started using placement for those resource types you'd be hosed.. that was the real reason we needed type I thought15:14
dansmithjgwentworth: so for example if bifrost or something like the container service, etc allocated those resources as well15:15
dansmithjgwentworth: and non-instance DISK_GB allocations for just generic volumes15:15
jgwentworthdansmith: yeah, if that's the case, then yeah type would be an inevitable need. or at least need a way for a subsystem to ask, "what's the resource usage for the resources that **I** put there?" so some identifier that describes the source or the type15:15
*** Eran_Kuris_ has quit IRC15:16
dansmithjgwentworth: yup, either type or "creator" or something15:16
jgwentworthyeah15:16
kashyapAny "stickler for words", appreciate a quick once-over: https://review.openstack.org/#/c/565242/4/releasenotes/notes/Remove-support-for-Intel-CMT-events-017fbb890b631d70.yaml15:18
*** dave-mccowan has quit IRC15:20
*** pooja_jadhav has quit IRC15:24
jmccarthymriedman: totally missed your comment earlier ! I don't see image_ref, but 'image' has no value listed15:25
*** nicolasbock has quit IRC15:26
openstackgerritsahid proposed openstack/nova master: pci: don't consider case when match tags specs  https://review.openstack.org/56580815:27
openstackgerritsahid proposed openstack/nova master: network: update pci request spec to handle trusted tags  https://review.openstack.org/45882015:27
openstackgerritsahid proposed openstack/nova master: libvirt: configure trust mode for vfs  https://review.openstack.org/45851415:27
openstackgerritsahid proposed openstack/nova master: libvirt:  add vf_trusted field for network metadata  https://review.openstack.org/56634315:27
openstackgerritsahid proposed openstack/nova master: metadata: add vf_trusted field to device metadata  https://review.openstack.org/56634415:27
jgwentworthidlemind: boot from image without specifying a block device mapping will just use local storage on the compute host (hypervisor). boot from volume will use the volume's storage. what volume backend are you using?15:27
*** dave-mccowan has joined #openstack-nova15:27
*** suresh12 has joined #openstack-nova15:27
jgwentworthand if your local storage is shared/persistent, boot from image will use that (if you're using ceph, for example)15:28
*** Eran_Kuris_ has joined #openstack-nova15:28
sahidgiblet: there is a serie that jay already started to review, i think you were also interested about it so if you have a moment to have look https://review.openstack.org/#/c/561912/15:28
gibletsahid: I've put it on my review list15:29
sahidgiblet: thanks15:29
jmccarthyHiya melwitt: or mriedem: Any thought on this bug 1769131 ? I am getting this disk.info file created on the original compute after migrating the instance15:30
openstackbug 1769131 in OpenStack Compute (nova) "After cold-migration, disk.info file leftover on source host" [Undecided,New] https://launchpad.net/bugs/176913115:30
*** sususuryashines has quit IRC15:30
jgwentworthjmccarthy: hey, I looked at that earlier and agreed it looks like the same other similar bug you linked earlier. so I'm not sure what's going on there, how it's happening if someone already fixed the same problem15:31
jmccarthyjgwentworth: I dunno !? I'm not sure how it's happening for me, but it happens everytime15:31
jmccarthyjgwentworth: I have two setups doing it actually, but they both are cinder/lvm for volumes15:32
jgwentworthand it sounds like you're doing boot from volume? when you create the instance, are you specifying a volume or a block device mapping like source=image dest=volume?15:32
jmccarthyI'm just using horizon :| I give it an image name to start with and ask for it to create a new volume for it15:33
jgwentworthokay, that is going to be boot from volume I think15:33
smcginnisI believe so.15:33
jgwentworththat probably is why you're seeing something different than was described in the other similar bug15:33
jmccarthyWell the instance is definitely volume backed, but whether it boots from that as such I'm unclear now15:34
jgwentworthboot from volume is kind of a separate appendage in most of the code15:35
jmccarthyThe only file associated with under instances, is it's console.log, that is until I cold migrate it and this disk.info show up15:37
jgwentworthyeah, volume backed == boot from volume. it just means the operating system, disk etc is stored on the volume15:38
*** wwriverrat_ has joined #openstack-nova15:38
*** nicolasbock has joined #openstack-nova15:40
*** wwriverrat has quit IRC15:40
*** wwriverrat_ is now known as wwriverrat15:40
mriedemgiblet: a virtual cornucopia of comments and questions in https://review.openstack.org/#/c/502306/15:41
mriedemgiblet: good news is i think most of it is just asking for clarification15:41
jgwentworthjmccarthy: you see disk.info on the source or destination?15:42
openstackgerritEric Fried proposed openstack/nova master: placement: Object changes for granular  https://review.openstack.org/56435115:42
openstackgerritEric Fried proposed openstack/nova master: placement: Granular GET /allocation_candidates  https://review.openstack.org/51775715:42
gibletmriedem: thanks for the review.15:42
jmccarthyjgwentworth: It's no where in sight, until I confirm the resize/migrate - and then it appears on the host (the cold migrate completes fine)15:42
*** bnemec is now known as beekneemech15:42
jmccarthy*source host15:43
jgwentworthok15:43
jmccarthyI'm going to check - I just remembered I looked at the file earlier - have to recheck what is actually in it somethingsomething qcow2 it said in the file15:44
gibletmriedem: I will go through you comments on Monday15:44
jgwentworthyeah, I can never remember what all of those are. I have to re-look at it every time in the code15:44
mriedemdansmith: (1) where is superdan and (2) i've got a request spec modeling comment in https://review.openstack.org/#/c/502306/26/specs/rocky/approved/bandwidth-resource-provider.rst@172 that could use your input15:45
mriedemgiblet: ack15:45
*** dansmith is now known as superdan15:45
superdanmriedem: tab queued15:45
*** armaan has quit IRC15:49
*** armaan has joined #openstack-nova15:49
jgwentworthjmccarthy: what's your CONF.libvirt.images_type set to?15:50
jmccarthyone sec15:51
mriedemumm https://review.openstack.org/#/c/516395/15:51
jgwentworthhah, nice15:52
*** artom_ has joined #openstack-nova15:52
mriedemalso added a tempest test for that https://review.openstack.org/#/c/516396/15:52
jgwentworthso maybe ... supposed to remove the disk.info that imagebackend creates but don't remove the whole instance directory?15:53
jmccarthyHmm it's images_type = rbd in nova.conf15:53
jgwentworthk, thanks15:53
mriedemyeah so that's exactly what that patch was meant to fix,15:53
mriedemand from the tempest patch commit message, it's about shared storage backends15:53
mriedemso in our ci, that's ceph and nfs15:53
*** artom_ has quit IRC15:53
mriedemthe problem was you would resize the instance and then try to get the console log which was deleted15:54
*** artom_ has joined #openstack-nova15:54
mriedemhttps://bugs.launchpad.net/nova/+bug/172860315:54
openstackLaunchpad bug 1728603 in OpenStack Compute (nova) pike "Resize a boot-from-volume instance with NFS destroys instance" [High,Fix committed] - Assigned to Matt Riedemann (mriedem)15:54
jgwentworthright, that's what I'm trying to say is that it's true we shouldn't nuke the entire instance dir15:54
jgwentworthbut, we should delete the disk.info by itself15:54
jgwentworththe original intent of https://review.openstack.org/#/c/437356/3/nova/virt/libvirt/driver.py was to delete the disk.info that imagebackend sometimes creates15:55
*** damien_r has quit IRC15:55
jgwentworthbut it went ahead and took out the entire instance directory not realizing it would lose the console.log15:56
jmccarthyYea I was reading those comments in driver.py - but the rm commands seem to only involve the dir (which I agree you can remove i.e. nfs)15:56
jmccarthy*can't15:56
Cardoemriedem: ok so a bit more info. Modifying vm_states.py to allow rescued to be rebooted then it works.15:56
*** dpawlik has joined #openstack-nova15:57
mriedemCardoe: sure, when using the xenapi driver right?15:57
Cardoeyes15:57
jmccarthyjgwentworth: But there must be logic to know when it's safe to remove that dir on the source host ?15:57
jgwentworthjmccarthy: did you see the patch mriedem linked though? it's bypassing all of that if volume-backed https://review.openstack.org/#/c/516395/2/nova/virt/libvirt/driver.py because it was trying to fix the case where the console.log was being deleted15:57
mriedemi have no idea if libvirt/hyperv/vmware support that15:57
jmccarthy1728603 ? Let me look15:57
Cardoemriedem: I've been told that I do not believe that they do.15:58
jgwentworthno, https://review.openstack.org/#/c/516395/2/nova/virt/libvirt/driver.py15:58
Cardoes/I/rax OpenStack folks/15:58
jmccarthyjswentworth: I think the driver.py that I have now looks like that one ?15:59
jgwentworthjmccarthy: so because you are volume-backed, it's not removing anything at all. I think it needs to be adjusted to only delete disk.info if volume-backed, or something like that16:00
mriedemjmccarthy: because you're on queens and that change was made in queens16:00
mriedemand backported to pike and ocata because it was fixing a regression which was also backported to pike and ocata :)16:00
jmccarthyjgwentworth: Ok so it's not just me - yes some logic is missing ?16:00
mriedemit's bugs all the way down16:00
jmccarthyjgwentworth: Leaving the dir there causes a problem for live migration too16:00
*** gyee has joined #openstack-nova16:00
jgwentworthyeah, there is definitely a bug. we were just trying to find what it was16:00
mriedemjmccarthy: the dir or just the disk.info file itself?16:01
jmccarthyjgwentworth: the dir16:01
jmccarthymriedman: the dir16:01
jmccarthySorry I'm eventually getting there lol thanks for the help all ! :)16:01
jmccarthyOne sec16:01
jgwentworthso what about the console.log then? where is it supposed to go16:01
openstackgerritEric Fried proposed openstack/nova master: placement: Object changes for granular  https://review.openstack.org/56435116:01
openstackgerritEric Fried proposed openstack/nova master: placement: Granular GET /allocation_candidates  https://review.openstack.org/51775716:01
jgwentworthoh, wait, supposed to remove the dir from the source16:02
*** dpawlik has quit IRC16:02
mriedemjgwentworth: but if you're on shared local storage, deleting the dir on the source will also remove it from the dest16:02
jmccarthymriedman: Actually I have it at the end of the bug - https://bugs.launchpad.net/nova/+bug/1769131 about 'already exists, it is expected not to exist.'16:02
openstackLaunchpad bug 1769131 in OpenStack Compute (nova) "After cold-migration of a volume-backed instance, disk.info file leftover on source host" [Undecided,Triaged]16:02
jgwentworthmriedem: yeah, right. okay.16:02
mriedemjmccarthy: yeah DestinationDiskExists only happens if compute says you're not on shared storage,16:02
mriedembut since you're using image_type=rbd i'd think your computes would be using shared storage16:03
jgwentworthyeah so it sounds like just need to delete disk.info, the presence of the dir should be okay right?16:03
jmccarthyShould it ?16:03
jmccarthyI only have 2 computes16:03
jmccarthyif I try to live migrate back I get the complaint about the dir being there16:03
mriedemjgwentworth: i don't think so https://github.com/openstack/nova/blob/4b0d0ea9f18139d58103a520a6a4e9119e19a4de/nova/virt/libvirt/driver.py#L745716:03
jgwentworthoh :\16:04
mriedemjmccarthy: i guess you can use image type rbd for local storage and not having it be shared, but that seems weird16:04
jmccarthy1) cold migrate - it works, but disk.info is left on source16:04
mriedemapparently people do it, but i'm not sure why you'd be using rbd and not sharing it16:04
jmccarthy2) try to live back fails due to dir :/16:04
jgwentworththen how is this supposed to work with shared storage16:04
jmccarthymriedman: Not sure I follow, I'm using cinder for storage, not local ?16:04
mriedemthe console.log is stored on local disk for the compute host16:05
mriedemnot in cinder16:05
jmccarthyWell after the live fails then it does: Cleaning up deleted instances with incomplete migration16:05
jmccarthy_cleanup_incomplete_migrations16:05
jmccarthyand the next attempt to live migrate works16:05
jgwentworthokay yeah I see now, you are using rbd but not shared storage ... only does DestinationDiskExists if not shared16:05
mriedemso is it just me, or does https://review.openstack.org/#/c/437356/3/nova/virt/libvirt/driver.py@1136 seem like kind of a hack?16:06
jmccarthymreidman: I'm confused, I do have a console log file there, but I am getting volumes also ..16:06
Cardoemriedem: what would you like to see happen with the rescue stuff? We can try and submit a patch to allow it for xenapi?16:06
mriedem"self.image_backend.image for some backends recreates instance directory and image disk.info - remove it here if exists"16:06
jgwentworthmriedem: yeah, it does. when I read it I was like, "why is imagebackend sometimes recreating the dir"16:06
mriedemCardoe: idk yet, that's why i posted to the ML16:06
jmccarthys/getting/using16:06
mriedemthose details are in https://bugs.launchpad.net/nova/+bug/166683116:07
openstackLaunchpad bug 1666831 in OpenStack Compute (nova) ocata "Nova recreates instance directory after migration/resize" [Low,Fix committed] - Assigned to Lee Yarwood (lyarwood)16:07
*** germs has quit IRC16:08
mriedemapparently this recreates the disk.info on the source host https://github.com/openstack/nova/blob/4b0d0ea9f18139d58103a520a6a4e9119e19a4de/nova/virt/libvirt/driver.py#L115216:08
mriedemand then https://github.com/openstack/nova/blob/4b0d0ea9f18139d58103a520a6a4e9119e19a4de/nova/virt/libvirt/driver.py#L1170 was added to delete it16:08
*** kholkina has quit IRC16:08
Cardoemriedem: I've been told that the reason why we didn't upstream the change is that there was no easy way to allow it only for xenapi at the time.16:09
jmccarthyFor me this happens, and it's ok16:09
jmccarthyCMD "rm -rf /var/lib/nova/instances/371e669b-0f15-49f2-9a84-bd1e89f34294_resize" returned: 016:09
jmccarthyexcept then16:09
*** EmilienM is now known as EvilienM16:09
jmccarthyLock "/var/lib/nova/instances/371e669b-0f15-49f2-9a84-bd1e89f34294/disk.info" acquired16:09
jmccarthyand Lock "/var/lib/nova/instances/371e669b-0f15-49f2-9a84-bd1e89f34294/disk.info" released by "nova.virt.libvirt.imagebackend.write_to_disk_info_file"16:10
jmccarthyrecreates it from what I can tell ?16:10
jgwentworthyeah, I think so16:10
*** fragatina has quit IRC16:10
*** armaan has quit IRC16:11
jgwentworthCardoe: is rebooting a rescued instance only safe or something that makes sense for xenapi?16:11
mriedemright, that's what bug 1666831 is saying,16:11
openstackbug 1666831 in OpenStack Compute (nova) ocata "Nova recreates instance directory after migration/resize" [Low,Fix committed] https://launchpad.net/bugs/1666831 - Assigned to Lee Yarwood (lyarwood)16:11
mriedemand was trying to fix16:11
mriedemto summarize, the libvirt driver and the imagebackend are totally inbred and shitty16:11
mriedemmdbooth: ^?16:11
*** armaan has joined #openstack-nova16:11
mriedemthe driver needs the image backend for rbd to remove snapshots,16:11
mriedembut for qcow2 imagebackend it recreates the disk.info,16:12
mriedemso then the libvirt driver deletes the directory that imagebackend.by_name() for qcow2 created16:12
mriedemthe control flow logic in the driver _cleanup_resize method is totally tightly coupled based on the image backend being used16:12
jgwentworthyeah ... sucks16:13
*** fried_rice is now known as fried_rolls16:13
Cardoejgwentworth: No. It'd make sense for others to get it. How its been explained to me is that when someone screws up their grub or whatever bootloader and they can't boot their instance it can go into a rescue mode where their disk is attached to a read-only Linux instance where they can fix it themselves. Then when its rebooted it will go back to their original configuration, but hopefully this time with a fixed boot loader.16:13
*** r-daneel has quit IRC16:13
*** r-daneel has joined #openstack-nova16:13
mriedemCardoe: so this isn't a case where the user literally calls the rescue API on the instance and then reboots it?16:14
mriedemit's server create -> fails -> xen rescue mode shenanigans -> user reboots the instance16:15
Cardoecreate or software update16:15
mriedem"software update" being something that happens within the xen guest?16:15
mriedemthat's not a nova term16:15
mriedemanyway, none of that sounds like it puts the instance vm_state into RESCUED16:16
mriedemwhich is what the compute manager code is checking16:16
CardoeWhen the instance fails to boot, the rescue API can be called to put it into rescued.16:16
jgwentworthlooks like cfriesen might have highlighted why reboot is rejected in his reply to the ML, reboot could make it impossible to unrescue the instance?16:16
jgwentworth"loss of original instance state"16:17
mriedemjgwentworth: jmccarthy: so i have an idea about how to handle this disk.info issue,16:17
mriedemlet me wip something up here and we can take a gander16:17
jmccarthymriedman: Ok cool :)16:17
jgwentworthmriedem: sounds good16:18
mriedemCardoe: if you're subscribed to the openstack-dev ML, it would be cool if you could reply with details on the xenapi background in that thread16:19
mriedemi've got some code to break16:19
jmccarthymriedman: I did try running the tox tests in this area, either I ran the wrong tests, or this setup isn't quite covered16:20
CardoeI'm not. I certainly can as I get more info. sorry its a bad game of telephone with me. If you guys wanted to talk assembly and hypercalls I'm you're guy. APIs for orchestrating VMs not so much.16:20
*** derekh has quit IRC16:21
*** sahid has quit IRC16:24
mriedemi haven't wanted to talk assembly in 19 years16:25
jmccarthyIs it a misconfiguration on my part to have images_type = rbd if I'm not using ceph ?16:25
mriedemjmccarthy: well what local ephemeral storage on your compute hosts are you using for non-volume-backed instances?16:26
jmccarthyI don't have anything setup specifically, local disk on computes I guess ?16:26
jgwentworthI would think so, rbd == ceph16:26
superdanmriedem: do we not store network_request(s) today?16:26
mriedemhttps://docs.openstack.org/nova/latest/configuration/config.html#libvirt.images_type16:27
mriedemsuperdan: not in the request spec no16:27
mriedemnor bdms16:27
superdanmriedem: I mean at all16:27
mriedemcorrect16:27
superdanmriedem: don't we need that on rebuild/evac? or do we get it from neutron or something?16:27
*** suresh12 has quit IRC16:27
mriedemwe have the network info cache / neutron16:27
superdansurely not just the info_cache at that point...?16:27
mriedemyou can't request new ports on rebuild/evac16:27
superdanhrm16:27
*** zhaochao has quit IRC16:28
superdanmriedem: so, storing it in the reqspec.. that may potentially include port uuids that you booted with right?16:28
mriedemthe original network request list woudn't have things attached to the instance after it was created either16:28
superdanmriedem: what happens if/when I attach a new port and detach the old one.. now the reqspec has a stale from-two-years-ago port uuid in it right?16:28
mriedemsuperdan: port id or network id yeah16:28
mriedemsuperdan: yeah, same could be said about the security groups right?16:29
superdanyes, although that seems less problematic to me,16:29
mriedemthe spec says they aren't going to persist this anyway, just include it in the request spec is a middleman to get from the api to the scheduler16:29
superdanprobably because port_uuids are somewhat ephemeral16:29
*** fragatina has joined #openstack-nova16:29
mriedemi'm fine with not persisting it16:29
superdanmriedem: okay in general I think it's confusing to put things in DB-persisted objects that we don't store in the DB16:30
mriedembut i was thinking for modeling, NetworkRequest object gains a RequestGroup field, and then RequestSpec gains a (non-persisted) NetworkRequestList field16:30
superdansomeone sets something there and calls save(), no error, so expects it's saved now, but isn't16:30
superdanwhat is requestgroup?16:30
mriedemok, gibi has an alternative in the spec that it doesn't go into the request spec at all, and it's passed as a separate param to select_destinations()16:30
mriedemit's in the placement lib - contains things about a granular request group16:31
jmccarthyAh sorry ! I was looking at a template, not the final rendered file16:31
superdanoh, that right16:31
mriedemso they'd have one of those per port16:31
jmccarthyFor my deployed nova.conf there is no entry there for images_type at all (so I guess default?)16:31
superdanmriedem: well, a new rpc argument to the scheduler just for network stuff is also kinda odd, which I guess was your point16:31
mriedemif it doesn't go in the request spec because we don't persist it, then it's a new param to select_destinations()16:31
mriedemjgwentworth: so i don't think my idea will work..drats16:32
*** dtantsur is now known as dtantsur|afk16:32
mriedemjgwentworth: my idea was just to check https://github.com/openstack/nova/blob/4b0d0ea9f18139d58103a520a6a4e9119e19a4de/nova/virt/libvirt/imagebackend.py#L57 in driver._cleanup_resize and if True, do the snapshot removal stuff that is rbd-specific16:32
jgwentworth*sad trombone*16:33
mriedembut to get that value, we have to init the imagebackend object which is the thing that recreates the gd disk.info file16:33
*** artom_ is now known as notartom16:33
mriedemso, we could make a module-level dict of image types that support clone and use that,16:33
mriedemor pass a flag to imagebackend init to tell it to not touch the filesystem16:33
mriedemformer seems easier16:34
mriedemor hell, just: if CONF.libvirt.images_type == 'rbd': in _cleanup_resize16:34
mriedemthat's essentially what we'd be doing if we check SUPPORTS_CLONE16:34
jgwentworthdo you mean change the check for is_volume_backed to essentially "is_shared_storage"?16:37
*** eharney has quit IRC16:38
mriedemthat entire block goes away16:38
jmccarthy<back asap - afk>16:39
mriedemi.e. basically undo this https://review.openstack.org/#/c/437356/3/nova/virt/libvirt/driver.py16:39
mriedemand fix the logic16:39
jgwentworthoh, I see, yeah16:39
jgwentworthinstead of using root_disk.exists()16:39
mriedem"if os.path.exists(inst_base) and not root_disk.exists():" was added for qcow2/flat/ploop because those will recreate the instance dir and disk.info on init,16:39
mriedemwhen all we needed the imagebackend for was the remove_snap call,16:40
mriedemwhich is rbd-specific16:40
jgwentworthright16:40
jgwentworthgotcha16:40
mriedemso if we just don't create the imagebackend object in the first place, we avoid the init et al16:40
mriedem\o/16:40
jgwentworthyeah, seriously16:40
mriedemi of course will require jmccarthy to test the patch in his setup16:40
jgwentworthoh, because you have to use it to do the remove_snap16:41
mriedemyup and that's pointed out in https://bugs.launchpad.net/nova/+bug/166683116:41
openstackLaunchpad bug 1666831 in OpenStack Compute (nova) ocata "Nova recreates instance directory after migration/resize" [Low,Fix committed] - Assigned to Lee Yarwood (lyarwood)16:41
mriedem"root_disk is used to remove rdb snapshots, but during execution of self.image_backend.by_name() nova recreates instance directory."16:41
jgwentworthso how can we remove_snap without the imagebackend object?16:41
mriedemso in his case, he wasn't even using rbd, he was using qcow216:41
mriedemwe can, we'll get it if the backend supports clone16:42
mriedemremove_snap is only implemented for image backends that support clone16:42
jgwentworthohhhh k16:42
mriedemand that's only rb16:42
mriedem*rbd16:42
*** sridharg has quit IRC16:42
*** AlexeyAbashkin has joined #openstack-nova16:43
jgwentworthyeah, makes sense16:43
*** moshele has joined #openstack-nova16:43
openstackgerritMerged openstack/nova master: Convert websocketproxy to use db for token validation  https://review.openstack.org/33399016:44
*** armaan has quit IRC16:45
mriedemand because i added that tempest test, we should be testing a resize of a volume-backed instance on shared local storage since we have the NFS job in nova's experimental queue16:45
mriedemplus CEPH16:45
jgwentworth*mind blown*16:48
*** tbachman has quit IRC16:48
*** udesale has quit IRC16:50
*** tbachman has joined #openstack-nova16:50
*** tbachman has quit IRC16:51
*** moshele has quit IRC16:52
jmccarthyback16:54
*** armaan has joined #openstack-nova16:55
*** jpena is now known as jpena|off16:55
*** mdbooth has quit IRC16:56
*** mvk has joined #openstack-nova16:58
*** mgoddard has quit IRC17:04
jmccarthymriedem: I can test any stuff no probs ! It might take a little while, but hopefully not too long17:07
*** tesseract has quit IRC17:09
openstackgerritMatt Riedemann proposed openstack/nova master: libvirt: check image type before removing snapshots in _cleanup_resize  https://review.openstack.org/56636717:12
mriedemjmccarthy: jgwentworth: ^17:12
jmccarthymriedman: Nice !17:12
jmccarthymriedman: Let me see about working that in17:12
*** itlinux has joined #openstack-nova17:14
*** esberglu has quit IRC17:17
*** germs has joined #openstack-nova17:18
*** germs has quit IRC17:18
*** germs has joined #openstack-nova17:18
*** tbachman has joined #openstack-nova17:19
*** germs has quit IRC17:19
*** germs has joined #openstack-nova17:19
openstackgerritMerged openstack/nova master: Add multi-cell negative test for cold migration with target host  https://review.openstack.org/52402717:21
openstackgerritMerged openstack/nova master: Update layout docs for running console proxies  https://review.openstack.org/55748917:21
*** sq4ind has quit IRC17:23
*** sq4ind has joined #openstack-nova17:27
*** mgoddard has joined #openstack-nova17:36
openstackgerritMatt Riedemann proposed openstack/nova master: libvirt: remove old rbd snapshot removal error handling  https://review.openstack.org/56636917:37
openstackgerritMatt Riedemann proposed openstack/nova master: libvirt: remove old rbd snapshot removal error handling  https://review.openstack.org/56636917:38
openstackgerritJay Pipes proposed openstack/nova master: rework how we pass candidate request information  https://review.openstack.org/56616617:39
idlemindjgwentworth thx i'm using lvm via iscsi (simple stuff for now)17:39
*** suresh12 has joined #openstack-nova17:40
*** suresh12_ has joined #openstack-nova17:48
jmccarthymriedman: Ok I thought this might happen - I'm going to need a while longer, unfortunately it's a long weekend here - I'll update the bug asap but it may not be until Tuesday17:49
*** yamamoto has joined #openstack-nova17:50
jmccarthymriedman: I appreciate your quick efforts ! I'm going to keep at it another while17:51
*** suresh12 has quit IRC17:51
*** evin has joined #openstack-nova17:52
*** pcaruana has joined #openstack-nova17:54
*** gjayavelu has joined #openstack-nova17:54
*** yamamoto has quit IRC17:54
*** eharney has joined #openstack-nova17:56
*** dpawlik has joined #openstack-nova17:58
*** dpawlik has quit IRC18:03
mriedemjmccarthy: sure np18:15
pipesinpainmriedem, jgwentworth, johnthetubaguy, alex_xu: your eyeballs on https://review.openstack.org/#/c/565565/ would be appreciated.18:15
*** fragatina has quit IRC18:18
*** janki has quit IRC18:19
arvindn05mriedem: can you look over the spec amendment? https://review.openstack.org/#/c/560718/18:21
arvindn05once its approved, hoping the scheduler patch can be upstreamed18:21
*** AlexeyAbashkin has quit IRC18:30
*** owalsh is now known as owalsh-afk18:32
*** mgoddard has quit IRC18:38
*** gyankum has quit IRC18:49
*** fried_rolls is now known as fried_rice18:49
jgwentworthpipesinpain: ack, it's on my list18:53
*** imacdonn has quit IRC18:54
*** imacdonn has joined #openstack-nova18:55
* jgwentworth will bbl18:57
openstackgerritChris Dent proposed openstack/nova master: Optional separate database for placement API  https://review.openstack.org/36276618:59
openstackgerritChris Dent proposed openstack/nova master: Isolate placement database config  https://review.openstack.org/54143518:59
openstackgerritChris Dent proposed openstack/nova master: WIP: Ensure that os-traits sync is attempted only at start of process  https://review.openstack.org/55385718:59
openstackgerritChris Dent proposed openstack/nova master: WIP: Add PLACEMENT_DB_ENABLED=True to the nova-next job  https://review.openstack.org/56406719:00
*** liverpooler has quit IRC19:00
*** sq4ind has quit IRC19:04
pipesinpainjgwentworth: thx Melanie.19:06
openstackgerritMerged openstack/nova master: Base test module/class for functional placement db  https://review.openstack.org/56459019:07
*** sq4ind has joined #openstack-nova19:08
*** pchavva has quit IRC19:09
*** pcaruana has quit IRC19:10
*** sq4ind has quit IRC19:10
*** sq4ind has joined #openstack-nova19:14
*** tbachman has quit IRC19:14
eanderssonmriedem, I was gonna do a quick pull request to change the log "Successfully synced instances from host '%s'." to DEBUG, but noticed that it's still doing log translation19:19
eanderssonCan I remove the log translation in the same commit?19:20
*** jmccarthy has left #openstack-nova19:20
*** mgoddard has joined #openstack-nova19:22
mriedemeandersson: yes19:24
mriedemwe don't translate logs anymore19:24
eanderssonCan I remove the log translation for all the entries in that file? :D or will that make it too difficult to see what changed19:24
eanderssonI can also follow up with a new pull request for that :D19:24
mriedemi'd keep those separate19:25
openstackgerritErik Olof Gunnar Andersson proposed openstack/nova master: Changing scheduler sync event from INFO to DEBUG  https://review.openstack.org/56639219:27
eanderssonI don't even want to know how much disk space is wasted on that one log line :D19:29
*** mgoddard has quit IRC19:29
mriedemeasiest -1 ever19:31
eanderssonhaha19:31
eanderssonomg19:31
eanderssonwas too fixated on the translation19:31
eanderssongood, get to fix that missing e in computes19:31
kashyapmriedem: This is largely code deletion, should be easy for you: https://review.openstack.org/#/c/565242/19:32
openstackgerritErik Olof Gunnar Andersson proposed openstack/nova master: Changing scheduler sync event from INFO to DEBUG  https://review.openstack.org/56639219:32
* kashyap expects perhaps one more iteration from potential feedback from Matt19:32
mriedemeandersson: off the top of your head, what's the average number of cpus in your compute hosts?19:33
mriedem16? 32?19:34
eandersson32 probably19:35
mriedemok. so you wouldn't run something like 132 concurrent live migrations on a compute host like that would you.19:35
mriedem32 * 519:35
eanderssonYea unlikely19:35
mriedemcool, fyi https://docs.python.org/3.5/library/concurrent.futures.html#concurrent.futures.ThreadPoolExecutor19:36
mriedemyour logging change is sane btw, check out a 24 hour CI run for that log message http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Successfully%20synced%20instances%20from%20host%5C%22%20AND%20tags%3A%5C%22screen-n-sch.txt%5C%22&from=1d19:39
mriedem~16K hits19:39
openstackgerritJay Pipes proposed openstack/nova master: Add columns for generation to consumers  https://review.openstack.org/55795819:55
openstackgerritJay Pipes proposed openstack/nova master: placement: add Project, User and Consumer objects  https://review.openstack.org/56540319:55
openstackgerritJay Pipes proposed openstack/nova master: Add create() methods to Project, User and Consumer  https://review.openstack.org/56540419:55
openstackgerritJay Pipes proposed openstack/nova master: move consumer ensure to API layer  https://review.openstack.org/56540519:55
openstackgerritJay Pipes proposed openstack/nova master: remove Allocation.project_id & Allocation.user_id  https://review.openstack.org/56540619:55
openstackgerritJay Pipes proposed openstack/nova master: rework allocation handler _allocations_dict()  https://review.openstack.org/56540719:55
openstackgerritJay Pipes proposed openstack/nova master: Add a microversion for consumer generation support  https://review.openstack.org/56560419:55
*** dpawlik has joined #openstack-nova19:59
openstackgerritArtom Lifshitz proposed openstack/nova master: WIP: Add InstanceNUMATopology to LibvirtLiveMigrateData  https://review.openstack.org/56639820:01
openstackgerritArtom Lifshitz proposed openstack/nova master: WIP: Add InstanceNUMATopology to LibvirtLiveMigrateData  https://review.openstack.org/56639820:03
*** dpawlik has quit IRC20:04
*** brault has joined #openstack-nova20:07
*** notartom has quit IRC20:09
*** brault has quit IRC20:11
arvindn05mriedem: question on  tests cases within conductor20:15
arvindn05why are we running few tests multiple times? ConductorTaskAPITestCase,ConductorTaskRPCAPITestCase extend from _BaseTaskTestCase and test_compute.BaseTestCase20:17
arvindn0520:17
arvindn05they both run test_unshelve_instance_on_host for example...which is defined under the BaseTaskTestCase. i dont see any differences in the test setup either...20:18
mriedemone hits the rpcapi and one doesn't20:19
*** armaan has quit IRC20:23
arvindn05ahh...noticed the difference in setups now...the difference is very subtle...will add a line comment on top of self.conductor so it draws the difference for future contributors20:23
*** armaan has joined #openstack-nova20:23
arvindn05btw i investigated further on code changes...wanted to confirm something with you20:25
arvindn05mriedem: i would need to add an else condition here as well correct? to handle rebuild with image remaining the samehttps://github.com/openstack/nova/blob/master/nova/conductor/manager.py#L91320:26
*** pchavva has joined #openstack-nova20:26
arvindn05see http://paste.openstack.org/show/720407/ for how i think the code would need to look....let me know if this is not consistent with your idea and i can rework as needed20:29
openstackgerritMatt Riedemann proposed openstack/nova master: Use ThreadPoolExecutor for max_concurrent_live_migrations  https://review.openstack.org/56350520:31
mriedemsuperdan: huzzah ^ that's not too bad20:31
mriedemarvindn05: i said else after the elif here https://github.com/openstack/nova/blob/master/nova/conductor/manager.py#L94320:31
mriedemarvindn05: idk, do we need to re-validate the host/image for rebuild if the image doesn't change?20:31
mriedemi guess that's just to catch a case that the traits on the compute node resource provider changed even though the image didn't?20:32
arvindn05yup...melwitt suggested we use the same approach as imageproperties filter....which i beleive has the same behavior20:32
arvindn05we run even though image hasnt changed20:32
arvindn05i added the else as well @943 see http://paste.openstack.org/show/720407 - line5820:34
*** fishbone_ has quit IRC20:34
arvindn05briefly tested the approach...it works...adding more unit tests20:35
superdanmriedem: looks weird to index by migration uuid instead of instance, is that because of how the cancel migration call works?20:36
*** gbarros has quit IRC20:37
mriedemi think it could go either way, live_migration_abort gets the instance and migration20:37
mriedemkevin just doesn't have that patch up yet20:38
superdanokay I'll make a half-assed comment about it20:39
mriedemquarter cheek friday please20:40
*** mchlumsky has quit IRC20:42
*** fragatina has joined #openstack-nova20:43
*** fragatina has quit IRC20:43
mriedemarvindn05: that's not correct,20:44
mriedemfor rebuild, if the image doesn't change, we don't run through the scheduler, so we don't run the ImagePropertiesFilter20:44
mriedemsee https://github.com/openstack/nova/blob/master/nova/conductor/manager.py#L89820:44
mriedemif host != instance.host: will be False in that block for rebuild20:44
*** fragatina has joined #openstack-nova20:45
mriedemso, idk, that's new validation in the rebuild + same image case, i don't know if we need to revalidate the image in that case, we didn't before, but i also don't really care all that much20:45
*** fragatina has quit IRC20:46
arvindn05ok...i guess it can be handled as part of CR20:46
*** fragatina has joined #openstack-nova20:46
mriedemarvindn05: +2 on the spec amendment20:50
mriedemtime for you to pop a bottle20:50
mriedemof pills20:50
arvindn05awesome...thanks! :)20:50
arvindn05mriedem: see here on melwitt comments http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2018-05-03.log.html#t2018-05-03T20:48:5520:54
arvindn05i think if we are not running imageproperties filter now when image does not change we might want to be consistent...i can raise a bug to state that we dont run image properties filter if image hasnt changed(even though image properties on that image could have changed)20:55
arvindn05and when its fixed...they can fix to handle traits as well....another way is if i just need to call schedule instances for running the image properties filter...i can do that as part of this change20:57
mriedemplease no21:04
mriedemi think if we don't call the scheduler (ImagePropertiesFilter) today, we should just continue to not do the validation21:05
mriedemi.e. image doesn't change21:05
arvindn05sounds like a plan....although a bug might be warranted at that point....21:07
mriedemi don't know that it's a bug21:07
mriedembut it's 4pm on a friday, so i also don't care to think about this right now21:07
arvindn05in case of rebuild with a trait like Trusted host...if the host is no longer trusted we should prevent rebuild...might be a security issue21:07
arvindn05but like you said...its friday...we can figure it out in the CR :)21:08
mriedemis trusted host a standard trait?21:08
arvindn05any plans for the weekend?21:08
mriedemyardwork, mexican food and avoiding little girls21:08
*** burt has quit IRC21:09
mriedemi.e. my daughters annoying friends, not pervy stuff21:09
arvindn05nope....its a custom trait...but traits could be used for security things as well21:09
arvindn05lol....good job with the quick clarification :P21:09
openstackgerritJay Pipes proposed openstack/nova master: rework how we pass candidate request information  https://review.openstack.org/56616621:09
mriedemif an external service says this host is trusted or not and there are instances using an image that requires a trusted host, then i'd expect that external service to migrate those instances before saying it's no longer trusted21:10
mriedemnot waiting for the user to rebuild and find out21:10
mriedemthe instance user is not an admin so they can't see what the traits are on the node RP anyway21:10
arvindn05i guess there are 2 models...there is just a trust attestation piece which does not do any active managment...but more for reporting...another could be with active management like you mentioned21:11
arvindn05anyway...will leave you to enjoy your friday and the weekend :)21:12
*** arvindn05 is now known as arvindn05_away21:12
mriedemi would personally prefer that nova doesn't grow a bunch of side effect code to handle random traits-related what-if kind of conditionals because of the ability of external services to monkey with traits on compute node providers21:12
mriedemand with that, i'm out also, ttyl21:13
*** mriedem is now known as mriedem_yard21:13
arvindn05_awayttyl21:13
*** notartom has joined #openstack-nova21:19
*** dave-mccowan has quit IRC21:19
*** felipemonteiro has quit IRC21:20
*** pchavva has quit IRC21:29
*** awaugama has quit IRC21:29
*** edmondsw has quit IRC21:47
*** itlinux has quit IRC21:47
*** edmondsw has joined #openstack-nova21:47
*** brad[] has quit IRC21:50
*** hamzy_ has joined #openstack-nova21:51
*** edmondsw has quit IRC21:52
*** damien_r has joined #openstack-nova21:53
*** liverpooler has joined #openstack-nova21:54
*** hamzy has quit IRC21:54
*** wolverineav has quit IRC21:54
*** figleaf is now known as edleafe21:54
*** wolverineav has joined #openstack-nova21:55
*** Guest36566 has quit IRC21:57
*** moshele has joined #openstack-nova21:58
*** wolverineav has quit IRC21:59
*** fragatina has quit IRC22:00
*** slaweq has quit IRC22:03
*** moshele has quit IRC22:03
*** moshele has joined #openstack-nova22:04
*** abalutoiu_ has joined #openstack-nova22:08
*** ccamacho has quit IRC22:10
*** abalutoiu__ has quit IRC22:11
*** ccamacho has joined #openstack-nova22:12
*** moshele has quit IRC22:14
*** damien_r has quit IRC22:15
*** evin has quit IRC22:17
*** r-daneel has quit IRC22:21
*** fragatina has joined #openstack-nova22:24
*** markvoelker has quit IRC22:29
*** brad[] has joined #openstack-nova22:34
*** fragatina has quit IRC22:34
*** fragatina has joined #openstack-nova22:35
*** pchavva has joined #openstack-nova22:35
*** liverpooler has quit IRC22:40
*** wolverineav has joined #openstack-nova22:41
*** imacdonn has quit IRC22:42
*** fragatina has quit IRC22:45
*** fragatina has joined #openstack-nova22:45
*** wolverineav has quit IRC22:45
*** wolverineav has joined #openstack-nova22:49
*** linkmark has joined #openstack-nova22:52
*** wolverineav has quit IRC22:53
*** fried_rice is now known as efried22:57
*** hongbin has quit IRC23:01
*** wolverineav has joined #openstack-nova23:03
*** wolverineav has quit IRC23:05
*** wolverineav has joined #openstack-nova23:06
*** wolverineav has quit IRC23:10
*** slaweq has joined #openstack-nova23:11
*** krtaylor has quit IRC23:13
*** fragatina has quit IRC23:14
*** slaweq has quit IRC23:15
*** yamamoto has joined #openstack-nova23:21
*** pchavva has quit IRC23:22
*** wolverineav has joined #openstack-nova23:26
*** yamamoto has quit IRC23:26
*** gjayavelu has quit IRC23:31
*** wolverineav has quit IRC23:31
*** wolverineav has joined #openstack-nova23:34
*** wolverineav has quit IRC23:39
*** wolverineav has joined #openstack-nova23:40
*** wolverineav has quit IRC23:40
*** wolverineav has joined #openstack-nova23:40
*** wolverin_ has joined #openstack-nova23:43
*** wolverineav has quit IRC23:45
*** tbachman has joined #openstack-nova23:45
*** wolverin_ has quit IRC23:57

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