14:58:16 <ChrisPriceAB> #startmeeting OPNFV TSC
14:58:16 <collabot> Meeting started Tue Feb 10 14:58:16 2015 UTC.  The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:58:16 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:58:16 <collabot> The meeting name has been set to 'opnfv_tsc'
14:58:23 <ChrisPriceAB> #topic roll call
14:58:29 <ChrisPriceAB> #info Chris Price
14:59:43 <julien_ZTE> #info Julien
14:59:54 <ulik> #info Uli Kleber
15:00:34 <dku_> #info Dirk Kutscher
15:00:37 <Wenjing> #info Wenjing Chu
15:01:24 <cdub> #info Chris Wright
15:01:43 <ChrisPriceAB> #chair ulik
15:01:43 <collabot> Current chairs: ChrisPriceAB ulik
15:01:48 <frankbrockners> #info Frank Brockners
15:01:58 <ChrisPriceAB> #chair rpaik
15:01:58 <collabot> Current chairs: ChrisPriceAB rpaik ulik
15:02:51 <ChrisPriceAB> #chair dneary
15:02:51 <collabot> Warning: Nick not in channel: dneary
15:02:51 <collabot> Current chairs: ChrisPriceAB dneary rpaik ulik
15:02:51 <Pranav> #info Pranav Mehta
15:03:46 <GeraldK> #info Gerald Kunzmann (DOCOMO)
15:03:51 <ChrisPriceAB> #topic Approval of previous minutes
15:03:54 <dlenrow> #info dlenrow
15:03:59 <ChrisPriceAB> #agree previous minutes approved
15:04:05 <ChrisPriceAB> #topic Agenda Bashing
15:04:52 <tapio_> #info Tapio Tallgren
15:05:29 <dneary> #info Dave Neary
15:05:52 <ChrisPriceAB> #chair dneary
15:05:52 <collabot> Current chairs: ChrisPriceAB dneary rpaik ulik
15:06:23 <dneary> Thanks ChrisPriceAB - turns out I was talking into the ether b/c of a long IRC disconnect timeout
15:06:43 <ChrisPriceAB> #topic Committer Promotions
15:07:12 <bryan_att> #info Bryan Sullivan
15:07:29 <ChrisPriceAB> #link https://wiki.opnfv.org/developer/committer_promotions
15:10:02 <dneary> #info Requirements: History of activity, demonstrated knowledge and judgement to project lead, willingness to lead in the project
15:10:39 <dneary> #info Project lead nominates to the TSC, committer promotion must be approved by the TSC
15:11:11 <dneary> #info No goal to get in the way, but TSC promotion review is important to introduce new committers to community
15:12:48 <rprakash___> link for meeting  #?https://global.gotomeeting.com/
15:16:51 <dneary> #info Question raised as to whether the TSC is the right place to approve committers, discussion whether decision on committer promotions should be handled by project leads directly
15:17:22 <ulik> @prakash: https://global.gotomeeting.com/join/798898261
15:17:22 <collabot> ulik: Error: "prakash:" is not a valid command.
15:17:23 <dneary> #info TSC should be able to stop promotions in the situation where something happens not in accordance with the charter
15:17:52 <dneary> #info Still important to inform TSC of new promotions, to ensure that people are introduced to the community
15:18:50 <bryan_att> #info any resolutions of the TSC should be first input in the IRC as "proposed resolution" - this makes it easier for meeting attendees to know exactly what is being proposed as a resolution, prior to agreement
15:19:07 <dneary> #info TSC role should be limited to mitigating issues, or intervening when there is a problematic contributor
15:19:16 <ChrisPriceAB> #agree The TSC agrees that committer promotions should be handled by the project committers, the TSC should only be involved when there are highlighted issues to be addressed in the promotion.
15:19:24 <Parviz> #info Parviz Yegani
15:19:31 <dneary> ChrisPriceAB, Looks god
15:19:33 <dneary> good
15:19:36 <ulik> good
15:20:14 <dneary> Once more, reference for meetbot commands: https://wiki.opnfv.org/wiki/meetbot
15:21:18 <dneary> ulik, Did you see a need for updating the charter on this point? I'm unfamiliar with it
15:21:39 <ChrisPriceAB> #action Dave Lenrow to update the wiki to reflect the above statement.  https://wiki.opnfv.org/developer/committer_promotions
15:21:44 <ulik> dneary, I think it is very flexible
15:22:29 <dneary> So are we naming Uli the project lead?
15:22:41 * dneary is confused
15:22:48 <ulik> dneary, the project has to do that.
15:23:24 <dneary> Isn't a project lead named during the creation review?
15:24:16 <ulik> yes, but we didn't do it in the past.
15:24:20 <ChrisPriceAB> #topic OPNFV Release 1
15:24:38 <ChrisPriceAB> #info BGS project update - Frank
15:24:42 <cdub> dlenrow: this is openstack process: https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess
15:25:03 <dlenrow> cdub: Thx
15:25:04 <cdub> dlenrow: i think the main differenec we have in our process is...no defined process for a project to follow
15:25:12 <ChrisPriceAB> #info the main topic for BGS is to automate the foundation installation.  A number of experiments are ongoing in this area.
15:25:46 <ChrisPriceAB> #info The focus right now is to get the OpenStack OpenDaylight integration done, some issues have been found with this activity.
15:25:48 <cdub> dlenrow: ours is simply: https://www.opnfv.org/developers/technical-project-governance/tsc-charter
15:26:26 <cdub> dlenrow: which has "A standard meritocracy model with new Committers will be approved and implemented by the TSC which will include provision for fully open code submission, review, acceptance, build, test, delivery, and support model."
15:26:31 <ChrisPriceAB> #info the project is driving to create a draft schedule for release 1
15:26:49 <ChrisPriceAB> #info octopus project updates
15:27:20 <ChrisPriceAB> #info The project is focused on bottom up work, looking at the infrastructure and working with the LinuxFoundation on the tools
15:27:40 <ChrisPriceAB> #info Release Intent discussion
15:31:34 <bryan_att> #info in addition to "in an HA configuration" we need to ensure that release 1 includes an easily deployable OPNFV deployment in non-HA configurations, e.g. on minimal hardware requirements for development purposes
15:35:24 <rprakash___> #info availability of release, proper documentation  , functionality in Release 1, Delivery by early teams/projects, Infrastrure to continuously build, develop and install ... more clarity required = by Frank
15:38:31 <rprakash___> #info VNF application should work on VIM  say specific ones like say vLB and say  another
15:39:33 <rprakash___> #info what HA means
15:40:20 <rprakash___> #info more details installing HA for what Control Plane or Data Plane or both
15:41:48 <rprakash___> #info Pharos and Function Test Proje ct has done lot of the above and so setting expections for these project is key to defining content of Relase 1 - Chris
15:42:07 <julien_ZTE> #@rprakash___ info I think that means we will install the control nodes of Openstack in HA mode.
15:43:19 <ChrisPriceAB> #chair rprakash__
15:43:19 <collabot> Warning: Nick not in channel: rprakash__
15:43:19 <collabot> Current chairs: ChrisPriceAB dneary rpaik rprakash__ ulik
15:43:31 <ChrisPriceAB> #chair rprakash___
15:43:31 <collabot> Current chairs: ChrisPriceAB dneary rpaik rprakash__ rprakash___ ulik
15:43:42 <rprakash___> #action Access to environment on Jenkins on OPNFV to do some CI work is key within the domain pointing to their own setup or infrastructure if necesssary
15:48:33 <ulik> #info Bryan proposes that minimal configuration be part of release 1 (maybe optional)
15:54:01 <bryan_att> #info I set a development environment as a key goal, perhaps not gating, but the fact that something is not gating should not decrease it's importance. I believe that functional gap closure is the key thing that OPNFV will drive - performance gap closure is essential also but development of solutions for both will often be developed in non-HA laboratory
15:54:01 <bryan_att> environments or on developer laptops. The "platform" should support those development environments.
15:55:09 <cdub> #link http://lists.opnfv.org/pipermail/opnfv-tsc/2015-February/000480.html list of release details
15:56:30 <rprakash___> #acition  "have content defined for release 1 a minimal set infra harware function " and then set the date at next meeting
15:58:01 <julien_ZTE> #agree @bryan_att, maybe we will update the wiki about the evironment refered to bgs
15:58:16 <rprakash___> #info define "project" expections for release 1 , and deliverables in reality"  and this includes Pharos , Functional test etc.
16:01:42 <ulik> #info besides BGS and Octopus, also Pharos and functest should be in the group
16:02:50 <cdub> hmm, phone crashed
16:04:45 <rprakash___> #info Progress for Project based on the Chris's 6 points with cpaibility and time lines
16:05:27 <dneary> Signing off, conflicting call
16:05:36 <rprakash___> #info Parveezs point endorsed by Frank as above
16:06:23 <rprakash___> #info getting right matrix for Project & CI tec.
16:06:31 <ChrisPriceAB> #topic  Quick update on Meet-up (Santa Rosa) & Hackfest (Prague)
16:07:23 <ChrisPriceAB> #info Ray gives an update on questions and communication traffic for coming the meet-up and hackfest
16:07:56 <ChrisPriceAB> #link https://etherpad.opnfv.org/p/MeetUpFeb19
16:08:06 <ChrisPriceAB> https://etherpad.opnfv.org/p/HackfestFeb23
16:13:00 <rprakash___> #info topic of interest between hackfest and OPNFV  to be probed including secuirity and other allignments
16:13:08 <ChrisPriceAB> #link https://etherpad.opnfv.org/p/HackfestFeb23
16:15:10 <rprakash___> #info should we use Tech review committe to evaluate the proposlas / projects fromally ?
16:16:34 <rprakash___> #info document the process between Tech review committee to TSC
16:17:33 <Parviz> @Parakash: Parviz not Parveez
16:17:33 <collabot> Parviz: Error: "Parakash:" is not a valid command.
16:17:46 <rprakash___> #in fo Thursday tech review helps community gather dicuss in details , cross project collab and get deeper in to project for clarification etc.
16:19:14 <rprakash___> #info Good socilizing mechnism and editing, proof reading , plus technical details and clarifications , thus very usefull as many particpants chime
16:20:45 <rprakash___> #info not all TSC members do attent Thursday Tech Review Meeting helps  whet the proposal for the team that brings helps get recommendation from Tech review committee
16:23:32 <ChrisPriceAB> #topic Project aprrovals
16:23:42 <rprakash___> #action Recommend that a new project goes through Thursday Tech Review Meeting to get clarity for TSC to approve
16:24:02 <ChrisPriceAB> #topic Creation review of the Re-visit Data Plane Acceleration prtoject
16:24:06 <ChrisPriceAB> #undo
16:24:06 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Topic object at 0x1cf6ad0>
16:24:15 <ChrisPriceAB> #topic Creation review of the Re-visit Data Plane Acceleration project
16:24:50 <ChrisPriceAB> #link https://wiki.opnfv.org/requirements_projects/data_plane_acceleration
16:25:17 <ChrisPriceAB> #info this is a re-review of the dpacc project.  Some clarifications were required after the previous review
16:26:55 <ChrisPriceAB> #info clarifications on the project include:  accommodation of both hardware and software aceleration, compatibility to existing API's should be leveraged, a layer approach to the solution should be adopted.
16:27:13 <ChrisPriceAB> #info OpenStack has been added as a relevant upstream project due to management interactions
16:28:32 <dlenrow> Is the implication that all listed are both contributors and committers?
16:29:00 <Parviz> #info Parviz
16:30:03 <rprakash___> #info Data Plane Acceeeleration seeks approval after Group agreeing to include both SWA and HWA in the two options propsed in the requirments
16:31:01 <rprakash___> #info Committers to have specific rights and hence seperating Commiters from Contributors for voting on decisions within the project
16:32:24 <rprakash___> #action Conditional approval subject to specifying the Commiters within some time period
16:33:29 <ChrisPriceAB> #startvote On conditional approval of the dpacc project, pending clarification of the committer list for the project? (+1, 0, -1)
16:33:29 <collabot> Begin voting on: On conditional approval of the dpacc project, pending clarification of the committer list for the project? Valid vote options are , +1, 0, -1, .
16:33:29 <collabot> Vote using '#vote OPTION'. Only your last vote counts.
16:33:33 <Pranav> #vote +1
16:33:34 <Guest71339> can that clarification be sent to the TSC list by some date please?
16:33:34 <julien_ZTE> #vote +1
16:33:35 <dku_> #vote +1
16:33:36 <frankbrockners> #vote +1
16:33:37 <ChrisPriceAB> #vote +1
16:33:37 <GeraldK> #vote +1
16:33:38 <tapio_> #vote +1
16:33:41 <cdub> #vote +1
16:33:43 <Guest71339> #vote +1
16:33:43 <Parviz> #vote +1
16:33:45 <dlenrow> #vote +1
16:33:48 <rprakash___> #vote +1
16:33:50 <bryan_att> #vote +1
16:33:57 <hui> +1
16:34:04 <Guest71339> BTW Guest71339 is Tom Nadeau
16:34:18 <ChrisPriceAB> #vote +1 (on behalf of Hui)
16:34:18 <collabot> ChrisPriceAB: +1 (on behalf of Hui) is not a valid option. Valid options are , +1, 0, -1, .
16:34:20 <dlenrow> If Guest71339 is TSC, you need a better nik.
16:34:36 <Guest71339> yes
16:34:56 <hui> #vote +1
16:34:56 <Guest71339> @dlenrow - yes I know. *)
16:34:56 <collabot> Guest71339: Error: "dlenrow" is not a valid command.
16:35:03 <dlenrow> Thx tom
16:35:04 <Guest71339> dlenrow - yes I know. *)
16:35:07 <ChrisPriceAB> #endvote
16:35:07 <collabot> Voted on "On conditional approval of the dpacc project, pending clarification of the committer list for the project?" Results are
16:35:07 <collabot> +1 (14): Pranav, frankbrockners, dku_, dlenrow, GeraldK, tapio_, Guest71339, ChrisPriceAB, hui, cdub, rprakash___, bryan_att, julien_ZTE, Parviz
16:35:12 <Wenjing> #vote +1
16:36:06 <GeraldK> GeraldK is today proxy for AshiqKhan
16:36:16 * ChrisPriceAB congratulations dpacc
16:36:34 <Guest71339> nic Tom
16:36:34 <cdub> /nick blahblah
16:37:11 <ChrisPriceAB> #topic Creation review of the OpenStack Based VNF Forwarding Graph
16:37:44 <ChrisPriceAB> #link https://wiki.opnfv.org/requirements_projects/openstack_based_vnf_forwarding_graph
16:38:11 <ChrisPriceAB> #info Cathy presents the project proposal as described on the linked WiKi page.
16:52:09 <rpaik> #info discussion on how the scope diagram in the project proposal maps to the OPNFV arch. diagram
16:58:20 <Yuriy> fully agree with rpaik, diagram should show where is all this box located in openstack arch. and opnfv arch.
17:03:09 <rpaik> #info suggestion to continue this discussion on a Thursday call (Technical Discussion mtg)
17:03:44 <julien_ZTE> #info I hope there is a some detail difference and releationship between forwarding graph with service chain
17:03:52 <rprakash___> #action Can we get Thursday meeting to re-review the projrct to clarify on scope & delivery path , plus plugins of Venodrs how they tie in
17:04:42 <rprakash___> #action ask questions through email for the project
17:05:47 <ChrisPriceAB> #info further questions related to the SFC project should be addressed on the coming technical meeting, to be reviewed for creation again next week.
17:05:52 <ChrisPriceAB> #endmeeting