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 a new share backend on the OpenStack controller node
A backend is an instance of the OpenStack Manila share service, which is defined in a section of the manila.conf file. Each backend has exactly one driver.
To create a new share backend va-share1 in OpenStack Manila, make the following changes on the OpenStack controller node, and restart the OpenStack Manila driver.
To create a new share backend on the OpenStack controller node
- On the OpenStack controller node, add the following configuration entries in the OpenStack Manila
/etc/manila/manila.conf
file.In the DEFAULT section, add the following:
##### enabled_share_backends=va-share1 #####
If the entry generic1 is already there, add the va-share1 entry after a comma. For example:
enabled_share_backends = generic1,va-share1
At the end of all sections in the
/etc/manila/manila.conf
file, add the following configuration entries:##### [va-share1] share_driver= manila.share.drivers.veritas.veritas_isa.VeritasShareDriver driver_handles_share_servers = False share_backend_name = va-share1 va_server_ip = 10.182.96.179 va_port = 14161 va_fstype = simple va_user = master va_pwd = password va_pool = pool1 #####
The following table describes the options.
share_backend_name
Name of the share backend. This name can be different for each share backend.
share_driver
OpenStack Manila driver name.
va_server_ip
Console IP address of the Veritas Access cluster.
va_port
14161
The port on Veritas Access to which the Manila driver is connected.
va_fstype
Type of file system to be created on the specified pool. It can be simple.
va_user
Root user name.
va_pwd
Root password.
va_pool
Existing storage pool on Veritas Access from which the file systems are to be created.
You use the OPENSTACK> manila configure command to display the configuration options that need to be performed on the OpenStack controller node.
- Restart the OpenStack Manila services.
The restart is on the OpenStack controller node, not on Veritas Access.