| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2022-05-10 | |||
| 13:40:49 | sean-k-mooney | when we pass --domain if neutron has the per-domain extension | |
| 13:41:04 | sean-k-mooney | then if nova creates a port then we should set the port domain to the value they passed | |
| 13:41:49 | sean-k-mooney | if we do that then you can set a default domain for an instance as part of nova boot for any ports created by nova and that will propaget via the metadta api and be sent to neutron/designate | |
| 13:42:16 | sean-k-mooney | if you precreate the ports then we will use the value of the domain form the network or port in the metadta | |
| 13:42:18 | gibi | I see | |
| 13:42:41 | sean-k-mooney | and neuton/desginsate will also advertise teh hostname/fqdn infor via dhcp | |
| 13:43:00 | sean-k-mooney | and if you have designate it woudl also configure the domains properly in dns | |
| 13:43:09 | artom | I keep coming back to the fact that the metadata stuff is just as a safety net to make sure cloud-init doesn't clobber what the instance gets from DHCP, once Neutron actually implements that | |
| 13:43:46 | sean-k-mooney | well the proably is that hostnames form dhcp are by defintion consider trasient hostnames | |
| 13:44:00 | sean-k-mooney | with a lower priortiy then static hostnames configured by /etc/hostname | |
| 13:44:02 | artom | So if we can't figure out a way to make sure cloud-init gets the correct FQDN from the metadata (because of multiple ports or other reason), then the whole spec is kinda useless | |
| 13:44:04 | sean-k-mooney | so its not clobbering it | |
| 13:44:37 | sean-k-mooney | not really i think it makes sense to pass the dns info via metadata | |
| 13:44:50 | sean-k-mooney | as the application in the vm may not have access to neutron api | |
| 13:45:30 | sean-k-mooney | and if you readd the api cahnge for --domain then you can also cater for updating the static hostname via cloud-init | |
| 14:49:58 | opendevreview | Merged openstack/nova-specs master: update userdata https://review.opendev.org/c/openstack/nova-specs/+/816542 | |
| 14:57:33 | bauzas | man, what a PCI spec :) | |
| 14:57:38 | gibi | sean-k-mooney: replied to some of your the deeper comments in https://review.opendev.org/c/openstack/nova-specs/+/791047 | |
| 14:58:15 | gibi | but I will disappear now and might return a last review round for today after 20:00 CEST | |
| 14:59:39 | sean-k-mooney | gibi: cool ill take a look im still take a first pass over some of the specs | |
| 14:59:44 | bauzas | reminder: nova meeting in 1 hour here | |
| 15:22:29 | bauzas | sean-k-mooney: you had a point about https://review.opendev.org/c/openstack/project-config/+/837595 | |
| 15:22:38 | bauzas | sean-k-mooney: I don't see in the agenda, do you want me to add it ? | |
| 15:22:50 | sean-k-mooney | oh ya sure | |
| 15:23:00 | bauzas | I'll briefly mention it in the right topic | |
| 15:23:01 | sean-k-mooney | just are we good to proceed with that | |
| 15:23:30 | bauzas | I'll call out for reviews and summarize the namings | |
| 15:23:40 | bauzas | shall be quick hopefully | |
| 15:37:04 | erlon | hey folks, can someone else +2 this patch so I can continue the backporting? | |
| 15:37:04 | erlon | https://review.opendev.org/c/openstack/nova/+/836014 | |
| 15:40:43 | sean-k-mooney | melwitt:^ | |
| 15:57:59 | bauzas | nova meeting in 2 mins here | |
| 16:00:12 | bauzas | #startmeeting nova | |
| 16:00:12 | opendevmeet | Meeting started Tue May 10 16:00:12 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:12 | opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 16:00:12 | opendevmeet | The meeting name has been set to 'nova' | |
| 16:00:19 | bauzas | hello everyone | |
| 16:00:21 | stephenfin | o/ | |
| 16:00:22 | elodilles | o/ | |
| 16:00:39 | bauzas | #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting | |
| 16:00:53 | chateaulav | \0 | |
| 16:01:50 | bauzas | ok, let's start, people can join | |
| 16:01:54 | bauzas | #topic Bugs (stuck/critical) | |
| 16:02:00 | bauzas | #info No Critical bug | |
| 16:02:06 | bauzas | #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 19 new untriaged bugs (-3 since the last meeting) | |
| 16:02:14 | bauzas | thanks artom et al. for the triage | |
| 16:02:35 | artom | \o/ a net minus! | |
| 16:02:40 | bauzas | artom created an etherpad for bugs he looks https://etherpad.opendev.org/p/nova-bug-triage-20220503 | |
| 16:02:44 | bauzas | looked* | |
| 16:03:04 | bauzas | artom: nothing to tell about those ? | |
| 16:03:19 | artom | Not really, just the evacuation one that's really funky | |
| 16:03:31 | artom | gibi and sean-k-mooney already looked at the reproducer func test | |
| 16:03:33 | bauzas | okay thanks | |
| 16:03:51 | bauzas | continuing then | |
| 16:03:59 | sean-k-mooney | because it inovled data loss im oke with it being a bug | |
| 16:04:05 | bauzas | #link https://storyboard.openstack.org/#!/project/openstack/placement 26 open stories (0 since the last meeting) in Storyboard for Placement | |
| 16:04:10 | sean-k-mooney | but otherwise i woudl consider it a small specless blueprint | |
| 16:04:24 | bauzas | sean-k-mooney: artom: bug link ? | |
| 16:04:46 | sean-k-mooney | https://review.opendev.org/c/openstack/nova/+/841170 | |
| 16:04:54 | sean-k-mooney | https://bugs.launchpad.net/nova/+bug/1952745 | |
| 16:05:35 | bauzas | thanks | |
| 16:07:08 | bauzas | ok, don't want to overdiscuss this bug in large, so I trust you, folks | |
| 16:07:36 | bauzas | let's say Valid and we can nitpick on whether it's requiring a BP or not during the code review | |
| 16:07:55 | sean-k-mooney | i think we can proceed as a bug | |
| 16:08:13 | sean-k-mooney | but its borderline | |
| 16:08:20 | sean-k-mooney | so we can move on i think | |
| 16:08:40 | bauzas | my first thoughts wonder whether this should be supported or not | |
| 16:08:48 | bauzas | but I need to look at other comments | |
| 16:09:09 | bauzas | but I agree, evacuate should work even if the compute is definitely gone | |
| 16:09:26 | bauzas | that's actually why we have evacuate :) | |
| 16:09:51 | bauzas | but let's not bikeshid this by noxw | |
| 16:09:55 | bauzas | next point | |
| 16:10:03 | bauzas | #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster | |
| 16:10:15 | kashyap | bauzas: On bugs ... | |
| 16:10:22 | bauzas | which leads me to the next point, | |
| 16:10:27 | bauzas | #info Next bug baton is passed to Uggla | |
| 16:10:38 | bauzas | Uggla: you're ok with this ? | |
| 16:10:58 | bauzas | reminder : this is best-effort | |
| 16:11:18 | bauzas | metrics are cool, but that's not important | |
| 16:11:25 | bauzas | any effort counts, even the lowest | |
| 16:11:44 | kashyap | Having dedicated days of public bug triage would be nice. We did it in the distant past (here and also for RDO) | |
| 16:11:48 | bauzas | hmmmm, looks like Uggla is gone for today | |
| 16:11:54 | kashyap | But doing it off alone quietly ... it's hard to sustain | |
| 16:12:15 | sean-k-mooney | kashyap: i think that is the reason to have it rotate | |
| 16:12:23 | bauzas | kashyap: we can discuss the opportunity of a Bug Triage day later if you wish | |
| 16:12:38 | bauzas | but this is exceptional by nature | |
| 16:12:52 | bauzas | rotation helps with the triage fatigue | |
| 16:13:00 | kashyap | Right. A small idea: | |
| 16:13:20 | kashyap | When we were bootstrapping the RDO community, I used to do these public reports to the mailing list: | |
| 16:13:23 | kashyap | https://kashyapc.fedorapeople.org/virt/openstack//rdo-bug-status/2017/nova-bugs-05-SEP-2017.txt | |
| 16:13:23 | bauzas | I don't want people to mark their agendas with a triage day, we're upstream here and I don't want to order people | |
| 16:13:42 | kashyap | _With_ the title of the bug in the mail; so people could skim it via email ... | |
| 16:14:16 | kashyap | (I'm not sure if that'll work here, to send them to the -discuss list. Once every month? I don't know) | |
| 16:14:26 | kashyap | bauzas: No, you're misunderstanding me :) | |
| 16:14:27 | bauzas | kashyap: again I don't want to force any formalization of things | |
| 16:14:33 | kashyap | bauzas: We're not "ordering" anyoone on anything. | |
| 16:14:46 | sean-k-mooney | that feels a bit heavy wait but proably workable i would be less enclined to do it if i had to send a main however | |
| 16:14:57 | kashyap | bauzas: We've done this countless times before when doing upstream RDO community work: | |
| 16:15:11 | bauzas | sean-k-mooney: even the triage etherpad has to be kept *optional* | |
| 16:15:26 | kashyap | You simply mark a day ahead of time, note it on the list, as an announce to let people know. If people have time, thye'll join | |