15:00:51 <ChrisPriceAB> #startmeeting OPNFV TSC
15:00:52 <collabot`> Meeting started Thu Jan  8 15:00:51 2015 UTC.  The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:52 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:00:52 <collabot`> The meeting name has been set to 'opnfv_tsc'
15:00:59 <ChrisPriceAB> #topic TSC roll call
15:01:08 <GeraldK> #info Gerald Kunzmann (DOCOMO)
15:01:09 <ChrisPriceAB> #info Chris Price
15:01:19 <dku> #info Dirk Kutscher (NEC)
15:01:21 <frankbrockners> #info Frank Brockners
15:01:25 <uli__> will be a bit late in the audio
15:01:36 <rprakash__> OK
15:01:44 * ChrisPriceAB you can still # info in!
15:02:01 <fzdarsky> #info Frank Zdarsky (Red Hat)
15:02:10 <rpaik> #info Julien
15:02:12 <Parviz> #info Parviz Yegani
15:02:25 <uli__> #info Uli Kleber
15:02:49 <dlenrow> #info dlenrow
15:02:51 <rprakash__> #info Prakash
15:03:02 <bryan_att> #info Bryan Sullivan
15:03:33 <ChrisPriceAB> #topic Approval of minutes
15:04:02 <Pranav> #info Pranav Mehta
15:04:26 <ChrisPriceAB> #agree minutes approved.
15:04:28 <Wenjing> #info Wenjing Chu
15:04:35 <ChrisPriceAB> #topic Agenda Bashing
15:05:21 <rprakash__> #help minutes link?
15:05:25 <dlenrow> suggest topic Do we still need two hour TSC weekly by default?
15:05:49 <rpaik> minutes are posted on the wiki #link https://wiki.opnfv.org/wiki/tsc
15:07:39 <rprakash__> #topic OSCAR status?
15:08:09 <ChrisPriceAB> #info frankbrockners indicates meeting can finish earlier.
15:08:38 <ChrisPriceAB> #chair dlenrow
15:08:38 <collabot`> Current chairs: ChrisPriceAB dlenrow
15:08:43 <ChrisPriceAB> #chair dneary
15:08:43 <collabot`> Current chairs: ChrisPriceAB dlenrow dneary
15:08:49 <ChrisPriceAB> #chair frankbrckners
15:08:49 <collabot`> Warning: Nick not in channel: frankbrckners
15:08:49 <collabot`> Current chairs: ChrisPriceAB dlenrow dneary frankbrckners
15:08:53 <ChrisPriceAB> #chair frankbrockners
15:08:53 <collabot`> Current chairs: ChrisPriceAB dlenrow dneary frankbrckners frankbrockners
15:08:59 <dneary> Danke ChrisPriceAB!
15:09:02 <dlenrow> #info discussed and agreed two hour TSC still necessary by default
15:09:35 <rprakash__> #info  depending on topics we have can keep to 2 hrs or less
15:09:46 <ChrisPriceAB> #topic OpenStack community discussion
15:10:09 <ttx> fwiw I'm also around to represent OpenStack (Thierry Carrez, Openstack Technical committee chair)
15:10:41 <rprakash__> #info telcowg in openstack has not met as per my intercations  may be some one has beter info
15:10:59 <dneary> #info Introductions: Russell Bryant, OpenStack techncal committee member, looking into NFV as part of his OpenStack work
15:11:02 <rprakash__> #info I mean 2015
15:11:06 <dneary> rprakash__, They have a weekly meeting
15:11:14 <dneary> rprakash__, They met yesterday
15:11:16 <palani> #info palani
15:11:44 <rprakash__> #info Ok I missed it was to get the use case for MNO/MVNO added and will ersue next week
15:12:17 <dneary> #info Introductions: Jay Pipes, OpenStack TC member, working for Mirantis, former PTL, interested in avoiding duplication of effort & ensuring OpenStack and OPNFV work well together
15:12:24 <rprakash__> #info any updates on  yesterday meetings any links to share on summary?
15:12:43 <dneary> #info Introductions: Kyle Mestery, future Neutron PTL
15:13:16 <dneary> #info Introductions: Thierry Carrez, release manager for OpenStack, OpenStack TC chair
15:13:21 <dneary> Hi ttx
15:13:24 <ttx> dneary: o/
15:13:28 <russellb> ttx: thanks for coming
15:13:35 <dneary> rprakash__, Not really on topic for this topic in the meeting...
15:13:49 <rprakash__> #info any action items taken up in yesterdays telcowg?
15:15:27 <rprakash__> #info I don't see yet any 2015 meeting logs in telcowg
15:16:12 <dneary> rprakash__, They meet in #openstack-meeting, 4pm EST, 10pm CET. Last minutes: http://eavesdrop.openstack.org/meetings/telcowg/2015/telcowg.2015-01-07-22.00.html
15:16:12 <rprakash__> #link link: evesdrop.openstack.org/meetings/nfv/
15:16:32 <jaypipes> russellb: big ++
15:16:53 <dneary> rprakash__, And the Etherpad: https://etherpad.openstack.org/p/nfv-meeting-agenda
15:17:59 <dneary> rprakash__, Ah, there was a name change from nfv to telcowg after the summit
15:18:11 <dneary> Would explain why you missed recent minutes
15:18:26 <rprakash__> #info thanks its telcowg and not nfv I see details on zones etc - appreciate and any summay from attendees?
15:19:45 <GeraldK> rprakash__, the correct link would be eavesdrop.openstack.org/meetings/nfv/
15:21:02 <rprakash__> #info so the focus on telcowg was on Security Seggregation (Placement Zones)
15:21:10 <jaypipes> dneary: exactly. ++
15:22:27 <rprakash__> #info I will submit the MNO/MVNO use case by email to one of you from A&T who can update that on site?
15:24:24 <rprakash__> #info reason I may not be able to join next week but if there is a way to add and start debating will help in telcowg for as OPNFV will will need to bind Policys, users/tenant sructure etc. have several BPs impacting for k2/l.. in upstream
15:28:13 <rprakash__> #info going back on Security Seggregation why only L2 (VLAN) seggeration between MZ & DMZ , most designs or IPV6 L3 based any specific reason for that in use case presentaion
15:30:29 <dlenrow> based on my understanding of recent changes to OStack projects/status, community is currently figuring how to define certain projects level of maturity in general. I see OPNFV as being able o certify them as having a certain level of maturity  WRT NFV and NFV use cases.
15:31:00 <rprakash__> #info will add my inpus to DaSchad is he here?
15:33:18 <rprakash__> #help is there a goto meeting along with this or just IRC for today?
15:33:37 <frankbrockners> https://global.gotomeeting.com/join/798898261
15:34:12 <dlenrow> #info this is GTM meeting #798898261
15:34:42 <dlenrow> #info nobody presenting thus far on GTM
15:34:59 <ChrisPriceAB> #info Mike B asks how we can best manage end to end test/use cases when significant portions of these are built in upstream communities.  If the validation schema's are distributed it can be difficult to understand and troubleshoot these and manage the lifecycle of them.  (I think)
15:37:37 <ChrisPriceAB> #info Jay asks for a process overview of OpenStack methodologies in this area to help provide clarity around upstream processes in OpenStack for the OPNFV community.  (which will help answer the above question)
15:39:16 <jaypipes> #info Overview on release and planning: design summits every 6 months. It's a working event, usually 5 days, where specifications of proposed feature implementations are discussed/debated, and priorities for the next release cycle are agreed upon.
15:39:27 <jaypipes> #info Next design summit is in Vancouver in May
15:40:06 <jaypipes> #link Specifications targeted for Kilo that are approved for Nova: http://specs.openstack.org/openstack/nova-specs/specs/kilo/index.html
15:40:21 <jaypipes> #link Example NFV-related spec: http://specs.openstack.org/openstack/nova-specs/specs/kilo/approved/input-output-based-numa-scheduling.html
15:40:41 <ChrisPriceAB> #info OPNFV plans a technical event to coincide with the Vancouver OpenStack event to maximize collaborative dialogs across communities.
15:40:49 <ttx> #info OpenStack uses a time-based release cycle. Current one is named Kilo -- https://wiki.openstack.org/wiki/Kilo_Release_Schedule
15:41:02 <jaypipes> #link *Unapproved* specifications currently under review: https://review.openstack.org/#/q/status:open+project:openstack/nova-specs,n,z
15:41:16 <jaypipes> #info anyone can vote and comment on any spec (and we encourage lots of feedback)
15:42:13 <jaypipes> #info We are available on mailing list and #openstack-[nova|neutron|dev] IRC channels if you have any questions on our processes
15:43:06 <ChrisPriceAB> #info the prefix [NFV] is used in OpenStack to identify e-mail traffic intended to discuss NFV related topics (topic filtering is possible)
15:43:36 <rprakash__> #help do we mainatain logs of these meetings in opnfv?
15:43:49 * ChrisPriceAB yes
15:43:59 * ChrisPriceAB check minutes on the TSC page for each call
15:44:07 <rprakash__> #help where can I fiind that?
15:44:19 <rpaik> #link http://meetbot.opnfv.org/meetings/opnfv-meeting/
15:44:22 <rprakash__> #info thanks Chris
15:44:28 <ChrisPriceAB> #link https://wiki.opnfv.org/wiki/tsc
15:46:42 <jaypipes> #info Telco Working Group IRC meeting information: https://wiki.openstack.org/wiki/Meetings#Telco_Working_Group_Meeting
15:48:07 <ttx> Thanks +1
15:48:20 * ttx 's phone just died
15:49:02 <ChrisPriceAB> #topic Update on Bootstrap project
15:49:12 * ChrisPriceAB thanks ttx, appreciate it
15:49:24 <ChrisPriceAB> #link https://wiki.opnfv.org/get_started
15:49:35 <mestery> Thanks again folks, looking forward to more OpenStack + OpNFV interactions going forward!
15:50:02 * ChrisPriceAB mestery: Thanks kyle.
15:52:06 <ChrisPriceAB> #info Frank provides an update of the bgs project:
15:52:22 <ChrisPriceAB> #info many participants doing private investigative work and experimentation
15:52:43 <ChrisPriceAB> #info unable to run collaborative activites due to a lack of sufficient hardware resources
15:53:29 <ChrisPriceAB> #info hardware is now available for developmental work, with restrictions on security access to the equipment
15:54:03 <ChrisPriceAB> #info it has been identified that our own hardware is needed to overcome the various issues we have found trying to get the bgs project off the ground
15:55:05 <ChrisPriceAB> #info the topic of installers is an item pending concensus on the best approach for OPNFV release 1, attempts ongoing with Fuel found to be difficult to extend for OPNFV work
15:56:30 <ChrisPriceAB> #info daily meetings are being run over IRC, at 06:00 PST and 17:00 PST which have not been attended as much as would have been hoped for.  IRC chanel is irc.freenode.net:6697/opnfv-bgs
15:58:03 <ChrisPriceAB> #info Frank identifies the hardware need is the blocking issue currently, and that an installer needs to be selected.
15:59:14 <ChrisPriceAB> #info Gerard asks if there is an estimate for a timeline for key decisions.  (installer and hardware for instance)
16:00:12 <ChrisPriceAB> #info Frank answers that some of these issues are ready for decision now however a clear plan is not easily defined right now.
16:01:59 <ChrisPriceAB> #info Palani mentions he is interested to continue with Fuel based on his experiences so far working with it, including the possibility to include OpenDaylight.
16:04:51 <TapioT> #join Tapio Tallgren (Nokia)
16:05:45 <ChrisPriceAB> #info Trevor indicates that the Intel testbed may be able to provide the needed hardware for bgs and CI until the build and integration infrastructure is available.
16:16:36 * ChrisPriceAB if random is reproducible, then random is fine! frankbrockners - define random again for me!
16:28:25 <ChrisPriceAB> #topic Octopus project update
16:28:41 <ChrisPriceAB> #info Uli provides and update on the CI project process.
16:29:03 <ChrisPriceAB> #info the team is wrking on the detailed task list for the project to establish a framework for collaboration.
16:29:57 <ChrisPriceAB> #info Uli indicates there are issues with the timing of next weeks meeting.
16:30:42 <ChrisPriceAB> #info dlenrow asks is octopus is suspended until bgs has reached a certain point and then would start working form that base point.
16:31:32 <ChrisPriceAB> #info Uli describes that the planning phase needs to be mature and actionable when bgs has reached such a point.  This work needs to be done first in anticipation of the bgs baseline output.
16:35:41 <ChrisPriceAB> #topic OPNFV HW infrastructure requirements
16:36:36 <ChrisPriceAB> #link https://wiki.opnfv.org/get_started/get_started_work_environment
16:37:36 <ChrisPriceAB> #info Frank describes that a selection of POD's would be required to enable parallel development of platform types as a wish list for the hardware.
16:38:22 <ChrisPriceAB> #info The basic POD set-up would include a master-node, 3 control nodes, and 2 compute nodes
16:39:06 <ChrisPriceAB> #info servers require to be able to be pixie booted, a 40g NIC is required to work toward our target capabilities for OPNFV.
16:39:40 <ChrisPriceAB> #info any purchase should be relatively future proof.
16:39:54 <ChrisPriceAB> #info dedicated storage does not seem to be a high priority requirement for NFV functions.
16:40:37 <julien_ZTE> #info 2 40g NICs are prefered, nor necessary
16:50:27 <julien_ZTE> #info question: does the NIC support SR-IOV ?
16:51:21 <ChrisPriceAB> #agree the hardware needs for the CI/CD and bgd projects need to be concluded by the upcoming TSC meeting on Tuesday the 13th of January.
16:51:35 <frankbrockners> will likely depend on the NIC used... that said, do you really want to go via the bus to move packets... probably not
16:51:44 <rprakash> #action tuesday deadline for opnfv hardware upgrade on get started web page
16:52:33 <ChrisPriceAB> #action frankbrockners to present options for hardware aquisition/leasing on Tuesdays TSC meeting.
16:53:29 <ChrisPriceAB> #action All:  identify needed, networking, connectivity, networking, storage, power needs for the hardware.
16:53:41 <julien_ZTE> #info frankbrokners, yes in our test, currently no other sulotions for the the traffic
16:54:23 <julien_ZTE> #info frankbrockners, yes in our test, currently no other sulotions for the the traffic
16:58:13 <ChrisPriceAB> #topic AoB
17:00:28 <ChrisPriceAB> #info the OPNFV WiKi is not up to date and seems stale at times.  Actions needed on the guidelines for the WiKi shoudl be addressed next week.
17:00:52 <rpaik> #info project leads should keep project wiki pages up tp date
17:01:08 <ChrisPriceAB> #endmeeting