========================= #opnfv-meeting: OPNFV TSC ========================= Meeting started by ChrisPriceAB at 15:00:03 UTC. The full logs are available at http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-02-23-15.00.log.html . Meeting summary --------------- * Roll Call (ChrisPriceAB, 15:00:12) * Chris Price (ChrisPriceAB, 15:00:19) * Dirk Kutscher (dku, 15:00:39) * Juha Oravainen (proxy for Tapio Tallgren) (JuhaOravainen, 15:00:59) * Morgan Richomme (IRC) (morgan_orange, 15:01:21) * Uli (uli-k_, 15:01:29) * Parviz Yegani (Parviz, 15:01:48) * Brian Skerry (bjskerry, 15:01:48) * Narinder Gupta (narindergupta, 15:02:18) * Approval of previous minutes of meeting (ChrisPriceAB, 15:02:42) * LINK: https://wiki.opnfv.org/wiki/tsc#february_16_2016 previous TSC minutes (ChrisPriceAB, 15:02:48) * no feedback was received minutes approved. (ChrisPriceAB, 15:03:08) * Agenda Bashing (ChrisPriceAB, 15:03:18) * Gerald Kunzmann (GeraldK, 15:03:18) * bryan sullivan (bryan_att, 15:03:19) * Frank Brockners (frankbrockners, 15:03:29) * LINK: https://wiki.opnfv.org/wiki/tsc#february_23_2016 current agenda for today (ChrisPriceAB, 15:03:39) * rpaik raises the need to discuss release artifacts and release pages (ChrisPriceAB, 15:05:11) * geraldk would like to discus projects that did not make the release. (ChrisPriceAB, 15:05:26) * these topics will be captured in the Brahmaputra discussion (ChrisPriceAB, 15:06:13) * Julien (Julien-zte, 15:06:21) * Brahmaputra release update (ChrisPriceAB, 15:06:24) * LINK: https://wiki.opnfv.org/releases/brahmaputra/daily_status (debrascott, 15:06:40) * the following scenario's are ready for release: apex/odl_l2 - compass/odl_l2 - compass/onos - compass-nosdn - fuel/nosdn - fuel/old_l2 - fuel/onos (ChrisPriceAB, 15:07:09) * projects that do not yet have a stable scenario include: NFVOVS, KVM4NFV, SFC, BGP-VPN, Doctor (ChrisPriceAB, 15:08:15) * ebrjohn Brady Johnson, SFC (ebrjohn, 15:08:15) * Jonas Bjurel ([1]JonasB, 15:08:46) * Joid deploy has achieved stability for odl_l2 and nosdn (ChrisPriceAB, 15:09:24) * stability runs are ongoing in preparation for release on Thursday (ChrisPriceAB, 15:09:40) * dneary (dneary, 15:09:49) * ghall ( proxy Tom Nadeau ) (ghall, 15:10:10) * trevor_intel (trevor_intel_, 15:10:34) * Doctor is being deployed on apex/odl_l2 (ChrisPriceAB, 15:12:14) * as of et there have not been 4 successful runs verifying the doctor functionality. (ChrisPriceAB, 15:12:33) * discussion that scenarios like Apex/ONOS and Apex/ODL-L3 are deploying successfully but have known limitations (rpaik, 15:22:39) * concensus that these scenarios could be released with issues documented (rpaik, 15:24:28) * LINK: http://artifacts.opnfv.org/opnfvdocs/review/10487/configguide/configoptions.html#opnfv-scenario-s scenario matrix patch (ChrisPriceAB, 15:30:32) * AGREED: the TSC agree that scenario's which have known limitations can be released with the limitations documented for Thursday. The scenario's need to be stable and reproducable. (ChrisPriceAB, 15:46:38) * ACTION: ChrisPriceAB and opnfvdocs team to work with the deploy and test teams to clarify and fully document the state of each scenario according to the above agreement. (ChrisPriceAB, 15:53:39) * ACTION: debra, aricg and the octopus team to ensure the release tagging process is well understood for the project leads. Tagging must be done by Wednesday for all projects. (ChrisPriceAB, 15:59:10) * Brahmaputra release and artifact handling (ChrisPriceAB, 15:59:53) * LINK: https://www.opnfv.org/software/download current software downloads page (rpaik, 16:00:06) * updates will be made to the software downloads page (ChrisPriceAB, 16:00:13) * on the main dowwnloads page there will be links to each deploy tool (ChrisPriceAB, 16:01:24) * the link will take users to the download page including documentations for each deploy tool. (ChrisPriceAB, 16:01:42) * LINK: https://wiki.opnfv.org/releases/brahmaputra/releasedocs docs wiki (rpaik, 16:01:51) * the main downloads page will also contain direct links the composite docs and a link to the release documentation page which will contain all project documentation. (ChrisPriceAB, 16:02:35) * AoB Brahmaputra (ChrisPriceAB, 16:04:02) * Heather asks what terminology we would want to use for our release iterations. (ChrisPriceAB, 16:04:39) * frankbrockers indicates "release additions" would be a good convention (ChrisPriceAB, 16:05:49) * Feature Release? (RayNugent_, 16:12:36) * C Release planning and discussion. (ChrisPriceAB, 16:12:50) * ACTION: rpaik to start a mailing list coversation on the C-release naming (rpaik, 16:15:51) * LINK: https://etherpad.opnfv.org/p/c-release-brainstorming (fdegir, 16:16:49) * LINK: https://etherpad.opnfv.org/p/c-release-brainstorming c release brainstorming etherpad (ChrisPriceAB, 16:17:13) * agree with Daniel, I suggest to reduce the test cases which cost too much resources including CI hardware resources (Julien-zte, 16:20:32) * debrascott notes back-end resource issues (e.g. for testing, documentation, CI, etc.) (rpaik, 16:20:37) * currently there are 23 scenarios, but only fewer can be released in B (Julien-zte, 16:22:58) * dan outlines that pharos and reosurce management is a key area to improve for C-Release (ChrisPriceAB, 16:32:26) * discussion on resource issues for Pharos, install teams, etc. (rpaik, 16:32:51) * Debra identifies that we need to identify how many new projects will be involved and what impact this will have on integration, test & infra (ChrisPriceAB, 16:34:37) * Debra suggest trade-off between scope and more resources. the challenge is that there are several types of installers which will cost each project team more resources to be integrated (Julien-zte, 16:36:30) * LINK: https://etherpad.opnfv.org/p/Q1'2016_Hackfest ([1]JonasB, 16:39:53) * +1 on Dan's idea that we identify content early on so we can do reasonable resource mapping and communicate to installers and test what the workload will be. (RayNugent_, 16:40:08) * radez adds that shifting requirements late in the Brahmaputra release cycle was also a challenge (rpaik, 16:41:54) * inparticular, scheduling a requirements freeze of some sort early on in the release cycle (radez, 16:42:39) * dneary agrees with DanSmithEricsson that the community is setup to provide adequate support (rpaik, 16:45:07) * dneary agrees with DanSmithEricsson that the community is not set up to provide adequate support across multiple versions of upstream projects (dneary, 16:52:39) * +1 with ildikov for reference platform (Julien-zte, 17:01:21) Meeting ended at 17:02:42 UTC. Action items, by person ----------------------- * ChrisPriceAB * ChrisPriceAB and opnfvdocs team to work with the deploy and test teams to clarify and fully document the state of each scenario according to the above agreement. * rpaik * rpaik to start a mailing list coversation on the C-release naming People present (lines said) --------------------------- * ChrisPriceAB (39) * rpaik (11) * DanSmithEricsson (9) * dneary (7) * [1]JonasB (7) * Julien-zte (5) * collabot` (4) * debrascott (4) * bryan_att (3) * ildikov (3) * RayNugent_ (3) * GeraldK (2) * ashyoung_ (2) * fdegir (2) * radez (1) * narindergupta (1) * bjskerry (1) * morgan_orange (1) * frankbrockners (1) * ghall (1) * uli-k_ (1) * trevor_intel_ (1) * JuhaOravainen (1) * Parviz (1) * ebrjohn (1) * dku (1) * jose_lausuch (1) Generated by `MeetBot`_ 0.1.4