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 [2018_07_27 12:07] – jim | cloudappliance [2020_07_23 20:05] – jim |
|---|
| |
| |
| ====== Storage Made Easy File Fabric====== | ====== Enterprise File Fabric====== |
| |
| |
| \\ | \\ |
| Storage Made Easy provides an On-Premises Enterprise File Fabric solution that is storage agnostic and can be used either with a single storage back-end or multiple public / private storage systems. In the event of the latter the File Fabric unifies the view across all access clients and implements a common control and governance policies through the use of its cloud control features.\\ \\ The product is supplied as a software 'appliance' that is run inside of a hypervisor and consists of a pre-configured 'hardened' operating system (CentOS) and the File Fabric Application provided by Storage Made Easy. | Storage Made Easy provides a multi-cloud Secure Data Management solution that is deployed on-premises, is storage agnostic and can be used either with a single storage back-end or multiple public / private storage systems. In the event of the latter the File Fabric unifies the view across all access clients and implements a common control and governance policies through the use of its cloud control features.\\ \\ The product is supplied as a software 'appliance' that is run inside of a hypervisor and consists of a pre-configured 'hardened' operating system (CentOS) and the File Fabric Application provided by Storage Made Easy. |
| | |
| | |
| | {{ ::eff_architecture_3_.png?600 |}}\\ |
| |
| {{ :sme_appliance.jpg?600 |}}\\ | |
| The File Fabric can be provided as an OVF compliant image or as a VMWARE image. Both of these can work with ESXi, XEN, KVM or Hyper-V infrastructures.\\ \\ The purpose of providing the Appliance in a package manner is to simplify delivery and operation of the File Fabric Application. Deployment of an Appliance in this manner can also eliminate problems with installation and configuration such as software or driver issues. Users simply download a single file and run and configure the Application. | The File Fabric can be provided as an OVF compliant image or as a VMWARE image. Both of these can work with ESXi, XEN, KVM or Hyper-V infrastructures.\\ \\ The purpose of providing the Appliance in a package manner is to simplify delivery and operation of the File Fabric Application. Deployment of an Appliance in this manner can also eliminate problems with installation and configuration such as software or driver issues. Users simply download a single file and run and configure the Application. |
| |
| |
| |
| ===== 2 File Fabric Architecture ===== | ===== 2 File Fabric Logical Architecture ===== |
| |
| |
| {{ ::sme_cloud_control_appliance.jpg?600 |}} | {{ :logical-architecture.png?600 |}} |
| |
| The File Fabric is composed of:\\ \\ The core engine which incorporates:\\ \\ - Security Manager(s)\\ - Audit Manager\\ - Access Control Manager\\ - Sync Engine\\ - Cloud Backup engine\\ \\ The Cloud Control Appliance connects to various clouds on the 'back end' and entry points include:\\ \\ - SME Native Applications\\ - REST / JSON API\\ - WebDav API\\ - FTP / FTPS / SFTP API\\ - S3 API\\ \\ These API's and clients enable entry points to all data irrespective of whether the mapped clouds support such protocols or entry points or not.\\ | The File Fabric is composed of:\\ \\ The core engine which incorporates:\\ \\ - Security Manager(s)\\ - Audit Manager\\ - Access Control Manager\\ - Sync Engine\\ - Cloud Backup engine\\ \\ The Cloud Control Appliance connects to various clouds on the 'back end' and entry points include:\\ \\ - SME Native Applications\\ - REST / JSON API\\ - WebDav API\\ - FTP / FTPS / SFTP API\\ - S3 API\\ \\ These API's and clients enable entry points to all data irrespective of whether the mapped clouds support such protocols or entry points or not.\\ |
| |
