*** matrohon has joined #openstack-meeting-5 | 07:59 | |
*** matrohon has quit IRC | 11:09 | |
*** matrohon has joined #openstack-meeting-5 | 12:59 | |
*** tongli has joined #openstack-meeting-5 | 13:28 | |
*** zhipengh has joined #openstack-meeting-5 | 13:52 | |
*** zhipengh has quit IRC | 14:00 | |
topol | #startmeeting interop_challenge | 14:00 |
---|---|---|
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
*** openstack changes topic to " (Meeting topic: interop_challenge)" | 14:00 | |
openstack | The meeting name has been set to 'interop_challenge' | 14:00 |
tongli | o/ | 14:00 |
skazi | o/ | 14:00 |
topol | Hi everyone, who is here for the interop challenge meeting today? | 14:00 |
topol | The agenda for today can be found at: | 14:00 |
topol | #link https://etherpad.openstack.org/p/interop-challenge-meeting-2017-01-04 | 14:00 |
markvoelker | o/ | 14:00 |
topol | We can use this same etherpad to take notes | 14:00 |
*** garloff has joined #openstack-meeting-5 | 14:00 | |
garloff | Happy new year everyone! | 14:01 |
topol | first topic: | 14:01 |
topol | #topic Welcome everyone to our 2017 Kickoff | 14:01 |
*** openstack changes topic to "Welcome everyone to our 2017 Kickoff (Meeting topic: interop_challenge)" | 14:01 | |
topol | WELCOME and Happy New Year!!! | 14:01 |
topol | next topic | 14:02 |
tongli | thanks Brad | 14:02 |
topol | #topic Refresh everyone on the decisions we made in December | 14:02 |
*** openstack changes topic to "Refresh everyone on the decisions we made in December (Meeting topic: interop_challenge)" | 14:02 | |
topol | AGREED: Kubernetes and NFV will be our top priority workloads for this round of the interop challenge | 14:02 |
topol | #link http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-12-14-14.00.html | 14:02 |
topol | So that's gets us all refreshed | 14:03 |
topol | #topic Review last meeting action items | 14:03 |
topol | #link http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-12-14-14.00.html | 14:03 |
topol | eeiden to push up the NFV workload to new repo as soon as possible | 14:04 |
topol | Is eeiden here? Has this been done? | 14:04 |
*** zhipengh has joined #openstack-meeting-5 | 14:04 | |
topol | I don't recall seeing any patches on this | 14:04 |
tongli | @topol, I did not see any patches. | 14:04 |
topol | K. We'll keep that action goin then | 14:05 |
topol | #action eeiden to push up the NFV workload to new repo as soon as possible | 14:05 |
topol | next action. | 14:05 |
topol | tongli to start on kubernetes | 14:06 |
topol | tongli, how is that going? | 14:06 |
tongli | @topol, yes, already started working on that. | 14:06 |
topol | Willing to share some details? Enquiring minds want to know | 14:06 |
*** hogepodge has joined #openstack-meeting-5 | 14:07 | |
topol | When might you have a patch for folks to review? | 14:07 |
tongli | probably in two weeks. | 14:07 |
topol | tongli, excellent! | 14:08 |
topol | Keep going! | 14:08 |
tongli | then we can add more things if it is too basic. | 14:08 |
topol | Very cool | 14:08 |
topol | next action | 14:09 |
topol | tongli to create lauchpad for our repo | 14:09 |
topol | Looks lije hogepodge did this correct? | 14:09 |
hogepodge | maybe docado? | 14:09 |
tongli | @topol, that is for bug tracking, right? | 14:09 |
topol | tongli yes | 14:10 |
tongli | if it is, then it is there already, and I have created a bug. | 14:10 |
topol | here is the link #link https://bugs.launchpad.net/interop-workloads | 14:10 |
tongli | right. | 14:10 |
topol | wasnt you hogepodge? | 14:10 |
topol | it was docado? | 14:10 |
tongli | it is all working, Chris created that for us. Thanks Chris. | 14:10 |
topol | THANKS docado!!! | 14:10 |
hogepodge | topol: yes, docadeo did it | 14:10 |
topol | docado gets a Gold Star! | 14:11 |
tongli | @topol, yes, | 14:11 |
topol | looks like we even have a bug posted | 14:11 |
topol | tongli looks like you triaged it | 14:12 |
topol | tongli were you going to try and fix it | 14:12 |
tongli | yes, I have been trying that for awhile. | 14:12 |
tongli | withno success. | 14:13 |
topol | #link https://bugs.launchpad.net/interop-workloads/+bug/1649949 | 14:13 |
openstack | Launchpad bug 1649949 in Interop Challenge Workloads "wordprocess failed to run wp core install" [Undecided,New] | 14:13 |
tongli | something went in actually break the lampstack workloads. | 14:13 |
tongli | I can not successfully run it any more. | 14:13 |
topol | so we get a new version of wordpress and that one no longer installs? | 14:14 |
tongli | I went all the way back (probably 10 patches back), it worked for ubuntu env. | 14:14 |
tongli | I think that the patches added to support fedora maybe the problem. | 14:14 |
tongli | but I can not be sure, spend quite few days on this already. | 14:14 |
topol | tongli 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 |
tongli | thinking who added the fedora support probably can fix it. | 14:16 |
topol | So this was a patch on the old repo? can we do a git blame check and see who added it? | 14:17 |
garloff | would be good indeed if the "old" workload stays in a working state ... | 14:17 |
tongli | sure. | 14:18 |
topol | garloff +++ | 14:18 |
topol | Thats putting it mildly | 14:18 |
topol | :-) | 14:18 |
tongli | I think we need to fix the old workloads. | 14:18 |
tongli | it bothers me a lot having the latest stuff not working. | 14:18 |
topol | tongli yes we most certainly do. Let's see if we can track down who added it | 14:19 |
topol | #action tongli, topol to track down who added the fedora patch | 14:19 |
topol | #action all please help trying to get wordpress back working | 14:19 |
topol | Next item: | 14:20 |
topol | all review and add stuff to the lessons learned doc | 14:20 |
tongli | is 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 |
tongli | just so that these content can be used by workloads. | 14:21 |
topol | tongli Im not sure I understand your question | 14:21 |
tongli | rely on some external site is sometimes difficult, when the content changes, the workloads may break. | 14:21 |
tongli | currently our workload download stuff such as wordpress code, theme, and content from external sites | 14:22 |
tongli | for 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 |
tongli | due to changed deployment methods or changed format. | 14:23 |
topol | so we could do that, but then we live in our own insulated bubble | 14:23 |
tongli | using the latest wordpress release, we can no longer import the example content because of the format change. | 14:24 |
tongli | true, I do not know what is the best way. | 14:24 |
topol | let's see how often wordpress continues to break us | 14:24 |
tongli | I found that one of the problems contributing to the current workload breakage is the wordpress content format change. | 14:25 |
topol | ideally, they dont break us too often and we stay up to date | 14:25 |
hogepodge | If this is meant to be a test environment, pinning to known working releases makes sense, since we're not testing wordpress, we're testing OpenStack | 14:25 |
tongli | @hogepodge, exactly. | 14:25 |
hogepodge | Or, just accept that if external dependencies break you fail and test for them (which is more of the 'OpenStack way') | 14:25 |
tongli | different wordpress release requires different way of deploy it, | 14:25 |
tongli | and the content could be different as well. | 14:26 |
tongli | the current sample wordpress content was downloaded from another site , which has to be modified slightly to import to new wordpress release. | 14:26 |
topol | hogepodge, 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 work | 14:26 |
tongli | I 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 |
tongli | that probably can help. But I am open for other good ideas. | 14:27 |
hogepodge | It 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 |
hogepodge | Fix on schedule means you can fall behind, especially if you don't honor the schedule. | 14:28 |
tongli | @hogepodge, yes. | 14:28 |
topol | my fear is that if we can't show workloads running with the latest wordpress and others run into that we have done them a disservice | 14:28 |
*** garloff has quit IRC | 14:28 | |
tongli | @topol, even with that, we still need to have a repo for content like openstack superuser award site. | 14:29 |
topol | Since were not in "important demo mode next week" my gut says seeing failures and fixing them is most valuable | 14:29 |
tongli | I suspect for kubernetes and nfv we will need something as well. | 14:29 |
skazi | for wordpress itself, we can pin the version by downloading from: https://wordpress.org/download/release-archive/ instead of the latest tarball | 14:29 |
hogepodge | for 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 release | 14:29 |
topol | tongli, 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-5 | 14:30 | |
skazi | tongli: 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 |
topol | tongli if we put them in a separate folder I think its fine | 14:31 |
topol | and then they get reviewed and controlled like everything else | 14:31 |
tongli | is everyone ok with that? | 14:32 |
tongli | I do not mind doing that. | 14:32 |
zhipengh | sounds great | 14:32 |
tongli | do we have an agreement? | 14:32 |
topol | Let's try it | 14:32 |
tongli | ok. sounds good to me. | 14:32 |
tongli | this helps , folks, thanks. | 14:33 |
topol | any concerns? actually folks can voice concerns when they see your patch | 14:33 |
tongli | sure, sure | 14:33 |
skazi | are 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 |
topol | K, 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 wordpress | 14:35 |
tongli | 1 GB per repo. | 14:35 |
tongli | 100 MB per file. | 14:35 |
tongli | that is the strict limit. | 14:35 |
topol | so hopefully are zips and tars are under these limits? | 14:35 |
tongli | any file bigger than that will be rejected. | 14:35 |
topol | err our zips and tar | 14:36 |
hogepodge | topol: 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 suggestion | 14:36 |
topol | hogepodge I like that idea | 14:36 |
topol | tongli markvoelker, thoughts? | 14:37 |
topol | you want to try pinning the old wordpress for now? | 14:37 |
tongli | well, we do want to specify a release for sure. | 14:38 |
markvoelker | Seems 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 |
tongli | blindly using the latest release will be an issue regardless. | 14:38 |
markvoelker | E.g. maybe have a variable for the tarball location which can be a url or file:/// ? | 14:38 |
topol | markvoelker, good point | 14:38 |
skazi | tongli: with such limits I would suggest to pin as much as possible from external resources and keep only our/modified content on the repo | 14:39 |
tongli | we already have the option (in configuration file) for you to select a release (where to get the wordpress). | 14:39 |
tongli | but the code to deploy them is the same. | 14:39 |
tongli | @skazi, we can try that. | 14:39 |
topol | skazi that plan sounds good to me as well | 14:40 |
tongli | smaller file can go in to the git hub repo, bigger file, other means. | 14:40 |
topol | Ok, let's try that | 14:40 |
topol | tongli with that approach will we be able to get wordpress bck runing soon? | 14:41 |
tongli | @topol, I hope so, | 14:41 |
topol | Ok, lets hope for the best | 14:42 |
tongli | it is just the time. I really really want to spend some time fixing the existing workload first. | 14:42 |
tongli | then dive into the kubernetes. | 14:42 |
topol | tongli, thats fine | 14:42 |
tongli | priority thing. | 14:42 |
topol | go ahead | 14:42 |
topol | your priority makes sense to me | 14:42 |
topol | most folks arent back to work for another week anyway :-0 | 14:43 |
topol | next item: | 14:43 |
topol | topol create a short blog article to update everyone on the status of the interopchallenge | 14:43 |
topol | I will get this done this week :-) | 14:43 |
topol | Will include some pictures I took of everyone at the summit | 14:44 |
topol | #topic open discussion | 14:44 |
*** openstack changes topic to "open discussion (Meeting topic: interop_challenge)" | 14:44 | |
topol | anything else we need to discuss? | 14:44 |
tongli | @topol, couple of things. | 14:45 |
topol | go ahead tongli | 14:45 |
tongli | there is a comment to the lesson's learnt patch. | 14:45 |
tongli | I copied the comment to the etherpad, | 14:45 |
zhipengh | o/ that was me | 14:45 |
tongli | please 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 |
zhipengh | okey. I do like the current content of the lesson leanrt doc, however it might just be too techy for some users | 14:46 |
zhipengh | therefore what I suggested is to have an overview section | 14:47 |
zhipengh | describe in a broad stroke that what interop chanllege has found/fixed | 14:47 |
zhipengh | then go into the details like what we have now | 14:47 |
topol | zhipengh Having an overview section makes sense to me. Will you push a patch with a first draft? | 14:48 |
zhipengh | sure no problem :) | 14:48 |
tongli | @zhipengh, I would like to have the current patch in, then you can change based on this. | 14:48 |
zhipengh | tongli okey | 14:48 |
tongli | otherwise, it will be just sitting there. which is what happened. | 14:48 |
topol | zhipeng, cool | 14:49 |
topol | tongli does your patch need some +2's? | 14:49 |
topol | tongli got a review link? | 14:49 |
tongli | in the etherpad. | 14:49 |
tongli | @topol, yes. | 14:49 |
tongli | https://review.openstack.org/#/c/409847/ | 14:50 |
topol | Folks it s #link https://review.openstack.org/#/c/409847/ | 14:50 |
tongli | sorry, I lied, it was not in the etherpad. | 14:50 |
topol | Im gonna +2 it even though tongli lied and made me check the etherpad | 14:50 |
tongli | @topol, most forgiven leader I ever had. | 14:51 |
tongli | @topol, thanks. | 14:51 |
topol | anyone else able to +2 and +A and then zhipeng can add to the merged patch? | 14:53 |
topol | tongli :-) | 14:53 |
*** garloff has quit IRC | 14:53 | |
tongli | Mark can, luzC can, zhipengh can | 14:53 |
* markvoelker is looking again as I haven't read it since before the holiday break...stand by | 14:54 | |
topol | we 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 |
markvoelker | done | 14:55 |
topol | cool! Thanks | 14:55 |
tongli | thanks guys. | 14:55 |
topol | #action zhipengh to add overview section to lessons learned doc | 14:56 |
topol | 4 mins left. anything else? | 14:56 |
zhipengh | will we have ptg sessions ? | 14:56 |
topol | zhipengh, we definitely should. Do we want informal sessions or do we want to lock in a time | 14:57 |
topol | I believe there will be plenty of rooms/space for us to meet | 14:57 |
zhipengh | is it required to book a room through Thiery ? | 14:58 |
topol | I asked him and he told me we could wither use some of the refstack room or their would be informal meeting space as well | 14:58 |
zhipengh | cool | 14:59 |
topol | I logged his response in one of our last meetings | 14:59 |
topol | so space is covered. | 14:59 |
topol | its more how much time folks want to carve out and use for interop? A day? | 14:59 |
topol | lets discuss this at next weeks meeting | 15:00 |
tongli | half day maybe enough. | 15:00 |
topol | #action all discuss PTG time allotment | 15:00 |
topol | THANKS EVRYONE | 15:00 |
zhipengh | agree tongli | 15:00 |
topol | #endmeeting | 15:00 |
*** openstack changes topic to "This channel does not run Meeting Infrastructure" | 15:00 | |
openstack | Meeting ended Wed Jan 4 15:00:49 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-01-04-14.00.html | 15:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-01-04-14.00.txt | 15:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-01-04-14.00.log.html | 15:00 |
*** garloff has joined #openstack-meeting-5 | 15:01 | |
*** zhipengh has left #openstack-meeting-5 | 15:02 | |
*** tongli has quit IRC | 15:14 | |
garloff | a | 15:25 |
*** garloff has quit IRC | 15:40 | |
jlvillal | #startmeeting test | 15:54 |
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:54 |
*** openstack changes topic to " (Meeting topic: test)" | 15:54 | |
openstack | The meeting name has been set to 'test' | 15:54 |
jlvillal | #help blah blah | 15:54 |
jlvillal | #undo | 15:54 |
openstack | Removing item from minutes: #help blah blah | 15:54 |
jlvillal | #endmeeting | 15:54 |
*** openstack changes topic to "This channel does not run Meeting Infrastructure" | 15:54 | |
openstack | Meeting ended Wed Jan 4 15:54:36 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:54 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/test/2017/test.2017-01-04-15.54.html | 15:54 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/test/2017/test.2017-01-04-15.54.txt | 15:54 |
openstack | Log: http://eavesdrop.openstack.org/meetings/test/2017/test.2017-01-04-15.54.log.html | 15:54 |
*** pabelanger has joined #openstack-meeting-5 | 16:11 | |
*** pabelanger has quit IRC | 16:19 | |
*** pabelanger has joined #openstack-meeting-5 | 16:19 | |
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:20 | |
*** jroll has joined #openstack-meeting-5 | 16:22 | |
*** matrohon has quit IRC | 17:31 | |
*** pabelanger has left #openstack-meeting-5 | 17:42 | |
*** matrohon has joined #openstack-meeting-5 | 19:24 | |
*** fitoduarte has joined #openstack-meeting-5 | 19:27 | |
*** fitoduarte has quit IRC | 19:30 | |
*** ttx has quit IRC | 19:36 | |
*** ttx has joined #openstack-meeting-5 | 19:36 | |
*** matrohon has quit IRC | 21:58 | |
*** clarkb has joined #openstack-meeting-5 | 22:52 | |
*** openstack has joined #openstack-meeting-5 | 22:55 | |
*** ChanServ sets mode: +o openstack | 22:55 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!