Software Defined Datacenters (SSDC) is a term invented to describe new datacenter networking systems and their connection to server systems centralized management and deployment. SSDC is leveraging centralized management and deployment of networking devices and server hypervisor hosts in a way then their configuration is seamlessly configured in order to automate, simplify and speed-up IT services deployment.
Here are some articles regarding some of the most popular SDDC solutions, how they work and what are the caveats behind building SDDC solutions:
- Google Jupiter Data Center Network Fabric – New Way of Building Data Center Network Underlay
- Switch vSphere Enterprise Plus license to vSphere Standard on a NSX-T enabled cluster
- NSX-T Edge Transport Node Packet Capture
- VMware NSX-T Install Tips & Tricks
- VMware TKGI – Deployment of Harbor Container Registry fails with error
- Software-defined data center and what’s the way to do it
- What is Cisco ACI?
- CLOS Topology
- Setting up Cisco ACI From Scratch
- New ACI deployment? Watch out when connecting APICs to Leafs
- ACI MultiPod and how to build MultiDatacenter with Cisco ACI
- Cisco ACI – API Calls vs JSON POST
- Cisco ACI – Configuring by POSTing JSON
- How to Advertise a Route from ACI Layer2 BD Outside the Fabric?
- ACI MultiPod – Enable Standby APIC
If you’re interested in a specific vendor’s solution, some of those articles are sorted by:
In the image below, there’s the Google’s way of doing data center stuff with their Jupiter Datacenter Fabric, OCS switching and SDN enabled traffic engineering. Really cool stuff.
Google Jupiter Datacenter Fabric with OCS switching and SDN enabled traffic engineering