Gateway has infrastructural support for optional features and extensions (such as Video Clipping for Partial File Restore) that can be drop into a Swarm implementation as desired. (v6.1)
Table of Contents | ||
---|---|---|
|
...
Info |
---|
Best practiceUse Docker and install DataCore's provided container; this avoids dealing with third-party repository choices, dependencies, and resource reconfiguration required to protect Gateway's performance. Installing without the container requires assistance from DataCore Support. |
Copy the package for the feature to a server running Content Gateway:
caringo-FEATURE-VERSION.noarch.rpm
Upgrade to RHEL/CentOS 7 (required by Docker) if the server is running RHEL/CentOS 6.x.
Upgrade Gateway (versions 6.1 and higher support drop-in features such as video clipping) if running Content Gateway 6.0 or earlier.
See Gateway Installation.Upgrade Content UI to support this feature if running version 6.1 or earlier.
See Content UI Installation.Install the package.
Code Block yum install caringo-FEATURE-VERSION.noarch.rpm
The installation creates a
features.d
directory under/etc/caringo/cloudgateway/
, which is where Gateway detects optional, dynamic features.Install any additional frameworks, such as multimedia support via FFmpeg, which DataCore provides preconfigured in a Docker container.
From an Internet-connected machine:Check whether Docker is installed:
docker info
Else, install the Docker package, start the daemon, check its status, and enable it system-wide. See docs.docker.com/install/linux/docker-ce/centos/Verify Docker by running a container test:
Code Block docker run hello-world
Load the provided container:
Code Block docker load < caringo-gateway-VERSION.feature.FEATURE.via.docker.VERSION.x86_64
Gateway creates the following directory for spooling content:
/var/spool/caringo/cloudgateway/features
Gateway refuses to start if it cannot create this directory.In setting
iptables
rules, Docker closes external TCP access to port 80 (although ping and ssh work); be sure to explicitly open port 80 again so clients can access Gateway.Code Block firewall-cmd --add-port=80/tcp --permanent firewall-cmd --reload systemctl restart docker
Repeat the above process on any remaining Content Gateway servers.
Restart the Gateway(s).
On reboot, Content Gateway detects the feature; on a page refresh, Content UI displays the additional functionality, such as the clipping control for video content.
...