<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vault on</title><link>/vault/</link><description>Recent content in Vault on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Tue, 06 Oct 2020 08:49:15 +0000</lastBuildDate><atom:link href="/vault/index.xml" rel="self" type="application/rss+xml"/><item><title>First things first</title><link>/vault/first-things-first/</link><pubDate>Tue, 06 Oct 2020 08:49:31 +0000</pubDate><guid>/vault/first-things-first/</guid><description>It all starts with your Kerberos Agents. You might set up one or more agents at several locations, sites, rooms, offices, etc. Each Kerberos Agent will monitor a particular video stream and persist recordings on a local disk; taking into account the specific conditions such as region of interest, time window, etc.
While growing your video landscape, and adding more and more Kerberos Agents, it will become interesting, and probably also required to have a central place of storage.</description></item><item><title>Getting Started</title><link>/vault/getting-started/</link><pubDate>Tue, 06 Oct 2020 08:49:31 +0000</pubDate><guid>/vault/getting-started/</guid><description>Once you&amp;rsquo;ve installed Kerberos Vault, you should have access to the Kerberos Vault application. The application allows you to administrate Kerberos Vault, and more specifically create storage providers, integrations and accounts, through a single interface. Isn&amp;rsquo;t that great.
Having a UI in place, it is important to note that Kerberos Vault also ships numerous APIs, that allow you to automate the configurations. The APIs are exposed as, Swagger documentation, and can be used for configuration of Kerberos Vault but also integration and development of custom applications or business logic.</description></item><item><title>Installation</title><link>/vault/installation/</link><pubDate>Tue, 06 Oct 2020 08:49:31 +0000</pubDate><guid>/vault/installation/</guid><description>Kerberos Vault is shipped as a container image and is preferably installed inside a Kubernetes cluster. This means that you can run it where and how you want. Depending on your setup, home installation or production ready deployment, you might decide to install it using standard Docker or Kubernetes depending on your needs and requirements.
Docker You can quickly ramp-up Kerberos Vault by using docker compose. We have provided a docker-compose.</description></item><item><title>Configuration</title><link>/vault/configuration/</link><pubDate>Tue, 06 Oct 2020 08:49:31 +0000</pubDate><guid>/vault/configuration/</guid><description>Once you have set up Kerberos Vault successfully on your Kubernetes cluster, it is time to set it up and configure the different elements.
The steps we have to go through to get a functional Kerberos Vault are as following,
Mount and connect a storage provider, implement and configure one or more integrations, create an account, so Kerberos Vault can be consumed. 1. Providers Storage providers are the foundation of Kerberos Vault.</description></item><item><title>Providers</title><link>/vault/providers/</link><pubDate>Tue, 06 Oct 2020 08:49:31 +0000</pubDate><guid>/vault/providers/</guid><description>When deploying Kerberos Agents you have the possibility to Bring Your Own Storage; at the edge or in the cloud. By configuring Kerberos Vault you persist your recordings in your preferred storage providers. Following providers are supported:
Google Cloud Platform Storage Amazon Web Services S3 Storj Minio Ceph Kerberos Vault allows you to attach one or more (and different) storage providers. Depending on the use case: Kerberos Vault in a cloud environment or at the edge, you will opt for a specific storage provider.</description></item><item><title>Integrations</title><link>/vault/integrations/</link><pubDate>Tue, 06 Oct 2020 08:49:31 +0000</pubDate><guid>/vault/integrations/</guid><description>One of the key differentiators, is the ability to extend and integrate. Next to uploading and persisting recordings on your preferred storage providers, Kerberos Vault can trigger events and be configured through APIs.
Each time a Kerberos Agent sends a recording to Kerberos Vault, it is persisted on a storage provider, and an event is triggered through one of the following integrations.
Apache Kafka Amazon Web Services SQS Kerberos Hub Kerberos Vault (remote forwarding) Every time an event is delivered, it will be consumed by the configured integrations.</description></item><item><title>Accounts</title><link>/vault/accounts/</link><pubDate>Tue, 06 Oct 2020 08:49:31 +0000</pubDate><guid>/vault/accounts/</guid><description>Having setup Providers and Integrations, you need a secure way to interact with them through the creation of an account.
By creating an account you will receive credentials that give access to the Kerberos Vault&amp;rsquo;s providers, integrations and APIs. Account credentials are being used by a Kerberos Agent to send recordings, and/or through custom code by API calls to download and/or forward recordings.
Prerequisites Before you can configure a provider, make sure you have installed a Kerberos Vault inside a Kubernetes cluster.</description></item><item><title>Machine learning</title><link>/vault/machine-learning/</link><pubDate>Tue, 06 Oct 2020 08:49:31 +0000</pubDate><guid>/vault/machine-learning/</guid><description>Machine learning or computer vision at scale is one of the key motivations of the entire Kerberos Enterprise Suite. All services going from Kerberos Agents, Kerberos Vault to Kerberos Hub are designed in such a way that you can scale them independently of each other.
The design principle of Kerberos Enterprise Suite allows to decouple videos streams from any CPU or GPU workloads, through the creation of video chunks, queueing and event messaging.</description></item><item><title>Forwarding</title><link>/vault/forwarding/</link><pubDate>Tue, 06 Oct 2020 08:49:31 +0000</pubDate><guid>/vault/forwarding/</guid><description>Multiple Kerberos Vaults can be installed in your video landscape. You may have Kerberos Vaults at the edge and/or in a cloud environment, connected to edge and/or cloud storage providers.
Kerberos Vaults can be chained and configured in forwarding mode. This configuration makes it possible to enable offline capabilities and keep the majority of your recordings at the edge. Only a subset of your recordings will be transferred from the edge to the cloud by requesting a forward from Kerberos Hub or building your own forwarding application code.</description></item><item><title>License</title><link>/vault/license/</link><pubDate>Tue, 06 Oct 2020 08:49:31 +0000</pubDate><guid>/vault/license/</guid><description>Kerberos Vault is a closed source solution but is made available free of charge. The solution and its source code is maintained by the Kerberos.io development team, and made available as binaries through a Docker container. Kerberos Vault, and its related binaries, can be used under the MIT license.
The MIT License (MIT) Copyright © 2021 Kerberos.io
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:</description></item></channel></rss>