Wednesday, 2019-01-09

*** rcernin has quit IRC00:07
*** rcernin has joined #openstack-meeting-alt00:09
*** yamamoto has joined #openstack-meeting-alt00:09
*** slaweq has quit IRC00:18
*** yamamoto has quit IRC00:19
*** macza has quit IRC00:28
*** slaweq has joined #openstack-meeting-alt00:35
*** liuyulong has quit IRC00:39
*** yamamoto has joined #openstack-meeting-alt00:41
*** yamamoto has quit IRC00:45
*** Swami has quit IRC00:46
*** slaweq has quit IRC00:47
*** tetsuro has joined #openstack-meeting-alt00:53
*** iyamahat_ has quit IRC01:09
*** jesusaur has joined #openstack-meeting-alt01:12
*** erlon has joined #openstack-meeting-alt01:15
*** slaweq has joined #openstack-meeting-alt01:18
*** erlon has quit IRC01:22
*** slaweq has quit IRC01:23
*** baojg has quit IRC01:24
*** tetsuro has quit IRC01:41
*** hongbin_ has joined #openstack-meeting-alt01:48
*** macza has joined #openstack-meeting-alt01:53
*** macza has quit IRC01:57
*** gyee has quit IRC03:10
*** markvoelker has joined #openstack-meeting-alt03:11
*** markvoelker has quit IRC03:12
*** apetrich has quit IRC03:16
*** janki has joined #openstack-meeting-alt03:45
*** yamamoto has joined #openstack-meeting-alt03:52
*** yamamoto has quit IRC03:54
*** yamamoto has joined #openstack-meeting-alt03:55
*** diablo_rojo has quit IRC04:00
*** yamamoto has quit IRC04:04
*** yamamoto has joined #openstack-meeting-alt04:05
*** vishalmanchanda has joined #openstack-meeting-alt04:11
*** yamamoto has quit IRC04:12
*** macza has joined #openstack-meeting-alt04:16
*** bhavikdbavishi has joined #openstack-meeting-alt04:22
*** hongbin_ has quit IRC04:24
*** sridharg has joined #openstack-meeting-alt04:27
*** markvoelker has joined #openstack-meeting-alt04:37
*** markvoelker has quit IRC04:42
*** dtrainor_ has joined #openstack-meeting-alt04:53
*** rf0lc0 has joined #openstack-meeting-alt04:53
*** lifeless_ has joined #openstack-meeting-alt04:57
*** jbadiapa has joined #openstack-meeting-alt04:57
*** sridharg has quit IRC05:02
*** jesusaur has quit IRC05:02
*** rfolco has quit IRC05:02
*** dtrainor has quit IRC05:02
*** irclogbot_1 has quit IRC05:02
*** chason has quit IRC05:02
*** lifeless has quit IRC05:02
*** irclogbot_1 has joined #openstack-meeting-alt05:05
*** sridharg has joined #openstack-meeting-alt05:08
*** jesusaur has joined #openstack-meeting-alt05:09
*** bhavikdbavishi has quit IRC05:26
*** bhavikdbavishi has joined #openstack-meeting-alt05:27
*** markvoelker has joined #openstack-meeting-alt06:04
*** radeks has joined #openstack-meeting-alt06:05
*** e0ne has joined #openstack-meeting-alt06:22
*** e0ne has quit IRC06:23
*** macza has quit IRC06:28
*** e0ne has joined #openstack-meeting-alt07:18
*** e0ne has quit IRC07:22
*** rcernin has quit IRC07:26
*** e0ne has joined #openstack-meeting-alt07:47
*** lpetrut has joined #openstack-meeting-alt07:55
*** yikun has quit IRC07:55
*** slaweq has joined #openstack-meeting-alt08:13
*** bhavikdbavishi has quit IRC08:21
*** bhavikdbavishi has joined #openstack-meeting-alt08:22
*** hongbin has quit IRC08:23
*** apetrich has joined #openstack-meeting-alt08:38
*** e0ne has quit IRC08:47
*** yamamoto has joined #openstack-meeting-alt08:56
*** yamamoto has quit IRC08:57
*** ccamacho has joined #openstack-meeting-alt09:16
*** yamamoto has joined #openstack-meeting-alt09:27
*** yamamoto_ has joined #openstack-meeting-alt09:27
*** yamamoto has quit IRC09:31
*** markvoelker has quit IRC09:33
*** yamamoto_ has quit IRC09:33
*** derekh has joined #openstack-meeting-alt09:38
*** carlos_silva has joined #openstack-meeting-alt09:46
*** kopecmartin|off is now known as kopecmartin09:56
*** bhavikdbavishi has quit IRC10:00
*** panda|off is now known as panda10:18
*** e0ne has joined #openstack-meeting-alt10:21
*** pbourke has quit IRC11:10
*** pbourke has joined #openstack-meeting-alt11:12
*** yamamoto has joined #openstack-meeting-alt11:22
*** yamamoto has quit IRC11:23
*** yamamoto has joined #openstack-meeting-alt11:23
*** erlon has joined #openstack-meeting-alt11:34
*** erlon has quit IRC11:40
*** erlon has joined #openstack-meeting-alt12:10
*** yamamoto_ has joined #openstack-meeting-alt12:29
*** e0ne has quit IRC12:30
*** yamamoto has quit IRC12:33
*** erlon has quit IRC12:37
*** raildo has joined #openstack-meeting-alt12:48
*** rf0lc0 is now known as rfolco12:49
*** erlon has joined #openstack-meeting-alt12:52
*** yamamoto_ has quit IRC12:54
*** yamamoto has joined #openstack-meeting-alt12:55
*** yamamoto has quit IRC12:57
*** erlon has quit IRC13:09
*** jcoufal has joined #openstack-meeting-alt13:16
*** dave-mccowan has joined #openstack-meeting-alt13:19
*** sridharg has quit IRC13:20
*** e0ne has joined #openstack-meeting-alt13:24
*** erlon has joined #openstack-meeting-alt13:25
*** yamamoto has joined #openstack-meeting-alt13:28
*** dkrol has joined #openstack-meeting-alt13:50
*** vishalmanchanda has quit IRC13:51
*** yamamoto has quit IRC13:54
dkrol#startmeeting trove14:00
openstackMeeting started Wed Jan  9 14:00:14 2019 UTC and is due to finish in 60 minutes.  The chair is dkrol. 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: trove)"14:00
openstackThe meeting name has been set to 'trove'14:00
dkrolHello All14:00
*** bzurkowski has joined #openstack-meeting-alt14:01
bzurkowskiHello14:01
dkrolHello14:02
dkrolIs there anyone else from Samsung?14:02
*** qwebirc35204 has joined #openstack-meeting-alt14:02
qwebirc35204hi14:02
*** qwebirc35204 has quit IRC14:02
dkrolHello14:03
*** cezary_zukowski_ has joined #openstack-meeting-alt14:03
bzurkowskiLet's wait for Marcin14:03
dkrolWow14:03
dkrolToo many people :)14:03
dkrolAre we waiting for someone?14:04
cezary_zukowski_there are no available slots for Marcin14:06
dkrolWe have python 3 update on our agenda14:08
dkrolIs there anything you can do?14:10
*** munimeha1 has joined #openstack-meeting-alt14:14
dkrolCan we start?14:14
bzurkowski1 more minute pls14:14
*** bzurkowski has left #openstack-meeting-alt14:14
*** vishalmanchanda has joined #openstack-meeting-alt14:15
*** bzurkowski has joined #openstack-meeting-alt14:15
*** mpwiwoarczy has joined #openstack-meeting-alt14:15
bzurkowskiReady, let's go!14:15
mpwiwoarczyhi there14:15
dkrolOk, great let's go14:15
mpwiwoarczywhat is the topic?14:15
dkrol#topic python 3 status14:15
*** openstack changes topic to "python 3 status (Meeting topic: trove)"14:15
dkrolThere was an email from Doug about it14:16
mpwiwoarczyok, I can update status of this task14:16
dkrolAnd there is a wiki page14:16
mpwiwoarczyyeah14:16
mpwiwoarczyI have update wiki tracking page14:16
dkrolWhere is mentioned that we have functional tests running in python 314:17
dkrolWith trove devstack base14:17
mpwiwoarczyactualy, status is up to date in etherpad https://etherpad.openstack.org/p/trove-python-314:17
dkrolBut as far as I now it runs on python 214:17
mpwiwoarczylet me see14:17
dkrolWe should check it14:18
dkrolSo what is an update?14:19
mpwiwoarczywait, we have tests executed under python314:19
mpwiwoarczyintegration tests are closed in tox env which uses python3 version14:20
dkrolHow about functional tests?14:20
dkrolGate tests are mysql functional14:21
mpwiwoarczywhere in your repo functional tests are placed?14:21
dkrolAnd this is our trovestack14:21
mpwiwoarczyare torvestack tests functional?14:21
dkrolYes14:21
dkrolThe main gate test is mysql functional14:21
mpwiwoarczyyeah, and it is done under this change https://review.openstack.org/#/c/604816/14:22
dkrolSo you mean it is run with python 3?14:23
mpwiwoarczyyes, it is14:23
mpwiwoarczythis implementation does the thing https://review.openstack.org/#/c/604816/55/tox.ini14:23
dkrolOk, so please double check the wiki I linked in the agenda for today's meeting and it will be all14:23
dkrolIs there anything left about python 3 support?14:24
mpwiwoarczyall type of tests are now executed via tox and all of them have basepython set to verson 314:24
dkrolThis is great14:24
dkrolSo this goal is completed?14:25
mpwiwoarczyyes, please have a look on etherpad https://etherpad.openstack.org/p/trove-python-314:25
mpwiwoarczyit is up to date14:26
dkrolOk, I cannot do it right now but I will check it later14:26
mpwiwoarczynow we can focus on remaining projects14:26
dkrolWe can move on14:26
*** bzurkowski has quit IRC14:26
dkrol#topic pre upgrade check14:26
*** openstack changes topic to "pre upgrade check (Meeting topic: trove)"14:26
mpwiwoarczyok14:26
dkrolPre upgrade is another topic14:26
*** janki has quit IRC14:26
dkrolI've commited a change about it14:26
dkrolYou should get a notification14:27
*** janki has joined #openstack-meeting-alt14:27
dkrolMy idea was to check if there are instances running with assigned task e. G build, resize etc14:27
*** yamamoto has joined #openstack-meeting-alt14:27
mpwiwoarczyyes, I got review request14:27
dkrolAnd mark it as a warning14:28
mpwiwoarczyI did not study implementation yet but sounds good14:28
dkrolPlease check it and we can discuss it next week14:29
dkrolWe should also thinks about breaking changes in the guest agents14:29
dkrolBut in Stein we didn't intruduce such changes14:29
dkrolAFAIK14:30
dkrolAnyway this was may initial idea to start this work14:30
mpwiwoarczyas first we would need to create blueprints14:30
mpwiwoarczyor there are any?14:31
dkrolPlease check it and if you don't have any comments right now we can talk about it next week14:31
dkrolThe whole framework for this check was already delivered14:32
*** jakub has joined #openstack-meeting-alt14:32
dkrolMy change was to add a function which does something instead of a place holder14:32
dkrolI think we don't need blueprint for it14:32
*** yamamoto has quit IRC14:33
mpwiwoarczyok I will check this change soon14:33
mpwiwoarczyyou can also add cezary_zukowski to reviewers list14:34
dkrolIf no other comments let's move on14:34
dkrolSure14:34
dkrol#topic documentation14:34
*** openstack changes topic to "documentation (Meeting topic: trove)"14:34
dkrolAny update on this topic?14:34
cezary_zukowski_not for now14:35
cezary_zukowski_I think I should talk with guys first about current work done, how to utilize it14:36
cezary_zukowski_move to RST and so on...14:36
dkrolOk, I've take a look at it and I see I can add something to the existing docs14:36
cezary_zukowski_great14:37
dkrolWhat do you mean by current work done?14:37
cezary_zukowski_what is in google docs14:37
dkrolYes, true14:38
dkrolOk, let's read it again and mark what should be moved first to rsts14:38
cezary_zukowski_some people found it useful in #openstack-trove, so I think we can somehow incorporate it in official docs14:39
cezary_zukowski_dkrol: ok, sure14:39
dkrolOk let's move on14:39
dkrol#topic recent changes and current work14:40
*** openstack changes topic to "recent changes and current work (Meeting topic: trove)"14:40
dkrolFrom my side there was trovestack redesignand pre upgrade check14:40
dkrolI've also see some small changes from other people14:40
dkrolTypos and small changes14:41
dkrolIf both my topics will be reviewed and completed I can help with docs14:41
dkrolAlso I started to think about guest agent upgrade14:41
dkrolThat's all from my side14:42
cezary_zukowski_grand14:42
dkrolBut I'm curious what you were doing recently? :)14:42
dkrolAnd what plans do you have for the near future?14:42
cezary_zukowski_to be honest, it's busy time with internal release14:43
cezary_zukowski_although, some changes might be then pushed to open source14:44
dkrolYou were mentioning something in December about coming changes14:45
dkrolIn the new year14:45
dkrolAnd now we have it14:45
dkrolWill there be any good news for trove community?14:46
cezary_zukowski_a yeah, it's about pushing internal changes to upstream due to more people hired, but it haven't started yet14:46
cezary_zukowski_should start soon, bzurkowski should know more details14:46
*** janki has quit IRC14:47
dkrolbzurkowski: any comments?14:47
*** janki has joined #openstack-meeting-alt14:47
*** bzurkowski has joined #openstack-meeting-alt14:48
bzurkowskidkrol: This is still work in progress14:48
dkrolOk, but can you share what is the goal and deadlines?14:49
bzurkowskiThe goal is to have more head counts working full-time on upstreaming Trove14:51
*** janki has quit IRC14:51
*** janki has joined #openstack-meeting-alt14:52
dkrolThat would be great14:52
bzurkowskiWe were very optimistic about January, but unfortunately severaly issues emerged14:52
bzurkowskiI cannot objectively estimate when new head counts will join us14:53
*** janki has quit IRC14:53
dkrolAnd what about time for contribution of current people?14:53
bzurkowskiThis month is very tough14:54
bzurkowskiLots of work for business14:54
dkrolYou mean January or December?14:54
bzurkowskiJanuary14:54
dkrolAh I see14:54
dkrolSo unfortunate14:54
bzurkowskiFrom my side I will try to do some reviews this week14:54
bzurkowskiI know that I already promised that several times14:55
bzurkowskiBut this time I will do my best :)14:55
dkrolSo January for all of you will be difficult?14:56
bzurkowskiYeah, probably14:56
dkrolThere are some changes which require another core contributor review14:56
dkrolI understand14:56
dkrolI hope there will be more time next month14:57
dkrolI suppose we are running out of time14:57
dkrolIf you'd don't have anything else we can finish now14:57
dkrolAnd I wish you all happy new year :)14:58
dkrolAnd I hope see you next week14:58
mpwiwoarczymany thanks, you too14:58
mpwiwoarczybye14:58
dkrol#stopmeeting14:59
cezary_zukowski_see you :)14:59
dkrol#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:59
openstackMeeting ended Wed Jan  9 14:59:15 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2019/trove.2019-01-09-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2019/trove.2019-01-09-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2019/trove.2019-01-09-14.00.log.html14:59
*** mpwiwoarczy has quit IRC14:59
e0ne#startmeeting horizon15:02
openstackMeeting started Wed Jan  9 15:02:12 2019 UTC and is due to finish in 60 minutes.  The chair is e0ne. 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
rdopierao/15:02
*** vishakha has joined #openstack-meeting-alt15:02
e0nerdopiera: hi15:02
jakub#info15:02
vishalmanchanda0/15:02
e0neamotoki: hi. are you around?15:02
amotokihi15:02
e0negreat. looks like we're OK to start today15:03
*** bzurkowski has quit IRC15:03
*** yamamoto has joined #openstack-meeting-alt15:03
e0neI hope, you enjoyed Christmas and New Year holidays15:03
jakubhello all15:03
e0ne#link https://wiki.openstack.org/wiki/Meetings/Horizon#Agenda_for_Next_Meeting15:04
e0ne#topic Notices15:04
*** openstack changes topic to "Notices (Meeting topic: horizon)"15:04
e0neOpenStack Summit  CFP is  open until Wednesday, January 23 at 11:59pm PT.15:05
e0nedon't forget to submit a talk proposal if you're going to do it15:05
*** dkrol has quit IRC15:06
e0ne#link https://www.openstack.org/summit/denver-2019/call-for-presentations/15:06
e0neOpenStack PTG will be in the same location right after the summit15:07
e0ne#link https://www.openstack.org/ptg15:07
e0neamotoki, rdopiera: are we OK to have one day for the PTG?15:07
*** yamamoto has quit IRC15:08
rdopierae0ne: I can't come anywyas, so it's fine by me15:08
e0nerdopiera: :(15:08
*** chason_ has joined #openstack-meeting-alt15:09
e0neI have to answer until January 20th if we want to get some room for PTG discussions15:09
e0neI hope, we'll have some good discussions there15:10
e0neamotoki: are you going to attend the Summit and PTG?15:11
*** PagliaccisCloud has joined #openstack-meeting-alt15:12
amotokiI haven't decided and got approved yet, but i hope so15:13
e0neI didn't get an approval too, but I have some time for it15:13
e0neI'll sent a note to organizers that we're going to attend it. I think we can cancel if if nobody goes15:14
amotokisounds good15:15
e0ne#topic New ceilometer-dashboard repository15:15
*** openstack changes topic to "New ceilometer-dashboard repository (Meeting topic: horizon)"15:15
e0nejakub: could you please share with us what are you proposing?15:15
e0ne#link https://review.openstack.org/#/c/619235/15:17
e0ne#link https://bitbucket.org/ultimumtechnologies/ceilometer-dashboard/src15:17
e0neso Telemetry team are going to create own plugin for Horizon15:18
e0neit's great15:19
amotokiIt seems we need a discussion on naming per Doug's comment15:19
jakubWe would like to add a plugin to horizon for ceilometer. Ceilometer stores data in gnocchi and these data can be displayed in Grafana. But if you want to see it you have to login to Grafana and create some basic structure. And this is the point, our hoziron plugin creates this structure via a button and also can redirect you to the grafana dashboar without need of additional authentication.15:19
jakubWe would like to get the code under Openstack.15:20
jakubRegarding naming - as I just described above, it is not a grafana plugin, therefore there is no need to rename the repository15:21
*** whoami-rajat has joined #openstack-meeting-alt15:21
amotokiA dashboard for telemetry is a missing point for a long time :)15:21
amotokijakub: I see. AFAIU, it is a horizon plugin which leverages/redirects to grafana UI15:21
amotokiis it right?15:22
jakubbasically yes15:22
jakubbut not only15:22
*** hongbin has joined #openstack-meeting-alt15:22
amotokiack15:23
amotokifrom the governance perspective, we need an ack from the telemetry PTL15:23
e0neamotoki: +115:23
amotokiwe use plugin model now. this means dashboard supports for non-core features are hosted by corresponding projects.15:24
amotokido we see any blocking issue from horizon perspective?15:24
e0nenothing I'm familiar with15:25
amotokiI haven't followed comments/discussions in the proposed review yet. I will look thru it tomorrow.15:25
e0nejakub asked me if horizon team wants to share responsibility to maintain this plugin15:25
e0nein general, we don't have capacity to maintain plugins too15:26
e0nebut I think it's reasonable if horizon team will have +2 on plugins for some emergency cases .e.g. if gate is blocked by some horizon or dependency changes15:27
e0neIMO, that's all we can do15:27
amotokidoes "share" mean that both the telemetry and horizon teams co-maintain it?15:27
jakube0ne: yes I have asked you because PTL of Telemetry did not want to share the responsibility15:28
e0nejakub: it's up to your team15:28
amotokijakub: does it mean that the telemetry team cannot host it?15:28
jakubjust a note, I am not member of Telemetry team15:29
amotokijakub: or would the telemetry team like to maintain it by themselves?15:29
amotoki"share" means some team shares some reponsibility with another team15:30
amotokiso I am a bit confused with the statement.15:30
jakubamotoki: yes, AFAIK they do not want to host it15:30
e0nehm...15:30
e0nejakub: so who will maintain it?15:30
jakubour company, if is that what you are asking15:31
e0neI'm confused now15:32
amotokithis sounds a governance discussion. we need to consider both maintenance bandwidth and which project can host it.15:32
e0neamotoki: +115:32
amotokire: the maintenance bandwidth, jakub's company can provide it (at least for now)15:33
jakubthe question is also whether it needs to be official or unofficial15:33
jakubif there is any difference15:33
amotokire: the project governance there are several choces: horizon official , telemetry official and unofficial15:34
amotokire: the diffrence between offical vs unofficial, at least contributors to official projects get ATC status15:35
amotokiin addition, "official" would be a good reason to contribute such project more compared to "unofficial" ones.15:35
*** yamamoto has joined #openstack-meeting-alt15:36
e0neit would be good it telemetry project can host it15:36
amotokiI think it is better to raise this to TC with what we discussed so far.15:37
e0ne I'm not sure that we should host it under Horizon umbrella15:37
*** lpetrut has quit IRC15:37
amotokiincluding the fact that the telemetry PTL would like not to host it (in personal conversation?)15:37
jakubre: yes, via email15:38
amotokiAFAIK, this is the first case that any project would like not to host its dashboard.15:38
e0neamotoki: :(15:38
*** purplerbot has quit IRC15:38
jakubwe do not insist on the official.. originaly I went unofficial but as you can see in the change request Andreas Jaeger wanted me to create it under governance so that is why I am here now15:38
*** yikun has joined #openstack-meeting-alt15:39
jakubwe simply wanted to be somehow under openstack not necessarily official15:39
amotokijakub: yeah, generally speaking it is a good suggestion, but the situation seems a bit complicated..... we didn't expect it :(15:39
jakubamotoki: me neither :)15:39
amotokiso what is the next step?15:39
jakubthat is what I would like to know as well15:40
amotokiI see two ways: (1) raise this situation to TC, or (2) create a repo as unofficial project.15:40
jakubhow can I do the (2) ?15:41
amotokijakub: it is simple. what we need to do is to send a mail explaining the current situation to openstack-discuss ML with [tc] tag.15:42
e0nejakub: here is some manual https://docs.openstack.org/infra/system-config/unofficial_project_hosting.html15:42
*** yamamoto has quit IRC15:42
amotokiyou can also join TC meetings to discuss it but I believe sending a mail to the ML is a good first step15:43
jakubamotoki: what is ML?15:43
jakubI see now15:43
amotokijakub: openstack-discuss ML15:43
e0nejakub: mailing list15:43
jakubok then, I will do that15:43
amotokiaha, ML was a common abbrev of mailing list, but it now means machine learning :)15:43
amotokijakub: when you send a mail, could you iinclude "[tc][telemetry][horizon]" in the subject?15:45
amotokithis is what I mean by "tag".15:45
jakubsure, I can15:45
amotokiwe can support the discussion then.15:45
jakubok, thank you15:46
e0nejakub: thanks for raising this topic15:46
*** purplerbot has joined #openstack-meeting-alt15:46
e0necan we move forward? I've got one more topic to discuss15:47
jakubthanks15:47
e0ne#topic unused XStatic-* packages15:48
*** openstack changes topic to "unused XStatic-* packages (Meeting topic: horizon)"15:48
e0newe've got few xstatic-* libraries which we don't use in Horizon and they were not released at all15:48
e0nee.g. https://github.com/openstack/xstatic-angular-ui-router15:48
e0nedo we want to drop them from horizon deliverables?15:49
e0nesuch repos were created about two years ago and we still don't use them15:50
amotokiI am okay to drop them unless any horizon plugins depend on it15:50
amotokis/it/them/15:50
e0neamotoki: I don't think somebody uses them because we don't have any releases15:51
e0nebut I'll double check before removing them15:51
amotokiyeah, agree15:51
e0nethat's all from me today15:51
e0ne#topic Open Discussion15:51
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"15:51
amotokiI have one topic to discuss.15:51
amotokiit is about error reporting15:51
amotokican I go?15:52
e0nesure15:53
e0newe've got 7 minutes more15:53
amotokihorizon now catches an exception from back-end services and creates error messages in our code.15:53
amotokiit hides the detail and we receive many bug reports on insufficient messages.15:53
amotokiAFAIK, it is done from two reasons.15:54
*** bhavikdbavishi has joined #openstack-meeting-alt15:54
amotokithe one is to hide too *more detail* from back-end services like UUID15:54
amotokithe other is for translation. we cannot translate messages from back-end services.15:55
e0neI'm OK to show exception messages from the APIs but not full tracebacks15:55
amotokihowever, I think detail information is more important than the above two reasons.15:55
amotokimy proposal is to include exception strings to error messages.15:55
amotokie0ne: yeah, it is same as mine15:56
e0neI'm glad to be on the same page with the rest of the team15:56
amotokiwhat in my mind is like this https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/networks/workflows.py#L499-L50215:57
amotokiat least some leading messages can be translated :)15:58
*** purplerbot has quit IRC15:58
e0ne:)15:58
amotokii think we can do this gradually15:59
*** purplerbot has joined #openstack-meeting-alt15:59
amotokithat's all from me.16:00
e0ne+116:00
e0nethanks for the participation! see you next week16:00
e0ne#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Wed Jan  9 16:00:52 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2019/horizon.2019-01-09-15.02.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2019/horizon.2019-01-09-15.02.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2019/horizon.2019-01-09-15.02.log.html16:00
*** hongbin has quit IRC16:03
*** bhavikdbavishi has quit IRC16:04
*** bhavikdbavishi has joined #openstack-meeting-alt16:04
*** thgcorrea has joined #openstack-meeting-alt16:08
*** yamamoto has joined #openstack-meeting-alt16:10
*** yamamoto has quit IRC16:14
*** gyee has joined #openstack-meeting-alt16:18
*** jakub has quit IRC16:21
*** diablo_rojo has joined #openstack-meeting-alt16:26
*** lhinds has quit IRC16:37
*** rnoriega has quit IRC16:38
*** macza has joined #openstack-meeting-alt16:38
*** kopecmartin has quit IRC16:39
*** haleyb|away has quit IRC16:39
*** lhinds has joined #openstack-meeting-alt16:40
*** rnoriega has joined #openstack-meeting-alt16:43
*** iyamahat has joined #openstack-meeting-alt16:51
*** e0ne has quit IRC17:03
*** yamamoto has joined #openstack-meeting-alt17:24
*** yamamoto has quit IRC17:29
*** derekh has quit IRC17:56
*** yamamoto has joined #openstack-meeting-alt17:56
*** yamamoto has quit IRC18:01
*** bhavikdbavishi1 has joined #openstack-meeting-alt18:15
*** bhavikdbavishi has quit IRC18:16
*** bhavikdbavishi1 is now known as bhavikdbavishi18:16
*** bhavikdbavishi has quit IRC18:20
*** yamahata has quit IRC18:31
*** lpetrut has joined #openstack-meeting-alt18:33
*** e0ne has joined #openstack-meeting-alt18:35
*** cezary_zukowski_ has quit IRC18:36
*** lpetrut has quit IRC18:37
*** macza has quit IRC18:44
*** macza has joined #openstack-meeting-alt18:45
*** vishakha has quit IRC18:53
*** e0ne has quit IRC19:02
*** carlos_silva has quit IRC19:02
*** e0ne has joined #openstack-meeting-alt19:05
*** yamamoto has joined #openstack-meeting-alt19:16
*** panda has quit IRC19:19
*** yamamoto has quit IRC19:21
*** panda has joined #openstack-meeting-alt19:21
*** efried has joined #openstack-meeting-alt20:06
*** e0ne has quit IRC20:08
*** thgcorrea has quit IRC20:13
*** radeks_ has joined #openstack-meeting-alt20:22
*** radeks has quit IRC20:25
*** munimeha1 has quit IRC20:34
*** slaweq has quit IRC20:37
*** efried has quit IRC20:40
*** hongbin has joined #openstack-meeting-alt20:42
*** markvoelker has joined #openstack-meeting-alt20:45
*** slaweq has joined #openstack-meeting-alt20:53
*** yamamoto has joined #openstack-meeting-alt21:04
*** yamamoto has quit IRC21:09
*** radeks_ has quit IRC21:13
*** vishalmanchanda has quit IRC21:31
*** jdennis has quit IRC22:00
*** ccamacho has quit IRC22:08
*** ccamacho has joined #openstack-meeting-alt22:27
*** ccamacho has quit IRC22:28
*** hongbin has quit IRC22:40
*** rcernin has joined #openstack-meeting-alt22:52
*** hongbin has joined #openstack-meeting-alt22:52
*** yamamoto has joined #openstack-meeting-alt22:52
*** hongbin has quit IRC22:52
*** diablo_rojo has quit IRC22:53
*** hongbin has joined #openstack-meeting-alt22:54
*** yamamoto has quit IRC22:56
*** markvoelker has quit IRC22:57
*** markvoelker has joined #openstack-meeting-alt22:57
*** macza has quit IRC22:59
*** macza has joined #openstack-meeting-alt22:59
*** markvoelker has quit IRC23:02
*** jcoufal has quit IRC23:03
*** whoami-rajat has quit IRC23:04
*** erlon has quit IRC23:06
*** diablo_rojo has joined #openstack-meeting-alt23:12
*** yamamoto has joined #openstack-meeting-alt23:30
*** hongbin has quit IRC23:52

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!