Tuesday, 2022-01-11

sean-k-mooney[m]fungi ack, im not sure ill have much time in the short term but i would like to expore a new image again i might look into the docker file support00:00
sean-k-mooney[m]fungi presumable we could host such an image in the ci infra somewhere or on tarballs.o.o00:01
sean-k-mooney[m]if we were to make that move00:01
fungisure, ironic does (or did) that with their ipa images too00:01
sean-k-mooney[m]we have had times where it would have been useful to upgade specific packages like the guest kernel in the past to workaround itermitent gate issues00:02
fungibut if it's small enough we could just bake a copy into our test node images like we do with cirros00:02
sean-k-mooney[m]ya any replacment would have to be both small on disk and on ram requiremnt00:02
sean-k-mooney[m]but hosting it woudl be usefull for devstack00:03
sean-k-mooney[m]i have been leaning about and using nixos on my work laptop over the break and they have a way to make very  small image for contaienr but also have generator for many other formats https://github.com/nix-community/nixos-generators00:06
sean-k-mooney[m]one of them is openstack00:06
sean-k-mooney[m]nixos is also declaritvie by design so we could specify exactly what we wanted to include00:07
clarkbsean-k-mooney[m]: sorry I've been distracted and the point about types is exactly what I was trying to say before00:19
clarkbbut it seems nova assumes rsa == ssh in this case00:19
clarkbI don't think its crazy to have ssh_rsa and ssh_ecdsa and so on00:19
clarkbnote a new version of dropbear isn't good enough either I don't think00:20
clarkbI don't think they have fixed this issue in dropbear00:20
sean-k-mooney[m]well the value we have rith now are ssh or x50900:20
sean-k-mooney[m]technially there is no guarentee that ssh is rsa i think00:21
sean-k-mooney[m]ill have to check the api ref00:21
clarkbI think nova is hardcoded to do that though00:21
clarkbbut ya I doubt it is written in api docs00:21
sean-k-mooney[m]right but its and implemention detail00:21
sean-k-mooney[m]not part fo the api contract00:21
sean-k-mooney[m]we just promice we will give you a valid ssh key we dont tell you how its generated00:22
clarkbI've not been very fond of nixos image generation fwiw. our matrix gerritbot image is generated with nixos and it does a bunch of silly stuff like set a unicode shell prompt. But then doesn't install a shell00:22
clarkbIts a super power tool and if you aren't using it for everything seems extremely clunky00:22
sean-k-mooney[m]ya i just lost my will to live with fedora any longer and tried it to get back some contol of my laptop00:23
sean-k-mooney[m]its seams to be working fine for me right now but just geting used to it00:24
clarkbthe problem with the give me an ssh key api is that as a user I don't want an ssh key per instance. I want each instance to use my ssh key00:25
sean-k-mooney[m]clarkb honetst alpine or simlar would still be my perfered alternitive00:25
clarkbya alpine would be a good choice too since they target embedded environments00:25
sean-k-mooney[m]alpine was what i prviosuly tried to get working00:25
clarkbbut running a full openssh server on alpine etc isn't likely to be much faster than say on ubuntu00:25
sean-k-mooney[m]i should proably abandon does patches00:25
clarkbwhich is why I mention that dropbear isn't patched yet as far as I know00:25
clarkbto me using ecdsa and dropbear regardless of the image is still going to be necessary00:26
sean-k-mooney[m]well its not about speed right00:26
clarkbit definitely is00:26
sean-k-mooney[m]we could use ubunut if we could get it to fit the ram requiremnts00:26
clarkbtempest is running however many hundreds of instance boots per run00:26
clarkbif you make each one 5 minutes longer that isn't sustainable00:26
sean-k-mooney[m]ok ya speed is also imporant00:26
sean-k-mooney[m]but the first limit we have is must work with 64-96 mb of ram00:27
clarkbok I'm wrong dropbear does do rsa-sh200:27
sean-k-mooney[m]then must have small disk footprint then must not really be any slower then cirros00:27
clarkbas of version 2020.7900:27
sean-k-mooney[m]yep00:27
sean-k-mooney[m]the version in the cirros image is just too old00:27
clarkbI think frickler mentioned that a new cirros is in the works though00:27
sean-k-mooney[m]so alpine with dropbear would be nice00:28
sean-k-mooney[m]i mean thats also an option buy if frikler does i hope they also update the kernel to something form this decade00:28
sean-k-mooney[m]i think cirros is still using a ubuntu 18.04 kernel00:29
sean-k-mooney[m]it might be from 20.04 but its several years out of date in anycase00:30
clarkbI'm not super familiar with cirros build tooling but I think last I looked you get an entirely new user space when you update busybox to get a new dropbear00:30
clarkband when you do that chances of needing an ew kernel are much higher too00:30
clarkbI would be surprised if it wasn't a comprehensive update. But also if not updating the kernel as a subsequent step is probably not terrible00:30
clarkbone step at a time and all that00:30
sean-k-mooney[m]the current one has a bug that we ocationally hit00:31
sean-k-mooney[m]its patched in later version of that kernel in ubuntu but not in the specific point release they have imported00:31
sean-k-mooney[m]ya they skip updating the kernel the last time they rebuilt for somethign we needed so hopefully they will do it this time00:32
sean-k-mooney[m]clarkb i just generally like the idea of using something more mainstream but on the other hand its worked well for us for a long time so i dont dislike cirros just its update cadence00:33
clarkbya, but also frickler seems to be working on solving those problems so I'm happy to defer to epople doing the work :)00:33
clarkbthe good thing about cirros is its a proven system that works while still being tiny00:33
clarkbwhittling something else down could be significant work and as far as I know no one is doing that work (unlike with frickler and cirros)00:34
sean-k-mooney[m]so one option i think woudl be more viable would be to update nova ssh keygen to use ecrsa unconditioanlly00:34
clarkbThere is a problem with that: ecdsa isn't considered secure by many beacuse it relies on magic from NIST00:35
sean-k-mooney[m]clarkb well alpine because of its embeded and contaienr focus is the only thing that comes close form off the shelf solutions00:35
sean-k-mooney[m]clarkb well that depend on the curve00:35
clarkbFIPS is on board with it, but you might notice there is a conflict of interest between the people making FIPS and NIST :)00:35
sean-k-mooney[m]no one should use the nist curve00:35
clarkbI don't think there is another kind that ssh-keygen emits?00:36
clarkbecsda as supported by fips is the curve that nist magic'd00:36
clarkb(there are other eliptic curve algorithms but fips doesn't support them)00:37
sean-k-mooney[m]Ed25519 is not allowed?00:37
clarkbit is not00:37
sean-k-mooney[m]oh well personally im not really comfrotable with default to the nist curve so ignorem my previous suggestion00:38
sean-k-mooney[m]i was assuming we would only enable Ed2551900:38
ade_leeed25519 is in proposed fips standard but hasn't been accepted yet, so it wont work for fips now00:39
funginot allowed by current fips standards, but slated for inclusion in the "near" future (for usa gubment definitions thereof)00:39
fungiyeah, what ade_lee said00:39
sean-k-mooney[m]ack00:40
fungiit may be prudent, tinfoil hat on, to assume that means the nsa has only recently figure out how to break ed25519 ;)00:40
* fungi waves at the handlers reading all his communications00:41
sean-k-mooney[m]rsa 4096 with sha2 i think is till the best generally compatible ssh key you can generate today00:42
sean-k-mooney[m]which i still need to do later this week actully00:42
fungiagreed, except for all those half-baked sshds that serve up rsa host keys with sha-1 signatures (to the case in point)00:42
clarkbthe sha1/sha2 stuff is handled during protocol negotiation and not key generation time fwiw00:42
clarkbI really really wish that the clients whould just force sha2 for those sshds that can sha2 but don't advertise it00:43
clarkblike gerrit00:43
sean-k-mooney[m]yep00:43
sean-k-mooney[m]i tried doing that in my ssh config but could not get it to work00:44
sean-k-mooney[m]well forcing sha2 and enabling sha 1 but just failed00:44
sean-k-mooney[m]i could proably get it to work but was not worht the time00:44
clarkbya I converted to ed25519 and called it a day00:46
sean-k-mooney[m]i was actully reading https://blog.peterruppel.de/ed25519-for-ssh/ earlier today00:46
ade_leeso -- for fips testing, then, it sounds like - unless we can update or change cirros - the best short term solution is allowing ecdsa - and we'd prefer to generate the key in tempest?00:48
sean-k-mooney[m]yes that would be my preference00:49
ade_leegmann, ^^00:49
sean-k-mooney[m]generating in tempest would also be useful for downstream osp 17 testing based on wallaby00:49
sean-k-mooney[m]ade_lee we would not backport the nova ssh key generation downstream00:49
sean-k-mooney[m]we never backport api changes downstream00:50
ade_leeack, then the tempest change would be preferable for sure00:50
fungiideally, we'd generate the ssh-rsa keys in tempest too, and nova would slap a big red "deprecated" on its server-side key generation api00:54
sean-k-mooney[m]gmann deprecation is not an api change right from a micorversion point of view00:56
sean-k-mooney[m]so we could just propos a patch to update the docs to do that ?00:56
sean-k-mooney[m]the removal would be an api change00:57
sean-k-mooney[m]so that would need a spec00:57
sean-k-mooney[m]honestly i would be ok with doing the deprecation and removing in a later microversion but keeping the code to support the older micro verions00:58
sean-k-mooney[m]you should not really use it but it cost use very little to leave the code there for backwards compatiblity00:59
fungiwith my vmt/security wonk hat firmly affixed, i'd be fine deprecating it and never getting around to removing it. just so long as its use is discouraged01:37
gmannade_lee: yeah generating in tempest and testing is always ok/more coverage irrespective of nova auto generate or not01:40
gmannsean-k-mooney[m]: no, we have to do with microversion. 01:43
gmannit will be like <=2.xx microversion it will work as it is and >2.xx this will return 404, 400 or something 01:44
gmannremoving is not possible until we bump the minimum  microversion 01:44
gmannthat is how we deprecate the API in nova01:45
sean-k-mooney[m]we have to have the microversion for the removal os generating the key yes but to deprecate it with out any other change we dont01:45
gmannand yes we need spec for that01:45
sean-k-mooney[m]e.g. just a docs update01:45
gmannohk you mean just auto generation part01:46
gmannin that case, removal is possible yes and with microversion01:46
sean-k-mooney[m]and ya since we still woud have the code for < 2.x a 400 would be correct01:46
gmannbut deprecation is again I will say need microversion for notification at least01:46
sean-k-mooney[m]the same endpoint is used for create and import too01:46
sean-k-mooney[m]so we would still support import in the new verion just not create01:47
sean-k-mooney[m]its a http post in both cases i belive01:47
sean-k-mooney[m]with differnt body for create vs import01:47
gmannwe cannot return 400 directly without version bump as it will break users who are curently getting 200 success case and then will get 40001:47
gmannit is behavior change not just about return code01:48
sean-k-mooney[m]yep im not suggesting returnnign a 400 without a new microversion01:48
gmannso we can directly remove the auto generation of key in microversion and keep supporting for old microversion01:48
sean-k-mooney[m]yep01:48
gmannno need for deprecation 01:48
sean-k-mooney[m]i spoke of deprecation becasue i dont know if we will get arount to it this cycle01:49
sean-k-mooney[m]so more a reminder to us and warning to users that we might remove it next cycle01:49
sean-k-mooney[m]but we could also just add it to your api cleanup etherpad01:50
gmannsure, putting something in api-ref like 'this is not recommended to use' and later with microversion can amend that with 'not supported >2.xx'01:50
gmann+101:50
sean-k-mooney[m]ok i really should try and go to sleep so ill chat to ye tomorrow o/01:51
gmannsean-k-mooney[m]: done.01:52
gmannsean-k-mooney[m]: yeah, me too. GN01:52
opendevreviewMerged openstack/nova stable/victoria: Ensure MAC addresses characters are in the same case  https://review.opendev.org/c/openstack/nova/+/81692701:53
EugenMayerHello, experimenting with the "lock" feature. It seems that lock does not protect against deletion, against what does it protect then? Is there anything like a protected flag in openstack which protects particular instances form deletion?07:00
EugenMayerAh i see https://platform9.com/kb/openstack/can-i-lock-preserve-instance-from-deletion - admins can always delete. So i need somewhat of a different user, interesting07:01
*** hemna9 is now known as hemna07:38
lyarwoodEugenMayer:  yeah see https://docs.openstack.org/api-ref/compute/?expanded=lock-server-lock-action-detail#lock-server-lock-action for more details09:11
lyarwoodand https://docs.openstack.org/api-guide/compute/server_concepts.html#server-actions09:11
sean-k-mooneyEugenMayer: the primay uage of lock is to prevent normal users starting or stoping a vm09:21
sean-k-mooneyadmins can always bypass it as you have found09:21
opendevreviewIlya Popov proposed openstack/nova master: Fix to implement 'pack' or 'spread' VM's NUMA cells  https://review.opendev.org/c/openstack/nova/+/80564911:12
opendevreviewMerged openstack/nova-specs master: libvirt: Allow Manila shares to be directly attached to instances  https://review.opendev.org/c/openstack/nova-specs/+/81318012:25
*** hemna1 is now known as hemna12:30
opendevreviewMerged openstack/os-traits master: Updating python testing classifier as per Yoga testing runtime  https://review.opendev.org/c/openstack/os-traits/+/81920513:28
*** whoami-rajat__ is now known as whoami-rajat13: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/+/82405014:13
opendevreviewJonathan Race proposed openstack/nova master: Adds Pick guest CPU architecture based on host arch in libvirt driver support  https://review.opendev.org/c/openstack/nova/+/82205314:20
opendevreviewyuval proposed openstack/nova-specs master: lightos volume driver spec  https://review.opendev.org/c/openstack/nova-specs/+/82419114: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/+/82405014:40
opendevreviewJonathan Race proposed openstack/nova master: Adds Pick guest CPU architecture based on host arch in libvirt driver support  https://review.opendev.org/c/openstack/nova/+/82205314:40
*** xek_ is now known as xek15:04
bauzasreminder: nova meeting starts in 45 mins here at #openstack-nova15:14
gibimelwitt: Hi! Happy New Year! if you have time, could you look at this placement spec please https://review.opendev.org/q/topic:any-traits-support ?15:18
sean-k-mooneygibi i tought that was approved?15:20
sean-k-mooneyoh its not ok15:20
sean-k-mooneythen yes it woudl be useful for the emulation feature too15:21
sean-k-mooneyso we can say give me a host with HW_ARCH_X86_64 or COMPUTE_ARCH_X86_6415:22
* bauzas disappears now but is back around 16:50 hopefully15:22
bauzasgibi: I need to get my car back, in case I'm not there on time, could you start the meeting ?15:23
bauzasgibi: I wrote the agenda15:23
gibibauzas: sure15:28
gibino worries15:28
gibisean-k-mooney: yeah I saw the discussion around the emulation and I agree that needs OR relationship for traits15:29
yuvalHey, the nova meeting, on which channel is it?15:39
gibiyuval: it will be here in this channel from the top of the hour15:41
yuvalok thanks15:41
gibigmann: if you have time could you look at the qos tempest tests https://review.opendev.org/c/openstack/tempest/+/806257 ?15:51
gmanngibi: sure, I started it yesterday but could not finish. let me review today15:55
gibigmann: thanks a lot!15:55
bauzasI'm here15:58
bauzasnova meeting starting in 1 min15:59
Uggla\o/15:59
bauzas#startmeeting nova16:00
opendevmeetMeeting started Tue Jan 11 16:00:00 2022 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
opendevmeetThe meeting name has been set to 'nova'16:00
gibi\o16:00
bauzashey ho everybody16:00
elodilleso/16:00
bauzasgibi: elodilles: welcome back \o/16:00
elodilles\o/16:00
bauzashope you both have good vacations16:00
bauzashad*16:00
chateaulav\o16:00
gmanno/16:01
bauzas#link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting16:01
bauzasI guess we can start, people will join meanwhile16:02
bauzas#topic Bugs (stuck/critical) 16:02
bauzas#info No Critical bug16:02
bauzas#link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 36 new untriaged bugs (+3 since the last meeting)16:02
bauzas#help Nova bug triage help is appreciated https://wiki.openstack.org/wiki/Nova/BugTriage16:02
bauzas#link https://storyboard.openstack.org/#!/project/openstack/placement 25 open stories (+0 since the last meeting) in Storyboard for Placement 16:02
bauzasI need to do homework 16:02
bauzasany bug to discuss in particular?16:03
bauzaslooks not16:03
bauzas#topic Gate status 16:04
bauzas#link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:04
bauzasno new gate failure16:04
bauzas#link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status 16:04
bauzasno placement periodic job issue16:04
bauzas#info Please look at the gate failures, file a bug, and add an  elastic-recheck signature in the opendev/elastic-recheck repo (example: https://review.opendev.org/#/c/759967)16:04
bauzasnothing to say about the gate jobs ?16:04
gibiI have no experience yet on how good our CI this year :)16:05
bauzasgibi: I haven't seen it too16:06
bauzasanyway16:06
bauzas#topic Release Planning 16:06
bauzas#info Yoga-2 was Jan 6th16:06
bauzas#link https://releases.openstack.org/yoga/schedule.html#y-216:06
bauzas#info FeatureApprovalFreeze is punted to Jan 13st, 2 days left.16:06
bauzasthat means we need to review some spec changes :)16:07
yuvalI have added a spec today for review16:07
bauzasI have seen it16:08
chateaulavand there is the one i added yesterday. fixing items from sean's review16:08
sean-k-mooneyhttps://review.opendev.org/c/openstack/nova-specs/+/824191 and https://review.opendev.org/c/openstack/nova-specs/+/82404416:08
sean-k-mooneyyuval: your spec is very very light on details.16:09
bauzashttps://review.opendev.org/q/project:openstack/nova-specs+is:open+directory:specs/yoga16:09
yuvalsean: yes, I just saw your comment16:09
bauzasI'll review them tomorrow16:10
yuvalthere is not much in the nova driver most of the logic is in the cinder side  and os-brick16:10
bauzasalso, if people want to have specless bps approved, today is the last meeting for verifying them16:11
bauzasif so, please add your blueprint in the open discussion topic 16:11
bauzas#info fwiw, we have 16 accepted blueprints at the moment https://blueprints.launchpad.net/nova/yoga16:11
bauzasso, I guess we should be around 18-20 for yoga, which is like xena16:12
bauzasI have a question16:13
bauzas#info  any releases wanted for clients or libs ?16:13
bauzaswe're around the midcycle for yoga16:13
bauzastbh, I haven't looked at what we merged for all repos, but I can do 16:14
ade_leegmann, so based on discussion last night, you good with the generation of the ecdsa key in tempest?16:15
bauzasade_lee: we're in a meeting16:16
bauzasplease wait for the end of it16:16
gmannade_lee: let's discuss after meeting or in qa channel16:16
ade_leebauzas, sorry 16:16
bauzasanyway, moving to the next topic, looks like nobody wants a release for now16:16
bauzasand I'll look at the os-vif and os-brick repos to see whether we need some releases16:17
bauzas#topic Review priorities 16:17
gibithe release team will propose the release pathes if they need a release from us :)16:17
sean-k-mooneywe have a few patches under review for os-trait16:17
bauzas#undo16:17
opendevmeetRemoving item from minutes: #topic Review priorities 16:17
bauzassean-k-mooney: that's what I want to verify16:17
sean-k-mooneywe might want to do an os-trait release in week or two once those land16:18
bauzaswe're around yoga-2 which means it's time for us to provide new lib releases if needed16:18
bauzasso new features could use them16:18
sean-k-mooneywe use release with intermidary we dont have to wait for or only release at milestones16:18
bauzasif this is around yoga-3 and featurefreeze, I don't see how it could help16:18
bauzassean-k-mooney: yeah, my point is not about milestones16:18
sean-k-mooneyso we can do it when it make the most sense for us to consume them16:19
sean-k-mooneyack16:19
elodillesthe release patches were generated for yoga-2 already, so i guess there were no content from nova16:19
bauzasit's more about saying "meh, we're like 6 weeks from feature freeze, maybe it's time to release some libs"16:19
bauzaselodilles: I haven't got a release change for yoga-216:20
bauzas(for nova I mean)16:20
bauzasbut this is fine, we no longer do them16:20
elodillessorry, s/nova/libs16:20
bauzaselodilles: oh ok16:21
bauzasanyway, moving on16:21
bauzas#topic Review priorities 16:21
bauzas#link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+label:Review-Priority%252B116:21
bauzasnothing to tell here16:21
bauzaswe said last week that the three late changes should be reviewed16:22
bauzasany review priority to discuss in particular ?16:23
bauzasdo people want to have a priority ?16:23
bauzaslooks not16:24
yuvalHey, we really try to reach the deadline16:24
bauzasyuval: there are two deadlines tbc16:24
yuvalif we can have priority in review that will be great16:25
bauzasfirst is in 2 days, which is spec approval16:25
yuvalyes16:25
bauzasthe second is in 6.2 weeks which is feature freeze16:25
yuvalthen the code need to be merged16:25
bauzasthere is no rush about merging features but for your spec, agreed, we'll try to review it before the spec freeze16:25
yuvalThank you16:26
bauzasyuval: correct, code for feature delivery has to be merged before yoga-316:26
sean-k-mooneyyuval: do you have an approved cinder spec yet16:26
sean-k-mooneythe nova work depens on the cinder driver being merged before we can proceed16:27
sean-k-mooneyyou might have missed there deadline for cinder devers this cycle16:27
sean-k-mooneyhttps://releases.openstack.org/yoga/schedule.html#y-cinder-driver-deadline16:28
sean-k-mooneyjan 17th16:28
sean-k-mooneyand os brick freature freeze is feb 10th16:29
yuvalyesterday brain approved the blueprints16:29
yuvalthere was not request for spec so I havent created one16:30
yuvalbut I can talk to him to verfiy if it needed16:30
sean-k-mooneyok if they are ok with a specless blueprint for a driver that is fine16:30
bauzashum16:30
bauzasI'd then appreciate if some cinder cores could review this nova spec too16:30
sean-k-mooneybut the timing is quite tight16:30
bauzasyuval: do you think you could ask them to look at your nova spec ?16:31
bauzasI'm a bit concerned by being realistic16:31
yuvalI can try, I will answer sean comments, update and talk to them16:31
sean-k-mooneyack16:31
bauzasif some cores can sponsor this, this would raise my confidence into the blueprint being able to be merged in time16:32
sean-k-mooneyone of ther requirements is a third party ci in place before merging th edriver code16:32
bauzasand this is a huge commitment16:32
yuvalwe have thrid party ci running on cinder16:32
sean-k-mooneycool16:32
yuvaland I will have it running on nova today also16:32
bauzasoh this would be nice16:32
yuvalcan you specify the regex for the tempest run?16:33
bauzasthat kind of things raise my level of confidence easily :)16:33
bauzasyuval: yeah you can 16:33
bauzashttps://docs.openstack.org/tempest/latest/run.html16:33
bauzasbut I guess we can discuss this off-meeting16:34
bauzasmoving on16:34
bauzas#link https://review.opendev.org/c/openstack/nova/+/816861 bauzas proposing a documentation change for helping contributors to ask for reviews, needs more cores to vote16:34
bauzasjust sayin'16:35
bauzasanyway, next topic16:36
bauzas#topic Stable Branches 16:36
bauzaselodilles: anything in particular to mention ?16:36
elodilleswell, i haven't updated the stable status16:36
elodillesbut actually it is still valid if i'm not mistaken16:36
elodillesstable gates are not blocked16:36
elodillesbut recheckes are needed mostly before patches merge16:37
elodillesso nothing special i would say16:37
elodillesthat's it16:37
bauzaselodilles: yeah I left this status :D16:37
bauzasintentionally I mean16:38
elodillesbauzas: thanks :)16:38
elodillesit came handy o:)16:38
bauzasok, looks it's a nobrainer16:38
bauzas#topic Sub/related team Highlights 16:38
bauzas#info No subteam left16:38
bauzaswe demoted the libvirt one16:38
gibi:)16:38
bauzasjust in case some people are wondering about the process, this is simple16:39
bauzashttps://wiki.openstack.org/wiki/Nova#Nova_subteams16:39
bauzasthe tl;dr is "Sub-teams don't need permission. They can be around for short or long periods of time. "16:39
bauzasso, I'll leave this topic as a placeholder 16:40
bauzasbut if I don't see needs, I'll skip it 16:40
bauzasjust keep in mind subteams exist and are a good way forward to communicate and raise trustfulness and confidence16:40
bauzaslast item before we close16:41
bauzas#topic Open discussion 16:41
bauzasI have no item in the agenda16:41
yuvalcan I introduce myself?16:42
bauzaslast reminder, today is the last meeting for approving specless blueprints16:42
bauzasyuval: sure, any introduction is appreciated16:42
yuvalmy name is yuval brave, from lightbits labs16:42
yuvallightbits is working on a storage cluster solution16:43
yuvalworking with nvme over tcp16:43
yuvalwe have been working with openstack for few years now16:43
yuvaland support rockey, queens, stein, train and xena16:43
yuvaland questions?16:44
bauzasyuval: I guess you'll get plenty of them once we review your spec :D16:44
sean-k-mooney:)16:44
yuval:)16:44
gibi:)16:44
bauzasanyway, welcome16:45
bauzaswe don't bite16:45
yuvalthats it, good "meet" you all16:45
chateaulavim Jonathan Race, from the Georgia Cyber Center. We support security and medical device research. currently working with providing emulation support.16:45
bauzaswelcome chateaulav too16:46
chateaulavwe use our our framework for deployment and orchestration of openstack, so I be around here and there16:46
* bauzas wonders the nick but that's absolutely not the right timing and place to do such thing16:46
bauzascool16:46
* artom just wants to make more "Race condition" puns16:46
bauzasartom: man, have you just pop up at the end of the meeting literally just for a oneliner which is a pun ?16:47
gibi:)16:47
yuvallol16:47
artomHey, I was here all along16:48
gibibauzas: would have been better if artom starts the meeting with that?16:48
bauzasartom: speak more then :D16:48
artomOnly if I have something to say :P16:48
sean-k-mooneyi think we can proably wrap up the meeting at this point16:48
bauzasabsolutely16:48
bauzasthat being said,16:48
bauzas#endmeeting16:48
opendevmeetMeeting ended Tue Jan 11 16:48:56 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:48
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2022/nova.2022-01-11-16.00.html16:48
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2022/nova.2022-01-11-16.00.txt16:48
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2022/nova.2022-01-11-16.00.log.html16:48
bauzasprobably the weirdest ending I made16:49
bauzasbut it's all artom's fault16:49
artomI am *not* touching that16:49
yuval:)) its funny here16:50
gibiso if there is good vibes the all can start thinking and proposing names for the Z release https://wiki.openstack.org/wiki/Release_Naming/Z_Proposals16:50
gmann+1, please do16:50
artomWould "zizi" fly? bauzas and my 5 year old son would find it *hillarious*16:51
bauzasgibi: I assume Zombie was proposed 1000 times ?16:51
gibibauzas: actulay not on the list16:51
gibibauzas: so go ahead16:51
yuvalzoro is classic16:51
bauzasartom: man, you're gross16:51
artombauzas, correction, I am 5 years old in my head16:52
bauzasartom: you're on the verge of a big thing16:52
artomOuch16:52
gmannbauzas: that is good candidate, feel free to add in wiki16:53
gibiwondering what zizi means for you 16:53
bauzasgmann: I'll propose and hide16:53
bauzasprobably the last thing I'm able to support16:53
gmann:)16:53
gmannade_lee: on ecdsa, from tempest side yes we can generate the key in test case. what I commented in  https://review.opendev.org/c/openstack/tempest/+/80746516:55
sean-k-mooneythe cynical side of me likes Zenith since it would be all down hill form there16:56
* artom is surprised no one proposed Zulu16:56
artomWell, until I did just now16:56
sean-k-mooneyand zion obviously because the matix16:56
bauzasgibi: it's a childish word about male attributes16:57
sean-k-mooneybauzas: its also a first name16:57
gibibauzas: aah, here it is a type of sweet rice16:57
bauzasgibi: you can't imagine how many times children laughed at the rock band ZZ Top here16:58
gibi:D16:58
* bauzas is glad we stopped the meeting but remembers that the chan is logged16:59
sean-k-mooneyhttps://www.youtube.com/watch?v=Ae829mFAGGE i think thats the only zz top song i know17:00
artombauzas, hah, almost makes we want to propose ZZ, and facetiously say it's in honour of the band17:00
sean-k-mooneyoh and sharp dressed man too https://www.youtube.com/watch?v=7wRHBLwpASw17:01
artomSo then all the francophones would snigger when we say "on a sorti ZZ"17:01
artom"ZZ a un bug"17:01
artomAnd so on17:01
artom"J'arrive pas a deployer ZZ"17:01
* artom stops17:01
bauzasartom: yeah, like my Yoga has a problem17:01
* bauzas is glad we chose Ussuri over Uranus17:02
gibinah Uranus would be understood universally at least 17:02
chateaulavthat really would have put things in the dump17:02
artomchateaulav, top kek, you're fitting right in :D17:02
bauzasgibi: I don't know how Uranus is known, but I prefer to keep it secret17:03
sean-k-mooneyok im going to take a break for a while o/17:03
* gibi ends his day too17:05
gibio/17:05
bauzasartom: you swamped both my proposal and another https://wiki.openstack.org/w/index.php?title=Release_Naming/Z_Proposals&diff=next&oldid=18032917:06
bauzasbooo17:06
artombauzas, ah crap, sorry17:07
artomI thought I refreshed to avoid the conflict17:07
bauzasartom: I'm writing them back17:07
artomApologies17:08
bauzasdone17:08
bauzasartom: heh, no worries17:08
opendevreviewMerged openstack/nova master: Make the CellDatabases fixture work with fasteners >= 0.15  https://review.opendev.org/c/openstack/nova/+/81311417:19
spatelsean-k-mooney Hi and happy new year17:30
spatelI am getting stranger error in nova-scheduler logs - numatopologyfilter returned 0 hosts17:30
spatelQuestion can i check resource provider inventory of host to see why my numa not getting filter? 17:31
spatelall i can see this but how do i check my NUMA related resources in placement? - https://paste.opendev.org/show/812039/17:33
opendevreviewMerged openstack/nova master: Fill the exception msg  https://review.opendev.org/c/openstack/nova/+/82138517:34
bauzasspatel: there are no NUMA resources in placement17:37
spatelhmm17:37
bauzasif the filter returns 0 hosts, then look at it17:37
bauzasadd a DEBUG if you can17:37
bauzasfor the nova-scheduler service log level17:38
spatelok so there is no way to see my host NUMA inventory in DB. anyway if that is the case then only option i have which is debug17:38
spatelI was reading this - https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/numa-topology-with-rps.html17:39
spatelhttps://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/numa-topology-with-rps.html#optionally-configured-numa-resources17:40
bauzasspatel: yeah but as you can see, the spec was only approved, not implemented17:40
spatel+1 copy that17:41
spatelThank you so much! let me play with debug and see17:41
bauzasspatel: ack, I'll leave by now17:45
ade_leegmann, sorry - just to confirm -- as we're not going to add ecdsa key generation to nova api, we can leave the key generation code in create_keypair() in https://review.opendev.org/c/openstack/tempest/+/807465/23/tempest/lib/services/compute/keypairs_client.py#84 for ecdsa , right?18:04
ade_leegmann, so that basically the only changes needed in that patch is adding more detail to the release note18:07
gmannade_lee:  for nova api, yes we do not need to add and we will remove the existing ssh key generation part too with microversion. 18:13
gmannade_lee: for tempest, let me re-review it now. I think it make sense to me now to add in create_keypair() so that complete set of test can be tested with configured key. I will leave comment in review today18:15
ade_leegmann, great thanks18:15
gmannade_lee: I will be able to review in my evening, need to prepare lunch now :)18:16
ade_leegmann, ok - enjoy -- I have to do the same ..18:17
yuvalHey regarding running third party ci on the nova repo18:27
yuvalwhich tempest test should I run?18:27
gmannyuval: you can run compute integrated test which is what we run in upstream ci (or less depends on what you want to test). this file is used to prepare the integrated compute tests https://github.com/openstack/tempest/blob/master/tools/tempest-integrated-gate-compute-exclude-list.txt18:30
gmannthis file exclude all other tests and in tempest run you can pass this file with --exclude-list , example: https://github.com/openstack/tempest/blob/master/tox.ini#L16118:31
yuvalI see thank you18:34
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:47
chateaulavsean-k-mooney: I think that covers what was identified. 19:04
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:11
opendevreviewJonathan Race proposed openstack/nova master: Adds Pick guest CPU architecture based on host arch in libvirt driver support  https://review.opendev.org/c/openstack/nova/+/82205319:15
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:16
opendevreviewMerged openstack/placement master: Spec: support any trait in allocation candidates  https://review.opendev.org/c/openstack/placement/+/64999221:02
opendevreviewMerged openstack/placement master: Spec: support mixing required traits with any traits  https://review.opendev.org/c/openstack/placement/+/64936821:05
opendevreviewyuval proposed openstack/nova master: NO MERGE - activate lightbits third party ci on nova repo  https://review.opendev.org/c/openstack/nova/+/82425522:47
*** dasm is now known as dasm|off22:52
yuvalif someone is still awake - I have enabled the third party ci23:02

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