...
Requirements in the network domain
There are several factors in DC's DCs network setup that dictates what we need to think through in the Warren application development process. Such factors include:
Network topology (tree, clos, fat-tree, thorus, etc)
This aspect restricts defines network traffic between components, servers, racks and also between DC and the internet. Also, it sets DC's It sets DCs physical extendability properties, thus, we need to think through how consider:
How the automated discovery process will be handled
...
What deployment schema to use when implementing new nodes
Which components are involved in such
...
processes
How the non-positive results of such cases
...
will be handled.
Obviously, we cannot fine-tune our setup for every topology type because it's not a standalone factor, so the set of variables in such analysis is large and too costly compared to the business-value of the outcome. But we can target the solution that covers topologies mostly used in target DC's DCs with a sufficient degree of quality (metrics . Metrics of service reliability and availability standards are something that cannot be purely theoretically calculated in the platform that is under heavy development and . Thus, they will rather be deduced during DC from DCs adoption process). The current assumption is that the most widely used topologies in the probable target DC group are fat-tree and various forms of clos.
...
. Based on that, most optimizations are made for the latter two topology types.
Nature of applications and services offered by DC
Although, both, this and next point seem to be trivial compared to a real problem magnets like network topology, adopting SDN solution, or better yet, consolidating different SDN solutions; this has become a major issue in public clouds (and presumably also in private ones, where such issues are usually not materialized as a series of scientific papers). Like almost all (except for SDN maybe) network-related considerations, also this one has the quantity-dependent nature.
In-DC traffic amount between racks
The bigger the amounts of data-flow between hardware devices, the bigger of a problem it tends to be.
In-DC traffic amount between racks
This traffic (and also In-DC traffic between silos, if larger DC is under consideration), is the one that measures the service system (Warren) efficiency. It's a two-fold problem, first the traffic the traffic that is generated by the clients, secondly the one that is generated by Warren as a management system. Management flow must always take precedence when client flow is causing problems.
Existing SDN solution
Requirements in storage domain
...