14:01:41 #startmeeting OPNFV TSC call 14:01:41 Meeting started Tue Mar 17 14:01:41 2015 UTC. The chair is rpaik. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:41 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:01:41 The meeting name has been set to 'opnfv_tsc_call' 14:01:42 frankbrockners: Error: Can't start another meeting, one is in progress. Use #endmeeting first. 14:01:55 #info Gerald Kunzmann (DOCOMO) 14:02:02 #info Uli Kleber 14:02:13 #chair frankbrockners 14:02:13 Current chairs: frankbrockners rpaik 14:02:30 #info Pierre Lynch 14:02:40 #info Frank Brockners 14:02:46 #info Dirk Kutscher 14:03:28 #info Heather Kirksey 14:04:39 #info Tapio Tallgren (Nokia) 14:04:52 #info Wenjing 14:05:19 #info previous minutes approved 14:08:20 #info Prathima from LF introduced the OPNFV Ambassadors program for technical speaking opportunities 14:09:46 can we have the email address;s 14:09:58 #info similar program has been very successful in OpenDaylight. If you are interested in participating, please send an email to Prathima. A mailing list will be created and we can help with the presentation materials. 14:10:36 #action Prathima/Ray: post the relevant info on the wiki 14:11:05 #info emails: pramesh@linuxfoundation.org & rpaik@linuxfoundation.org 14:11:24 #info Parviz Yegani 14:13:06 my question is: will the ambassador program help also if we already have an opportunity, so we can speak o behalf of ONNFV 14:14:36 #info question is if there is a process for getting contents approved. 14:15:29 #info Prathima replied that she will come up with a more structured proposals in a few weeks 14:16:02 #info Heather added that this is not just for TSC reps, but everyone in the technical community 14:16:56 #info Brandon provided a mkt committee update 14:17:30 #info A succcessful MWC (power hour presentation + reception) 14:18:36 #info Powerhour video will also be posted along with a blog post recapping MWC activities 14:19:52 #info Release 1 campaign in the works (e.g. top level messaging, internal FAQ, release diagram, press briefings, etc.) 14:20:57 #info upcoming events: NFV World Congress (May) now in the process of identifying speakers 14:22:23 #info can send questions to bwick@linuxfoundation.org 14:23:41 #info Open Netowrking Summit (June): tutorial + dev track. In process of identifying speakers 14:24:14 14-18 June - ONS Summit - http://www.opennetsummit.org/ 14:24:20 #info Open Daylight Summit (July): Speakerships + co-located Hackfests 14:24:25 5-7 May 2015, San Jose, CA - NFV World Congress - http://www.layer123.com/nfv 14:24:42 #info 5-7 May 2015, San Jose, CA - NFV World Congress - http://www.layer123.com/nfv 14:24:53 #info 14-18 June - ONS Summit - http://www.opennetsummit.org/ 14:25:21 #info 18-22 May 2015 - Vancouver, Canada - OpenStack Summit - https://www.openstack.org/ 14:26:05 #info Are summary of events available? 14:26:55 rpaik: https://wiki.opnfv.org/#community_events 14:29:08 #action Ray/Brandon: investigate where we can post event information on the wiki 14:29:21 starting with MWC 14:31:35 #info having these information available is helpful for community building 14:32:05 #info Konstantin reports that all hardware has been racked 14:32:28 #info there is a mailing list for infra discussion 14:33:10 #info leads for Pharos, Functest, and BGS needs to be on the mailing list 14:33:59 #info suggestion is to send an email to opnfv-tech-discuss to setup a meeting 14:35:39 #action Ray to send an email and target a meeting on Thursday (incl. Aric & Konstatin) 14:37:12 where’s the link? 14:37:49 #info HW_Front https://dl.dropboxusercontent.com/u/12773330/opnfv_hw_pics/OPNFVHardwareFront.jpg 14:38:06 #info HW_Rear https://dl.dropboxusercontent.com/u/12773330/opnfv_hw_pics/OPNFVHardwareRear.png 14:38:29 nice! 12 cisco UCS blades… 14:39:02 #info Heather provided an update on OpenStack Summit. Now the proposal is to have an OPNFV Day on Monday. And participate in Telco WG Design Summit Wed/Thur (where blueprints will be discussed) 14:39:43 #info Plus an OPNFV reception on Monday evening after the booth crawl 14:41:56 #info On Monday, we have a room after keynote is over until 6pm. More direct upstream engagement (vs. a traditional hackfest). How do we organize the day so that it is productive/useful? 14:43:51 #link https://etherpad.opnfv.org/p/Vancouver_OpenStack 14:46:36 #info Ray will also have invitation letter information available 14:47:25 #info Heather will add information on conference passes on etherpad 14:48:09 we should have some logo pin or stickers 14:48:21 22:47 #info Heather will add information on conference passes on etherpad 14:48:28 when we go to a conference we can put these on our lanyards 14:48:37 sorry mistake 14:48:54 thoughts? 14:50:10 #topic release names - rivers 14:50:40 Winner over what option? 14:50:43 what was the second runner up? 14:50:52 avon 14:50:57 and what was the first? 14:51:01 how do you spell it? 14:51:01 Arno 14:51:04 arno! 14:51:10 #info Ray shared that Arno is the name for Release 1 14:51:29 In Florence 14:51:38 avon is a brand 14:51:43 so it's good arno won 14:51:58 I think the "pick 5 options" made it harder - if everyone chose Arno and Avon as viable names, they're of course neck & neck 14:52:12 Avon isn't a brand in SDN though :-) 14:52:22 Trademarks aredomain specific 14:52:33 #info Fatih gave an update on dev tools training 14:52:46 Avon would have allowed a Shakespeare theme 14:53:48 #info presentation material in place. also includes OPNFV workflow discussion 14:54:42 #info session maybe ~2 hours long 14:56:14 #info Frank suggests 2 separate sessions for multiple timezones 14:56:42 To virtualize or not...that is the question 14:57:40 #link http://docs.openstack.org/icehouse/training-guides/content/ for reference 14:57:55 #action Ray/Fatih/Iben/Aric to announce schedule to mailing lists 14:58:39 any suggestion for a file name in each repo that new contributors modify as part of the training? 14:58:51 #info Iben is working on developing training content based on recordings 14:58:55 (add your name to the file and a few goals, submit for review etc) 15:01:26 Etherpad on training for the interested https://etherpad.opnfv.org/p/tools_training 15:01:30 #info Suggestion is to have 3 parts in one go in a training session; General OPNFV Developer Tool Info, OPNFV Developer Workflow, and live Hands on session 15:02:36 will dial back in 15:03:00 frankbrockners, We did hear you, but it seems like there's a big lag 15:03:35 Is this call 1h or 2h? 15:03:56 dneary: 2h 15:04:22 Thanks aricg 15:06:14 #info Ray reminds eeryone not to use release names in the codebase (file name is OK) 15:07:08 frankbrockners, We hear you 15:08:09 frankbrockners, Sorry, I couldn't go to BGS meeting yesterday 15:08:22 #topic project plans & tracking 15:09:37 #info Foreman team maybe able to provide HA. Cannonical team will start working on juju path 15:10:53 #info BGS project is working on defining the commonalities across the final system states after the multiple installers 15:11:03 #info Frank recommends having system states better defined in the wiki 15:11:09 #chair dneary 15:11:09 Current chairs: dneary frankbrockners rpaik 15:11:09 #info Another collaboration area is a shared test suite to run on the platform 15:11:15 Thanks rpaik 15:11:24 I think the infos still work 15:11:45 what is the call after this one? 15:13:51 #info Uli provided update on Octopus. Reviewed scripts from the Fuel team yesterday. Looking forward to running in Jenkins after issues are worked out 15:13:53 * dneary does not know 15:17:11 #info Trevor provided Functest update. Communicating with Palani if he’s still interested in being a project lead. Coordination with Ci & BGS teams are needed 15:18:00 got dropped from the call. 15:18:43 #info Uli suggests having a rep from Octopus join the Testing team meeting on Thursday 15:22:23 the test vm should be built as part of the ci 15:22:41 but it would be part of another project like functest 15:22:51 #action Trevor to send a wiki link so that people can provide feedback 15:24:49 #info Iben gave an update on documentation. Training will cover documentation process. 15:28:55 #info git will be used for documentation 15:29:21 #info I suggest a tool for markdown, MOU. It's easy to use and learn. 15:29:40 #link https://wiki.openstack.org/wiki/Documentation/HowTo 15:35:57 #info There are two expertise. One to write the documentation for release 1 and the other is to establish a documentation process 15:41:52 #info iben can you include me in your invite 15:42:13 #action Iben to schedule a meeting with Bryan and others to walk through the potential process 15:43:43 Hmmm 15:43:49 #info tool like Word does not support version control 15:43:54 Anyone who can write a Word doc can write plain text 15:44:06 #agreed 15:44:12 +1 15:44:39 julien_ZTE, Word does have version control internally (if it's enabled and people use it, you can record changes and save versions 15:45:20 plain text cannot have figures etc included (except ascii art) 15:46:10 I would not use Word for version control (done that once) 15:46:50 depending on the number of authors. few authors word is great. many changes -> it becomes a mess 15:46:50 #info dneary, yes Word support internal control, but no tools can compare 2 different version of it. 15:49:01 tapio__, I agree 15:49:17 For sure, the best approach is version control with plain text 15:49:35 #topic project proposal review VIM Northbound Model and Interface 15:49:48 word can compare versions: http://support.microsoft.com/en-us/kb/306484 15:50:07 #info Tianran Zhou (Huawei) presenting the proposal 15:52:50 #info goal is to provide consistent/intuitive northbound interfaces for VIM 16:02:07 #info Disuccsion on collaboation with ETSI NFV, scope, etc. may need to be discussed on a Thursday meeting. Schedule for another quick review at the next TSC call. 16:02:17 #info Louis Fourie 16:02:48 #stopmeeting 16:03:00 #endmeeting