Pure Storage FlashBlade File Services Driver for OpenStack¶
Overview¶
The Pure Storage FlashBlade File Services Driver for OpenStack provides NFS Shared File Systems to OpenStack.
Requirements¶
Pure Storage FlashBlade
Purity//FB v2.3.0 or higher
Preparation and Deployment¶
Important
It is mandatory that FlashBlade 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 FlashBlade driver in
/etc/kolla/globals.yml
enable_manila: "yes"
enable_manila_backend_flashblade: "yes"
Configure the OpenStack networking so it can reach FlashBlade Management interface and FlashBlade Data interface.
To configure two physical networks, physnet1 and physnet2, with ports eth1 and eth2 associated respectively:
In /etc/kolla/globals.yml
set:
neutron_bridge_name: "br-ex,br-ex2"
neutron_external_interface: "eth1,eth2"
Note
eth1
is used to Neutron external interface and eth2
is
used to FlashBlade data interface.
FlashBlade back end configuration¶
In /etc/kolla/globals.yml
uncomment and set:
manila_flashblade_mgmt_vip: "172.24.44.15"
manila_flashblade_data_vip: "172.24.45.22"
manila_flashblade_api: "<API token for admin-privilaged user>"
Configuration on FlashBlade¶
Create the FlashBlade data 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:
$ openstack network create --project <SERVICE_ID> \
--provider-physical-network physnet2 \
--provider-network-type flat \
flashblade_network
Optional - List available networks:
$ openstack network 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:
$ openstack subnet create --project <SERVICE_ID> --gateway <GATEWAY> \
--subnet_range <SUBNET_CIDR> flashblade_subnet
Optional - List available subnets:
$ openstack subnet list
Add the subnet interface to a router, providing the router ID and subnet ID created before:
$ openstack router add submet <ROUTER_ID> <SUBNET_ID>
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,fb1,fb2
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
[fb1]
share_backend_name = FB1
share_driver = manila.share.drivers.purestorage.flashblade.FlashBladeShareDriver
driver_handles_share_servers = False
flashblade_mgmt_vip = <fb1_mgmt_ip>
flashblade_data_vip = <fb1_data_ip>
flashblade_api = <FB1 API token>
[fb2]
share_backend_name = FB2
share_driver = manila.share.drivers.purestorage.flashblade.FlashBladeShareDriver
driver_handles_share_servers = False
flashblade_mgmt_vip = <fb2_mgmt_ip>
flashblade_data_vip = <fb2_data_ip>
flashblade_api = <FB2 API token>
For more information about how to manage shares, see the Manage shares.
For details on how to use the Pure Storage FlashBlade, refer to the Pure Storage Manila Reference Guide.
The use of this backend requires that the purity_fb
SDK package is
installed in the manila-share
container. To do this follow the steps
outlined in the kolla image building guide
particularly the Package Customisation
and Custom Repos
sections.