Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
cloudappliance/appladmin [2018_02_13 01:56] – cleaned up steven | cloudappliance/appladmin [2020_06_25 13:20] – jim | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | # SME Appliance System | + | # Enterprise File Fabric |
## 1 Software Stack | ## 1 Software Stack | ||
Line 5: | Line 5: | ||
{{:/ | {{:/ | ||
- | The SME platform | + | The File Fabric |
- | The web interface is written in using PHP / HTML / Ajax, and protocol adapters are written using Perl. | + | The web interface is written in PHP / HTML / Ajax, and protocol adapters are written using Perl / Python. |
- | By using standard components | + | By using standard components |
- | A standard firewall friendly protocol HTTPS is used for communicating with the clients. | + | A standard firewall friendly |
- | The basic premises of SME is to act as a cloud gateway | + | The basic premises of the File Fabric |
- | The apache | + | The Apache |
## 2 Components | ## 2 Components | ||
Line 21: | Line 21: | ||
{{:/ | {{:/ | ||
- | SME is built as an open modular platform. All the functionality is available via the SME API and major components have hook points to integrate external system .e.g authentication , a new storage provider, payment gateway etc. | + | The File Fabric |
- | Details of the SME API can be found at: | + | Details of the File Fabric |
- | https:// | + | https:// |
**Protocol Adaptors** | **Protocol Adaptors** | ||
- | At the top of the SME Architecture diagram are protocol adapters | + | At the top of the File Fabric |
- | Out of the box SME supports: | + | Out of the box the File Fabric |
- | * REST/XML and REST/ | + | * REST/XML and REST/ |
- | * WebDav/ | + | * WebDav/ |
* FTP/FTPS: Standard FTP and FTP Secure protocol | * FTP/FTPS: Standard FTP and FTP Secure protocol | ||
Line 41: | Line 41: | ||
**Provider Sync Engine** | **Provider Sync Engine** | ||
- | The provider Sync Engine s used to discover new data added to the provider outside of SME. Can run in realtime, scheduled and manual mode. | + | The provider Sync Engine s used to discover new data which has been added to the storage |
- | * Real-time: new data is checked every time storage provider is accessed. 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 |
- | * Scheduled: storage provider is accessed at schedule | + | * Scheduled: storage provider is accessed at a set scheduled |
- | * Manual: Administrator initiates a sync | + | * Manual: |
- | **Multi-Site Backup Engine** | + | **Multi-Site Backup |
- | Used to backup files updated | + | Used to backup files updated |
**Access Control Module** | **Access Control Module** | ||
- | The ACL module is responsible for applying permissions. Every operation is verified by the access control module to ascertain that the user has permission to perform the operation | + | The ACL module is responsible for applying permissions. Every operation is verified by the access control module to ascertain that the user has permission to perform the operation. |
**Audit Manager** | **Audit Manager** | ||
- | The Audit module is used by all components to generate audit records for all file interactions. The granularity of this can be controlled at a per Organization level. | + | The Audit module is used by all components to generate audit records for all file interactions. The granularity of this can be controlled at a per Organization |
**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 SME Security white paper. | + | 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 |
**Payment Gateway** | **Payment Gateway** | ||
- | The Payment Gateway enables Integration with external billing system and supports PayPal | + | The Payment Gateway |
Custom payment gateways can also be integrated. | Custom payment gateways can also be integrated. | ||
Line 71: | Line 71: | ||
**Storage Connectors** | **Storage Connectors** | ||
- | SME supports more that 60 cloud storage providers including Amazon S3, OpenStack, MS Azure, Google Storage, WebDav and FTP. | + | The File Fabric |
- | Additional providers can be easily developed using a storage providers native API | + | Additional |
**Protocol Adaptors** | **Protocol Adaptors** | ||
- | The protocol adaptors are the front end adaptors that are additional to the SME API. They enable access from a compatible S3 API, FTP/S, or Secure WebDav. | + | The protocol adaptors are the front end adaptors that are additional to the File FabricAPI. They enable access from a compatible S3 API, FTP/S, or Secure WebDav. |
## 3 Administration | ## 3 Administration | ||
Line 110: | Line 110: | ||
**Temporarily Disable selinux** | **Temporarily Disable selinux** | ||
| | ||
- | | + | You can temporarily disable sexlinux by running the following command. |
| | ||
echo 0 >/ | echo 0 >/ | ||
Line 116: | Line 116: | ||
**Enable selinux** | **Enable selinux** | ||
| | ||
- | | + | To enable selinux run the command |
| | ||
echo 1 >/ | echo 1 >/ | ||
Line 122: | Line 122: | ||
**Cloud FTP** | **Cloud FTP** | ||
| | ||
- | | + | CloudFTP is an FTP implementation on top of Clouds that do not natively support FTP. Once a Cloud has been added to an account, you can access it from any FTP Client. |
| | ||
**Stopping CloudFTP** | **Stopping CloudFTP** | ||
Line 148: | Line 148: | ||
**HTTPD Logs** | **HTTPD Logs** | ||
| | ||
- | | + | Httpd server logs are located at / |
| | ||
**HTTPD Configuration** | **HTTPD Configuration** | ||
| | ||
- | | + | HTTPD server configuration files are located in the following 2 directories |
| | ||
/ | / | ||
Line 213: | Line 213: | ||
**Application Log Location** | **Application Log Location** | ||
| | ||
- | | + | The SME appliacation logs are located at |
| | ||
/ | / | ||
| | ||
- | | + | A brief description below |
| | ||
* allmails.txt all sent mails to address and subject are logged here | * allmails.txt all sent mails to address and subject are logged here | ||
Line 230: | Line 230: | ||
{{:/ | {{:/ | ||
- | You can use any tool that support monitoring CentOS | + | You can use any tool that support monitoring CentOS |
We recommend monitoring the following parameters | We recommend monitoring the following parameters |