13:54:30 #startmeeting OPNFV TSC 13:54:30 Meeting started Tue May 19 13:54:30 2015 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:54:30 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:54:30 The meeting name has been set to 'opnfv_tsc' 13:54:38 #topic roll call 13:54:50 #info Chris Price 13:58:47 Please # in for those on IRC 13:59:49 #info Frank Brockners 14:00:47 #info Tapio Tallgren 14:01:03 #info Gerald Kunzmann (DOCOMO) 14:02:23 #info Carlos Goncalves 14:03:08 #info Trevor Cooper 14:04:25 #info Rajeev Koodli 14:06:42 #topic Approve previous minutes 14:07:01 #agree Previous minutes Approved 14:07:07 #topic Agenda Bashing 14:08:02 #info Bryan Sullivan 14:09:48 * ChrisPriceAB we have lost audio in the room. 14:10:00 #chair rpaik 14:10:00 Current chairs: ChrisPriceAB rpaik 14:11:37 #topic OPNFV Release Manager role & update 14:11:55 #chair frankbrockners 14:11:55 Current chairs: ChrisPriceAB frankbrockners rpaik 14:12:13 Can anybody pass the number to call in? Tried # is 626 521 0010 but it's not working 14:12:37 #info Heather mentions that we hired a new release manager who will start on June 1st 14:13:18 #info she will start helping us with Release 2 planning 14:13:20 #info Larry Lamers 14:13:22 #info Uli Kleber 14:13:40 #topic OPNFV Day @ OpenStack overview 14:14:10 #info dneary (proxy for cdub) 14:14:26 #info huge audience and interest in OPNFV day 14:15:03 #info Heather noted that email was sent out with recommended sessions at OpenStack Summit on Sunday 14:15:16 #link https://etherpad.opnfv.org/p/Vancouver_OpenStack 14:15:32 ChrisPriceAB, Is that the link you were looking for? 14:15:54 #info plan is to also participate as a commuity at OpenStack Tokyo 14:16:39 #link OpenStack Design Summit 101: https://libertydesignsummit.sched.org/event/e480edc1483038153cf2dcd99686686a#.VVtFvMuCnsw 14:16:51 #info previous topic (Debra Scott is the name of the Release Manager) 14:17:26 #topic Arno Project plans & tracking 14:17:32 #info Debra Scott: https://www.linkedin.com/in/debrascottpmp 14:19:20 #info opnfvdocs update 14:20:22 #info Chris updates that a lot of people are still heads down on Arno work and need to find time to edit documentation 14:20:41 #info opnfv docs is approaching readiness, the remaining work is required by the same resources performing other activities in the projects 14:22:43 #info Chris asks for community to help with reviewing documents 14:24:25 #link https://wiki.opnfv.org/documentation/Arno Arno documentation references for all release docs 14:24:32 I could call in finally 14:26:24 #action ChrisPriceAB to send a mail to the tech discuss list to request help with reviewing documentation. 14:27:36 #info Octopus update 14:28:06 #info nothing to report 14:28:19 #info release ready 14:31:25 #info BGS update 14:31:36 #undo 14:31:36 Removing item from minutes: 14:32:26 #info pharos update 14:32:57 #info Pharos Arno docs still under review 14:33:17 #info haros project is in a ready state apart from needing to complete the documentation 14:33:21 #undo 14:33:21 Removing item from minutes: 14:33:29 O_o 14:33:33 #info Pharos project is in a ready state apart from needing to complete the documentation 14:33:57 #info funcest update 14:34:01 #undo 14:34:01 Removing item from minutes: 14:34:05 #info functest update 14:34:12 #info https://wiki.opnfv.org/opnfv_functional_testing#testcases_follow-up 14:36:56 #info transient failures usually take some time to debug 14:37:16 #info BGS update 14:37:17 #info updates on BGS 14:37:21 #undo 14:37:21 Removing item from minutes: 14:37:28 #info https://wiki.opnfv.org/meetings/bgs?&#may182015 14:38:39 #info frankbrockners mentioned that autodeploy on both PODs are green 14:40:47 #info still need ISO that boots 14:43:46 #info see test cases 1-3 on link above from frankbrockners (these are critical tests failures that need to be addressed) 14:47:45 #link artifacts.opnfv.org 14:49:54 #info BGS feels release cannot be done before June 4 14:52:33 I updated https://etherpad.opnfv.org/p/Vancouver_OpenStack with key design summit sessions (aggregation of end-of-week/weekend email 14:52:38 ) 14:52:59 Tomorrow from 9am to 10:30am is insane: 14:53:31 9 - 10:30am: Ops summit: Telco 14:54:20 9 - 9:40: Neutron Liberty development, 9:50 - 10:30: Neutron use-case discussion 14:55:01 9 - 9:40: Nova: Scheduler in Liberty, 9:50 - 10:30: Nova: Scaling out the scheduler for v2 Cells 14:55:25 All relevant to NFV and telco 14:56:02 I would suggest: engagement at a higher level on use-cases and needs: Telco WG session in Ops summit 14:57:19 #startvote Shall the TSC set an Arno release date of June 4th? (+1, 0, -1) 14:57:19 Begin voting on: Shall the TSC set an Arno release date of June 4th? Valid vote options are , +1, 0, -1, . 14:57:19 Vote using '#vote OPTION'. Only your last vote counts. 14:57:25 #vote +1 14:57:30 #vote +1 14:57:33 #vote +1 14:57:33 #vote +1 14:57:35 #vote +1 14:57:35 #vote +1 14:57:35 #vote +1 14:57:36 #vote +1 14:57:40 #vote +1 14:57:41 #vote +1 14:57:41 #info rpaik proxy for Bryan Sullivan 14:57:46 I think it's essentially arbitrary at this point 14:57:58 Anything we choose has a possibility of being wrong 14:58:07 Let's just put a line in the sand 14:58:14 @dave - your statement is true in general, right? *) 14:58:14 TomNadeau: Error: "dave" is not a valid command. 14:58:31 dave your statement is true in general, right? *) 14:58:36 #endvote 14:58:36 Voted on "Shall the TSC set an Arno release date of June 4th?" Results are 14:58:36 +1 (10): AndreaP, frankbrockners, dneary, cgoncalves, rajeev, ChrisPriceAB, Tapio_ta, Gerald_K, rpaik, TomNadeau 14:58:44 TomNadeau, Indeed 14:59:50 Just checking: Did we have a quorum? (Only 10 votes received) 15:00:12 frankbrockners, How many is a quorum? 15:00:25 not sure how many TSC members are here... 15:01:01 #info The TSC has agreed to set a release date of June 4th for the Arno release, the Arno team has approximately 2 weeks to complete release activity. 15:01:45 #topic Release 2 preparation and planning 15:03:22 #info Chris suggests having a post-mortem session after the Arno release 15:05:16 #info simultaneous release process needs to be defined and will be a learning prcess for the community 15:11:46 #info dneary outlines that system state definition will be important in release 2 15:14:04 RayNugent, I mentioned something that we can have as a headline feature 15:14:11 #info dneary adds that identifying a marquee feature or set of features for release 2 would be helpful 15:15:07 And as ChrisPriceAB said, I'd see it touching multiple upstream projects and multiple features 15:18:11 #info ideas for such marky features were discussed: 15:18:26 #info Carrier grade as an example 15:18:36 #info SFC as an example 15:19:41 -"àè-( 15:19:54 Ubikey - sorry 15:20:20 #info Security and Performance as example 15:20:52 #info suggestion for the community to think of other possible themes for Release 2 15:21:24 #info We should do some homework and think about this. 15:23:21 #info testing (performance, functional, etc.) is another possible topic 15:23:32 #topic TSC update to the Board 15:25:53 #info development process updates requiered 15:26:43 Wouldn't question of major themes/use-cases/characteristics for Rel 2.0 be something board should advise and make recommendations to TSC? 15:27:04 Make board aware of the search for a theme? 15:28:00 #info Project definitions and classification 15:29:50 #topic Project Review and approvals of the Inspector project 15:29:57 #link https://wiki.opnfv.org/requirements_projects/inspector 15:30:06 dlenrow raises a great point. We need a product management role to set the thematic goal of a release. Not sure the board can drive that 15:30:56 RayNugent, The board can make suggestions, of course, but there's a clear separation of powers - TSC sets the technical direction 15:31:50 Everyone in Vancouver: Just a reminder that the Telco Ops summit is 9-10:30, East building, meeting rooms 2-3 15:32:15 technical direction yes. Thematic content should be a product management function 15:33:17 #info Juan notes that other people (e.g. from Huawei) expressed interest in joining the Inspector project 15:34:20 #info suggestion to add contributors/committers to the project proposal 15:36:57 What does CADF mean? 15:37:46 And, in the context of Inspector, what does audit mean? What are you auditing, and to what end? 15:38:09 Sorry for the dumb questions... 15:40:11 #info rprakash is interested in joining as contributor if ONOS is included 15:40:17 CADF = http://www.dmtf.org/standards/cadf 15:40:55 yes, I agree the project could use help in providing a little more background/context 15:41:22 #info bryan_att says CADF = Cloud Audit Data Federation. http://www.dmtf.org/standards/cadf 15:42:48 #info will vote on the project proposal after committer/contributor list is updated (next week) 15:43:57 that was Mike Young on the phone 15:44:00 #info Mike Young (Huawei) is also interested in joining the project 15:45:06 ##action Juan to update the committer and contributor list for recking next week 15:45:58 #topic Project creation review Juju OPNFV Infrastructure Deployer 15:46:23 #link https://wiki.opnfv.org/project_proposals/joid JOID project proposal 15:50:21 did Mike Young mention if he wants to be a contributor or a commiter? Just to know where to add him 15:51:16 #info add David Karr (ATT) to the project 15:51:22 For AT&T, David Karr will contribute 15:53:23 As we get involved we will decide whether David needs to be a committer for Inspector 15:53:27 #info discussion on how BGS will be structured post Arno 16:00:08 #info discussion that we’re not making a decision on JOID being part of release 2 yet 16:00:42 #action Artur to update the committer/contributor list before approval next week 16:01:16 #action joid team to update the committer and contributor list 16:01:42 #endmeeting