Browse Source

Add more detail of what Calico is to the plugin README

Change-Id: I7d85ea31bcf6258e62609b736895cd457120ec34
Emma Gordon 3 years ago
parent
commit
e1a39b408c
1 changed files with 20 additions and 8 deletions
  1. 20
    8
      README.md

+ 20
- 8
README.md View File

@@ -7,16 +7,28 @@ with the Fuel 6.1 release, you should see the 6.1 branch of this repository.
7 7
 
8 8
 Calico plugin for Mirantis Fuel
9 9
 ===============================
10
+Calico’s pure L3 approach to data center networking integrates seamlessly with
11
+Mirantis OpenStack to bring simple, scalable and secure networking to your
12
+deployment.
10 13
 
11
-Calico provides seamless, scalable, secure Layer 3 Virtual Networking for your
12
-Mirantis OpenStack Deployment.
14
+Based on the same scalable IP network principles as the Internet, Calico
15
+implements a highly efficient vRouter in each compute node that leverages the
16
+existing Linux kernel forwarding engine without the need for vSwitches. Each
17
+vRouter propagates workload reachability information (routes) to the rest of
18
+the data center using BGP – either directly in small scale deployments or
19
+via BGP route reflectors to reach Internet level scales in large deployments.
13 20
 
14
-By replacing OpenStack’s native networking model, Calico targets deployments 
15
-where the vast majority of workloads only require L3 connectivity, providing 
16
-efficient, easy to troubleshoot networking, without the complexity and 
17
-inefficiency of overlay networking models. Calico does not require any 
18
-additional nodes or Calico specific management – it just works, and gets out 
19
-of your way!
21
+Calico peers directly with the data center’s physical fabric (whether L2 or
22
+L3) without the need for on/off ramps, NAT, tunnels, or overlays.
23
+
24
+With Calico, networking issues are easy to troubleshoot. Since it's all IP,
25
+standard tools such as ping and traceroute will just work.
26
+
27
+Calico supports rich and flexible network policy which it enforces using
28
+bookended ACLs on each compute node to provide tenant isolation, security
29
+groups, and external reachability constraints.
30
+
31
+For more details, see [projectcalico.org](http://www.projectcalico.org).
20 32
 
21 33
 Limitations:
22 34
 ------------

Loading…
Cancel
Save