How do I create publish destinations and transports: SAN?
Publishing your site should always be as easy as pushing a button. It is; however, what needs to come before that can be a little more complicated. In addition to our article Creating Publish Destinations and Transports: SFTP, we now have details for setting up a SAN mount configuration.
Clients may choose to have a directory on their local server mounted directly in the file system of the Web CMS servers. Basically, this option allows a directory tree on a client host to be shared with the Web CMS server essentially as a shared drive: a SAN mount.
For the uninitiated, Webopedia defines SAN as: "a Storage Area Network (SAN) that is a high-speed subnetwork of shared storage devices. A storage device is a machine that contains nothing but a disk or disks for storing data."
There are two types of SAN mounts. A description of each had how to create them follows.
SAN mount using NFS
For a NFS SAN mount, permissions for read/write are granted on a by-host basis, so there is no need to create user permissions. The Web CMS servers will have read/write access for all directories in the SAN mount. If the client server is a Linux system, this is probably the easiest route. If the client server is a Windows system, any files created by the Web CMS on the mounted directory will not be tied to any Windows users and will have unknown Windows permissions.
SAN mount using CIFS
A CIFS SAN mount requires an Active Directory user account in the AD3 domain to be used to mount the directory. For each directory in the SAN mount that the Web CMS will access, the client must grant that user account read/write permission.
Creating a SAN mount
Send a request for creating SAN mount to firstname.lastname@example.org.
Create a Transport
- In Cascade, under the "Administration" tab, select "Transports."
- In the left panel, select "New Transport". Then select "Filesystem" radio button and submit.
- Fill in the appropriate information for your SAN mount in the form and submit:
- System name: is a name/label for this transport (you could have more than one).
- Server Directory: is the path to the SAN mount on the Web CMS servers where stuff will be published. This directory path for most instances will be provided by the uConnect staff and will probably be of form: /net/dcfs.ucdavis.edu/MOUNT_NAME/path
- Select your new transport in the left panel.
- Select the "Test Transport" link and submit.
- If all is well, you should see:
NOTE: a successful test does NOT mean the SAN mount is correctly defined. However, any failure certainly means it is not.