Thursday, 2019-04-18

*** sapd1_x has joined #openstack-nova00:01
*** tiendc has joined #openstack-nova00:03
*** awalende has joined #openstack-nova00:08
*** tetsuro has joined #openstack-nova00:10
*** _erlon_ has quit IRC00:11
*** awalende has quit IRC00:13
*** sapd1_x has quit IRC00:32
*** wxy-xiyuan_ has joined #openstack-nova00:54
*** lxkong_ has joined #openstack-nova00:54
*** TheJulia_ has joined #openstack-nova00:54
*** NobodyCam_ has joined #openstack-nova00:54
*** kmalloc_ has joined #openstack-nova00:54
*** coreycb_ has joined #openstack-nova00:54
*** fyx_ has joined #openstack-nova00:54
*** csatari_ has joined #openstack-nova00:55
*** tinwood_ has joined #openstack-nova00:56
*** mriedem has joined #openstack-nova01:00
*** lchabert_ has joined #openstack-nova01:01
*** yedongcan has joined #openstack-nova01:02
*** NobodyCam has quit IRC01:02
*** kmalloc has quit IRC01:02
*** TheJulia has quit IRC01:02
*** Dinesh_Bhor has quit IRC01:02
*** coreycb has quit IRC01:02
*** csatari has quit IRC01:02
*** fyx has quit IRC01:02
*** lxkong has quit IRC01:02
*** tinwood has quit IRC01:02
*** dannins has quit IRC01:02
*** lchabert has quit IRC01:02
*** jonspw has quit IRC01:02
*** melwitt has quit IRC01:02
*** wxy-xiyuan has quit IRC01:02
*** kmalloc_ is now known as kmalloc01:02
*** NobodyCam_ is now known as NobodyCam01:02
*** lxkong_ is now known as lxkong01:02
*** TheJulia_ is now known as TheJulia01:02
*** lchabert_ is now known as lchabert01:02
*** coreycb_ is now known as coreycb01:02
*** csatari_ is now known as csatari01:02
*** wxy-xiyuan_ is now known as wxy-xiyuan01:02
*** fyx_ is now known as fyx01:02
*** irclogbot_1 has quit IRC01:05
*** ricolin has joined #openstack-nova01:05
*** irclogbot_2 has joined #openstack-nova01:06
*** Dinesh_Bhor has joined #openstack-nova01:08
*** gyee has quit IRC01:20
*** whoami-rajat has joined #openstack-nova01:24
*** melwitt has joined #openstack-nova01:24
*** brinzhang has joined #openstack-nova01:35
*** brinzhang has quit IRC01:36
imacdonnanyone know how to trigger GMR when nova(-api) is running under uWSGI? Seems that uWSGI has its own interpretation of SIGUSR2 :/01:37
*** brinzhang has joined #openstack-nova01:37
*** brinzhang has quit IRC01:38
*** brinzhang has joined #openstack-nova01:39
*** mriedem has quit IRC02:00
*** tkajinam has quit IRC02:15
*** tkajinam has joined #openstack-nova02:19
*** tkajinam has quit IRC02:31
*** itlinux has joined #openstack-nova02:32
*** nicolasbock has quit IRC02:36
*** psachin has joined #openstack-nova03:08
*** cfriesen has quit IRC03:08
*** tbachman has quit IRC03:10
*** brinzhang has quit IRC03:18
*** brinzhang has joined #openstack-nova03:20
openstackgerritya.wang proposed openstack/nova-specs master: Expose auto converge and post copy  https://review.openstack.org/65168103:26
*** wwriverrat has joined #openstack-nova03:27
*** tbachman has joined #openstack-nova03:27
*** itlinux has quit IRC03:32
*** itlinux has joined #openstack-nova03:38
*** tkajinam has joined #openstack-nova03:45
*** lpetrut has joined #openstack-nova03:54
*** imacdonn has quit IRC04:07
*** imacdonn has joined #openstack-nova04:08
*** brinzh has joined #openstack-nova04:09
*** brinzhang has quit IRC04:12
*** lbragstad has quit IRC04:16
*** lpetrut has quit IRC04:17
*** itlinux has quit IRC04:30
*** slaweq has joined #openstack-nova04:45
*** slaweq has quit IRC04:49
*** ratailor has joined #openstack-nova05:01
*** d34dh0r53 has quit IRC05:02
*** dpawlik has joined #openstack-nova05:04
openstackgerritMerged openstack/nova master: Remove 'nova-manage cell' commands  https://review.openstack.org/65129405:12
openstackgerritMerged openstack/nova master: Stop handling cells v1 for console authentication  https://review.openstack.org/65129505:12
*** ivve has joined #openstack-nova05:43
openstackgerritSundar Nadathur proposed openstack/nova master: ksa auth conf and client for cyborg access  https://review.openstack.org/63124205:45
openstackgerritSundar Nadathur proposed openstack/nova master: WIP: Add Cyborg device profile groups to request spec.  https://review.openstack.org/63124305:45
openstackgerritSundar Nadathur proposed openstack/nova master: WIP: Create and bind Cyborg ARQs.  https://review.openstack.org/63124405:45
openstackgerritSundar Nadathur proposed openstack/nova master: WIP: Get resolved Cyborg ARQs and add PCI BDFs to VM's domain XML.  https://review.openstack.org/63124505:45
*** slaweq has joined #openstack-nova05:56
openstackgerritBoxiang Zhu proposed openstack/nova master: Fix live migration break group policy simultaneously  https://review.openstack.org/65196905:58
openstackgerritTakashi NATSUME proposed openstack/nova master: Fix cleaning up console tokens  https://review.openstack.org/63771606:04
*** lpetrut has joined #openstack-nova06:13
*** lpetrut has quit IRC06:14
*** lpetrut has joined #openstack-nova06:15
*** Luzi has joined #openstack-nova06:23
*** lpetrut has quit IRC06:30
openstackgerritSundar Nadathur proposed openstack/nova master: ksa auth conf and client for cyborg access  https://review.openstack.org/63124206:38
openstackgerritSundar Nadathur proposed openstack/nova master: WIP: Add Cyborg device profile groups to request spec.  https://review.openstack.org/63124306:38
openstackgerritSundar Nadathur proposed openstack/nova master: WIP: Create and bind Cyborg ARQs.  https://review.openstack.org/63124406:38
openstackgerritSundar Nadathur proposed openstack/nova master: WIP: Get resolved Cyborg ARQs and add PCI BDFs to VM's domain XML.  https://review.openstack.org/63124506:38
*** awalende has joined #openstack-nova07:10
*** ianw is now known as ianw_pto07:15
*** tesseract has joined #openstack-nova07:16
*** slaweq has quit IRC07:16
*** rpittau|afk is now known as rpittau07:17
*** lpetrut has joined #openstack-nova07:20
*** slaweq has joined #openstack-nova07:28
*** luksky has joined #openstack-nova07:28
openstackgerritBoxiang Zhu proposed openstack/nova master: Add host and hypervisor_hostname flag to create server  https://review.openstack.org/64552007:31
*** pcaruana has joined #openstack-nova07:32
*** helenafm has joined #openstack-nova07:34
*** tosky has joined #openstack-nova07:42
*** tssurya has joined #openstack-nova07:47
openstackgerritHamdy Khader proposed openstack/nova master: Do not perform port update in case of baremetal instance.  https://review.openstack.org/64934508:01
*** awalende has quit IRC08:13
*** awalende has joined #openstack-nova08:13
openstackgerritTakashi NATSUME proposed openstack/python-novaclient master: Fix a description for config_drive parameter  https://review.openstack.org/65368308:15
*** ralonsoh has joined #openstack-nova08:16
*** takashin has left #openstack-nova08:17
*** dtantsur|afk is now known as dtantsur08:25
*** dpawlik has quit IRC08:27
*** dpawlik has joined #openstack-nova08:27
*** awalende has quit IRC08:29
*** awalende has joined #openstack-nova08:30
*** tkajinam has quit IRC08:32
*** ttsiouts has joined #openstack-nova08:45
*** luksky has quit IRC08:59
*** mkarpiarz has joined #openstack-nova09:01
openstackgerritSurya Seetharaman proposed openstack/nova master: [WIP] Support adding the reason behind a server lock  https://review.openstack.org/64866209:04
openstackgerritSurya Seetharaman proposed openstack/nova master: Plumbing for locking an instance with reason  https://review.openstack.org/65369109:04
*** tssurya has quit IRC09:05
*** tssurya has joined #openstack-nova09:05
*** lpetrut has quit IRC09:10
*** markvoelker has joined #openstack-nova09:11
openstackgerritBoxiang Zhu proposed openstack/nova master: Make evacuation respects anti-affinity rule  https://review.openstack.org/64996309:14
*** plestang has joined #openstack-nova09:15
openstackgerritBoxiang Zhu proposed openstack/nova master: Fix live migration break group policy simultaneously  https://review.openstack.org/65196909:16
plestangHi all!09:19
plestangI have a question regarding nova-conductor09:19
plestangregurlarly compute hosts are requesting for unconfirmed migration by dest compute09:20
*** alex_xu has quit IRC09:20
plestangThe function called is here: https://github.com/openstack/nova/blob/03322bb517925a9f5a04ebdb41c3fd31e7962440/nova/db/sqlalchemy/api.py#L431309:21
plestangthe read_deleted params is set to yes09:21
plestangin model_query09:21
plestangit generates some load on our infra09:21
plestangbecause we have around 300000 lines in that table09:22
plestangso all compute hosts of our infra reads regularly all the database09:22
plestangwhen I explain the request09:24
plestang+------+---------------+------------+--------+-----------------+--------+-----------+--------+--------+-------------+09:25
plestang|   id | select_type   | table      | type   |   possible_keys |    key |   key_len |    ref |   rows | Extra       |09:25
plestang|------+---------------+------------+--------+-----------------+--------+-----------+--------+--------+-------------|09:25
plestang|    1 | SIMPLE        | migrations | ALL    |          <null> | <null> |    <null> | <null> | 261177 | Using where |09:25
plestang+------+---------------+------------+--------+-----------------+--------+-----------+--------+--------+-------------+09:25
*** boxiang has quit IRC09:25
plestangI was asking if it were a good idea to set the read_deleted to no instead of yes09:25
*** boxiang has joined #openstack-nova09:26
plestangit would make the MariaDB query plan use one of the index that use the delete column09:26
*** ratailor_ has joined #openstack-nova09:27
plestangif I add "and deleted=0" the query plan becomes09:27
plestang+------+---------------+------------+--------+---------------------------------------------------------------------------------+-----------------------------------------+-----------+-------+--------+------------------------------------+09:27
plestang|   id | select_type   | table      | type   | possible_keys                                                                   | key                                     |   key_len | ref   |   rows | Extra                              |09:27
plestang|------+---------------+------------+--------+---------------------------------------------------------------------------------+-----------------------------------------+-----------+-------+--------+------------------------------------|09:27
plestang|    1 | SIMPLE        | migrations | ref    | migrations_by_host_nodes_and_status_idx,migrations_instance_uuid_and_status_idx | migrations_instance_uuid_and_status_idx |         5 | const |  23610 | Using index condition; Using where |09:28
plestang+------+---------------+------------+--------+---------------------------------------------------------------------------------+-----------------------------------------+-----------+-------+--------+------------------------------------+09:28
plestangin other word the question is what is the idea behind requesting finished migration in deleted status for compute host09:28
*** ratailor has quit IRC09:29
*** alex_xu has joined #openstack-nova09:31
*** luksky has joined #openstack-nova09:41
*** markvoelker has quit IRC09:41
*** ttsiouts has quit IRC09:51
*** ttsiouts has joined #openstack-nova09:53
*** lpetrut has joined #openstack-nova09:54
*** luksky has quit IRC09:57
*** brinzh has quit IRC10:07
*** ttsiouts has quit IRC10:09
*** ttsiouts has joined #openstack-nova10:10
*** Luzi has quit IRC10:28
*** ttx has quit IRC10:31
*** ttx has joined #openstack-nova10:31
*** bbowen has quit IRC10:33
aspiersplestang: you might have more luck when the Americans come online10:35
aspierskashyap: any thoughts on how to split the getDomainCapabilities() patch up?10:35
kashyapaspiers: Hiya, I want to spend some careful time on it10:35
*** nicolasbock has joined #openstack-nova10:35
kashyapaspiers: Right now, I'm chugging through a few things that I "need" to finish10:35
aspiersI guess I could manufacture something to test which isn't ever used in the real world10:36
kashyapaspiers: Rest assured, since I have a "vested interest" in it10:36
aspiersOK np10:36
aspiersSure, I noticed ;-)10:36
kashyapHehe10:36
aspiersIn the mean time I guess I can rebase at least10:36
kashyapLet me quickly re-read it, actually10:36
aspiersNeed to fix the merge conflicts10:36
*** pcaruana has quit IRC10:36
*** markvoelker has joined #openstack-nova10:38
*** ratailor__ has joined #openstack-nova10:41
*** luksky has joined #openstack-nova10:42
*** ratailor_ has quit IRC10:44
*** tbachman has quit IRC10:47
openstackgerritIvaylo Mitev proposed openstack/nova master: VMware: Attach volumes using adapter type from instance  https://review.openstack.org/61659910:47
stephenfindansmith: When you're about, this is probably worth you looking at https://review.openstack.org/#/c/651296/10:51
*** pcaruana has joined #openstack-nova10:58
openstackgerritStephen Finucane proposed openstack/nova master: tests: autospecs all the mock.patch usages  https://review.openstack.org/47077511:00
openstackgerritStephen Finucane proposed openstack/nova master: hyper-v: autospec classes before they are instantiated  https://review.openstack.org/34221111:00
*** erlon has joined #openstack-nova11:06
*** zigo has joined #openstack-nova11:07
*** cdent has joined #openstack-nova11:09
*** markvoelker has quit IRC11:11
*** slaweq is now known as slaweq|lunch11:15
kashyapaspiers: Responded on the change.  I can understand if my response is not fully satisfying...11:16
* kashyap --> lunch11:16
aspierskashyap: thanks!11:17
kashyapFirst see if I make sense :-)  Free to correct me if I didn't consider something else.11:17
aspierssure11:19
* aspiers gets lunch too11:19
*** eharney has quit IRC11:25
*** panda is now known as panda|lunch11:26
*** sapd1_x has joined #openstack-nova11:27
*** slaweq|lunch is now known as slaweq11:33
*** yedongcan has left #openstack-nova11:34
*** bbowen has joined #openstack-nova11:35
*** erlon has quit IRC11:37
openstackgerritHamdy Khader proposed openstack/nova master: Do not perform port update in case of baremetal instance.  https://review.openstack.org/64934511:41
*** ttsiouts has quit IRC11:59
plestangaspiers: ok thx waiting a couple of hours12:05
*** plestang has quit IRC12:06
*** plestang has joined #openstack-nova12:08
*** markvoelker has joined #openstack-nova12:08
*** ttsiouts has joined #openstack-nova12:09
*** ttsiouts has quit IRC12:12
*** ttsiouts_ has joined #openstack-nova12:12
openstackgerritLee Yarwood proposed openstack/nova master: fixtures: Return a mocked class instead of method within fake_imagebackend  https://review.openstack.org/61980412:12
*** cdent has quit IRC12:15
*** johnthetubaguy has joined #openstack-nova12:16
*** lbragstad has joined #openstack-nova12:18
*** tbachman has joined #openstack-nova12:33
*** ratailor__ has quit IRC12:38
*** lbragstad has quit IRC12:40
*** markvoelker has quit IRC12:41
openstackgerritSylvain Bauza proposed openstack/nova-specs master: Proposes NUMA affinity for vGPUs  https://review.openstack.org/65096312:43
bauzasdansmith: efried: thanks for commenting the vGPU affinity spec, I made it way simplier ^12:44
bauzasefried: about your comment on the new field name, I just wanted to make this field as arbitrary as possible, since other features could want to affinitize it too (think of... network ports :) heh gibi)12:45
*** eharney has joined #openstack-nova12:49
*** tetsuro has quit IRC12:52
*** tiendc has quit IRC12:52
*** sapd1_x has quit IRC12:57
*** jdillaman has joined #openstack-nova13:00
efriedbauzas: But you're already calling it "devices". The part that makes it clearer is the "rp_uuids" bit. Otherwise the only thing you have to go on is the fact that it's a UUIDField. Are you saying it could include UUIDs *other* than RP UUIDs? How would the code know which is which??13:02
bauzasok, we can call it rp_uuids if so13:03
bauzasor related_rp_uuids13:03
bauzasFWIW, I'm very bad at naming things but my children13:03
sean-k-mooneybauzas: ya i think rp_uuids is good13:03
sean-k-mooney-1 to related_rp_uuids13:03
sean-k-mooneytoo much typeing13:03
openstackgerritSylvain Bauza proposed openstack/nova-specs master: Proposes NUMA affinity for vGPUs  https://review.openstack.org/65096313:05
bauzassean-k-mooney: efried: my pleasure ^13:05
efriedbauzas: So now does it include the UUID of the NUMA cell RP?13:06
sean-k-mooneyno13:06
*** ttsiouts_ has quit IRC13:06
sean-k-mooneymaybe child_rps  woould be better...13:07
sean-k-mooneyactully it could13:07
efriedYeah, good idea, child_rp_uuids13:07
sean-k-mooneywe coudl do it either way13:07
sean-k-mooneyif it doen not include it we shoudl have a field for the numa node RP13:08
efriedI don't love including the NUMA cell RP UUID, because how would you tell which one that is. But yes, this ^13:08
sean-k-mooneybut this spec does not depend on have numa nodes as RPs in placment13:08
efriedthen make the field nullable13:08
efriedor set it to the compute RP UUID.13:09
efriedum, not that second thing - because there can still be more than one, eh?13:09
sean-k-mooneyso in this spec i think have it as just child_rp_uuids makes sense13:10
sean-k-mooneyand if we also do the numa in placement spec add a rp_uuid filed for the numa node RP13:10
*** pcaruana has quit IRC13:10
efriedSo summarizing:13:11
efried- Add rp_uuid (the UUID of the NUMA cell) as a nullable UUIDField, only set if the NUMA cell is represented as a nested RP13:11
efried- Name the new ListOfUUIDField `child_rp_uuids` and it includes all & only UUIDs of child RPs like PGPUs, NICs, etc.13:11
sean-k-mooney+113:12
sean-k-mooneybauzas: what do you think ^13:12
*** ttsiouts has joined #openstack-nova13:13
* bauzas shrugs13:13
bauzasefried: I don't want the vGPU affinity spec to tell about any NUMA node being a nested RP13:14
bauzasit's a different spec13:14
bauzasfor the moment, pGPUs are a specific RP, sure, but NUMA nodes are just using the root RP13:14
sean-k-mooneybauzas: well you could leave adding the the nullable rp_uuid fiedl to the other spec13:15
bauzassean-k-mooney: maybe, I'm not sure we need it13:15
openstackgerritSylvain Bauza proposed openstack/nova-specs master: Proposes NUMA affinity for vGPUs  https://review.openstack.org/65096313:16
bauzasbikeshed update ^13:16
sean-k-mooney:) that looks fine too me13:17
sean-k-mooneythe other thing i wanted to point out is if we did not have the numa-as-nested-rp spec then this is enought to do numa with placement in general13:17
efriedmdbooth: https://bugs.launchpad.net/nova/+bug/1823251 <== have you had a chance to look into this? (weird db race brought up two nova meetings ago)13:18
openstackLaunchpad bug 1823251 in OpenStack Compute (nova) "Spike in TestNovaMigrationsMySQL.test_walk_versions/test_innodb_tables failures since April 1 2019 on limestone-regionone" [High,Confirmed]13:18
sean-k-mooneytake sriov as an example if we just model the pfs as RPs of the compute node and add the rps to the child_rp_uuids then it will work13:18
sean-k-mooneywell we will need to do a few tweeks but the datamdoel will support it13:19
sean-k-mooneyso if we dont make progress on the richer query syntax this cycle then we can atleast model the capasity with placement and use the numa toplogy filter to track the numa locality13:20
efriedsean-k-mooney: Can you give me a rundown of the reviews you have open for CI-ish stuff?13:21
efriedIs it just this one https://review.openstack.org/#/c/652197/ ?13:22
sean-k-mooneythat is the main one13:22
*** dpawlik has quit IRC13:22
efriedcan I call on you in the nova meeting to give a brief summary of that effort?13:22
sean-k-mooneyam sure13:23
sean-k-mooneyi plan to allso add a tempest-dpdk job13:23
sean-k-mooneyand i might work with the ovn folk to create a tempest-dpdk-ovn job after13:23
sean-k-mooneyi have a dpdk job in my thirdparty ci just need to port it13:24
*** mriedem has joined #openstack-nova13:24
efriedcool. You can say all of that again for the crowd :)13:24
sean-k-mooneyhehe yes we have a topic at the ptg too13:24
sean-k-mooneythere are related things to talk about but ill give a summary in the meeting13:24
openstackgerritya.wang proposed openstack/nova-specs master: Expose auto converge and post copy  https://review.openstack.org/65168113:25
efriedmriedem: https://review.openstack.org/#/q/project:openstack/nova+branch:stable/pike+topic:bug/1669054 merged, are we ready to update the pike-em patches and make them go or are we waiting for other things?13:26
*** mchlumsky has joined #openstack-nova13:26
*** awaugama has joined #openstack-nova13:27
efriedhttps://review.openstack.org/#/c/613263/ ?13:27
mriedemi personally don't think we need that change, it was only noticed on newer branches related to some other changes in the RT which aren't backported to queens, not sure why rado is backporting it to pike13:28
mriedemmel wants https://review.openstack.org/#/c/653514/13:28
mriedemdansmith: this is quite old and we talked about this fix at the last ptg in denver - would be nice to flush it https://review.openstack.org/#/c/581912/13:29
mriedemefried: so yeah there are still more changes we want in pike13:29
mriedemi'm working on it13:29
mriedemi might just start approving things13:30
*** lbragstad has joined #openstack-nova13:30
efriedmriedem: ack; should we make a pike-em-potential etherpad or something, or is it okay for this to be all in your head?13:30
efriedmmedvede: I've noticed http://ciwatch.mmedvede.net/project?project=nova&time=7+days is a little wonky lately, some rows seem to be duplicated, are you aware?13:31
mriedemefried: i can do that - one might already exist13:31
efriedthanks13:32
mriedemelod: did you create a pike-em potential etherpad for each project?13:32
mriedemor one that was tracking all projects/13:32
mriedem?13:32
mriedemah yes https://etherpad.openstack.org/p/pike-final-release-before-em13:32
mriedemhttps://etherpad.openstack.org/p/nova-stable-pike-em13:32
*** pcaruana has joined #openstack-nova13:32
dansmithmriedem: hmm, that im=None isn't used huh?13:34
openstackgerritIvaylo Mitev proposed openstack/nova master: VMware VMDK detach: get adapter type from instance VM  https://review.openstack.org/65373813:34
mriedemdansmith: been awhile but the logic i think is if we have the api db and get the not found, we should raise b/c that shouldn't happen. if we don't have the api db configured, we assume we're in the cell conductor and we don't need to target the context anyway.13:36
mriedemthe latter is the devstack case, the former is like everyone else in real life right now13:37
dansmithmriedem: okay I'm not sure I follow that, but also not sure that's what is here13:37
dansmithnot found does not raise13:37
gibibauzas: I left a question about the GPU weigher in https://review.openstack.org/#/c/65096313:37
mriedemsorry not the not found, the CantStartEngineError13:38
*** markvoelker has joined #openstack-nova13:38
dansmithmriedem: right, I get that logic, I'm just talking about the line you removed13:38
mriedemif we're in the cell conductor with no api db config, like devstack, reschedules will fail b/c of CantStartEngineError13:38
mriedemthat's dead code13:38
dansmithmriedem: the im=None, but I don't know why that was there in the first place13:38
mriedemit's dead, my ide shows it as dead so i removed it most likely13:38
dansmith"my ide made me do it".. jesus, these kids.13:39
*** jmlowe has quit IRC13:39
mriedem"my text based terminal editor doesn't show me fun stuff like this" jesus these oldies13:40
mriedem<313:40
dansmithheh13:41
bauzasgibi: ack, will look13:42
*** markvoelker has quit IRC13:42
*** lbragstad has quit IRC13:43
*** lbragstad has joined #openstack-nova13:46
gibimriedem, dansmith: about the https://review.openstack.org/#/c/652608/4/specs/train/approved/server-move-operations-with-ports-having-resource-request.rst@190 do you have a feeling which one is easier: 1) implement multiple portbinding usage for every server move operation 2) pass around the RequestSpec in the compute RPC API?13:51
mriedemi'm not sure i understand the question13:52
mriedemyou need the request spec in methods like unshelve to do the port binding in the networking api methods properly right?13:52
mriedemoh,13:53
mriedemyou mean change all move ops to do the port binding stuff that live migration does?13:53
gibimriedem: cannot set up the portbinding in the conductor for unshelve?13:53
mriedemi'd think you'd still have behavioral changes in the compute if you did that13:54
gibimriedem: yeah, do multiple portbinding in the conducotr for every move operation then the binding is created in the conductor13:54
mriedemit's really hard for me to say without it being poc'ed first13:54
gibimriedem: true, we anyhow need a behavior change in the compute either due to the requestspec or due to the multiple portbinding13:54
mriedemfor live migration we create the port bindings in the conductor but there were changes in the compute to use those port bindings if they existed13:54
gibimriedem: yes13:54
mriedemchanging the compute rpc api interface is much more straightforward to me13:55
gibimriedem: OK that is the kind of input I'm looking for as for me both is blackbox now13:55
gibimriedem: thanks13:55
*** sapd1 has joined #openstack-nova13:56
mriedemif you haven't heard, there is some weird issue sean-k-mooney is working on with the port binding live migratoin stuff too, so until the root cause of that is figured out i'd be nervous about switching everything over13:56
gibimriedem: yeah I saw that weirdness too13:56
*** takashin has joined #openstack-nova13:57
efriedNova meeting real soon in #openstack-meeting13:58
kashyap(Sigh, conflicting call)13:59
openstackgerritsean mooney proposed openstack/nova master: [WIP] Libvirt: add nfv job  https://review.openstack.org/65219714:00
sean-k-mooneyi still have the other gate jobs disabled in ^ but if its clean ill uncomment them and drop the [WIP]14:00
*** cfriesen has joined #openstack-nova14:01
sean-k-mooney... i have that emacs adds tabs...14:01
efriedjust reprogram it14:03
efriedhow's yer lisp?14:03
openstackgerritsean mooney proposed openstack/nova master: [WIP] Libvirt: add nfv job  https://review.openstack.org/65219714:04
mdboothefried: Sorry, I did not in the end. I had good intentions :/14:10
*** lpetrut has quit IRC14:10
*** cdent has joined #openstack-nova14:10
efriedmdbooth: Okay. Should I keep you associated with it on my radar or no?14:10
mriedemgibi: replied to the rest of your comments in your spec https://review.openstack.org/#/c/652608/ - question inline about why can't we heal the missing port allocatoins during the _heal_instance_info_cache periodic?14:11
gibimriedem: ack14:11
mdboothefried: Given how the next 2-3 weeks looks, it would probably be best not to.14:11
efriedmdbooth: okay, thanks.14:12
*** tinwood_ is now known as tinwood14:14
*** vishakha has joined #openstack-nova14:15
*** jaosorior has quit IRC14:15
mriedemsean-k-mooney: can you split the 3rd party NFV / HPC / etc CI testing section out of https://etherpad.openstack.org/p/nova-ptg-train into another etherpad, because it's getting really big in the main one14:17
mriedem~L9914:17
openstackgerritGhanshyam Mann proposed openstack/nova-specs master: Spec for API inconsistency cleanup  https://review.openstack.org/60396914:18
sean-k-mooneymriedem: yes ill do that and update it with a link14:19
mriedemthanks14:20
*** awalende has quit IRC14:20
*** awalende has joined #openstack-nova14:21
*** awalende_ has joined #openstack-nova14:24
*** awalende has quit IRC14:25
*** markvoelker has joined #openstack-nova14:26
*** awalende_ has quit IRC14:29
*** samueldmq has joined #openstack-nova14:29
*** ricolin has quit IRC14:32
kashyapmriedem: I was _just_ about to say that; to split out that giant CI JSON bits away from the main Etherpa14:32
*** jmlowe has joined #openstack-nova14:34
*** mlavalle has joined #openstack-nova14:35
*** florius has joined #openstack-nova14:41
*** ttsiouts has quit IRC14:44
*** tbachman has quit IRC14:44
*** ttsiouts has joined #openstack-nova14:44
*** awalende has joined #openstack-nova14:48
kashyapcfriesen: Heya, mind having a gander at this Secure Boot spec: https://review.openstack.org/#/c/50672014:49
openstackgerritMatt Riedemann proposed openstack/nova stable/pike: Add missing libvirt exception during device detach  https://review.openstack.org/65164214:49
kashyapmriedem: Heh, I was referring to this (Hyper-V) commit of yours & Claudiu: http://git.openstack.org/cgit/openstack/nova/commit/?h=master&id=29dab99714:50
kashyapThe stuff I'm adding in the spec is similar, but for the open source hypervisor14:51
mriedemkashyap: don't confuse me as the author there, that was probably due to a bad rebase which changed the author14:52
mriedemi was likely just helping to clean up nits to get it approved14:52
kashyapYeah, I know Claudiu was driving it14:52
*** awalende has quit IRC14:52
mriedemcdent: if you have hooks to rado, can you ask if we really need this in pike? https://review.openstack.org/#/c/613263/14:54
cdenti can probalby find him, yeah14:54
sean-k-mooneymriedem: by the way for NewBruce RDO -> OSA bug. they tested my backported fix last night and it worked at least for the test instnace.14:55
mriedemsean-k-mooney: i need to read your commit message to figure out what the problem was14:56
mriedemor we don't know what the problem was, but this works around it14:56
mriedemi'm also doing about 10 other things atm14:56
sean-k-mooneyso we know what the problem is and this works fixes it but i still dont know what teh cause is. im going to try and figure out a reporducer14:56
elodmriedem: only that have stable-policy-follows tag14:57
cdentmriedem: i've pinged him, but based on a cursory examination I think your analysis is correct. If we don't hear anything from him, probably safe to kill/ignore14:57
sean-k-mooneymriedem: no worries i just wanted to say im going to be away for a few days due to pulic holidays but ill try to get back to working on it before the ptg14:57
mriedemcdent: cool thanks14:58
elodmriedem: did i miss something?14:58
mriedemi'm glad you dropped the b rather than l in 'public'14:58
mriedemelod: no i'm just trying to organize the nova pike-em work14:58
mriedemusing https://etherpad.openstack.org/p/nova-stable-pike-em14:58
sean-k-mooney:) yes so am i14:59
elodmriedem: ok, is see. actually the pads are quite out-of-date, maybe i should update them15:00
gibimriedem: replied in https://review.openstack.org/#/c/652608/ but I have to disappear now15:00
elodmriedem: i see that you updated nova's etherpad already15:00
*** gibi is now known as gibi_off15:01
*** takashin has left #openstack-nova15:01
*** ratailor has joined #openstack-nova15:01
*** _erlon_ has joined #openstack-nova15:02
mriedemelod: yeah i'm working on onva's15:04
mriedem*nova's15:04
mriedemcdent: i left some more details about why maybe that patch would still be good for vcenter but i'm not sure - maybe only in the 1:M host:node case but i thought we stopped doing that with vcenter back in like kilo or liberty - long before you had to care about it :)15:08
mriedemtl;dr i think we can drop it15:08
cdentmriedem: in addition to all that, from a vio/vmware standpoint, pike doesn't really matter any more15:14
mriedemheh that was my other guess15:15
*** florius has quit IRC15:16
*** cdent has quit IRC15:18
cfriesenkashyap: it looks like centos 7.6 has modified the OVMF-20180508-3 rpm to no longer contain the file /usr/share/OVMF/OVMF_CODE.fd that nova looks for in nova/virt/libvirt/driver.py.  Instead it now seems to be named /usr/share/OVMF/OVMF_CODE.secboot.fd15:25
kashyapcfriesen: I think it is following just RHEL.15:25
kashyapcfriesen: It's a good step: because it keeps things simpler15:25
cfriesenlikely...but either way nova has an issue15:25
kashyapcfriesen: Because we hardcode the file15:26
kashyapI know15:26
kashyapThat will go away.  We will use the convenient formal interfaces provided by libvirt and QEMU15:26
cfriesenis anyone planning on making it a config option or something?15:26
cfriesenah15:26
kashyapcfriesen: They've _vastly_ simplified it.15:26
kashyapIt took more than one year (necessarily so) to get all the work done across EDK2/OVMF, QEMU, libvirt merged15:27
kashyapcfriesen: Since I've see you on #qemu, OFTC.  I know you're comfortable with looking at some QEMU docs, let me point you to somethin15:27
*** ttsiouts has quit IRC15:27
cfriesenkashyap: you started this in 2017?  yikes. :)15:28
kashyapcfriesen: The firmware.json file, and specifically read the "@Firmware:" bit: https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json#l29715:28
kashyapcfriesen: Yes!  I've posted periodic updates.  :-)  Because work needs to be done in QEMU15:28
kashyapcfriesen: The main work started with this RFC I posted to 'qemu-devel':15:29
*** ttsiouts has joined #openstack-nova15:29
kashyaphttps://lists.nongnu.org/archive/html/qemu-devel/2018-03/msg01978.html15:29
kashyap"[RFC] Defining firmware (OVMF, et al) metadata format & file"15:29
cfriesenfor some reason it's taking forever to open that link15:29
kashyapcfriesen: Which one?  The git.qemu.org?  Strange.  Since you have the repo locally, look at it15:30
openstackgerritAdam Spiers proposed openstack/nova-specs master: Re-approve AMD SEV support for Train  https://review.openstack.org/64199415:30
kashyapcfriesen: See the "Work Items" section in the spec.  I've spent a lot of time tring to be as clear as I can15:30
*** pcaruana has quit IRC15:31
kashyapcfriesen: Note, I had to pause the spec for a year, because the main libvirt bits (firmware auto-selection) merged in 5.2, which released earlier this week :-)15:31
mriedemmelwitt: your rocky/queens/pike backports for https://review.openstack.org/#/q/Iefab05e84ccc0bf8f15bdbbf515a290d282dbc5d are all failing unit tests for a real issue15:33
openstackgerritAdam Spiers proposed openstack/nova-specs master: Re-approve AMD SEV support for Train  https://review.openstack.org/64199415:33
melwittmriedem: yeah, I saw zuul -1s and concerned it's real but I haven't dug in yet15:34
cfriesenkashyap: just read the @Firmware section.  that looks useful.  do any distros support it yet?15:34
kashyapcfriesen: Very good question.15:35
kashyapcfriesen: The firmware.json file is supported by current QEMU versions.  But, they went one step ahead, and also provided the firmware descriptor files15:35
mriedembauzas: dansmith: can you hit these backports? https://review.openstack.org/#/q/topic:bug/1819963+(status:open+OR+status:merged)+branch:stable/queens15:36
kashyapcfriesen: That thing will be in QEMU 4.1 (July/August).  Should be ready for Train15:36
aspiersefried: latest patch set of SEV spec is fully converted to the resource class approach https://review.openstack.org/#/c/641994/915:36
bauzasmriedem: on a meeting (again) but sure, will look15:36
mriedemlyarwood: melwitt: want to hit this backport? https://review.openstack.org/#/c/647630/15:36
openstackgerritBoxiang Zhu proposed openstack/nova master: Add host and hypervisor_hostname flag to create server  https://review.openstack.org/64552015:36
efriedaspiers: Cool. Did you get feedback from other stakeholders on that approach before you did that?15:37
*** helenafm has quit IRC15:37
kashyapcfriesen: Look at this one, which has the documentation: https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01558.html15:37
melwittmriedem: queued15:37
efriedaspiers: (once again, I'm not caught up)15:37
kashyapcfriesen: Those files will be part of QEMU 4.1, which will be shipped by distros Real Soon Now.15:37
* kashyap bbiab; "meeting"15:37
aspiersefried: Not yet, but I can't actually imagine how else we could solve the guest limit problem, so any other version of the spec proposal would be incomplete or dishonest right now15:37
aspiersefried: and there's always git if I need to revert bits ;-)15:38
dansmithmriedem: yeah15:38
efriedaspiers: fair enough.15:38
mriedemdansmith: thanks15:38
*** gyee has joined #openstack-nova15:38
aspierskashyap: finally reading your comments15:38
mriedemneed a stable core on https://review.openstack.org/#/c/647913/ as well15:39
mriedemsmcginnis: tonyb[m]: ^?15:39
smcginnisLooking15:40
aspierskashyap: sounds reasonable, I'll take a stab at splitting up shortly15:41
aspiersgoing out for a run in the sun first though :)15:41
kashyapaspiers: Ah, good.  I was briefly worrying if I missed to consider anything else15:41
kashyapaspiers: Go for it; more important.  Damn screens can cait.15:41
kashyaps/cait/wait/15:41
aspiers;-)15:41
efriedmdbooth, lyarwood: Thoughts on how long https://etherpad.openstack.org/p/ptg-train-xproj-nova-cinder should take?15:41
efriedbe conservative, please.15:41
cfriesenSo as I mentioned to Kashyap, I think we've got an issue with UEFI boot on recent CentOS/RHEL.  https://bugs.launchpad.net/nova/+bug/182538615:42
openstackLaunchpad bug 1825386 in OpenStack Compute (nova) "nova is looking for OVMF file no longer provided by latest CentOS" [Undecided,New]15:42
smcginnisI think in the past we've always done half a day, but there's not as many in-flight nova-cinder things at the moment.15:43
kashyapcfriesen: An ugly workaround is to symlink the file name15:43
cfriesenkashyap: all sorts of possible workarounds, but I'm assuming we want nova to work out of the box.15:43
mdboothefried: Depends. If it branches into a separate discussion of 'internal apis' it could take a long time.15:44
efriedsmcginnis: Half a day? I've remembered an hour or two over the past three PTGs or so, never half a day. In any case, a) there's one small-looking topic on that list, and b) very compressed time.15:44
efriedmdbooth: See b) above. We've got to time box it.15:44
efriedgiven that, what do you think, an hour?15:45
mdboothefried: Purely api definition and discussion, 30-60 mins.15:45
efriedokay, thanks.15:45
aspiersYikes, SEV is the second largest nova spec to date15:45
efriedaspiers: what's the largest?15:46
aspiersspecs/newton/implemented/generic-resource-pools.rst15:46
efriedphew. I thought it was going to be one of mine15:46
aspiersXD15:46
elodmriedem: meanwhile i've generated the unreleased Changes between 16.1.7 and 9191083, so i can paste it to etherpad if you need15:46
efriedmaybe would have been if dansmith hadn't red-penned it15:46
*** luksky has quit IRC15:46
aspiersWell surely SEV has to be up there in the red-pen stakes X-D15:47
*** ivve has quit IRC15:48
smcginnisefried: Maybe it just felt like half a day. :)15:48
kashyapcfriesen: Oh, yes!15:48
kashyapcfriesen: Please read the spec.  All that hard-coding in Nova is fugly, and will go15:48
cfriesenkashyap: reading it now.  I think we should fix (or at least bandaid) nova in the meantime.15:49
cfriesenkashyap: so is /usr/share/OVMF/OVMF_CODE.secboot.fd a superset of /usr/share/OVMF/OVMF_CODE.fd ?  I haven't gone digging yet.15:50
kashyapcfriesen: I would not the word "superset", but they are two distinct things15:51
kashyapcfriesen: The binary: /usr/share/OVMF/OVMF_CODE.secboot.fd -- has Secure Boot + SMM built into it15:51
*** plestang has quit IRC15:51
kashyapcfriesen: While the "plain" /usr/share/OVMF/OVMF_CODE.secboot.fd -- does *not* have Secure Boot ability baked into it at buld time15:52
kashyapcfriesen: Can add a band-aid to look for this file, too.  In addition to what Nova already looks15:52
cfriesenkashyap: I think we've also got to deal with https://bugs.launchpad.net/nova/+bug/1633447 and https://bugs.launchpad.net/nova/+bug/1785123 before secure boot is really useful, right?15:54
openstackLaunchpad bug 1633447 in OpenStack Compute (nova) "nova stop/start or reboot --hard resets uefi nvram" [Undecided,In progress] - Assigned to Jack Ding (jackding)15:54
openstackLaunchpad bug 1785123 in OpenStack Compute (nova) "UEFI NVRAM lost on cold migration or resize" [Low,In progress] - Assigned to Jack Ding (jackding)15:54
kashyapcfriesen: I've had a cursory look, but needs more concentration; for tomm / Tuesday (Mon is a holiday).15:55
openstackgerritmelanie witt proposed openstack/nova stable/rocky: libvirt: set device address tag only if setting disk unit  https://review.openstack.org/65351115:57
cfriesenI'm off most of next week, so don't expect quick response if you leave review comments.  (I'm mostly taking over for jackding.)15:57
kashyap(Nod)15:58
*** ttsiouts has quit IRC16:00
openstackgerritmelanie witt proposed openstack/nova stable/queens: libvirt: set device address tag only if setting disk unit  https://review.openstack.org/65351216:04
mriedemefried: https://etherpad.openstack.org/p/nova-stable-pike-em is up to date16:04
efriedthanks mriedem16:05
*** ratailor has quit IRC16:05
mriedemtl;dr novaclient is ready for final release, no open changes,16:05
mriedemos-vif has no open changes nor any changes since the last release, so it's ready for em16:05
mriedemnova has 6 pending16:06
efriedtonyb[m]: ^ FYI16:09
openstackgerritmelanie witt proposed openstack/nova stable/pike: libvirt: set device address tag only if setting disk unit  https://review.openstack.org/65351416:09
lyarwoodefried / mdbooth ; sorry was stuck on a call, I'd say 30mins to be conservative16:10
*** tesseract has quit IRC16:10
efriedlyarwood: Cool, we've set it up for 1115-115016:10
efriedif really needed we can come back after team picture and go til lunch16:11
*** panda|lunch is now known as panda16:11
lyarwoodefried: ack thanks16:13
*** tssurya has quit IRC16:14
*** cdent has joined #openstack-nova16:14
cfriesenkashyap: what happens if you have running instances using  /usr/share/OVMF/OVMF_CODE.fd, then you shut down the node, upgrade the OVMF RPM, and boot the node.  Are the instances all toast?16:16
kashyapcfriesen: Have not tested it; but I'd expect some error.  I don't think instance will be "toast".  Because it's "only" the firmware.16:17
cfriesenbut we wouldn't be able to boot it, as the xml would be specifying the "wrong" file16:18
kashyapcfriesen: Can you try on one instance, by doing the fugly workaround of:16:18
kashyap    ln -sf /usr/share/OVMF/OVMF_CODE.secboot.fd /usr/share/OVMF/OVMF_CODE.fd16:18
kashyapDoes it boot, if you do the above?16:18
cfriesenI don't have a suitable setup at the moment.16:18
kashyapcfriesen: But yes -- obviously, instance won't boot if the file is missing16:20
*** wwriverrat has quit IRC16:20
cfriesenI'm wondering why RHEL/Centos didn't include both OVMF_CODE.fd and OVMF_CODE.secboot.fd in the RPM16:20
gmannmriedem: fixed all formatting and scheduler_hints -  https://review.openstack.org/#/c/603969/16:20
cfriesenkashyap: oooh, interesting.  the fedora package has both16:22
kashyapcfriesen: Yes16:22
kashyapcfriesen: This whole OVMF binary file names across distributions is a cluster fuck sized Jupiter16:22
kashyapcfriesen: But ... good news!16:22
kashyapcfriesen: That's why upstream QEMU we introduced a formal *schema* (the @Firmware thing you read)16:22
kashyapcfriesen: Because the firmware paths and names differ _across_ distros.   E.g. see this on Ubuntu: https://packages.ubuntu.com/disco/all/ovmf/filelist16:23
kashyapcfriesen: Anyway, all of this is resolved now (and much more simpler) thanks to a lot of work in EDK2/OVMF, QEMU & libvirt.16:27
kashyapMore details in a firefox tab (with the Secure Boot spec) near you :D16:27
* kashyap --> AFK; my brain is fried16:28
cfriesenyeah, it'll be better in another release cycle.16:28
cfriesenlater16:28
mriedemgmann: comments inline :) but it's pretty good.16:28
mriedemgmann: i'll probably just +1 once you fix those since we're close to the ptg and i want to make sure other cores (and ops/users) are aware of what's being proposed here before we move forward16:29
gmannmriedem: sure, i will update16:29
mriedemi think the majority of the team needs to approve or at least be aware and not care since this is a pretty big change16:29
gmannmake sense.16:29
*** sapd1 has quit IRC16:31
*** rcernin has quit IRC16:32
openstackgerritMatt Riedemann proposed openstack/nova stable/pike: Drop legacy-grenade-dsvm-neutron-multinode-live-migration from Pike  https://review.openstack.org/65381116:35
mriedemdansmith: melwitt: ^ spring cleaning16:35
openstackgerritGhanshyam Mann proposed openstack/nova-specs master: Spec for API inconsistency cleanup  https://review.openstack.org/60396916:38
gmannmriedem: ^^ done16:38
melwittmriedem: curious how the job is broken if it's passing?16:41
mriedemit's not16:42
mriedemnon-voting16:42
mriedemsee https://review.openstack.org/#/c/640207/16:42
mriedemif you really want to go mad, you can read my ramblings in https://review.openstack.org/#/c/640197/ trying to fix the job in queens16:42
melwittoh, ok. I was confused by "removes the (broken) non-voting job"16:43
mriedemtl;dr one of the nodes is using nova-cpu.conf and one is using nova.conf and as a result, only one of them has the rbd creds which means the ceph stuff all fails during live migration16:44
mriedemi guess one way for me to deal with the busted job on queens is to just nix the rbd testing so we still have just block migration live migration16:44
melwittah ok16:44
*** rcernin has joined #openstack-nova16:45
*** lbragstad has quit IRC16:47
*** lbragstad has joined #openstack-nova16:48
*** igordc has joined #openstack-nova16:49
*** igordc has quit IRC16:49
*** dtantsur is now known as dtantsur|afk16:50
*** lbragstad_ has joined #openstack-nova16:52
*** lbragstad has quit IRC16:56
*** lbragstad_ is now known as lbragstad16:56
*** tosky has quit IRC16:56
aspierssean-k-mooney: latest patch set of SEV spec is fully converted to the resource class approach https://review.openstack.org/#/c/641994/916:57
aspierscdent / jaypipes might be interested too16:57
cdentthanks aspiers, putting it on the list17:01
aspierscheers17:01
*** pcaruana has joined #openstack-nova17:02
openstackgerritMatt Riedemann proposed openstack/nova stable/queens: Fix legacy-grenade-dsvm-neutron-multinode-live-migration  https://review.openstack.org/64019717:02
openstackgerritMatt Riedemann proposed openstack/nova stable/queens: Move legacy-grenade-dsvm-neutron-multinode-live-migration in-tree  https://review.openstack.org/64019817:02
*** jchhatbar has joined #openstack-nova17:03
sean-k-mooneyaspiers: loook like there is a pep8 issue jsut an fyi17:04
aspiersdarn17:04
aspiersweird, can't see that locally17:05
aspiersoh, wrong environment17:05
aspiersI wonder why tox -e flake8 is allowed17:05
*** lbragstad has quit IRC17:05
*** lbragstad has joined #openstack-nova17:06
openstackgerritAdam Spiers proposed openstack/nova-specs master: Re-approve AMD SEV support for Train  https://review.openstack.org/64199417:07
aspierssean-k-mooney: fixed17:07
*** jchhatbar has quit IRC17:08
*** lbragstad has quit IRC17:17
*** psachin has quit IRC17:27
cdentaspiers: that's the just the unfortunate way tox works...17:32
openstackgerritMerged openstack/nova master: libvirt: set device address tag only if setting disk unit  https://review.openstack.org/61197417:32
*** mvkr has quit IRC17:33
*** ralonsoh has quit IRC17:43
*** rpittau is now known as rpittau|afk17:49
efriedaspiers: Re-reviewed SEV spec17:59
aspiersefried: thanks17:59
efriedcdent: I tried to explain there ^ why we don't ever remove things from os-traits, even if they're trash.17:59
efriedperhaps you can reinforce/augment18:00
cdentefried: looking18:00
aspiersefried, cdent: To "The pathological theoretical case is where somebody (not limited to nova) is on 0.11.0 or 0.12.0, sees the trait and uses it for $whatever", my question is: what could $whatever possibly be? Literally there is zero code which uses it.18:05
efriedI'm basically saying it doesn't matter18:06
aspiersAnd even if they somehow concocted some way to use it, that couldn't possibly relate to SEV in any way, because again there is zero SEV code merged which uses it anywhere.18:06
cdentaspiers, efried : the additional aspect is that whenever a placement service sees a new version of os-traits it syncs up its database with the strings that are in the package, creating a row in the traits table, with an id that becomes a foreign key in other tables18:06
cdents/becomes/can become/18:06
aspiersAhah18:06
aspiersNow that sounds like it could be a good reason18:06
cdentnothing is present is in placement to do a reverse sync18:06
aspiersGotcha18:07
aspiersIn any case, it's trivial to ditch the removal from the spec, and I'm happy to do that18:07
aspiersI just wanted to understand the rationale out of curiosity ;-)18:07
cdentthat wasn't the reason why we can't remove, but once we decided we -weren't- going to remove, then it became safe for the sync mechanism to be that18:07
openstackgerritmelanie witt proposed openstack/nova master: Count instances from mappings and cores/ram from placement  https://review.openstack.org/63807318:07
openstackgerritmelanie witt proposed openstack/nova master: Set [quota]count_usage_from_placement = True in nova-next  https://review.openstack.org/65314618:07
openstackgerritmelanie witt proposed openstack/nova master: Use instance mappings to count server group members  https://review.openstack.org/63832418:07
aspiersYep that makes sense18:07
cdentbut the general ideas was simply: an extensible only enumeration is easier to manage than one than can be shrunk18:08
aspiersSure18:08
aspiersOK, so it stays18:08
aspiersIn that case I'll just need to amend the docs to say not to use it for anything18:08
cdentyeah, that's probably a good idea18:08
efriedYeah, I kept trying to phrase that in terms of this specific trait, where it doesn't necessarily apply. That wasn't the most convincing approach.18:09
efriedthanks for the save cdent18:09
efried:*18:09
cdent:hugs:18:09
cdentIt does suggest that we probably need some kind of "are you really really sure" mechanism when we start adding traits18:09
sean-k-mooneyi am trying to think is there still a usecase for the trait but with the resouce class approch not really18:10
cdentwhen these went by I don't remember them seeming bad or suspect in any way18:10
cdentso it _might_ be that they are still okay in general, just not for this use18:10
sean-k-mooneythe only one i have is a forbiden trait18:10
aspiersefried: Your idea of combining the resources: extra spec with an AMD trait is a nice idea. We're into bikeshedding territory now which is probably not ideal when formulating specs, but it is *conceivable* (if not likely) that in the future AMD might release another memory encryption technology - I dunno, maybe SEV2 or something18:10
sean-k-mooneye.g. i have only a few host that support SEV so please avoaid them18:10
aspiersIn that case, not having an SEV-specific resource class would be problematic18:10
aspierssean-k-mooney: that's an interesting idea. Maybe could be done with anti-affinity scheduler somehow?18:11
efriedaspiers: Well now, this could be an argument for use of the trait :)18:11
efriedin the future18:11
aspiers... based on the premise that you can do anti-affinity for traits but not resources?18:12
sean-k-mooneyaspiers: well if we report both the inventory of the sev resouce class  + add the sev trait to the RP18:12
*** vishakha has quit IRC18:12
sean-k-mooneythen operators can do it by just adding a forbidon trait to there non sev flavor18:12
cdentHaving provided a tiny bit of useful information, I think I'm going to bow out. Since those of you who will be in denver, in denver.18:12
* cdent waves18:12
openstackgerritMatt Riedemann proposed openstack/nova stable/pike: Move legacy-grenade-dsvm-neutron-multinode-live-migration in-tree  https://review.openstack.org/64020718:12
cdents/Since/See/18:12
aspierssean-k-mooney: I'm fine with that (the trait provision code is already written)18:12
cdentsigh18:12
aspierscdent: looking forward to it!18:12
* cdent waves again18:12
*** cdent has quit IRC18:12
sean-k-mooneycdent: o/18:12
efriedI care that my memory encryption is done specifically with SEV2: resources:MEM_ENCRYPT_CONTEXT=1,trait:HW_CPU_AMD_SEV2=required18:12
aspiersefried: right, so we're back to traits then ;-)18:13
aspiersPlaying devil's advocate, are there any downsides to sort of duplicating info between a resource class and a trait?18:13
sean-k-mooneyplease dont call it MEM_ENCRYPT_CONTEXT18:13
efriedFor now, since there's only one way to do it, we don't need to use the trait18:13
aspiersefried: OK, so we could just declare the trait as reserved for potential future use?18:14
efriedjust so.18:14
sean-k-mooneyactully i was going to say that was confusing with intels SGX18:14
sean-k-mooneybut SGX does not encrypt18:14
efriedaspiers: As for the duplication question: IMO it would be nice to strive to not duplicate anything ever.18:14
aspierssean-k-mooney: right, Intel has MKTME instead18:15
sean-k-mooneyya18:15
aspiersefried: +1 ;-)18:15
sean-k-mooneyok im going to have dinner ill try and review the sepc again before i sign off for the long weekend18:16
sean-k-mooneyaspiers: efried i take it taht we are close however on the spec?18:16
aspierssean-k-mooney: thanks!18:16
aspiersit feels close to me but I'm usually over-optimistic18:16
efriedaspiers: The inventory (resource class) is telling you how many of a thing your provider can give. The trait is telling you characteristics of the provider. I don't really see a difference between VCPU:1&HW_CPU_X86_AVX512F:required and MEM_ENC_CTX:1&HW_CPU_AMD_SEV:required18:16
efriedaspiers: I feel we're close on the bits I understand, yes :)18:17
aspiershehe18:17
sean-k-mooneyefried: yes that is a fair comparison18:17
aspiersI see a big difference actually18:17
sean-k-mooneyso we could have  MEM_ENC_CTX:1&HW_CPU_INTEL_MKTME:required also18:17
sean-k-mooneymaybe18:17
efriedsean-k-mooney: exactly18:18
efriedif you don't care which technology you use, omit the traits18:18
efriedIf you want to restrict to one (or more - I think we implemented traits=in:[list], didn't we?) use traits.18:18
sean-k-mooneyaspiers: i forget does the guest need to do anything to use sev18:19
sean-k-mooneye.g. would an app in the guest care18:19
aspiersThe difference is that the presence of HW_CPU_AMD_SEV implies MCM_ENC_CTX, whereas HW_CPU_X86_AVX512F doesn't imply VCPU:1 (because AFAIK you can't have a guest without a vcpu)18:19
sean-k-mooneyor is it jsut something that the host/qemu need to care about18:19
aspierssean-k-mooney: just the host I think, apart from UEFI boot18:20
efriedaspiers: say wha? What sense would HW_*CPU*_X86_AVX512F make if you weren't using any CPUs?18:20
*** jmlowe has quit IRC18:20
aspiersefried: I didn't explain it very well, but my point was that VCPU:1 is essentially a no-op18:20
aspierss/1/2/ and my point is much clearer18:21
efriednope, sorry, not following you.18:21
sean-k-mooneyi see you point but form a placement point of view a VCPU and SEV context are both jsut resouces18:21
sean-k-mooneyit doesnt care18:21
sean-k-mooneyand traits are jsut strings18:21
aspierssure, but efried was saying we should avoid duplication18:21
aspiersHW_CPU_AMD_SEV implies MEM_ENC_CTX:1 therefore there is duplication18:22
*** awalende has joined #openstack-nova18:22
aspierswhereas with VCPU:2&HW_CPU_X86_AVX512F there is none18:22
aspiersboth constraints are needed in the latter, but not in the former18:22
efriedI've said I want two VCPUs. They have to support x86 AVX 512F. If I just say "I want x86 AVX 512F", you still don't know how many VCPUs I want. I could theoretically have made HW_CPU_X86_AVX512F a resource class so I could just say HW_CPU_X86_AVX512F=218:22
efriedbut then I would need a separate flavor for every possible flag18:22
sean-k-mooneywe are ratholeing  i think :)18:22
mriedemmelwitt: heh you said the same as i did before i could post it https://review.openstack.org/#/c/653145/18:23
efriedand couldn't ever say "I'll accept any one of these variants"18:23
efriedetc etc.18:23
efriedThat's why we have quantitative and qualitative separated.18:23
aspiersI think we're on the same page, but I was responding specifically to the example you were describing as equivalent18:23
melwittmriedem: hah, nice18:23
aspiersI don't think that specific example exhibits equivalence18:24
efriedThere I go again using a poor specific example.18:24
aspiersbut yeah if you made HW_CPU_X86_AVX512F a resource class that would be a totally different thing18:24
aspiers;)18:24
efriedI actually haven't a clue what AVX512F means.18:24
aspiershaha, nor me18:24
efriedOr, for that matter, SEV18:24
aspiersI know it's a CPU flag though ;-)18:24
efriedjust that both are qualitative characteristics of a thing.18:24
aspiersanyway I have enough to go on for another patch set18:25
efriedcool18:25
aspiersare you around much longer today?18:25
aspiersjust wondering if it's worth trying to get it done shortly18:25
efriedaspiers: was going to say, in further response to your "almost ready" question, that if we got an ack from danpb at this point, I would +2 with the discussed changes.18:25
efriedI'm around for at least another 3.5h18:26
aspiersOK I'll try to ditch the trait removal then18:26
*** awalende has quit IRC18:26
aspierswhich timezone is danpb?18:26
efried...noting of course that I still definitely want someone like jaypipes to weigh in on the using-rc-vs-trait shift.18:26
efriedno idea.18:26
aspiersoh yeah, me too :)18:27
aspiersdon't know if he's around though18:27
mriedemUK18:27
mriedemlondon i think specifically18:27
aspiersno way!18:27
aspiersthat's where I am18:27
aspiershad no idea18:27
mriedemhe's your neighbor you weird hermit18:27
aspiershaha18:27
mriedemhe's probably in your garden right now18:27
* aspiers checks18:28
mriedemby garden i mean "back yard"18:28
aspiersI have a garden18:28
aspierscommunal, but I'm counting it18:28
efriedanyway, aspiers, I'm not sure we're shooting to get this merged today, but couldn't hurt to have a ps without a blocking issue (os-traits reduction) in it for whenever those guys do get to looking.18:28
aspiershrm, need to google a pic of him first18:28
aspiersefried: agreed18:28
aspiersI'll try to address shortly18:28
efriedthanks for your patience aspiers18:28
aspiersefried: likewise!!18:29
artomWe do beg your pardon, we are in your garden18:40
aspiersX-D18:47
*** jmlowe has joined #openstack-nova18:49
*** jmlowe has quit IRC18:54
*** jangutter has joined #openstack-nova19:15
*** lbragstad has joined #openstack-nova19:24
openstackgerritErik Olof Gunnar Andersson proposed openstack/nova master: [WIP] Validate that ironic_url works with regions  https://review.openstack.org/65383919:30
*** lyarwood has quit IRC19:30
openstackgerritMerged openstack/nova master: Remove old-style cell v1 instance listing  https://review.openstack.org/65129619:39
efriedmriedem: Since Spec: https://review.openstack.org/#/c/645458/ (Add host and hypervisor_hostname flag to create server) is merged/approved, can I strike it from the PTG agenda?19:41
openstackgerritmelanie witt proposed openstack/nova master: Add get_usages_counts_for_quota to SchedulerReportClient  https://review.openstack.org/65314519:44
openstackgerritmelanie witt proposed openstack/nova master: Count instances from mappings and cores/ram from placement  https://review.openstack.org/63807319:44
openstackgerritmelanie witt proposed openstack/nova master: Set [quota]count_usage_from_placement = True in nova-next  https://review.openstack.org/65314619:44
openstackgerritmelanie witt proposed openstack/nova master: Use instance mappings to count server group members  https://review.openstack.org/63832419:44
openstackgerritmelanie witt proposed openstack/nova master: Add documentation for counting quota usage from placement  https://review.openstack.org/65384519:44
mriedemefried: i think so19:45
efriedthx19:45
openstackgerritmelanie witt proposed openstack/nova master: Add documentation for counting quota usage from placement  https://review.openstack.org/65384519:47
openstackgerritmelanie witt proposed openstack/nova master: Add documentation for counting quota usage from placement  https://review.openstack.org/65384519:48
*** jangutter has quit IRC19:49
*** eharney has quit IRC19:55
*** boxiang has quit IRC20:02
*** jangutter has joined #openstack-nova20:04
*** jangutter has quit IRC20:09
*** bbowen has quit IRC20:15
openstackgerritErik Olof Gunnar Andersson proposed openstack/nova master: [WIP] Validate that ironic_url works with regions  https://review.openstack.org/65383920:16
*** tjgresha has joined #openstack-nova20:22
*** tjgresha has quit IRC20:26
openstackgerritMerged openstack/nova stable/queens: Add functional recreate test for bug 1819963  https://review.openstack.org/64841420:41
openstackbug 1819963 in OpenStack Compute (nova) queens "Reverting a resize does not update the instance.availability_zone value to the source az" [Medium,In progress] https://launchpad.net/bugs/1819963 - Assigned to Matt Riedemann (mriedem)20:41
openstackgerritsean mooney proposed openstack/nova master: [WIP] Libvirt: add nfv job  https://review.openstack.org/65219720:42
*** pcaruana has quit IRC20:47
*** luksky has joined #openstack-nova20:51
*** awaugama has quit IRC20:55
*** efried has quit IRC20:55
*** efried has joined #openstack-nova20:56
efriedmriedem: re deprecating nova-console: I read http://lists.openstack.org/pipermail/openstack-dev/2018-October/135422.html as "no objections". Is there anything to be gained by discussing it at the PTG, someone who happens to be in the room voicing an objection?21:07
*** tbachman has joined #openstack-nova21:08
efried"...PTG, *beyond* someone who happens to be in the room..."21:09
*** tjgresha has joined #openstack-nova21:12
sean-k-mooneyefried: maybe at the fourm21:13
sean-k-mooneyget operators to weigh in21:13
efriedIt just seems pretty hit or miss to me. We ask the question and nobody responds, we're not really any better off than we were. Maybe the guy who cares just left the room, or isn't at the summit, or whatever.21:14
efriedI would think the ML would be a better way to canvass the right cross-section of people. And that's been done.21:15
*** tjgresha has quit IRC21:16
sean-k-mooneywell we can deprecated it in train and then the have until U to say "hay we use that"21:16
efriedThen we deprecate it for a release or two (or six, viz. nova-network), giving people yet more time to make noise.21:16
mriedemefried: i agree that the ML is likely better than the PTG since i don't expect any xen/citrix people to be at the ptg21:16
mriedemBob's reply in the ML wasn't exactly clear to me about there being a replacement people are using21:16
mriedemthe service has already been deprecated technically21:16
efriedmriedem: ack. I was focusing on the part where he said "yeah, deprecate"21:16
efriedmriedem: okay. I'm going to put it at the bottom of the list, for like 4:55pm Saturday.21:17
efrieddo you want to fup on the ML? or want me to do so? Or leave it alone?21:17
mriedemdeprecated as of stein https://review.openstack.org/#/c/610075/ - the bigger question for me was if we drop the service, the APIs have to also start returning a 40121:17
mriedem*41021:17
efriedmm21:17
mriedemthis is just like if we remove the nova-cells and nova-network services, the APIs that rely on those will just not work21:18
mriedemwell, won't work in train - might work in stein21:18
efriedright; which we're fine with21:18
efriedBut, are you considering taking this on in train?21:18
efriedor hoodwinking stephenfin into doing so :P21:19
sean-k-mooneyby the way i moved the ci stuff here https://etherpad.openstack.org/p/nova-ptg-train-ci but im not really sure what we want to get out of it21:19
mriedemefried: it's not really much to take on21:19
efriedsean-k-mooney: Good, since you're here, that's a question I'm basically trying to ask everyone about their topics.21:19
mriedemrm -rf nova/console21:19
efriedmriedem: death of a thousand cuts?21:19
mriedemthis is definitely not a priority for me21:20
efriedk. I'll fup on the ML like I did for the privsep topic, proposing to cut it from the agenda unless objections.21:20
mriedemi see the tc has a ptg item about "can we just start breaking stuff so people can get all the fancy new awesome cloud stuff" so we could just drop, say it's the tc's fault, and then move on21:21
efriedperfect21:22
sean-k-mooneyefried: can you get some of the intel folks to attend  https://etherpad.openstack.org/p/nova-ptg-train-ci that will be setting up/runing the cis21:34
efriedhrm, I'm actually not sure if our boots-on-the-ground CI folk are going to be attending.21:35
efriedBut I believe dtroyer is the, ahem, spokesperson for the effort.21:35
*** mvkr has joined #openstack-nova21:35
sean-k-mooneyok well 2 of the feature intel is pushing for this cycle would need 3rd part ci.21:37
sean-k-mooneypersitent memeoy and rmd21:37
efriedoh, yes, we are well aware.21:37
aspierssean-k-mooney: do you have a suggestion for a resource class name instead of MEM_ENCRYPTED_CONTEXT?21:39
efriedsean-k-mooney: I can see you're still working on that agenda; as you go along, if you could be thinking about what we hope to achieve in the room, that we actually need to all be in a room for, that would be neat.21:40
sean-k-mooneyif we combine it with the trait i think it fine but i was also oke with SEV_CONTEXT21:40
aspiersefried: sean-k-mooney's earlier suggestion of trait:HW_CPU_AMD_SEV=forbidden as a valid use case has finally sunk in. It seems to me that operators could use this in flavors as soon as the SEV code merged, for keeping non-SEV guests off SEV machines.21:41
sean-k-mooneyefried: well i would like mriedem input on that21:41
aspiersOf course this would mean providing the trait from day 0, but I'm tempted to think that it's already a compelling enough use case that maybe I should propose that in the spec21:42
sean-k-mooneythis item basicaly came form the fact the nfv ci went way(on the nova side) and we got a bunch of new numa/hardware feature requests21:42
efriedif it's important to keep SEV-capable machines free of non-SEV instances. Do we care?21:42
aspiersI would definitely expect some operators to want that, yes21:42
sean-k-mooneyaspiers: some but not all21:42
sean-k-mooney?21:42
aspiersSurely it would be likely that a compute plane would be mostly non-SEV hosts, with a few SEV hosts to cater for the more demanding customers21:42
aspierssean-k-mooney: sorry, you lost me - not all what?21:43
efriedOkay. Then cool, I have no problem reintroducing the trait for that purpose - and also the future purpose of being able to distinguish between different mem encryption technologies.21:43
sean-k-mooneyaspiers: i think the quest efiried is asking is it required for it to work21:43
efriedno, I was just asking whether it matters that we consume non-sev-context resources on a sev-capable machine21:44
aspiersIt's probably not *required*, but the trait is already in os-traits and the code to provide it is already working, so ... :)21:44
aspiersefried: Yes, I think it would matter to many operators21:44
efriedaspiers: Yes, and adding the trait at the same time as you add the context inventory is trivial, and enables this use case with no additional work.21:44
aspiersAFAIK SEV hardware is still niche (and maybe more expensive too, I dunno)21:44
aspiersefried: exactly21:44
efriedother than that 2LOC in update_provider_tree, you get to write a paragraph in the docs. That's it.21:45
aspiersRight21:45
aspiersI'll mention the potential future use case too21:45
efriedexcept... didn't we have a better way to turn on a "don't land here" by default?21:45
efriedrather than having to put it in every non-SEV flavor?21:45
aspiersProbably not21:46
efriedForbidden aggregates...21:46
aspiersOh21:46
aspiersAnd required traits would override that?21:46
efriedhttps://review.openstack.org/#/c/609960/21:46
efriedit's... a little complicated.21:47
aspiershah21:47
aspiersbut similar looking21:47
sean-k-mooneyefried: you mean the RP forbiden traits feature i suggested liek a year ago or soemthing else21:47
sean-k-mooney* RP required tratis21:47
sean-k-mooneywwell actuly it was both21:48
efriedsean-k-mooney: Yes, exactly the same use case.21:48
efriedit's just, you were the only person in the world who could get their mind around reverse-required traits.21:48
sean-k-mooneyhaha21:48
efriedThis solution isn't beautiful, but it's at least *slightly* less confusing to mere mortals.21:49
sean-k-mooneyif only the term required traits was not already used21:49
efriedaspiers: I would have to reread that spec to understand whether the SEV trait would be applicable, or whether it would have to be a different kind of trait or aggregate somethingsomething.21:50
*** francoisp has quit IRC21:51
aspiersYeah21:51
efriedah, okay, yes21:51
aspiersWell I'll make the SEV spec raise the idea of using the trait sooner rather than later, but I'll leave it up for debate in subsequent reviews21:51
efriedso aspiers it would actually want to work more like this: you would want a generalized trait - basically exactly matching the freaking resource class - for people to isolate all their mem-enc-capable systems for mem-enc-only VMs.21:52
efriedor21:52
efriedyou could still have the traits be granular, and the operator would simply have to add all of them to the agg metadata.21:53
efriedthat would be fine too.21:53
sean-k-mooneyor you could not do it in placement and just have a 4 like weigher21:53
sean-k-mooney*4 line21:53
aspiersmaybe a topic for Denver?21:54
efriedaspiers: I think it would be goodness for you to set the trait on sev-capable hosts, but not suggest any specific uses for it in the docs.21:54
sean-k-mooneyit might be intersting to have a generalised weigher that operates on traits21:54
aspiersefried: OK, but the spec would still need to justify setting it21:54
sean-k-mooneyefried: yep i think that is a good idea too21:55
sean-k-mooneyaspiers: not really21:55
efriedaspiers: In the spec, you can mention the two cases we've discussed here: 1) When more than one mem-enc technology is available, you can use it to get a specific one; and 2) it can be used with <reference forbidden aggs spec> to keep non-SEV guests clear of SEV-capable hosts.21:55
aspiersack21:55
efried"...but those impls are outside the scope of this spec."21:55
aspiers+121:56
sean-k-mooneyya the ... out of scope is the imporant bit21:56
efriedand \o/ the trait is no longer trash :)21:56
sean-k-mooney:)21:56
aspiershaha21:56
aspiersbut this needs to be updated still https://docs.openstack.org/os-traits/latest/reference/index.html#amd-sev21:56
aspierswell, just the last sentence21:57
aspiersthe rest is good I think21:57
efriedhmph, that paragraph is a lie21:57
aspiersInstead it probably needs to caution *against* relying on just trait:HW_CPU_AMD_SEV=required21:57
efriedimplies that you can get SEV by specifying the trait. That's not true yet.21:57
efriedso yeah, that doc should be updated regardless. Sooner rather than later, even.21:58
sean-k-mooneyefried: or ever with out the resoruce request21:58
aspiersGood point. We originally expected it all to be merged within Stein :-(21:58
efriedaspiers: Re Denver, if we can possibly get away with resolving this before we get there, I will be very happy.21:58
aspiersBut yeah, I guess the last paragraph should have started out as a forward-looking statement21:59
aspiersand then been changed to present tense later, when it was all implemented21:59
aspiersLesson learnt for next time21:59
sean-k-mooneyefried: actully on the traits weigher thing. would it make sense to have a weigh that looked at teh traits on the selcect resouce providers and looked at the traits you requested and used that to calulate a weight for the host22:00
sean-k-mooneyunrealted to SEV22:01
efriedsean-k-mooney: The ol' "preferred traits" deal22:01
sean-k-mooneykind of but not quite22:01
efriedIt be like a "reverse preferred traits" deal22:01
sean-k-mooneyperferred tratis worked by you saying i would like x22:01
efriedright, you're saying "If I didn't ask for X, prefer hosts that *don't* have X"22:01
sean-k-mooneyya22:02
efriedThat would be a pretty cool weigher. Sounds like fun to write too.22:02
sean-k-mooneyor rather prefer the host whos traits match the ones you asked for the closes22:02
*** mchlumsky has quit IRC22:02
sean-k-mooneyi might hack on it before the ptg22:02
sean-k-mooneythe premmis being host with less traits have less intersting stuff22:03
sean-k-mooneyso prefer the boaring hosts22:03
efriedit would also be nice to know which traits were more interesting than other traits.22:05
efriedLike, I probably care way less about HW_CPU_X86_AVX512F than I do HW_AMD_SEV22:05
sean-k-mooneywe can sprinkle in a little ML/AI it will be grand22:05
sean-k-mooneybut yes22:05
efriededleafe would suggest using trait metadata on the placement side so we can rank the traits in priority order.22:05
sean-k-mooneyif we had a histogram of how often traits exisit for a given resouce class22:06
sean-k-mooneywe could use that as an input22:06
edleafeefried: I would??22:06
sean-k-mooneyedleafe: ofcouse efried just said so above :)22:06
sean-k-mooneyit would be eaiser to do some of this on the placement side however22:07
efriedoh, edleafe, is this *your* goat?22:07
mriedemoh nice a stack overflow in unit tests http://logs.openstack.org/45/649345/7/check/openstack-tox-py36/ba15c17/job-output.txt.gz#_2019-04-18_18_10_53_42395222:07
edleafeWeighers in Placement - yay!22:07
sean-k-mooneymriedem: so there is definetly an infinity loop between _get and __getattr__ in tha tpatch22:09
efriedbut only in py3622:09
mriedemsean-k-mooney: i've seen this TestRPC class intermittently failing unit tests all over the gate today22:09
mriedemit's not this patch22:09
sean-k-mooneywith the same oslo config issue?22:10
mriedemmaybe?22:10
mriedemhttp://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22%7C%20Fatal%20Python%20error%3A%20Cannot%20recover%20from%20stack%20overflow.%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d22:10
mriedemwhat did we merge on april 15?22:11
sean-k-mooneyin oslo config. apparently droping python 35 testing22:12
mriedem...22:12
mriedemwhy would that matter in a nova py36 job?22:12
mriedemespecially if an oslo.config change is unreleased for us to use it22:13
sean-k-mooneyi assume this is a version bump in upper constratins or a new release?22:13
mriedemhttps://github.com/openstack/requirements/commit/a96ee0e258aafb2880149b3e25dd5959f7b37c0922:13
efriedsean-k-mooney: are you at the PTG through Saturday?22:13
sean-k-mooneyim flying there the friday before and leaving the Starday afternoon so yes22:14
sean-k-mooneymriedem:  oslo.config 4.11.2 came out 2 days ago22:14
efriedsean-k-mooney: I'm going to assert that the CI topic is one we don't need jaypipes for; and dtroyer is booked Th+Fr. So I'll set the CI topic for Saturday a.m., cool?22:15
sean-k-mooneyoh never mind22:15
sean-k-mooneythat is old22:15
sean-k-mooneyefried: ya that sound fine22:15
mriedemwe're using 6.8.1 from 2 months ago22:15
mriedemi also started seeing seg faults in pip 3.6 installs yesterday, so maybe something in py36 on bionic nodes since april 1522:16
mriedemhttps://bugs.launchpad.net/nova/+bug/182543522:18
openstackLaunchpad bug 1825435 in OpenStack Compute (nova) "TestRPC unit tests intermittently fail with "'>' not supported between instances of 'NoneType' and 'datetime.datetime'"" [Undecided,Confirmed]22:18
aspierssean-k-mooney: I forgot to get your take on whether hugepages are still helpful for SEV, in terms of accounting22:19
sean-k-mooneyam i think they are22:19
aspierssean-k-mooney: I'm a little confused by recent discussions but I got the impression they can only be used for accounting guest RAM22:19
sean-k-mooneymainly because you still have to lock the memory22:19
aspiersand QEMU allocates a whole bunch of other stuff22:19
sean-k-mooneyyes it does for mmio/dma22:20
sean-k-mooneywith SEV instace there will be no oversubsription of memory22:20
sean-k-mooneythat is also true of hugepages22:20
aspiersis it useful to only track part of what is allocated though?22:20
sean-k-mooneyyes which will be most of it22:21
sean-k-mooneythe qemu overhead is ment to be tracked using the resved meory config option22:21
aspiersYeah, that's the bit which danpb is suggesting should have an rlimit at the top /machine.slice cgroup I think?22:22
sean-k-mooneyor on a hugepage host its assumed you leave enough free non hugepage memeroy on the host for the os and any qemu memroy required outside of the guest ram22:22
sean-k-mooneyya22:22
aspiersi.e. reserving some memory for the host22:22
*** awalende has joined #openstack-nova22:23
aspiersI added some paras in the spec about this - please could you check them if you didn't already?22:23
sean-k-mooneyso my suggetion is still use the locked element but dont set the hard_limit22:23
aspiersYes, I already changed the spec to propose that22:23
sean-k-mooneyand preferably use hugepages22:23
aspiersit pretty much says that too22:23
aspiersMost of my recent edits were just copying your advice ;)22:23
sean-k-mooneyif you dont use hugepages we need to tell the operators to set the ram_allocatoin_raito to 1.022:23
aspiersbut I'm not 100% sure I got it all accurate22:24
sean-k-mooneyill take a look at it before the ptg22:24
aspierscool thanks22:24
*** awalende has quit IRC22:27
mriedem"'>' not supported between instances of 'NoneType' and 'datetime.datetime'" seems to be showing up in stephen's cells v1 removal series first...i'm not sure what could have introduced that22:27
sean-k-mooneydid we merge any of that yet22:28
mriedemyes22:28
sean-k-mooneymaybe the instance list change22:32
sean-k-mooneymaybe not im wondering if we change how we are handeling the sorted list22:34
sean-k-mooneywe used to call self._get_instances_by_filters and now we call instance_list.get_instance_objects_sorted22:35
sean-k-mooneyacutly no _get_instances_by_filters just calls instance_list.get_instance_objects_sorted22:39
*** _erlon_ has quit IRC22:40
sean-k-mooneyjust skimmed through the few that have merged but nothing obvious jumped out at me22:46
efriedsean-k-mooney: Are you particularly motivated to discuss provider yaml at the PTG?22:47
sean-k-mooneyno22:47
sean-k-mooneyi mean we can but i didnt think many people were interested22:48
sean-k-mooneyand im not planning to work on it in train22:48
efriedRight, lack of interest had put it way on the back burner for me22:48
sean-k-mooneyya same22:48
efriedIt's not something we can discuss without jaypipes, so putting it at the back of the agenda is kinda pointless. I'm just going to scrub it, k?22:48
sean-k-mooneysure22:49
sean-k-mooneyi think we have more pressing things for Train22:49
efriedright22:49
*** tkajinam has joined #openstack-nova22:54
*** luksky has quit IRC22:59
sean-k-mooneylooking at the etherpads i dont really have much propsoed anymore23:00
efriedsean-k-mooney: It's not a requirement for you to have stuff on there :)23:00
sean-k-mooneyya i know23:00
efriedbesides, I think the CI topic is plenty, don't you?23:00
sean-k-mooneywell the ci topic was not originally my idea23:01
sean-k-mooneybut i ment it more as what i will like be working in trains has shifited some what so i have not really need to propose much to discuss23:01
*** whoami-rajat has quit IRC23:03
sean-k-mooneythats actully a good thing as  i need to still figure out what cyborg/plaement topics i shoudl attend23:03
*** bbowen has joined #openstack-nova23:08
efriedsean-k-mooney: It's not a bad thing if the stuff you will be working on is well enough understood that we don't need PTG time for it.23:08
efriedIf we could do that for everything, we wouldn't need a PTG :)23:08
efriedgotta run o/23:08
sean-k-mooneyo/23:08
*** igordc has joined #openstack-nova23:20
openstackgerritAdam Spiers proposed openstack/nova-specs master: Re-approve AMD SEV support for Train  https://review.openstack.org/64199423:20
openstackgerritmelanie witt proposed openstack/nova master: Create request spec, build request and mappings in one transaction  https://review.openstack.org/58674223:55

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