diff --git a/alpha-5/404.html b/alpha-5/404.html new file mode 100755 index 0000000..18b664f --- /dev/null +++ b/alpha-5/404.html @@ -0,0 +1,1183 @@ + + + +
+ + + + + + + + + + + + + + + + + + +The Hedgehog Open Network Fabric is an open source network architecture that provides connectivity between virtual and
+physical workloads and provides a way to achieve network isolation between different groups of workloads using standard
+BGP EVPN and vxlan technology. The fabric provides a standard kubernetes interfaces to manage the elements in the
+physical network and provides a mechanism to configure virtual networks and define attachments to these virtual networks.
+The Hedgehog Fabric provides isolation between different groups of workloads by placing them in different virtual
+networks called VPC's. To achieve this we define different abstractions starting from the physical network where we
+define Connection
which defines how a physical server on the network connects to a physical switch on the fabric.
The Hedgehog Fabric currently support two underlay network topologies.
+A collapsed core topology is just a pair of switches connected in a mclag configuration with no other network elements. +All workloads attach to these two switches.
+ +The leaf's in this setup are configured to be in a mclag pair and servers can either be connected to both switches as +a mclag port channel or as orphan ports connected to only one switch. both the leaves peer to external networks using +BGP and act as gateway for workloads attached to them. The configuration of the underlay in the collapsed core is very +simple and is ideal for very small deployments.
+A spine-leaf topology is a standard clos network with workloads attaching to leaf switches and spines providing +connectivity between different leaves.
+ +This kind of topology is useful for bigger deployments and provides all the advantages of a typical clos network. +The underlay network is established using eBGP where each leaf has a separate ASN and peers will all spines in the +network. We used RFC7938 as the reference for establishing the +underlay network.
+The overlay network runs on top the underlay network to create a virtual network. The overlay network isolates control +and data plane traffic between different virtual networks and the underlay network. Visualization is achieved in the +hedgehog fabric by encapsulating workload traffic over vxlan tunnels that are source and terminated on the leaf switches +in the network. The fabric using BGP-EVPN/Vxlan to enable creation and management of virtual networks on top of the +virtual. The fabric supports multiple virtual networks over the same underlay network to support multi-tenancy. Each +virtual network in the hedgehog fabric is identified by a VPC. In the following sections we will dive a bit deeper into +a high level overview of how are vpc's implemented in the hedgehog fabric and it's associated objects.
+We know what is a VPC and how to attach workloads to a specific VPC. Let us now take a look at how is this actually +implemented on the network to provide the view of a private network.
+To enable communication between 2 different VPC's we need to configure a VPC peering policy. The hedgehog fabric +supports two different peering modes.
+Under construction.
+{"use strict";/*!
+ * escape-html
+ * Copyright(c) 2012-2013 TJ Holowaychuk
+ * Copyright(c) 2015 Andreas Lubbe
+ * Copyright(c) 2015 Tiancheng "Timothy" Gu
+ * MIT Licensed
+ */var Ha=/["'&<>]/;Un.exports=$a;function $a(e){var t=""+e,r=Ha.exec(t);if(!r)return t;var o,n="",i=0,s=0;for(i=r.index;i