*** lbragstad_ is now known as lbragstad | 00:27 | |
*** yamamoto has joined #openstack-meeting-alt | 00:31 | |
*** tetsuro has joined #openstack-meeting-alt | 00:38 | |
*** macz_ has joined #openstack-meeting-alt | 00:51 | |
*** macz_ has quit IRC | 00:55 | |
*** dave-mccowan has quit IRC | 01:01 | |
*** yamamoto has quit IRC | 01:33 | |
*** rfolco has quit IRC | 01:47 | |
*** yaawang has quit IRC | 02:08 | |
*** yaawang has joined #openstack-meeting-alt | 02:08 | |
*** ysandeep|away is now known as ysandeep|rover | 02:31 | |
*** ijw_ has joined #openstack-meeting-alt | 02:37 | |
*** macz_ has joined #openstack-meeting-alt | 02:39 | |
*** ijw has quit IRC | 02:41 | |
*** macz_ has quit IRC | 02:43 | |
*** lbragstad has quit IRC | 02:45 | |
*** yamamoto has joined #openstack-meeting-alt | 03:13 | |
*** tetsuro has quit IRC | 03:15 | |
*** tetsuro has joined #openstack-meeting-alt | 03:19 | |
*** maohongbo has quit IRC | 03:19 | |
*** maohongbo has joined #openstack-meeting-alt | 03:20 | |
*** tetsuro has quit IRC | 03:20 | |
*** maohongbo1 has joined #openstack-meeting-alt | 03:31 | |
*** maohongbo has quit IRC | 03:32 | |
*** maohongbo1 is now known as maohongbo | 03:32 | |
*** yamamoto has quit IRC | 03:44 | |
*** tetsuro has joined #openstack-meeting-alt | 03:52 | |
*** yamamoto has joined #openstack-meeting-alt | 03:55 | |
*** macz_ has joined #openstack-meeting-alt | 04:27 | |
*** macz_ has quit IRC | 04:32 | |
*** yamamoto has quit IRC | 04:40 | |
*** yamamoto has joined #openstack-meeting-alt | 04:42 | |
*** yamamoto has quit IRC | 04:42 | |
*** yamamoto has joined #openstack-meeting-alt | 04:43 | |
*** yamamoto has quit IRC | 04:47 | |
*** yamamoto has joined #openstack-meeting-alt | 04:47 | |
*** vishalmanchanda has joined #openstack-meeting-alt | 05:22 | |
*** links has joined #openstack-meeting-alt | 05:30 | |
*** Liang__ has joined #openstack-meeting-alt | 05:56 | |
*** maaritamm has joined #openstack-meeting-alt | 06:05 | |
*** irclogbot_1 has quit IRC | 06:49 | |
*** maaritamm has quit IRC | 06:50 | |
*** maaritamm has joined #openstack-meeting-alt | 06:50 | |
*** masahito has joined #openstack-meeting-alt | 06:50 | |
*** smyers has quit IRC | 06:51 | |
*** spotz has quit IRC | 06:51 | |
*** jhesketh has quit IRC | 06:52 | |
*** smyers has joined #openstack-meeting-alt | 06:52 | |
*** irclogbot_1 has joined #openstack-meeting-alt | 06:52 | |
*** irclogbot_1 has quit IRC | 06:53 | |
*** jhesketh has joined #openstack-meeting-alt | 06:53 | |
*** tonyb has quit IRC | 06:54 | |
*** irclogbot_2 has joined #openstack-meeting-alt | 06:54 | |
*** Liang__ has quit IRC | 06:56 | |
*** yaawang has quit IRC | 06:56 | |
*** Liang__ has joined #openstack-meeting-alt | 06:57 | |
*** yaawang has joined #openstack-meeting-alt | 06:59 | |
*** tonyb has joined #openstack-meeting-alt | 06:59 | |
*** priteau has joined #openstack-meeting-alt | 07:00 | |
*** Liang__ is now known as LiangFang | 07:01 | |
*** ysandeep|rover is now known as ysandeep|brb | 07:03 | |
*** slaweq has joined #openstack-meeting-alt | 07:03 | |
*** rcernin has quit IRC | 07:15 | |
*** maaritamm has quit IRC | 07:21 | |
*** maaritamm has joined #openstack-meeting-alt | 07:23 | |
*** e0ne has joined #openstack-meeting-alt | 07:35 | |
*** ttsiouts has joined #openstack-meeting-alt | 07:46 | |
*** ysandeep|brb is now known as ysandeep | 07:52 | |
*** ysandeep is now known as ysandeep|rover | 07:57 | |
*** maaritamm has quit IRC | 08:21 | |
*** maaritamm has joined #openstack-meeting-alt | 08:23 | |
*** gshippey has joined #openstack-meeting-alt | 09:02 | |
*** priteau has quit IRC | 09:03 | |
*** yamamoto has quit IRC | 09:07 | |
*** tetsuro has quit IRC | 09:09 | |
*** yamamoto has joined #openstack-meeting-alt | 09:28 | |
*** LiangFang has quit IRC | 10:00 | |
*** masahito has quit IRC | 10:31 | |
*** rcernin has joined #openstack-meeting-alt | 10:35 | |
*** derekh has joined #openstack-meeting-alt | 10:49 | |
*** maaritamm has quit IRC | 10:50 | |
*** ysandeep|rover is now known as ysandeep|afk | 10:56 | |
*** jcoufal has joined #openstack-meeting-alt | 11:10 | |
*** maaritamm has joined #openstack-meeting-alt | 11:11 | |
*** masahito has joined #openstack-meeting-alt | 11:19 | |
*** ysandeep|afk is now known as ysandeep|rover | 11:22 | |
*** maaritamm has quit IRC | 11:38 | |
*** ttsiouts has quit IRC | 11:42 | |
*** ttsiouts has joined #openstack-meeting-alt | 11:44 | |
*** maaritamm has joined #openstack-meeting-alt | 11:47 | |
*** ricolin has quit IRC | 11:54 | |
*** raildo has joined #openstack-meeting-alt | 11:56 | |
*** spotz has joined #openstack-meeting-alt | 12:07 | |
*** maaritamm has quit IRC | 12:08 | |
*** yamamoto has quit IRC | 12:09 | |
*** rfolco has joined #openstack-meeting-alt | 12:23 | |
*** derekh has quit IRC | 12:25 | |
*** yamamoto has joined #openstack-meeting-alt | 12:40 | |
*** derekh has joined #openstack-meeting-alt | 12:45 | |
*** dave-mccowan has joined #openstack-meeting-alt | 12:50 | |
*** maaritamm has joined #openstack-meeting-alt | 12:53 | |
*** dave-mccowan has quit IRC | 12:54 | |
*** lbragstad has joined #openstack-meeting-alt | 12:58 | |
*** ricolin_ has joined #openstack-meeting-alt | 13:01 | |
*** enriquetaso has joined #openstack-meeting-alt | 13:04 | |
*** masahito has quit IRC | 13:25 | |
*** liuyulong has joined #openstack-meeting-alt | 13:26 | |
*** maaritamm has quit IRC | 13:27 | |
*** ganso has left #openstack-meeting-alt | 13:32 | |
*** maaritamm has joined #openstack-meeting-alt | 13:36 | |
*** ttsiouts has quit IRC | 13:38 | |
*** ttsiouts has joined #openstack-meeting-alt | 13:48 | |
*** Liang__ has joined #openstack-meeting-alt | 13:55 | |
*** Liang__ is now known as LiangFang | 13:56 | |
*** rosmaita has joined #openstack-meeting-alt | 13:57 | |
*** eharney has joined #openstack-meeting-alt | 13:59 | |
rosmaita | Courtesy reminder: Cinder meeting in #openstack-meeting-alt at 1400 UTC | 14:00 |
---|---|---|
rosmaita | jungleboyj rosmaita smcginnis tosky whoami-rajat m5z e0ne geguileo eharney walshh_ jbernard lseki sfernand rajinir ^^ | 14:00 |
*** sfernand has joined #openstack-meeting-alt | 14:00 | |
LiangFang | hi | 14:00 |
walshh_ | hi | 14:00 |
rajinir | o/ | 14:00 |
sfernand | hi | 14:00 |
rosmaita | #startmeeting cinder | 14:00 |
rosmaita | #topic roll call | 14:00 |
rosmaita | #link https://etherpad.openstack.org/p/cinder-ussuri-meetings | 14:00 |
openstack | Meeting started Wed Apr 1 14:00:46 2020 UTC and is due to finish in 60 minutes. The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:00 |
jungleboyj | o/ | 14:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
geguileo | hi! o/ | 14:00 |
*** openstack changes topic to " (Meeting topic: cinder)" | 14:00 | |
e0ne | hi | 14:00 |
openstack | The meeting name has been set to 'cinder' | 14:00 |
*** openstack changes topic to "roll call (Meeting topic: cinder)" | 14:00 | |
rosmaita | sorry, had some technical difficulties there | 14:00 |
lseki | hi | 14:00 |
whoami-rajat | Hi | 14:01 |
*** tosky has joined #openstack-meeting-alt | 14:01 | |
tosky | o/ | 14:01 |
eharney | hi | 14:01 |
rosmaita | looks like a good crowd, i'll get started because there's a meeting right after ours | 14:01 |
LiangFang | o/ | 14:01 |
*** ganso has joined #openstack-meeting-alt | 14:02 | |
ganso | hello | 14:02 |
rosmaita | #announcements - upcoming deadlines | 14:02 |
rosmaita | this week (tomorrow) - os-brick release | 14:02 |
rosmaita | next week: | 14:02 |
rosmaita | * ussuri cinderclient release | 14:02 |
rosmaita | * ussuri milestone-3 release | 14:02 |
rosmaita | * FEATURE FREEZE | 14:02 |
rosmaita | two weeks after that (week of 20 April): | 14:02 |
rosmaita | * RC-1 | 14:02 |
rosmaita | so feature freeze coming up fast | 14:02 |
rosmaita | let's do a quick check of the os-brick release status | 14:03 |
rosmaita | #link https://etherpad.openstack.org/p/os-bric-ussuri-release | 14:03 |
rosmaita | not much in there, just a few bugfixes | 14:03 |
rosmaita | looks like no change in the status of the unmerged changes | 14:03 |
rosmaita | #link https://review.opendev.org/#/q/status:open+project:openstack/os-brick+branch:master | 14:04 |
rosmaita | so unless anyone has a last minute thing, i'll propose the release from HEAD later today | 14:04 |
rosmaita | for victoria, we will have some big changes | 14:04 |
e0ne | +1 for a release | 14:04 |
rosmaita | thanks e0ne | 14:05 |
*** smcginnis has joined #openstack-meeting-alt | 14:05 | |
rosmaita | #topic announcements - relaxing the two-company rule | 14:05 |
*** openstack changes topic to "announcements - relaxing the two-company rule (Meeting topic: cinder)" | 14:05 | |
rosmaita | #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013423.html | 14:06 |
rosmaita | this has become an issue with so many of us working for red hat these days | 14:06 |
rosmaita | nova has relaxed the rule | 14:06 |
rosmaita | i think we should as well | 14:06 |
LiangFang | +1 | 14:07 |
whoami-rajat | ++ | 14:07 |
rosmaita | but with the proviso that it's always better to have a diversity of opinion, so we should try to get reviewers from different companies | 14:07 |
smcginnis | We've suggested it in the past, but I don't think it's ever been an issue in cinder. | 14:07 |
e0ne | nothing changes for me :) | 14:07 |
rosmaita | but we shouldn't hold things up too long | 14:07 |
enriquetaso | hi | 14:07 |
rosmaita | smcginnis: ++ | 14:07 |
rosmaita | #topic announcements - virtual PTG brainstorming sessions | 14:08 |
*** openstack changes topic to "announcements - virtual PTG brainstorming sessions (Meeting topic: cinder)" | 14:08 | |
rosmaita | in case anyone is interested | 14:08 |
e0ne | rosmaita: +1 | 14:08 |
rosmaita | there are some virtual sessions over the next week or so | 14:08 |
rosmaita | #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013699.html | 14:08 |
rosmaita | so if you'd like to help shape what the virtual PTG would be like, please attend | 14:09 |
rosmaita | i think that's it for announcements | 14:09 |
rosmaita | #topic Volume migration improvements | 14:09 |
*** openstack changes topic to "Volume migration improvements (Meeting topic: cinder)" | 14:09 | |
rosmaita | zigo: that's you | 14:09 |
rosmaita | #link https://blueprints.launchpad.net/cinder/+spec/migration-improvement | 14:10 |
rosmaita | looks like zigo may have been called away | 14:11 |
rosmaita | anyway, he's interested in this, but doesn't have time to implement | 14:11 |
zigo | rosmaita: I'm in a meeting too ... | 14:11 |
rosmaita | basically, missing features are: progress indication, and migration abort command. This was proposed 5 years ago, but abbandoned (see linked review on that page). It'd be nice if someone was picking-up the idea and implementing it for Victoria | 14:11 |
zigo | (another meeting with my work) | 14:11 |
rosmaita | zigo: ok | 14:11 |
zigo | It'd be very nice if the progress thing could be implemented by someone. | 14:12 |
e0ne | it's a good feature to have... but we need a volunteer to get this done | 14:12 |
rosmaita | my question is does anyone know if there was a technical reason why we didin't follow through? | 14:12 |
rosmaita | or just lack of volunteers? | 14:12 |
zigo | I don't think I'd have the needed skills anyway, I don't know the cinder project. | 14:12 |
e0ne | rosmaita: it could be an issue for some drivers, I guess | 14:12 |
eharney | i'd imagine that measuring progress is a tricky problem to solve since it would vary depending on the driver and how it copies data on the backend | 14:12 |
e0ne | rosmaita: but speaking about generic migration it's absolutely doable | 14:12 |
eharney | we'd need some system where each driver could have a hook that would report that data, if it even could | 14:13 |
zigo | Having it for at least LVM would be nice already. | 14:13 |
e0ne | eharney: +1 | 14:13 |
*** throne82_ has joined #openstack-meeting-alt | 14:13 | |
rosmaita | ok | 14:13 |
zigo | With the old patch, it would have work for any driver where the compute node does a dd between volumes. | 14:14 |
smcginnis | We need to make sure whatever we introduce can be used by all drivers. | 14:14 |
rosmaita | sorry, i am thinking too much | 14:16 |
rosmaita | 2 things | 14:16 |
rosmaita | 1) is there sufficient interest on the part of driver maintainers? | 14:16 |
rosmaita | 2) someone to drive the work | 14:16 |
rosmaita | would be good to get a sense of 1 before the PTG | 14:16 |
rosmaita | so we don't spend a lot of time designing an interface no one will use | 14:17 |
*** ttsiouts has quit IRC | 14:17 | |
rosmaita | for the progress indication | 14:17 |
rosmaita | zigo: do you want to circulate something on the ML? | 14:17 |
rosmaita | maybe after M-3 | 14:17 |
rosmaita | ok, that's probably enough for now | 14:18 |
rosmaita | #topic backporting 'supported' status for drivers | 14:18 |
*** openstack changes topic to "backporting 'supported' status for drivers (Meeting topic: cinder)" | 14:18 | |
rosmaita | so, several vendors are getting their CIs running to be 'supported' in ussuri (were supported == False in train) | 14:19 |
rosmaita | the question came up, can that be backported to train? | 14:19 |
rosmaita | initially i was thinking no | 14:19 |
e0ne | technically, it's not a new feature | 14:19 |
rosmaita | but someone found a precedent: | 14:19 |
eharney | since we don't have drivers running CI on stable branches a lot of the time... hard to say | 14:19 |
rosmaita | #link https://review.opendev.org/#/c/700775/ | 14:20 |
rosmaita | eharney: exactly | 14:20 |
e0ne | I don't have a stong opinion on this | 14:20 |
e0ne | at lease we have to force drivers maintainers to have CI working for stable branches | 14:20 |
rosmaita | and this time, we are only testing python 3, whereas train also supports py2 | 14:20 |
rosmaita | e0ne: good idea | 14:20 |
rosmaita | so do we want to say, to backport 'supported', you need to have the CI working for Train? | 14:21 |
eharney | is there good knowledge out there for how to do that? | 14:22 |
eharney | not sure if it's just a switch to flip or more involved | 14:22 |
rosmaita | eharney: good question, i don't know | 14:22 |
rosmaita | well, i guess one way of looking at this is | 14:23 |
rosmaita | actually, forget that, it doesn't make sense now that i started to write it down | 14:24 |
smcginnis | I guess at least we know the vendor is around and presumably willing to address any issues that come up. | 14:24 |
rosmaita | that is true | 14:24 |
rosmaita | ok, tell you what, let's table this and return to it next week | 14:25 |
rosmaita | #topic Bug: Cinder throws error creating incremental backup from parent in another project | 14:25 |
*** openstack changes topic to "Bug: Cinder throws error creating incremental backup from parent in another project (Meeting topic: cinder)" | 14:25 | |
ganso | hello | 14:25 |
rosmaita | the floor is yours! | 14:25 |
ganso | I found this bug: https://bugs.launchpad.net/cinder/+bug/1869746 | 14:25 |
openstack | Launchpad bug 1869746 in Cinder "Cinder throws error creating incremental backup from parent in another project" [Undecided,New] | 14:25 |
ganso | and it has two possible solutions, I would like to discuss which one of them makes more sense | 14:26 |
enriquetaso | oh no | 14:26 |
ganso | so the bug in summary: if the user tries to create an incremental backup based on a backup created by another user, the code throws an error, but the backup is created anyway | 14:27 |
ganso | this only happens like this running the ceph backup driver | 14:27 |
e0ne | ganso: bug description says nothing about different projects, only different users are mentione4d | 14:27 |
ganso | e0ne: sorry perhaps I need to improve the description | 14:27 |
rosmaita | good question, so it's same project, different user? | 14:27 |
smcginnis | Seems like this would only be an issue between admin creating a backup and an owning user/project creating a backup. | 14:28 |
ganso | rosmaita: that's actually a good question, I did the steps to reproduce exactly, with users admin and demo | 14:28 |
rosmaita | actually user admin could be any project | 14:28 |
smcginnis | They should probably be treated separately. | 14:28 |
ganso | the user admin belongs to the admin project, while the demo user belongs to the demo project, so could be both | 14:28 |
smcginnis | Or even if created by admin, backup should get the owning project of the volume owner. Any reason why a cloud admin would be creating backups they don't want accessible by a project? | 14:29 |
ganso | the volume from where the backup is created belongs to demo | 14:29 |
ganso | smcginnis: so in this specific case, we were able to spot this bug because there were a few backups created by admin | 14:31 |
ganso | smcginnis: and they thought to be harmless, but they are actually causing issues | 14:31 |
rosmaita | ganso: so you know if it's just 2 users in the same project, does everything work as expected? | 14:31 |
e0ne | ganso: is it reproducible using different users without admin role? | 14:31 |
smcginnis | ganso: Is it their intent that those admin created backups are not accessible by the volume owner? | 14:31 |
ganso | rosmaita: I didn't test with those other combinations of 2 different users in same project, or if it has to be different projects | 14:32 |
ganso | e0ne: I am not sure | 14:32 |
rosmaita | ok, because in general, i think you would not expect this to work cross-project | 14:32 |
rosmaita | smcginnis: ^^ is that right? | 14:32 |
smcginnis | I would guess it has to be different projects. Which would mean it has to be admin versus someone in the project. | 14:32 |
eharney | it sounds to me like the real failure here is about checking if the user has access to the backup (i.e. two different projects) -- not really anything related to admin | 14:32 |
ganso | smcginnis: so, it was a special case that caused this bug, the customer can just reorganize their backups to avoid the bug, but this specific scenario allowed the bug to be found | 14:32 |
smcginnis | eharney: ++ | 14:33 |
eharney | perhaps a check is not happening early enough to catch when that should be rejected | 14:33 |
e0ne | eharney: +1 | 14:33 |
rosmaita | eharney: ++ | 14:33 |
smcginnis | I think 1) we should make sure the user has access to the backup before attempting to create an incremental backup from it, and | 14:33 |
ganso | eharney: so, exactly, other drivers that have the chunkeddriver as base class don't have this problem because it tries to get the parent first | 14:33 |
eharney | right | 14:33 |
ganso | and it throws the error immediately | 14:33 |
enriquetaso | eharney +1 | 14:34 |
smcginnis | 2) decide whether we need to support two different sets of backup trees by keeping these separate, or if an admin creates a backup if the backup should still be set to be owned by the same project as the one that owns the volume. | 14:34 |
eharney | we can check this in the API rather than in the backup driver though | 14:34 |
rosmaita | yes, would be good to fail as early as possible | 14:34 |
ganso | so, the way we found this problem was actually through the other bug: https://bugs.launchpad.net/cinder/+bug/1869749 | 14:34 |
openstack | Launchpad bug 1869749 in Cinder "Cinder leaves quota usage when deleting incremental backup with parent from another project" [Undecided,New] | 14:34 |
ganso | we noticed that the quotas were frequently going off sync | 14:34 |
ganso | and the code in that section could be improved to prevent that from happening | 14:35 |
smcginnis | SO for my point 2, is it a valid use case that an admin wants their own backups of a tenant's volumes, or is the use case that the admin should be able to create backups on behalf of the tenant. | 14:35 |
enriquetaso | #link https://bugs.launchpad.net/cinder/+bug/1869746 | 14:36 |
rosmaita | i'd think it would be the "on behalf of" use case | 14:36 |
openstack | Launchpad bug 1869746 in Cinder "Cinder throws error creating incremental backup from parent in another project" [Undecided,New] | 14:36 |
ganso | but anyway, the root cause is during creation, the backup should either not be created successfully, or not raise errors. So the question is: If we are creating an incremental backup based on another backup that is not visible to that user, should the code override that (if possible) and create it anyway (since the volume owner is the user creating the incremental backup), or should we just implement a better check and throw a more friendly | 14:37 |
ganso | error (preferably at the API), and prevent the backup from being created at all | 14:37 |
smcginnis | In that case, we don't need to put in extra checking because a volume's backup would be for a volume they have access to... actually, scratch that - volume transfer. | 14:37 |
smcginnis | So we do need the check. | 14:37 |
smcginnis | And regardless of whoever creates a backup, the backup should be owned by the volume's project, not the creator's project. | 14:37 |
smcginnis | And then, should we allow volume transfer to happen if there are backups present? Should those backups follow the volume like we decided to do with snapshots? | 14:38 |
ganso | smcginnis: so, even if admin creates the backup, the backup should always be in the same project as the volume, that sounds good | 14:38 |
ganso | and it solves the issue | 14:39 |
eharney | that only works if you reject creating backups that users attempt on volumes they don't have access to | 14:39 |
rosmaita | the volume transfer question is trickier | 14:39 |
smcginnis | ganso: We still would need to address your concern because of backwards compatibility. We need to add a check on owner of the last full backup before we attempt to create an incremental backup from it. | 14:39 |
eharney | because you don't want one user being able to consume another user's quota with failed backups etc | 14:39 |
smcginnis | eharney: Don't we do that now? I sure hope we do. | 14:39 |
smcginnis | Admin being a special case. | 14:40 |
eharney | well, i thought the bug report was showing that we don't do it before creating them | 14:40 |
smcginnis | If it's admin. | 14:40 |
smcginnis | If we allow anyone else to create a backup of someone else's volume, that would be a huge security hole. | 14:40 |
*** macz_ has joined #openstack-meeting-alt | 14:40 | |
ganso | eharney: the backups shouldn't be visible to that user, otherwise that would be possible | 14:40 |
eharney | ok | 14:41 |
eharney | also, is_public volumes... | 14:42 |
ganso | eharney: good point, It will end up consuming quota against someone else's project | 14:42 |
* eharney will look at some of this later | 14:42 | |
smcginnis | Ah, yep. So backup trees do need to be per-project. | 14:42 |
smcginnis | So incremental does need a check to make sure the full backup it attempts to use is one that is actually owned by the current user. | 14:43 |
smcginnis | And skip any that are not. | 14:43 |
ganso | smcginnis: but considering the ceph driver, doesn't it cause problems for the driver? imagine that you have backup A as demo, backup B as admin, and backup C as demo, if backup C skips B according to the code and considers A as parent, doesn't it cause problems? | 14:44 |
ganso | actually, considering any driver, not just ceph | 14:44 |
smcginnis | ganso: I'm not sure, but it sounds like it would need to be able to handle that situation. | 14:45 |
*** links has quit IRC | 14:45 | |
smcginnis | I think we need to start an etherpad or something to start capturing some of this. Or a spec, but it's not really a new feature. Something somewhere to make sure everyone understands what the issue is and what any proposed fixes would be. | 14:46 |
rosmaita | ok, so have we agreed that an incremental backup must be in the same project as the full backup it depends on? | 14:47 |
ganso | rosmaita: actually no, because of is_public volumes | 14:47 |
smcginnis | I think it has to be. | 14:47 |
jungleboyj | rosmaita: That sounds right. | 14:47 |
smcginnis | ganso: Yes, because of is_public. | 14:47 |
ganso | I'm confused | 14:47 |
rosmaita | ganso: the backup, not the volume | 14:47 |
eharney | yes... is_public was more about why a backup might not have the same owner as a volume | 14:48 |
ganso | rosmaita: ooooh ok | 14:48 |
rosmaita | but except for public volumes, sounds like the backup should normall be in the same project as the volume | 14:48 |
ganso | makes sense | 14:48 |
rosmaita | but i agree with smcginnis | 14:48 |
smcginnis | The open question for me is what happens with admin created backups. | 14:48 |
rosmaita | ganso, please write up how this should work in an etherpad | 14:48 |
smcginnis | But I think, based on everything else, those backups would just be owned by the admin and now the owner. | 14:49 |
ganso | smcginnis: I will update the launchpad bug entry with a summary of what was discussed here, with a link to the meeting notes | 14:49 |
rosmaita | and we can all look at it and make sure it makes sense | 14:49 |
smcginnis | *owner of the volume | 14:49 |
smcginnis | ganso: ++ | 14:49 |
e0ne | what does it mean 'is_public volume'? | 14:49 |
e0ne | AFAIR, volume could be owned only by one project | 14:49 |
e0ne | and we can't share volumes between projects | 14:49 |
rosmaita | e0ne: good question ... i thought we only had public volume_types | 14:49 |
ganso | e0ne: everyone can see the volume, which is owned by somebody. This would mean anybody can create a backup of the volume, since it is public | 14:50 |
e0ne | rosmaita: +1. | 14:50 |
e0ne | ganso: is't not public. it's available for everybody form tenant | 14:50 |
e0ne | it's really different cases | 14:50 |
*** ysandeep|rover is now known as ysandeep|away | 14:50 | |
rosmaita | it's different from visibility == public images in glance | 14:51 |
ganso | hmmmm I am not familiar with this. I know "is_public" from manila/glance/nova and thought this was the same | 14:51 |
smcginnis | My cloud is down, so I can't check. I may have been mixing that up with volume types and images. | 14:51 |
rosmaita | yeah, i believe e0ne is correct, it's only the volume_type that can be public | 14:51 |
ganso | smcginnis: if that is the case, then the previous idea of always having the backup the same project as the volume could work | 14:51 |
rosmaita | ok, we are running low on time, this is another thing to investigate | 14:52 |
ganso | ok | 14:52 |
rosmaita | e0ne: thank you for raising this point | 14:52 |
ganso | thanks everyone for feedback on this! =) | 14:52 |
e0ne | http://paste.openstack.org/show/791472/ | 14:52 |
smcginnis | ganso: Yeah, if we don't have public, then I do think backups should always be in the project that owns the volume. | 14:53 |
e0ne | smcginnis: +2 | 14:53 |
rosmaita | #topic tempest tests | 14:53 |
*** openstack changes topic to "tempest tests (Meeting topic: cinder)" | 14:53 | |
rosmaita | LiangFang: that's you | 14:53 |
eharney | that seems like an odd thing to always require to me, but i need to think on it more | 14:53 |
rosmaita | is that for your devstack plugin? | 14:53 |
rosmaita | #link https://review.opendev.org/#/c/713772/ | 14:54 |
LiangFang | yes | 14:54 |
LiangFang | I have solve the issues | 14:54 |
smcginnis | eharney: Kind of like a snapshot. It wouldn't make sense for a volume to be in one project, and one of its snapshots to be in another. Anyway, we can think about it and talk later. | 14:54 |
rosmaita | LiangFang: good news, i will look at the patch later | 14:55 |
LiangFang | thanks | 14:55 |
rosmaita | #open discussion | 14:55 |
rosmaita | quickly, i learned about the reno.cache | 14:55 |
whoami-rajat | is anyone aware about any changes in zuul or something merged in cinder causing this issue https://review.opendev.org/#/c/697636/ | 14:56 |
rosmaita | if you get crazy releasenote builds, everything the same for all releases, delete the reno.cache in releasenotes/notes | 14:56 |
whoami-rajat | there are a lot of valid failures on pylint but unrelated to the patch | 14:56 |
rosmaita | wow, that is pretty ugly | 14:57 |
whoami-rajat | yep, most of them are in test files | 14:58 |
eharney | pylint is not smart enough to understand a lot of unit test code adequately | 14:58 |
smcginnis | whoami-rajat: https://review.opendev.org/#/c/716600/ | 14:58 |
whoami-rajat | smcginnis, great, so i just need to recheck | 14:59 |
whoami-rajat | eharney++ | 14:59 |
*** lpetrut has joined #openstack-meeting-alt | 14:59 | |
smcginnis | Not sure how quickly that makes it into the gate. Just ignore for now. | 14:59 |
smcginnis | But it should go away soon. | 14:59 |
rosmaita | ok, we are out of time | 15:00 |
rosmaita | #endmeeting | 15:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 15:00 | |
openstack | Meeting ended Wed Apr 1 15:00:16 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-04-01-14.00.html | 15:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-04-01-14.00.txt | 15:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-04-01-14.00.log.html | 15:00 |
whoami-rajat | smcginnis, ok. but i need to recheck anyway, there is an unrelated failure :/ | 15:00 |
enriquetaso | thanks rosmaita | 15:00 |
enriquetaso | bye | 15:00 |
*** tosky has left #openstack-meeting-alt | 15:00 | |
whoami-rajat | rosmaita, thanks! | 15:00 |
amotoki | #startmeeting horizon | 15:01 |
openstack | Meeting started Wed Apr 1 15:01:29 2020 UTC and is due to finish in 60 minutes. The chair is amotoki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
*** openstack changes topic to " (Meeting topic: horizon)" | 15:01 | |
openstack | The meeting name has been set to 'horizon' | 15:01 |
e0ne | hi | 15:01 |
amotoki | hi | 15:01 |
vishalmanchanda | hi all | 15:02 |
*** rosmaita has left #openstack-meeting-alt | 15:02 | |
amotoki | okay, let's start | 15:03 |
amotoki | #topic notices/announcements | 15:03 |
*** openstack changes topic to "notices/announcements (Meeting topic: horizon)" | 15:03 | |
*** lbragstad has quit IRC | 15:03 | |
*** ttsiouts has joined #openstack-meeting-alt | 15:03 | |
amotoki | first, the ptl nomination period is over and e0ne volunteered for our PTL | 15:04 |
amotoki | thanks | 15:04 |
vishalmanchanda | e0ne: congrats Ivan. | 15:04 |
e0ne | amotoki: np. I hope I'll be helpful for the team as a PTL | 15:04 |
e0ne | unfortunately, I forgot to send a mail to openstack-discuss :( | 15:04 |
amotoki | I don't leave the community and horizon, so I would like to continue to help the team | 15:05 |
e0ne | amotoki: it's good | 15:05 |
*** lpetrut has quit IRC | 15:06 | |
amotoki | I will care Ussuri release as my responsibility | 15:06 |
e0ne | amotoki: TBH, it's a responsibility of the whole team | 15:06 |
*** lbragstad_ has joined #openstack-meeting-alt | 15:06 | |
amotoki | e0ne: yeah, that's true | 15:06 |
* e0ne will try to not break horizon again with a new pyscss release:) | 15:06 | |
amotoki | I just would like to mention a release related stuff :) | 15:07 |
e0ne | :) | 15:07 |
amotoki | second thing is this week is non-client lib freeze and next week is feature freeze | 15:07 |
amotoki | I don't think we have things related to non-client lib freeze though | 15:08 |
-amotoki- is spending time for neutron stuffs this week | 15:09 | |
amotoki | the third one is our gate is now healthy including stable/train and stable/stein | 15:09 |
vishalmanchanda | yeah finally:) | 15:10 |
amotoki | requirements change with pyscss 1.3.7 has landed today | 15:10 |
vishalmanchanda | e0ne: amotoki : thanks. | 15:10 |
amotoki | I will send a summary on pyscss, setuptools and horizon to the mailing list. | 15:10 |
e0ne | amotoki: does it mean we've fixed gates for stable/ussuri and stable/train? | 15:11 |
*** lbragstad_ has quit IRC | 15:11 | |
amotoki | e0ne: I think stable/stein gate also has recovered because upper-constraints has been updated | 15:11 |
e0ne | amotoki: awesome! | 15:12 |
amotoki | we still need to land requirements.txt bump in stein too | 15:12 |
amotoki | we have one known issue related to this | 15:12 |
amotoki | the material design theme is broken with pyscss 1.3.5+ | 15:12 |
amotoki | it turns out a fix from e0ne is partial so I reopened bug 1771559 | 15:13 |
openstack | bug 1771559 in OpenStack Dashboard (Horizon) "error while loading icon with pyscss 1.3.5 or later" [High,Confirmed] https://launchpad.net/bugs/1771559 | 15:13 |
amotoki | see https://bugs.launchpad.net/horizon/+bug/1771559/comments/9 for more detail | 15:13 |
e0ne | amotoki: oh.. I'll take a look on it asap | 15:14 |
amotoki | we would like to fix it till around RC phase | 15:14 |
e0ne | +1 | 15:14 |
vishalmanchanda | I have a question to ask about pyScss related stuff. | 15:14 |
amotoki | e0ne: I will share what I found so far with you | 15:14 |
amotoki | vishalmanchanda: go ahead | 15:14 |
vishalmanchanda | amotoki: there are some plugins which still have pyScss==1.3.4 in 'lower-contraints.txt'. | 15:15 |
vishalmanchanda | http://codesearch.openstack.org/?q=pyScss%3D%3D1.3.4&i=nope&files=lower-constraints.txt&repos= | 15:15 |
amotoki | vishalmanchanda: reagrding l-c, every project needs to update their l-c | 15:16 |
vishalmanchanda | Should we also need to update it to pyScss==1.37. | 15:16 |
vishalmanchanda | amotoki: ok. | 15:16 |
amotoki | l-c defines a set of python dependencies (direct and indirect) which we test. | 15:16 |
amotoki | vishalmanchanda: yes, l-c in plugin projects need to be updated | 15:17 |
*** lbragstad_ has joined #openstack-meeting-alt | 15:17 | |
vishalmanchanda | then i will purpose a series of patch in plugin to update it. | 15:17 |
amotoki | but actually scss stuffs are not tested in our unit tests, so the update is not urgent | 15:17 |
vishalmanchanda | I have already updated it in openstack/Sahara-dashboard. | 15:18 |
amotoki | this is a downside of the current lower-constriants mechanism | 15:18 |
vishalmanchanda | https://review.opendev.org/#/c/716367/ | 15:19 |
amotoki | IMHO I would like to let each project team review it. | 15:19 |
vishalmanchanda | amotoki: +1. | 15:19 |
e0ne | +1 | 15:19 |
amotoki | it is really a tricky issue as we cannot blacklist a specific version of setuptools in our testing with tox :-( | 15:20 |
*** lbragstad_ has quit IRC | 15:22 | |
amotoki | I should use a separate topic on the third one.... | 15:22 |
amotoki | moving on | 15:22 |
amotoki | #topic General Priorities | 15:22 |
*** openstack changes topic to "General Priorities (Meeting topic: horizon)" | 15:22 | |
amotoki | I need to say sorry for my delay on the policy stuff. | 15:23 |
*** LiangFang has quit IRC | 15:23 | |
amotoki | I had a cold later last week and could not have time to work on it.... | 15:23 |
e0ne | amotoki: I hope you're ok now | 15:24 |
vishalmanchanda | amotoki: get well soon. | 15:24 |
amotoki | I am working on this now, but I am not sure I can send a patch you satisfies. I will try to do my best | 15:24 |
amotoki | thanks. I am okay this week | 15:25 |
amotoki | regarding xstatic, we had a progress. | 15:26 |
amotoki | we released three new xstatic packages https://review.opendev.org/#/c/714682/ | 15:26 |
amotoki | we released them with help from the release team | 15:26 |
e0ne | it's good! | 15:26 |
amotoki | they are now used with horizon deployments, so I would encourage you to test horizon with them :) | 15:27 |
amotoki | I think rdopiera is working on a new release of xstatic-angular-fileupload | 15:28 |
amotoki | these four packages were updated during this cycle | 15:28 |
amotoki | * in their repos | 15:28 |
vishalmanchanda | nice. | 15:29 |
amotoki | let's test them in our browsers i.e. as GUI :) | 15:30 |
amotoki | regarding translations, have anyone tried zh-hans/hant? | 15:31 |
e0ne | unfortunately, no:( | 15:32 |
amotoki | If not AND we have no big issues after LOCALE_PATHS change, I think it is better to go as-is for Ussuri | 15:32 |
e0ne | +1 | 15:32 |
amotoki | hopefully Django 2.2 helps us | 15:33 |
amotoki | vishalmanchanda: did you have a chance to get feedbacks on your error-meesage-refactor stuff? | 15:34 |
amotoki | I failed to do it | 15:34 |
vishalmanchanda | not yet. | 15:34 |
amotoki | okay, let's try to look into it this and next weeks | 15:35 |
vishalmanchanda | thanks. | 15:36 |
*** maaritamm has quit IRC | 15:36 | |
amotoki | it covers python impl side. | 15:36 |
*** gyee has joined #openstack-meeting-alt | 15:36 | |
vishalmanchanda | yeah. | 15:36 |
amotoki | I think we also need corresponding changes on Angular side | 15:36 |
*** maaritamm has joined #openstack-meeting-alt | 15:36 | |
amotoki | it would be an action item in Victoria | 15:36 |
vishalmanchanda | yeah. | 15:37 |
e0ne | sounds reasonable | 15:37 |
*** maaritamm has quit IRC | 15:38 | |
amotoki | moving on | 15:38 |
amotoki | #topic community goals | 15:38 |
*** openstack changes topic to "community goals (Meeting topic: horizon)" | 15:38 | |
amotoki | we did not cover this topic for long | 15:39 |
amotoki | Ussuri community goal is found at https://governance.openstack.org/tc/goals/selected/ussuri/index.html | 15:39 |
amotoki | we completed "Drop Python 2.7 Support" | 15:39 |
amotoki | I plan to work on "Project Specific PTL and Contributor Documentation" during the RC period | 15:40 |
*** maaritamm has joined #openstack-meeting-alt | 15:40 | |
amotoki | the template landed later in the cycle and it does not affect our ussuri deliverable, so I believe it makes sense. | 15:40 |
e0ne | +1 | 15:41 |
amotoki | and while we didn't cover it in our meetings, we finally completed mox removal :) | 15:42 |
*** maaritamm has quit IRC | 15:42 | |
amotoki | it is achieved as collaboration with several folks. it is very nice. | 15:43 |
amotoki | #topic bugs/reviews | 15:44 |
*** openstack changes topic to "bugs/reviews (Meeting topic: horizon)" | 15:44 | |
amotoki | anything to raise? | 15:45 |
vishalmanchanda | none from my side. | 15:45 |
amotoki | I have one on stable/train (while it is not urgent) | 15:46 |
amotoki | https://review.opendev.org/#/c/710174/ | 15:46 |
amotoki | e0ne: hopefully you can have a feedback on this | 15:46 |
e0ne | amotoki: will review it after the meeting | 15:46 |
amotoki | e0ne: thanks. it is related to a dilemma between cinderclient 5 and stalbe/train dependency (cinderclient 4) | 15:47 |
amotoki | e0ne: no detail review is needed. a feedback on rough direction would be appreicated | 15:48 |
amotoki | #topic open discussion | 15:48 |
*** openstack changes topic to "open discussion (Meeting topic: horizon)" | 15:48 | |
amotoki | anything to discuss? | 15:49 |
e0ne | nothing from me | 15:50 |
amotoki | I interprete silience means nothing :) | 15:51 |
vishalmanchanda | nothing | 15:51 |
amotoki | thanks all for joining | 15:51 |
amotoki | I would like to cover pending reviews for ussuri in the meeting next week. | 15:51 |
amotoki | have a great week and care yourselves | 15:51 |
amotoki | #endmeeting | 15:51 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 15:51 | |
vishalmanchanda | ok guys. Sayonara! | 15:51 |
openstack | Meeting ended Wed Apr 1 15:51:48 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:51 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-04-01-15.01.html | 15:51 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-04-01-15.01.txt | 15:51 |
openstack | Log: http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-04-01-15.01.log.html | 15:51 |
*** maaritamm has joined #openstack-meeting-alt | 16:06 | |
*** maaritamm has quit IRC | 16:07 | |
*** maaritamm has joined #openstack-meeting-alt | 16:12 | |
*** maaritamm has quit IRC | 16:15 | |
*** maaritamm has joined #openstack-meeting-alt | 16:15 | |
*** maaritamm has quit IRC | 16:19 | |
*** maaritamm has joined #openstack-meeting-alt | 16:19 | |
*** maaritamm has quit IRC | 16:23 | |
*** maaritamm has joined #openstack-meeting-alt | 16:23 | |
*** maaritamm has quit IRC | 16:26 | |
*** sfernand has quit IRC | 16:29 | |
*** jcoufal has quit IRC | 17:28 | |
*** gmann is now known as gmann_lunch | 17:56 | |
*** lbragstad_ has joined #openstack-meeting-alt | 17:59 | |
*** lbragstad_ is now known as lbragstad | 17:59 | |
*** lbragstad has quit IRC | 18:00 | |
*** lbragstad has joined #openstack-meeting-alt | 18:00 | |
*** yamamoto has quit IRC | 18:13 | |
*** yamamoto has joined #openstack-meeting-alt | 18:14 | |
*** yamamoto has quit IRC | 18:19 | |
*** lbragstad_ has joined #openstack-meeting-alt | 18:20 | |
*** lbragstad has quit IRC | 18:23 | |
*** yamamoto has joined #openstack-meeting-alt | 18:25 | |
*** gmann_lunch is now known as gmann | 18:28 | |
*** lbragstad_ is now known as lbragstad | 18:28 | |
*** diablo_rojo has quit IRC | 18:32 | |
*** diablo_rojo has joined #openstack-meeting-alt | 18:33 | |
*** e0ne has quit IRC | 18:38 | |
*** e0ne has joined #openstack-meeting-alt | 18:38 | |
*** e0ne has quit IRC | 18:39 | |
*** maaritamm has joined #openstack-meeting-alt | 18:42 | |
*** lbragstad has quit IRC | 18:50 | |
*** enriquetaso has quit IRC | 19:11 | |
*** yamamoto has quit IRC | 19:16 | |
*** throne82_ has quit IRC | 19:22 | |
*** maaritamm has quit IRC | 19:26 | |
*** maaritamm has joined #openstack-meeting-alt | 19:27 | |
*** early` has quit IRC | 19:36 | |
*** derekh has quit IRC | 19:40 | |
*** early has joined #openstack-meeting-alt | 19:44 | |
*** yamamoto has joined #openstack-meeting-alt | 19:47 | |
*** yamamoto has quit IRC | 19:57 | |
*** e0ne has joined #openstack-meeting-alt | 20:11 | |
*** gshippey has quit IRC | 20:21 | |
*** igordc has joined #openstack-meeting-alt | 20:27 | |
*** vishalmanchanda has quit IRC | 20:39 | |
*** maaritamm has quit IRC | 20:52 | |
*** slaweq has quit IRC | 20:54 | |
*** slaweq has joined #openstack-meeting-alt | 21:12 | |
*** ttsiouts has quit IRC | 21:22 | |
*** ttsiouts has joined #openstack-meeting-alt | 21:54 | |
*** enriquetaso has joined #openstack-meeting-alt | 21:56 | |
*** ijw has joined #openstack-meeting-alt | 21:57 | |
*** ttsiouts has quit IRC | 21:59 | |
*** ijw_ has quit IRC | 22:01 | |
*** frickler_ has joined #openstack-meeting-alt | 22:03 | |
*** ijw_ has joined #openstack-meeting-alt | 22:03 | |
*** ijw has quit IRC | 22:06 | |
*** melwitt has quit IRC | 22:08 | |
*** aspiers has quit IRC | 22:08 | |
*** frickler has quit IRC | 22:08 | |
*** carthaca has quit IRC | 22:11 | |
*** e0ne has quit IRC | 22:20 | |
*** e0ne has joined #openstack-meeting-alt | 22:21 | |
*** ayoung has joined #openstack-meeting-alt | 22:23 | |
*** slaweq has quit IRC | 22:31 | |
*** ttsiouts has joined #openstack-meeting-alt | 22:36 | |
*** macz_ has quit IRC | 22:44 | |
*** aspiers has joined #openstack-meeting-alt | 22:44 | |
*** lbragstad has joined #openstack-meeting-alt | 22:47 | |
*** melwitt has joined #openstack-meeting-alt | 22:51 | |
*** enriquetaso has quit IRC | 23:11 | |
*** e0ne has quit IRC | 23:13 | |
*** ayoung has quit IRC | 23:15 | |
*** ayoung has joined #openstack-meeting-alt | 23:16 | |
*** enriquetaso has joined #openstack-meeting-alt | 23:20 | |
*** ayoung has quit IRC | 23:40 | |
*** ayoung has joined #openstack-meeting-alt | 23:41 | |
*** enriquetaso has quit IRC | 23:41 | |
*** tetsuro has joined #openstack-meeting-alt | 23:44 | |
*** yamamoto has joined #openstack-meeting-alt | 23:54 | |
*** ayoung has quit IRC | 23:56 | |
*** ayoung has joined #openstack-meeting-alt | 23:58 | |
*** yamamoto has quit IRC | 23:58 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!