Latest version: 5.0.1-1
|
At a Glance |
|
|
Catalog |
System |
|
Category |
Miscellaneous Appliances |
|
User volumes |
yes |
|
Min. memory |
128 MB |
|
OS |
Linux |
|
Constraints |
no |
|
Questions/Comments |
|
The NAS appliance is a shared file storage appliance. It provides file storage accessible over HTTP, NFS, and CIFS file protocols.
The NAS appliance serves files contained within a configured (pluggable) data volume thus providing the ability for the content served by the appliance to be changed easily as well as the ability for the volume to have varied sizes. For example, if NAS is being used to store log files, the data volume does not need to be as large as what may be needed to store content for an Apache server.
The root directory of the volume is shared and the HTTP, NFS, and CIFS (samba) servers see the same volume, at the same root. The NFS server exposes the volume as a shared named /mnt/data. The CIFS server exposes the volume as a share named share. The root directory of the volume is accessible for read-only access by the HTTP server and for read/write access by the NFS and CIFS (samba) server.
The security for HTTP access may be open (no user/pwd), fixed single user/pwd (from property) or from .htpasswd file stored within the root directory of the data volume.
The CIFS access is anonymous. It is assumed that only appliances that are allowed to access the volume are connected to the cifs terminal. This eliminates the need to configure complex security settings on the client and server and makes it possible to simply connect appliances that need file access to the cifs input.
There are three key use cases for the NAS appliance:
Resources
|
Resource |
Minimum |
Maximum |
Default |
|
CPU |
0.1 |
16 |
0.2 |
|
Memory |
128 MB |
32 GB |
256 MB |
|
Bandwidth |
1 Mbps |
2 Gbps |
250 Mbps |
Terminals
|
Name |
Dir |
Protocol |
Description |
|
http |
in |
HTTP |
Terminal on which HTTP requests are received. This terminal is used to access NAS's data volume using the HTTP/1.1 protocol. HTTP requests are served by HTTP server version 2.2.3-31. |
|
nfs |
in |
NFS |
Terminal on which NFS requests are received. This terminal is used to access NAS's data volume using the NFS/3.0 protocol. |
|
cifs |
in |
CIFS |
Terminal on which CIFS requests are received. This terminal is used to access NAS's data volume using the CIFS/1.0 protocol. CIFS requests are served by Samba server version 3.0.28-1. |
|
mon |
out |
CCE |
Sends performance and resource usage statistics. |
The default interface is enabled. This provides the ability for administrators to log into the appliance using the '3t ssh comp' command to perform maintenance or to troubleshoot problems. One possible maintenance activity might be to add/remove users from the .htpasswd file stored on the data volume.
User Volumes
|
Volume |
Description |
|
data |
Read/write volume providing storage for the files to be served by the appliance |
The following file may reside within the root directory on the volume:
|
File |
Description |
|
.htpasswd |
HTTP Password File. If present, this file is inaccessible from the http interface but will be accessible through the cifs interface (so that new users can be added/passwords changed) |
Error Messages
The following messages may appear in either the appliance log file or the system log of the grid controller when the appliance fails to start:
Static Content Server
The following diagram shows a typical usage of NAS for a simple web server application:
Appliances in use:
The nas appliance in this example is used to serve the static content of the web site (for example, images) as it is simple to configure and less resource-demanding, while a separate apache server is set up to serve the dynamic content (for example, forms interface, and so on)
The admin appliance in this example is used to authenticate users and provide access to the cifs terminal of the nas appliance so that an administrator may update the set of files exposed by nas through its http terminal.
Note: The URLSW appliance in this example is not shipped with CA AppLogic® for System z, but can be built using Apache and Nginx. The Apache appliance in this example is not shipped with CA AppLogic® for System z. However, CA AppLogic® for System z does provide a similar appliance named WEB64.
HTTP Access:
web accepts HTTP requests coming to the application and passes them to urlsw through its out terminal. urlsw sends HTTP file requests for dynamic content through its out1 terminal to be served by nas1 on its http terminal. urlsw forwards all other HTTP requests through its aux terminal to be served by Apache.
CIFS Access:
When an administrator needs to modify the set of files made available for HTTP access by nas, the administrator connects and logs into the admin appliance through the maint appliance. The user then mounts the CIFS share exposed by nas (if it is not already mounted) and modifies the files as needed.
Example:
|
Property name |
Value |
Notes |
|
data |
mydata |
Data volume holding the files to be served by the web server |
|
http_url_prefix |
/images |
Root path at which the web server should expose the file system. |
|
http_dir_enabled |
no |
Directory listing is disabled. |
|
http_sec_mode |
none |
No security is enabled for HTTP access. |
|
cifs_read_only |
no |
The CIFS share is exposed for read/write access. |
|
cifs_case_sensitive |
yes |
Enable case sensitive file paths. |
Shared Storage
The following diagram shows a typical usage of NAS as shared storage for multiple application servers.
Appliances in use:
The nas1 appliance in this example is used as shared storage for app1 and app2. Both application servers have read/write access to the directories and files served by nas1.
app1 and app2 issue CIFS requests through their out terminals to the cifs terminal of nas1 to access files stored on the volume shared by nas1. Any changes made by one application server are seen by the other application server.
Example:
|
Property name |
Value |
Notes |
|
data |
mydata |
Data volume holding the files to be shared between the applications |
|
cifs_read_only |
no |
The CIFS share is exposed for read/write access. |
|
cifs_case_sensitive |
yes |
Enable case sensitive file paths. |
Log Server
The following diagram shows a typical usage of NAS as a log server.
Appliances in use:
The logs appliance in this example is used to store the log files for the two web servers and the database server and makes those files available through its http terminal.
The log terminals for the web servers (web1 and web2) and the database server (dbase) are all connected to the cifs terminal of logs so that when they write to their log files, the files are stored on the logdata volume that is configured on logs.
When an administrator needs to inspect the log files, he connects via the admin gateway to the http terminal of the logs appliance. He logs in with the configured administrator user name and password and is shown a listing of the root directory of the logdata volume from which the administrator is free to view the log files he is interested in.
Example:
|
Property name |
Value |
Notes |
|
data |
logdata |
Data volume holding the log files |
|
http_url_prefix |
/logs |
URL root path where log files can be accessed. |
|
http_dir_enabled |
yes |
Directory listing is enabled. |
|
http_sec_mode |
single |
HTTP security mode is single user. |
|
http_user |
admin |
User name for HTTP access. |
|
http_pwd |
admin123 |
User password for HTTP access. |
|
cifs_read_only |
yes |
The CIFS share is exposed for read-only access. |
|
cifs_case_sensitive |
yes |
Enable case sensitive file paths. |
Change the Size of the Data Volume Used by NAS
The features of the http and samba servers are limited and only those features that properties support are exported.
To change the size of the data volume used by NAS
Open Source and Third-Party Software Used on the Appliance
NAS uses the following third-party open source packages in addition to the third-party open source packages used by its base class LUX64.
|
Copyright © 2013 CA.
All rights reserved.
|
|