14:59:04 <ChrisPriceAB> #startmeeting OPNFV TSC
14:59:04 <collabot`> Meeting started Tue Dec 15 14:59:04 2015 UTC.  The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:59:04 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:59:04 <collabot`> The meeting name has been set to 'opnfv_tsc'
14:59:10 <ChrisPriceAB> #topic roll call
14:59:14 <uli-k_> #info Uli Kleber
14:59:15 <ChrisPriceAB> #info Chris Price
15:00:06 <frankbrockners> #info Frank Brockners
15:00:31 <edgarstp> #info Edgar StPierre
15:00:45 <dneary> #info Dave Neary
15:00:46 <bjskerry> #info Brian Skerry
15:00:57 <dneary> (proxy for Chris Wright)
15:01:00 <GeraldK> #info Gerald Kunzmann (DOCOMO)
15:01:05 <ChrisPriceAB> #topic approval of previous minutes of meeting
15:01:10 <ChrisPriceAB> #link https://wiki.opnfv.org/wiki/tsc#december_8_2015 previous minutes
15:01:23 <ChrisPriceAB> #info minutes approved, no comments
15:01:29 <ChrisPriceAB> #topic Agenda Bashing
15:01:42 <ChrisPriceAB> #link https://wiki.opnfv.org/wiki/tsc#december_15_2015 todays agenda
15:02:13 <bryan_att> #info Bryan Sullivan
15:02:18 <dku> #info Dirk Kutscher
15:02:45 <ChrisPriceAB> #info no additions to the Agenda
15:02:56 <Julien-zte> #info Julien
15:02:57 <ChrisPriceAB> #topic OPNFV internship program proposal
15:03:06 <rpaik> #link https://wiki.opnfv.org/developer/internship-program main internship program page
15:03:10 <ChrisPriceAB> #chair rpaik
15:03:10 <collabot`> Current chairs: ChrisPriceAB rpaik
15:03:26 <dlenrow> # info dlenrow
15:03:27 <rpaik> #link https://wiki.opnfv.org/developer/intern-projects-page project proposal page
15:03:33 <dlenrow> #info dlenrow
15:04:13 <ChrisPriceAB> #info rpaik outlines the proposed structure for the internship program
15:04:25 <ChrisPriceAB> #info we have allocated a budget for around 10 interns for 2016
15:04:51 <ChrisPriceAB> #info any community member can propose an "internship project proposal" targetting graduate or undergraduate students
15:05:22 <ChrisPriceAB> #info The goal of the program is to advertise the project proposals to the student community
15:05:44 <ChrisPriceAB> #info the mentor who proposed the project will be responsible for selecting and mentoring the candidates
15:06:11 <ChrisPriceAB> #info rpaik has proposed a program that will be able to run all year to accomodate our global community.
15:06:56 <ChrisPriceAB> #info internships may run as a three month program, or optionally as a six month program for students who will be studying while doing the internship.
15:08:18 <ChrisPriceAB> #info the internship program pages can be improved by the community or by providing feedback directly to rpaik
15:08:57 <ChrisPriceAB> #info dneary outlines the constraining factor may be a limit to the number of mentors, is there a process for identifying mentors.
15:09:22 <ChrisPriceAB> #rpaik states that the success of this program will be based on the availability of our community to mentor the students.
15:10:01 <TomNadeau> effort from mentors depends on what the project is. I mentored an intern for ODL this summer
15:10:03 <ChrisPriceAB> #info there will be effort required from the mentor during the project.
15:10:12 <TomNadeau> and its a significant amount of work, depending on how you want to set it up
15:10:33 <TomNadeau> and what you want to achieve.
15:11:06 <TomNadeau> my summer project transitioned into a full on ODL project, so the work didn't stop at the end of the mentoring period. But its a very positive outcome.
15:11:27 <anac1> Can we define the required profile for the student(s) ?
15:11:30 <TomNadeau> The keys are to structure things well so that there are clear goals.
15:11:43 <TomNadeau> no required profile - thats up to the mentors
15:11:47 <ChrisPriceAB> #info dku states that a result or summary of the work would be valuable to provide at the end of the project for visibility and awareness of the results.
15:12:04 <TomNadeau> you can have separate projects, or even mentor students on existing project
15:12:23 <ChrisPriceAB> anac1 If you want to mentor you can provide such a profile to help with finding the right candidates, when publishing your project
15:12:42 <ildikov> anac1: there's a Desirable Skills: section on the Project proposal template, I guess that can be used for this purpose
15:13:00 <TomNadeau> in ODL we proposed projects, and then reviewed proposed students against those.
15:13:12 <TomNadeau> there were 2 milestones: half way point, and final.
15:13:31 <anac1> is there a link from ODL so we can get inspirtion?
15:13:39 <anac1> inspiration
15:13:46 <ildikov> anac1: https://wiki.opendaylight.org/view/Interns/Summer_2015#2015_Project_Proposals
15:13:48 <ChrisPriceAB> #info chrispriceab asks if we are constrained to 10 projects
15:14:07 <ChrisPriceAB> #info rpaik says we can increase the available budget if we have more mentors available for projects
15:14:10 <anac1> thanks
15:14:30 <bryan_att> #info We could make suggestions that the mentors post progress (e.g. on the wiki) toward the goals on a regular basis or at key progress points, without getting too specific on the timing.
15:15:08 <ChrisPriceAB> #info HKirksey describes that the quality of the mentor will be critical for the success of the program.  The interns are dependant on the mentor for their success which reflects on our community.
15:15:19 <ChrisPriceAB> #chair bryan_att
15:15:19 <collabot`> Current chairs: ChrisPriceAB bryan_att rpaik
15:15:39 <TomNadeau> i recommend 1:mentors setup but only on the same project. The time required to properly mentor and run a project can be considerable if its done well.
15:15:56 <TomNadeau> i know some that had multiple projects, and that is a lot of work depending on what your day job is *)
15:15:59 <ChrisPriceAB> #info dneary asks if there is an expectation that the project be OPNFV focused, or also be able to wrk in upstream projects?
15:16:17 <ildikov> dneary: thanks, I wanted to ask the exact same question :)
15:16:22 <ChrisPriceAB> #info rpaik states that both would be viable, as long as the work relates to OPNFV developmental efforts.
15:16:59 <Parviz> #info Parviz Yegani
15:17:21 <ChrisPriceAB> #info dneary adds that upstream mentoring requires competent mentors form the upstream community.  and to keep the projects simple.
15:17:27 <TomNadeau> but i suppose that since opnfv is paying the bill, that the projects should be opnfv-related *)
15:18:04 <ildikov> also if we don't have team members from the upstream projects we cannot guarantee reviews on patches and progress, which can be an issue
15:19:46 <Ritch> Scope of project needs to be right for 3 to 6 months, Common training for interns, Follow-on Internship
15:19:54 <ChrisPriceAB> #topic Brahmaputra update
15:20:01 <ildikov> rpaik: +1 for starting and then checking what worked and what not
15:20:29 <ChrisPriceAB> #info debra has been working with the community on CI/Genesis/test infrastructure focus activities.
15:20:57 <ChrisPriceAB> #info a community call was held for plugin development as it was identified as a gap in our Brahmaputra development
15:21:36 <ChrisPriceAB> #info more discussion will be needed for test case writing and  upcoming milestone E in January
15:22:06 <ChrisPriceAB> #link https://wiki.opnfv.org/releases/brahmaputra#overview brahmaputra release page
15:24:08 <bryan_att> #info It would be good to clarify that if a use case turns out not to be verifiable, that use case needs to be removed from the release docs, or clearly put into a non-released backlog.
15:24:09 <ChrisPriceAB> #info GeraldK asks if we have a summary of the features available for all installer in Brahmaputra
15:24:30 <frankbrockners> #link https://git.opnfv.org/cgit/genesisreq/tree/docs/sources/system-requirements.rst
15:24:41 <frankbrockners> #link https://git.opnfv.org/cgit/genesisreq/tree/docs/sources/ux-requirements.rst
15:26:34 <bryan_att> So there is a significant difference between Arno and B, i.e. in Arno a base system *would* be installed without any options selected. Just to clarify if this is the case.
15:27:14 <ChrisPriceAB> #info uli-k describes that we do not yet have a stable base for our testing projects to further develop stability in the test suites.
15:30:34 <fdegir> we identified 8 pods to use; 4 for installers and 4 for used for CI/testing/releases
15:30:44 <fdegir> only 3 pods are operational at the moment
15:31:52 <fdegir> and I personally think we should focus/stick on the plan
15:33:01 <fdegir> here is the link to identified PODs: https://wiki.opnfv.org/brahmaputra_testing_page
15:33:07 <fdegir> the first table on the page
15:33:27 <ChrisPriceAB> #topic Review and comments on the API workshop material
15:34:23 <ChrisPriceAB> #link https://wiki.opnfv.org/_media/community/opnfv_infomodels.pptx proposed material for the API modelling meeting on behalf of OPNFV
15:34:50 <ChrisPriceAB> #info the intention of this meeting is to communicate our desire to collaborate with SDO' performing interface modelling and specification
15:34:56 <ChrisPriceAB> #undo
15:34:56 <collabot`> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1aab9d0>
15:35:03 <ChrisPriceAB> #info the intention of this material is to communicate our desire to collaborate with SDO' performing interface modelling and specification
15:35:34 <ChrisPriceAB> #info bryan_att is still looking for input from the community on some technical areas.
15:36:39 <ChrisPriceAB> #info #info bryan_att will outline the way in which open source project adopt standards and implement them as they are made available
15:37:19 <ChrisPriceAB> #info working quickly and iteratively is the best way of SDO's interacting with open source projects on emerging standards.
15:42:05 <ChrisPriceAB> #info GeraldK adds that we may not need to model every interface in Yang/TOSCA but should be open to adopt existing interfaces where it makes sense.
15:42:43 <ChrisPriceAB> #topic Methods of publishing requirements work with our release
15:42:59 <rpaik> #info bryan_att adds that ETSI pre-workshop meeting on Dec. 17th
15:45:55 <rpaik> #info uli-k adds that if requirements are added to the documentation tree, it may not require a lot of effort
15:46:09 <GeraldK> #info Uli points out that the documents we release should receive a proper review before publication
15:48:14 <bryan_att> it depends upon what you mean by requirements docs
15:48:30 <bryan_att> I believe you mean specifically bluepritsd
15:48:36 <bryan_att> I believe you mean specifically blueprints
15:49:01 <bryan_att> not all req docs are meant for upstream consumption - some are OPNFV-centric
15:49:54 <ChrisPriceAB> #info there is a view that requirements projects are living documents that are not fixed in time.
15:50:00 <ildikov> bryan_att: but still getting outdated :(
15:50:20 <edgarstp> There are requirements being defined that are in search of blueprints to send upstream.
15:50:47 <ChrisPriceAB> #topic creation review for OVN for NFV
15:51:08 <bryan_att> ildikov: if a doc is useful it will be maintained. if not useful it should be archived.
15:51:17 <ildikov> bryan_att: I think we could link to the artifacts page regarding the active requirements projects' documents
15:51:23 <ChrisPriceAB> #link https://wiki.opnfv.org/ovn4nfv ovn for nfv project proposal
15:51:26 <edgarstp> These need sponsor members to convert the requirements to blueprints and execute to them. The requirements are good for capturing use cases and such, but are lacking in execution.
15:51:59 <edgarstp> +1 on just linking to requirements as independent docs on artifacts page
15:52:05 <ChrisPriceAB> #info the goal of this project is to align on NFV requirements and contribute upstream to OVN to address then
15:52:30 <ildikov> edgarstp: right, but I think we could think of advertising more the already existing documents and not even wait until the release
15:52:30 <ChrisPriceAB> #undo
15:52:30 <collabot`> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1bc9ed0>
15:52:33 <ChrisPriceAB> #info the goal of this project is to align on NFV requirements and contribute upstream to OVN to address them
15:52:52 <edgarstp> @ildikov: +1
15:52:52 <collabot`> edgarstp: Error: "ildikov:" is not a valid command.
15:53:02 <edgarstp> ildikov: +1
15:53:04 <ildikov> edgarstp: as if we can get attention early enough that can even help with the use cases phase in some cases
15:53:30 <bryan_att> ildikov: yes, at least that would provide the link to the "living docs". I made the suggestion that the artifacts page provide links to the "stable/Brahmaputra" docs. and the latest docs, as the reader may want to see one or the other and should not have to hunt with different results across projects.
15:55:10 <ChrisPriceAB> #info parviz asks what additional capability OVN provides
15:55:16 <ildikov> bryan_att: yeap, I think it's a good approach to make them available and add a note to warn people to check the latest version
15:55:55 <ChrisPriceAB> #info vikramdham answers that OVN provides an alternative method of implementing existing features, but distributes network control elements.
15:57:22 <ChrisPriceAB> #info bjskerry asks if this project will work with the ovsnfv project
15:57:37 <ChrisPriceAB> #info vikram answers that the project intends to align
15:58:31 <ChrisPriceAB> #info chrispriceab asks if the project could be implemented within the scope of the ovsnfv project
15:58:51 <ChrisPriceAB> #info vikram answers that the objectives of the projects area quite different
15:59:31 <Julien-zte> #info agree with VikramDham
16:00:11 <ChrisPriceAB> #startvote Shall the TSC vote to create the ovn4nfv project? (+1, 0 -1)
16:00:11 <collabot`> Begin voting on: Shall the TSC vote to create the ovn4nfv project? Valid vote options are , +1, 0, -1, .
16:00:11 <collabot`> Vote using '#vote OPTION'. Only your last vote counts.
16:00:49 <dlenrow> #vote +1
16:00:51 <Julien-zte> #vote +1
16:00:51 <Wenjing> #vote +1
16:00:52 <bryan_att> I believe we have had enough discussion on the technical community call
16:00:59 <edgarstp> #vote +1
16:00:59 <bjskerry2> #info Brian Skerry
16:01:05 <bryan_att> these questions are coming pretty late
16:01:28 <bryan_att> #vote +1
16:02:27 <dlenrow> My understanding is we don't prune on project creation, we prune on elevation to mature.  People want to work on this. We should let them.
16:02:44 <dneary> #vote +1
16:02:45 <bjskerry2> #vote +1
16:02:48 <dku> #vote 0
16:02:49 <ChrisPriceAB> #vote +1
16:02:57 <uli-k_> #vote 0
16:03:06 <GeraldK> #vote 0
16:03:10 <Parviz> #vote 0
16:03:21 <ChrisPriceAB> #endmeeting