What is Data Center Building Blocks and Network Virtualization Services?
Data Center Building Blocks
As the role of virtualization in data centers increases, these key building blocks may look different. Currently, we’d expect a fully-virtualized data center to:
be software-defined: automated and managed by a single set of policy-based software tools that allow you to centrally monitor and administer all applications across different environments (physical, virtual, and cloud) and infrastructure types
have built-in security
be very easy to adjust in size – either scaling out/in by adding/removing devices, or by scaling up/down by adding/removing resources such as CPUs or storage to a single device
support the latest developments in application technology, such as containers and apps specifically designed for the cloud
support infrastructure as a code - i.e., support the writing of code that takes care of configuration and automates provisioning.
These building blocks will change as the SDDC grows and develops. Since the emergence of virtualization in the 1960s, with the likes of the Burroughs Corporation’s B5000 computer and IBM mainframe computers, it has changed the world. Servers have probably gone through the most innovative, with tangible benefits including reduced physical complexity, increased operational efficiency, and simplified repurposing (i.e., virtualizing) of underlying physical resources. Today the vast majority of servers are virtualized and, in terms of networking, there are now more virtual ports being used globally than physical ones.
With an already-large range of products in data center management and automation (vSphere, vRealize, and NSX, to name just three), VMware continues to innovate for its current and future customers.
Network Virtualization Services
In this 7-Layer network model, data is transferred from Host A to Host B in segments, packets, frames, and bits.
In Layers 7, 6, and 5, data is referred to simply as data.
In Layer 4 (the transport layer) data is divided into smaller chunks. A process called encapsulation takes place in which information is added to the data as it moves from Layer to Layer. This information (the precise contents of which will vary from layer to Layer) is called a header. In layer 4, once a header is added to the data, the data is referred to as a segment. Its header will contain port numbers for the applications that will use the data is Host B. Layer 4 then hands each segment down to Layer 3.
In Layer 3 (the network layer) data is transferred from one Internet Protocol (IP) address to another via a router. Each segment that's been handed down from Layer 4 will be encapsulated with source information (Host A's IP address), destination information (Host B's IP address), an identification number, another number that identifies how many pieces the information that's being sent (the payload) has been broken up into, and part of that information. Once the header is attached, the segment is referred to as a packet. Layer 3 hands the packet down to Layer 2.
Layer 2 (the data link layer) is responsible for error-free data transfer from one device to another. The packets are encapsulated with Host A and Host B's Media Access Control (MAC- i.e., hardware) addresses, as well as with Logical Link Control (LLC) which maintains the link between devices as they transmit data across the physical network connection. Each packet is also encapsulated with a footer (or trailer), containing error-detecting information. With its header and footer/trailer attached, the packet is referred to as a frame. Layer 2 hands the frame down to Layer 1.
Layer 1 is the physical layer that consists of physical cables and connections. It converts frames into binary bits in the form of voltage for physical cables and radio signals for wireless connections.
In the overlay networking used by network virtualization, endpoints connect the physical network (the underlay) to the overlay network. Encapsulated traffic is transferred between hosts via a stateless tunnel (i.e., no TCP connections are made with the tunnel) that is created between the source endpoint and the destination endpoint.