In a scaled-out scenario for Content Delivery Deployers, it is possible to setup a shared file system as the Binary Storage medium for incoming transport packages.
The Deployer Receiver writes these transport package zip files into the Binary Storage folder. Then it is up to the Deployer Workers to read these zip files as they deployer/underploy the content.
Below, we present the configurations for an AWS Elastic File System (EFS) acting as storage medium for transport packages.
Start by simply creating an EFS in AWS console. This whole step might take you 5 minutes :)
AWS is going to generate a hostname where this file system is available and it will give instructions on how to mount it in your server.
The Deployer Receiver writes these transport package zip files into the Binary Storage folder. Then it is up to the Deployer Workers to read these zip files as they deployer/underploy the content.
Below, we present the configurations for an AWS Elastic File System (EFS) acting as storage medium for transport packages.
Start by simply creating an EFS in AWS console. This whole step might take you 5 minutes :)
AWS is going to generate a hostname where this file system is available and it will give instructions on how to mount it in your server.
For example, in Linux CentOS, one can mount an FS using the mount command. The following command will mount the EFS drive under folder /efs01 on the current server:
sudo mount -v -t nfs4 -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2 fs-a17668.efs.eu-west-1.amazonaws.com:/ /efs01
fs-a17668.efs.eu-west-1.amazonaws.com:/ /efs01 nfs4 nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,_netdev 0 0
mount | grep efs01
The response should look something like this:
The response should look something like this:
fs-a17668.efs.eu-west-1.amazonaws.com:/ on /efs01 type nfs4 (rw,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.10.2.173,local_lock=none,addr=10.10.2.145,_netdev)
At this moment, the EFS drive is ready and we can configure it in our deployer-conf.xml:
<BinaryStorage Id="PackageStorage" Adapter="FileSystem">
<Property Name="Path" Value="/efs01/deployer-queues"/>
</BinaryStorage>
The same BinaryStorage node must be present on the Deployer Receiver as well as on all Deployer Workers.
Comments