Wednesday, 2019-07-03

*** slaweq has joined #openstack-nova00:16
*** slaweq has quit IRC00:21
*** gyee has quit IRC00:28
melwittalex_xu: hey, would appreciate to have your thoughts on the unified limits spec around the proxy API/deprecation and migration parts https://review.opendev.org/60220100:40
melwitt*especially the proxy API/deprecation and migration parts00:40
openstackgerritMerged openstack/nova stable/rocky: Init HostState.failed_builds  https://review.opendev.org/66852000:45
openstackgerritMerged openstack/nova master: Stabilize unshelve notification sample tests  https://review.opendev.org/66867500:45
*** brinzhang has joined #openstack-nova00:47
*** ricolin_ has joined #openstack-nova00:51
*** ricolin_ is now known as ricolin00:52
*** tbachman has quit IRC01:02
*** panda has quit IRC01:03
*** tbachman has joined #openstack-nova01:05
*** panda has joined #openstack-nova01:05
*** imacdonn has quit IRC01:11
*** imacdonn has joined #openstack-nova01:11
*** Kevin_Zheng has joined #openstack-nova01:12
openstackgerritMerged openstack/nova stable/queens: Fail to live migration if instance has a NUMA topology  https://review.opendev.org/62959701:21
*** lbragstad has quit IRC02:04
openstackgerritMerged openstack/nova stable/queens: libvirt: Avoid using os-brick encryptors when device_path isn't provided  https://review.opendev.org/65646402:06
*** dasp has quit IRC02:46
*** dasp has joined #openstack-nova03:03
*** StevenK has quit IRC03:08
*** psachin has joined #openstack-nova03:34
*** StevenK has joined #openstack-nova03:37
*** ricolin_ has joined #openstack-nova03:54
*** udesale has joined #openstack-nova03:56
*** ricolin has quit IRC03:57
*** _alastor_ has quit IRC04:25
*** toabctl has quit IRC04:31
*** whoami-rajat has joined #openstack-nova04:34
*** shilpasd has joined #openstack-nova04:34
*** brinzhang_ has joined #openstack-nova04:47
*** brinzhang has quit IRC04:50
*** tkajinam has quit IRC05:01
*** brinzhang_ has quit IRC05:05
*** brinzhang_ has joined #openstack-nova05:05
*** pcaruana has joined #openstack-nova05:06
*** ratailor has joined #openstack-nova05:23
*** ratailor_ has joined #openstack-nova05:29
*** ratailor has quit IRC05:32
*** shilpasd has quit IRC05:36
*** ricolin_ is now known as ricolin05:37
*** udesale has quit IRC05:38
*** igordc has quit IRC05:41
*** artom has joined #openstack-nova05:41
*** ratailor_ has quit IRC05:41
*** artom is now known as artom|gmtplus305:41
*** shilpasd has joined #openstack-nova05:44
*** ratailor has joined #openstack-nova05:47
*** Luzi has joined #openstack-nova05:54
*** tkajinam has joined #openstack-nova06:00
openstackgerritArtom Lifshitz proposed openstack/nova master: [WIP] Introduce live_migration_claim()  https://review.opendev.org/63566906:17
openstackgerritArtom Lifshitz proposed openstack/nova master: New objects for NUMA live migration  https://review.opendev.org/63482706:17
openstackgerritArtom Lifshitz proposed openstack/nova master: LM: add support for sending NUMAMigrateData to the source  https://review.opendev.org/63482806:17
openstackgerritArtom Lifshitz proposed openstack/nova master: LM: add support for updating NUMA-related XML on the source  https://review.opendev.org/63522906:17
openstackgerritArtom Lifshitz proposed openstack/nova master: RPC changes to prepare for NUMA live migration  https://review.opendev.org/63460506:17
openstackgerritArtom Lifshitz proposed openstack/nova master: NUMA live migration support  https://review.opendev.org/63460606:17
openstackgerritArtom Lifshitz proposed openstack/nova master: CONF.enable_numa_live_migration is not needed >= Train  https://review.opendev.org/64002106:17
*** luksky has joined #openstack-nova06:27
*** rha has quit IRC06:28
*** maciejjozefczyk has joined #openstack-nova06:36
*** shilpasd has quit IRC06:38
*** belmoreira has joined #openstack-nova06:39
*** slaweq has joined #openstack-nova06:46
*** rdopiera has joined #openstack-nova06:48
*** luksky has quit IRC06:48
*** ricolin_ has joined #openstack-nova06:51
*** maciejjozefczyk has quit IRC06:53
*** ricolin has quit IRC06:53
*** maciejjozefczyk has joined #openstack-nova06:55
*** ttsiouts has joined #openstack-nova06:58
openstackgerritYongli He proposed openstack/nova master: Add server sub-resource topology API  https://review.opendev.org/62147607:02
*** cdent has joined #openstack-nova07:04
*** luksky has joined #openstack-nova07:06
*** rpittau|afk is now known as rpittau07:06
*** xek has joined #openstack-nova07:07
*** tssurya has joined #openstack-nova07:10
*** damien_r has joined #openstack-nova07:12
*** tesseract has joined #openstack-nova07:21
openstackgerritBalazs Gibizer proposed openstack/nova stable/stein: Stabilize unshelve notification sample tests  https://review.opendev.org/66880607:25
*** ttsiouts has quit IRC07:26
*** ttsiouts has joined #openstack-nova07:27
*** toabctl has joined #openstack-nova07:30
*** ttsiouts has quit IRC07:31
*** bhagyashris has joined #openstack-nova07:32
openstackgerritLee Yarwood proposed openstack/nova master: Get rid of args to RBDDriver.__init__()  https://review.opendev.org/66856407:34
*** luksky11 has joined #openstack-nova07:43
*** luksky has quit IRC07:45
*** ttsiouts has joined #openstack-nova07:51
openstackgerritLee Yarwood proposed openstack/nova master: libvirt: Remove unreachable native QEMU iSCSI initiator config code  https://review.opendev.org/66875007:52
*** luksky11 has quit IRC07:55
*** ralonsoh has joined #openstack-nova07:59
*** ociuhandu has joined #openstack-nova08:05
*** ociuhandu has quit IRC08:05
*** ociuhandu has joined #openstack-nova08:06
*** trident has quit IRC08:08
*** luksky11 has joined #openstack-nova08:08
*** trident has joined #openstack-nova08:09
*** ratailor_ has joined #openstack-nova08:10
*** luksky11 has quit IRC08:11
*** ratailor has quit IRC08:12
*** ratailor__ has joined #openstack-nova08:13
*** ratailor_ has quit IRC08:16
*** ratailor_ has joined #openstack-nova08:16
*** sridharg has joined #openstack-nova08:18
*** ratailor__ has quit IRC08:19
*** priteau has joined #openstack-nova08:26
*** luksky11 has joined #openstack-nova08:27
*** luksky11 has quit IRC08:33
*** ivve has joined #openstack-nova08:34
openstackgerritBoxiang Zhu proposed openstack/nova master: Make evacuation respects anti-affinity rule  https://review.opendev.org/64996308:37
*** tkajinam has quit IRC08:39
*** ricolin__ has joined #openstack-nova08:44
*** ricolin_ has quit IRC08:47
kashyapjohnthetubaguy: You about by any chance?  If so, the Secure Boot spec requires the final +2 (& a +W), assuming you're satisfied with all the things I've addressed: https://review.opendev.org/#/c/506720/08:47
*** zzzeek has quit IRC08:48
*** zzzeek has joined #openstack-nova08:49
*** mdbooth has joined #openstack-nova08:49
*** davidsha has joined #openstack-nova08:49
*** ricolin__ is now known as ricolin08:55
*** tesseract-RH has joined #openstack-nova08:57
*** tesseract has quit IRC08:58
*** udesale has joined #openstack-nova09:04
*** ratailor_ has quit IRC09:05
*** ratailor has joined #openstack-nova09:07
*** luksky11 has joined #openstack-nova09:12
*** tesseract-RH has quit IRC09:29
*** tesseract has joined #openstack-nova09:29
*** tesseract has quit IRC09:33
*** tesseract has joined #openstack-nova09:33
*** tesseract has quit IRC09:38
*** tesseract has joined #openstack-nova09:39
*** guozijn has joined #openstack-nova09:50
kashyapalex_xu: Hi, maybe you can give the final ACK (if you don't spot anything else): https://review.opendev.org/64996309:57
*** lei-zh has joined #openstack-nova09:59
*** lei-zh has quit IRC10:01
*** lei-zh has joined #openstack-nova10:02
*** bhagyashris has quit IRC10:07
*** guozijn has quit IRC10:14
*** ttsiouts has quit IRC10:16
*** ttsiouts has joined #openstack-nova10:16
*** ttsiouts has quit IRC10:21
*** udesale has quit IRC10:28
*** udesale has joined #openstack-nova10:29
*** brinzhang_ has quit IRC10:35
*** lei-zh has quit IRC10:36
*** udesale has quit IRC10:52
*** udesale has joined #openstack-nova10:54
*** udesale has quit IRC10:58
*** guozijn has joined #openstack-nova10:58
*** udesale has joined #openstack-nova10:58
*** cdent has quit IRC10:58
*** ttsiouts has joined #openstack-nova11:01
*** psachin has quit IRC11:06
*** guozijn has quit IRC11:10
*** sapd1_x has joined #openstack-nova11:14
*** udesale has quit IRC11:19
openstackgerritJosephine Seifert proposed openstack/nova-specs master: Spec for the Nova part of Image Encryption  https://review.opendev.org/60869611:23
Luzisean-k-mooney, I added a few sentences concerning the lifecycle11:26
*** cdent has joined #openstack-nova11:28
*** sapd1_x has quit IRC11:30
*** bbowen has joined #openstack-nova11:31
*** priteau has quit IRC11:32
*** tssurya has quit IRC11:34
*** tssurya has joined #openstack-nova11:37
*** ratailor has quit IRC11:42
openstackgerritArtom Lifshitz proposed openstack/nova master: NUMA live migration support  https://review.opendev.org/63460611:56
openstackgerritArtom Lifshitz proposed openstack/nova master: CONF.enable_numa_live_migration is not needed >= Train  https://review.opendev.org/64002111:56
*** shilpasd has joined #openstack-nova11:59
*** tbachman has quit IRC12:05
*** cdent has quit IRC12:08
*** francoisp has joined #openstack-nova12:10
*** elod has quit IRC12:11
*** priteau has joined #openstack-nova12:18
*** tbachman has joined #openstack-nova12:28
*** cdent has joined #openstack-nova12:29
*** _erlon_ has joined #openstack-nova12:33
*** eharney has joined #openstack-nova12:37
sean-k-mooneyLuzi: thanks ill re review but overall i liked the spec12:37
sean-k-mooneyLuzi: so all server operations like shelve,rescure, mirgrations will all work12:41
Luziyes12:42
sean-k-mooneyand for shelve if the instance is create form an encypted image teh snapshot that is created automaticly by shelve will be encrypted12:43
*** psachin has joined #openstack-nova12:43
LuziI will have a deeper look into this, but we only wanted to create encrypted images when a user triggers the encryption12:46
sean-k-mooneywithout a change to the shelve api the user would not be able to say use encyption since for shvele and cross cell resize a snapshot is created automatically12:47
*** elod has joined #openstack-nova12:47
sean-k-mooneyrather then the user calling the snapshot api directly12:48
sean-k-mooneyso we would really want the encyption to be sticky. e.g. if the instacne was created form an encypeted image defult to encyption12:48
Luziwell it seems there are three options here:12:52
Luzi1. leaving this alone, so there would not be any encryption during shelve12:53
Luzi2. automaticly encryption - which is a huge problem for glance, btw...12:53
Luzior 3. let the user trigger the encryption (and maybe deny the operation, when the original image was encrypted)12:54
Luzithe last one would need a metadata change, so we can check, whether the snapshot could be taken without encryption12:55
Luzibut it seems to be the most reasonable way12:55
sean-k-mooneywell if we do 1 if i wanted to steal you sensitive data all i have to do is shelve you instnace grap a copy of the snapshot which is in the clear and unshelve it12:56
Luzithere was a misunderstanding here with the word snapshot, so thank you for the hint12:57
Luziyeah, thats not nice from a security perspective :D12:57
sean-k-mooney2 and 3 are the most secure12:57
sean-k-mooneythe issue with 3 woudl be that its  would be fine for shelve to be exteded with a "encypte this please" option12:58
sean-k-mooneyresize im less sure about12:58
*** elod_ has joined #openstack-nova12:58
Luzi2 would not be practically as automatically creating secrets for a ressource of another project is horrible12:58
*** elod has quit IRC12:58
sean-k-mooneyfor resize we only create a snapshot if its a cross cell resize12:58
*** elod_ is now known as elod12:59
sean-k-mooneya normal resize wont create a snapshot12:59
Luziso i will add number three in the spec and will have a look into resize too12:59
sean-k-mooneyand as an unprivaldaged user i cant tell if its cross cell or not12:59
Luzithank you, that was reasonable the best review I got so far :D13:00
sean-k-mooney:) well hopefully we can get this landed soon. as i said the rest of the spec looks good to me13:01
sean-k-mooneyjust to undersdand the problem with option 2, what is the issue with createing keys automatically13:02
sean-k-mooneyi had assumed we would use the same key we are currently using13:02
*** udesale has joined #openstack-nova13:03
sean-k-mooneyrather then create a new one but i also have not considered it much13:03
Luziwho will delete a newly created key bound to an image?13:03
Luziwell if its not exactly the same image anymore, would you encrypt it with the same key?13:04
sean-k-mooneywell for shelve we delete the image we created when unshelving13:04
Luziso there would be a point for nova to create and delete a key, that would be okay13:05
sean-k-mooneyand for cross cell resize we auto delete teh image snapthot  when we create the instnace on the dest node13:05
sean-k-mooneyso nova13:05
sean-k-mooneyyes in both cases nova could create a temperoy key and it could delete it at the correct time13:06
Luzii know that discussion from cinder and glance, there cinder creates a key which glance has to delete - that is not a good practise13:06
*** elod has quit IRC13:06
sean-k-mooneyright that is messy13:06
*** elod has joined #openstack-nova13:07
Luzisean-k-mooney, that seems good from my perspective, so automatic key creation for shelve and cross-cellresize, given a metadata parameter indicating a formerly encrypted image13:07
sean-k-mooneyyep and if that metadata paramter is not set just do what we do today13:08
Luziyes13:08
sean-k-mooneyso you can make it complete transparent to the end user and no api changes needed13:08
Luzithat sounds good, I will add this to the spec :)13:09
*** nicolasbock has joined #openstack-nova13:11
*** owalsh has quit IRC13:13
*** owalsh has joined #openstack-nova13:14
*** owalsh has quit IRC13:15
*** priteau has quit IRC13:15
*** owalsh has joined #openstack-nova13:15
lyarwoodmdbooth: https://review.opendev.org/#/c/668750/ - thoughts on this? Came across it last night while looking at upstream bugs and suddenly noticed this codepath is dead. We could just keep it but it hasn't been tested in ~3 years so it might be easier to start over with a clean volume driver.13:16
*** priteau has joined #openstack-nova13:18
mdboothlyarwood: Hmm. It doesn't sound like we're going to implement native iscsi any time soon, tbh, due to lacking multipath and no upstream motivation to implement it.13:18
mdboothMaking this just dead code which isn't like to be used any time soon.13:18
mdboothAnd which probably doesn't work anyway.13:18
mdboothlyarwood: Is os-brick based iscsi problematic?13:19
*** owalsh_ has joined #openstack-nova13:20
lyarwoodmdbooth: it has some rough edges wrt to multipath etc but the basic single path stuff also covered by this native support is QEMU is pretty solid13:20
*** BjoernT has joined #openstack-nova13:20
lyarwoods/is/in/g13:20
lyarwoodso yeah I'm fine nuking this for now and if anyone cares enough we can reintroduce it later in a broken out volume driver13:21
lyarwoodand have it actually tested in the gate etc13:21
mdboothlyarwood: +1 from me for nuking unusable code13:21
lyarwoodack thanks13:22
*** owalsh has quit IRC13:23
*** owalsh_ is now known as owalsh13:23
*** brinzhang has joined #openstack-nova13:24
shilpasdefried: Hi, need discussion on https://review.opendev.org/#/c/667952/1/nova/conf/scheduler.py@18813:25
efriedSure shilpasd13:26
efriedI'm sure we must have discussed this during the spec review13:26
shilpasdhere saying 'enable_forbidden_aggregates_filter' conf option bydefault enabled13:26
efriedIt must be about the performance penalty.13:26
shilpasdefried: but what we observed for other request filters, its not so13:26
efriedWell, this one is doing a pretty expensive db lookup every time. The other filters are (I think) exclusively local processing.13:27
*** ttsiouts has quit IRC13:27
efriedHave you done any kind of performance analysis of this filter?13:27
efriedespecially on a large database with lots of aggregates13:27
shilpasdefried: not on that large scale13:28
efrieddansmith: you were also concerned about the performance of this filter.13:29
efriedHaving thought about it some, we're better off being conservative unless we can demonstrate that the db lookup is super cheap.13:30
efriedSo - leave the conf option as is shilpasd :)13:30
efriedI'll update the review.13:30
sean-k-mooneyefried: i think all the prefilters default to false so for consitency i would keep it as false too13:31
*** avolkov has quit IRC13:31
shilpasdefried: great, thank you, we are keeping it as False13:31
sean-k-mooneyat least until we have info from deploymetns that its cheap and works well13:31
efriedsean-k-mooney: In this case I was suggesting that we remove the toggle entirely. You have to do enough other stuff to opt in, the only benefit you get by having it switched off is that you don't run the code.13:31
shilpasdsean-k-mooney: thank you for opinion13:32
sean-k-mooneyah right ok13:32
shilpasdefried: thanks for discussion13:33
efriedyw13:33
*** lpetrut has joined #openstack-nova13:34
*** francoisp has quit IRC13:39
*** _alastor_ has joined #openstack-nova13:42
gibistephenfin, efried: I'm +2 on the extra_spec validation spec https://review.opendev.org/#/c/638734 . alex_xu and bauzas had comments earlier. do we want to wait for them to chime in?13:44
stephenfingibi: alex_xu, sure, but I think bauzas is MIA now since it's summer and he's French13:44
*** ttsiouts has joined #openstack-nova13:44
*** francoisp has joined #openstack-nova13:44
gibistephenfin: OK, cool with me13:44
efriedprobably want to get sean-k-mooney to re-ack as well13:46
sean-k-mooneywhich reivew?13:46
efriedhe has the medal for most comments in a single review on that one.13:46
efriedsean-k-mooney: https://review.opendev.org/#/c/63873413:46
efriedextra spec validation13:46
sean-k-mooneyah ok13:46
sean-k-mooneyam ya that is a medal i get a little too often13:47
*** psachin has quit IRC13:47
sean-k-mooneyill quickly re review it now13:47
*** zzzeek has quit IRC13:49
efriedstephenfin: any merit in changing the topic of that spec and its patch (https://review.opendev.org/640733) to ...-extended to match the new bp?13:49
efriedI could understand if you want to keep them grouped with the old ones, as currently.13:49
efriedeither way13:49
stephenfinI'm happy with either too13:49
stephenfinso I'll leave it but won't object if you want to change it :)13:50
efriedI only glanced at the number of results https://review.opendev.org/#/q/topic:bp/flavor-extra-spec-image-property-validation+(status:open+OR+status:merged) -- no idea how related/unrelated they actually are.13:50
efriedis your work really a continuation of that?13:50
stephenfinTo be honest, not really now. It's the same idea but on a broader scale13:50
*** zzzeek has joined #openstack-nova13:51
stephenfinPerhaps I should have a totally different name. Open to suggestions13:51
stephenfinGiven that I'm not doing image metadata validation now, a new name would definitely be a good idea13:51
efriedOh, let's not go through the paperwork of changing the blueprint and stuff.13:51
efriedbut yeah, that's a point13:51
*** zzzeek has quit IRC13:53
*** zzzeek has joined #openstack-nova13:54
sean-k-mooneycool your going with my stevador suggestion for cyborge extra spec valdaditon or other services.13:55
sean-k-mooneyalmsot done13:55
*** zzzeek has quit IRC13:55
stephenfinyeah, it was a good one13:55
*** zzzeek has joined #openstack-nova13:56
efriedsean-k-mooney: I saw (but did not read) you discussing image encryption with Luzi. Where are you on that spec?13:57
efriedI noticed she added a sentence on (no) impact on lifecycle operations; is that sufficient to address your concern from the previous PS?13:57
efriedalso lyarwood: are you +1 on that? Your words imply so, but there's no vote.13:58
efriedtalking about https://review.opendev.org/#/c/608696/ btw13:58
sean-k-mooneyefried: nova should create a tempory key on shelve and encypte the snapshot if the instance image was encypted and delete the key when unshelving. same for cross cell resize13:58
Luziefried, i have to reconsider shelve and cross-cell resize13:58
lyarwoodefried: yeah sorry the comments were against an older PS so I couldn't vote13:59
* lyarwood votes now13:59
efriedokay, cool, thanks all. I'll hold off and wait for a new PS13:59
*** BjoernT_ has joined #openstack-nova13:59
sean-k-mooneyeither that or we need to expsoe it on the shelve/resize api endpoint for the end user to decide13:59
*** mriedem has joined #openstack-nova13:59
openstackgerritDakshina Ilangovan proposed openstack/nova-specs master: Spec: Provider config YAML file  https://review.opendev.org/61249714:00
efriedsean-k-mooney, Luzi: But that changes everything.14:00
openstackgerritMatt Riedemann proposed openstack/nova stable/queens: Init HostState.failed_builds  https://review.opendev.org/66891114:01
sean-k-mooneyefried: what changes everything? auto encypte or api endpoint or both14:01
efriedAuto encrypt: As previously written, you didn't keep track of whether a server was originated from an encrypted image. Now you would have to.14:01
efriedAPI endpoint: now you need a microversion (right?)14:01
sean-k-mooneyyes14:02
sean-k-mooneytoo ^ we would need a microversion14:02
*** BjoernT has quit IRC14:02
sean-k-mooneynot sure about keeping track of if it was encypted14:02
sean-k-mooneyi think Luzi said there was a metadta key on the image/instance14:03
efriedI thought the spec said we forget about that.14:03
sean-k-mooneyi assume it would be in the embeded copy of hte image meta we store in the request spec14:03
efried"...the encryption-related14:04
efriedadditional metadata properties become irrelevant and thus may be discarded14:04
efriedinstead of being carried over into the server's metadata."14:04
Luziefried, i thought so until sean-k-mooney asked me, we misinterpreted the word snapshot14:04
efriedI'm on the fence about whether it's better to encrypt automatically or on-demand when doing things involving snapshot.14:06
efriedbut it seemed reasonable as written (on-demand)14:06
efriedand simpler14:06
sean-k-mooneyeither would be ok. what i dont think is ok would be that shelve and cross cell resize alway result in unencypted snap shots with no way to encyrpte them14:06
efried(cross-cell resize creates a snapshot?)14:07
sean-k-mooneyso if we do the microversion bump or auto encypt i think both are fine14:07
sean-k-mooneyefried: yes14:07
efriedokay14:07
sean-k-mooneyefried: for corss cell resize we can rely on direct connectivity to the host14:07
*** BjoernT_ is now known as BjoernT14:08
efriedif we auto-encrypt, then we should do the same for the already-considered snapshot case (createImage)14:08
efriedi.e. it should be symmetrical.14:08
Luziefried, and that cannot happen14:08
efriedbut that would require a key...14:08
*** mrch_ has quit IRC14:09
Luzibecause the new key would be generated in nova and is then used in glance, which doesn't delete the key in the case a user deletes the image14:09
openstackgerritLee Yarwood proposed openstack/nova master: block_device: Optionally recreate attachments when refreshing connection_info  https://review.opendev.org/57900414:09
efriedLuzi: I assume saving the *original* key with the server metadata is a nonstarter.14:10
efriedlike taping your car keys to the fender14:10
Luziwell the key could have been deleted at the point14:11
sean-k-mooneyLuzi: how?14:11
Luzibecause it was just tied to the original image14:11
stephenfinNewb question: when I'm told to delay string interpolation by doing "LOG.warning('foo %s', 'bar')" instead of "LOG.warning('foo %s' % 'bar')", what actually resolves that?14:11
sean-k-mooneydose the instance not have a key associated to it14:11
stephenfinIs it a feature of the logging library14:12
Luziif the original image is deleted, the key can be deleted too14:12
sean-k-mooneyfo use in its encyped ephmeral disk14:12
stephenfinor the translation framework?14:12
Luzibut that would only be the case if we use a backend which supports ephemeral storage encryption14:12
sean-k-mooneyah right14:13
Luziceph right now doesn't - maybe a nice thing to look for in the future :D14:13
stephenfinI ask because we appear to be delaying interpolation here but I didn't that was supported for exceptions https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L5842-L584714:13
stephenfinSo I'm guessing it's a minor bug14:13
sean-k-mooneyyes native encyption fo ceph rbds would be nice at somepoint14:14
efriedstephenfin: yes that looks like a bug14:14
stephenfinokay, phew. I'll fix14:14
*** ivve has quit IRC14:14
*** tbachman has quit IRC14:16
sean-k-mooneyLuzi: efried so if we cant make auto encyption symetric for normal snapshoting those that make it a non starter in your minds14:16
*** ricolin has quit IRC14:16
sean-k-mooneyi would personlally prefer teh asymatry to give a better user experince and be secure by defualt14:17
efriedstephenfin: http://paste.openstack.org/show/753821/14:17
efriedyour exception message winds up being a %s-ification of a tuple of a string and a dict.14:17
stephenfinefried: I did the exact same thing :) However, I wasn't sure if the i18n marker changed things14:18
efriedoh, definitely not, it returns a string14:18
*** munimeha1 has joined #openstack-nova14:18
efriedThe marker can't see the stuff after the comma.14:18
stephenfinSweet, so it is logging that does the delayed interpolation. Good to know I hadn't been mistaken all these years, heh14:18
efriedyes, logging does delayed, because it's conditional. The exception is always happening (if you get to that point), so there's no reason to delay anything.14:19
*** jaosorior has quit IRC14:20
*** tbachman has joined #openstack-nova14:34
openstackgerritKashyap Chamarthy proposed openstack/nova master: libvirt: Remove MIN_{QEMU,LIBVIRT}_LUKS_VERSION  https://review.opendev.org/66892414:35
openstackgerritDakshina Ilangovan proposed openstack/nova-specs master: Spec: Provider config YAML file  https://review.opendev.org/61249714:36
openstackgerritBalazs Gibizer proposed openstack/nova master: Translatable output strings in heal allocation  https://review.opendev.org/66892514:39
*** tbachman has quit IRC14:39
*** tbachman has joined #openstack-nova14:49
*** igordc has joined #openstack-nova14:50
*** bnemec has quit IRC14:50
adriancstephenfin, efried, thanks for taking the time to review14:51
adrianc[FUP] Follow-up patch for SR-IOV live migration14:51
efriedyw adrianc14:51
efriedhope the minor updates were acceptable14:51
*** factor has quit IRC14:51
adriancsure thx for uploading the new PS14:52
*** factor has joined #openstack-nova14:52
*** brinzhang has quit IRC14:55
*** Luzi has quit IRC14:58
*** icarusfactor has joined #openstack-nova15:00
*** brinzhang has joined #openstack-nova15:00
*** factor has quit IRC15:00
*** mriedem has left #openstack-nova15:05
*** mriedem has joined #openstack-nova15:05
cdentefried: I've been waiting for you +1/2 on https://review.opendev.org/#/c/612497/ before reviewing it, assuming until it meets your expectations it wasn't worth the effort. So I'll probably get to it tomorrow morning...15:08
efriedcdent: I'm working through it (again) now.15:08
efriedyour input would be valuable at this stage anyway, but I understand wanting to wait until the dust settles a bit.15:08
cdenti've also already crested my 8 hour limit aleady today (was up early to work with some folk in china), so unless I get an afflatus this evening, it'll be manana15:10
*** tssurya has quit IRC15:11
*** cdent has quit IRC15:11
kashyapjohnthetubaguy: Ping^2, maybe now you're about :-) -- Want to get the Secure Boot spec across the line? -- https://review.openstack.org/#/c/506720/ )15:12
*** tbachman has quit IRC15:13
*** priteau has quit IRC15:14
efriedapparently cdent should stock bean-o15:14
dansmithmriedem: I think I could probably slam your experimental job add patch amirite?15:18
*** hoonetorg has quit IRC15:20
mriedemthe ovs hybrid plug one? yeah.15:20
*** brinzhang has quit IRC15:21
*** liuyulong has joined #openstack-nova15:22
dansmithmriedem: yeah15:22
dansmithso slammed.15:23
*** tbachman has joined #openstack-nova15:23
bauzasefried: gibi: johnthetubaguy: any reason why https://review.opendev.org/#/c/638734/8 wasn't +W yet ? I'm also cool with it, so I wonder why we hold it15:28
efriedbauzas: We're waiting for alex_xu to re-ack at this point.15:28
bauzasack, thanks15:28
*** priteau has joined #openstack-nova15:28
bauzaswe basically already agreed on it at the PTG15:28
bauzasso I'm not sure why we need to wait more but okay :)15:29
*** bnemec has joined #openstack-nova15:29
bauzasthe key part of the validation would be more controversial15:29
bauzasbut just checking the value looks just cool and simple15:29
bauzasefried: ^15:29
bauzasI mean, plain simple15:29
*** sridharg has quit IRC15:29
bauzasfrom a spec perspective, we can nitpick on the implementation tho15:30
*** liuyulong has quit IRC15:30
*** ttsiouts has quit IRC15:30
efriedI'll go ahead and merge it.15:30
*** ttsiouts has joined #openstack-nova15:31
bauzascool15:31
*** gyee has joined #openstack-nova15:31
efriedstephenfin: assuming you didn't want to change the bp name?15:31
efried...which I just realized isn't in the commit message, ima fix that quick.15:31
openstackgerritEric Fried proposed openstack/nova-specs master: Add 'flavor-extra-spec-image-property-validation-extended' spec  https://review.opendev.org/63873415:32
efriedf15:32
efriednow ima fix it right15:32
openstackgerritEric Fried proposed openstack/nova-specs master: Add 'flavor-extra-spec-image-property-validation-extended' spec  https://review.opendev.org/63873415:33
*** hoonetorg has joined #openstack-nova15:33
*** icarusfactor has quit IRC15:34
*** factor__ has joined #openstack-nova15:34
efriedstephenfin: I went ahead and made those topic changes https://review.opendev.org/#/q/topic:bp/flavor-extra-spec-image-property-validation-extended15:35
*** ttsiouts has quit IRC15:36
stephenfinefried++ thanks :)15:36
stephenfinThat WIP probably needs to be abandoned since we've gone a totally different direction, but that's a job for later this week/next week15:37
*** factor has joined #openstack-nova15:38
*** factor__ has quit IRC15:39
*** jangutter has quit IRC15:42
openstackgerritEric Fried proposed openstack/python-novaclient master: Modify the url of upper_constraints_file  https://review.opendev.org/66593415:43
*** udesale has quit IRC15:45
efriedmriedem: cross-cell resize got no love this runway slot?  :(15:45
efriedmove back into queue, yah?15:46
mriedemefried: it got some love from gibi and dansmith but yes i have some comments to address from gibi and need to re-queue15:47
efriedight15:47
mriedemare you going to update the etherpad?15:47
mriedemnvm i'll do it15:51
*** tbachman has quit IRC15:51
*** tbachman has joined #openstack-nova15:52
openstackgerritMerged openstack/nova-specs master: Add 'flavor-extra-spec-image-property-validation-extended' spec  https://review.opendev.org/63873415:55
mriedemgerrit is being restarted15:56
efriedthanks15:57
openstackgerritBalazs Gibizer proposed openstack/nova master: Mova consts from neutronv2/api to constants module  https://review.opendev.org/66894515:58
openstackgerritBalazs Gibizer proposed openstack/nova master: Use neutron contants in cmd/manage.py  https://review.opendev.org/66894615:58
openstackgerritBalazs Gibizer proposed openstack/nova master: Add 'resource_request' to neutronv2/constants  https://review.opendev.org/66894715:58
*** cfriesen has joined #openstack-nova15:58
mriedemgibi: fyi i'm going through the heal allocations change now15:59
mriedemand thanks for hitting the disabled compute series so fast15:59
*** markguz_ has joined #openstack-nova15:59
gibimriedem: thanks. Above is the fup I promised to move to use contants instead of string for 'binding:profile' and the rest16:00
gibimriedem: disabled compute seemed an easy hit, and also I was vocal in the spec so I felt responsible16:01
gibimriedem: I need to drop soon so I will get back to your comments (if any) on the heal port allocation tomorrow16:04
mriedemyup np16:07
*** hemna has quit IRC16:08
*** hemna has joined #openstack-nova16:09
openstackgerritSylvain Bauza proposed openstack/nova-specs master: Proposes NUMA affinity for vGPUs  https://review.opendev.org/65096316:14
*** rpittau is now known as rpittau|afk16:14
bauzasdansmith, efried: thanks for reviewing ^, I just provided some new revision with more explanation about upgrades16:14
bauzasefried: I understand your concerns about this being a legacy mechanism and the fact that we approved the placement nested magic spec, so it could be seen as competitive16:15
bauzasefried: but what I'm trying to explain is that my spec isn't competing with NUMA be modeled in placement, as it just provides a soft affinity check that can still be done once NUMA is modeled with placement16:16
bauzaseven the object change16:16
bauzasso we can keep it, and drop it when we want16:16
openstackgerritMartin Midolesov proposed openstack/nova master: Implementing graceful shutdown.  https://review.opendev.org/66624516:25
*** priteau has quit IRC16:28
*** qqmber has joined #openstack-nova16:30
*** damien_r has quit IRC16:30
*** munimeha1 has quit IRC16:31
qqmberhi... since today when I attach a volume (cinder volume), horizon shows that it is attached to the instance (Centos 7). If I run "nova show ID", shows the new volume's ID, but nothing happens on the instance... if it supposed to be in /dev/vdd, I run "sudo dmesg | grep vdd" nothing is shown (inside the instance). Any ideas where should I look for the problem?16:32
*** bnemec has quit IRC16:45
*** mvkr has quit IRC16:47
*** mvkr has joined #openstack-nova16:50
sean-k-mooneyqqmber: what does lsblk show16:59
sean-k-mooneyqqmber: the name you specified is not garunteeded to be the one it gets16:59
qqmberin Nova host or the instance?16:59
sean-k-mooneyin the instance16:59
qqmberok16:59
qqmbersean-k-mooney: not vdd there.. only vda and vdb (vdc is another story)17:00
sean-k-mooneyif the attach succeeded i woudl expect tehre to be a new block device that is not mounted but it might have a different name17:00
qqmberI just sent you what I got17:01
*** davidsha has quit IRC17:02
*** markvoelker has joined #openstack-nova17:02
*** factor has quit IRC17:03
*** openstackgerrit has quit IRC17:04
*** elod has quit IRC17:05
*** elod has joined #openstack-nova17:07
*** bnemec has joined #openstack-nova17:14
*** lpetrut has quit IRC17:16
*** ociuhandu has quit IRC17:26
dansmithefried: can you save me some reading and summarize the opinion on bauzas' gpu numa spec17:39
dansmith?17:39
*** markguz_ has quit IRC17:39
dansmithlike, are you saying that we're really far enough along to fully model (and reshape to) gpus under numa nodes with allocation candidates during scheduling to not do any of what he prescribes?17:40
dansmithstoring the child providers in the numa object and a weigher to look at it seems like (a) it might be useful for other things and (b) a weigher isn't a huge amount of debt17:40
dansmithlike, I can imagine the "show me the instance topology" thing might use some info in that child object to construct a view of where your assigned gpu (or something else) fits into the topop17:41
*** tbachman has quit IRC17:42
*** igordc has quit IRC17:45
*** luksky11 has quit IRC17:46
efrieddansmith: We're talking about coding a weigher that would provide a subset of the capability, and be 100% obsolete when we do placement-based topo modeling & affinity.17:56
efriedreading material, like the placement side specs & patches?17:56
dansmithefried: even if placement returns an AC with hierarchical allocations for the proper gpus, we'd still have weigher activity to decide which of those we want right?17:58
*** tbachman has joined #openstack-nova17:58
efriedwhat would we be weighing in that case?17:58
efriedlike, what's a use case where "pick the first one" isn't right.17:58
dansmithefried: there is always a decision to be made about which allocation we want right?17:58
sean-k-mooneywe are weighign host that can fufile numa affitny above those that cant17:59
*** BjoernT has quit IRC17:59
dansmithplacement may return two ACs, one where the gpu is on a node with the minimum amount of memory, and one where there's a bunch extra, and a weigher would choose the latter I would think18:00
dansmithor the weigher would opt for the AC with the best combination of cpu, memory and gpu, especially where there are more than one gpu and you want as even of a distribution as possible18:00
sean-k-mooneythe other usecase for the weigher would be to avoid placeing instace on a host with a gpu if they did not request one18:01
efriedI thought bauzas's spec proposes that we binarily weigh "satisfies affinity requirements" higher than "doesn't"18:01
sean-k-mooneyby weighering them lower18:01
dansmithsean-k-mooney: that's what bauzas' proposed weigher is doing yeah, but I'm saying that may evolve to something still useful after placement is returning ACs with gpu elements18:01
sean-k-mooneywe do that in the pci weigher i think18:01
sean-k-mooneyright18:01
efriedI'm certainly not saying there's no value in a weigher18:01
sean-k-mooneywhen modeled in placmenet if we have two AC on the same host it coudl weigh the ACs based on some other parmater18:02
efriedbut weighing "satisfies affinity requirements" is a thing we can do very soon with placement, if we're willing to put the work in it.18:02
dansmithI'm just saying I expect that the bones of the proposed weigher would still be useful after placement is returning more data18:02
dansmithefried: and also, we've been on the verge of being able to do this for a while, so it's easy to never move forward on a sub-optimal approach in favor of something else that never comes,18:03
dansmithso if there's something re-usable about this after the better thing comes, I'm not as concerned about the "100% debt after merge" concern18:03
efriedokay, so let's talk about how close we are to being able to move forward:18:03
sean-k-mooneyi see tetsuro pushed up https://review.opendev.org/#/c/668376/ on monday but he has -w it so i assume it still have more work to do.18:05
efriedFor NUMA we need18:06
efriedrg-to-rp mappings (implemented, microversion 1.34) https://docs.openstack.org/placement/latest/specs/train/approved/placement-resource-provider-request-group-mapping-in-allocation-candidates.html18:06
efriedand pieces from https://docs.openstack.org/placement/latest/specs/train/approved/2005575-nested-magic-1.html as follows18:06
efriedarbitrary group suffixes (implemented, microversion 1.33)18:06
efriedsame_subtree + resourceless request groups (https://review.opendev.org/#/c/668376/ -W as sean-k-mooney says, but pretty close)18:06
efriedand then obviously we have to do the things in nova to 1) reshape and 2) request accordingly.18:06
dansmithyeah the reshape is what I'm concerned about.. that delaying us another cycle18:06
efriedI feel it is very well understood what 1 and 2 will look like.18:07
sean-k-mooney1 is https://review.opendev.org/#/q/topic:story/2006068+(status:open+OR+status:merged) right18:07
dansmiththose are all placement,18:07
dansmiththe reshape is in nova18:07
sean-k-mooneyoh ya but the reshap cant happen until the placment stuff is done18:08
dansmithsure, just being clear18:08
dansmiththe reshape is more complicated (IMHO, and IME), so unless that's "close" I'd be more concerned18:08
sean-k-mooneyim not sure we fully underdand what the reshap will looklike18:08
efriedyeah, those are a minor bugfix for rg-to-rp mappings. Really only cdent's is needed, the rest are what-ifs.18:09
efriedThe nested magic spec has several examples of what the topo will look like18:09
dansmithI think knowing what it will look like is not so much the problem18:09
efrieddeciding which resources need to go where?18:10
sean-k-mooneyyes18:10
dansmiththe actual mechanics of doing the reshape.. I know it's doable and we know what the end result will look like18:11
sean-k-mooneyfor exampel i think cpus are going to need to be moded in a nested resouce provider of the numa node not as an inventory of the numa node18:11
sean-k-mooneyhugepages should proably be on the numa node but as a new resouce class per pagesize or as somthign else?18:12
dansmithefried: case in point ^ :)18:12
sean-k-mooneydose memroy_mb stay on the compute resouce proveiider?18:12
dansmithstill plenty of discussion to derail the reshape18:12
dansmithefried: anyway, I think you oughta make a clear decision on this point, and -2 bauzas' thing if so, so that the messaging is clear what to expect and focus on18:15
dansmithI'm not saying that's a terrible thing, I just think it's not terrible to continue with both18:16
dansmithobviously I want the pure-placement approach for all the right reasons18:16
efried"not terrible to continue with both" is why I haven't downvoted18:17
dansmithokay18:17
efriedbut "want the pure-placement approach" is why I haven't upvoted.18:17
efriedWho's going to work the code for bauzas's spec.18:17
efried?18:17
sean-k-mooneybauzas:18:17
dansmithum, bauzas I hope :D18:17
sean-k-mooneyassumign its approved if not he will bw working on other things18:18
dansmithmriedem: any thoughts on this? if you and efried are both -0.9 then it's probably not worth expecting it to happen18:18
efriedIf that person were dedicated instead to working on the topo reshape, that would get us closer18:18
efriedfaster18:18
efriedeven if it doesn't all come together in train.18:18
efriedwhereas I'm not sure what we gain by having the separate weigher.18:19
sean-k-mooneywe get numa support for gpus in trian which will be the basis of our next longer support release donwstream18:19
dansmiththe weigher gets us a lot closer to the correct behavior with a minimal amount of code and pretty predictable amount of work18:19
dansmithit doesn't get us to perfection, obviously18:19
efriedcloser to the correct behavior... for just vgpu, right?18:20
dansmithwell, the bulk of this is reusable for other child devices,18:21
sean-k-mooneywe already do the right thing for pci pasthough18:21
sean-k-mooneyand for hugepages and cpu pinning18:21
dansmithalthough I expect the weigher would probably be specific to gpus18:21
efriedother child devices - that we don't model in placement yet18:21
efriedso n/a?18:21
efriedand please let's not start modeling devices in non-NUMA-aware placement and adding weigher code to do the NUMA stuff for that.18:22
dansmithefried: other things we hang off of the compute RP that aren't specific in placement, but yeah, nothing pending, just saying this isn't adding a bunch of stuff to do gpu-specific things18:22
sean-k-mooneywe dont track them in plamcneet and can provide better placmente and affintiy because of that18:22
efrieduntil we track them *properly* in placement, right.18:22
*** BjoernT has joined #openstack-nova18:22
sean-k-mooneywhich has been promsied for 2 years at this point18:23
efriedgood, so let's get it the f done instead of keep kicking it down the road18:23
dansmithefried: just FYI I hate myself for even arguing about this, because pure-placement is obviously the right way, I'm just hedging because of the pain of things not actually being in train18:23
dansmithbecause seriously... years.18:23
efriedI've said before (or maybe just thought it) vgpu may have been nice as a foot in the door proving device modeling in placement, but premature. And now we're trying to retrofit to make it work instead of shelving it until we can make the infrastructure support it properly.18:24
efriedbut18:25
efriedI still don't feel strongly enough to block18:25
sean-k-mooneyefried: for context the CAT stuff im working on here https://review.opendev.org/#/c/662264/ which you would also like me to track only with numa awer placment was requested for pike18:25
dansmithif we didn't have basic gpu stuff that we have today at this point, I think we'd probably be having a much different conversation.. and not a fun one.18:25
*** amodi has quit IRC18:25
efriedTell ya, though, if sam_subtree lands pretty soon, as appears likely to do, that may be enough to make me -1 the vgpu affinity spec.18:26
dansmithI thought you were the "don't wait forever for perfect" guy? :)18:26
efriedTotally. And I have no illusions that numa-in-placement will be perfect right away18:26
dansmithwell, if you think that's going to happen, you should just preemtively -1 it, or18:27
efriedwhich btw is why we should not be arguing about hugepages and splitting CPUs finer than per-numa-node.18:27
dansmithor -1 it contingent on that merging when you think it will18:27
dansmithbecause really, messaging the likelihood of this being a thing is pretty important to us18:27
*** _erlon_ has quit IRC18:28
efriedand why we punted on can_split18:28
efried"messaging the likelihood of this being a thing" is actually the best argument I've heard so far.18:28
dansmithit's the most important I think18:29
sean-k-mooneywell if we cant have memory fine then a numa node we can implemenat CAT18:29
sean-k-mooneythe cpus inventories and cache inventores shoudl be in the same RP18:30
sean-k-mooneyand cache regins are finer then numa node18:30
sean-k-mooneywe can have mulplie l3 cache regins in the same numa node18:30
efriedunderstood.18:30
efriedSo18:30
sean-k-mooneyit would basicaly be a 3 level tree18:31
efriedwhen we implement CAT *after* having implemented NUMA topo as its own thing, we can reshape the CPUs and L3s down into grandchild providers.18:31
sean-k-mooneyyes we could18:31
efriedbut we should not be trying to solve CAT preemptively.18:32
sean-k-mooneyor we could do that first and reshap them under the numa node when they are added18:32
*** shilpasd has quit IRC18:32
efriedI owe you a response in the pqos spec, but that doesn't buy us anything at this point.18:32
sean-k-mooneywe talked about it a little today in our squad call18:32
sean-k-mooneyim going to simplfy it and proably add a depency on some of the placmenet stuff18:33
sean-k-mooneyi will likely make memory bandwith depend on the numa in placment spec18:33
sean-k-mooneyi would like to keep cache not depenent on tha tbut may on same tree18:33
sean-k-mooneywell it depends i have to see  is there a way to us more of the plamcent stuff18:34
sean-k-mooneyit significantly incresase the risk we wont have CAT in train however18:35
*** artom|gmtplus3 has quit IRC18:35
*** ralonsoh has quit IRC18:35
efriedI'm addressing similar concerns in the providers.yaml spec18:35
sean-k-mooneyill admit i have nto really been following that one. i kindof got burt out on that topic last cycle18:36
sean-k-mooneyis it approching agreement or still in flux18:37
efriedDakshina has me convinced that there's a reason to do cache in child providers. But only to ensure that one request group gets all its cacheways from one package -- *not* because we can do anything about affinity.18:37
efriedhowever18:37
efriedin tree18:37
efriedwe can do affinity after GET /a_c via the NUMATopologyFilter18:37
efriedwas gonna say that couples the filter to libvirt, but that's already dismally true anyway.18:39
efriedsean-k-mooney: I haven't posted those comments yet, but will ping you once I have.18:40
sean-k-mooneyok. im goign to leave the rebasing it so that we can continue the disucssion in one place18:41
sean-k-mooneyare you off for the 4th of july weekend?18:41
sean-k-mooneyi assume yes18:41
efriedand dansmith, I'll review tetsuro's same_subtree patch. I have the broad strokes from an earlier iteration, but it's now been squashed and reworked a little bit, so I need to refresh and see how far off it still is. And if it's as close as I think, I'll take a stand on the vgpu affinity spec.18:41
dansmiththanks18:42
efriedsean-k-mooney: yes, I'll be off Th & F18:42
efriedFriday is my 22nd anniversary :)18:42
*** luksky11 has joined #openstack-nova18:42
dustincefired: congrats!18:43
sean-k-mooney22nd, surly not wedding? unless you were married quite young18:43
dustincefried..18:43
sean-k-mooneyas in before its legal.18:44
efriedhehe. I was married at 2018:44
*** tesseract has quit IRC18:44
efriedso it was legal to marry, just not legal to buy alcohol :P18:44
efriedthanks dustinc18:44
sean-k-mooneywell congrats and i always get confused about how the us legislates for mimium ages for things18:45
efriedyou're not the only one18:45
dustinccan active duty still buy beer/wine at 18 on base?18:46
dustincgets even more confusing18:46
efried21 for alcohol is country-wide at this point. Louisiana was (I think) the last one to capitulate in the late '90s (from 18) when the fed cut off their road funding.18:46
sean-k-mooneyyou can drive from 16 and get a gun licence at 16 or 18 right and marry at like 16-18 depending on the state18:47
efriedsean-k-mooney: I grew up near London, where the official age was 18 but not enforced at all. I was pubbing from 14.18:47
sean-k-mooneyand vote at 18 too right18:47
dustincthe problem with voting here is you can vote at 18 but nobody does until 60 sigh...18:48
efriedvote at 18, yes, that was a big deal ~20y ago. Driving depends on the state, but it's 16 in most places. You can get an exception for "hardship" or farming (which are the same thing to me :P )18:48
efriedthat's not a problem18:48
efriedthe problem with voting is that you are allowed to do so despite being completely ignorant18:48
dustincthat doesn't change with age18:48
efriedswhat I'm sayin.18:48
dustincgotcha :)18:49
dustincvoting is really complicated in some states too18:49
sean-k-mooneyya you can get a work vechles lices that allows you do drive a tracker or combin haveser at 16 in ireland but need to be 18 to get a car license which is ... odd18:49
dustincmy state votes by mail, others you have to stand in line for hours18:49
dustincdo you have graduated licensing for motorcycles?18:50
sean-k-mooneyyes18:50
dustincwe get 18 year olds buying a 1000cc for their first bike here18:50
dustincso annoying18:50
sean-k-mooneyhttp://www.rsa.ie/Documents/Learner%20Drivers/Third%20Directive/bikes_chart_3rd_directive_V2.pdf18:51
efriedIn the UK didn't they pass a thing where you have to have a decal of some sort for the first year after you get your license, so other motorists are warned that you still suck?18:51
sean-k-mooneyhttp://www.rsa.ie/en/RSA/Learner-Drivers/Motorcyclists/Licence-categories-explained/18:51
sean-k-mooneyefried: thats in ireland18:52
sean-k-mooneyyou have N placnete for novice18:52
sean-k-mooney*plates18:52
sean-k-mooneyi like the metric system but i really dont understadn inutitivly how much 11KW is vs horsepower18:53
dustincabout 14hp according to google..dunno how you can even get around with so little18:54
dustinca common starter bike here is 250cc twin and they make around 35hp I think18:55
dustincand are sooo slow18:55
sean-k-mooneywhat does a 125cc engin normally put out18:55
dustincnot sure, guessing 11kw/14hp is probably pretty typical18:55
dustincwe just don't have many street-legal 125cc here18:55
sean-k-mooneyya that is the smalest license you get when your 1618:56
sean-k-mooneyso its mainly scotters and dirt bikes18:56
sean-k-mooneythat said i was not expecting thise to qualify https://www.bennetts.co.uk/bikesocial/news-and-views/advice/new-riders-and-training/top-10-a1-licence-friendly-bikes-201818:57
dustincit should be that way here, maybe start at 250cc since 125cc is hard to find, but people starting out on 110hp 600cc sport bikes (or worse...180-200hp liter bikes) is common and causes lots of accidents..and then expensive insurance and stupid laws18:57
sean-k-mooneyi guess you really dont need the same level of raw horse power vs a car. anyway i better finish up my email and sign off for the evening o/18:59
dustincyou guys get some cool little bikes there...19:00
sean-k-mooneyunfortunetly i dont have a bike license so cant ride any of them19:00
sean-k-mooneyi have though about getting it but mainly since i never drive my car and have been thinink of gettin rid of it but still should have somthing19:01
qqmbersean-k-mooney: I just ceated a new instance and in this one worked (attaching a new volume)... Crap... maybe the instance is screwed :(19:02
sean-k-mooneyqqmber: it might be related to your iscsi backend19:03
sean-k-mooneydo you have issue conencting to it form other vms on the same host19:03
qqmberthat's what I'll try now19:03
sean-k-mooneyyou could also try moving the vm to anohter host and see if that fixes it19:04
*** maciejjozefczyk has quit IRC19:04
sean-k-mooneybut it could be that its not propely exported19:04
mriedemdansmith: efried: i was out getting my quarterly sheering, do i need to weigh in on this numa affinity spec thing? b/c i don't really want to.19:04
mriedem*shearing19:04
mriedemsorry19:04
efriedmriedem: Apparently we all have to take a stand one way or another, or dansmith won't be our friend anymore.19:05
dansmithmriedem: if you want, but I think I nudged efried in enough of a direction that it won't matter19:05
efriedwait19:05
*** igordc has joined #openstack-nova19:05
mriedemi haven't reviewed the latest updates on sylvain's spec19:06
dansmithefried: not all of us, just you (have to take a stand)19:06
mriedemnor do i really have much skin in this game19:06
mriedemdoes france vacation season end before or after FF....19:08
dansmithdoes it end...at all?19:09
mriedemtouche19:10
mriedemfyi for anyone following along, there is 1 queens change to merge https://review.opendev.org/#/q/status:open+project:openstack/nova+branch:stable/queens+label:Code-Review=2 and then i'll be doing a release19:11
*** whoami-rajat has quit IRC19:12
sean-k-mooney i was expecting that to auto merge whne the parent did19:12
qqmbersean-k-mooney: one (maybe) important point... the instance with the (apparent) problem was migrated from one host to another (I shutdown the instance first)19:12
mriedemsean-k-mooney: it would have if not for gate failures19:12
sean-k-mooneymriedem: ya i just clicked in an notice the job that failed faild before the test ran19:13
sean-k-mooneyqqmber: did you confimr the migration19:13
sean-k-mooneyif not the instace might still be pointing at the source node.19:14
* sean-k-mooney goes to check19:14
qqmberyes, I did19:16
qqmberis there any way to confirm that? (I'm 99.9999999% sure I did)19:17
sean-k-mooneyok i was just wondering if the instace.host could still be set to the old host19:17
sean-k-mooneywhich would likely mess up attaching new volumes19:17
qqmberthis instance had 2 volumes before the migration... after the migration one volume "died" (maybe because of the current problem), and now I'm not able to attach new ones...19:18
sean-k-mooneyis the dead volume form the same cinder backend as the one that does not show up19:19
*** markvoelker has quit IRC19:19
*** markvoelker has joined #openstack-nova19:19
sean-k-mooneydansmith: by the way for atroms revert resize change you want to avoid the api change by doing the db lookup as mriedem and i were discussing and then have the followup patch on master change to passing the migration object down and remvoe the db lookup right19:21
dansmithsean-k-mooney: I19:21
sean-k-mooneycool19:21
dansmithsean-k-mooney: I'm fine with doing the one thing and backporting it, but mriedem is not, so then yes, those two steps19:21
sean-k-mooneyi kind of prefered that too but was not sure how you would feel about the extra db query19:22
*** cfriesen has quit IRC19:22
dansmithsean-k-mooney: IMHO, backporting the interface change is not a problem, so we could avoid the lookup and the two-step dance19:22
dansmithbut mriedem wants the interface to be stable, which is also fine19:22
dansmithwhat I'm not okay with is the duck typing on our internal interface19:23
mriedemwe'll have a two step either way (to remove the TypeError handling)19:23
sean-k-mooneyyep19:23
dansmithmriedem: I'm not okay with the typeerror either.. like, at all.19:23
*** mrch_ has joined #openstack-nova19:23
dansmithmriedem: we don't need it though, because it's all an internal interface.. we could just pass the thing in and change all the drivers, and backport that19:23
sean-k-mooneywell the type error handeling is for oot drivers19:23
dansmithsean-k-mooney: right, which I don't care about at all19:24
sean-k-mooneywhich i know we technicaly dont support19:24
mriedemi only really care here b/c of backports19:24
mriedemif it weren't being backported i'd just say change the interface19:24
mriedemi'm not losing sleep over this though19:24
sean-k-mooneyok im just trying to make sure we know what to change while both of ye are on vacation for the next two days19:24
dansmithright, but I don't get why the backport matters, since this is all inside nova-compute, except for the OOT drivers, which .. I don't care about19:25
dansmithbut whatever19:25
mriedemoh i'm here friday19:25
dansmithme too19:25
sean-k-mooneyoh ok19:25
mriedemi am, however, gone the entire week of the 15th19:25
mriedemwith no laptop19:25
dansmithso wait until the 15th and then we merge? :D19:25
mriedemand the revert on the 16th? sure.19:25
dansmithgeg19:25
dansmither, heh19:26
sean-k-mooneyi mean its only merged once 3 times the charm right19:26
mriedemi really look forward to having to eyeball the diff yes19:27
*** eharney has quit IRC19:27
sean-k-mooneyso to sumerise do the two step dance with the db lookup to minimes the backport size19:28
dansmithyes19:29
sean-k-mooneycool19:29
*** whoami-rajat has joined #openstack-nova19:29
sean-k-mooneyok im catully going to drop for the evenying enjoy tommorow o/19:30
*** igordc has quit IRC19:31
*** openstackgerrit has joined #openstack-nova19:34
openstackgerritMerged openstack/python-novaclient master: Modify the url of upper_constraints_file  https://review.opendev.org/66593419:35
openstackgerritMatt Riedemann proposed openstack/nova master: Follow up for pre-filter-disabled-computes series  https://review.opendev.org/66898619:56
efriedsean-k-mooney: I posted that review. The part that pertains to what we were discussing earlier (child providers for LLC) is here https://review.opendev.org/#/c/612497/4/specs/train/approved/provider-config-file.rst@10919:56
efriedsean-k-mooney, dansmith: That spec is probably close enough for y'all to start looking at now. https://review.opendev.org/#/c/612497/19:57
*** damien_r has joined #openstack-nova19:57
efriedThere's still work to be done, as noted, but it's in a place where there are no longer *major* issues that I am seeing. So a good time for *you* to identify major issues :)19:57
mriedemthis all looks dead https://review.opendev.org/#/q/topic:bp/add-emulated-virtual-tpm+(status:open+OR+status:merged)20:03
*** eharney has joined #openstack-nova20:04
*** hemna has quit IRC20:27
*** hemna has joined #openstack-nova20:27
*** jaypipes has quit IRC20:34
*** trident has quit IRC20:43
*** trident has joined #openstack-nova20:45
*** xek has quit IRC20:47
*** damien_r has quit IRC20:55
*** _alastor_ has quit IRC20:59
efriedmriedem: as in, been in merge conflict for a while, or as in, you looked at the code and it doesn't seem like it matches the spec etc?21:08
mriedemformer21:11
mriedemi feel my abandon finger itching21:11
*** slaweq has quit IRC21:11
*** igordc has joined #openstack-nova21:14
*** pcaruana has quit IRC21:16
efriedmriedem: We reapproved that spec for this release (in April). Go abandon something *really* old.21:21
mriedemblarg21:24
openstackgerritEric Fried proposed openstack/nova master: Fix GET /servers/detail host_status performance regression  https://review.opendev.org/66604221:26
*** slaweq has joined #openstack-nova21:27
*** slaweq has quit IRC21:32
*** slaweq has joined #openstack-nova21:38
openstackgerritMerged openstack/nova master: [FUP] Follow-up patch for SR-IOV live migration  https://review.opendev.org/65910121:41
openstackgerritMerged openstack/nova stable/stein: Stabilize unshelve notification sample tests  https://review.opendev.org/66880621:42
openstackgerritMerged openstack/nova master: Follow-up for I6a777b4b7a5729488f939df8c40e49bd40aec3dd  https://review.opendev.org/66496721:42
*** slaweq has quit IRC21:43
*** takashin has joined #openstack-nova21:51
*** rcernin has quit IRC22:04
*** qqmber has quit IRC22:11
*** bbowen has quit IRC22:15
*** _alastor_ has joined #openstack-nova22:17
*** whoami-rajat has quit IRC22:42
*** tbachman_ has joined #openstack-nova22:43
*** tbachman has quit IRC22:43
*** tbachman_ is now known as tbachman22:43
efrieddansmith: I voted on the vgpu affinity spec22:45
efriedgotta run, see y'all Monday o/22:45
*** efried is now known as efried_pto22:45
*** luksky11 has quit IRC22:48
*** tkajinam has joined #openstack-nova22:54
openstackgerritMerged openstack/nova master: Remove 'MultiattachSupportNotYetAvailable' exception  https://review.opendev.org/65131523:00
openstackgerritMerged openstack/nova master: Rename CinderFixtureNewAttachFlow to CinderFixture  https://review.opendev.org/66856123:00
*** rcernin has joined #openstack-nova23:09
*** owalsh_ has joined #openstack-nova23:10
*** owalsh has quit IRC23:10
*** slaweq has joined #openstack-nova23:14
*** slaweq has quit IRC23:19
*** gyee has quit IRC23:39
*** nicolasbock has quit IRC23:41
openstackgerritMerged openstack/nova master: Add neutron-tempest-iptables_hybrid job to experimental queue  https://review.opendev.org/66715423:45
*** gyee has joined #openstack-nova23:54

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