14:00:19 #startmeeting OPNFV TSC 14:00:19 Meeting started Tue Apr 21 14:00:19 2015 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:00:19 The meeting name has been set to 'opnfv_tsc' 14:00:24 #topic roll call 14:00:32 #info Chris Price 14:00:35 #info Frank Brockners 14:00:39 #chair rpaik 14:00:39 Current chairs: ChrisPriceAB rpaik 14:00:39 #info Uli Kleber 14:00:50 * dneary here 14:00:51 #chair frankbrockners 14:00:51 Current chairs: ChrisPriceAB frankbrockners rpaik 14:00:57 #chair ulik 14:00:57 Current chairs: ChrisPriceAB frankbrockners rpaik ulik 14:01:02 #chair dneary 14:01:02 Current chairs: ChrisPriceAB dneary frankbrockners rpaik ulik 14:01:07 * ChrisPriceAB Hi dave 14:01:31 * ChrisPriceAB voluntary IRC chairpeople! 14:02:15 #info Dirk Kutscher 14:02:23 #info Julien 14:02:28 #info Tapio Tallgren 14:02:37 #info Rajeev Koodli 14:02:45 #info Wenjing Chu 14:02:54 #info Andrea Pinnola 14:03:24 #topic approval of previous minutes of meeting 14:03:25 #info dlenrow 14:03:43 #agree previous minutes of meeting approved 14:03:48 #topic Agenda Bashing 14:03:59 #info Bryan Sullivan 14:04:20 #info hui 14:05:02 #info Bryan Sullivan 14:05:16 #info rpaik introduces rajeev 14:05:44 #topic Introducing Raveej Koodli, Intel TSC representative 14:06:32 #topic Arno Project plans & tracking 14:06:56 #link https://wiki.opnfv.org/get_started/get_started_release_plan#arno_release_readiness_-_status_summary 14:07:17 #info BGS aggregated all information regarding the release flow in the above link 14:07:51 #info ISO images are ready, not deployed in an automated way, hardware configuration not yet complete, documentation not yet complete. 14:08:24 #info BGS daily meeting to update the table and iterate through activities. 14:09:26 ChrisPriceAB, cdub let me know he won't be able to attend the meeting today - I am proxying for him 14:09:26 #info frankbrockners, where can I find the documents for review? 14:09:27 #info Octopus readiness report 14:09:34 * ChrisPriceAB thanks dneary, # in 14:09:51 #info dneary proxying for Chris Wright 14:09:51 ChrisPriceAB: dneary == RH proxy 14:09:55 #info documentation is ready and scraped to the WiKi for octopus 14:10:30 #info octopus readiness pending configuration of hardware in the LF labs 14:10:43 julien_ZTE: See the genesis repo - for example https://git.opnfv.org/cgit/genesis/tree/fuel/docs/src 14:10:51 #info CI scripting for testing not yet confirmed ready 14:11:37 frankbrockners, 3x 14:11:51 #info Pharos generic architecture description is ready. 14:12:04 #info LF lab specifics documentation is ongoing. 14:12:40 #info pending update from functest 14:13:03 #info opnfvdocs release readiness status report 14:13:19 #info toolchain, many under review documents 14:13:47 #info final release structure yet to be completed. 14:14:28 where are docs? 14:14:57 http://artifacts.opnfv.org/ should have everthing that is built daily. 14:15:38 http://artifacts.opnfv.org/opnfvdocs/docs/enable_docu_gen.html 14:15:47 #action opnfvdocs to construct a consolidated presentation of release documentation. 14:16:16 ChrisPriceAB, Could you #link the link to where docs are in Gerrit please? 14:16:33 these are mostly in patches for sub projects 14:17:05 #link https://wiki.opnfv.org/documentation opnfv docs overview page 14:19:18 #link http://artifacts.opnfv.org/ everything is there, but you have to search on the page for docutments. 14:19:59 #info Release readiness discussion 14:20:51 #info the hardware is 4 weeks delayed and we continue to run into issues as we try to move forward with the Arno release 14:24:00 #info configuration of the hardware is ongoing. May be able to conclude the basic set-up today. 14:24:39 #info A reasonable approach may be to set a date of one week after we have succesfull manual deployments 14:26:12 Is this hardware availability a prerequisite for launch? 14:26:32 yes we have defined the release gate as being able to deploy to the OPNFV infrastructure 14:27:16 Specifically the Linux Foundation hardware? 14:27:36 Our LF hosted OPNFV hardware. 14:27:50 OK 14:30:46 Will putting a Device Connectlogate on the release, such that it has to be deployable on LF hardware, really add any value at this point? It seems we still have distinct install experiences anyway. I would say that successful install on one of the Foreman or Fuel pods is success for R1. 14:31:17 (sorry...) Will putting a gate on the release, such that it has to be deployable on LF hardware, really add any value at this point? It seems we still have distinct install experiences anyway. I would say that successful install on one of the Foreman or Fuel pods is success for R1. 14:31:48 #info we also need clarity on Functest status 14:36:02 #info Release decision for April 23rd 14:36:25 #agree We will not be able to release on the 23rd of Arpil 14:36:42 #info Parviz 14:38:54 #info frankbrockners indicates setting a release date can be a twice weekly discussion until we are able to confirm a target date. 14:50:10 #agree Arno project leads will construct a plan leading up to Thursday where the TSC will reconvene and provide a determinism on the Arno target release date. 14:50:27 #action Arno project leads to craft a concise plan of action for Arno 14:50:59 #action Chris Price to call for a TSC call to review the plan and agree on a target date. 14:51:28 This may be a stupid question, but does BGS or any other project need some more hands (new hands) over the next few days? Is there a resource issue? 14:52:30 I would say jump on IRC, octopus, bgs, meeting. Follow the traffic and jump on activities that you can help with. 14:53:32 "ships in the night" can still take you to the same place 14:54:10 isn't that the goal? that in the end we have the same capabilities. if we get there via different paths IMO that's the same destination. 14:55:13 i would say NO 14:55:39 functional equivalence should be the goal - not detailed installed state equivalence 14:56:21 we have known for at least 2 months that we cannot reach a single end-state e.g. the ODL/docker issue 14:59:28 #info frankbrockners adds that both Fuel & Foreman are in similar stages in terms of deployment 15:05:08 #topic Arno marketing/messaging update 15:06:14 #info Heather indicates the marketing team will have some work to do now that the date has slipped pending a TSC decision on when we will be able to communicate around that. 15:06:41 #info changes were made to the messaging based on community discussion 15:09:10 #topic OpenStack Summit discussion 15:09:55 #info heather asks for feedback on the set-up at the OpenStack summit meetings 15:10:31 "info the proposal is to use a fishbowl style set-up in the morning. In the afternoon to use a smaller breakout style set-up to focus on specific topics. 15:11:04 #info the proposal is to use a fishbowl style set-up in the morning. In the afternoon to use a smaller breakout style set-up to focus on specific topics. 15:11:04 etherpad link for OpenStack? 15:11:12 https://etherpad.opnfv.org/p/Vancouver_OpenStack 15:11:36 #link https://etherpad.opnfv.org/p/Vancouver_OpenStack openstack etherpad for planning 15:11:58 #link https://etherpad.opnfv.org/p/Vancouver_OpenStack 15:15:02 I had provided some input to the etherpad before - looks like it got lost somehow 15:15:21 * ChrisPriceAB the problem with etherpad.... 15:17:16 #topic Open Access update 15:17:33 Having multiple discussions, the main topic I think might need concerted effort around the Summit is IPv6 15:17:35 #info Jira is now open to the public. 15:17:45 s/Having/Based on/ 15:18:07 #info Gerrit will be set to open after Arno is released to save any collateral interruptions. 15:18:35 #topic Updating Section 7 of TSC Charter: Ray 15:18:59 #link https://www.opnfv.org/developers/technical-project-governance/tsc-charter TSC charter 15:22:06 Robert's Rules of Order defines a majority as being more than one half of the votes cast including votes for ineligible candidates or choices. 15:24:09 Need whole TSC to define majority? 15:25:00 * dneary would be happy to defer to Merriam-Webster 15:25:30 Dneary:+1 15:28:30 yeah, not going to happen. 15:29:17 #topic project reviews 15:29:33 #topic Creation review of Multisite Virtualized Infrastructure 15:29:58 #link https://wiki.opnfv.org/requirements_projects/multisite project propsal for multisite 15:32:59 #info the multisite project is proposed based on the ETSI NFV phase 1 work. 15:33:32 #info the team identify needs in upstream communities to enable this functionality which are intended to be addressed in the requirements project. 15:36:11 #info Parvis asks if there are dependencies on the movie project 15:36:30 #info Howard responds that none have been identified, however the projects will coordinate to ensure these are captured. 15:38:01 #info Howard identifies that Neutron and Keystone are the likely first areas of focus 15:43:55 #startvote TSC to vote to create the project multisite? (+1, 0, -1) 15:43:55 Begin voting on: TSC to vote to create the project multisite? Valid vote options are , +1, 0, -1, . 15:43:55 Vote using '#vote OPTION'. Only your last vote counts. 15:44:00 #vote +1 15:44:02 #vote +1 15:44:03 #vote +1 15:44:05 #vote +1 15:44:05 #vote +1 15:44:07 #vote +1 15:44:10 #vote +1 15:44:14 #vote +1 15:44:14 #vote +1 15:44:18 #vote +1 15:44:30 #vote +1 15:44:31 #vote +1 15:44:37 ChrisPriceAB, Who are you calling simple? 15:44:38 #endvote 15:44:38 Voted on "TSC to vote to create the project multisite?" Results are 15:44:38 +1 (12): AndreaP, dneary, dku, dlenrow, frankbrockners, bryan_att, julien_ZTE, ChrisPriceAB, hui, Tapio_T, rajeev_, ulik 15:44:48 ChrisPriceAB, sorry I lost the link 15:46:29 #topic Creation review of Escalator project 15:46:47 #link https://wiki.opnfv.org/requirements_projects/escalator project proposal for the escalator project 15:47:05 * ChrisPriceAB I like the icon :D 15:49:07 ChrisPriceAB: if the upgrade is via things deployed on ONOS/ODL, then a roll back is just redeploy the previous version 15:49:15 * icbts thanks OSGi for making that easy 15:49:26 #info The escalator project intends to address the needs of operators for system upgrade 15:50:06 * icbts deploy kars on docker image 15:50:26 :) yes we need a complete system view of this. ODL thankfully at least makes this easy. 15:52:46 ChrisPriceAB: you may want to take a gander at https://github.com/apache/karaf-decanter - we’ll have that properly in karaf shortly - that way you can monitor your ONOS or ODL controllers (i know only a small part of the overall architecture) 15:54:25 #info Jie indicates that upgrade is a common issue and developing some specific requirements and motivating them upstream can help the overall system 15:54:42 #info prakash asks if this project is specific to the control plane 15:55:14 #info Jie answers that the project intends to address the platform (infrastructure piece) and not on the VNF. 15:58:00 #info ulik describes that the specific requirements on upstream components depends on the way those components are used and the project will address the needs independantly. 15:59:42 #startvote TSC vote to create the escalator project? (+1, 0, -1) 15:59:42 Begin voting on: TSC vote to create the escalator project? Valid vote options are , +1, 0, -1, . 15:59:42 Vote using '#vote OPTION'. Only your last vote counts. 15:59:46 #vote +1 15:59:48 #vote +1 15:59:48 #vote +1 15:59:48 #vote +1 15:59:49 #vote +1 15:59:51 #vote +1 15:59:52 #vote +1 15:59:52 #vote +1 15:59:54 #vote +1 15:59:54 #vote +1 15:59:58 #vote +1 16:00:00 #vote +1 16:00:17 #endvote 16:00:17 Voted on "TSC vote to create the escalator project?" Results are 16:00:17 +1 (12): AndreaP, dneary, rajeev_, dlenrow, frankbrockners, bryan_att, ChrisPriceAB, hui, Tapio_T, julien_ZTE, Parviz, ulik 16:01:18 Are we doing a BGS checkin now? 16:01:27 #endmeeting