add agent section, rewrote the vault installation section a bit

config/_default/menus.toml

@@ -10,11 +10,11 @@
   identifier = "opensource"
   url = "/opensource/"
 
-[[opensourcev3]]
-  name = "Opensource v3"
+[[agent]]
+  name = "Agent"
   weight = 12
-  identifier = "opensourcev3"
-  url = "/opensource-v3/"
+  identifier = "agent"
+  url = "/agent/"
 
 [[enterprise]]
   name = "Enterprise"

content/agent/_index.md

@@ -1,5 +1,5 @@
 ---
-title: "Opensource v3"
+title: "Agent"
 description: ""
 lead: ""
 date: 2020-10-06T08:49:15+00:00

content/agent/announcement/index.md

@@ -0,0 +1,53 @@
+---
+title: "Announcement"
+description: "A Kerberos Agent with more features, better performance, and great UX."
+lead: "A Kerberos Agent with more features, better performance, and great UX."
+date: 2020-10-06T08:49:31+00:00
+lastmod: 2020-10-06T08:49:31+00:00
+draft: false
+images: []
+menu:
+    agent:
+        parent: "agent"
+weight: 300
+toc: true
+---
+
+Kerberos Agent is the next generation of Kerberos.io, and is the successor of Kerberos Open Source (v1/v2). More specifically it will replace and merge the [machinery](https://github.com/kerberos-io/machinery) and [web](https://github.com/kerberos-io/web) repositories. A switch in technologies and architecture has been made. Kerberos Agent is still under active development, and not yet released. The progress can be followed at the [develop branch](https://github.com/kerberos-io/opensource/tree/develop) and [project overview](https://github.com/kerberos-io/opensource/projects/1).
+
+## What is changing?
+
+Bottom line, we are rebuilding the project from scratch using a different technology stack. We are saying goodbye to C++, PHP (Laravel), BackboneJS and saying hello to Golang and React. Despite the technology changes, we are also changing the architecture which was put in place a couple of years ago. The biggest change is to run the show inside a single repository, and no longer over seperate repos (machinery and web). Read more about this in the FAQ.
+
+{{< figure src="opensource-to-agent.svg" alt="The Kerberos Agent 3 is a complete new rewrite of the Kerberos Open Source version 1 and 2." caption="The Kerberos Agent 3 is a complete new rewrite of the Kerberos Open Source version 1 and 2." class="stretch">}}
+
+## FAQ
+
+### 1. Why a mono repo?
+
+We have noticed in the past (v1 and v2) that splitting the repositories (machinery and web), created a lot of confusion within our community. People didn't understand the different versions and so on. This caused a lack of collaboration, and made it impossible for some people to collaborate and contribute.
+
+Having a mono repo, which is well-organised, simplifies the entry point for new people who would like to use, understand and/or contribute to Kerberos Agent.
+
+### 2. Why a change in technologies?
+
+In previous versions (v1 and v2) we used technologies like C++, PHP and BackboneJS. 7 years ago this was still acceptable, however time has changed and new technologies such as React and Golang became very popular.
+
+Due to previous reason we have decided to rebuild the Kerberos Open Source technology from scratch, taking into account all the feedback we acquired over the years. Having these technologies available, we will enable more people to contribute and use our technology.
+
+### 3. How is the Kerberos Enterprise Suite involved?
+
+We started the developments of the Kerberos Enterprise Suite a year ago (January, 2020), our focus here was scalability, fast development and easy deployment. We noticed that with technologies such as Golang and React, we can still provide a highly performant video surveillance system.
+
+The Kerberos Agent which is currently part of the Kerberos Enterprise Suite will be open sourced and become the one and only engine for video stream capturing, motion detection, etc.
+
+The Kerberos Agent will be used both in the open source as the B2B communities. Other solutions such as Factory, Vault and Hub will be made available through different licensing.
+
+### 4. When are we going to be able to install the first version?
+
+We plan to ship the **first version by the end of Q1**, afterwards we will add more and more features as usual.
+
+
+### 5. Change in License
+
+Kerberos Agent is now available under the MIT license.

content/opensourcev3/announcement/index.md

@@ -1,51 +0,0 @@
----
-title: "Announcement"
-description: "A new Open Source agent with more features, better performance, and great UX."
-lead: "A new Open Source agent with more features, better performance, and great UX."
-date: 2020-10-06T08:49:31+00:00
-lastmod: 2020-10-06T08:49:31+00:00
-draft: false
-images: []
-menu:
-  opensourcev3:
-    parent: "opensourcev3"
-weight: 300
-toc: true
----
-
-Kerberos Open Source (v3) is the next generation of Kerberos.io, and is the successor of (v1/v2). More specifically it will replace and merge the [machinery](https://github.com/kerberos-io/machinery) and [web](https://github.com/kerberos-io/web) repositories. A switch in technologies and architecture has been made. Version 3 is still under active development, and not yet released. The progress can be followed at the [develop branch](https://github.com/kerberos-io/opensource/tree/develop) and [project overview](https://github.com/kerberos-io/opensource/projects/1).
-
-## What is changing?
-
-At the bottom line, we are rebuilding the project from scratch using a different technology stack. We are saying goodbye to C++, PHP (Laravel), BackboneJS and saying hello to Golang and React. Despite the technology changes, we are also changing the architecture, we have put in place a couple of years ago. The biggest change is to run the show inside a single repository, and no longer over seperate repos (machinery and web). Read more about this in the FAQ.
-
-{{< figure src="opensource-version2-version3.svg" alt="The Opensource version 3 is a complete new rewrite of the version 2." caption="The Opensource version 3 is a complete new rewrite of the version 2." class="stretch">}}
-
-## FAQ
-
-### 1. Why a mono repo?
-
-We have noticed in the past (v1 and v2) splitting the repositories (machinery and web), created a lot of confusion within our community. People didn't understand the different versions and so on. This caused a lack of collaboration, and made it impossible for some people to collaborate and contribute.
-
-Having a mono repo, which is well organised, simplifies the entry point for new people who would like to use, understand and/or contribute to Kerberos Open Source.
-
-### 2. Why a change in technologies?
-
-In previous versions (v1 and v2) we used technologies like C++, PHP and BackboneJS. 7 years ago this was still acceptable, however time has changed and new technologies such as React and Golang became very popular.
-
-Due to previous reason we have decided to rebuild the Kerberos Open Source technology from scratch, taking into account all the feedback we acquired over the years. Having these technologies available, we will enable more people to contribute and use our technology.
-
-### 3. What is the difference with Kerberos Enterprise?
-
-We started the developments of Kerberos Enterprise a year ago (January, 2020), our focus here was scalability, and fast development and easy deployment. We noticed that with technologies such as Golang and React, we can still provide a highly performant video surveillance system.
-
-Kerberos Open Source will use the same technology stack, and some code pieces, of Kerberos Enterprise which we have already build. We have a very clear now, of how a well developed and documented video surveillance system needs to look like.
-
-### 4. When are we going to be able to install the first version?
-
-We plan to ship the **first version by the end of Q1**, afterwards we will add more and more features as usual.
-
-
-### 5. Change in License
-
-Kerberos Open Source (v3) is now available under the MIT license.

content/vault/installation/index.md

@@ -13,28 +13,29 @@ weight: 302
 toc: true
 ---
 
-Just like Kerberos Enterprise, Kerberos Vault can be installed where Kubernetes can be installed. This means that it can run at the Edge - Baremetal -, in the cloud - VMs - or at Kubernetes service providers - SAAS - such as GCP, Azure, AWS, DigitalOcean, and the list goes on.
+Kerberos Vault is shipped as a Docker container and is preferably installed inside a Kubernetes cluster. This means that it can run at the edge, or in the cloud.
 
-Although you might except Kubernetes at the Edge or Kubernetes in the cloud, there are no differences, well sorry to say there are. As Kubernetes service providers implemented features such as LoadBalancers, Persistent Volumes, and others, they have automated and integrated a huge portion of the Kubernetes stack with their related PAAS services. To be more concrete if you are running a Kubernetes Cluster on GCP, you will use the LoadBalancing and Storage services from GCP.
+Although you might except that Kubernetes at the edge or Kubernetes in the cloud is the same installation, you will notice that there are a few differences. 
 
-{{< figure src="deployment-models.svg" alt="Kerberos Vault can be installed everywhere your Kubernetes cluster can be installed." caption="Kerberos Vault can be installed everywhere your Kubernetes cluster can be installed." class="stretch">}}
+When running a Kubernetes cluster on a Kubernetes service provider, such as [GKE](https://cloud.google.com/kubernetes-engine), [EKS](https://aws.amazon.com/eks/), you will have a couple of superpowers such as a `LoadBalancer` service, automatic `Volume` creation, etc. The latter is something what is missing in an Edge deployment, there you have to prepare the volumes yourself and install an edge load balancer like `MetalLB`. 
 
-Compared to Kubernetes at the Edge, there are no predefined LoadBalancers, Storage capabilities, and more. This means more administration work for you, but - with great power comes great responsibility - so no worries. In the end there are alternative functionalties available, for features which you find out-of-the-box at the Kubernetes service providers, you just have to spend more time on configuring and installing those services/pods/deployments yourself.
+{{< figure src="vault-edge-cloud-deployments.svg" alt="Kerberos Vault can be installed everywhere your Kubernetes cluster can be installed." caption="Kerberos Vault can be installed everywhere your Kubernetes cluster can be installed." class="stretch">}}
 
 ## Installation on a Kubernetes Service Provider
 
-Installing Kerberos Vault, just like Kerberos Enterprise, on a Kubernetes Service Provider (Azure, GCP, AWS) is straight forward, as you can create a Kubernetes cluster in a few clicks, get access to public Load Balancers, storage and more. Running Kerberos Vault in such a cluster is just a matter of copy-pasting some configuration (yaml) files, and executing some `kubectl apply` commands.
+Installing Kerberos Vault on a Kubernetes Service Provider (Azure, GCP, AWS) is straight forward, as you can create a Kubernetes cluster in a few clicks, get access to public load balancers, volumes and more. Running Kerberos Vault in such a cluster is just a matter of copy-pasting some configuration (yaml) files, and execution of `kubectl apply` commands.
 
-{{< figure src="../first-things-first/arch-kerberos-vault-providers.svg" alt="Bring your own storage using Kerberos Vault" caption="Bring your own storage using Kerberos Vault" class="stretch">}}
+Install Kerberos Vault on a Kubernetes Service Provider by [following this step-by-step installation guide](/vault/installation-cloud).
 
-Install Kerberos Vault on a Kubernetes Service Provider by [following this step-by-step installation guide](/storage/installation-cloud).
+{{< figure src="vault-cloud-deployment.svg" alt="Bring your own storage using Kerberos Vault" caption="Bring your own storage using Kerberos Vault" class="stretch">}}
 
 ## Installation in Private cloud or Baremetal
 
-No need to install Kerberos Vault on a Kubernetes Service Provider, you could install it on your own Kubernetes cluster in your private cloud, or even better inside your own premise. The closer you bring Kerberos Vault to your surveillance infrastructure, and Kerberos Enterprise, the more benefits you will experience (low latency, low bandwidth, etc).
+No need to install Kerberos Vault on a Kubernetes Service Provider, it can be installed on your own Kubernetes cluster in your private cloud, or at the edge. The closer you bring Kerberos Vault to your video streams, and Kerberos Agents, the more benefits you will experience (low latency, low bandwidth, etc). 
 
-{{< figure src="../first-things-first/arch-edge-kerberos-vault.svg" alt="Store your recordings at the edge with Kerberos Vault" caption="Store your recordings at the edge with Kerberos Vault" class="stretch">}}
-
-In contradiction to the Kubernetes Service Provider, you will have some work todo. Setting up Kubernetes Cluster, play with MetalLB, Persistent Volumes and claims. Don't be scared, it's pretty straight forward as well. You can't simple expect a: click, click, 💥 approach.
+In contradiction to the Kubernetes Service Provider, there will be more work required. Setting up a Kubernetes Cluster, configure a load balancer, create persistent bolumes and claims.
 
 Install Kerberos Vault on a Private cloud or Baremetal by [following this step-by-step installation guide](/vault/installation-edge).
+
+
+{{< figure src="vault-edge-deployment.svg" alt="Store your recordings at the edge with Kerberos Vault" caption="Store your recordings at the edge with Kerberos Vault" class="stretch">}}

layouts/partials/sidebar/docs-menu.html

@@ -21,12 +21,12 @@
   </ul>
   {{ end -}}
 {{ end -}}
-{{ range .Site.Menus.opensourcev3 -}}
+{{ range .Site.Menus.agent -}}
   <h3>{{ .Name }}</h3>
   {{ if .HasChildren -}}
   <ul class="list-unstyled">
     {{ range .Children -}}
-    {{- $active := or ($currentPage.IsMenuCurrent "opensourcev3" .) ($currentPage.HasMenuCurrent "opensourcev3" .) -}}
+    {{- $active := or ($currentPage.IsMenuCurrent "agent" .) ($currentPage.HasMenuCurrent "agent" .) -}}
     <li><a class="docs-link{{ if $active }} active{{ end }}" href="{{ .URL | relURL }}">{{ .Name }}</a></li>
     {{ end -}}
   </ul>
@@ -75,4 +75,4 @@
     {{ end -}}
   </ul>
   {{ end -}}
-{{ end -}}
+{{ end -}}