========================= #opnfv-meeting: OPNFV TSC ========================= Meeting started by ChrisPriceAB at 13:59:44 UTC. The full logs are available at http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-06-02-13.59.log.html . Meeting summary --------------- * roll call (ChrisPriceAB, 13:59:50) * Chris Price (ChrisPriceAB, 13:59:58) * Tapio Tallgren (Tapio_ta, 14:00:12) * Wenjing Chu (Wenjing, 14:00:13) * Morgan Richomme (morgan_orange, 14:00:38) * Uli Kleber (uli-k, 14:01:27) * Chris Wright (cdub, 14:01:47) * Dirk Kutscher (dku, 14:01:55) * rprakash (rprakash, 14:02:41) * Bryan Sullivan (bryan_att, 14:02:51) * Approval of previous minutes (ChrisPriceAB, 14:03:15) * Frank Brockners (frankbrockners, 14:03:35) * AGREED: TSC approves the previous minutes (ChrisPriceAB, 14:03:50) * Agenda Bashing (ChrisPriceAB, 14:03:55) * LINK: https://wiki.opnfv.org/wiki/tsc (ChrisPriceAB, 14:04:07) * Larry Lamers (VMware) (ljlamers, 14:05:13) * dlenrow (dlenrow, 14:05:21) * Ildiko Vancsa (ildikov, 14:05:46) * Hui (hui, 14:06:23) * Introducing Debra Scott (OPNFV Release Manager) (ChrisPriceAB, 14:06:55) * Debra will work with our community to establish our release processes and shepherd our projects through future OPNFV releases. (ChrisPriceAB, 14:08:15) * Arno Project plans & tracking (ChrisPriceAB, 14:09:02) * discuss ongoing release activities. (ChrisPriceAB, 14:09:21) * Chris reports that release documentation needs to be finalized tonight/tomorrow morning (rpaik, 14:12:03) * LINK: https://wiki.opnfv.org/meetings/bgs#june12015 (frankbrockners, 14:15:28) * BGS status update (ChrisPriceAB, 14:15:41) * Rajeev Koodli (rajeev, 14:15:50) * three remaining issues in the BGS project which we hope to complete prior to release. (ChrisPriceAB, 14:21:27) * functest update (ChrisPriceAB, 14:21:33) * morgan outlines that there have been discrepancies in executing testing when altering the platform. (ChrisPriceAB, 14:22:12) * morgan describes that all issues are known and able to be defined and documented in the release. (ChrisPriceAB, 14:22:35) * Issues in upstream community bugs result in limitations in our platform that are not able to be solved prior to the release. (ChrisPriceAB, 14:23:18) * documentation updates are required prior to release, stability remains an issue but is not able to be solved with the current release components. (ChrisPriceAB, 14:25:26) * every-one is exhausted :-) (understandably) (ChrisPriceAB, 14:25:49) * morgan_orange reports that there will be documentation on tests that are failing (rpaik, 14:34:23) * CI update (ChrisPriceAB, 14:35:04) * octopus has prepared a release procedure to be reviewed (ChrisPriceAB, 14:35:39) * Release process, labeling and artifact cutting (ChrisPriceAB, 14:35:46) * LINK: https://wiki.opnfv.org/octopus/releasepipeline (uli-k, 14:36:03) * LINK: https://wiki.opnfv.org/octopus/releasepipeline release process (ChrisPriceAB, 14:36:03) * Uli walks through the process described on the above link (ChrisPriceAB, 14:37:38) * Julien (julien_ZTE, 14:40:08) * Want to go through steps outlined by Uli on Wedesday (June 3rd) in preparation for the release on Thursday (rpaik, 14:44:31) * propose that we identify a cut off time/date so that the prep for the release has time to execute (RayNugent, 14:48:18) * Uli asks the TSC for a decision on the release tag format. (ChrisPriceAB, 14:48:46) * cdub agree that a format is needed and should work well with updates. (ChrisPriceAB, 14:49:06) * Proposed formats are (fdegir, 14:49:12) * using Openstack alike named tag (julien_ZTE, 14:49:19) * release/arno (ODL way) (fdegir, 14:49:20) * 2015.1.0 (fdegir, 14:49:25) * Arno.2015.1.0 (fdegir, 14:49:32) * arno_1.0.0 (fdegir, 14:49:39) * AGREED: TSC agrees to use arno.2015.1.0 as our release tag (ChrisPriceAB, 14:51:02) * arno_2515.1.0? (julien_ZTE, 14:51:31) * looks ok to me. (tnadeau, 14:51:36) * AGREED: TSC agrees to use stable/arno as our stable branch (ChrisPriceAB, 14:51:36) * frankbrockners asks for the artifact storage to include /scripts and /images (ChrisPriceAB, 14:55:18) * source code tag link, image or iso and documents will be released? (julien_ZTE, 14:59:52) * Arno landing page review (ChrisPriceAB, 15:03:20) * Ray demonstrates the Arno download landing page (ChrisPriceAB, 15:03:56) * LINK: https://wiki.opnfv.org/documentation/Arno current release documents (ChrisPriceAB, 15:06:21) * Arno support (ChrisPriceAB, 15:15:08) * a support mailing address exists support@opnfv.org (ChrisPriceAB, 15:16:26) * this can be set with a mailing list that is open for anyone to post to that we can use for OPNFV support (ChrisPriceAB, 15:17:27) * consensus would indicate a mailing list alias called opnfv-user would seem to be the best approach (ChrisPriceAB, 15:18:30) * ACTION: create a mailing list called “opnfv-user” (rpaik, 15:18:36) * support offered for OPNFV is community support, with no sla's associated. (ChrisPriceAB, 15:18:56) * use Jira to report bugs (rpaik, 15:21:12) * establishing an ask-bot to the users mailing list could be a valuable addition in the future. (ChrisPriceAB, 15:25:14) * WiKi structure & Layout (ChrisPriceAB, 15:25:33) * dneary raises the point that a community manager for OPNFV would be able to handle many of these issues (ChrisPriceAB, 15:28:49) * I agree with dneary, community management is a full time job and we'll need a dedicated person to do the job (RayNugent, 15:30:01) * Development process/project categories (ChrisPriceAB, 15:30:13) * cdub thinks the process may need review, preferably done after the release. (ChrisPriceAB, 15:32:34) * dlenrow indicates some additional work could improve the way the projects integrate with the overall OPNFV project (ChrisPriceAB, 15:34:13) * AGREED: to postpone the discussion until after Arno is released (ChrisPriceAB, 15:34:43) * OPNFV Release 2 "marquee feature" discussion (ChrisPriceAB, 15:35:45) * Ray indicates some concern that focusing on a feature a thematic approach may be better. (ChrisPriceAB, 15:37:48) * of the topics under discussion dneary describes SFC as a theme due to it's functional breadth (ChrisPriceAB, 15:39:02) * uli-k states that the value of OPNFV can be easily identified when considering a feature set that combines a number of upstream components (ChrisPriceAB, 15:40:59) * Rajeev indicates that a clear definition of what we are trying to achieve with the marquee feature is required (ChrisPriceAB, 15:42:20) * from the link https://www.opnfv.org/about, carrier-grade is OPNFV's one of targets "OPNFV will establish a carrier-grade, integrated, open source reference platform that industry peers will build together to advance the evolution of NFV and to ensure consistency, performance and interoperability among multiple open source components" (julien_ZTE, 15:50:39) * rpaik please add carrier grade as a suggestion (RayNugent, 15:53:34) * discussion that SFC and Faulat mgmt/HA maybe achievable in 6 months. Will need more time for Policy (rpaik, 15:53:40) * Release 2 planning (ChrisPriceAB, 15:53:47) * SFC+HA=carrier grade phase 1 (RayNugent, 15:54:19) * LINK: https://wiki.opnfv.org/simultaneous_release_process_and_guidelines wiki page for simultaneous release process (rpaik, 15:56:09) * can we output a schedule like openstack, https://wiki.openstack.org/wiki/Liberty_Release_Schedule (julien_ZTE, 15:57:11) * ACTION: Debra to initiate the development of the release plan for release 2 (ChrisPriceAB, 15:57:25) * dlenrow and uli-k to head up the community team (ChrisPriceAB, 15:57:45) * julian_ZTE agree with schedule proposal (RayNugent, 15:58:07) * AOB (ChrisPriceAB, 15:58:11) Meeting ended at 15:58:31 UTC. People present (lines said) --------------------------- * ChrisPriceAB (64) * dneary (33) * bryan_att (12) * RayNugent (12) * tnadeau (11) * rpaik (11) * fdegir (10) * dlenrow (8) * collabot (7) * julien_ZTE (7) * uli-k (7) * cdub (5) * morgan_orange (3) * dku (3) * tapio__ (3) * frankbrockners (2) * Tapio_ta (1) * ildikov (1) * cgoncalves (1) * rajeev (1) * hui (1) * ljlamers (1) * HKirksey (1) * Wenjing (1) * rprakash (1) Generated by `MeetBot`_ 0.1.4