Differences

This shows you the differences between two versions of the page.

--- cloudappliance/appladmin [2021_03_24 20:17] – steven
+++ cloudappliance/appladmin [2021_06_15 12:28] – jim
@@ Line 6: / Line 6: @@
-The File Fabric is built using open Internet technologies. The base operating system used s hardened Linux CentOS. HTTPD Apache Server is used for serving http requests and for temporary caching memcached is used. File Metadata is stored using a MySQL database.
+The File Fabric is built using open Internet technologies. The base operating system used is hardened Linux CentOS. HTTPD Apache Server is used for serving http requests and for temporary caching memcached is used. File Metadata is stored using a MySQL database.
 The web interface is written in  PHP / HTML / Ajax, and protocol adapters are written using Perl / Python.
@@ Line 14: / Line 14: @@
 A standard firewall friendly secure protocol, HTTPS, is used for communicating with clients.
-The basic premises of the File Fabric is to unify content, whether stored on-cloud and/or on-premises, and provide a single audit, control and encryption point. All files continue to reside in the storage provider with the File Fabric only caching metadata e.g. file name, size (if available), security permissions.
+The basic premise of the File Fabric is to unify dispersed storage content, whether stored on-cloud and/or on-premises, and provide a single audit, control and encryption point. All files continue to reside in the storage provider with the File Fabric only caching metadata e.g. file name, size (if available), security permissions.
 The Apache server is stateless and can run on a separate host from the MySQL DB Server. This allows flexibility in deployment topologies for scalability and high availability using proven deployment configurations supported by Apache web server (e.g. multiple web servers behind a load balancer) and MySQL DB (replication, data sharding).
@@ Line 44: / Line 44: @@
 **Provider Sync Engine**
-The provider Sync Engine s used to discover new data which has been added to the storage provider outside of the File Fabric. This can run in realtime, scheduled and manual mode.
+The provider Sync Engine is used to discover new data which has been added to the storage provider outside of the File Fabric. This can run in realtime, scheduled and manual mode.
   * Real-time: new data is checked every time a storage provider is accessed by and end-user. For optimum performance only relevant subset of data is checked for new data.
@@ Line 64: / Line 64: @@
 **Encryption Engine**
-The Encryption engine s used to encrypt data before sending to a remote cloud provider. It uses 256 bit encryption to encrypt data at rest. Further details on how this works and security can be referenced in the File Fabric Security white paper.
+The Encryption engine s used to encrypt data before sending to a remote cloud provider. It uses [[https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program/details?product=8582|FIPS certified 256 bit encryption]] to encrypt data at rest. Further details on how this works and security can be referenced in the [[https://sme.sc/WP-SME-for-Security|File Fabric Security white paper]].
 **Payment Gateway**
@@ Line 74: / Line 74: @@
 **Storage Connectors**
-The File Fabric supports more that 60 cloud storage providers including Amazon S3, S3 compatible storage, OpenStack, MS Azure, Google Storage, WebDav and FTP.
+The File Fabric supports more that 60 cloud storage providers including Amazon S3, S3 compatible storage, OpenStack, MS Azure, Google Storage, SMB / NAS / SAN, WebDav and FTP/SFTP.
 Additional storage providers can be easily developed using a storage providers native API
@@ Line 216: / Line 216: @@
 **Application Log Location**
-The SME appliacation logs are located at
+The File Fabric application logs are located at
     /var/www/smestorage/sitelogs