14:00:23 #startmeeting Octopus weekly meeting 14:00:23 Meeting started Mon Apr 27 14:00:23 2015 UTC. The chair is ulik. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:23 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:00:23 The meeting name has been set to 'octopus_weekly_meeting' 14:01:19 Hi, please #info, so we know who is listening. 14:01:41 #info Fatih Degirmenci 14:01:42 #info Larry Lamers (VMware) 14:01:52 #info zhifeng jiang 14:01:57 #info Jun Li 14:01:59 #info on irc only Praksh 14:02:01 #info chigang 14:02:14 We are all IRC only ;-) 14:02:17 #info Brian Smith 14:02:30 ok thanks 14:02:46 #info aricg 14:02:54 #info 14:02:56 #info David Karr 14:03:38 I put on the agenda for today: 14:03:59 Arno Release follow-up, Move main wiki pages to git, Release 2 Brainstorming 14:04:12 Anything else? 14:04:26 I think that's a good agenda to start with 14:04:43 that's good 14:04:53 OK. then let's go 14:05:03 #topic Arno Release follow-up 14:05:26 were there any requests to Octopus? 14:05:45 #info Meimei 14:05:48 not that much at the moment 14:05:50 What will be plan for rolling in BGS and OSCAR into Octopus, is there a plan ? 14:06:05 rprakash: can we stick to subject please 14:06:08 Arno issues first 14:06:35 So any deploy steps running smootly? 14:06:35 I though it was follow on o octopus not follow up, so I take back my question 14:07:03 #info Deployment in Ericsson and Intel labs are "running" according to BGS 14:07:20 #info But baremetal deployment is yet to be completed for Fuel and Foreman 14:07:26 #info on LF HW 14:08:11 OK better question: Deploy scripts now called regularly on LF PODs? 14:08:24 not yet 14:08:54 as we all know, we are very dependent on the BGS output 14:09:14 so, we won't be ready until they're ready - and they're not ready yet 14:09:19 So they still try manual deploy on LF.... 14:09:33 I'm not so sure that either 14:09:39 if manual deploy works or not 14:09:50 there have been some discussions regarding LF Lab setup 14:09:59 which will probably be finalized today 14:10:09 and then first manual deployments should happen there 14:10:13 and then we come next 14:10:20 OK that's a start then to see things moving. 14:10:42 so, this was dependency towards BGS 14:10:48 we have dependency to FuncTest as well 14:11:03 But it's disappointing that lab setup is that criticatl - will say no flexibility in the deploy...... 14:11:11 is there anything we Octopus can do for this? 14:11:13 Yes Functest is second question..... 14:11:35 MatthewL2: I don't think Octopus has too much to help here 14:11:45 regarding LF HW setup 14:11:46 I don't know. As far as I know they also try manually 14:12:24 ok 14:12:47 Agree. We cannot do much. 14:13:07 We can polish our Arno documents. 14:13:39 agree 14:13:51 Pipeline document is not merged yet. 14:14:55 I just checked that jenkins wow is also not there (I thought we had it already) 14:15:01 #info We have 2 documents waiting to be merged 14:15:08 #link https://gerrit.opnfv.org/gerrit/#/c/399/ 14:15:13 #link https://gerrit.opnfv.org/gerrit/#/c/400/ 14:15:25 #info pipeline and slave connection documentation 14:15:51 Do you still wait for reviews? 14:16:08 could be good everyone can take a look and give feedback 14:16:19 we can keep them open for reviews 1 more day 14:16:27 and merge tomorrow 14:16:44 this way we can get everyone aware of what we are doing for Arno :D 14:16:53 We are a good group here. So please everybody have a look and put comments. 14:17:02 some reviewer may don't review in time, this is really a question 14:17:12 #info Everybody Please engage and review 14:17:33 we normally should wait 24hrs at least given that we're on different locations 14:17:34 No one talking or I am off line. 14:17:52 but this was a special case to get more input so that's why I didn't merge them 14:18:12 but yes, as ulik says, you have 1 more day 14:18:37 once Arno is out of the door, we will improve the documentation based on "evolved" CI 14:18:49 +1 14:19:03 but anyway, documentation is almost done for R1 - and this is a "reference" documentation 14:19:21 won't be released as part of Arno since CI is not something to be released 14:19:34 it just outlines how we do CI for OPNFV 14:20:03 if there is no other documentation update 14:20:10 If you want to see how it looks like in html, you can find the 2 existing docs already via the wiki links. 14:20:22 This leads to the next topic. 14:20:24 I'd like to say some words regarding FuncTest 14:20:38 I have skimmed it 14:20:39 OK go ahead I wait 14:21:02 mainly pay attention to the robot they use 14:21:15 #info We've been doing some trials with available FuncTest suites on Orange and Ericsson slaves 14:21:49 #info We had some hangings on Orange slave when we run vim-tempest 14:21:59 #info But it "completed" fine on Ericsson slave 14:22:12 #link https://build.opnfv.org/ci/view/functest/job/functest-vim_tempest-test/ 14:22:30 #info We are now waiting for input for vping-test 14:22:45 #info this will again probably be done on Ericsson slave 14:23:02 #info so, we have some progress 14:23:17 and that's all for functest 14:23:35 join to #opnfv-functest channel if you want to keep up to date with functst stuff 14:23:45 ok, I know more, now 14:23:48 Good point! 14:23:56 sorry - opnfv-testperf channel 14:24:31 #info Main FuncTest contacts are morgan_orange, jose_lausuch and pbandzi at the moment 14:24:41 By the vping-test exercise did you learn something for the setup? 14:24:55 we haven't tried vping as of yet 14:25:01 waiting input from Malla (?) 14:25:04 I mean about what will be possible problems when moving that to LF? 14:25:36 sorry but haven't come that far 14:25:41 fdegir: yes. I successfully tested vPing on orange POD manually but people from NTT are customizing vPing 14:25:52 OK. No problem. Just a question..... 14:26:04 thanks morgan_orange 14:26:19 #info vPing has successsfully been tested on Orange POD manually 14:26:33 #info People from NTT are customizing vPing 14:26:40 We have almost completed vping test in our local test-bed, hopefully by tomorrow, we will submit for review. 14:26:51 it seems BTW that there is a vPing scenario in tempest :) 14:27:24 #info Updates to vPing has been tested locally and will be sumitted for review tomorrow (input from Malla) 14:27:44 thanks Malla 14:27:57 and I think that's all for FuncTest vs Octopus updates 14:28:11 ok then.... 14:28:15 #topic Move main wiki pages to git 14:28:47 #info Part of main octopus wiki page is already created from rst file. 14:29:18 #info I can help at this topic, just give me the list of pages you want moved 14:29:46 vlaza: we already fixed them - 2 of them were merged 14:29:48 Did you check what I did? 14:29:51 2 of them are under review 14:30:10 but we still have this embedding images to html issue 14:30:38 #info Here are the pages we either finished working on or pending to be merged 14:30:49 #link CI Pipeline: https://gerrit.opnfv.org/gerrit/#/c/400/ 14:31:05 #link Jenkins Slave connection: https://gerrit.opnfv.org/gerrit/#/c/399/ 14:31:18 #link Artifact Repo Usage: https://gerrit.opnfv.org/gerrit/#/c/393/ 14:31:31 #link JJB Usage: https://gerrit.opnfv.org/gerrit/#/c/397/ 14:31:45 fdegir: we can try to upload images also into artifactory while merging 14:32:02 I think we should take a discussion with aricg regarding this 14:32:13 since it is a common thing to solve for all projects 14:32:19 aric is here 14:32:20 sure, we ca talk after the meeting 14:32:28 yes. 14:32:32 yep 14:32:39 not all the details in the meetig.... 14:32:53 Should we also move https://wiki.opnfv.org/octopus/flows to repo? 14:33:09 ulik: flows is covered by pipeline document 14:33:22 right. sorry. 14:33:42 Then when pipeline doc is there, we can remove that link. 14:33:57 yes; that's something I did for artifact repo 14:34:05 we can do the same for flows page as well 14:34:05 what about https://wiki.opnfv.org/octopus/infrastructure? 14:34:22 that page is also outdated 14:34:28 (kind of) 14:34:47 a new "more general" infra document can be created 14:34:50 and moved to git 14:34:54 yes 14:35:20 fdegir: https://gerrit.opnfv.org/gerrit/#/c/387/ is necessary for the https://gerrit.opnfv.org/gerrit/#/c/399/?? 14:35:55 meimei: not at the moment since document talks about manual connection 14:36:02 it doesn't have reference to that script 14:36:31 ok 14:37:12 fdegir, do we need a new infra rst document? 14:37:54 I think the outdated info from the link ulik put there can be removed 14:38:00 and what is left can be put into .rst file 14:38:37 Can somebody help fdegir and do it? 14:38:49 I can try 14:38:51 #link https://jira.opnfv.org/browse/OCTO-63 14:39:02 above is the story for infra document 14:39:18 feel free to take it over please 14:39:25 OK. So we have a couple of actions: 14:39:48 #action all to review 399 and 400 14:40:09 #action MatthewL2 new infra document according to OCTO-63 14:40:32 #action uli remove outdated links etc. in main page. 14:40:37 Did I forget one? 14:40:41 nope 14:40:45 that was all I think 14:40:54 just a quick info to everyone 14:41:02 #info The documentation we have in git talks about "what we currently have" 14:41:09 #info not "we want to have" 14:41:29 agree 14:41:31 so, please do reviews and the documentation based on this 14:41:57 So the info on main page about what we currently have should be in git, all other information just in wiki. 14:42:11 or etherpad for brainstorming 14:42:20 yes.... 14:42:46 I'll try to make that a bit more clear.... 14:43:13 Anything else about doc? 14:43:29 should we put agreed regarding doing documentation in git? 14:43:38 yes. 14:43:41 for "reference documentation" 14:43:50 so everyone can review it and/or be made aware 14:43:50 Anybody against that? 14:44:14 agreed..... 14:44:28 #agree all reference documentation shall be put in git 14:44:54 agree 14:45:19 .. and all git documents should be accessible easily via the wiki. E.g. the links we already have should point to all docs. 14:45:43 Should we also put links to download the pdfs? 14:46:11 we could do that as well 14:46:38 Yes, I think it's also better to keep the links to pdf's 14:47:21 Just put a link to the pdf from artifact repo, so people will see it easily. Yes. Will do. 14:47:35 #action uli to add also links to pdf documents. 14:47:49 Anything else about doc? 14:48:23 nope. so let's spend a few remaining minutes.... 14:48:31 #topic Release 2 Brainstorming 14:48:42 Everybody found the etherpad? 14:48:56 #link https://etherpad.opnfv.org/p/octopusR2 14:49:17 I have put some topics this afternoon(china), you can see there 14:49:50 May I say too many Huawei? Where are others? 14:49:54 :) 14:50:41 but I'm quite chatty there as well :D 14:50:54 Yeah saw you. 14:51:14 I think it is good if eveyone can share what they think about how we can improve the CI moving to R2 14:51:23 it is a good place to have discussions 14:51:28 yep 14:51:33 Anyways, I suggest we go a little bit longer "internally" - that's the octopus team. 14:51:56 And make sure we have something to share with other projects as soon as Arno is done. 14:52:02 yep 14:52:09 yep 14:52:10 may be even a bit before that. 14:52:20 once arno is done, we should involve our "customers" in our discussions 14:52:41 customers = all the other OPNFV projects 14:52:50 right. We neeeeed their input. 14:53:22 But we get better input if we raise a few ideas. 14:54:02 OK. I think not much need to discuss it deeper here. Just write on the etherpad.... 14:54:17 sugeest first training to opnfv other proejct eams as what is Octopus is 14:54:30 teams 14:54:41 yea! 14:54:55 This will help hem what to expect and add value to opnfv 14:55:37 In what form? We already had a few training sessions. What's missing? 14:55:45 Plus what's the scope of ocotopus , does it include BGS an dOSCAR , or there will be seperate teams for them 14:56:00 no 14:56:01 Let's put training as another group on etherpad. 14:56:08 CI includes deployment as well 14:56:37 there is no separation and/or handover to another project such as oscar 14:56:45 anyway, we can discuss this on etherpad 14:56:48 that's a good question. 14:57:25 OK. I'll create a section for deploy 14:57:31 please don't 14:57:37 if we start separating 14:57:39 we lose the CI 14:57:48 fdegir: what is different with deployment in BGS 14:57:59 3 minutes left 14:58:14 Note Inputs from BGS and or other stacks and output Arfticacts for deployment need some interfaces and understanding , anyway will add my inouts to etherpad 14:58:17 CI is something that is above of build, deployment and test 14:58:29 whatever deployment mechanism is developed 14:58:39 I meant: Ideas around deployment environment .... ? 14:58:41 that is executed by CI 14:58:54 please do not forget e2e view 14:59:21 Yes. 14:59:27 agreed fdegir thats perfect e2e view 14:59:33 Folks... quick time check: You're at the top of the hr... 14:59:44 OK. we have to postpone and have better time next week for R2. 14:59:58 Thanks everybody in Octopus! 15:00:06 #endmeeting