========================= #opnfv-meeting: OPNFV TSC ========================= Meeting started by ChrisPriceAB at 15:01:28 UTC. The full logs are available at http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-03-15.01.log.html . Meeting summary --------------- * dlenrow (dlenrow, 15:01:32) * Chris Price (ChrisPriceAB, 15:01:35) * Bryan Sullivan (bryan_att, 15:01:41) * Uli Kleber (ulik, 15:01:46) * Frank Brockners (frankbrockners, 15:01:46) * Tapio Tallgren (Nokia) (tapio__, 15:02:10) * fuqiao (proxy (fuqiao, 15:02:29) * Approval of previous minute (ChrisPriceAB, 15:02:39) * AGREED: TSC approved the previous minutes (ChrisPriceAB, 15:03:06) * Agenda Bashing (ChrisPriceAB, 15:03:13) * Gerald Kunzmann (DOCOMO) (Gerald_K, 15:03:59) * I would like to add a discussion about OpenStack blueprint deadlines and how we act in a coordinated manner across OPNFV. (bryan_att, 15:04:21) * I'll help (dlenrow, 15:05:56) * Review of NFV#9 meeting (ChrisPriceAB, 15:06:38) * Chris at TST meeting at ETSI, proposed a contribution re similarity between reqs & defs on Phase 2 for testing (bryan_att, 15:07:43) * ... similarities etc call for closer collaboration with OPNFV (bryan_att, 15:08:29) * ... we need to get access to the ETSI proposals e.g. a link if it can be open (bryan_att, 15:10:04) * ... Chris will add a note to the list on what was stated in case we dont have access (bryan_att, 15:10:26) * CP stated to SDO collab meeting agreed to LOI between ETSI and OPNFV (dlenrow, 15:10:56) * ... ETSI plans to write a letter of intent re cross-group coorindation, leveraging work across groups (bryan_att, 15:11:02) * ... cross-consortia discussion went on later, anyone there to share what happened? (bryan_att, 15:11:51) * Parviz was there (bryan_att, 15:12:03) * TMF, ETSI NFV, 3GPP SA5 will work closely together (Gerald_K, 15:12:32) * ... TMF, ETSI ISG, 3GPP SA5 will work to enhance the mgmt stack. Immediate OPNFV impact may be minimal (bryan_att, 15:12:36) * ... TMF ZOOM will work with ISG on Phase 2 POCS (bryan_att, 15:13:13) * JUlien (julien_ZTE, 15:13:16) * ... Work in SA5 will inform specs for MANO stack (bryan_att, 15:13:48) * ... open question is how to coordinate the ISG IFA WG (interfaces & arch) and SA5 (bryan_att, 15:14:24) * ... ZOOM is being used as "marketing collateral" to influence the industry on NFV (bryan_att, 15:15:02) * http://docbox.etsi.org/ISG/NFV/05-CONTRIBUTIONS/2015/NFV(15)000057_Further_collaboration_between_OPNFV_and_ETSI_NFV.docx (ETSI Portal; closed for ETSI members) (Gerald_K, 15:15:28) * (available to ETSI members) (Gerald_K, 15:15:48) * Dave L was there; ETSI was happy OPNFV supported it also. (bryan_att, 15:15:48) * dlenrow adds that ETSI NFV leadership was very happy that OPNFV attended, and were also apologetic about the lack of agility/bureaucracy in the ETSI process (dneary, 15:16:11) * no action items for OPNFV from that workshop (Gerald_K, 15:16:48) * OPNFV Release 1 Naming (ChrisPriceAB, 15:17:12) * Ray sent the suggestions on names out to the list based on current inputs (ChrisPriceAB, 15:17:56) * Ray asks if we settled on "A" and real names (bryan_att, 15:18:01) * Chris: we haven't voted on methodology - that should be implicit in the vote (bryan_att, 15:18:36) * ... we need to trim the options; any we can drop, or any higher priority? (bryan_att, 15:19:00) * ... it can be anything at this point - we have not eliminated all but "A" e.g. (bryan_att, 15:19:31) * in OpenStack there is also a legal review (Gerald_K, 15:19:40) * we should also do this filter before doing the voting (Gerald_K, 15:19:54) * ... e.g. for (TM) (bryan_att, 15:20:25) * The filter is to names which could lead to trademark issues (like Amazon, perhaps) (dneary, 15:20:34) * Pranav Mehta (Pranav_, 15:21:19) * I like fictional rivers (bryan_att, 15:21:48) * how about Phoenix (bryan_att, 15:22:21) * what about "anchor" holding OPNFV together a river name (rprakash, 15:22:36) * or Styx (bryan_att, 15:24:05) * alphabetical order has benefit of being "predictable" and will avoid for the same discussion all over (Gerald_K, 15:24:06) * Chris: OK to allow Ray to simplify the list and get legal approval, run a doodle etc? (bryan_att, 15:24:51) * Frank: only the TSC can vote? (bryan_att, 15:25:54) * Chris: good question - put to the TSC, community, or anyone? (bryan_att, 15:26:25) * Ray: it would be hard to open it too wide (bryan_att, 15:26:41) * Dave keep it simple, to the tech-discuss list. (bryan_att, 15:27:22) * I'd go with the community voting if feasible (AndreaP, 15:27:47) * Chris: it is a community right to have a vote on this (Gerald_K, 15:28:01) * Frank: we should include name with vote (bryan_att, 15:28:10) * AGREED: That voting shall be open to all participants of the opnfv-tech-discuss list, we will ask voters to enter their name when voting. (ChrisPriceAB, 15:29:02) * opnfv-tech-discuss topic filters (ChrisPriceAB, 15:29:28) * Parviz Yegani (Parviz, 15:29:31) * Ray: topic filter email sent out last week - use Jira name rather than repo name (ChrisPriceAB, 15:30:26) * Bryan: why do we need to change (bryan_att, 15:32:17) * why not use filter on email client side? (Gerald_K, 15:32:48) * if you want to address a specific project, use a specific tag in the email subject (Gerald_K, 15:33:27) * A tag includes the project tag [BGS] in the e-mail header (ChrisPriceAB, 15:33:40) * you can choose in the mailman config which tags to receive (Gerald_K, 15:34:05) * should be "disabled" by default. anyone who wants to use it can "enable" it (Gerald_K, 15:34:59) * enable auto-filtering in subject-line with project-name=repo-name or project specified tag and this optional (rprakash, 15:37:46) * AGREED: TSC agrees to enable filters on opnfv-tech-discuss, Ray will provide clarification on the wiki. (ChrisPriceAB, 15:38:13) * Chris: need to address project naming conventions etc (bryan_att, 15:38:46) * ... call for a proposal for project name & tool chain proposals (bryan_att, 15:39:05) * Project naming conventions, repo names, Jeera project tags (volunteers?) (rprakash, 15:39:50) * LINK: https://wiki.opnfv.org/developers/project_page_template (rpaik, 15:39:50) * Ray: project page template can include instructions (bryan_att, 15:40:11) * ACTION: Ray & Chris to update the project page template and project key facts sections to reflect the naming needs across Jira/mail/repositories (ChrisPriceAB, 15:40:17) * Maintaining project leader, committer & contributor list (ChrisPriceAB, 15:40:51) * Ray: Aric had an idea for source info better than the wiki (bryan_att, 15:41:31) * Ray explains that the current method of managing project leader, committer and contributors on the wiki is creating some confusion. (ChrisPriceAB, 15:41:34) * Aric: wiki list can be modified - have to go back and review changes; adding a list of contributors to the repo would enable automatic reports (bryan_att, 15:43:02) * aric proposes that when a project is created a file is created in the repository that describes the current list of committers & project lead. (ChrisPriceAB, 15:43:04) * "commiters" should be in repo, but contributors can be many and change , so access control should be for commiters? (rprakash, 15:44:57) * pals (pals, 15:44:57) * Frank: it would be good to have HTTP access to the wiki so that it can be easily synced with the wiki (bryan_att, 15:46:10) * ... "access to the repo"... (bryan_att, 15:46:27) * ... key project facts should be stable and visible on the wiki - a uniform source of info (bryan_att, 15:46:53) * +1 to Frank's proposal (bryan_att, 15:47:06) * https://gerrit.opnfv.org/gerrit/gitweb?p=releng.git;a=summary (aricg, 15:47:41) * Aric: gitweb doesn't need authentication (bryan_att, 15:48:07) * ACTION: frankbrockers and hinds to work with aric to prototype autogenerating key project facts onto the wiki pages. (ChrisPriceAB, 15:49:26) * Chris: every project needs a leader / contact person (bryan_att, 15:50:07) * ACTION: hinds to propose a security project for documentation and activity (ChrisPriceAB, 15:50:49) * Development tool training, Jira, Gerrit, Git, Jenkins (ChrisPriceAB, 15:51:09) * Chris: not all are familiar with tools e.g. agile, jira, tying to gerrit etc (bryan_att, 15:51:50) * ... some members would be willing to do basic walkthrus (bryan_att, 15:52:06) * +1 (bryan_att, 15:52:19) * ... how do we move forward (bryan_att, 15:52:44) * Bryan just get people started setting up the sessions (bryan_att, 15:52:56) * Chris: will do that, record on GTM etc for later use (bryan_att, 15:53:20) * ACTION: chris to oraganise training sessions and record them for others to follow (ChrisPriceAB, 15:53:30) * some tutorial and recording of training sessions for getting started on tools (rprakash, 15:53:36) * Release 1 Updates (bryan_att, 15:53:54) * Chris: goal is R1 happens when we have achieved our intent, but is time-boxed (bryan_att, 15:54:27) * ... Uli captured some text on that (bryan_att, 15:54:45) * Uli: sent an email with text, and put it on an etherpad (bryan_att, 15:55:19) * LINK: https://etherpad.opnfv.org/p/release1 (ulik, 15:55:19) * ... Added Chris' intro, comments, and a summary, functionality, documentation, operations environment, availability (bryan_att, 15:56:20) * ... should serve as a R1 description - we can continue to edit on etherpad (bryan_att, 15:56:48) * ... first sentence sets the overview (bryan_att, 15:57:07) * Frank: how relates to Chris' email (bryan_att, 15:57:22) * Uli: took the email and comments, with the result being the current text on etherpad (bryan_att, 15:57:51) * Chris: R1 is not addressed on wiki yet. Do we need a specific page for it, and other things related? (bryan_att, 15:58:30) * Uli: we need that, for openness on what we want to achieve beyond TSC and OPNFV (bryan_att, 15:59:04) * +1 (bryan_att, 15:59:08) * +1 (rprakash, 15:59:26) * Frank: public info can set things in stone - marketing team may want to edit the storyline (bryan_att, 15:59:54) * ... barebones tech detail could be used by marketing to create the public storyline (bryan_att, 16:00:18) * +1 (julien_ZTE, 16:00:19) * +1 - it would be good to get marketing directly involved in public messsaging (bryan_att, 16:00:55) * Frank: we can add components as tag lines as they get firmed up, and avoid the marketing type description (bryan_att, 16:01:44) * Uli: we are not too early - 7 weeks left and we should know now what we want there (bryan_att, 16:02:05) * Frank: just recommend tht we let marketing craft the "tagline" (descriptive text) (bryan_att, 16:02:33) * Chris: this is worth starting to collect on the wiki (bryan_att, 16:03:03) * Prathima: will create the marketing message given the basic input from the TSC (bryan_att, 16:03:43) * Uli: should we get basic agreement on the existing descriptive content now (bryan_att, 16:04:41) * Chris: defer that due to MWC focus - focus on our intent for the wiki (bryan_att, 16:05:08) * AGREED: to begin to describe release one on the OPNFV wiki page, capturing the intended activities and objectives (ChrisPriceAB, 16:05:33) * ACTION: ulik to begin to put this material on the wiki page (ChrisPriceAB, 16:06:00) * Project plans & tracking (ChrisPriceAB, 16:06:25) * LINK: https://wiki.opnfv.org/get_started/get_started_installer_approach (frankbrockners, 16:06:28) * Frank indicates there are a number of deployment tools being worked on. Each has a status page showing current activity. (ChrisPriceAB, 16:07:30) * Frank: on BGS, we have three (Fuel, Foreman, OpenSteak) efforts on basic installer - page linked has info on each (bryan_att, 16:07:42) * Frank invites OPNFV members to look into the status pages and help where they are able to. (ChrisPriceAB, 16:07:54) * ... opportunities to help in various places (bryan_att, 16:08:32) * the team is starting to put the material into Jira for more public visibility (ChrisPriceAB, 16:08:46) * ... 50% are certain April date is achieveable (bryan_att, 16:08:49) * ... thus we need more hands on deck (bryan_att, 16:09:00) * Frank asks for more engineers to engage where possible in order to hit the April deadline. (ChrisPriceAB, 16:09:25) * ulik outlines the current activity in CI, they are currently focused on integrating with other projects for automated test (ChrisPriceAB, 16:09:53) * Uli: for Octopus, hackfest showed Jenkins setup etc (bryan_att, 16:09:54) * Bryan: would be great to get info on presentations and takeaways from the hackfest, on the wiki (bryan_att, 16:10:59) * LINK: https://wiki.opnfv.org/events/meetupfeb19-2015 (ChrisPriceAB, 16:11:10) * Palani: for FuncTest, jira project was created. Any TSC guidelines on creating user stories? (bryan_att, 16:11:58) * pals outlines the functest activity. Jira is created and the team is looking to structure the epics/stories/activities for clarity. (ChrisPriceAB, 16:12:32) * Frank: create a bunch of epics for various installer approaches for a high level grouping purpose (bryan_att, 16:12:33) * ... individual cases underneath avoids flat high-level confusion (bryan_att, 16:13:09) * Palani: have outlined 5 stories in basic FuncTest (bryan_att, 16:13:25) * ... prototyping / development - two are working incl Morgan, started using devstack & tempest (bryan_att, 16:13:53) * ... tech issues are being worked; I'm not duplicating that effort (bryan_att, 16:14:20) * ... using devstack are started using tempest tests on OpenStack in a VM (bryan_att, 16:14:57) * palani looking for volunteers to work on stories. (ChrisPriceAB, 16:15:14) * ... would be great to assign stories to get community action (bryan_att, 16:15:27) * Chris: just need to be people willing to do the work, not committers (bryan_att, 16:15:49) * Palani: will create stories and send to the list (bryan_att, 16:16:02) * Frank: Tim and Dan were successul/mostly on bringing up Foreman in Intel lab - should sync up with them on testing e.g. Robot once we have a stable environment. Running tempest in top eg. via CI should be possible (bryan_att, 16:17:35) * Documentation (bryan_att, 16:17:49) * Chris has documenation template (rprakash, 16:19:10) * Chris: reach out if you want to help on thdocumentaiton (bryan_att, 16:19:41) * https://wiki.opnfv.org/documentation_projects/opnfv_documentation (Gerald_K, 16:20:01) * ulik Uli K is leaving im2bz2p__ (MIke Young) will stand in his place. (ChrisPriceAB, 16:22:09) * OpenStack blueprint handling (ChrisPriceAB, 16:22:14) * request in last week meeting to submit BPs, but there was no process defined yet how to handle this (Gerald_K, 16:22:58) * proposed BPs should be as visible and aligned among multiple projects (Gerald_K, 16:23:49) * Brian outlines the need to have a well formed set of ideas on how we will work toward openstack. (ChrisPriceAB, 16:24:14) * Chris: proposal to have 30mins discussion prior to next TSC call (Gerald_K, 16:25:38) * Bryan: can someone provide info on the deadline (bryan_att, 16:26:06) * he asks for OPNFV to coordinate internally before discussing too much externally to reduce confusion (ChrisPriceAB, 16:26:15) * LINK: http://www.openstack.org/blog/2015/02/sign-up-for-openstack-upstream-training-in-vancouver/ (ChrisPriceAB, 16:26:30) * Dave will send mail with details on it (Gerald_K, 16:28:08) * final call for BPs for L-release will be Vancouver meeting in May (Gerald_K, 16:29:21) * reviewer resources is currently a bottleneck in OpenStack (Gerald_K, 16:30:18) * we need reach out to people involved in OpenStack (Gerald_K, 16:31:19) * Bryan: I take the result of this as that Requirements projects are not cadenced with OPNFV releases (bryan_att, 16:32:26) * Gerald: we may need high-level description of the BPs in the Wiki, but shall use OpenStack terminology in the OpenStack Launchpad (Gerald_K, 16:34:19) * LINK: https://wiki.opnfv.org/community (ChrisPriceAB, 16:34:24) * Bryan: we will also meet on IRC to tune the doctor blueprints e.g. for alignment with copper (bryan_att, 16:34:26) * DaveN will add the OpenStack release information, suggest we have similar for OpenDaylight, Open vSwitch, DPDK, Linaro, OpenContrail and other projects (bryan_att, 16:36:10) * Project Approvals (ChrisPriceAB, 16:36:29) * ... and a knowledge base about how decisions get made in upstream projects (bryan_att, 16:36:32) * LINK: https://wiki.opnfv.org/requirements_projects/data_collection_of_failure_prediction (ChrisPriceAB, 16:36:57) * ???/Huawei: goal is to avoid failures in advance (bryan_att, 16:37:11) * ...(sharing screen) (bryan_att, 16:38:48) * presenter is Linghui Zeng/Huawei (Gerald_K, 16:39:17) * ... ETSI has defined general requirements for failure prediction (bryan_att, 16:39:51) * ... most important is data collection and depends upon real-time data sources; second major component is a failure predictor (bryan_att, 16:41:38) * ... goal of this project is to investigate functional gaps and identify data needing to be collected (bryan_att, 16:42:27) * ... current gaps known are e.g. re state of guest OS (bryan_att, 16:43:10) * architecture: predictor will provide input to Doctor module (Gerald_K, 16:43:21) * data collection is done by Ceilometer, Zabbix, ... (Gerald_K, 16:43:48) * ... predictor will send notifications to other handlers e.g. doctor module (bryan_att, 16:44:27) * first goal is to focus on the data collector (Gerald_K, 16:44:52) * Chris: scope is to find out data that shall be collected, but is not yet available (Gerald_K, 16:45:51) * Bryan: is the scope limited to what is available thru OpenStack? (bryan_att, 16:47:24) * the first release will not consider the interface to "FaultManagement" (Gerald_K, 16:48:46) * Linghui: data collection is different to Doctor data collection (Gerald_K, 16:50:43) * investigates on how to hook various open source monitors in Monasca (Gerald_K, 16:53:57) * VOTE: Voted on "TSC to approve the creation of the collector (data collection for failure prediction) project?" Results are, +1: 9 (ChrisPriceAB, 16:57:09) * ACTION: everyone cheer for bryan for taking notes (ChrisPriceAB, 16:58:30) Meeting ended at 16:59:33 UTC. Action items, by person ----------------------- * ulik * ulik to begin to put this material on the wiki page * **UNASSIGNED** * Ray & Chris to update the project page template and project key facts sections to reflect the naming needs across Jira/mail/repositories * frankbrockers and hinds to work with aric to prototype autogenerating key project facts onto the wiki pages. * hinds to propose a security project for documentation and activity * chris to oraganise training sessions and record them for others to follow * everyone cheer for bryan for taking notes People present (lines said) --------------------------- * bryan_att (105) * ChrisPriceAB (58) * Gerald_K (38) * collabot (16) * dneary (7) * rprakash (7) * dlenrow (5) * frankbrockners (4) * fuqiao (3) * aricg (2) * Pranav_ (2) * rpaik (2) * tapio__ (2) * julien_ZTE (2) * ulik (2) * AndreaP (1) * joekidder (1) * im2bz2p__ (1) * pals (1) * Parviz (1) * dnaery (0) Generated by `MeetBot`_ 0.1.4