...

Network Topology

This network topology aspect type defines network traffic between components, servers, racks and network traffic between the DC and the internet. Network topology defines physical extendability properties of the DC, thus, we need to consider:

• How will the automated hardware discovery process be handled?

• What deployment schema should be used when implementing new nodes?

• Which system components are involved in discovery and deployment processes?

• How will any non-positive results of discovery and deployments be handled?

Topology types:

• tree, tree 

• clos

• fat-tree

• thorus

• etc)

We are obviously not able to fine-tune Warrens setup for every type of topology. Topology is not a standalone factor and the set of variables in pre-analysis makes it too costly compared to the business-value of the expected outcome. However we can target discovery and deployment solutions most widely used by DCs with a sufficient degree of quality. Service reliability and availability metrics cannot theoretically be calculated in a platform that is under continuous heavy development. Thus these metrics will rather be defined during the DC adoption and on-boarding process. 

...

The goal of Warren is to reallocate resources to minimize internal-DC traffic. In rare cases this can result in destabilising the network flow for a short period of time. In cases where client application related data flow is causing problems, system management related data flow must always take priority, even in cases where client throughput as a result decreases further. The purpose is to restore the systems previous state or maximise the efficiency of limited available resources in a given point in time. 

Pre-Existing DC

...

SDN

...

Solution

In general, all SDN systems are based on the same principles an and in major part, derived from two prevalent frameworks for SDN generation. There are several types of protocols when it comes to network device configuration , among which, ( OpenFlow is still the most dominant one). Almost all needed routing protocols are also supported by all major SDN solutions.  To conclude the above, there shouldn’t arise any drastic This means any pre-existing SDN solution the DC might already use, should not cause any drastic adoption or installation problems on a connection basis (which . Which doesn't mean it's a trivial task!).

However, there is an exception to that hypothetical balance - the security domain. All SDN systems implement some (or more) security domains, whether it’s client level or system-wide. To configure 2 or more SDN systems to cooperate simultaneously on that domain, might be more time consuming than to configure the whole system to use adopt a new one.

Considerations and Goals in the Storage Domain

...