Wednesday, 2017-01-04

*** matrohon has joined #openstack-meeting-507:59
*** matrohon has quit IRC11:09
*** matrohon has joined #openstack-meeting-512:59
*** tongli has joined #openstack-meeting-513:28
*** zhipengh has joined #openstack-meeting-513:52
*** zhipengh has quit IRC14:00
topol#startmeeting interop_challenge14:00
openstackMeeting started Wed Jan  4 14:00:31 2017 UTC and is due to finish in 60 minutes.  The chair is topol. 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: interop_challenge)"14:00
openstackThe meeting name has been set to 'interop_challenge'14:00
tonglio/14:00
skazio/14:00
topolHi everyone, who is here for the interop challenge meeting today?14:00
topolThe agenda for today can be found at:14:00
topol#link https://etherpad.openstack.org/p/interop-challenge-meeting-2017-01-0414:00
markvoelkero/14:00
topolWe can use this same etherpad to take notes14:00
*** garloff has joined #openstack-meeting-514:00
garloffHappy new year everyone!14:01
topolfirst topic:14:01
topol#topic Welcome everyone to our 2017 Kickoff14:01
*** openstack changes topic to "Welcome everyone to our 2017 Kickoff (Meeting topic: interop_challenge)"14:01
topolWELCOME and Happy New Year!!!14:01
topolnext topic14:02
tonglithanks Brad14:02
topol#topic Refresh everyone on the decisions we made in December14:02
*** openstack changes topic to "Refresh everyone on the decisions we made in December (Meeting topic: interop_challenge)"14:02
topolAGREED: Kubernetes and NFV will be our top priority workloads for this round of the interop challenge14:02
topol#link http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-12-14-14.00.html14:02
topolSo that's gets us all refreshed14:03
topol    #topic Review last meeting action items14:03
topol     #link http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-12-14-14.00.html14:03
topoleeiden to push up the NFV workload to new repo as soon as possible14:04
topolIs eeiden here? Has this been done?14:04
*** zhipengh has joined #openstack-meeting-514:04
topolI don't recall seeing any patches on this14:04
tongli@topol, I did not see any patches.14:04
topolK.  We'll keep that action goin then14:05
topol#action eeiden to push up the NFV workload to new repo as soon as possible14:05
topolnext action.14:05
topoltongli to start on kubernetes14:06
topoltongli, how is that going?14:06
tongli@topol, yes, already started working on that.14:06
topolWilling to share some details? Enquiring minds want to know14:06
*** hogepodge has joined #openstack-meeting-514:07
topolWhen might you have a patch for folks to review?14:07
tongliprobably in two weeks.14:07
topoltongli, excellent!14:08
topolKeep going!14:08
tonglithen we can add more things if it is too basic.14:08
topolVery cool14:08
topolnext action14:09
topoltongli to create lauchpad for our repo14:09
topolLooks lije hogepodge did this correct?14:09
hogepodgemaybe docado?14:09
tongli@topol, that is for bug tracking, right?14:09
topoltongli yes14:10
tongliif it is, then it is there already, and I have created a bug.14:10
topolhere is the link #link https://bugs.launchpad.net/interop-workloads14:10
tongliright.14:10
topolwasnt you hogepodge?14:10
topolit was docado?14:10
tongliit is all working, Chris created that for us. Thanks Chris.14:10
topolTHANKS docado!!!14:10
hogepodgetopol: yes, docadeo did it14:10
topoldocado gets a Gold Star!14:11
tongli@topol, yes,14:11
topollooks like we even have a bug posted14:11
topoltongli looks like you triaged it14:12
topoltongli were you going to try and fix it14:12
tongliyes, I have been trying that for awhile.14:12
tongliwithno success.14:13
topol#link https://bugs.launchpad.net/interop-workloads/+bug/164994914:13
openstackLaunchpad bug 1649949 in Interop Challenge Workloads "wordprocess failed to run wp core install" [Undecided,New]14:13
tonglisomething went in actually break the lampstack workloads.14:13
tongliI can not successfully run it any more.14:13
topolso we get a new version of wordpress and that one no longer installs?14:14
tongliI went all the way back (probably 10 patches back), it worked for ubuntu env.14:14
tongliI think that the patches added to support fedora maybe the problem.14:14
tonglibut I can not be sure, spend quite few days on this already.14:14
topoltongli is there someone you think can help us to debug this?14:15
tongli@topol, anyone from the last summit can actually help.14:16
tonglithinking who added the fedora support probably can fix it.14:16
topolSo this was a patch on the old repo? can we do a git blame check and see who added it?14:17
garloffwould be good indeed if the "old" workload stays in a working state ...14:17
tonglisure.14:18
topolgarloff +++14:18
topolThats putting it mildly14:18
topol:-)14:18
tongliI think we need to fix the old workloads.14:18
tongliit bothers me a lot having the latest stuff not working.14:18
topoltongli yes we most certainly do.  Let's see if we can track down who added it14:19
topol#action tongli, topol to track down who added the fedora patch14:19
topol#action all please help trying to get wordpress back working14:19
topolNext item:14:20
topolall review and add stuff to the lessons learned doc14:20
tongliis there a way for us to find a ftp/http repository so that we can put something there such as the superuser theme, content.14:20
tonglijust so that these content can be used by workloads.14:21
topoltongli Im not sure I understand your question14:21
tonglirely on some external site is sometimes difficult, when the content changes, the workloads may break.14:21
tonglicurrently our workload download stuff such as wordpress code, theme, and content from external sites14:22
tonglifor example, we get the latest wordpress from wordpress site, however, when they release new ones, the new release of wordpress may no longer work in our workloads.14:23
tonglidue to changed deployment methods or changed format.14:23
topolso we could do that, but then we live in our own insulated bubble14:23
tongliusing the latest wordpress release, we can no longer import the example content because of the format change.14:24
tonglitrue, I do not know what is the best way.14:24
topollet's see how often wordpress continues to break us14:24
tongliI found that one of the problems contributing to the current workload breakage is the wordpress content format change.14:25
topolideally, they dont break us too often and we stay up to date14:25
hogepodgeIf this is meant to be a test environment, pinning to known working releases makes sense, since we're not testing wordpress, we're testing OpenStack14:25
tongli@hogepodge, exactly.14:25
hogepodgeOr, just accept that if external dependencies break you fail and test for them (which is more of the 'OpenStack way')14:25
tonglidifferent wordpress release requires different way of deploy it,14:25
tongliand the content could be different as well.14:26
tonglithe current sample wordpress content was downloaded from another site , which has to be modified slightly to import to new wordpress release.14:26
topolhogepodge, that is true.   But not working on them over the long haul results in us convincing oursleves that "this is fine"  but for real world folks we dont work14:26
tongliI was thinking if we can have  a ftp or http repository just to save some of these static content (do not want to put these in git hub)14:27
tonglithat probably can help. But I am open for other good ideas.14:27
hogepodgeIt all depends on the model of updates you want to have. Fix on fail means you're up to date, but have unexpected outages.14:27
hogepodgeFix on schedule means you can fall behind, especially if you don't honor the schedule.14:28
tongli@hogepodge, yes.14:28
topolmy fear is that if we can't show workloads running with the latest wordpress and others run into that we have done them a disservice14:28
*** garloff has quit IRC14:28
tongli@topol, even with that, we still need to have a repo for content like openstack superuser award site.14:29
topolSince were not in "important demo mode next week"  my gut says seeing failures and fixing them is most valuable14:29
tongliI suspect for kubernetes and nfv we will need something as well.14:29
skazifor wordpress itself, we can pin the version by downloading from: https://wordpress.org/download/release-archive/ instead of the latest tarball14:29
hogepodgefor context, I've spoken a bit with some of the kubernetes folks about testing on OpenStack. They do not want to test using OpenStack master, and will only accept a stable release14:29
topoltongli, why cant we use our own repo to store anyting you want static?14:30
tongli@skazi, yes, we can do that for the wordpress itself, but not for the content.14:30
*** garloff has joined #openstack-meeting-514:30
skazitongli: true :o|14:30
tongli@topol, I was thinking about that but do we want to store these tars , zips in the code stream?14:31
topoltongli if we put them in a separate folder I think its fine14:31
topoland then they get reviewed and controlled like everything else14:31
tongliis everyone ok with that?14:32
tongliI do not mind doing that.14:32
zhipenghsounds great14:32
tonglido we have an agreement?14:32
topolLet's try it14:32
tongliok. sounds good to me.14:32
tonglithis helps , folks, thanks.14:33
topolany concerns? actually folks can voice concerns when they see your patch14:33
tonglisure, sure14:33
skaziare there any size limitations on those repos?14:33
tongli@skazi, good question. I do not really know. let me do a search.14:34
topolK, let's see what happens.  I see the benefits both ways.  Pinning the wordpress version gives us stability.  Eventually somone might complain we arent working with latest wordpress14:35
tongli1 GB per repo.14:35
tongli100 MB per file.14:35
tonglithat is the strict limit.14:35
topolso hopefully are zips and tars are under these limits?14:35
tongliany file bigger than that will be rejected.14:35
topolerr our zips and tar14:36
hogepodgetopol: mu suggestion would be to just schedule mainteance to bring it up to date, but I know some would throw things at me for that suggestion14:36
topolhogepodge I like that idea14:36
topoltongli markvoelker, thoughts?14:37
topolyou want to try pinning the old wordpress for now?14:37
tongliwell, we do want to specify a release for sure.14:38
markvoelkerSeems like it would be relatively easy to provide option to try the latest wordpress or use a local copy.  Best of both worlds?14:38
tongliblindly using the latest release will be an issue regardless.14:38
markvoelkerE.g. maybe have a variable for the tarball location which can be a url or file:/// ?14:38
topolmarkvoelker, good point14:38
skazitongli: with such limits I would suggest to pin as much as possible from external resources and keep only our/modified content on the repo14:39
tongliwe already have the option (in configuration file) for you to select a release (where to get the wordpress).14:39
tonglibut the code to deploy them is the same.14:39
tongli@skazi, we can try that.14:39
topolskazi that plan sounds good to me as well14:40
tonglismaller file can go in to the git hub repo, bigger file, other means.14:40
topolOk, let's try that14:40
topoltongli with that approach will we be able to get wordpress bck runing soon?14:41
tongli@topol, I hope so,14:41
topolOk, lets hope for the best14:42
tongliit is just the time. I really really want to spend some time fixing the existing workload first.14:42
tonglithen dive into the kubernetes.14:42
topoltongli, thats fine14:42
tonglipriority thing.14:42
topolgo ahead14:42
topolyour priority makes sense to me14:42
topolmost folks arent back to work for another week anyway :-014:43
topolnext item:14:43
topoltopol create a short blog article to update everyone on the status of the interopchallenge14:43
topolI will get this done this week :-)14:43
topolWill include some pictures I took of everyone at the summit14:44
topol#topic open discussion14:44
*** openstack changes topic to "open discussion (Meeting topic: interop_challenge)"14:44
topolanything else we need to discuss?14:44
tongli@topol, couple of things.14:45
topolgo ahead tongli14:45
tonglithere is a comment to the lesson's learnt patch.14:45
tongliI copied the comment to the etherpad,14:45
zhipengho/ that was me14:45
tongliplease take a look.14:45
tongli@zhipengh, please let everybody know what you mean. I am not sure I can address your comment.14:46
zhipenghokey. I do like the current content of the lesson leanrt doc, however it might just be too techy for some users14:46
zhipenghtherefore what I suggested is to have an overview section14:47
zhipenghdescribe in a broad stroke that what interop chanllege has found/fixed14:47
zhipenghthen go into the details like what we have now14:47
topolzhipengh Having an overview section makes sense to me.  Will you push a patch with a first draft?14:48
zhipenghsure no problem :)14:48
tongli@zhipengh, I would like to have the current patch in, then you can change based on this.14:48
zhipenghtongli okey14:48
tongliotherwise, it will be just sitting there. which is what happened.14:48
topolzhipeng, cool14:49
topoltongli does your patch need some +2's?14:49
topoltongli got a review link?14:49
tongliin the etherpad.14:49
tongli@topol, yes.14:49
tonglihttps://review.openstack.org/#/c/409847/14:50
topolFolks it s #link https://review.openstack.org/#/c/409847/14:50
tonglisorry, I lied, it was not in the etherpad.14:50
topolIm gonna +2 it even though tongli lied and made me check the etherpad14:50
tongli@topol, most forgiven leader I ever had.14:51
tongli@topol, thanks.14:51
topolanyone else able to +2 and +A and then zhipeng can add to the merged patch?14:53
topoltongli :-)14:53
*** garloff has quit IRC14:53
tongliMark can, luzC can, zhipengh can14:53
* markvoelker is looking again as I haven't read it since before the holiday break...stand by14:54
topolwe can keep adding patches that revise it.14:54
tongli@markvoelker, please take a look again.14:54
tongli@topol, yes, that is the point of having the github so that we can always update it.14:55
markvoelkerdone14:55
topolcool! Thanks14:55
tonglithanks guys.14:55
topol#action zhipengh to add overview section to lessons learned doc14:56
topol4 mins left. anything else?14:56
zhipenghwill we have ptg sessions ?14:56
topolzhipengh, we definitely should. Do we want informal sessions or do we want to lock in a time14:57
topolI believe there will be plenty of rooms/space for us to meet14:57
zhipenghis it required to book a room through Thiery ?14:58
topolI asked him and he told me we could wither use some of the refstack room or their would be informal meeting space as well14:58
zhipenghcool14:59
topolI logged his response in one of our last meetings14:59
topolso space is covered.14:59
topolits more how much time folks want to carve out and use for interop? A day?14:59
topollets discuss this at next weeks meeting15:00
tongli half day maybe enough.15:00
topol#action all discuss PTG time allotment15:00
topolTHANKS EVRYONE15:00
zhipenghagree tongli15:00
topol#endmeeting15:00
*** openstack changes topic to "This channel does not run Meeting Infrastructure"15:00
openstackMeeting ended Wed Jan  4 15:00:49 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-01-04-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-01-04-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-01-04-14.00.log.html15:00
*** garloff has joined #openstack-meeting-515:01
*** zhipengh has left #openstack-meeting-515:02
*** tongli has quit IRC15:14
garloffa15:25
*** garloff has quit IRC15:40
jlvillal#startmeeting test15:54
openstackMeeting started Wed Jan  4 15:54:13 2017 UTC and is due to finish in 60 minutes.  The chair is jlvillal. Information about MeetBot at http://wiki.debian.org/MeetBot.15:54
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:54
*** openstack changes topic to " (Meeting topic: test)"15:54
openstackThe meeting name has been set to 'test'15:54
jlvillal#help blah blah15:54
jlvillal#undo15:54
openstackRemoving item from minutes: #help blah blah15:54
jlvillal#endmeeting15:54
*** openstack changes topic to "This channel does not run Meeting Infrastructure"15:54
openstackMeeting ended Wed Jan  4 15:54:36 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/test/2017/test.2017-01-04-15.54.html15:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/test/2017/test.2017-01-04-15.54.txt15:54
openstackLog:            http://eavesdrop.openstack.org/meetings/test/2017/test.2017-01-04-15.54.log.html15:54
*** pabelanger has joined #openstack-meeting-516:11
*** pabelanger has quit IRC16:19
*** pabelanger has joined #openstack-meeting-516:19
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:20
*** jroll has joined #openstack-meeting-516:22
*** matrohon has quit IRC17:31
*** pabelanger has left #openstack-meeting-517:42
*** matrohon has joined #openstack-meeting-519:24
*** fitoduarte has joined #openstack-meeting-519:27
*** fitoduarte has quit IRC19:30
*** ttx has quit IRC19:36
*** ttx has joined #openstack-meeting-519:36
*** matrohon has quit IRC21:58
*** clarkb has joined #openstack-meeting-522:52
*** openstack has joined #openstack-meeting-522:55
*** ChanServ sets mode: +o openstack22:55

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