Wednesday, 2020-05-06

*** ttsiouts has joined #openstack-meeting-alt00:00
*** ttsiouts has quit IRC00:33
*** rfolco has quit IRC00:35
*** jamesmcarthur has joined #openstack-meeting-alt00:37
*** enriquetaso has quit IRC00:40
*** jamesmcarthur has quit IRC01:17
*** Liang__ has joined #openstack-meeting-alt01:54
*** wxy has joined #openstack-meeting-alt01:59
*** tetsuro has joined #openstack-meeting-alt02:00
*** ttsiouts has joined #openstack-meeting-alt02:30
*** jamesmcarthur has joined #openstack-meeting-alt02:33
*** tetsuro has quit IRC02:37
*** ttsiouts has quit IRC02:39
*** ttsiouts has joined #openstack-meeting-alt02:39
*** vishalmanchanda has joined #openstack-meeting-alt03:03
*** baojg has joined #openstack-meeting-alt03:03
*** ttsiouts has quit IRC03:04
*** jamesmcarthur has quit IRC03:06
*** jamesmcarthur has joined #openstack-meeting-alt03:06
*** tetsuro has joined #openstack-meeting-alt03:06
*** jamesmcarthur has quit IRC03:11
*** tetsuro has quit IRC03:16
*** baojg has quit IRC03:18
*** tetsuro has joined #openstack-meeting-alt03:22
*** jamesmcarthur has joined #openstack-meeting-alt03:41
*** tetsuro has quit IRC03:45
*** tetsuro has joined #openstack-meeting-alt03:47
*** tetsuro has quit IRC03:54
*** openstack has joined #openstack-meeting-alt04:24
*** ChanServ sets mode: +o openstack04:24
*** tetsuro has joined #openstack-meeting-alt04:34
*** gyee has quit IRC04:40
*** ttsiouts has joined #openstack-meeting-alt05:01
*** jamesmcarthur has quit IRC05:04
*** jamesmcarthur has joined #openstack-meeting-alt05:05
*** jamesmcarthur has quit IRC05:11
*** jamesmcarthur has joined #openstack-meeting-alt05:11
*** tetsuro has quit IRC05:25
*** tetsuro has joined #openstack-meeting-alt05:27
*** ttsiouts has quit IRC05:33
*** tetsuro has quit IRC05:43
*** tetsuro has joined #openstack-meeting-alt05:44
*** ysandeep|away is now known as ysandeep05:51
*** diablo_rojo has quit IRC05:57
*** jamesmcarthur has quit IRC06:00
*** jamesmcarthur has joined #openstack-meeting-alt06:01
*** jamesmcarthur has quit IRC06:06
*** tetsuro has quit IRC06:09
*** tetsuro has joined #openstack-meeting-alt06:10
*** ysandeep is now known as ysandeep|away06:12
*** tetsuro has quit IRC06:15
*** yamamoto has joined #openstack-meeting-alt06:18
*** yamamoto has quit IRC06:24
*** roman_g has joined #openstack-meeting-alt06:28
*** ysandeep|away has quit IRC06:29
*** jamesmcarthur has joined #openstack-meeting-alt06:39
*** tetsuro has joined #openstack-meeting-alt06:49
*** tetsuro has quit IRC06:50
*** tetsuro has joined #openstack-meeting-alt06:50
*** slaweq has joined #openstack-meeting-alt06:56
*** ttsiouts has joined #openstack-meeting-alt07:04
*** ccamacho has joined #openstack-meeting-alt07:04
*** lpetrut has joined #openstack-meeting-alt07:19
*** roman_g has quit IRC07:41
*** openstack has joined #openstack-meeting-alt07:48
*** ChanServ sets mode: +o openstack07:48
*** ttsiouts has quit IRC08:07
*** ttsiouts has joined #openstack-meeting-alt08:07
*** tetsuro has quit IRC08:26
*** tetsuro has joined #openstack-meeting-alt08:26
*** roman_g has joined #openstack-meeting-alt08:28
*** e0ne has joined #openstack-meeting-alt08:30
*** baojg has joined #openstack-meeting-alt08:40
*** jamesmcarthur has quit IRC08:41
*** tetsuro has quit IRC08:46
*** kaisers_ has joined #openstack-meeting-alt08:59
*** vishakha has joined #openstack-meeting-alt09:00
*** strigazi has joined #openstack-meeting-alt09:00
*** tetsuro has joined #openstack-meeting-alt09:15
*** jamesmcarthur has joined #openstack-meeting-alt09:16
*** Liang__ has quit IRC09:24
*** jamesmcarthur has quit IRC09:26
*** lbragstad has quit IRC09:45
*** tetsuro has quit IRC09:54
*** jamesmcarthur has joined #openstack-meeting-alt09:57
*** ttsiouts has quit IRC09:58
*** ttsiouts has joined #openstack-meeting-alt09:59
*** tetsuro has joined #openstack-meeting-alt10:00
*** jamesmcarthur has quit IRC10:07
*** tetsuro has quit IRC10:12
*** tetsuro has joined #openstack-meeting-alt10:15
*** tetsuro has quit IRC10:16
*** baojg has quit IRC10:18
*** tetsuro has joined #openstack-meeting-alt10:18
*** ttsiouts has quit IRC10:27
*** ttsiouts has joined #openstack-meeting-alt10:30
*** tetsuro has quit IRC10:36
*** jamesmcarthur has joined #openstack-meeting-alt10:43
*** jamesmcarthur has quit IRC10:43
*** jamesmcarthur has joined #openstack-meeting-alt10:43
*** jamesmcarthur has quit IRC10:44
*** jamesmcarthur has joined #openstack-meeting-alt10:44
*** derekh has joined #openstack-meeting-alt10:46
*** tetsuro has joined #openstack-meeting-alt10:48
*** ttsiouts has quit IRC10:48
*** jamesmcarthur has quit IRC10:51
*** jamesmcarthur has joined #openstack-meeting-alt10:58
*** jamesmcarthur has quit IRC10:59
*** jamesmcarthur has joined #openstack-meeting-alt10:59
*** tetsuro has quit IRC11:00
*** jamesmcarthur has quit IRC11:01
*** jamesmcarthur has joined #openstack-meeting-alt11:02
*** priteau has joined #openstack-meeting-alt11:04
*** jamesmcarthur has quit IRC11:07
*** vkmc has quit IRC11:09
*** tetsuro has joined #openstack-meeting-alt11:24
*** ttsiouts has joined #openstack-meeting-alt11:25
*** ttsiouts has quit IRC11:30
*** rfolco has joined #openstack-meeting-alt11:30
*** ttsiouts has joined #openstack-meeting-alt11:32
*** raildo has joined #openstack-meeting-alt11:37
*** yamamoto has joined #openstack-meeting-alt11:40
*** jamesmcarthur has joined #openstack-meeting-alt11:40
*** yamamoto has quit IRC11:42
*** andrebeltrami has joined #openstack-meeting-alt12:01
*** jamesmcarthur has quit IRC12:25
*** tetsuro has quit IRC12:41
*** vkmc__ has joined #openstack-meeting-alt12:50
*** vkmc__ is now known as vkmc12:52
*** jamesmcarthur has joined #openstack-meeting-alt13:01
*** lbragstad has joined #openstack-meeting-alt13:10
*** lbragstad has quit IRC13:13
*** rfolco is now known as rfolco|rover13:13
*** lbragstad has joined #openstack-meeting-alt13:21
*** jamesmcarthur has quit IRC13:21
*** enriquetaso has joined #openstack-meeting-alt13:32
*** ttsiouts has quit IRC13:39
*** enriquetaso has quit IRC13:54
*** enriquetaso has joined #openstack-meeting-alt13:54
*** rosmaita has joined #openstack-meeting-alt13:58
*** eharney has joined #openstack-meeting-alt13:58
*** sfernand has joined #openstack-meeting-alt13:58
*** LiangFang has joined #openstack-meeting-alt13:59
*** tosky has joined #openstack-meeting-alt13:59
rosmaita#startmeeting cinder14:00
openstackMeeting started Wed May  6 14:00:31 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: cinder)"14:00
openstackThe meeting name has been set to 'cinder'14:00
rosmaita#link https://etherpad.openstack.org/p/cinder-ussuri-meetings14:00
rosmaita#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: cinder)"14:00
eharneyhi14:00
rajinirhi14:00
LiangFanghi14:00
smcginniso/14:00
*** throne82_ has joined #openstack-meeting-alt14:00
lsekihi14:01
walshh_hi14:01
jungleboyjO/14:01
sfernandhi14:01
*** jamesmcarthur has joined #openstack-meeting-alt14:01
whoami-rajatHi14:01
rosmaitalooks like a good turnout14:02
e0nehi14:02
enriquetasoo/14:02
rosmaitabefore we get started, i want to say that I hope everyone and their loved ones are healthy and doing well in these stressful times14:02
rosmaitaand even your non-loved ones, i guess14:02
rosmaita#topic updates14:02
*** openstack changes topic to "updates (Meeting topic: cinder)"14:02
rosmaitaok, RC-2 was released on monday14:03
rosmaitahttp://lists.openstack.org/pipermail/openstack-discuss/2020-May/014623.html14:03
rosmaitathat should be our final RC, i haven't seen anyone post any release critical bugs14:03
rosmaitaand we are running out of time to fix them anyway14:03
rosmaitanext item: no meeting next week, you can attend the "community meeting" instead14:04
rosmaitathe next cinder meeting on May 20 will be the first meeting of the Victoria cycle14:04
rosmaitaso, as is our tradition, there will be a new agenda etherpad:14:05
rosmaita#link https://etherpad.opendev.org/p/cinder-victoria-meetings14:05
rosmaitait's empty now because i just thought of it14:05
*** felipe_rodrigues has joined #openstack-meeting-alt14:05
rosmaitabut i'll fill it with the boilerplate stuff after today's meeting14:05
rosmaitaoops i skipped an item14:05
rosmaitaPTG registration is open14:05
rosmaita#link https://virtualptgjune2020.eventbrite.com/14:06
rosmaitait's free, but the foundation would like to keep track of who's planning to attend14:06
rosmaitawill also get you on the mailing list about communication methods14:06
rosmaita(which i don't think have been decided yet)14:06
rosmaitaso please register14:07
rosmaitaand on that note, we could use some topics on the Cinder PTG etherpad14:07
rosmaita#link https://etherpad.openstack.org/p/cinder-victoria-ptg-planning14:07
rosmaitathe times for the cinder meetings are on that etherpad ^^14:08
rosmaitaany questions about the PTG?14:08
*** ttsiouts has joined #openstack-meeting-alt14:08
rosmaitaok, there's always open discussion later if you think of something14:09
rosmaitafinal announcement14:09
rosmaitayesterday or this morning, depending on where you are, we merged a change related to eventlet and monkey patching14:09
rosmaita#link https://review.opendev.org/#/c/724754/14:10
rosmaitaif you want the background:14:10
jungleboyjThanks for putting the Timezones in there.14:10
rosmaita#link https://github.com/eventlet/eventlet/issues/59214:10
rosmaitathis is just awareness, in case anything weird starts happening ... because you never know14:10
smcginnisEspecially with eventlet.14:11
smcginnis"You never know" ^14:11
rosmaita:)14:11
rosmaitaok, that's all the announcements14:11
rosmaita#topic  coordination with barbican(-tempest-plugin) people on volume tests14:11
*** openstack changes topic to " coordination with barbican(-tempest-plugin) people on volume tests (Meeting topic: cinder)"14:11
rosmaitaso, we have an interesting situation14:12
rosmaitaour encrypted volume tests need access to barbican14:12
rosmaitaand the easiest way to do that is to have them live in the barbican-tempest-plugin14:12
rosmaitasomething about circular dependencies, tosky can explain if you are interested14:12
rosmaitaanyway, i think that's why he put it on the agenda14:12
rosmaitatosky: you're up14:13
enriquetaso++14:13
toskywe may benefit from an increased amount of cinder tests that use barbican14:13
rosmaitai poked around a bit, there is no barbican-tempest-plugin core group14:13
*** ttsiouts has quit IRC14:13
rosmaitait's just barbican-core14:13
rosmaitado we want to propose to help maintain that plugin14:14
toskynow, the barbican tempest client is defined inside barbican-tempest-plugin and they also have a few tests there14:14
toskysome of them mirror the corresponding basic encryption tests from tempest.git, but with a barbican flavor14:14
rosmaitaor could we propose re-architecting it so that we can use the stuff we need in the cinder-tempest-plugin?14:14
rosmaita(sorry, tosky i should let you talk)14:14
toskyI would say it may be easier to see if they could agree with having some of us voting on those patches, with the agreement of not approving non-volume tests (or waiting anyway for other approvals)14:15
toskyI took the liberty of raising this point at yesterday's barbican meeting, but as I haven't discussed about it here before, I didn't go in details14:15
toskyhttp://eavesdrop.openstack.org/meetings/barbican/2020/barbican.2020-05-05-13.01.log.html14:15
rosmaitawell, looks like they didn't tell you to go boil your head14:16
jungleboyj:-)14:16
rosmaitai can propose something on the ML like we did for ceph and nfs devstack plugins14:17
rosmaitaand will stress the gentleperson's agreement not to approve anything non-volume related14:17
toskyyes, that could help, maybe we can define this before the PTG, and then use that time to refine and/or implement it properly14:17
enriquetasoOne question: should I move the retype encrypt test to barbican-tempest-plugin then? https://review.opendev.org/#/c/715566/14:17
rosmaitaenriquetaso: good question, i was wondering about that myself14:18
eharneysince that retype test doesn't need to interact with barbican directly (and in theory could work with other key managers as well), i think not14:18
eharneyit's purely a cinder functionality test14:18
toskyright: if it does not use the barbican client, it can stay there14:19
enriquetaso++14:19
enriquetasothanks14:19
toskyI don't have anything else to add about this right now; the direction is "discuss and find an agreement"14:20
toskyIMHO14:20
rosmaitaok, i'll put up something to the ML to get this moving and we can follow up as necessary14:21
toskythanks!14:21
rosmaita#action rosmaita email about cooperation with barbican-tempest-plugin14:21
rosmaitaok, thanks tosky14:21
rosmaita#topic security-related issue  when an attached volume exposes host information to non-admins 14:22
*** openstack changes topic to "security-related issue  when an attached volume exposes host information to non-admins  (Meeting topic: cinder)"14:22
rosmaitawhoami-rajat: that's you14:22
*** ttsiouts has joined #openstack-meeting-alt14:22
whoami-rajatSo we discussed a security issue during cinder mid-cycle PTG, the summary of the issue is, an attached volume could expose the nova host details via the volume show API and attachments API14:22
*** jamesmcarthur has quit IRC14:22
*** jhesketh has quit IRC14:22
whoami-rajatthe general consensus on lauchpad was to change the policy of the attachment API to admin only14:22
whoami-rajatbut this might have affect on the consumer projects such as nova and glance14:23
eharneythat policy being, to only how the host to admins?14:24
eharneyonly show*14:24
whoami-rajatyes14:24
whoami-rajatin volume show API, show host to only admins and in attachments API only show connection_info to admins14:24
rosmaitabut in volume-show, don't you get the same stuff as attachments api as far as connection_info ?14:25
whoami-rajatrosmaita, i'm not sure, the bug is only reported against the HOST field14:26
whoami-rajati will check that as well14:26
rosmaitaalso, we should probably be clear about what "host" we are talking about14:26
rosmaitathis is the attatched_host ?14:26
whoami-rajatIIUC it's the nova host14:26
whoami-rajatwhere the volume is attached14:27
rosmaitaok14:27
rosmaitayeah, nova does not like to expose the VM host to users14:28
whoami-rajati just posted this topic here for a general discussion and gather opinions on the path on which we should move ahead14:28
whoami-rajati think nova also has some policy rules for not exposing the host info to non-admins14:28
rosmaitai think the issue is that nova does not like this being available as a backdoor for a user to discover the host info14:29
whoami-rajatyep14:29
smcginnisIt is a concern for leaking out underlying infrastructure information.14:29
jungleboyjRight.14:30
rosmaitai don't know if this makes sense, but14:30
rosmaitaif we keep the volume-show and attachments api the way they are now14:30
rosmaitaadmin or owner14:30
*** lpetrut has quit IRC14:30
rosmaitaand only hide the attached_host, how does that affect usefulness of the response14:30
rosmaita?14:30
smcginnisI wouldn't think anyone (person or system) should be relying on that information for anything.14:31
rosmaitayeah, my intuition is that the person making the connection knows who they are already14:32
eharneythat's kind of my gut feeling too14:32
jungleboyjThat would be my thought.14:32
rosmaitaso i guess whoami-rajat's next question is, do we need a policy on that single field? or do we just do an internal "is_admin" check and display or not?14:33
rosmaitaor maybe just never display?14:33
smcginnisMight be worth calling it out on the ML that responses will be changing and why. That way if for some reason someone actually is paying attention to that information in this response, they have a warning not to do so anymore.14:33
rosmaitasmcginnis: ++14:33
smcginnisI would vote never display. Unless maybe is_admin, since an admin may be able to use that information to troubleshoot or something.14:33
rosmaitasince this is a security issue, i don't think we need to worry about microversioning this change?14:34
whoami-rajatalso JFYI from the raw response of attachment API, non-admins can get this all info https://bugs.launchpad.net/cinder/+bug/1736773/comments/114:34
openstackLaunchpad bug 1736773 in Cinder "attachment-show is including `connection_info` for non-admin callers, it shouldn't" [High,Triaged] - Assigned to John Griffith (john-griffith)14:34
smcginnisrosmaita: Agree14:34
jungleboyjAgreed.14:34
eharneyshouldn't need microversioning since this field can already be blank etc now14:34
smcginniswhoami-rajat: Hmm, that's a concern too.14:34
whoami-rajatit contains auth_password which i'm not sure how important but a password shouldn't show up in an API response i guess14:35
eharneydepends, is that api used to connect to volumes?14:36
eharneyi guess this is after it's already attached/connected14:37
whoami-rajathmm, i think nova uses initialize_connection to connect and attachment_update to get the connection_info later14:37
whoami-rajatbut i'm not sure if they use attachment_get for any purpose14:37
whoami-rajatrefresh*14:38
*** ttsiouts has quit IRC14:38
*** ccamacho has quit IRC14:39
rosmaitaok, looks like we may need some research here14:40
rosmaitaok, so to summarize: (1) should not populate the host_name in the volume-show response (except to admins); propose to rely on the admin context to decide whether to show or not; since no change to response, no need to microversion this14:42
rosmaita(2) need to verify that connection_info is not required for non-admin users in the attachment-show response14:42
rosmaitaand depending on the outcome of (2), will either hide the connection_info or just depopulate the attached_host (or whatever it's called in that response)14:43
whoami-rajatchanging the attachments api to admin only would require nova changes so i think this needs discussion with the nova team as well14:43
whoami-rajatrosmaita, that sounds like a good plan to me14:43
rosmaitawhoami-rajat: do you want to continue to pursue this and we can also discuss (2) at ptg?14:44
whoami-rajatrosmaita, sure14:44
rosmaitai can send an email out about (1) since i think that won't affect anyone really14:44
whoami-rajati think i can also work on this i parts since only 2 is the concern14:45
rosmaitaand it's ok to discuss on the ML because this bug has been public since at least the cinder midcycle14:45
whoami-rajatrosmaita, that would be great14:45
rosmaita#action rosmaita (see above)14:45
rosmaitaok, thanks whoami-rajat14:45
whoami-rajatthanks everyone14:45
rosmaita#topic priorities for victoria milestone-114:45
*** openstack changes topic to "priorities for victoria milestone-1 (Meeting topic: cinder)"14:45
rosmaitai lost my tab, but M-1 is like 2 weeks after the ptg14:46
rosmaitaanyway, the cinder team priorities are:14:46
rosmaita(1) volume local cache, and14:46
rosmaita(2) nfs encryption14:46
rosmaitaLiangFang is working on 1, enriquetaso is working on 214:47
rosmaita#topic volume local cache14:47
*** openstack changes topic to "volume local cache (Meeting topic: cinder)"14:47
rosmaitaLiangFang: that's you14:47
LiangFangthanks rosmaita14:47
LiangFangshould I add this topic in PTG?14:47
LiangFangone thing in cinder patch is:14:48
rosmaitayes, if things aren't moving along well, or if some things come up that require discussion14:48
LiangFangvolume type extra-spec without prefix "capabilities:" will be treated as filter. See: https://github.com/openstack/cinder/blob/master/cinder/scheduler/filters/capabilities_filter.py#L6214:48
LiangFangI just copied from patch comment14:48
LiangFangSo extra-spec "cacheable" will be treated as filter. As discussed in spec, some backends like nfs and rbd will not be supported. So I'm trying to enable the supported backends explicitly. Any backends not marked "cacheable=True" will not be supported by default. It is like white list mode. We may can go through backends drivers and add more drivers as supported later in a following patch.14:48
eharneyi need to study up on this again, but i (still) think it's not correct to put this as a flag in the LVM driver14:49
LiangFangok14:49
eharneyas far as i can tell, it isn't a driver attribute, it's a protocol attribute14:49
eharneyyour suggestion is currently: enable this flag in every iscsi/fc driver (i think)14:49
eharneywe should just have the manager apply it to iscsi/fc etc as appropriate without requiring driver changes, unless we think there are driver-specific reasons that caching won't work14:50
*** jhesketh has joined #openstack-meeting-alt14:51
LiangFangif we add like: capabilities:cacheable14:51
LiangFangthen it is not act as filter14:51
LiangFangbut how to prevent nfs and rbd14:52
eharneyi think the point about "capabilities:" is correct but i haven't yet figured out why that means we need to do this inside the driver14:52
LiangFangif we don't add capabilities:14:53
LiangFangthen cacheable will be treat as a filter, that means if the driver is not marked as "cacheable", it will not be scheduled14:54
LiangFangat last, will pop up like "can not find a valid backend"14:55
eharneyi'll do some research into how that works, but i think the point remains that "cacheable" isn't actually a property of the driver -- so it should be set somewhere else14:55
eharneyi don't know enough of the details to get to the bottom of it right now14:55
LiangFangeharney: thanks, may can see: https://github.com/openstack/cinder/blob/master/cinder/scheduler/filters/capabilities_filter.py#L6214:56
LiangFanganother thing is about testing14:56
LiangFangI find I cannot finish tempest test at this point14:57
LiangFangbecause tempest test requires the patches ready first14:57
LiangFangthere're 3 patches, cinder, os-brick, nova14:58
rosmaitaso is the issue that: 'cacheable' is a property of the volume-type, but the way it is expressed now prevents some drivers from being scheduled at all?14:58
LiangFangrosmaita: yes14:58
*** smcginnis has quit IRC14:58
rosmaitasorry, we are almost out of time ... looks like we need to continue to discuss this at next meeting and PTG14:58
LiangFangcacheable in type will schedule no backends14:58
eharneyyou can still apply it for all relevant drivers, for them to be scheduled, in the manager rather than in the driver code14:59
LiangFangrosmaita: Ok, thanks14:59
LiangFangeharney: maybe I need to study how to add in manager14:59
enriquetasoOne quick thing About (2) I re based the patch this week because of merge conflicts, but know it's ready for reviews https://review.opendev.org/#/c/597148/ . Please feel free to add comments14:59
rosmaitasounds like something to look at14:59
LiangFangeharney: may be you are right14:59
rosmaitaenriquetaso: thanks !15:00
rosmaitaok, thanks everyone, we need to get out of the way for Horizon15:00
rosmaita#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Wed May  6 15:00:28 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-05-06-14.00.html15:00
whoami-rajatThanks!15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-05-06-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-05-06-14.00.log.html15:00
jungleboyjThanks!15:00
*** lpetrut has joined #openstack-meeting-alt15:00
*** tosky has left #openstack-meeting-alt15:00
amotoki#startmeeting horizon15:02
openstackMeeting started Wed May  6 15:02:11 2020 UTC and is due to finish in 60 minutes.  The chair is amotoki. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: horizon)"15:02
openstackThe meeting name has been set to 'horizon'15:02
amotokihi15:02
vishalmanchandahi15:02
amotoki#chair e0ne15:02
openstackCurrent chairs: amotoki e0ne15:02
e0nehi15:02
amotokilet's start15:03
amotokiI first would like to cover topics around the ussuri release and then pass the chair to e0ne for further discussions.15:03
amotoki#topic announcements/notices15:03
*** openstack changes topic to "announcements/notices (Meeting topic: horizon)"15:03
amotokithis week is the week of final RC and final intermediary release15:04
amotokiI will cut another release of horizon tomorrow15:04
amotokimainly to import translations15:04
vishalmanchandagreat.15:04
*** smcginnis has joined #openstack-meeting-alt15:04
e0neamotoki: do we have any critical bugs for Ussuri?15:05
amotokie0ne: I don't see any so far15:05
e0neit's good:)15:05
amotokiussuri will be released next week15:06
e0ne#link https://releases.openstack.org/ussuri/schedule.html15:06
*** rosmaita has left #openstack-meeting-alt15:07
amotokiI think e0ne will start to host the team meeting next week as victoria cycle is officially open :)15:08
e0nefair eniough15:09
vishalmanchanda🙂)15:09
amotokias you may notice, next week there will be also community meeting where various people will highlight project achievements in Ussuri: http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014646.html15:10
amotokiI am not sure I can join but if you have interest feel free to join15:10
e0neamotoki: thanks for the reminder! I totally forgot about it15:11
vishalmanchandae0ne: Also do we need to book some room for ptg as mentioned in this ML http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014650.html15:12
e0nevishalmanchanda: horizon in the list15:12
e0nevishalmanchanda: I've already booked a room15:12
vishalmanchandae0ne: oh cool.15:12
amotokivishalmanchanda: the list there is a list of team who already booked :)15:13
vishalmanchandai have just see horizon but not read the complete mail :).15:13
e0ne:)15:13
*** ttsiouts has joined #openstack-meeting-alt15:13
amotokie0ne: anything to share on PTG?15:14
e0nehere is anetherpad https://etherpad.opendev.org/p/horizon-v-ptg15:14
e0ne*etherpad15:14
amotokiI haven't added topics.. :(15:14
e0nemee to15:15
e0nethere are 3 time slots there. it should be enogh15:15
e0ne*enough15:15
amotokiyeah i think so15:16
amotokithe registration for the virtual PTG is now open15:16
amotokihttp://lists.openstack.org/pipermail/openstack-discuss/2020-May/014649.html15:16
e0neregistration is free now:)15:16
*** ccamacho has joined #openstack-meeting-alt15:17
vishalmanchandaI have already done registration.15:17
*** LiangFang has quit IRC15:18
vishalmanchandaMaybe now more people can join as it's free.15:18
vishalmanchandaLet's see.15:18
*** ttsiouts has quit IRC15:18
amotokimy final topic to share is http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014691.html15:19
amotokiOpenDev events are prepared virtually too.15:20
amotokithis is just FYI.15:20
amotokianything other to share?15:21
e0neI'm afraid, all events will be virtual this year :(15:22
amotokiyeah, our life has totally changed15:22
e0nethat's true15:22
amotokiit would be a good chance to rethink why we travels :)15:23
e0neI still hope, I'll have a vacation with some hiking this year15:23
amotokihope the situation gets better15:25
e0ne+115:25
vishalmanchanda+1.15:25
amotokianything to discuss today?15:26
e0nenothing from my side15:26
vishalmanchandanothing from my side.15:27
amotokiokay, we can wrap up the meeting earlier.15:27
vishalmanchandabye bye!15:27
amotokilet's add topics to the ptg etherpad15:27
amotokitake care yourselves.15:27
amotokithanks all15:27
e0nekeep yourself safe15:27
amotoki#endmeeting15:27
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:28
openstackMeeting ended Wed May  6 15:27:59 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-05-06-15.02.html15:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-05-06-15.02.txt15:28
amotokio/15:28
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-05-06-15.02.log.html15:28
*** roman_g has quit IRC15:33
*** roman_g has joined #openstack-meeting-alt15:34
*** ccamacho has quit IRC15:51
*** gyee has joined #openstack-meeting-alt15:53
*** ttsiouts has joined #openstack-meeting-alt16:05
*** jamesmcarthur has joined #openstack-meeting-alt16:20
*** ttsiouts has quit IRC16:23
*** priteau has quit IRC16:25
*** ttsiouts has joined #openstack-meeting-alt16:41
*** ttsiouts has quit IRC16:51
*** jamesmcarthur has quit IRC16:55
*** sfernand has quit IRC16:58
*** throne82_ has quit IRC17:09
*** irclogbot_3 has quit IRC17:20
*** jamesmcarthur has joined #openstack-meeting-alt17:21
*** irclogbot_2 has joined #openstack-meeting-alt17:23
*** derekh has quit IRC17:26
*** jamesmcarthur has quit IRC17:37
*** jamesmcarthur has joined #openstack-meeting-alt17:38
*** ttsiouts has joined #openstack-meeting-alt17:45
*** ttsiouts has quit IRC17:49
*** lpetrut has quit IRC18:22
*** e0ne has quit IRC18:34
*** felipe_rodrigues has quit IRC18:35
*** enriquetaso has quit IRC18:45
*** enriquetaso has joined #openstack-meeting-alt18:57
*** vishakha has quit IRC19:20
*** jamesmcarthur has quit IRC19:25
*** jamesmcarthur has joined #openstack-meeting-alt19:30
*** ayoung has joined #openstack-meeting-alt19:54
*** diablo_rojo has joined #openstack-meeting-alt20:12
*** enriquetaso has quit IRC20:22
*** jamesmcarthur has quit IRC20:50
*** ayoung has quit IRC20:51
*** jamesmcarthur has joined #openstack-meeting-alt20:51
*** ayoung has joined #openstack-meeting-alt20:55
*** jamesmcarthur has quit IRC21:10
*** jamesmcarthur has joined #openstack-meeting-alt21:16
*** slaweq has quit IRC21:26
*** e0ne has joined #openstack-meeting-alt21:35
*** e0ne has quit IRC21:44
*** raildo_ has joined #openstack-meeting-alt21:45
*** smcginnis has quit IRC21:46
*** raildo has quit IRC21:48
*** enriquetaso has joined #openstack-meeting-alt21:51
*** jamesmcarthur has quit IRC21:55
*** raildo_ has quit IRC22:01
*** enriquetaso has quit IRC22:02
*** smcginnis has joined #openstack-meeting-alt22:05
*** andrebeltrami has quit IRC22:11
*** enriquetaso has joined #openstack-meeting-alt22:14
*** ayoung has quit IRC22:16
*** ayoung has joined #openstack-meeting-alt22:17
*** enriquetaso has quit IRC23:41

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!