13:59:10 #startmeeting OPNFV TSC meeting 13:59:10 Meeting started Tue Apr 28 13:59:10 2015 UTC. The chair is frankbrockners. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:10 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:59:10 The meeting name has been set to 'opnfv_tsc_meeting' 13:59:25 #info Uli Kleber 13:59:41 #info Gerald Kunzmann (DOCOMO) 14:00:47 #chair ulik 14:00:47 Current chairs: frankbrockners ulik 14:00:56 #info Dave Neary (proxy for Chris Wright) 14:01:19 #chair dneary 14:01:19 Current chairs: dneary frankbrockners ulik 14:01:28 :-) 14:01:58 Once on conf call speaker phone, once to see screen on phone 14:02:25 <[1]JonasB> #info Jonas Bjurel 14:02:48 #info Julien 14:02:59 #info Dirk Kutscher 14:03:01 #info Wenjing Chu 14:03:09 #chair [1]JonasB 14:03:09 Current chairs: [1]JonasB dneary frankbrockners ulik 14:03:13 #info morgan 14:03:18 Hi, is the audio bridge operational? (I am not hearing anything...) 14:03:32 Working here 14:03:32 there is. usual one. 14:03:35 dku: yes it is 14:03:42 ok, thanks -- 14:03:52 #link https://global.gotomeeting.com/join/798898261 14:04:41 can we pls wait 2 more minutes. Doctor? NFV REL call is still ongoing. 14:04:48 #chair rpaik 14:04:48 Current chairs: [1]JonasB dneary frankbrockners rpaik ulik 14:04:53 can we pls wait 2 more minutes? Doctor - NFV REL call is still ongoing. 14:05:49 #info agenda for today: https://wiki.opnfv.org/wiki/tsc#april_28_2015 14:07:01 #topic approval of previous minutes 14:07:11 * ulik tapio, can you (and others) #info please 14:07:14 #info Tapio Tallgren 14:07:32 #info previous minutes approved 14:07:39 #topic agenda bashing 14:07:42 #info Trevor Cooper 14:09:04 #info Bryan Sullivan 14:11:11 #info agenda agreed 14:11:29 #topic Arno Project plans & tracking 14:11:57 #info Manuel Rebellon 14:12:03 ulik, Which requirements projects? 14:12:29 where are these docs? 14:12:40 Doctor and Promise 14:12:44 both are in Gerrit 14:12:53 #info I would like to put somethign on the backlog: We should talk about how to deal with the requirement documents that were shared for review already. 14:13:23 #info Ui tpo discussion on requirement for requirment documents beyond Arno 14:13:26 #info requirement docs for Doctor and Promise; both are available in Gerrit 14:14:14 #action Uli to prepare the discussion on requirement projects document approval and further proceeding in the next TSC meeting 14:14:29 #info Gerald will help 14:14:58 #info Gerald asks if links to Doctor & Promise documents can be included in Arno documentations 14:15:21 #link https://wiki.opnfv.org/releases/arno/releasereadiness 14:15:57 #topic Arno project plans & tracking 14:16:01 #info How do we make requirement documents of projects and proposal for release of it and its dependency 14:17:10 #info Pharos update: waiting for finalization/documentation of LF HW POD deployments 14:17:39 #info Pharos requires another "couple of days" to complete the overall work for Arno 14:18:08 I have to leave after 90 mins 14:18:16 (so, in 1h10) 14:18:16 #info Dirk Kutscher 14:18:31 #info There is still deployment in devlopment lbas, migration to LF is continuing 14:19:19 #info Parviz 14:19:22 #info Getting things operational on LF is pending but both teams have a made a good progress like IPMI filtered on Firewall etc 14:19:27 #info Dave Neary is proxy for me (Chris Wright) today 14:20:47 #info BGS: Work still progressing to get things deployed on LF lab (progress made - but still work to be done). 14:20:49 #info At the same point awaiting Automation on LF, but good progress on Octopus documentation 14:21:19 #info Octopus: Docs progressing. Automatic build working. Automatic deploy pending BGS work 14:22:02 #info Functest: Manual installs of tools (Rally, Robot) available. 14:22:46 #info Functest: vIMS still pending (working in Metaswitch lab only). Requires features (e.g. Heat) originally not planned for Arno - but considered as a stretch addition. 14:22:58 #info Functest: Documentation progressing. 14:23:13 #info func_test working on scripts and some use cases and good work on meta switch lab , manual test on Ericsson lab, ODL being in pipeline today, before end of week will have better results 14:25:28 #info is it possible to use func_test in BGS for Smoke test? Ericcson is close and on Intel depends on resource available after LF , excluding IMS may be a week 14:26:46 #info BSG stack on Ericsson works and able to run Sanity checks, about 70 error from 300 in Fuel, some anaysis to be done to clear the tets and missing modules, may take few more days 14:27:59 #info Functest: Rough estimate: "couple of days to have smoke testing available" - "vIMS - unsure about required time to complete work". 14:28:40 #info Docs Iban - lot for progress, document guidelines, more comfortable with MS word, can use RST formats to be able to deploy to iso, pdf ad wiki formats 14:28:56 #info Docs: Team is there to help with converting proprietary file formats (like MSFT) to .rst 14:29:12 #info Iben reports that documentation pipeline coming along. If people are more comfrtable with MS Word, that can be converted to .rst 14:29:29 #info 4 projects using this docs formats in ci 14:31:32 #info staus and state of items per projct readme, lincense etc listed , some may require Architecture Guide, Installation Guide etc. is Customer consumable 14:31:47 #action Iben to provide an invventory of what is required for documentation 14:31:56 Iben is this it? https://wiki.opnfv.org/documentation_projects/opnfv_documentation?&#scope 14:32:08 #info across the project with contents may help as per Iben 14:33:21 #info for outgoing documents etc logo etc may be good and so some cleanup required 14:34:41 #info checklist of documents is defined as basic minimum and each project can add as and when there is seen addition al requirements 14:36:20 #info some templates are lsited in documents projects and feed back sought in Gitrepo 14:37:05 #link https://wiki.opnfv.org/documents MS Word template 14:37:20 #info please review +1 or -1 as one uses it 14:38:41 <[1]JonasB> #link https://gerrit.opnfv.org/gerrit/#/c/356/ 14:40:46 #info suggestion is to setup a meeting between Arno project leads and the documentation team so that documentation questions can be addressed 14:41:18 #action Iben to create a "documentation happy hour" where people can meet on IRC and get their docs questions answered 14:42:11 #info can we devide code review and documentation review in to diffrent links or can we use some filter? 14:44:56 Are all the currently available docs/remplates in https://git.opnfv.org/cgit/opnfvdocs/ ? 14:45:10 #info we need Arno users to check the documents whether they provide the necessary information 14:45:52 #info agree with Uli 14:46:31 bryan_att: no, they won't be visible on cgit until they get merged 14:46:42 iben, can you put a link in IRC which points to where the current docs/templates are for review? And where should we create new docs/templates that seem to be missing? 14:46:47 Still feels uncertain to me 14:47:12 here is a link to all open/merged documents on opnfvdocs: https://gerrit.opnfv.org/gerrit/#/q/project:opnfvdocs 14:47:12 <[1]JonasB> Agree 14:47:26 #info Target release date: Stil kept at 2nd half of May. 14:47:29 #undo 14:47:29 Removing item from minutes: 14:47:38 #info Target release date: Still kept at 2nd half of May. 14:47:43 #info We are further along in terms of release readiness, but not able to narrow down the Arno release target date 14:48:30 #topic Ratify updates to Section 7 of TSC Charter - https://www.opnfv.org/developers/technical-project-governance/tsc-charter 14:48:47 Can we time-box this topic to 10 mins max? 14:48:55 +1 14:49:02 If it takes any more then it should be punted back to the list 14:49:05 * frankbrockners we'll try hard 14:49:28 At the top of the hour I will move that we defer or approve. 14:49:29 fdegir, on the last topic can anyone add comments or +1 etc to the docs in gerrit or only the opnfvdocs committers? 14:49:46 everyone can do reviews and give +1/-1 14:50:05 only committers can give +2/-2 and merge 14:50:51 what's the difference between +1 and +2 (is 2 "I feel stronger"?) 14:51:03 +2 means the change can be merged to master 14:51:14 +1 means it is just good and someone else must approve and give +2 14:51:21 and merge can happen only if there has been a +2 14:52:57 bryan_att, A +2 is "this can be committed now" 14:52:57 merge to happen, +2 and jenkins verified, +2 is not enough if jenkins -1d the change 14:52:59 works for me either way - simple or not 14:53:06 Therefore, only committers can +2 14:55:04 #agree For internal project decisions where no consensus can be reached, a majority vote among all Committers of the project via +1 voting should be used. 14:55:04 A simple majority voting should be used for decisions within the TSC at which a quorum is present, unless otherwise required. 14:55:11 #agree Updated verbiage as presented by Ray was agreed. 14:55:17 5 minutes early! 14:55:42 #topic OPNFV Day at OpenStack Summit 14:55:48 #info voting process agreed 14:56:04 #undo 14:56:04 Removing item from minutes: 14:56:05 #undo 14:56:05 Removing item from minutes: 14:56:10 #info voting process agreed 14:56:18 #topic OPNFV Day at OpenStack Summit 14:56:28 (just getting things in order 14:57:56 #link https://etherpad.opnfv.org/p/Vancouver_OpenStack for preparation of Vancouver OpenStack summit 14:59:09 #info Looking through BP submitted , no design summit sessions are there for BP , so make few sessions of VNFFG , IPv6, Doctor, Multi-site for hashing out opnfv use cases 15:00:45 #info should the breakout sessions simultaneous or go one after another or divide 270 preople room in to partition or request facility to split 15:01:18 #info so post lunch can be split in 2 or 4 sessions tec 15:02:08 #info have agenda and then plan out 2 is better than 4 15:03:14 #info 3 slots 2 in paralle with say 20-40 min each etc 15:04:55 #info add to etherpad sessions and requirements for projects etc and with telcowg etc. 3 weeks from now so time is premium 15:05:30 #action dneary/rpaik/hkirksey to schedule an IRC session to discuss OpenStack Summit agenda 15:06:51 #info nfv global world no specific ther than opnfv day session details 15:07:06 #topic Project Proposal & Creation Review Checklist 15:07:22 #link https://wiki.opnfv.org/developers/project_proposal_creation_review_checklist 15:12:29 FYI for NFV World Congress: http://www.layer123.com/nfv-agenda-workshop/ 15:12:38 bryan_att, http://www.layer123.com/nfv-agenda-workshop/ 15:13:50 #info Bin Hui mentiones difference between maturity verses two weeks as mimimum and depending on project review and mailing list , prefer agree to maturity level 15:16:57 #info Frank would like updtae the page with this suggessions made earlier and get this suggested by Bin and finally voted to get into the new process 15:18:02 #action ChrisPriceAB bring this topic back to next week’s TSC call to come to a consensus 15:18:06 #topic Project Approvals 15:18:35 #info Yardstick - https://wiki.opnfv.org/project_proposals/yardstick 15:19:50 #info Yardstick: test framework, including test cases and test stimuli, to verify the infrastructure compliance when running VNF applications 15:27:04 #info anac, I'm interested in this project, please add me to the contributor list, 3x. 15:28:48 Moving to IRC only for the rest of the meeting... I have to drop off 15:29:02 #link to rally for #info on benchmarking https://wiki.openstack.org/wiki/Rally#Use_Cases 15:32:24 frankbrockners: will we have time for more creation reviews if we need to discuss all these details here? 15:33:44 ulik: ack - we'll move to vote shortly - 15min each is typical - so let's allow for some discussion 15:38:23 #startvote TSC to vote to create the project yardstick? (+1, 0, -1) 15:38:23 Begin voting on: TSC to vote to create the project yardstick? Valid vote options are , +1, 0, -1, . 15:38:23 Vote using '#vote OPTION'. Only your last vote counts. 15:38:39 #vote +1 15:38:39 #vote +1 15:38:41 #vote +1 15:38:43 <[1]JonasB> #vote +1 15:38:43 #vote +1 15:38:44 #vote +1 15:38:45 #vote +1 15:38:51 #vote +1 15:38:51 #vote +1 15:39:05 +1 15:39:13 #info - trevor Cooper representing Rajeev Koodli 15:39:35 <[1]JonasB> #info Jonas Bjurel representing Chris Price 15:39:48 #info GeraldK representing Ashiq Khan 15:40:08 #endvote 15:40:08 Voted on "TSC to vote to create the project yardstick?" Results are 15:40:08 +1 (8): frankbrockners, trevor_intel, bryan_att, GeraldK, tallgren, [1]JonasB, julien_ZTE, Parviz 15:40:34 I missed it 15:40:39 #vote +1 15:40:51 Too late? 15:40:56 #info Trevor Cooper 15:41:20 #info late +1 vote from Dave Neary 15:41:42 #info Project yardstick got approved by TSC majority vote over IRC 15:42:21 #info OPNFV Service Function Chaining project approval review 15:42:25 #link https://wiki.opnfv.org/network_function_chaining 15:44:47 #info no representative of OPNFV Service Function Chaining was on the TSC call to present the project. Project will be up for review at the next TSC meeting. 15:45:14 #link https://wiki.opnfv.org/onosfw 15:45:36 #info ONOS framework project review 15:45:45 #link https://wiki.opnfv.org/onosfw 15:52:41 Call finished early - joining back 15:59:52 what is link to opentack bp for ONOS ML2 driver? 16:02:27 #info to re-visit the project review next week 16:02:52 Ray - can we close? 16:02:58 #info re-visit first on agenda. 16:03:01 #stopmeeting 16:03:06 #endmeeting