Hitachi NAS Platform File Services Driver for OpenStack¶
The Hitachi NAS Platform File Services Driver for OpenStack provides NFS Shared File Systems to OpenStack.
Hitachi NAS Platform Models 3080, 3090, 4040, 4060, 4080, and 4100.
HNAS/SMU software version is 12.2 or higher.
HNAS configuration and management utilities to create a storage pool (span) and an EVS.
Preparation and Deployment¶
The manila-share node only requires the HNAS EVS data interface if you plan to use share migration.
It is mandatory that HNAS management interface is reachable from the Shared File System node through the admin network, while the selected EVS data interface is reachable from OpenStack Cloud, such as through Neutron flat networking.
Configuration on Kolla deployment¶
Enable Shared File Systems service and HNAS driver in
enable_manila: "yes" enable_manila_backend_hnas: "yes"
Configure the OpenStack networking so it can reach HNAS Management interface and HNAS EVS Data interface.
To configure two physical networks, physnet1 and physnet2, with ports eth1 and eth2 associated respectively:
neutron_bridge_name: "br-ex,br-ex2" neutron_external_interface: "eth1,eth2"
eth1 is used to Neutron external interface and
used to HNAS EVS data interface.
HNAS back end configuration¶
/etc/kolla/globals.yml uncomment and set:
hnas_ip: "172.24.44.15" hnas_user: "supervisor" hnas_password: "supervisor" hnas_evs_id: "1" hnas_evs_ip: "10.0.1.20" hnas_file_system_name: "FS-Manila"
Configuration on HNAS¶
Create the data HNAS network in Kolla OpenStack:
List the available tenants:
$ openstack project list
Create a network to the given tenant (service), providing the tenant ID, a name for the network, the name of the physical network over which the virtual network is implemented, and the type of the physical mechanism by which the virtual network is implemented:
$ neutron net-create --tenant-id <SERVICE_ID> hnas_network \ --provider:physical_network=physnet2 --provider:network_type=flat
Optional - List available networks:
$ neutron net-list
Create a subnet to the same tenant (service), the gateway IP of this subnet, a name for the subnet, the network ID created before, and the CIDR of subnet:
$ neutron subnet-create --tenant-id <SERVICE_ID> --gateway <GATEWAY> \ --name hnas_subnet <NETWORK_ID> <SUBNET_CIDR>
Optional - List available subnets:
$ neutron subnet-list
Add the subnet interface to a router, providing the router ID and subnet ID created before:
$ neutron router-interface-add <ROUTER_ID> <SUBNET_ID>
Create a file system on HNAS. See the Hitachi HNAS reference.
Make sure that the filesystem is not created as a replication target. Refer official HNAS administration guide.
Prepare the HNAS EVS network.
Create a route in HNAS to the tenant network:
$ console-context --evs <EVS_ID_IN_USE> route-net-add --gateway <FLAT_NETWORK_GATEWAY> \ <TENANT_PRIVATE_NETWORK>
Make sure multi-tenancy is enabled and routes are configured per EVS.
$ console-context --evs 3 route-net-add --gateway 192.168.1.1 \ 10.0.0.0/24
Configure multiple back ends¶
An administrator can configure an instance of Manila to provision shares from one or more back ends. Each back end leverages an instance of a vendor-specific implementation of the Manila driver API.
The name of the back end is declared as a configuration option share_backend_name within a particular configuration stanza that contains the related configuration options for that back end.
So, in the case of an multiple back ends deployment, it is necessary to change the default share backends before deployment.
Modify the file
/etc/kolla/config/manila.conf and add the contents:
[DEFAULT] enabled_share_backends = generic,hnas1,hnas2
Modify the file
/etc/kolla/config/manila-share.conf and add the contents:
[generic] share_driver = manila.share.drivers.generic.GenericShareDriver interface_driver = manila.network.linux.interface.OVSInterfaceDriver driver_handles_share_servers = True service_instance_password = manila service_instance_user = manila service_image_name = manila-service-image share_backend_name = GENERIC [hnas1] share_backend_name = HNAS1 share_driver = manila.share.drivers.hitachi.hnas.driver.HitachiHNASDriver driver_handles_share_servers = False hitachi_hnas_ip = <hnas_ip> hitachi_hnas_user = <user> hitachi_hnas_password = <password> hitachi_hnas_evs_id = <evs_id> hitachi_hnas_evs_ip = <evs_ip> hitachi_hnas_file_system_name = FS-Manila1 [hnas2] share_backend_name = HNAS2 share_driver = manila.share.drivers.hitachi.hnas.driver.HitachiHNASDriver driver_handles_share_servers = False hitachi_hnas_ip = <hnas_ip> hitachi_hnas_user = <user> hitachi_hnas_password = <password> hitachi_hnas_evs_id = <evs_id> hitachi_hnas_evs_ip = <evs_ip> hitachi_hnas_file_system_name = FS-Manila2
For more information about how to manage shares, see the Manage shares.
For more information about how HNAS driver works, see Hitachi NAS Platform File Services Driver for OpenStack.