Wikis > Network Services Broker

Notice: The views and opinions expressed here are collective derived from the members of this ONUG working group and are not the express opinion of any individual or company. 

FALL 2016

ONUG Use Case Working Groups Schedule: Network Services Broker
Date Time
TBD TBD Conference Call
October 24 & 25, 2016 TBD ONUG Fall 2016 – Face-to-Face
Working Group Chairman
Vesko Pehlivanov (Credit Suisse)
Carlos Matos (Fidelity Investments)
Members
Craig Martinson Australia & New Zealand Banking Group (ANZ)
Neal Secher BNY Mellon
Kent Brown FedEx
Kevin McCaleb Fidelity
Ted Turner Intuit
Bob Natale MITRE
Makiko Kimura Mitsui & Co.
Hailu Meng Monsanto
Mahesh Desai Tesla Motors
Chris Parchinski Unilever
Jeff Gray Glue
Stefan Dietrich Glue
Mike Haugh Glue
Senad Palislamovic Nuage Networks

 


SPRING 2016

ONUG Use Case Working Groups Schedule: Network Services Broker
Date Time
January 1, 2016 2:00pm-3:00pm ET Conference Call
January 25, 2016 2:00pm-3:00pm ET Conference Call  
February 8, 2016 2:00pm-3:00pm ET Conference Call  
February 22, 2016 2:00pm-3:00pm ET Conference Call  
March 7, 2016 2:00pm-3:00pm ET Conference Call  
March 21, 2016 2:00pm-3:00pm ET Conference Call  
April 4, 2016 2:00pm-3:00pm ET Conference Call  
April 18, 2016 2:00pm-3:00pm ET Conference Call  
May 2, 2016 2:00pm-3:00pm ET Conference Call  
May 9-11, 2016 TBD ONUG Spring 2016 – Face-to-Face
Working Group Chairman
Vesko Pehlivanov (Credit Suisse)
Carlos Matos (Fidelity Investments)
Members
Craig Martinson Australia & New Zealand Banking Group (ANZ)
Neal Secher BNY Mellon
Kent Brown FedEx
Kevin McCaleb Fidelity
Ted Turner Intuit
Bob Natale MITRE
Makiko Kimura Mitsui & Co.
Hailu Meng Monsanto
Mahesh Desai Tesla Motors
Chris Parchinski Unilever
Aziz Abdul Cisco
Jeff Gray Glue
Stefan Dietrich Glue
Mike Haugh Glue
Senad Palislamovic Nuage Networks

Meeting Notes

January 11, 2016

We need to define / Create the following items in order to start getting the deliverables needed

  • Create the Light weight business case
  • Besides our initial definition, Identify users to agree and define what the broker function is
  • Create a full gap  analysis and where the broker can be
  • Define and understand the Scope and possible Sue cases
  • The Broker can use elements of policy definition and from Management groups
  • Later Define the Requirements logically
  • Later after having all these items define the Reference Architecture

Some Ideas

  • The Broker is like the OpenStack of the Network layer as it will offer a NorthBound standard API and could have multiple backend plugins
  • Modules that could integrate and map into all of the other Users groups
  • How Broker can help to keep State
  • Provision using a Service Catalog, service definition, policy definition
  • How Broker helps on analytics and