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
Veritas Access iSCSI based Cinder driver
Veritas Access enables its users to use Veritas Access as a storage backend for OpenStack Cinder service. Veritas Access Cinder driver over an iSCSI recently successfully merged in OpenStack for Rocky release. However, the driver has been successfully tested with OpenStack Ocata and Queens releases. You can configure the Veritas Access that is to be used as storage backend for the OpenStack Cinder service over an iSCSI.
To list all the available targets
- To list all the available targets, enter the following:
Target> iscsi target list Target Name Store ================================ ========= iqn.2018-02.com.veritas:target02 target_fs iqn.2018-02.com.veritas:target01 fs1
To list all the target configuration details that need to be configured for OpenStack
- To list all the target configuration details, enter the following:
Openstack> cinder iscsi configure <comma separated target list>
You can obtain all the target configuration details that can be used for OpenStack configuration.
For example:
Openstack> cinder iscsi configure iqn.2018-02.com.veritas:target02
To create a new backend (va-iscsi) in Cinder
- Perform the following changes on the OpenStack controller node and restart the Cinder services.
Add the following configuration entries in the
/etc/cinder/cinder.conf
file:In the [DEFAULT] section:
##### enabled_backends = va-iscsi #####
At the end of all sections:
##### [va-iscsi] volume_driver = cinder.volume.drivers.veritas_access.veritas_iscsi.ACCESSIscsiDriver volume_backend_name = ACCESS_ISCSI iscsi_protocol = iscsi reserved_percentage = 0 vrts_iscsi_port = 3260 vrts_lun_sparse = false vrts_target_config = /etc/cinder/vrts_target.xml vrts_server_ip = 10.182.168.90 vrts_port = 14161 vrts_user = <master_user> vrts_pwd = <master_user_password> #####
Replace the following in the
/etc/cinder/vrts_target.xml
file:##### <?xml version="1.0" ?> <VRTS> <VrtsTargets> <Target> <Name>iqn.2018-02.com.veritas:target02 <PortalIP>10.182.174.189 <Authentication>0 </Target> </VrtsTargets> </VRTS> #####
To enable multipathing, make following changes in
nova.conf
fileIn the [DEFAULT] section: ##### volume_use_multipath = True #####
Note:
If you want to configure new targets, include the previously configured targets in the Openstack> cinder iscsi configure <target_list> command to get the complete configuration details.
To list the LUNs and LUN-snapshots created by Cinder
- To list the LUNs and LUN-snapshots created by Cinder, enter the following:
Openstack> cinder iscsi show Target Name Store ================================ ========= iqn.2018-02.com.veritas:target02 target_fs iqn.2018-02.com.veritas:target01 fs1
For example:
Openstack> cinder iscsi show LUNs created by openstack cinder: 745e4e4d-d6f5138b LUN snapshot created by openstack cinder: e774b3bb-7540a2a6