Network engineering continued ...

  This is a continuation of the earlier posts starting with this one: http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html

452. The virtual machines for the individual customers are sticky. Customers don’t usually release their resource and even identify it by their name or ip address for their daily work.  They host applications, services and automations on their virtual machines and often cannot let go of their virtual machine unless files and programs have a migration path to another compute resource. Typically, they do not take this step to create regular backups and keep moving the resource.  

453. Cluster based topology testing differs significantly from peer-to-peer networking-based topology testing. One represents the capability and the other represents distribution. The tests must articulate different loads for each. 

454. 459. The testing of software layers is achieved with simulation of lower layers. However, integration testing is closer to real life scenarios. Specifically, the testing of data corruption, unavailability or loss is critical to the networking product 

     460. The use of injectors, proxies, man-in-the-middle test topology aspect but networking is more concerned with throughput and latency, specific numbers associated with minimum and maximum limits and inefficiencies when the limits are exceeded. 

     461. Most storage products have a networking aspect. Testing covers networking separately from the others. This means timeouts, downtime, resolutions and traversals up and down the networking layers on a host. It also includes location information. 

     462. The control and data path traces and execution cycles statistics are critical to capture and query with a tool so that the testing can determine if the compute is at fault. Most such tools provide data over the http.