1 / 7

Advanced Network Connectivity Use Cases for Component Integration and Monitoring

This document outlines various use cases for network connectivity between components in distributed systems. It emphasizes the requirements and provisions of endpoints, detailing how Component A interacts with Component B. The discussion covers symmetric connectivity, multiple network ports, and connection directions — particularly in client-server relationships. It highlights scenarios such as cluster communication and database monitoring setups. The emphasis is on proper expression of connectivity needs and the importance of whitelisting and directionality in securing network interactions.

alexa
Télécharger la présentation

Advanced Network Connectivity Use Cases for Component Integration and Monitoring

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Some Network Connectivity Use Cases dpalma@vnomic.com

  2. Requires/Provides • EndPoints are Capabilities • Component A requires and endpoint E1 which B provides • Component A resolves to B (and its subclasses) at assembly time Component A Component B Requires (E1) Provides (E1) Connector

  3. ConnectsTo (thus far) • Component A connectsTo Component B • i.e. Component A requires a connection to Component B Component A Component B Requires (E1) Provides (E1) ConnectsTo Client Server Connection • Connection has been assumed to be a single network connection, e.g. Client connection of TCP to MySQL at well known port 3306 over one network connection. • Client side of connection is assumed to be the requiring side of the relationship.

  4. Additional Use Cases • Multiple network L4 ports or protocols required to realize the connectivity • Symmetric connectivity • Both A and B can connect to each other in any order • Network connection in opposite direction than Req/Cap relationship

  5. Multiple network L4 ports or protocols • Consider NFS • TCP or UDP: 2049(nfsd), 111(rpcbind), 892(mountd), 662(statd) • TCP 32803 (lockd) • UDP 32769 (lockd) • We must be able to express • Multiple ports • Connection direction (see opposite direction use case) • Consider firewall filter tuple syntax and treat as directional flow • Use white-listing (assume everything is disabled by default) NOT black-listing (we don’t know what is open by default!)

  6. Symmetric connectivity • Consider a cluster • They may know each others’ IP address and connect to each other via the same well known port over TCP • They may use a multi-cast cluster discovery/group membership protocol • This is peer-to-peer • Any member can initiate communication • Expresses membership • Order is not important (for orchestration)

  7. Network connection in opposite direction than Req/Cap • A DB is deployed • It requires needs monitoring implemented by an additional monitoring node • Monitoring node connects to DB node via SSH (could be any protocol, it is the direction that is important here) to collect metrics • Need to be able to express this Component A Component B Requires (E1) Provides (E1) Client Server Connection

More Related