Skip to content

Commit 0d067d5

Browse files
authored
Acs improvements (#287)
* wip * WIP * wip * wip * added optional OOB network handling
1 parent 28043a2 commit 0d067d5

File tree

5 files changed

+539
-232
lines changed

5 files changed

+539
-232
lines changed

conf.py

+1
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,7 @@
3636
'sphinx.ext.githubpages',
3737
'sphinx_rtd_theme',
3838
'sphinx_copybutton',
39+
'sphinx_tabs.tabs',
3940
]
4041

4142
# Add any paths that contain templates here, relative to this directory.

tutorials/netris-cloudstack_p1.rst

+32-30
Original file line numberDiff line numberDiff line change
@@ -48,51 +48,53 @@ Use Cases
4848
Compute and Network Architecture
4949
================================
5050

51-
The current infrastructure for Netris-CloudStack integration is designed to support scalable and dynamic networking for cloud workloads. Below is a breakdown of the key components and their roles:
51+
The current infrastructure for Netris-CloudStack integration is designed to support **scalable and dynamic** networking for cloud workloads. This section outlines the key infrastructure components and their roles.
5252

5353
Diagram Overview
5454
----------------
5555

56-
The diagram illustrates the interconnected infrastructure, consisting of:
56+
The diagram represents the interconnected infrastructure, consisting of:
5757

58-
1. Leaf and Spine Switches:
58+
1. **Leaf and Spine Switches**:
5959

60-
* These form the core networking layer, enabling high-speed and fault-tolerant connections.
61-
* Spine switches (Spine 1 and Spine 2) aggregate traffic and connect to the leaf switches.
62-
* Leaf switches (Leaf 1 and Leaf 2) connect directly to the compute nodes and softgates, ensuring efficient traffic distribution and handling VXLAN traffic.
60+
- These switches form the **core networking fabric**, ensuring **high-speed, redundant, and fault-tolerant connectivity**.
61+
- **Spine switches** (Spine 1 and Spine 2) aggregate traffic and connect to **leaf switches**.
62+
- **Leaf switches** (Leaf 1 and Leaf 2) connect directly to **compute nodes and softgates**, handling **VXLAN encapsulation**.
6363

64-
2. Softgates:
64+
2. **Softgates**:
6565

66-
* Softgates play a critical role in integrating physical and virtual network environments. They are responsible for:
67-
68-
* NAT Function: Enabling secure communication between private and external networks.
69-
* Elastic Load Balancer: Distributing traffic across multiple resources for high availability and scalability.
70-
* Network Access Control: Enforcing access policies for secure communication.
71-
72-
* Additionally, they bridge VXLAN and traditional networks and support BGP/EVPN-based signaling for dynamic routing.
66+
- Softgates play a critical role in integrating physical and virtual network environments. They are responsible for:
7367

74-
3. Servers:
68+
- **NAT Functionality**: Facilitates secure communication between **private and external networks**.
69+
- **Elastic Load Balancer**: Distributes inbound traffic to multiple backend instances.
70+
- **Network Access Control**: Enforces security policies at the edge.
7571

76-
* Server 1: Designated as the CloudStack Management Node, responsible for orchestrating the environment.
77-
* Server 2, Server 3, and Server 4: These are KVM hypervisors managed by CloudStack, functioning as VTEPs for VXLAN tunnels.
72+
- Additionally, Softgates bridge **VXLAN and traditional networking** and support **BGP/EVPN for dynamic routing**.
7873

79-
4. OOB (Out-of-Band) Switch:
74+
3. **Servers**:
8075

81-
* An Out-of-Band (OOB) switch connects all servers for administrative purposes.
82-
* This switch allows administrators to:
83-
* Access servers during emergencies.
84-
* Install software packages and perform updates.
85-
* Troubleshoot and manage servers independently of the main network.
76+
- **Server 1**:
8677

87-
5. Internet eBGP:
78+
- Designated as the **CloudStack Management Node**, responsible for orchestrating the environment.
79+
- **Server 2, Server 3, and Server 4**:
8880

89-
* Leaf switches are connected to external networks via eBGP, ensuring reachability for public and private traffic.
81+
- These **KVM hypervisors** are managed by **CloudStack** and function as **VXLAN Tunnel Endpoints (VTEPs)**.
82+
83+
4. **OOB (Out-of-Band) Switch (If Present)**:
84+
85+
- If available, an **OOB switch** provides an independent **management network** for accessing servers.
86+
- Allows administrators to:
87+
88+
- Perform **software installations and updates**.
89+
- Troubleshoot and manage servers independently of the main network.
9090

9191

9292
Network Flow
9393
------------
94-
#. Traffic flows between hypervisors (VTEPs) over VXLAN tunnels. These tunnels are dynamically configured using BGP/EVPN signaling.
95-
#. Softgates handle routing between overlay and underlay networks, ensuring seamless communication for workloads.
96-
#. The CloudStack Controller communicates with the Netris Controller API to coordinate network configurations.
97-
#. Leaf and spine switches provide a robust and scalable fabric to support high availability and performance.
98-
#. The OOB switch provides an independent path for server management, ensuring operational reliability.
94+
95+
1. **Hypervisor traffic** traverses **VXLAN tunnels**, dynamically configured via **BGP/EVPN**.
96+
2. **Softgates handle routing** between overlay and underlay networks, ensuring seamless workload communication.
97+
3. **CloudStack Controller** communicates with **Netris Controller API** to synchronize network configurations.
98+
4. **Leaf and Spine switches** ensure a **highly available and scalable** fabric for compute workloads.
99+
5. If an **OOB switch is available**, it provides **direct administrative access** to all servers.
100+
6. **Softgates establish BGP sessions** for external connectivity, ensuring **public and private traffic reachability**.

0 commit comments

Comments
 (0)