Veritas Access Appliance Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Configuring the network
- Configuring authentication services
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- Configuring ISCSI
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Access Appliance as a CIFS server
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Configuring an FTP server
- Using Access Appliance as an Object Store server
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Section VI. Monitoring and troubleshooting
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- Configuring event notifications and audit logs
- Section VII. Provisioning and managing Access Appliance file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- About managing application I/O workloads using maximum IOPS settings
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About the NFS shares
- Creating and maintaining CIFS shares
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- Using Access Appliance with OpenStack
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Compressing files
- Section X. Reference
Creating an OpenStack Manila file share
An OpenStack Manila file share is equivalent to a file system in Access Appliance. You can create an OpenStack Manila file share on the OpenStack controller node.
To create an OpenStack Manila file share on the OpenStack controller node
- On the OpenStack controller node, if you wanted to create two OpenStack Manila file shares called prod_fs and finance_fs of size 1 GB accessible over NFS, enter the following:
One of the file shares resides on va_backend1, and one of the file shares resides on va-backend2.
manila@C4110-R720xd-111045:~/OpenStack$ manila create --name prod_fs --share-type va-backend1 NFS 1
manila@C4110-R720xd-111045:~/OpenStack$ manila create --name finance_fs --share-type va-backend2 NFS 1
Use the manila list command to see how the file shares look on the OpenStack controller node.
You can see how the file systems look on Access Appliance as part of the share creation process.
- Give prod_fs read-write access to 10.182.111.84.
manila@C4110-R720xd-111045:~/OpenStack$ manila access-allow --access-level rw ecba1f14-86b0-4460-a286-a7e938162fb4 ip 10.182.111.84 +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | share_id | ecba1f14-86b0-4460-a286-a7e938162fb4 | | deleted | False | | created_at | 2015-04-28T17:59:45.514849 | | updated_at | None | | access_type | ip | | access_to | 10.182.111.84 | | access_level | rw | | state | new | | deleted_at | None | | id | 8a1c2d0b-a3fc-4405-a8eb-939adb8799db | +--------------+--------------------------------------+
In the manila access-allow command, you can get the ID (ecba1f14-86b0-4460-a286-a7e938162fb4) from the output of the manila list command.
- Give finance_fs read-write access to 10.182.111.81.
manila@C4110-R720xd-111045:~/OpenStack$ manila access-allow --access-level rw f8da8ff6-15e6-4e0c-814b-d6ba8d08543c ip 10.182.111.81 +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | share_id | f8da8ff6-15e6-4e0c-814b-d6ba8d08543c | | deleted | False | | created_at | 2015-04-28T18:01:49.557300 | | updated_at | None | | access_type | ip | | access_to | 10.182.111.81 | | access_level | rw | | state | new | | deleted_at | None | | id | ddcfc2d2-7e71-443a-bd94-81ad05458e32 | +--------------+--------------------------------------+
Use the manila access-list <share-id> command to display the different access given to instances.