Wednesday, 2018-10-03

*** jesusaur has quit IRC00:01
*** diablo_rojo has quit IRC00:02
*** yamamoto has joined #openstack-meeting-alt00:08
*** tetsuro has joined #openstack-meeting-alt00:15
*** markvoelker has quit IRC00:17
*** markvoelker has joined #openstack-meeting-alt00:17
*** jesusaur has joined #openstack-meeting-alt00:20
*** markvoelker has quit IRC00:21
*** gyee has quit IRC00:29
*** erlon has quit IRC00:35
*** macza has joined #openstack-meeting-alt00:59
*** macza has quit IRC01:03
*** iyamahat has quit IRC01:15
*** ianychoi has quit IRC01:17
*** ianychoi has joined #openstack-meeting-alt01:28
*** tetsuro has quit IRC01:29
*** cloudrancher has joined #openstack-meeting-alt01:40
*** ianychoi has quit IRC01:42
*** vishakha has joined #openstack-meeting-alt01:43
*** tetsuro has joined #openstack-meeting-alt01:49
*** dave-mccowan has joined #openstack-meeting-alt01:55
*** jbadiapa has quit IRC01:56
*** iyamahat has joined #openstack-meeting-alt01:57
*** jbadiapa has joined #openstack-meeting-alt01:58
*** markvoelker has joined #openstack-meeting-alt02:18
*** ianychoi has joined #openstack-meeting-alt02:19
*** markvoelker has quit IRC02:51
*** dave-mccowan has quit IRC03:08
*** hongbin has joined #openstack-meeting-alt03:41
*** markvoelker has joined #openstack-meeting-alt03:48
*** hongbin has quit IRC03:59
*** markvoelker has quit IRC04:21
*** macza has joined #openstack-meeting-alt04:26
*** macza has quit IRC04:30
*** rossella_s has quit IRC04:34
*** rossella_s has joined #openstack-meeting-alt04:34
*** rossella_s has quit IRC04:40
*** rossella_s has joined #openstack-meeting-alt04:45
*** markvoelker has joined #openstack-meeting-alt05:18
*** rossella_s has quit IRC05:30
*** rossella_s has joined #openstack-meeting-alt05:30
*** rossella_s has quit IRC05:35
*** rossella_s has joined #openstack-meeting-alt05:38
*** markvoelker has quit IRC05:52
*** dims has quit IRC06:24
*** e0ne has joined #openstack-meeting-alt06:24
*** dims has joined #openstack-meeting-alt06:26
*** dims has quit IRC06:34
*** dims has joined #openstack-meeting-alt06:35
*** dpawlik has joined #openstack-meeting-alt06:39
*** yamamoto has quit IRC06:51
*** yamamoto has joined #openstack-meeting-alt06:51
*** rdopiera has joined #openstack-meeting-alt06:56
*** jroll has quit IRC07:19
*** amotoki has quit IRC07:23
*** jroll has joined #openstack-meeting-alt07:32
*** tssurya has joined #openstack-meeting-alt07:38
*** alexchadin has joined #openstack-meeting-alt07:41
*** tetsuro has quit IRC07:54
*** rcernin has quit IRC07:55
*** jroll has quit IRC08:13
*** markvoelker has joined #openstack-meeting-alt08:18
*** jtomasek_ has joined #openstack-meeting-alt08:21
*** alexchadin has quit IRC08:21
*** jtomasek has quit IRC08:23
*** jroll has joined #openstack-meeting-alt08:27
*** amotoki_ has joined #openstack-meeting-alt08:27
*** derekh has joined #openstack-meeting-alt08:33
*** jtomasek has joined #openstack-meeting-alt08:34
*** jtomasek_ has quit IRC08:36
*** ttsiouts has joined #openstack-meeting-alt08:51
*** jroll has quit IRC08:51
*** markvoelker has quit IRC08:51
*** ttsiouts has quit IRC08:53
*** jesusaur has quit IRC08:53
*** ttsiouts has joined #openstack-meeting-alt08:53
*** derekh has quit IRC08:58
*** ttsiouts has quit IRC08:58
*** jtomasek has quit IRC08:59
*** ttsiouts has joined #openstack-meeting-alt09:00
*** jroll has joined #openstack-meeting-alt09:05
*** ttsiouts has quit IRC09:07
*** ttsiouts has joined #openstack-meeting-alt09:07
*** ttsiouts_ has joined #openstack-meeting-alt09:10
*** ttsiouts has quit IRC09:12
*** alexchadin has joined #openstack-meeting-alt09:13
*** priteau has joined #openstack-meeting-alt09:13
*** jtomasek has joined #openstack-meeting-alt09:15
*** alexchadin has quit IRC09:46
*** yamamoto has quit IRC10:05
*** yamamoto has joined #openstack-meeting-alt10:06
*** ttsiouts_ has quit IRC10:07
*** yamamoto has quit IRC10:10
*** yamamoto has joined #openstack-meeting-alt10:14
*** dtrainor has quit IRC10:14
*** derekh has joined #openstack-meeting-alt10:22
*** jtomasek has quit IRC10:28
*** markvoelker has joined #openstack-meeting-alt10:49
*** ttsiouts has joined #openstack-meeting-alt11:02
*** erlon has joined #openstack-meeting-alt11:03
*** amotoki_ is now known as amotoki11:07
*** jtomasek has joined #openstack-meeting-alt11:18
*** yamamoto has quit IRC11:19
*** markvoelker has quit IRC11:22
*** yamamoto has joined #openstack-meeting-alt11:24
*** dtrainor has joined #openstack-meeting-alt11:33
*** macza has joined #openstack-meeting-alt11:37
*** yamamoto has quit IRC11:38
*** yamamoto has joined #openstack-meeting-alt11:39
*** macza has quit IRC11:42
*** yamamoto has quit IRC11:44
*** raildo has joined #openstack-meeting-alt11:48
*** jtomasek has quit IRC11:57
*** e0ne has quit IRC12:04
*** jcoufal has joined #openstack-meeting-alt12:05
*** ttsiouts has quit IRC12:05
*** ttsiouts has joined #openstack-meeting-alt12:07
*** ttsiouts has quit IRC12:11
*** e0ne has joined #openstack-meeting-alt12:16
*** dave-mccowan has joined #openstack-meeting-alt12:19
*** yamamoto has joined #openstack-meeting-alt12:20
*** yamamoto has quit IRC12:22
*** yamamoto has joined #openstack-meeting-alt12:22
*** pgodek has joined #openstack-meeting-alt12:28
*** ttsiouts has joined #openstack-meeting-alt12:31
*** ttsiouts has quit IRC12:33
*** ttsiouts has joined #openstack-meeting-alt12:34
*** jtomasek has joined #openstack-meeting-alt12:39
*** cezary_zukowski has joined #openstack-meeting-alt12:52
*** liuyulong has joined #openstack-meeting-alt13:20
*** dustins has joined #openstack-meeting-alt13:32
*** pgodek has quit IRC13:34
*** pgodek has joined #openstack-meeting-alt13:36
*** pgodek has quit IRC13:42
*** yamamoto has quit IRC13:45
*** yamamoto has joined #openstack-meeting-alt13:45
*** yamamoto has quit IRC13:50
*** pgodek has joined #openstack-meeting-alt13:52
*** hongbin has joined #openstack-meeting-alt13:57
*** bzurkowski has joined #openstack-meeting-alt13:58
dkrolHello14:00
dkrol#startmeeting trove14:00
openstackMeeting started Wed Oct  3 14:00:05 2018 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
pgodekhi!14:00
dkrollets wait a few more minutes14:00
dkrol#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: trove)"14:00
bzurkowskipgodek: Hello14:00
bzurkowskiHello everyone14:00
cezary_zukowskihello14:00
dkrolHello everyone14:01
dkrolI see we have more people then last time14:01
bzurkowskiMarcin has problems with connection14:02
bzurkowskiLet's give him a minute14:02
dkrolsure thing14:02
*** SergeyLukjanov has quit IRC14:04
*** bzurkowski has left #openstack-meeting-alt14:05
*** munimeha1 has joined #openstack-meeting-alt14:05
*** bzurkowski_ has joined #openstack-meeting-alt14:05
*** mpiwowarczy has joined #openstack-meeting-alt14:06
mpiwowarczyhello everyone14:06
dkrolhello14:06
*** SergeyLukjanov has joined #openstack-meeting-alt14:06
bzurkowski_mpiwowarczy: Hello14:06
mpiwowarczysorry for late, I had a connection issues - looks like ip quotas14:06
pgodekhi14:06
dkrolso maybe let's start14:06
*** bzurkowski_ has quit IRC14:07
dkrol#topic Core team members14:07
*** openstack changes topic to "Core team members (Meeting topic: trove)"14:07
*** bzurkowski has joined #openstack-meeting-alt14:07
dkrolbzurkowski: you proposed the topic14:07
*** yamamoto has joined #openstack-meeting-alt14:08
bzurkowskiRight14:08
bzurkowskiDuring last meeting we considered adding Marcin to the core team14:08
bzurkowskiToday we have more people participating in the meeting14:09
dkrolok14:10
dkrolso basically you would like to propose mpiwowarczy to be joined to the core contributor's list14:10
bzurkowskiYes, definitely14:10
dkrolI've sent an email to all missing core contributors about our meetings14:10
dkrolunfortunately, I see there was very little response rate14:11
dkrollast time I suggest we should contact them first as a reminder14:11
cezary_zukowskibtw., what are the duties of core team members? (in nutshell/briefly) More impact on code review?14:11
mpiwowarczydkrol: was there anyone objected?14:11
dkrolmpiwowarczy: no, though I didn't stated your case explicitly14:12
bzurkowskicezary_zukowski: Core member has permissions to add +2 for changes and setting +1 for workflow14:12
mpiwowarczydkrol: oh, ok14:13
cezary_zukowskibzurkowski: okay, more power :)14:13
bzurkowskiThat means that they have more impact on the decision whether given change should be submitted to the mainline14:13
dkrolIMHO we can put mpiwowarczy candidacy for voting14:13
cezary_zukowskisurely we can14:13
dkrol#startvote (Do you accept mpiwowarczy candidacy for trove core contributor ? ) ? YES, NO14:14
openstackBegin voting on: (Do you accept mpiwowarczy candidacy for trove core contributor ? ) ? Valid vote options are YES, NO.14:14
openstackVote using '#vote OPTION'. Only your last vote counts.14:14
dkrol#vote YES14:14
bzurkowski#vote YES14:14
pgodek#vote YES14:14
cezary_zukowski#vote YES14:14
dkrol#endvote14:15
openstackVoted on "(Do you accept mpiwowarczy candidacy for trove core contributor ? ) ?" Results are14:15
openstackYES (4): cezary_zukowski, bzurkowski, pgodek, dkrol14:15
dkrolI didn't say it before but only core contributors should vote :)14:15
cezary_zukowskidkrol: okay, so I am out :)14:15
mpiwowarczylooks it doesn't matter :)14:16
bzurkowskiThe remaining voices have symbolic meaning ;)14:16
dkrolanyway I think the output is obvious that mpiwowarczy should be added as core contributor to Trove due to his work on the project in recent months.14:16
mpiwowarczygreat14:17
dkrolas bzurkowski said the last time, having more core contributors should facilitate trove development14:17
mpiwowarczythanks guys14:17
dkrolmpiwowarczy: congratulations14:17
mpiwowarczyI am very pleased :)14:17
mpiwowarczythanks14:17
cezary_zukowskicongrats14:17
bzurkowskiCongrats Marcin14:17
dkrolwe can move to the next topic on our agenda14:18
mpiwowarczyI will do mybest as new core member14:18
dkrol#topic Recent changes and reviews14:18
*** openstack changes topic to "Recent changes and reviews (Meeting topic: trove)"14:18
dkrolthere were a few new changes and bugfixes merged14:19
dkrolby external contributors which is great14:19
dkrolhttps://review.openstack.org/60632014:20
dkrolhttps://review.openstack.org/57165214:20
dkrolhttps://review.openstack.org/59841214:20
*** ayoung has quit IRC14:20
dkrolhttps://review.openstack.org/60485414:20
dkrolhttps://review.openstack.org/60188614:20
dkrolI hope these people will maintain active - maybe we could invite them to our meetings14:21
dkrolthese are mainly small changes and fixes14:22
dkrolnothing major but still it is great to see it14:22
dkroldo you have anything to share on this ?14:22
bzurkowskidkrol: It is a good idea to encourage those people to co-operate14:23
bzurkowskiEspecially the ones that contributed changes that were database-related14:24
bzurkowskihttps://review.openstack.org/#/c/601886/ being an example14:24
mpiwowarczyjian.song looks more involved to trove project https://review.openstack.org/#/q/owner:jian.song+status:open14:25
dkrolthis can be one of our action points regarding trove revitalization14:26
bzurkowskimpiwowarczy: His changes look very interesting14:27
bzurkowskiIt would be great to bring him back14:27
dkrolI agree14:27
*** dpawlik has quit IRC14:27
dkrol#action send an email to possible trove contributors14:28
dkrolanything else on this topic or can we move to the next14:28
bzurkowskiLet's move on14:29
*** ttsiouts has quit IRC14:30
dkrol#topic Trovestack redesign14:31
*** openstack changes topic to "Trovestack redesign (Meeting topic: trove)"14:31
dkrolhttps://review.openstack.org/60696014:32
dkrolI made this change as a first step14:33
dkrolit is about adding image setup to trove devstack plugin14:33
mpiwowarczyI saw this change, a lot of good work14:33
mpiwowarczythere is one more thing about this14:34
mpiwowarczydo we want build these images in devstack for now?14:34
dkrolI don't follow14:35
mpiwowarczyif not, we could disable it temporarily14:35
dkrolwhat do you mean ?14:35
pgodekisn't needed for CI?14:35
mpiwowarczyfor now we have images built in trovestack14:36
bzurkowskimpiwowarczy: If not now, how to test it in the CI?14:37
dkrolhmm... we don't need them for now in CI14:37
cezary_zukowskimpiwoarczy: so it follows a trend of running away from trovestack (as with tests, i.e. rewriting to Tempest)?14:38
bzurkowskiIn my opinion we cannot just leave a bulk snippet of bash code turned off, outside of the testing scope14:38
mpiwowarczyare these images used anywhere now?14:38
mpiwowarczybzurkowski: great idea14:39
dkrolmpiwowarczy: no, besides development environment setup14:39
bzurkowskimpiwowarczy: It's rather about users evaluating new devstack feature in their environment14:39
*** yamamoto has quit IRC14:40
cezary_zukowskibzurkowski: could you list some examples of such features?14:40
*** ttsiouts has joined #openstack-meeting-alt14:40
mpiwowarczyok, got it14:41
*** yamamoto has joined #openstack-meeting-alt14:41
bzurkowskiI mean, we are providing new version on Trove devstack plugin to the users14:42
dkroldo you think we should switch to this image in trovestack tests ?14:42
*** yamamoto has quit IRC14:42
bzurkowskiAnd user will be able to run devstack with image building turned on14:43
*** yamamoto has joined #openstack-meeting-alt14:43
bzurkowskiTherefore I suggest having a testing job in the CI pipeline that evaluates this use case14:43
cezary_zukowskibzurkowski: so, it's about preparing customized images rather than downloading them from some repo (artifactory)?14:43
dkrolso such a test should be run only if this image was created14:44
mpiwowarczylets build image for now, it will tests building image code14:45
dkrolnormally when we have integration tests, we build an image first within a test job14:45
mpiwowarczylater we can consider to use images from devstack plugin14:45
bzurkowskidkrol: Yes, that is a one way to test it14:46
bzurkowskimpiwowarczy: So you suggest building an image twice per job?14:46
mpiwowarczylooks we are forced to do that14:47
dkrolhmmm14:47
bzurkowskiOnce during devstack installation, second time on trovestack kickstart14:47
dkrolwe have a flag to disable it14:47
dkrolso in most integration testing we can turn this flag on14:47
*** yamamoto has quit IRC14:48
bzurkowskidkrol: Good point14:48
dkroland then we will not have double image build14:48
*** slaweq has quit IRC14:48
dkroland we can add another integration test which will build this image and then have a tempest test to test it14:48
cezary_zukowskitesting is on topic, btw., is it a long process of building an image?14:49
mpiwowarczyI consider to create separate job in gate section14:50
dkrolwe can also reverse the flag to build an image only if a flag is turned on14:50
bzurkowskicezary_zukowski: Depending on the datastore, around 30 minutes14:50
pgodek@cezary ~20 min14:50
mpiwowarczythanks for that we will test this piece of code on each merge14:50
cezary_zukowskinot bad :)14:50
bzurkowskimpiwowarczy: I like this approach14:50
mpiwowarczythen, build time will be not a issue14:50
bzurkowskiWe could keep it experimental until rewriting trovestack and functional jobs14:51
dkrolthere is a question what kind of test we should have14:51
dkrollet's have an offline discussion about it since we are running out of time14:51
dkrol#topic Python 3 first support14:52
*** openstack changes topic to "Python 3 first support (Meeting topic: trove)"14:52
dkrollast week I had a discussion about supporting stable branches by python314:52
dkrolit seems there was a misunderstanding14:52
dkroland there is a task in python3-first goal to migrate zuul configuration to each project instead of having them centralized14:53
dkrolor something like this14:53
dkrolthis is not related to python3 to my best knowledge14:53
dkroland this change should be merged to stable branches14:53
dkrolas it will break tests otherwise14:54
dkroldo we have anything about this topic ?14:54
bzurkowskidkrol: We need to have appropriate permissions to submit remaining changes14:54
dkrolto stable branches ?14:55
bzurkowskiCurrently, we can only mark them with +114:55
bzurkowskidkrol: Yes14:55
dkrolyou are correct14:55
dkrolunfortunately for now my request for adding us to stable branch maintainers was declined14:55
*** slaweq has joined #openstack-meeting-alt14:56
mpiwowarczyas for master branch, the current status is that we have two open changes https://review.openstack.org/604854 and https://review.openstack.org/#/c/604816/14:56
mpiwowarczyfirst is almost done14:56
mpiwowarczywill be fine if anyone will review this change14:56
dkrolwe should contact people from the list for help14:56
dkrolmpiwowarczy: great14:57
dkrolkeep up the good work14:57
dkrolwe have only 2 more mites so probably we should finish now14:57
dkrolthanks all for being here14:57
dkrolwe had a great week14:58
bzurkowskiThanks, it was great to see now people in the conversation14:58
dkrolsee you next time14:58
bzurkowskiBye14:58
mpiwowarczythanks, bye14:58
cezary_zukowskibye14:58
dkrol#endmeeting14:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:58
openstackMeeting ended Wed Oct  3 14:58:44 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-10-03-14.00.html14:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-10-03-14.00.txt14:58
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-10-03-14.00.log.html14:58
*** mpiwowarczy has quit IRC14:58
*** bzurkowski has quit IRC14:59
*** pgodek has quit IRC15:00
e0ne#startmeeting horizon15:00
openstackMeeting started Wed Oct  3 15:00:53 2018 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: horizon)"15:00
openstackThe meeting name has been set to 'horizon'15:00
rdopierao/15:01
e0nehi15:01
amotoki...hi....15:02
e0nehi15:02
e0nelooks like we can start now :)15:02
e0ne# link https://wiki.openstack.org/wiki/Meetings/Horizon15:02
e0ne#topic Notices15:03
*** openstack changes topic to "Notices (Meeting topic: horizon)"15:03
e0neI've updated our agenda as discussed at PTG15:03
e0nethere is a list of our priorities for this cycle15:03
e0nefeel free to add any topic you would like to discuss15:04
e0ne#link https://releases.openstack.org/stein/schedule.html15:04
e0newe're about 3 weeks before stein-1 milstone15:04
amotokiit seems to cover the PTG topics well15:05
amotokione question15:05
e0nenothing special for Horizon team just a friendly reminder15:05
e0neamotoki: sure15:05
amotokido we need to track action items from PTG?15:05
dklyleo/15:05
e0neamotoki: I want to do it15:05
amotokiI think it can be covered in "Action items from the previous meeting"15:06
e0neamotoki: TBH, I tried to get this list today in the etherpad, but etharpad was unavailable almost all day :(15:06
amotokiah...15:06
e0neI'm doing to do it tomorrow15:06
e0nefinally finished with downstream work for our internal release, so I'll have more time for upstream at least next few months15:07
amotokiI didn't review and do other things after PTG due to my internal stuffs and the vacation, so there seems what I haven't synced.15:07
e0neamotoki: I'll do it and send a mail to the openstack-dev@ ML15:08
amotokisounds fine15:08
e0nethanks15:08
e0ne#help15:08
e0ne#action e0ne to create 'Action Items from PTG' list15:09
e0ne#topic Community Goals15:10
*** openstack changes topic to "Community Goals (Meeting topic: horizon)"15:10
*** jtomasek has quit IRC15:10
e0neI almost finished with openstack_auth tests. the patch will be proposed this week.15:10
*** jtomasek has joined #openstack-meeting-alt15:10
e0neit's the last thing we should do with mox removal15:10
e0ne#topic Python3 first15:11
*** openstack changes topic to "Python3 first (Meeting topic: horizon)"15:11
e0neI didn't check the list, but it seems that we're in a good shape with this goal15:11
e0ne#link https://storyboard.openstack.org/#!/story/200322715:12
e0ne#action e0ne to check what is the state with 'Python3 first' community goal15:13
amotokidoes everyone run devstack with python3 horizon?15:13
amotokiI runs horizon with apache mod-wsgi python3 and runserver with python3.15:13
amotokiI hope all developers try so.15:13
e0necool. do you have any issues?15:13
amotokiat least nothing serios hits me.15:14
e0neawesome!15:14
amotokiI see many debug message which complains template rendering though15:14
amotokithey are from django2.15:14
rdopierasame here15:15
amotokiwe need to clean them up in this cycle.15:15
e0neamotoki: it would be great if you could file a bug for this15:15
e0neamotoki: +115:15
amotokiack on filing a bug15:15
e0neamotoki: thanks15:15
-amotoki- earthquake alert hit me, but no real earthquake hits me so far15:17
e0ne:(15:17
amotokilet's move on15:17
e0ne#topic Community Goals: pre-upgrade check15:17
*** openstack changes topic to "Community Goals: pre-upgrade check (Meeting topic: horizon)"15:17
e0neas discussed at PTG, we agreed to implement a command to check if we have any  deprecated options in the config15:18
e0neit would be great to have volunteer for this goal15:18
*** dpawlik has joined #openstack-meeting-alt15:19
amotokido distros already have such kind of things internally?15:19
rdopieraI don't know the details, but since I was working with the config a lot, I could tentatively look into it?15:20
e0newe don't have anything like this in our distro15:20
rdopieraamotoki: I think it's too app-specific15:20
e0nerdopiera: sounds good15:20
amotokiI mean OpenStack distributors by "distros"15:20
rdopierawe just regenerate the config files from templates each time15:21
amotokithe basic concept is defined in the TC page https://governance.openstack.org/tc/goals/stein/upgrade-checkers.html15:21
rdopierausing configuration management tools15:21
rdopierapeople are not supposed to edit config files directly15:22
e0nerdopiera: good point15:22
amotokiunderstandable15:22
e0neanyway, it's a good idea to have such checks15:23
amotokias my operator hat, we directly consume Ubuntu packages and have our own horizon settings.15:23
*** dpawlik has quit IRC15:24
amotokiIn my understanding, what we need to check is just to alert them if local_settings contains deprecated settings.15:24
amotokiwe need to list deprecated settings15:24
e0ne+115:25
rdopieraI would also alert about unknown settings15:25
rdopieraonce we are at it15:25
amotoki+115:25
rdopierayou know, spelling mistakes and the like15:26
amotokibut we need to take into account django options.15:26
rdopierayes15:26
amotokiso it is not an easy thing.15:26
rdopieraI will see if I can outomate it somehow15:26
amotokiyeah, it is the right approach :)15:26
rdopierado we also need to list deprecated django settings?15:27
e0neyes15:27
amotokipersonally no15:27
e0ne:)15:27
amotokibecause django version choice is up to deployers15:27
rdopieraI wonder if I can reuse the mechanism that django uses for the warnings15:27
*** yamamoto has joined #openstack-meeting-alt15:28
e0neit's less important than horizon settings but it would be good to have such optio15:28
amotokiit sounds a thing we should explore as the second or optional step15:28
e0ne+115:29
amotokiI am not sure whether we should focus on N to N+1 upgrade or we should cover more than +2 releases.15:29
amotokiwe can start from N to N+1 of course.15:30
e0neN+1 model is what we should start15:30
amotokitotally agree15:31
*** ttsiouts has quit IRC15:31
e0newe can improve our solution in the future if needed15:31
e0nelooks like we've agreed on this topic15:33
e0nelet's move forward15:33
e0ne#Bug status15:33
e0nenot a big progress on bug triage for the last two weeks15:34
e0newe decreased a total number of 'New' bugs from 138 to 12015:34
amotokiit looks like we receieved a number of new bugs :(15:35
e0neyes:(15:35
amotokie0ne seems to triage most of them :)15:35
e0neI do my best to do it15:35
e0neI do expect to have about ~80 bugs with New status until next meeting15:36
amotokiI just checked the number of my new bug mails :p15:36
e0ne:)15:36
e0neAlso I added low-hang-fuits to few of them15:36
amotokifeel free to tag 'neutron' if related to networking. I will check them.15:37
e0neok, will do15:37
e0newe've got 38 low-hanging-fruit bugs15:37
e0ne120 New bugs15:37
e0ne463 Open bugs15:37
e0ne#link https://bugs.launchpad.net/horizon15:37
e0nelet's see what number will we have next week15:38
amotokiwhat does 'low-hanging-fruit' mean? are they really low-hanging-frust or are they starter bugs?15:38
amotokis/frust/fruit/15:38
e0neamotoki: what do you mean by "starter bugs"?15:38
e0neI added this tag to bugs which should be easy to fix even for new contributors15:39
amotokisometimes 'low-hanging-fruit' tag is used as bugs for new contributors15:39
amotokibut the actual meaning of low-hanging-fruit is different.15:39
*** macza has joined #openstack-meeting-alt15:39
amotokilow-hanging-fruit actually means that we can get a bit even if we fix them15:39
e0ne#link https://wiki.openstack.org/wiki/Bug_Tags15:40
e0ne"low-hanging-fruit: Bugs that are easy to fix, ideal for beginners to get familiar with the workflow and to have their first contact with the code in OpenStack development.15:40
e0ne"15:40
amotokiokay. we OpenStack have our own definition of low-hanging-fruit. got it15:40
e0ne:)15:41
amotokisometimes we added 'low-hanging-fruit' for bugs for which we can get a bit even if we fix.....15:42
rdopierait's just the style of my underwear15:42
amotokiheh15:42
e0ne#ation e0ne to update tags list at https://wiki.openstack.org/wiki/Bug_Tags#Horizon15:42
e0ne#action e0ne to update tags list at https://wiki.openstack.org/wiki/Bug_Tags#Horizon15:42
e0ne#topic Horizon feature gap15:43
*** openstack changes topic to "Horizon feature gap (Meeting topic: horizon)"15:43
amotokiperhaps I am the original author of that page..... but I forgot it15:43
e0neit's a bit related to the previous topic15:43
e0neI'll file a bug and blueprint according to https://etherpad.openstack.org/p/horizon-feature-gap15:44
e0ne#link https://etherpad.openstack.org/p/horizon-feature-gap15:44
e0nethe some of features are easy to implement15:44
e0newe need to create low-hanging-fruit bugs for them15:45
amotokifirst of all, thanks e0ne for discussing this topic with various project teams in PTG15:45
e0neof course, it's not easy to implement all features15:45
e0neamotoki: np. now we're got some plan to work on with priorities from project teams15:45
e0neit was a good time at PTG discussion horizon stuff15:46
e0nealso, I'll fill reviews priority list if we've got some feature gap fix proposal15:47
e0nethat is my plan15:47
e0ne#topic15:48
*** openstack changes topic to " (Meeting topic: horizon)"15:48
e0ne#topic I don't have any updates about 'CI for plugins' topic15:48
*** openstack changes topic to "I don't have any updates about 'CI for plugins' topic (Meeting topic: horizon)"15:48
e0ne#topic CI for plugins15:48
*** openstack changes topic to "CI for plugins (Meeting topic: horizon)"15:48
* e0ne hates copy&paste issues15:48
e0neI don't have a lot of updates about 'CI for plugins' topic15:48
amotokie0ne: '#undo' helps you :)15:48
e0neamotoki: thanks!15:48
e0neI'm working on manila and heat plugins to get basic tests up and working now15:49
amotokiwhat was the problem on horizon plugi CI failures?15:49
e0neI hope to get it landed before stein-115:49
e0neamotoki: xstatic-jquery 3 release15:49
amotokii see15:50
e0newe didn't have good solution now but workaround from Shu  helps to unblock gates15:50
amotokiI think horizon plugins should have the consistent approach for running tests15:50
e0newe need to think on publishing horizon to npm as npm package15:50
amotokiplugisn he maintains have some specific tricks which he thinks are good...15:51
e0neamotoki: +115:51
amotokiI sometimes try to convince him but I failed....15:51
e0neplugins CI is something I would like to improve this cycle15:52
amotokiyeah15:53
e0neteams are interested on get this working15:53
e0ne6 minutes reminder15:54
e0neaccording to the new xstatic-jquery release15:55
e0newe need to cap it's version in stable/* branches too:(15:55
e0neI didn't have a time to do it yet15:55
rdopierawe should probably cap all xstatic versions15:55
e0nerdopiera: +115:55
rdopieraat least to the major version15:56
e0nerdopiera: and try to get horizon working with new versions15:56
amotokifor our CI on stable branches, we should use upper-constraints15:56
e0neamotoki: we use it15:56
amotokiit is not easy to cap all cases15:56
amotokiso what broke our CI?15:57
e0nehttps://github.com/openstack/requirements/blob/stable/rocky/upper-constraints.txt#L7215:57
e0nelooks like stable branches are in safe now :)15:57
e0neI didn't check it befoew15:57
amotokiperhaps it is because some installations do not honor u-c.15:57
e0ne:(15:58
e0newe're almost out of time15:58
e0newe can continue in #openstack-horizon if needed15:58
e0nethanks for the great discussions! see you next week!15:59
amotokithanks15:59
e0ne#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:59
openstackMeeting ended Wed Oct  3 15:59:56 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2018/horizon.2018-10-03-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2018/horizon.2018-10-03-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2018/horizon.2018-10-03-15.00.log.html16:00
*** gyee has joined #openstack-meeting-alt16:06
*** tpsilva has joined #openstack-meeting-alt16:08
*** slaweq has quit IRC16:09
*** slaweq has joined #openstack-meeting-alt16:10
*** rdopiera has quit IRC16:12
*** ttsiouts has joined #openstack-meeting-alt16:12
*** ttsiouts has quit IRC16:15
*** ttsiouts has joined #openstack-meeting-alt16:16
*** ttsiouts has quit IRC16:20
*** macza has quit IRC16:22
*** macza has joined #openstack-meeting-alt16:22
*** panda is now known as panda|off16:24
*** macza has quit IRC16:24
*** dims has quit IRC16:28
*** dims_ has joined #openstack-meeting-alt16:35
*** e0ne has quit IRC16:47
*** macza has joined #openstack-meeting-alt16:57
*** iyamahat has quit IRC16:59
*** derekh has quit IRC17:00
*** iyamahat has joined #openstack-meeting-alt17:20
*** yamahata has joined #openstack-meeting-alt17:23
*** iyamahat_ has joined #openstack-meeting-alt17:24
*** iyamahat has quit IRC17:27
*** bhavikdbavishi has joined #openstack-meeting-alt17:57
*** e0ne has joined #openstack-meeting-alt18:02
*** bhavikdbavishi1 has joined #openstack-meeting-alt18:14
*** bhavikdbavishi has quit IRC18:15
*** bhavikdbavishi1 is now known as bhavikdbavishi18:15
*** bhavikdbavishi has quit IRC18:37
*** diablo_rojo has joined #openstack-meeting-alt18:41
*** e0ne has quit IRC18:45
*** liuyulong has quit IRC18:47
*** e0ne has joined #openstack-meeting-alt18:48
*** gyee has quit IRC18:50
*** efried has quit IRC18:58
*** cezary_zukowski has quit IRC18:58
*** efried has joined #openstack-meeting-alt19:00
*** e0ne has quit IRC19:10
*** tssurya has quit IRC19:30
*** slaweq has quit IRC20:10
*** slaweq has joined #openstack-meeting-alt20:11
*** macza has quit IRC20:15
*** macza has joined #openstack-meeting-alt20:16
*** rossella_s has quit IRC20:19
*** gyee has joined #openstack-meeting-alt20:24
*** rossella_s has joined #openstack-meeting-alt20:35
*** ijw has joined #openstack-meeting-alt20:46
*** raildo has quit IRC20:53
*** priteau has quit IRC21:01
*** erlon has quit IRC21:06
*** hongbin has quit IRC21:19
*** slaweq has quit IRC21:30
*** rossella_s has quit IRC21:34
*** slagle has quit IRC21:44
*** jtomasek has quit IRC21:54
*** dustins has quit IRC21:55
*** munimeha1 has quit IRC21:56
*** dustins has joined #openstack-meeting-alt21:56
*** rcernin has joined #openstack-meeting-alt22:25
*** dustins has quit IRC22:36
*** macza has quit IRC22:54
*** macza_ has joined #openstack-meeting-alt22:54
*** jtomasek has joined #openstack-meeting-alt23:02
*** pbourke has quit IRC23:03
*** pbourke has joined #openstack-meeting-alt23:03
*** jtomasek has quit IRC23:07
*** macza_ has quit IRC23:12
*** dtrainor has quit IRC23:43
*** slagle has joined #openstack-meeting-alt23:51

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