Page Comparison

...

• How does this project fit into the rest of the ONAP Architecture?
  
  
  
  • Please Include architecture diagram if possible
    
  • What other ONAP projects does this project depend on?
    
    • Integration
• How does this align with external standards/specifications?
  • APIs/Interfaces - OpenAPI/Swagger
  • Information/data models - Swagger JSON or YAML models
• Are there dependencies with other open source projects?
  • APIs/Interfaces - OpenResty, Consul, Redis
  • Integration Testing
  • etc.

MSB Use Case:

1. System internal service Service registration by service instanceprovider instances
   • Registration
     Service instances are registered to the registry by proxy or themselves. The visible scope should be indicated as a parameter when register. If a service is only internal visible, the service information is only pulled by the internal gateway (aka router & load balancer) and used by other components inside the system, the interal services can't be accessed by external systems or front end(web client). If a service is visible to external system, the service information is pulled by the external gateway and can be accessed by external systems and front end (web client) with auth.
              
       
   • Discovery ? Service Consuming
     • For internal service consumers(Components inside ONAP system, such as A&AI, SO, Controller, etc.)
       • Client side discovery and load balancing
         
       • Server side discovery and load balancing
         
     • For external service clients(OSS, BSS, Web client, etc.), access the service via external gateway
       
       
       
2. Service registration by service
   The service may have its own load balancer built inside, for example, Kubernetes can create a load balancer for a service. In such case, only need to register the service LB node to MSB, and the service request from the consumer is routed to the service LB node.
   
   • Registration
     Image Added
     
   • Discovery ? Service Consuming
     Image Added
     Note: Only show the client side discovery in this diagram for simplicity, it's also possible to use server side discovery by the internal gateway.
     
     
3. System internal service registration by service

...

1. • Registration

Resources:

• Primary Contact RamKoya, HuabingZhao, Al Hua, Sanjay Agraharam, Brijesh Khandelwal
• Names, gerritIDs, and company affiliations of the committer

• Name	Gerrit ID	Company	Email	Time Zone
  Ram Koya		AT&T	rk541m@att.com	Dallas, USA. CST/CDT
  John Murray		AT&T	jfm@research.att.com	Bedminster, USA EST/EDT
  Dominic Lunanuova		AT&T	dgl@research.att.com	MiddleTown, USA EST/EDT
  Zhaoxing Meng		ZTE	meng.zhaoxing1@zte.com.cn	Beijing, China. UTC +8
  Huabing Zhao	HuabingZhao	ZTE	huabing.zhao@zte.com.cn	Beijing, China. UTC +8
  Yonggang Wang		ZTE	wang.yonggang131@zte.com.cn	Beijing, China. UTC +8
  Tang Hua		ZTE	tang.hua52@zte.com.cn	Beijing, China. UTC +8
  Brijesh Khandelwal		Tech Mahindra	kbrijesh@TechMahindra.com	CDT, USA.
  Hailong He		ZTE	he.hailong5@zte.com.cn	Beijing, China. UTC +8
  Jian Ming		ZTE	jian.ming@zte.com.cn	Beijing, China. UTC +8
  Leibo Huang		ZTE	huang.leibo20@zte.com.cn	Beijing, China. UTC +8
  Hu Rui		ZTE	hu.rui2@zte.com.cn	Beijing, China. UTC +8
  Jinquan Ni		ZTE	ni.jinquan@zte.com.cn	Beijing, China. UTC +8

...