Monday, 2022-01-10

*** akekane_ is now known as abhishekk06:56
*** hemna8 is now known as hemna07:37
opendevreviewLior Friedman proposed openstack/nova master: support use_multipath for nvme driver  https://review.opendev.org/c/openstack/nova/+/82394108:24
opendevreviewTobias Urdin proposed openstack/nova master: libvirt: Add announce-self post live-migration workaround  https://review.opendev.org/c/openstack/nova/+/74152908:40
opendevreviewTobias Urdin proposed openstack/nova master: libvirt: Add announce-self post live-migration workaround  https://review.opendev.org/c/openstack/nova/+/74152908:41
bauzasgood morning Nova08:57
*** gibi_pto_back_on_10th is now known as gibi08:59
gibigood morning08:59
gibiI'm back08:59
gibiplease be gentle with me as I still needs to catch up09:00
bauzasgibi: well, I'd say I'm all way meetings this week again :)10:22
* bauzas winks at Uggla ;)10:23
bauzasgibi: so I won't harass you *by now*10:23
gibibauzas: all way meetings sounds bad10:26
gibibauzas: do I need to ask for a spec freeze exception for https://review.opendev.org/q/topic:%22any-traits-support%22 ?10:27
gibiOK, I saw the mail that the freez is moved to this week11:18
gibilyarwood: hi! do you have time to heck https://review.opendev.org/q/topic:any-traits-support spec before the spec freeze? (I'm hunting for a second core for it)11:20
gibi*check11:20
lyarwoodgibi: ack queued11:20
gibithanks11:21
opendevreviewMerged openstack/placement master: Add yoga spec directory  https://review.opendev.org/c/openstack/placement/+/81966012:02
gibistephenfin: I've replied in https://review.opendev.org/c/openstack/oslo.messaging/+/819142/comment/b5b812b5_8091e77f/ but I'm not about your second comment 13:57
gibi* not sure14:00
opendevreviewAlexey Stupnikov proposed openstack/nova master: Test aborting queued live migration  https://review.opendev.org/c/openstack/nova/+/77625014:36
sean-k-mooneydansmith: so ya looking at the code its defintly an unintended consequence18:01
dansmithyup18:01
sean-k-mooneydansmith: i tought we were only checking for up sevice but its any service record18:02
sean-k-mooneywhich results in the catch 22 of you cant start the conductor to be able to udpate the computes in the db18:02
sean-k-mooneywell unless service.get_minimum_version_all_cells is ignoreing down computes but i dont think it is18:04
sean-k-mooneyactully 18:06
sean-k-mooneyhttps://github.com/openstack/nova/blob/4a359d576ddbc4b104116515c7e8b4176ac511f7/nova/db/main/api.py#L403-L41218:06
sean-k-mooneyits not chekc up or down but is checking forced down18:06
sean-k-mooneyso the workaorund would have been to force them down before the upgrade18:07
sean-k-mooneyand the fix would be to allow filtering based on current state18:08
sean-k-mooneyor somethign like that18:08
dansmithyeah, makes sense18:11
dansmithalso,18:11
dansmithif you have one compute that was never upgraded and you forgot about (has been off for a year) you wouldn't want to hold up the upgrade until you find it18:12
opendevreviewJonathan Race proposed openstack/nova-specs master: Adds Pick guest CPU architecture based on host arch in libvirt driver support  https://review.opendev.org/c/openstack/nova-specs/+/82404418:19
opendevreviewArtom Lifshitz proposed openstack/nova master: WIP: libvirt: remove default cputune shares value  https://review.opendev.org/c/openstack/nova/+/82404818:36
opendevreviewJonathan Race proposed openstack/os-traits master: Adds Pick guest CPU architecture based on host arch in libvirt driver support  https://review.opendev.org/c/openstack/os-traits/+/82405019:10
*** artom__ is now known as artom19:25
artomSo if Jonathan Race writes an `if` block, is that a race condition? :D19:26
chateaulav-lol, its a fast one for sure19:27
kashyapchateaulav: Hey, I saw your email, but glad you're already here chatting.  (I'm just back and catching up with things)19:30
opendevreviewKashyap Chamarthy proposed openstack/nova-specs master: Repropose "CPU selection with guest hypervisor consideration"  https://review.opendev.org/c/openstack/nova-specs/+/82405319:35
kashyapartom: In case you have a bit of time, mind you mind looking at chateaulav (Jonathan Race's) spec/blueprint?  He has already been on it before I went on PTO19:36
artomkashyap, wait, can you clarify? That spec is jut for the automatic re-approval paperwork, right?19:38
kashyapartom: Mine, yes19:38
kashyapartom: I was referring to chateaulav's spec - https://review.opendev.org/c/openstack/nova-specs/+/82404419:38
kashyap"Adds Pick guest CPU architecture based on host arch in libvirt driver support"19:38
artomAh, sorry, got confused by the "CPU" in both19:38
artomAck, I can take a look19:39
kashyapchateaulav notes he's got a preview version of the code.19:39
kashyapchateaulav: Also, I must add, upstream has been severely starved of reviewer attention, so don't be dissuaded if you don't see "quick responses".  A ping here can help.19:40
kashyapartom: Yeah, not your fault; a quick look at the title can be deceiving :)19:40
chateaulavno worries, i understand. :)19:40
* kashyap --> heads out19:41
sean-k-mooneykashyap: did you reporpose that based on the xena version19:46
sean-k-mooneydansmith: i havent read your review comments on the health check speck but ill try and rework it tommorw with the other feedback19:52
dansmithsean-k-mooney: cool, looks very comprehensive :)19:52
sean-k-mooneyam i was considering punting warn out of the inital scope19:54
sean-k-mooneydo you think we shoudl try and keep it intiall or just start with pass/fail19:54
dansmithI think pass/fail for first go seems fine.. we can keep it in the spec as a valid result, but just implement everything as pass/fail initially I think19:55
sean-k-mooneyack. i was conidering moving it to the alternitives section but that works too19:55
dansmithif we're going to have it, it's not really an alternative, so I'd just leave the door open but say initially we'll just target pass/fail for the actual implementaiton19:56
sean-k-mooneyack19:56
sean-k-mooneyand yes i speelchecked v2 with gramerly but then i made a lot of changes  i will corret that in v419:57
dansmithI figured.. seemed like a whole section was affected :D19:57
sean-k-mooneyoh i like the idea of makeing devstack use this to see if the service is started19:59
dansmithyeah, dogfood is yummy :)19:59
sean-k-mooneyyour right we currently hit the service endpoitn and check if its up19:59
dansmithyeah19:59
sean-k-mooneyok its just 8 hear so ill call it a day. hope you enjoyed your PTO talk to you tommorow20:00
sean-k-mooneyo/20:00
dansmitho/20:01
opendevreviewAde Lee proposed openstack/nova master: Add ecdsa key generation  https://review.opendev.org/c/openstack/nova/+/82406221:19
ade_leesean-k-mooney, fungi , gmann https://review.opendev.org/c/openstack/nova/+/82406221:20
ade_leesean-k-mooney, fungi gmann please take a look and comment.  I'm not sure yet if all the tests will pass - but I want to make sure you all agree with the approach before I add more to it.21:21
ade_leeand let me know what else needs to be added 21:21
fungisure21:22
ade_leethanks!21:22
clarkbmy only though is the existing type seems to distinguish the encoding ssh vs x509 not the actual key algorithm. Might want to do ssh_ecdsa instead to keep that axis?21:29
ade_leeclarkb, sure I can do that - thats easy enough21:30
ade_leeclarkb, please add that comment to the review so others can comment on it21:30
clarkbcan do21:31
ade_leethanks21:31
clarkband ya I'd wait for someone that knows nova better to weigh in on what I say before implementing it21:31
fungioh, i assumed that was for ssh's x509 auth21:32
clarkbit may be, though I'm not sure how nova would configure the VM to enable that? it would have to add the CA to stuff right?21:34
clarkbin any case ssh vs x509 vs ecdsa is a bit confusing to me21:34
clarkbas they don't seem to align21:34
fungiyeah, agreed21:35
opendevreviewMerged openstack/nova stable/xena: [rt] Apply migration context for incoming migrations  https://review.opendev.org/c/openstack/nova/+/82055322:13
ade_leefungi, you haven't heard anything from canonical re: fips yet , have you?22:24
ade_leeclarkb, ^^22:25
ade_leeif not, I'll re-ping22:25
clarkbI haven't seen anything22:26
clarkbthere was an initial response and then fungi jumped in with more info iirc22:26
ade_leeclarkb, ack thats the last I saw too -- I'll re-ping them22:27
fungiade_lee: clarkb: while i'm trying not to be pessimistic, we're really no good at running things which are locked up by commercial registration (cf a decade of failing to find a legal solution to testing on rhel)22:58
fungithe easiest solution to it, from our perspective, is if ubuntu made their fips compliance solutions free for everyone22:59
clarkbya I suspect the easiset thing is for specific jobs to have access to a secret thta they use the enroll22:59
fungibut that's a business decision involving the parts of canonical we rarely have the pleasure of interacting with22:59
clarkband then run that post merge or something22:59
clarkbassuming their license system is ok with changing IPs and maybe even duplicate IPs over time23:00
gmannade_lee: ack, will check23:21
sean-k-mooney[m]ade_lee you willl need a spec to change the api to allow ssh key gen with the ec algorithim23:37
sean-k-mooney[m]nova currently allows you to import ecdsa keys23:37
sean-k-mooney[m]but it cant generate them23:38
sean-k-mooney[m]ade_lee if you want to start using them in tempest you should not relay on nova generating them23:39
sean-k-mooney[m]at least not if you want to do it this cycle given spec freeze is thursday23:39
sean-k-mooney[m]clarkb fungi gmann is there a reason for trying to do this in nova andn not in tempest23:44
sean-k-mooney[m]i dont think the current approch is the correct one23:44
clarkbsean-k-mooney[m]: well  Ithink if nova generates keys it is reasonable to generate different key types. As a nova user I have never once relied on a key generated by nova for me though so I can see both sides23:45
sean-k-mooney[m]ecdsa is not a differnt key type23:45
sean-k-mooney[m]its a diffent algortiom for ssh key generation23:45
sean-k-mooney[m]so the existing key-type fileid is not valid to extend23:45
sean-k-mooney[m]and if we wer to expose this implentation detail we also should be exposing the key lenght23:46
gmannsean-k-mooney[m]: there are two things here 1. add support and tests in tempest for ecdsa which is this (I have given comment to add tests for that)  https://review.opendev.org/c/openstack/tempest/+/807465 2. add support in nova to autogenerate the ecdsa  key this is what can be proposed in spec23:46
sean-k-mooney[m]which spec?23:47
gmannand in nova spec we can discuss about autogenerating the ecdsa key in nova. this nova change is not only because of tempest test but a new feature23:47
gmannsean-k-mooney[m]: it is not yet proposed. but as you mentioned this is API change and need spec23:47
sean-k-mooney[m]right so if we want to extend this feature we really shoudl add 2 knew parmaters 1 key size and 2 key algorthim or key cypher23:48
fungialternatively, consider that nova api deprecated and, as you say, have tempest generate and upload ecdsa keypairs instead23:49
sean-k-mooney[m]ya23:49
fungii agree i've never used this nova "feature" either, so it does seem like maybe it's a vestige of a bygone era23:49
sean-k-mooney[m]personally i would prefer to consider the generation part deprecated23:49
sean-k-mooney[m]same i have always uses ssh-keygen or simialr espically when scpriting in ansible or similr23:50
fungithe classical way to handle asymmetric keys is to generate the pairs client-side and only communicate the public part23:51
fungiso having nova supply both halves is not great from a security perspective23:51
sean-k-mooney[m]yep espically since using this api means if the rest api is not protected with ssl the private key is sent to you in the clear23:51
sean-k-mooney[m]meaning it can be intercepted and while we dont log or store this key anywere as a user you dont know that23:52
sean-k-mooney[m]the other benifit of the client generating it is they can generate it with any secuirty requirements they like23:53
gmannyeah that seems more reasonable and secure. 23:53
sean-k-mooney[m]fungi this is being motivated by limiations in the cirros image ssh server right23:53
fungiyes23:54
gmannsean-k-mooney[m]: that is from proposed goal https://review.opendev.org/c/openstack/governance/+/81658723:54
gmannpart of that23:54
sean-k-mooney[m]do we need to revisit using alpine or an alternitive guest image at somepoint or do we think cirros will continue to be upddated23:54
sean-k-mooney[m]gmann ack ya the fips goal23:55
fungiin short, the sshd in the cirros images lacks support for rsa with any signarture hash other than sha-1, and fips mode won't let tempest's ssh client use that, so ecdsa (which works on both ends) is an afreeable alternative23:56
fungiagreeable23:56
sean-k-mooney[m]yep its using a old version of dropbare from the commit message which makes sense23:57
fungiand yes, swapping out or improving cirros there is another option of course23:57
sean-k-mooney[m]ya i think long term we should look into nixos, alpine or maintianing cirros oursleve so we can update it23:57
sean-k-mooney[m]but ecdsa is a vaild short term step23:58
fungiif only someone had the time to resurrect emdebian23:58
sean-k-mooney[m]did the dib form docker feature ever land?23:58
fungiyeah, it's currently used to bootstrap fedora images, i believe23:59
sean-k-mooney[m]i more or less had alpine working i just could not get the init ram to find the root disk23:59
gmannfrom tempest test perspective we cab do either way 1. ecdsa  in proposed patch which seems ok and does not depends on nova featrure23:59
gmann2. new image has been considered in wallaby PTG and we said ok to try but again need someone to try adding/running tests with new image23:59

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!