Earlier  
Posted Nick Remark
#openstack-nova - 2022-05-06
08:40:50 opendevreview Balazs Gibizer proposed openstack/nova stable/xena: Remove unavailable but not reported PCI devices at startup https://review.opendev.org/c/openstack/nova/+/840835
08:40:51 opendevreview Balazs Gibizer proposed openstack/nova stable/xena: Simulate bug 1969496 https://review.opendev.org/c/openstack/nova/+/840836
08:40:52 opendevreview Balazs Gibizer proposed openstack/nova stable/xena: Allow claiming PCI PF if child VF is unavailable https://review.opendev.org/c/openstack/nova/+/840837
08:41:58 Uggla gibi, oh cool ! hungarian is a complete different branch !
08:42:18 gibi yeah
08:42:25 gibi and even finish is faaar
08:42:47 gibi the grammar has common patterns and we have couple of similar words but that is all
08:44:04 Uggla gibi, so it is completely different from Russian ?
08:45:07 gibi Uggla: the origins of the language is from the Ural mountains from Russia but the russian language is totally different
08:47:48 Uggla gibi, and so totally different from slovak as well ?
08:48:09 gibi Uggla: yes
08:48:22 gibi it has no slavic roots
08:48:35 gibi but also the hungarian language borrowed a lot from others after group moved from the Ural to the current place.
08:49:02 gibi we had a long ottoman occupation
08:51:25 Uggla gibi, and no germanic as well.
08:52:05 Uggla gibi, that's really interesting. I really did not know about that.
08:52:15 gibi no germanic roots but lot of germanic influence due to the Austro-Hungarian monarchy
08:53:31 Uggla gibi, means you are understanding more or less germans ?
08:53:35 gibi nope
08:53:47 gibi we have a lot of words we took over and integrated
08:53:57 gibi but the grammar is really different
08:54:05 Uggla gibi, ok.
08:54:39 gibi like slag = Schlauch = hose
08:56:07 gibi of course we have our own word for Schlauch that is not related: tömlő ;)
08:59:08 gibi as far as I see tömlő has Uralic roots so that one is an original :D
09:01:58 opendevreview Balazs Gibizer proposed openstack/nova stable/wallaby: Isolate PCI tracker unit tests https://review.opendev.org/c/openstack/nova/+/840841
09:01:59 opendevreview Balazs Gibizer proposed openstack/nova stable/wallaby: Remove unavailable but not reported PCI devices at startup https://review.opendev.org/c/openstack/nova/+/840842
09:02:00 opendevreview Balazs Gibizer proposed openstack/nova stable/wallaby: Simulate bug 1969496 https://review.opendev.org/c/openstack/nova/+/840843
09:02:01 opendevreview Balazs Gibizer proposed openstack/nova stable/wallaby: Allow claiming PCI PF if child VF is unavailable https://review.opendev.org/c/openstack/nova/+/840844
09:03:53 Uggla gibi, thanks for the hungarian lesson ! ;)
09:04:03 gibi you are welcome :)
09:12:21 opendevreview Balazs Gibizer proposed openstack/nova stable/victoria: Isolate PCI tracker unit tests https://review.opendev.org/c/openstack/nova/+/840845
09:12:22 opendevreview Balazs Gibizer proposed openstack/nova stable/victoria: Remove unavailable but not reported PCI devices at startup https://review.opendev.org/c/openstack/nova/+/840846
09:12:23 opendevreview Balazs Gibizer proposed openstack/nova stable/victoria: Simulate bug 1969496 https://review.opendev.org/c/openstack/nova/+/840847
09:12:24 opendevreview Balazs Gibizer proposed openstack/nova stable/victoria: Allow claiming PCI PF if child VF is unavailable https://review.opendev.org/c/openstack/nova/+/840848
09:14:35 opendevreview Balazs Gibizer proposed openstack/nova stable/yoga: Retry in CellDatabases fixture when global DB state changes https://review.opendev.org/c/openstack/nova/+/840734
09:18:32 opendevreview Balazs Gibizer proposed openstack/nova stable/ussuri: Isolate PCI tracker unit tests https://review.opendev.org/c/openstack/nova/+/840850
09:18:33 opendevreview Balazs Gibizer proposed openstack/nova stable/ussuri: Remove unavailable but not reported PCI devices at startup https://review.opendev.org/c/openstack/nova/+/840851
09:18:34 opendevreview Balazs Gibizer proposed openstack/nova stable/ussuri: Simulate bug 1969496 https://review.opendev.org/c/openstack/nova/+/840852
09:18:35 opendevreview Balazs Gibizer proposed openstack/nova stable/ussuri: Allow claiming PCI PF if child VF is unavailable https://review.opendev.org/c/openstack/nova/+/840853
09:20:25 opendevreview Balazs Gibizer proposed openstack/nova stable/train: Remove unavailable but not reported PCI devices at startup https://review.opendev.org/c/openstack/nova/+/839717
09:20:26 opendevreview Balazs Gibizer proposed openstack/nova stable/train: Simulate bug 1969496 https://review.opendev.org/c/openstack/nova/+/839718
09:20:27 opendevreview Balazs Gibizer proposed openstack/nova stable/train: Allow claiming PCI PF if child VF is unavailable https://review.opendev.org/c/openstack/nova/+/839719
09:20:28 opendevreview Balazs Gibizer proposed openstack/nova stable/train: Isolate PCI tracker unit tests https://review.opendev.org/c/openstack/nova/+/840854
10:11:06 sean-k-mooney gibi: +w on https://review.opendev.org/c/openstack/nova/+/840822
10:11:38 gibi sean-k-mooney: thansk
12:15:12 opendevreview ribaudr proposed openstack/nova-specs master: Allow unshelve to a specific host https://review.opendev.org/c/openstack/nova-specs/+/831506
12:17:35 opendevreview ribaudr proposed openstack/nova master: Allow unshelve to a specific host https://review.opendev.org/c/openstack/nova/+/831507
13:34:16 opendevreview Artom Lifshitz proposed openstack/nova master: WIP: Use network's dns_domain in metadata hostname https://review.opendev.org/c/openstack/nova/+/840899
13:34:25 artom Now to write the spec :P
13:36:32 sean-k-mooney oh free -2 then :P
13:36:46 sean-k-mooney the spec should be fairly short i guess
13:37:36 artom I'll need to explain why our PTG thinking of hostname per network didn't pan out
13:37:43 artom tl;dr, no schema for it
13:38:00 artom And cloud-init doesn't know/care, it only cares about the single hostname in the "main" metadata
13:39:51 sean-k-mooney it was fqdn per port
13:40:25 sean-k-mooney well we are not touching hostname at all
13:40:28 sean-k-mooney just adding fqdn
13:41:12 artom And since the point is to make cloud-init not clobber the DHCP-provided hostname, I think we have to touch the hostname
13:41:26 sean-k-mooney then no
13:41:31 sean-k-mooney we should not do this
13:42:10 sean-k-mooney the point is not to change the value of /etc/hostname that shoudl not end up with the fqdn
13:42:41 sean-k-mooney it shoudl have the hostname but the domain name shoudl be avaiabel to used for generating /etc/hosts
13:43:02 sean-k-mooney or making hostname -f provide the fqdn
13:44:23 artom I mean we already have code in there that uses CONF.api.dhcp_domain, which defaults to 'novalocal', and joins that with the instance hostname and returns the whole thing as the hostname
13:44:32 artom So not having the FQDN in hostname has sailed
13:44:42 sean-k-mooney artom: if you going donw that pacth we ar eback to needing an nova api change to pass teh instance default domain name
13:44:50 frickler artom: is this related to https://review.opendev.org/c/openstack/neutron-specs/+/832658 ?
13:45:12 artom frickler, yep
13:45:29 sean-k-mooney well not really its relate dbut not dependent on that
13:45:43 artom sean-k-mooney, not necessarily. I mean, we can, but grabbing it from the network's dns_domain is also valid
13:45:55 sean-k-mooney only if doen at the per port level
13:45:58 sean-k-mooney not at the vm level
13:46:13 artom Yeah, so that's... not great
13:46:27 artom The assumption is that all of a VM's networks will have the same domain name
13:46:33 sean-k-mooney there are no port ordering garentees so theere is no such thing as first port even to say just take the first one
13:46:35 artom Which is true in the case of the operator who wants this
13:46:45 sean-k-mooney artom: right that is flat out not valid
13:46:51 sean-k-mooney we cannot assume that
13:46:59 sean-k-mooney becuae that is not how it works normally
13:47:19 sean-k-mooney take a ooo deployment each neutorn network typicaly has a differnt domain
13:47:41 sean-k-mooney e.g. our manament domain. internal api ectra
13:48:13 artom sean-k-mooney, so, backing up a bit, the purpose is to prevent cloud-init from clobbering the DHCP-provided domain name
13:48:22 sean-k-mooney no
13:48:26 artom Yes!
13:48:27 sean-k-mooney that is not the purpose
13:48:31 artom That is literally what the use case is
13:48:39 sean-k-mooney no it is not
13:48:52 artom Then we're talking about different use cases :)
13:48:55 sean-k-mooney the usecaue is to provide a way to pass domain info via the metadata service
13:49:17 sean-k-mooney cloud-init is one implemation but not the only one
13:49:26 artom We're talking about different use cases then
13:49:41 sean-k-mooney sure so my joking -2 shoudl actully be a really one
13:49:53 artom I mean it's WIP anyways
13:50:11 sean-k-mooney i ment on the spec
13:50:22 artom There is no spec yet
13:52:04 sean-k-mooney so if we look at https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html
13:52:25 artom So there's public_hostname and local_hostname *per interface* in https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html#example-output
13:52:25 sean-k-mooney we had talked about updaing the info in the interface section
13:52:36 artom But I couldn't find where that actually comes from

Earlier   Later