Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
cloudappliance/appladmin [2020_06_25 13:51] – jimcloudappliance/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. 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. 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). 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** **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.   * 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** **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** **Payment Gateway**
Line 74: Line 74:
 **Storage Connectors** **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 Additional storage providers can be easily developed using a storage providers native API
Line 216: Line 216:
 **Application Log Location** **Application Log Location**
      
-The SME appliacation logs are located at+The File Fabric application logs are located at
      
     /var/www/smestorage/sitelogs     /var/www/smestorage/sitelogs
Line 228: Line 228:
  
  
-## 4 Monitoring+## Appliance Monitoring
  
- +See [[[cloudappliance/monitoring|]].
-{{:/cloudappliance:appladmin:steps:sme_4_monitoring.png}} +
- +
-You can use any tool that support monitoring CentOS 7. +
- +
-We recommend monitoring the following parameters +
- +
-**Base OS** +
- +
-    vmstat     +
-    Procs            +
-    r: The number of processes waiting for run time.            +
-    b: The number of processes in uninterruptible sleep.      +
-    Memory            +
-    swpd: the amount of virtual memory used.            +
-    free: the amount of idle memory.            +
-    active: the amount of active memory.        +
-    Swap            +
-    si: Amount of memory swapped in from disk (/s).            +
-    so: Amount of memory swapped to disk (/s).      +
-    IO            +
-    bi: Blocks received from a block device (blocks/s).            +
-    bo: Blocks sent to a block device (blocks/s).      +
-    CPU            +
-    us: Time spent running non-kernel code. (user time, including nice time)            +
-    sy: Time spent running kernel code. (system time)            +
-    id: Time spent idle.              +
-    st: Time stolen from a virtual machine.%%'' +
- +
-**Disk Space** +
- +
-    df -k +
-    Filesystem                1K-blocks         Used Available Use% Mounted on/dev/mapper/VolGroup00-LogVol00                                 18187836    2903080   14345956   17% //dev/sda1 +
-         101086        20047      75820   21% /boottmpfs +
-         512468            0     512468    0% /dev/shm%%' +
- +
-**MySQL** +
- +
-**Number of connections** +
- +
-    SHOW STATUS LIKE "Connections" +
- +
-**Network Usage** +
- +
-Monitor the network traffic using your monitoring system. Or you can get the information from +
- +
-    cat /proc/net/dev +
- +
-**Total Number of Processes** +
- +
-    ps -e|sed 1d|wc -l +
- +
-**Recipes** +
- +
-**Increasing Disk Space** +
- +
-To increase the disk space please follow the instructions at the following [[http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1006371|vmware kb article]] +
- +
-**Attaching a new Disk to The Appliance** +
- +
-To add a new disk to the appliance please follow the instructions at the following [[http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003940|vmware kb article]] +
- +
-**Using a New Disk as Local Storage** +
- +
-The appliance is already configured with an FTP server listening on ip address 127.0.0.1 and port 2001. +
- +
-  * Add a new user with user home directory located on the newly attached disk mounted at _newdisk_ +
- +
-        adduser   -b /newdisk   -s /sbin/nologin localstorage#change the  +
- +
-        passwd localstorage +
- +
-  * Set home directory context for ///newdisk/localstorage// +
- +
-        chcon -R -t user_home_dir_t   /newdisk/localstorage +
- +
-  * Now you can add the a FTP provider to your SME account using the credentials +
-    - account login:localstorage +
-    - account password: the password you entered for localstorage user +
-    - server host:ftp://127.0.0.1 +
-    - server port:2001 +
-    - server home directory:/ +
- +
- +
-**Production CheckList** +
- +
-  * [ ] SSL certificate Installed +
-  * [ ]Once you have installed SSL certificates enable https only in the configuration +
-  * [ ] Only have inbound port **443** open. If you are using CloudFTP then also open port **21** and **990** +
-  * [ ] Permanent IP address Configured +
-  * [ ] DNS Names Configured. Make sure webdav DNS is configured as webdav<DomaninName> e.g. if domain name is sme.yourdomain.com then webdav url should be webdavsme.yourdomain.com. +
-  * [ ] Passwords changed for default users +
-  * [ ] The date and time is set correctly in the appliance and not drifting.+
  
© Copyright 2024 Nasuni.