*** tosky has quit IRC | 00:18 | |
*** mlavalle has quit IRC | 00:22 | |
*** baojg has quit IRC | 00:26 | |
*** baojg has joined #openstack-meeting-3 | 00:28 | |
*** baojg has quit IRC | 01:50 | |
*** baojg has joined #openstack-meeting-3 | 01:51 | |
*** ricolin has quit IRC | 02:08 | |
*** hemanth_n has joined #openstack-meeting-3 | 02:29 | |
*** baojg has quit IRC | 02:58 | |
*** baojg has joined #openstack-meeting-3 | 02:59 | |
*** psachin has joined #openstack-meeting-3 | 03:59 | |
*** imtiazc has quit IRC | 06:19 | |
*** e0ne has joined #openstack-meeting-3 | 07:22 | |
*** e0ne has quit IRC | 07:32 | |
*** slaweq has joined #openstack-meeting-3 | 07:41 | |
*** lpetrut has joined #openstack-meeting-3 | 07:46 | |
*** belmoreira has joined #openstack-meeting-3 | 07:50 | |
*** ricolin has joined #openstack-meeting-3 | 08:03 | |
*** e0ne has joined #openstack-meeting-3 | 08:06 | |
*** e0ne has quit IRC | 08:08 | |
*** e0ne has joined #openstack-meeting-3 | 08:13 | |
*** tosky has joined #openstack-meeting-3 | 08:34 | |
*** baojg has quit IRC | 09:58 | |
*** psachin has quit IRC | 11:45 | |
*** artom has quit IRC | 12:44 | |
*** baojg has joined #openstack-meeting-3 | 12:48 | |
*** e0ne has quit IRC | 12:55 | |
*** hemanth_n has quit IRC | 13:07 | |
*** e0ne has joined #openstack-meeting-3 | 13:09 | |
*** artom has joined #openstack-meeting-3 | 13:13 | |
*** e0ne has quit IRC | 13:25 | |
*** mugsie has quit IRC | 13:32 | |
*** raildo has joined #openstack-meeting-3 | 13:32 | |
*** baojg has quit IRC | 13:39 | |
*** baojg has joined #openstack-meeting-3 | 13:40 | |
*** baojg has quit IRC | 13:49 | |
*** baojg has joined #openstack-meeting-3 | 13:50 | |
*** e0ne has joined #openstack-meeting-3 | 14:00 | |
*** psahoo has joined #openstack-meeting-3 | 14:47 | |
*** lpetrut has quit IRC | 15:30 | |
*** rafaelweingartne has joined #openstack-meeting-3 | 15:52 | |
*** macz_ has joined #openstack-meeting-3 | 15:56 | |
*** mlavalle has joined #openstack-meeting-3 | 15:57 | |
*** elod has joined #openstack-meeting-3 | 15:58 | |
gibi | #startmeeting nova | 16:00 |
---|---|---|
openstack | Meeting started Thu Dec 3 16:00:33 2020 UTC and is due to finish in 60 minutes. The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
*** openstack changes topic to " (Meeting topic: nova)" | 16:00 | |
openstack | The meeting name has been set to 'nova' | 16:00 |
gibi | o/ | 16:02 |
gmann | o/ | 16:02 |
stephenfin | o/ | 16:02 |
elod | o/ | 16:02 |
gibi | #topic Bugs (stuck/critical) | 16:03 |
*** openstack changes topic to "Bugs (stuck/critical) (Meeting topic: nova)" | 16:03 | |
gibi | One Critical bugs | 16:03 |
gibi | #link https://bugs.launchpad.net/nova/+bug/1906428 blocking the nova gate as nova-multi-cell job fails | 16:03 |
openstack | Launchpad bug 1906428 in OpenStack Compute (nova) "test_cold_migrate_unshelved_instance failing with cat: can't open '/mnt/timestamp': No such file or directory" [Critical,In progress] | 16:03 |
gibi | Patch is on the gate to skip the failing test until we find a solution #link https://review.opendev.org/c/openstack/nova/+/765141 | 16:03 |
gibi | I saw it bounced from the gate :/ | 16:03 |
gmann | ah again failed. | 16:03 |
gmann | 134 run already in check pipeline I think it would not merge soon | 16:04 |
gibi | lyarwood promised to continue looking into the actual problem next week | 16:04 |
gibi | gmann: yeah, gate feels slow these days | 16:05 |
bauzas | \o | 16:05 |
gibi | #link 14 new untriaged bugs (+0 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New | 16:05 |
gibi | we are hovering around this number during the whole week | 16:05 |
gibi | #link 75 bugs are in INPROGRESS state without any tag (+0 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=INPROGRESS | 16:06 |
gibi | these are potentially un-triaged bugs. Check if they are still valid | 16:06 |
gibi | Is there any bug we need to discuss here ? | 16:06 |
gibi | #topic Gate status | 16:07 |
*** openstack changes topic to "Gate status (Meeting topic: nova)" | 16:07 | |
gibi | Gate on master is blocked. Patch to unblock it is on the gate #link https://review.opendev.org/c/openstack/nova/+/765141 | 16:07 |
gibi | we dicussed this already | 16:07 |
gibi | Gate on stable/victoria is blocked. Fix is on the gate #link https://review.opendev.org/c/openstack/nova/+/764432 | 16:07 |
gibi | this also bounced | 16:07 |
gibi | :/ | 16:07 |
gibi | Classification rate 35% (+11 since the last meeting) #link http://status.openstack.org/elastic-recheck/data/integrated_gate.html | 16:08 |
gibi | Please look at the gate failures, file a bug, and add an elastic-recheck signature in the opendev/elastic-recheck repo (example: #link https://review.opendev.org/#/c/759967) | 16:08 |
gibi | I don't know how relevant the classification rate as an absolute value | 16:08 |
gibi | as it is now show better classification than last week but the gate feels in worst shape | 16:08 |
gibi | maybe what changed that we know why the gate fails but we didn't solved the failures yet | 16:09 |
gibi | anyhow I will keep reporting / tracking this number for a while to see if it is relevant | 16:09 |
gibi | any other gate issue we need to talk about? | 16:09 |
gibi | #topic Release Planning | 16:10 |
*** openstack changes topic to "Release Planning (Meeting topic: nova)" | 16:10 | |
gibi | Wallaby Milestone 1 is today! | 16:10 |
gibi | The second spec review day was a success. We now have 11 blueprints approved to Wallaby. #link https://blueprints.launchpad.net/nova/wallaby | 16:11 |
gibi | Until Milestone 1 we finished 0 blueprint out of the 11 approved blueprints. | 16:11 |
gibi | M2 is january 22 | 16:11 |
gibi | considering the holiday season there is not much time until M2 | 16:12 |
gibi | M2 will be spec freeze so if you have an open spec please hurry up :) | 16:12 |
gibi | any other release specific thing to disucss? | 16:12 |
gibi | #topic Stable Branches | 16:14 |
*** openstack changes topic to "Stable Branches (Meeting topic: nova)" | 16:14 | |
gibi | stable/victoria is blocked but patch to unblock is on the gate - https://review.opendev.org/764432 | 16:14 |
gibi | other stable branches seems to be OK, no outstanding issue | 16:14 |
gibi | EOM | 16:14 |
elod | sorry for repeating o:) | 16:14 |
gibi | no worry, thanks for consistently adding update to the agenda | 16:14 |
elod | did not see that it's already listed at gate status | 16:14 |
elod | np | 16:15 |
gibi | any other stable thing to discuss? ( lyarwood is on PTO today) | 16:15 |
elod | nothing that I'm aware of :) | 16:15 |
gibi | #topic Sub/related team Highlights | 16:16 |
*** openstack changes topic to "Sub/related team Highlights (Meeting topic: nova)" | 16:16 | |
gibi | Libvirt (bauzas) | 16:16 |
bauzas | nothing to say | 16:16 |
gibi | #topic Open discussion | 16:16 |
*** openstack changes topic to "Open discussion (Meeting topic: nova)" | 16:16 | |
gibi | there are two on the agenda | 16:16 |
gibi | (stephenfin): Stuck on what to do about invalid instance hostnames like 'ubuntu18.04' | 16:16 |
gibi | #link https://review.opendev.org/c/openstack/nova/+/764482 | 16:16 |
gibi | stephenfin: could you summarize where we are? | 16:17 |
stephenfin | I've brought this up on the mailing list | 16:17 |
gibi | I was only able to follow the ML thread partially | 16:17 |
stephenfin | tl;dr: people are using instance names that look like FQDNs | 16:17 |
stephenfin | I haven't yet figured out if they're relying on these to be balid | 16:17 |
stephenfin | *valid | 16:17 |
stephenfin | In any case, I'm not sure if we're going to be able to just replace all periods is the name | 16:18 |
stephenfin | so I'm still thinking the "if it's an invalid FQDN, munge the name, otherwise don't" approach is best | 16:19 |
rafaelweingartne | I would like to ask for guidance with a patch | 16:19 |
stephenfin | but I know sean-k-mooney at least disagrees | 16:19 |
rafaelweingartne | I proposed this patch: https://review.opendev.org/c/openstack/nova/+/711113, but it has not received much reviews so far | 16:19 |
rafaelweingartne | should I open an RFE, and then a spec for it as well? | 16:19 |
gibi | rafaelweingartne: i will ping you after stephen's topic | 16:19 |
rafaelweingartne | ops, sorry, sure | 16:19 |
gibi | stephenfin: but sean is not here :) | 16:20 |
stephenfin | quick - everyone review it while sean is distracted! | 16:21 |
stephenfin | :) | 16:21 |
gibi | stephenfin: your proposed the split approach to support two separate use cases? | 16:21 |
gibi | use case a) server name is used as fqdn in the guest | 16:22 |
gibi | but what is use case b) | 16:22 |
stephenfin | use case a) is more a FQDN is used as the server display name and therefore the server host name | 16:22 |
stephenfin | while use case b) is a server display name with a period in it that is *not* a FQDN is used, so the server host name should be something else | 16:23 |
stephenfin | i.e. 'test.domain.com' is okay. 'test.01' will be converted to 'Server-{serverUUID}' | 16:23 |
stephenfin | if that makes sense? | 16:24 |
gibi | and in case b) what will be the hostname in the guest? | 16:24 |
stephenfin | 'Server-{serverUUID}' | 16:24 |
stephenfin | which is the fallback today if you end up with an empty string after all non-alphanumeric characters are removed | 16:25 |
gibi | I assum now test.01 causing a real failure somewhere down the line | 16:25 |
stephenfin | if designate is deployed, you aren't able to boot an instance | 16:25 |
stephenfin | because neutron will error out when creating/attaching a port | 16:25 |
gibi | with proper documentation I'm OK to have this split behavior. I guess you need a backportable solution | 16:26 |
gibi | hence not trying to disconnect the name and the hostname | 16:26 |
stephenfin | yes, exactly | 16:26 |
stephenfin | the proper solution is 'openstack server create --hostname FOO ...' | 16:27 |
stephenfin | but that's not backportable (API change) | 16:27 |
gibi | yeah | 16:27 |
gibi | does sean has a counter proposal that is also backportable? | 16:27 |
stephenfin | Not backportable fwict, no | 16:27 |
gibi | I see | 16:27 |
stephenfin | It's user error in his eyes | 16:28 |
gibi | then I think we can say that do a backportable fix first then do a proper fix on master later | 16:28 |
*** sean-k-mooney has joined #openstack-meeting-3 | 16:28 | |
sean-k-mooney | o/ | 16:28 |
stephenfin | and we should close as WONTFIX, which is user hostile | 16:28 |
gibi | sean-k-mooney: o/ | 16:28 |
gibi | we are just discussing the server name test.01 issue | 16:28 |
sean-k-mooney | ah ok | 16:29 |
bauzas | mmmm | 16:29 |
* bauzas looks at the API docs to see what we tell about naming instances | 16:29 | |
bauzas | "The server name." | 16:29 |
bauzas | wow | 16:29 |
sean-k-mooney | bauzas: it tell you nothing | 16:30 |
gibi | sean-k-mooney: what is the reason you are against stephenfin's proposal to convert test.01 to server-{serverUUID} and not convert valid FQDNs | 16:30 |
bauzas | didn't see that coming | 16:30 |
sean-k-mooney | yep | 16:30 |
sean-k-mooney | gibi: it would change the hostname seen in the guest for one | 16:30 |
sean-k-mooney | the precendiet is also based on a missunder standing that unicode was invalid in a hostname | 16:30 |
bauzas | so, honestly, given we haven't told it's either the display name or the hostname, I think we are OK | 16:31 |
bauzas | because the semantics can change | 16:31 |
gibi | sean-k-mooney: I gues we not just remove unicode charachters but other non hostname compatible charachters too | 16:31 |
gibi | like / | 16:31 |
sean-k-mooney | so we should be allowing unicode hostnames | 16:31 |
sean-k-mooney | but ath is a seperete fature | 16:32 |
bauzas | definitelty ^ | 16:32 |
sean-k-mooney | *feature | 16:32 |
gibi | agree ^^ | 16:32 |
gibi | so unicode aside | 16:32 |
bauzas | asséééééé | 16:32 |
sean-k-mooney | we also are not transforming the hostnames acording to the relenvet RFEs | 16:32 |
sean-k-mooney | *RFCs | 16:32 |
sean-k-mooney | we shoudl be substituiing all punctianto and other special symble with _ | 16:32 |
sean-k-mooney | sorry - | 16:32 |
bauzas | or, just consider that if you provide a ".", then you knew you are providing a FQDN | 16:33 |
bauzas | so, the hostname should only be the server name, not the TLD | 16:33 |
sean-k-mooney | so what we coudl do is in a new microversion add an fqdn filed and take only what is before the . for the instance.hostname | 16:34 |
bauzas | ie. if I wrote "bauzas.local", that meant to me that the name of my server is "bauzas" | 16:34 |
sean-k-mooney | yep | 16:34 |
sean-k-mooney | which is what actully happens todya | 16:34 |
bauzas | and I leave my DNS telling me my own TLD | 16:34 |
stephenfin | an API microversion isn't backportable though | 16:34 |
gibi | but as far as I understand we need a backportable solution first, then a proper solution on master | 16:34 |
sean-k-mooney | but as i pointed out in the email thread the metadat is totally wrong in that case | 16:34 |
stephenfin | I totally agree that what we do is rubbish, but we do it and people rely on it to some degree | 16:35 |
sean-k-mooney | i dont belive we need a backporable solution | 16:35 |
sean-k-mooney | or at lease im not sold on it | 16:35 |
bauzas | stephenfin: can't we consider to limit the server name to be "server" and not the whole FQDN ? | 16:35 |
sean-k-mooney | bauzas: i woudl be ok backproting that although im uncofrotabel with the transformation in general | 16:36 |
bauzas | (speaking of "server.domain") | 16:36 |
stephenfin | if we do, that's a change in behavior for users that were doing e.g. 'openstack server create instance.domain.com' | 16:36 |
sean-k-mooney | stephenfin: its not form a cloud init poitn of view | 16:36 |
bauzas | stephenfin: that's why I said I'm cool with explaning this behavioural change | 16:36 |
sean-k-mooney | there hostname will be instance in both cases | 16:36 |
bauzas | as we didn't promised anything with the servername | 16:36 |
sean-k-mooney | e.g. with or without designate | 16:36 |
bauzas | we're not breaking the contract) | 16:37 |
stephenfin | hmm, okay, so I'd assumed that would be rejected as non-backportable | 16:37 |
sean-k-mooney | what that would change is the designate dns name | 16:37 |
bauzas | well, it says "The server name." | 16:37 |
bauzas | " | 16:37 |
sean-k-mooney | currently it appending the designate default domain to the full sever name | 16:37 |
sean-k-mooney | now it would do the sane thing and append the default domain tothe hostname | 16:37 |
bauzas | yup | 16:37 |
sean-k-mooney | which woudl acutlly be resolveable via dns | 16:38 |
bauzas | yup | 16:38 |
* gibi lost | 16:38 | |
bauzas | and we could keep the display name to be the FQDN | 16:38 |
stephenfin | so if you create a server with 'instance.domain.com' and designate's default domain is 'domain.com', what happens? | 16:38 |
sean-k-mooney | bauzas: sure | 16:38 |
bauzas | gibi: trying to rephrase | 16:38 |
sean-k-mooney | the dispaly name could be that server name as it was passed in | 16:38 |
stephenfin | gibi: bauzas and sean-k-mooney are suggesting we drop everything after the first period, and suggesting it's backportable because we never made a guarantee about what the instance's hostname would be | 16:38 |
bauzas | this ^ | 16:39 |
gibi | thanks | 16:39 |
stephenfin | so 'test-instance.domain.com' would have a hostname of 'test-instance' | 16:39 |
gibi | would this change the hostname of existing instances? | 16:39 |
bauzas | (with a big fat note explaining why we're so mean to the user) | 16:39 |
stephenfin | and 'ubuntu18.04' would have a hostname of 'ubuntu18' | 16:39 |
sean-k-mooney | gibi: no | 16:39 |
bauzas | gibi: don't | 16:40 |
sean-k-mooney | gibi: it would only change the hostname for new instances | 16:40 |
stephenfin | it shouldn't - that information is only calculated once on initial boot and stored in instance.hostname | 16:40 |
sean-k-mooney | yep | 16:40 |
gibi | ok | 16:40 |
bauzas | mustn't is the word :) | 16:40 |
sean-k-mooney | did peopel see http://lists.openstack.org/pipermail/openstack-discuss/2020-November/019137.html by the way | 16:40 |
stephenfin | I don't think we recalculate it if you e.g. change the instance name via 'openstack server set --name NAME server' | 16:40 |
stephenfin | assuming that is a command... | 16:40 |
sean-k-mooney | where i wen ther how the info is actully prented to the gust | 16:40 |
* stephenfin knows you can set the name when rebuilding but isn't sure about otherwise | 16:41 | |
gibi | then I'm OK to do this change as a backportable fix with a fat note | 16:41 |
bauzas | sean-k-mooney: yup, I saw your email | 16:41 |
gibi | could some of you please summarize it back to the ML to see if other will be against it? | 16:41 |
bauzas | sean-k-mooney: and that's why I think that people using periods in their server names are either foolish or smart enough | 16:41 |
gibi | sorry folks we have two other topics for today | 16:42 |
gibi | so we should move on | 16:42 |
stephenfin | yup | 16:42 |
* stephenfin will summarize | 16:42 | |
gibi | thanks! | 16:42 |
bauzas | I think we have a reasonable consensus here | 16:42 |
sean-k-mooney | stephenfin++ | 16:42 |
gibi | rafaelweingartne: your turn | 16:42 |
rafaelweingartne | Sure. I have proposed this patch (https://review.opendev.org/c/openstack/nova/+/711113), it has some conflicts, but before resolving them | 16:43 |
rafaelweingartne | I would like to understand if we are missing something | 16:43 |
rafaelweingartne | such as an RFE, or a spec | 16:43 |
gibi | rafaelweingartne: glancing at the patch and the commit message you plan to redefine what 'usage' currntly means in the os-simple-tenant-usage API | 16:44 |
*** e0ne has quit IRC | 16:44 | |
rafaelweingartne | yes, and no | 16:45 |
rafaelweingartne | we plan to externalise it. So, the default behaviour is maitained, and if somebody wants to redefine it, they could do so | 16:45 |
rafaelweingartne | To us, for instance, we were expecting something totally different from the data we get there (in the API) right now | 16:46 |
gibi | extrenalize is with a config option I assume | 16:46 |
sean-k-mooney | well if you wanted to do it differntly you can do so alredy | 16:46 |
sean-k-mooney | via consuming the instance notifocations | 16:46 |
rafaelweingartne | gibi: exactly | 16:46 |
sean-k-mooney | and building a system to track the lifecycle of the servers as you see fit | 16:46 |
rafaelweingartne | that is what the API is doing | 16:46 |
gibi | it feels like a config driver API | 16:46 |
rafaelweingartne | sean: we have other systems in-place that do that | 16:46 |
gibi | driven | 16:47 |
rafaelweingartne | gibi: yes | 16:47 |
gibi | we try to avoid config driven APIs as it makes differnt public coulds behave differently | 16:47 |
rafaelweingartne | when we saw that API, we just thought about using it to cross-check the data we already have in other monitoring and billing systems that we have in place | 16:47 |
gibi | Is os-simple-tenant-usage admin only by default? | 16:48 |
sean-k-mooney | so so this is one of the apis that i dont really fit well in nova | 16:48 |
sean-k-mooney | long term i think it would live better in an external service | 16:48 |
rafaelweingartne | probably yes | 16:48 |
sean-k-mooney | its one of the larger performance hedaces for our custoemr | 16:48 |
sean-k-mooney | this is very slow to query and result in a slow horizion as it used in the defautl overview page | 16:49 |
rafaelweingartne | but the current docs gave us the idea of providing the usage for a VM, but as I explain in the patch, it consider usage the time between the instance was created up until now or when it was destroyed | 16:49 |
sean-k-mooney | so im concerned about adding more complexity to it | 16:49 |
rafaelweingartne | I see | 16:49 |
rafaelweingartne | Right now, the API does not provide usage data as it says | 16:50 |
rafaelweingartne | at least, it is not the same understanding of usage as we have | 16:50 |
rafaelweingartne | that is why we proposed the patch | 16:50 |
gibi | rafaelweingartne: so it provides resource allocation usage but not runtime for the VM I guess | 16:50 |
rafaelweingartne | exactly | 16:51 |
sean-k-mooney | rafaelweingartne: well it does provide usage info | 16:51 |
gibi | I tend to agree with sean-k-mooney that this is not a good API for billing, and also rafaelweingartne you said that you have a different service anyhow for billing | 16:51 |
rafaelweingartne | but the documentation says usage, it does not differ between allocation and actual usage | 16:51 |
sean-k-mooney | but the defition of usage is differnt form what you are expecting | 16:51 |
rafaelweingartne | therefore, we tried to amend that | 16:52 |
gibi | I don't really think we shoudl develop os-simple-tenant-usage further (hence the name simple) but fix the doc to be precies instead | 16:52 |
sean-k-mooney | so amending that woudl be an api change and require a spec not a bugfix | 16:52 |
rafaelweingartne | well, ok that would help as well then | 16:52 |
sean-k-mooney | https://github.com/openstack/nova/blob/0e7cd9d1a95a30455e3c91916ece590454235e0e/doc/source/contributor/policies.rst#metrics-gathering | 16:52 |
sean-k-mooney | its slightly tangental but we have delcare metrics gathering as out of scope before | 16:53 |
sean-k-mooney | i tought we had a similar statement for billing but i dont see one | 16:53 |
rafaelweingartne | Ok, so no sense in creating an RFE then | 16:53 |
rafaelweingartne | well, I will create a patch to make the docs more clear then | 16:53 |
gibi | rafaelweingartne: thank you! | 16:54 |
gibi | (please file a doc bug for tracking) | 16:54 |
gibi | there is one more topic from the agenda | 16:54 |
gibi | (gibi): do we want to merge the backports for the placement-audit command? https://review.opendev.org/q/topic:%22placement-audit-backport%22 | 16:54 |
gibi | It was raised during the week on #openstack-nova | 16:54 |
stephenfin | yes please | 16:55 |
gibi | does somebody remember what was the reason not to merge it? | 16:55 |
stephenfin | artom: ^ ? | 16:55 |
stephenfin | I think the concern was that it's kind of feature'y, but it's not user visible and is a huge win for operators (and us, diagnosing problems) | 16:55 |
artom | Oh, it was just super messy | 16:55 |
stephenfin | oh, even simpler than that | 16:56 |
artom | Past, like, 1 or 2 releases back | 16:56 |
bauzas | yup | 16:56 |
bauzas | this was the concern | 16:56 |
stephenfin | it was merged in stable/ussuri, right? | 16:56 |
artom | Nope, we didn't bother | 16:56 |
stephenfin | no, I mean initially | 16:56 |
artom | I used the upstrem DNM backports for CI, essentially | 16:56 |
artom | Because our RH CI is... well, it is. | 16:56 |
artom | Ah, you'd have to ask bauzas about the initial landing. | 16:57 |
bauzas | when this was merged ? | 16:57 |
bauzas | well, I'm old | 16:57 |
bauzas | ussuri IIRC | 16:57 |
sean-k-mooney | dansmith had an opion on it and i belive it was in favor of mergeing based on the operator win but i also dont recal | 16:57 |
gibi | merged in ussuri | 16:57 |
bauzas | https://review.opendev.org/c/openstack/nova/+/670112 => ussuri | 16:57 |
bauzas | sean-k-mooney: I think his opinion was meh | 16:58 |
gibi | how risky it is to backport the mess? | 16:58 |
sean-k-mooney | bauzas: basically im rembering it was not a hell no | 16:58 |
bauzas | but honestly, audit is related to allocations recreate | 16:58 |
bauzas | from mriedem | 16:58 |
gibi | I assume the effor to create the backport was already spent so only future efforts on stable due to these patches in question | 16:59 |
bauzas | one is deleting orphaned, the other is recreating them | 16:59 |
bauzas | gibi: I'd say that the maintainance is low but the initial effort is worth it pre-Train | 16:59 |
bauzas | Train backport is easy | 16:59 |
gibi | bauzas: but the initial effort is already spent as we have the patches proposed | 17:00 |
bauzas | but then artom sweated a lot with older releases | 17:00 |
stephenfin | bauzas: is or is not? | 17:00 |
bauzas | technically, we QE'd it on Queens | 17:00 |
gibi | QE? | 17:00 |
artom | bauzas, did we tho? | 17:00 |
bauzas | so the effort is already done and manually validated | 17:00 |
bauzas | against Queens | 17:00 |
artom | I'd have to double check the BZ | 17:00 |
gibi | we run out of time | 17:00 |
gibi | lets move this to #openstack-nova | 17:01 |
gibi | sorry | 17:01 |
gibi | #endmeeting | 17:01 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 17:01 | |
openstack | Meeting ended Thu Dec 3 17:01:05 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:01 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-12-03-16.00.html | 17:01 |
bauzas | gibi: sorry, I meant this was validated by one of our engineers | 17:01 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-12-03-16.00.txt | 17:01 |
openstack | Log: http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-12-03-16.00.log.html | 17:01 |
*** imtiazc has joined #openstack-meeting-3 | 17:11 | |
*** psahoo has quit IRC | 17:25 | |
*** tosky has quit IRC | 17:29 | |
*** rafaelweingartne has quit IRC | 18:09 | |
*** artom has quit IRC | 18:37 | |
*** artom has joined #openstack-meeting-3 | 18:37 | |
*** belmoreira has quit IRC | 19:11 | |
*** tosky has joined #openstack-meeting-3 | 20:55 | |
*** purplerbot has quit IRC | 21:24 | |
*** purplerbot has joined #openstack-meeting-3 | 21:33 | |
*** purplerbot has quit IRC | 21:35 | |
*** purplerbot has joined #openstack-meeting-3 | 21:41 | |
*** bnemec has quit IRC | 23:22 | |
*** baojg has quit IRC | 23:43 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!