Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- 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 Veritas Access as an Object Store server
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VII. Configuring cloud storage
- Section VIII. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access 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 Veritas Access. 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 Veritas Access 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.