mirror of
https://github.com/kerberos-io/documentation.git
synced 2026-08-23 15:18:31 +00:00
move everything in sub dirs
This commit is contained in:
cedricve
@@ -7,6 +7,18 @@
|
||||
content: "";
|
||||
}
|
||||
|
||||
.docs-content figure {
|
||||
&.stretch img {
|
||||
width: 100%;
|
||||
}
|
||||
figcaption {
|
||||
text-align: center;
|
||||
font-weight: 400;
|
||||
font-size: 13px;
|
||||
padding: 10px 0 0 0;
|
||||
}
|
||||
}
|
||||
|
||||
.anchor {
|
||||
visibility: hidden;
|
||||
padding-left: 0.5rem;
|
||||
|
||||
@@ -4,31 +4,31 @@
|
||||
identifier = "prologue"
|
||||
url = "/prologue/"
|
||||
|
||||
[[docs]]
|
||||
[[opensource]]
|
||||
name = "Opensource v2"
|
||||
weight = 11
|
||||
identifier = "opensource"
|
||||
url = "/opensource/"
|
||||
|
||||
[[docs]]
|
||||
[[opensourcev3]]
|
||||
name = "Opensource v3"
|
||||
weight = 12
|
||||
identifier = "opensourcev3"
|
||||
url = "/opensource-v3/"
|
||||
|
||||
[[docs]]
|
||||
[[enterprise]]
|
||||
name = "Enterprise"
|
||||
weight = 13
|
||||
identifier = "enterprise"
|
||||
url = "/enterprise/"
|
||||
|
||||
[[docs]]
|
||||
[[vault]]
|
||||
name = "Vault"
|
||||
weight = 14
|
||||
identifier = "vault"
|
||||
url = "/vault/"
|
||||
|
||||
[[docs]]
|
||||
[[hub]]
|
||||
name = "Hub"
|
||||
weight = 15
|
||||
identifier = "hub"
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "First things first2"
|
||||
title: "First things first"
|
||||
description: ""
|
||||
lead: ""
|
||||
date: 2020-10-06T08:49:31+00:00
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
enterprise:
|
||||
parent: "enterprise"
|
||||
weight: 300
|
||||
toc: true
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Get Started2"
|
||||
title: "Get Started"
|
||||
description: ""
|
||||
lead: ""
|
||||
date: 2020-10-06T08:49:31+00:00
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
enterprise:
|
||||
parent: "enterprise"
|
||||
weight: 301
|
||||
toc: true
|
||||
@@ -55,26 +55,23 @@ On the left menu you will find the Kubernetes section. In this section 3 sub men
|
||||
|
||||
The nodes section lists all the available nodes inside your Kubernetes cluster. It shows a limited amount of information such as the version, the number of Docker images installed on the node, and some basic hardware information.
|
||||
|
||||
|
||||
<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
|
||||
<img src="/images/factory/kerberos-factory-nodes.png" style="width: 100%"/><br/>
|
||||
|
||||
## Deployments
|
||||
|
||||
The deployments section will list all the Kerberos Enterprise agents (running as deployments) that you have deployed inside your cluster. This page gives you access to deploy new Kerberos Enterprise agents one by one or in bulk. Next to that you can easily upgrade Kerberos Enterprise agents to a newer version, reboot them, view logging and update the configuration options of the Kerberos Enterprise agent.
|
||||
|
||||
|
||||
<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
|
||||
<img src="/images/factory/kerberos-factory-deployments.png" style="width: 100%"/><br/>
|
||||
|
||||
### Adding a new deployment
|
||||
|
||||
There are two options to add a new deployment, single deployments and bulk deployment.
|
||||
|
||||
|
||||
<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
|
||||
<img src="/images/factory/single-bulk-deployment.gif" style="width: 100%"/><br/>
|
||||
|
||||
- single deployment
|
||||
|
||||
By specifying a name for your deployment and it's corresponding RTSP url, a new deployment will be created for you, and deployed to one of your installed nodes.
|
||||
By specifying a name for your deployment, and it's corresponding RTSP url, a new deployment will be created for you, and deployed to one of your installed nodes.
|
||||
|
||||
- in bulk deployment.
|
||||
|
||||
@@ -82,15 +79,13 @@ By importing an Excel file, deployments can be created in bulk.
|
||||
|
||||
By specifying the name and corresponding RTSP url in multiple rows, you can deploy your deployments in bulk.
|
||||
|
||||
|
||||
<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
|
||||
<img src="/images/factory/kerberos-factory-add-bulk-deployment-excel.png" style="width: 100%"/><br/>
|
||||
|
||||
### Configuring a deployment
|
||||
|
||||
Once you have a running deployment, you should see a green circle next to the deployment, indicating that it is succesfully running. At any time you can configure your deployments by clicking on the <SettingsIcon className="pointer"/> icon. This will open a popup, allowing you to change some settings.
|
||||
|
||||
|
||||
<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
|
||||
<img src="/images/factory/deployment-configuration.gif" style="width: 100%"/><br/>
|
||||
|
||||
Following settings can be changed:
|
||||
|
||||
@@ -106,8 +101,7 @@ Configuration can be specified on a Kerberos Enterprise agent level, this means
|
||||
|
||||
By specifying configurations at a higher level, any Kerberos Enterprise agents will inherit from that configuration, improving the overall maintenance and management of your Kerberos Enterprise agents.
|
||||
|
||||
|
||||
<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
|
||||
<img src="/images/factory/global-configuration.gif" style="width: 100%"/><br/>
|
||||
|
||||
### Upgrade or reboot a Kerberos Enterprise agent
|
||||
|
||||
@@ -115,15 +109,13 @@ At Kerberos.io we have fast development cycles, which means that new versions wi
|
||||
|
||||
At any moment you can reboot your Kerberos Enterprise agent. When pressing the reboot button, next to your deployment, Kubernetes will destroy the pod of your deployment, and schedule a new one. This comes in handy, when you noticed one of your Kerberos Enterprise agents is in a stale state.
|
||||
|
||||
|
||||
<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
|
||||
<img src="/images/factory/upgrade-reboot.gif" style="width: 100%"/><br/>
|
||||
|
||||
## Pods
|
||||
|
||||
When creating a Kerberos Enterprise agent, Kubernetes will create a deployment and schedule a pod. This pod will be managed by your deployment, and deployed as a Docker container to one of your available nodes. Once a pod dies/ crashes, or whatever unexpected scenario, the deployment will make sure it is deployed again to a different (or the same) node. This makes sure the Kerberos Enterprise agent is in a healthy state at all times.
|
||||
|
||||
|
||||
<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
|
||||
<img src="/images/factory/kerberos-factory-pods.png" style="width: 100%"/><br/>
|
||||
|
||||
## Storage and video management
|
||||
|
||||
@@ -137,8 +129,7 @@ Kerberos Enterprise stores its recordings locally for a short amount of time. Th
|
||||
|
||||
On the other hand it's an open platform, as it allows you build extensions and integrations (web apps, mobile apps, machine learning services much more). Kerberos Vault ships with the ability of real-time messaging (Kafka) and a REST API (documented as Swaggger).
|
||||
|
||||
|
||||
<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
|
||||
<img src="/images/factory/kerberos-storage.png" style="width: 100%"/><br/>
|
||||
|
||||
To connect one or more Kerberos Enterprise agents to your Kerberos Vault instance, you should open the configuration option and navigate to the `cloud` tab. Once selected you need to fill-in the credentials from your Kerberos Vault account.
|
||||
|
||||
@@ -152,9 +143,7 @@ To connect one or more Kerberos Enterprise agents to your Kerberos Vault instanc
|
||||
|
||||
- Secret Access Key: this should match the secret access key of one of your Kerberos Vault accounts.
|
||||
|
||||
|
||||
|
||||
<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
|
||||
<img src="/images/factory/kerberos-enterprise-storage-setup.gif" style="width: 100%"/><br/>
|
||||
|
||||
### Kerberos Hub
|
||||
|
||||
@@ -164,8 +153,7 @@ You have two choices when using Kerberos Hub, either you send your recordings fr
|
||||
|
||||
Select the Kerberos Hub option, and copy-paste the credentials from your Kerberos Hub subscription.
|
||||
|
||||
|
||||
<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
|
||||
<img src="/images/factory/kerberos-enterprise-to-cloud.gif" style="width: 100%"/><br/>
|
||||
|
||||
- Region: this is the region where your recordings will be stored. Only `eu-west-1` for now (will change, on the roadmap).
|
||||
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
enterprise:
|
||||
parent: "enterprise"
|
||||
weight: 303
|
||||
toc: true
|
||||
@@ -175,4 +175,4 @@ It should look like this.
|
||||
|
||||
Once everything is configured correctly your cluster and DNS, you should be able to setup the Factory application. By navigating to the Factory domain `factory.domain.com` in your browser you will see the Factory login page showing up.
|
||||
|
||||
|
||||
<img src="/images/factory/kerberos-factory-loginpage.png" style="width: 100%"/>
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
enterprise:
|
||||
parent: "enterprise"
|
||||
weight: 304
|
||||
toc: true
|
||||
@@ -15,7 +15,7 @@ toc: true
|
||||
|
||||
Welcome to the Kerberos Enterprise Edge installation. This is the way to go if you want to install Kerberos Enterprise on your Baremetal infrastructure or inside your Private Cloud.
|
||||
|
||||
|
||||
<img src="/images/prologue/deployments/onpremise-more-then-5.svg" style="width: 100%"/>
|
||||
|
||||
Before we can actual start installing the different deployments in our cluster, we need to make sure we have one available.
|
||||
|
||||
@@ -254,4 +254,4 @@ It should look like this.
|
||||
|
||||
Once everything is configured correctly your cluster and DNS, you should be able to setup the Factory application. By navigating to the Factory domain `factory.domain.com` in your browser you will see the Factory login page showing up.
|
||||
|
||||
|
||||
<img src="/images/factory/kerberos-factory-loginpage.png" style="width: 100%"/>
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Installation2"
|
||||
title: "Installation"
|
||||
description: ""
|
||||
lead: ""
|
||||
date: 2020-10-06T08:49:31+00:00
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
enterprise:
|
||||
parent: "enterprise"
|
||||
weight: 302
|
||||
toc: true
|
||||
@@ -17,7 +17,7 @@ Kerberos Enterprise can be installed where Kubernetes can be installed. This mea
|
||||
|
||||
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.
|
||||
|
||||
|
||||
<img src="/images/factory/kerberos-enterprise-kubernetes.png" style="width: 100%"/><br/>
|
||||
|
||||
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.
|
||||
|
||||
@@ -25,7 +25,7 @@ Compared to Kubernetes at the Edge, there are no predefined LoadBalancers, Stora
|
||||
|
||||
Installing 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 Enterprise in such a cluster is just a matter of copy-pasting some configuration (yaml) files, and executing some `kubectl apply` commands.
|
||||
|
||||
|
||||
<img src="/images/prologue/deployments/cloud-more-then-5.svg" style="width: 100%"/>
|
||||
|
||||
Install Kerberos Enterprise on a Kubernetes Service Provider by [following this step-by-step installation guide](/enterprise/installation-cloud).
|
||||
|
||||
@@ -33,7 +33,7 @@ Install Kerberos Enterprise on a Kubernetes Service Provider by [following this
|
||||
|
||||
No need to install Kerberos Enterprise 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 Enterprise to your surveillance infrastructure, the more benefits you will experience (low latency, low bandwidth, etc).
|
||||
|
||||
|
||||
<img src="/images/prologue/deployments/onpremise-more-then-5.svg" style="width: 100%"/>
|
||||
|
||||
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 ssttraight forward as well. You can't simple expect a: click, click, 💥 approach.
|
||||
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
enterprise:
|
||||
parent: "enterprise"
|
||||
weight: 305
|
||||
toc: true
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
help:
|
||||
parent: "help"
|
||||
weight: 630
|
||||
toc: true
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-11-12T13:26:54+01:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
help:
|
||||
parent: "help"
|
||||
weight: 610
|
||||
toc: true
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-11-12T15:22:20+01:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
help:
|
||||
parent: "help"
|
||||
weight: 620
|
||||
toc: true
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "First things first4"
|
||||
title: "First things first"
|
||||
description: ""
|
||||
lead: ""
|
||||
date: 2020-10-06T08:49:31+00:00
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
hub:
|
||||
parent: "hub"
|
||||
weight: 300
|
||||
toc: true
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Get Started4"
|
||||
title: "Get Started"
|
||||
description: ""
|
||||
lead: ""
|
||||
date: 2020-10-06T08:49:31+00:00
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
hub:
|
||||
parent: "hub"
|
||||
weight: 301
|
||||
toc: true
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Installation4"
|
||||
title: "Installation"
|
||||
description: ""
|
||||
lead: ""
|
||||
date: 2020-10-06T08:49:31+00:00
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
hub:
|
||||
parent: "hub"
|
||||
weight: 302
|
||||
toc: true
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Releases4"
|
||||
title: "Releases"
|
||||
description: ""
|
||||
lead: ""
|
||||
date: 2020-10-06T08:49:31+00:00
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
hub:
|
||||
parent: "hub"
|
||||
weight: 303
|
||||
toc: true
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
opensource:
|
||||
parent: "opensource"
|
||||
weight: 208
|
||||
toc: true
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
opensource:
|
||||
parent: "opensource"
|
||||
weight: 201
|
||||
toc: true
|
||||
BIN
content/opensource/get-started/dashboard.png
Normal file
BIN
content/opensource/get-started/dashboard.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 157 KiB |
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
opensource:
|
||||
parent: "opensource"
|
||||
weight: 202
|
||||
toc: true
|
||||
@@ -31,7 +31,7 @@ When you've finished the welcome page, you will be redirected to the login page
|
||||
|
||||
After you have signed in successfully, you will land on the dashboard page. This page will give you an overview of some simple statistics. Such as the the activity per day, per hour, etc.
|
||||
|
||||
<img src="/images/opensource/kerberos-opensource-dashboard.png" style="width: 100%"/>
|
||||
{{< figure src="dashboard.png" alt="Dashboard" caption="This is my caption">}}
|
||||
|
||||
## Media
|
||||
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
opensource:
|
||||
parent: "opensource"
|
||||
weight: 204
|
||||
toc: true
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
opensource:
|
||||
parent: "opensource"
|
||||
weight: 203
|
||||
toc: true
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
opensource:
|
||||
parent: "opensource"
|
||||
weight: 206
|
||||
toc: true
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
opensource:
|
||||
parent: "opensource"
|
||||
weight: 209
|
||||
toc: true
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
opensource:
|
||||
parent: "opensource"
|
||||
weight: 205
|
||||
toc: true
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
opensource:
|
||||
parent: "opensource"
|
||||
weight: 207
|
||||
toc: true
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
opensource:
|
||||
parent: "opensource"
|
||||
weight: 210
|
||||
toc: true
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
opensourcev3:
|
||||
parent: "opensourcev3"
|
||||
weight: 300
|
||||
toc: true
|
||||
@@ -1,85 +0,0 @@
|
||||
---
|
||||
title: "First things first3"
|
||||
description: ""
|
||||
lead: ""
|
||||
date: 2020-10-06T08:49:31+00:00
|
||||
lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
parent: "vault"
|
||||
weight: 300
|
||||
toc: true
|
||||
---
|
||||
|
||||
Kerberos Opensource and Kerberos Enterprise both store recordings on the local disk. To centralise your data at a single place, additional solutions are available.
|
||||
|
||||
## The options
|
||||
|
||||
### Kerberos Hub
|
||||
|
||||
One or more Kerberos Enterprise agents, can store their data directly on [Kerberos Hub](/cloud), and benefit from the visualisation layer Kerberos Hub offers. When doing this your recordings will be uploaded inside the Kerberos datacenter (which is a black box for you).
|
||||
|
||||
### Kerberos Storage
|
||||
|
||||
In addition to that you have the option to Bring Your Own Storage (BYOS), using Kerberos Storage. Kerberos Storage allows you to configure the storage providers you want, and allows you to connect to [Kerberos Hub](/cloud) in parrallel. These storage provider could live in the cloud such as AWS S3, GCP storage and Azure Blob store, or can be located on premise - at the edge - such as Minio.
|
||||
|
||||
Despite the flexible storage capabilities, Kerberos Storage is also an open platform, which can be used to build extensions (mobile apps, web apps, machine learning services, etc) and integrations. It allows you to leverage a scalable and stable system as a strong backbone for your video analytics solutions, machine learning algorithms, and more.
|
||||
|
||||
## Kerberos Hub
|
||||
|
||||
Within Kerberos Open Source an Kerberos Enterprise you can upload your recordings to our [Kerberos Hub](/cloud) environment. This means that your data will be hosted and processed (metadata) in our Kerberos datacenter. For more information about how Kerberos Hub works [can be found here](/cloud).
|
||||
|
||||
|
||||
|
||||
## Kerberos Storage
|
||||
|
||||
If you are using Kerberos Enterprise you have the possibility to bring your own cloud storage or on premise storage. By installing Kerberos Storage you can send your recordings to your own datacenter, private or public cloud. Following providers are supported:
|
||||
|
||||
- [Google Cloud Platform Storage](https://cloud.google.com/storage)
|
||||
- [Microsoft Azure Storage](https://azure.microsoft.com/en-us/services/storage/)
|
||||
- [Amazon Web Services S3](https://aws.amazon.com/s3/)
|
||||
- [Minio](https://min.io/)
|
||||
|
||||
When installing Kerberos Storage in the cloud, following architecture can apply. Having your Kerberos Enterprise agents running at the edge, but uploading to Kerberos Storage in the cloud.
|
||||
|
||||
|
||||
|
||||
On the other hand you could also have Kerberos Storage running at the edge, next to your Kubernetes Enterprise agents. This could be useful if you want to do processing or video analytics suchs as computer bision or machine learning at the edge.
|
||||
|
||||
|
||||
|
||||
### Events
|
||||
|
||||
One of the key differentiators compared to other VMS solutions, is the abilitity to extend and integrate. Next to uploading and persisting data, Kerberos Storage can also trigger events. Each time a recording is send to Kerberos Storage an event can be triggered through one of the following providers.
|
||||
|
||||
- [Apache Kafka](https://kafka.apache.org/)
|
||||
- [Amazon Web Services SQS](https://aws.amazon.com/sqs/)
|
||||
|
||||
Those events can be fetched or subscribed by custom applications. For example, one can create a notifications service, machine learning service or an entire cloud application. Allowing you to leverage the power and scalability of Kerberos Enterprise, and building and focussing on your specific applications, API's, mobile apps, or whatever you have in mind to build.
|
||||
|
||||
|
||||
|
||||
### On-Demand upload
|
||||
|
||||
Next to the extension and integration capabilities of Kerberos Storage, we are currently working on a feature called On-Demand upload. On-Demand upload allows you to upload a subset of your recordings to a Kerberos Storage in the cloud.
|
||||
|
||||
|
||||
|
||||
A couple of usecases are the following ones:
|
||||
|
||||
- Continious recording: having continious recordings stored in your Kerberos Storage on premise, you don't want to replicate all your recordings to a Kerberos Storage provider in the cloud (to make them public available). Therefore you could implement custom logic, for example based on a machine learning algorithm, to only replicate recordings which matche a specific scenario.
|
||||
|
||||
- On-Demand request: Having Kerberos Hub, an end-user could initiate a request for upload. By default no recordings are forwarded from your Kerberos Storage on premise to your Kerberos Storage in the cloud. Only when an end user requests one or more recordings, the
|
||||
upload will start for the requested recordings.
|
||||
|
||||
### Open API
|
||||
|
||||
Both Kerberos Enterprise as Kerberos Storage ships with Swagger API's, which can be used to communicate with the previously mentioned systems. Simply type `/swagger/index.html` after the `api` url, and you will see the Swagger UI popping up. No need to explain the different API's, use the Swagger and see what is available. See something missing, let us know, and we add it ;).
|
||||
|
||||
|
||||
|
||||
## Licensing
|
||||
|
||||
Kerberos Storage is publicly available and **requires a license key** to operate correctly. Reach out to **cedric@verstraeten.io** for the commercial matters.
|
||||
580
content/vault/first-things-first/arch-edge-kerberos-vault.svg
Normal file
580
content/vault/first-things-first/arch-edge-kerberos-vault.svg
Normal file
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 250 KiB |
655
content/vault/first-things-first/arch-kerberos-hub.svg
Normal file
655
content/vault/first-things-first/arch-kerberos-hub.svg
Normal file
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 279 KiB |
653
content/vault/first-things-first/arch-kerberos-vault-events.svg
Normal file
653
content/vault/first-things-first/arch-kerberos-vault-events.svg
Normal file
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 279 KiB |
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 279 KiB |
708
content/vault/first-things-first/arch-sync-kerberos-vault.svg
Normal file
708
content/vault/first-things-first/arch-sync-kerberos-vault.svg
Normal file
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 303 KiB |
83
content/vault/first-things-first/index.md
Normal file
83
content/vault/first-things-first/index.md
Normal file
@@ -0,0 +1,83 @@
|
||||
---
|
||||
title: "First things first"
|
||||
description: ""
|
||||
lead: ""
|
||||
date: 2020-10-06T08:49:31+00:00
|
||||
lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
vault:
|
||||
parent: "vault"
|
||||
weight: 300
|
||||
toc: true
|
||||
---
|
||||
|
||||
Kerberos Opensource and Kerberos Enterprise both store recordings on the local disk. To centralise your data at a single place, additional solutions are available.
|
||||
|
||||
#### Kerberos Hub
|
||||
|
||||
One or more Kerberos Enterprise agents, can store their data directly on [Kerberos Hub](/hub/first-things-first), and benefit from the visualisation layer Kerberos Hub offers. When doing this your recordings will be uploaded inside the Kerberos datacenter (which is a black box for you).
|
||||
|
||||
#### Kerberos Vault
|
||||
|
||||
In addition to that you have the option to Bring Your Own Storage (BYOS), using Kerberos Vault. Kerberos Vault allows you to configure the storage providers you want, and allows you to connect to [Kerberos Hub](/hub/first-things-first) in parrallel. These storage provider could live in the cloud such as AWS S3, GCP storage and Azure Blob store, or can be located on premise - at the edge - such as Minio.
|
||||
|
||||
Despite the flexible storage capabilities, Kerberos Vault is also an open platform, which can be used to build extensions (mobile apps, web apps, machine learning services, etc) and integrations. It allows you to leverage a scalable and stable system as a strong backbone for your video analytics solutions, machine learning algorithms, and more.
|
||||
|
||||
## Kerberos Hub
|
||||
|
||||
Within Kerberos Opensource and Kerberos Enterprise you can upload your recordings to our public [Kerberos Hub](/hub/first-things-first) environment. This means that your data will be hosted and processed (metadata) in our Kerberos Vault (datacenteR). For more information about how Kerberos Hub works [can be found here](/hub/first-things-first).
|
||||
|
||||
{{< figure src="arch-kerberos-hub.svg" alt="Store your recordings in Kerberos Hub" caption="Store your recordings in Kerberos Hub" class="stretch">}}
|
||||
|
||||
## Kerberos Vault
|
||||
|
||||
If you are using Kerberos Enterprise you have the possibility to bring your own cloud storage or on premise storage. By installing Kerberos Vault you can send your recordings to your own datacenter, private or public cloud. Following providers are supported:
|
||||
|
||||
- [Google Cloud Platform Storage](https://cloud.google.com/storage)
|
||||
- [Microsoft Azure Storage](https://azure.microsoft.com/en-us/services/storage/)
|
||||
- [Amazon Web Services S3](https://aws.amazon.com/s3/)
|
||||
- [Minio](https://min.io/)
|
||||
|
||||
When installing Kerberos Vault in the cloud, following architecture can apply. Having your Kerberos Enterprise agents running at the edge, but uploading to Kerberos Vault in the cloud.
|
||||
|
||||
{{< figure src="arch-kerberos-vault-providers.svg" alt="Bring your own storage using Kerberos Vault" caption="Bring your own storage using Kerberos Vault" class="stretch">}}
|
||||
|
||||
On the other hand you could also have Kerberos Vault running at the edge, next to your Kubernetes Enterprise agents. This could be useful if you want to do processing or video analytics such as computer vision or machine learning at the edge.
|
||||
|
||||
{{< figure src="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">}}
|
||||
|
||||
### Events
|
||||
|
||||
One of the key differentiators compared to other VMS solutions, is the abilitity to extend and integrate. Next to uploading and persisting data, Kerberos Vault can also trigger events. Each time a recording is send to Kerberos Vault an event can be triggered through one of the following providers.
|
||||
|
||||
- [Apache Kafka](https://kafka.apache.org/)
|
||||
- [Amazon Web Services SQS](https://aws.amazon.com/sqs/)
|
||||
|
||||
Those events can be fetched or subscribed by custom applications. For example, one can create a notifications service, machine learning service or an entire cloud application. Allowing you to leverage the power and scalability of Kerberos Enterprise, and building and focussing on your specific applications, API's, mobile apps, or whatever you have in mind to build.
|
||||
|
||||
{{< figure src="arch-kerberos-vault-events.svg" alt="Build integrations and create your own workflows using the event capability of Kerberos Vault." caption="Build integrations and create your own workflows using the event capability of Kerberos Vault." class="stretch">}}
|
||||
|
||||
### On-demand upload
|
||||
|
||||
Next to the extension and integration capabilities of Kerberos Vault, it is also possible to synchronise with a central Kerberos Vault. On-Demand upload allows you to synchronise a subset of your recording with an additional Kerberos Vault in the cloud.
|
||||
|
||||
{{< figure src="arch-sync-kerberos-vault.svg" alt="Synchronise recordings between multiple Kerberos Vault" caption="Synchronise recordings between multiple Kerberos Vault" class="stretch">}}
|
||||
|
||||
A couple of usecases are the following ones:
|
||||
|
||||
- Continious recording: having continious recordings stored in your Kerberos Vault on premise, you don't want to replicate all your recordings to a Kerberos Vault provider in the cloud (to make them public available). Therefore you could implement custom logic, for example based on a machine learning algorithm, to only replicate recordings which matche a specific scenario.
|
||||
|
||||
- On-Demand request: Having Kerberos Hub, an end-user could initiate a request for upload. By default no recordings are forwarded from your Kerberos Vault on premise to your Kerberos Vault in the cloud. Only when an end user requests one or more recordings, the
|
||||
upload will start for the requested recordings.
|
||||
|
||||
### Open API
|
||||
|
||||
Both Kerberos Enterprise as Kerberos Vault ships with Swagger API's, which can be used to communicate with the previously mentioned systems. Simply type `/swagger/index.html` after the `api` url, and you will see the Swagger UI popping up. No need to explain the different API's, use the Swagger and see what is available. See something missing, let us know, and we add it ;).
|
||||
|
||||
{{< figure src="open-api.png" alt="All capabilities of Kerberos Vault are documented through swagger API's." caption="All capabilities of Kerberos Vault are documented through swagger API's" class="stretch">}}
|
||||
|
||||
## Licensing
|
||||
|
||||
Kerberos Vault is publicly available and **requires a license key** to operate correctly. Reach out to **cedric@kerberos.io** for the commercial matters.
|
||||
BIN
content/vault/first-things-first/open-api.png
Normal file
BIN
content/vault/first-things-first/open-api.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 245 KiB |
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Get Started3"
|
||||
title: "Get Started"
|
||||
description: ""
|
||||
lead: ""
|
||||
date: 2020-10-06T08:49:31+00:00
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
vault:
|
||||
parent: "vault"
|
||||
weight: 301
|
||||
toc: true
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Cloud Installation3"
|
||||
title: "Cloud Installation"
|
||||
description: ""
|
||||
lead: ""
|
||||
date: 2020-10-06T08:49:31+00:00
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
vault:
|
||||
parent: "vault"
|
||||
weight: 303
|
||||
toc: true
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Edge Installation3"
|
||||
title: "Edge Installation"
|
||||
description: ""
|
||||
lead: ""
|
||||
date: 2020-10-06T08:49:31+00:00
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
vault:
|
||||
parent: "vault"
|
||||
weight: 304
|
||||
toc: true
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Installation3"
|
||||
title: "Installation"
|
||||
description: ""
|
||||
lead: ""
|
||||
date: 2020-10-06T08:49:31+00:00
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
vault:
|
||||
parent: "vault"
|
||||
weight: 302
|
||||
toc: true
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
vault:
|
||||
parent: "vault"
|
||||
weight: 305
|
||||
toc: true
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
vault:
|
||||
parent: "vault"
|
||||
weight: 306
|
||||
toc: true
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Releases3"
|
||||
title: "Releases"
|
||||
description: ""
|
||||
lead: ""
|
||||
date: 2020-10-06T08:49:31+00:00
|
||||
@@ -7,7 +7,7 @@ lastmod: 2020-10-06T08:49:31+00:00
|
||||
draft: false
|
||||
images: []
|
||||
menu:
|
||||
docs:
|
||||
vault:
|
||||
parent: "vault"
|
||||
weight: 307
|
||||
toc: true
|
||||
@@ -9,4 +9,70 @@
|
||||
{{ end -}}
|
||||
</ul>
|
||||
{{ end -}}
|
||||
{{ end -}}
|
||||
{{ range .Site.Menus.opensource -}}
|
||||
<h3>{{ .Name }}</h3>
|
||||
{{ if .HasChildren -}}
|
||||
<ul class="list-unstyled">
|
||||
{{ range .Children -}}
|
||||
{{- $active := or ($currentPage.IsMenuCurrent "opensource" .) ($currentPage.HasMenuCurrent "opensource" .) -}}
|
||||
<li><a class="docs-link{{ if $active }} active{{ end }}" href="{{ .URL | relURL }}">{{ .Name }}</a></li>
|
||||
{{ end -}}
|
||||
</ul>
|
||||
{{ end -}}
|
||||
{{ end -}}
|
||||
{{ range .Site.Menus.opensourcev3 -}}
|
||||
<h3>{{ .Name }}</h3>
|
||||
{{ if .HasChildren -}}
|
||||
<ul class="list-unstyled">
|
||||
{{ range .Children -}}
|
||||
{{- $active := or ($currentPage.IsMenuCurrent "opensourcev3" .) ($currentPage.HasMenuCurrent "opensourcev3" .) -}}
|
||||
<li><a class="docs-link{{ if $active }} active{{ end }}" href="{{ .URL | relURL }}">{{ .Name }}</a></li>
|
||||
{{ end -}}
|
||||
</ul>
|
||||
{{ end -}}
|
||||
{{ end -}}
|
||||
{{ range .Site.Menus.enterprise -}}
|
||||
<h3>{{ .Name }}</h3>
|
||||
{{ if .HasChildren -}}
|
||||
<ul class="list-unstyled">
|
||||
{{ range .Children -}}
|
||||
{{- $active := or ($currentPage.IsMenuCurrent "enterprise" .) ($currentPage.HasMenuCurrent "enterprise" .) -}}
|
||||
<li><a class="docs-link{{ if $active }} active{{ end }}" href="{{ .URL | relURL }}">{{ .Name }}</a></li>
|
||||
{{ end -}}
|
||||
</ul>
|
||||
{{ end -}}
|
||||
{{ end -}}
|
||||
{{ range .Site.Menus.vault -}}
|
||||
<h3>{{ .Name }}</h3>
|
||||
{{ if .HasChildren -}}
|
||||
<ul class="list-unstyled">
|
||||
{{ range .Children -}}
|
||||
{{- $active := or ($currentPage.IsMenuCurrent "vault" .) ($currentPage.HasMenuCurrent "vault" .) -}}
|
||||
<li><a class="docs-link{{ if $active }} active{{ end }}" href="{{ .URL | relURL }}">{{ .Name }}</a></li>
|
||||
{{ end -}}
|
||||
</ul>
|
||||
{{ end -}}
|
||||
{{ end -}}
|
||||
{{ range .Site.Menus.hub -}}
|
||||
<h3>{{ .Name }}</h3>
|
||||
{{ if .HasChildren -}}
|
||||
<ul class="list-unstyled">
|
||||
{{ range .Children -}}
|
||||
{{- $active := or ($currentPage.IsMenuCurrent "hub" .) ($currentPage.HasMenuCurrent "hub" .) -}}
|
||||
<li><a class="docs-link{{ if $active }} active{{ end }}" href="{{ .URL | relURL }}">{{ .Name }}</a></li>
|
||||
{{ end -}}
|
||||
</ul>
|
||||
{{ end -}}
|
||||
{{ end -}}
|
||||
{{ range .Site.Menus.help -}}
|
||||
<h3>{{ .Name }}</h3>
|
||||
{{ if .HasChildren -}}
|
||||
<ul class="list-unstyled">
|
||||
{{ range .Children -}}
|
||||
{{- $active := or ($currentPage.IsMenuCurrent "help" .) ($currentPage.HasMenuCurrent "help" .) -}}
|
||||
<li><a class="docs-link{{ if $active }} active{{ end }}" href="{{ .URL | relURL }}">{{ .Name }}</a></li>
|
||||
{{ end -}}
|
||||
</ul>
|
||||
{{ end -}}
|
||||
{{ end -}}
|
||||
@@ -10494,6 +10494,15 @@ table {
|
||||
margin-top: -6rem;
|
||||
content: ""; }
|
||||
|
||||
.docs-content figure.stretch img {
|
||||
width: 100%; }
|
||||
|
||||
.docs-content figure figcaption {
|
||||
text-align: center;
|
||||
font-weight: 400;
|
||||
font-size: 13px;
|
||||
padding: 10px 0 0 0; }
|
||||
|
||||
.anchor {
|
||||
visibility: hidden;
|
||||
padding-left: 0.5rem; }
|
||||
|
||||
BIN
static/images/factory/kerberos-enterprise-kubernetes.png
Normal file
BIN
static/images/factory/kerberos-enterprise-kubernetes.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 68 KiB |
653
static/images/storage/kerberos-storage-events.svg
Normal file
653
static/images/storage/kerberos-storage-events.svg
Normal file
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 279 KiB |
BIN
static/images/storage/kerberos-storage-swagger.png
Normal file
BIN
static/images/storage/kerberos-storage-swagger.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 245 KiB |
Reference in New Issue
Block a user