| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2022-05-10 | |||
| 10:38:46 | gibi | sean-k-mooney: yep it looks good to me | |
| 10:38:56 | gibi | thanks for trying out all the legacy cases I was sloppy | |
| 10:39:09 | sean-k-mooney | we dont have a way to pin an unpinned guest in this caes | |
| 10:39:19 | sean-k-mooney | unless you use the old microverion | |
| 10:39:41 | sean-k-mooney | is that an issue | |
| 10:41:46 | sean-k-mooney | im going to take a break form this spec for a while but ill come back to it after Uggla has updated it | |
| 10:43:32 | gibi | sean-k-mooney: I agree that pinnin is not possible now but I think that is OK | |
| 10:44:20 | gibi | I remember a lot more questions about unpinning than pinning in the past | |
| 10:44:43 | sean-k-mooney | ya we could always add it later if needed. i think we have enough to update the spec and then we can get bauzas's and dansmith's input to see if they agree | |
| 10:46:14 | gibi | I agree | |
| 11:53:19 | gibi | bauzas: left feedback in https://review.opendev.org/c/openstack/nova-specs/+/840217 | |
| 12:03:29 | gibi | bauzas: fyi I cannot attend the today's nova meeting | |
| 12:03:32 | gibi | I will read back | |
| 12:26:21 | sean-k-mooney | artom: are you plannign to adress gibi's nits in https://review.opendev.org/c/openstack/nova/+/841170/3/nova/tests/functional/libvirt/test_evacuate.py or adress them in the follow up change that adressed the issue | |
| 12:35:43 | gibi | artom: left feedback in https://review.opendev.org/c/openstack/nova-specs/+/840974 | |
| 12:35:50 | opendevreview | Andre Aranha proposed openstack/nova master: Test setting the nova job to centos-9-stream https://review.opendev.org/c/openstack/nova/+/831844 | |
| 12:39:30 | bauzas | gibi: ack, thanks for the spec review and ack for missing the meeting | |
| 12:47:53 | opendevreview | Merged openstack/nova-specs master: Re-propose allow Project admin to list allowed hypervisors https://review.opendev.org/c/openstack/nova-specs/+/833165 | |
| 12:53:26 | gibi | bauzas: have you thought about abandoning open specs that was not re-proposed to the zed directory yet? It would clean up the open spec query a bit | |
| 12:53:49 | bauzas | gibi: we can do this | |
| 12:54:19 | bauzas | but let's discuss this on the next meeting as you're not there for today | |
| 12:54:31 | gibi | fine by me | |
| 12:54:56 | sean-k-mooney | im ok with abandoing them by the way | |
| 12:55:06 | sean-k-mooney | the owner can unabandone them | |
| 12:55:12 | sean-k-mooney | if they repopose them | |
| 12:55:32 | sean-k-mooney | but we are also not in a rush | |
| 12:55:43 | sean-k-mooney | so im fine to wait to make that desision | |
| 12:57:02 | gibi | it was just a sudden urge to close out the spec bottom third of the https://review.opendev.org/q/project:openstack%252Fnova-specs+status:open | |
| 12:57:08 | gibi | *specs | |
| 12:58:06 | sean-k-mooney | :) | |
| 13:06:08 | bauzas | but I'll respin https://review.opendev.org/c/openstack/nova-specs/+/840974 first | |
| 13:06:17 | gibi | bauzas: thanks, take an extra coffee :) | |
| 13:06:31 | bauzas | oh wait, wrong link | |
| 13:06:35 | gibi | sean-k-mooney: also thanks for the feedback on that one I will go through it | |
| 13:06:44 | bauzas | https://review.opendev.org/c/openstack/nova-specs/+/840217 | |
| 13:20:47 | artom | gibi, much thanks! So, with that spec, I'd really like for the original customer requesting it to weigh in | |
| 13:21:03 | artom | Since I'm not sure that in its current form it's of any use to them | |
| 13:21:34 | artom | sean-k-mooney, yeah, I can address the nits, I'll need to figure out a fix regardless and push that | |
| 13:26:22 | opendevreview | ribaudr proposed openstack/nova master: Allow unshelve to a specific host https://review.opendev.org/c/openstack/nova/+/831507 | |
| 13:35:16 | opendevreview | Sylvain Bauza proposed openstack/nova-specs master: Proposes to remove keypair generation https://review.opendev.org/c/openstack/nova-specs/+/840217 | |
| 13:36:22 | gibi | artom: ack, does the original requested aware of that we are discussing this in the spec? | |
| 13:36:30 | artom | gibi, yeah, sent them an email | |
| 13:36:38 | gibi | artom: cool then | |
| 13:36:41 | artom | And they previously commented on the Neutron bug | |
| 13:37:01 | sean-k-mooney | gibi: i think to adress the orginaly requester usecase we would need to add a --domain parmater to nova boot | |
| 13:37:37 | gibi | sean-k-mooney: is it about having one single domain per instance or domain per port? | |
| 13:37:39 | sean-k-mooney | and then updated hostname and local_hostname to be the full fQDN in the metadata | |
| 13:37:56 | sean-k-mooney | they want /etc/hostname to end up with the FQDN | |
| 13:38:08 | sean-k-mooney | so single per vm | |
| 13:38:10 | gibi | OK, I see, so one single domain per instance | |
| 13:38:13 | sean-k-mooney | yep | |
| 13:38:31 | gibi | then I agree that the current spec is going to a different direction | |
| 13:38:41 | sean-k-mooney | so to me if we want to do that we need to have that be a paramter to the nova boot command | |
| 13:38:59 | sean-k-mooney | gibi: the issue is they wanted use to backport this which we obvioulsy cant do | |
| 13:39:06 | sean-k-mooney | if its a new api parmater | |
| 13:40:04 | sean-k-mooney | so what i would like to see is as folows. we add --domain, when passed we set hostname to instnace.hostname+instance.domain when not set instance.hostname is the sanadised hostname as we have today | |
| 13:40:17 | sean-k-mooney | in addtion to that we generate the per port host name using the values from neutron | |
| 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) | |