x
/
fuel-plugin-solidfire-cinder
Code Issues Proposed changes

Retire repository 

Fuel repositories are all retired in openstack namespace, retire
remaining fuel repos in x namespace since they are unused now.

This change removes all content from the repository and adds the usual
README file to point out that the repository is retired following the
process from
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project

See also
http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011675.html

A related change is: https://review.opendev.org/699752 .

Change-Id: Iacbf223a8dbe9a8680b7e2def6a46c25e6b5bb51
This commit is contained in:
Andreas Jaeger 2019-12-18 19:46:01 +01:00
parent bdedbbf6cb
commit ac60fb8e41
25 changed files with 10 additions and 885 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
.gitignore vendored
View File

@ -1,10 +0,0 @@
.tox
.build
*.pyc
repositories/centos/*
repositories/ubuntu/*
deployment_scripts/puppet/modules/inifile
deployment_scripts/puppet/modules/stdlib
build.sh
*.rpm
.project

202
LICENSE
View File

@ -1,202 +0,0 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "{}"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright {yyyy} {name of copyright owner}
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

46
README.md
View File

@ -1,46 +0,0 @@
fuel-plugin-solidfire-cinder
============
Plugin description
--------------
SolidFire plugin for Fuel extends Mirantis OpenStack functionality by
adding support for SolidFire all Flash block storage cluster.
The SolidFire cluster is an iSCSI block storage device used as a
Cinder backend.
Requirements
------------
| Requirement | Version/Comment |
|----------------------------------------------------------|-----------------|
| Mirantis OpenStack compatibility | >= 6.1 |
| Access to SolidFire MVIP via cinder-volume node | |
| Access to SolidFire SVIP via compute/cinder-volume nodes | |
| iSCSI initiator on all compute/cinder-volume nodes | |
Limitations
-----------
Currently Fuel doesn't support multi-backend.
SolidFire configuration
---------------------
Before starting a deployment there are some things that you should verify:
1. Your SolidFire Cluster can route 10G Storage Network to all Compute nodes
as well as the Cinder Control/Manager node.
2. Create an account on the SolidFire cluster to use as the OpenStack Administrator
account (use the login/password for this account as san_login/password settings).
3. Obtain the MVIP address from the SolidFire cluster (uses as the san_ip)
SolidFire Cinder plugin installation
---------------------------
All of the needed code for using SolidFire in an OpenStack deployment is
included in the upstream OpenStack distribution. There are no additional
libraries, software packages or licenses.
SolidFire plugin configuration
----------------------------

10
README.rst Normal file
View File

@ -0,0 +1,10 @@
This project is no longer maintained.
The contents of this repository are still available in the Git
source code management system. To see the contents of this
repository before it reached its end of life, please check out the
previous commit with "git checkout HEAD^1".
For any further questions, please email
openstack-discuss@lists.openstack.org or join #openstack-dev on
Freenode.

7
components.yaml
View File

@ -1,7 +0,0 @@
- name: 'storage:block:backend:solidfire'
label: 'Cinder SolidFire'
description: 'Cinder with SolidFire backend'
compatible:
- name: 'storage:block:backend:ceph'
- name: 'storage:block:backend:lvm'
- name: 'storage:block:backend:netapp'

30
deployment_scripts/puppet/manifests/hiera_override.pp
View File

@ -1,30 +0,0 @@
notice('MODULAR: solidfire-hiera-override')
$cinder_solidfire = hiera_hash('cinder_solidfire', {})
$hiera_dir = '/etc/hiera/plugins'
$plugin_yaml = 'cinder_solidfire.yaml'
$plugin_name = 'cinder_solidfire'
$content = inline_template('
storage:
volume_backend_names:
solidfire: solidfire
')
file { $hiera_dir:
ensure => directory,
}
file { "${hiera_dir}/${plugin_yaml}":
ensure => file,
content => $content,
}
# Workaround for bug 1598163
exec { 'patch_puppet_bug_1598163':
path => '/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin',
cwd => '/etc/puppet/modules/osnailyfacter/manifests/globals',
command => "sed -i \"s/hiera('storage/hiera_hash('storage/\" globals.pp",
onlyif => "grep \"hiera('storage\" globals.pp"
}

3
deployment_scripts/puppet/manifests/site.pp
View File

@ -1,3 +0,0 @@
notice('MODULAR: fuel-plugin-solidfire-cinder')
class { 'plugin_cinder_solidfire': }

16
deployment_scripts/puppet/modules/plugin_cinder_solidfire/manifests/enable_backend.pp
View File

@ -1,16 +0,0 @@
define plugin_cinder_solidfire::enable_backend () {
notice("Enabling backend: ${backend_name}")
$config_file = '/etc/cinder/cinder.conf'
ini_subsetting {"enable_${name}_backend":
ensure => present,
section => 'DEFAULT',
key_val_separator => '=',
path => $config_file,
setting => 'enabled_backends',
subsetting => $name,
subsetting_separator => ',',
}
}

21
deployment_scripts/puppet/modules/plugin_cinder_solidfire/manifests/init.pp
View File

@ -1,21 +0,0 @@
#
# Copyright 2015 SolidFire, Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.
#
class plugin_cinder_solidfire {
$cinder_solidfire = hiera_hash('cinder_solidfire', {})
plugin_cinder_solidfire::solidfire { 'solidfire': backend_name => 'solidfire', }
}

49
deployment_scripts/puppet/modules/plugin_cinder_solidfire/manifests/solidfire.pp
View File

@ -1,49 +0,0 @@
# Copyright 2015 SolidFire, Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.
#
define plugin_cinder_solidfire::solidfire (
$backend_name = $name,
$cinder_solidfire = $plugin_cinder_solidfire::cinder_solidfire,
) {
include cinder::params
include cinder::client
Cinder::Backend::Solidfire <||> -> Plugin_cinder_solidfire::Enable_backend[$backend_name] ~> Service <||>
cinder::backend::solidfire { $backend_name :
san_ip => $cinder_solidfire['solidfire_mvip'],
san_login => $cinder_solidfire['solidfire_admin_login'],
san_password => $cinder_solidfire['solidfire_admin_password'],
volume_backend_name => $backend_name,
sf_emulate_512 => 'true',
sf_api_port => $cinder_solidfire['solidfire_api_port'],
sf_account_prefix => $cinder_solidfire['solidfire_account_prefix'],
sf_allow_template_caching => $cinder_solidfire['solidfire_allow_template_caching'],
sf_template_account_name => $cinder_solidfire['solidfire_template_account'],
sf_volume_prefix => $cinder_solidfire['solidfire_volume_prefix'],
extra_options => { "${backend_name}/host" =>
{ value => $backend_name },
},
}
plugin_cinder_solidfire::enable_backend { $backend_name: }
package { 'open-iscsi' :
ensure => 'installed',
}
service { $cinder::params::volume_service: }
}

63
deployment_tasks.yaml
View File

@ -1,63 +0,0 @@
- id: solidfire_hiera_override
type: puppet
version: 3.0.0
groups: [primary-controller]
requires: [hiera]
required_for: [create-cinder-types]
parameters:
puppet_manifest: puppet/manifests/hiera_override.pp
puppet_modules: puppet/modules:/etc/puppet/modules
timeout: 360
- id: solidfire_cinder_controller
type: puppet
version: 3.0.0
role: [primary-controller, controller]
requires: [openstack-cinder]
required_for: [deploy_end]
condition:
yaql_exp: >
$.storage.volumes_ceph and
changedAny($.cinder_solidfire, $.network_scheme, $.cinder, $.network_metadata.vips,
$.get('cinder_volume_group'), $.storage, $.ceilometer, $.sahara,
$.rabbit, $.get('region', 'RegionOne'), $.get('use_ssl'),
('primary-controller' in $.roles), $.get('proxy_port'),
$.get('kombu_compression'), $.get('keystone_endpoint'),
$.get('glance_endpoint'), $.get('glance_api_servers'),
$.get('use_syslog'), $.get('use_stderr'), $.get('verbose'), $.debug,
$.network_metadata.nodes.values().where(
$.node_roles.any($.matches('controller'))).network_roles.select(
$.get('mgmt/messaging')),
$.get('amqp_hosts'), $.get('syslog_log_facility_cinder'),
$.get('cinder_rate_limits'),
$.configuration.get('cinder_api_paste_ini'), $.configuration.get('cinder'))
parameters:
puppet_manifest: puppet/manifests/site.pp
puppet_modules: puppet/modules:/etc/puppet/modules
timeout: 360
# For LCM inherit condition from top-role-cinder
# otherwise enabled_backends will be overwritten.
# https://bugs.launchpad.net/puppet-cinder/+bug/1598094
- id: solidfire_cinder
type: puppet
version: 3.0.0
groups: [cinder]
requires: [top-role-cinder]
required_for: [deploy_end]
condition:
yaql_exp: >
changedAny($.cinder_solidfire, $.cinder, $.get('cinder_volume_group'),
$.network_metadata.nodes.get(concat("node-", $.uid)).network_roles.get('cinder/iscsi'),
$.network_metadata.vips, $.debug, $.node_volumes, $.storage, $.rabbit, $.ceilometer,
$.get('use_stderr'), $.get('use_syslog'), $.get('syslog_log_facility_cinder'),
$.get('syslog_log_facility_ceph'), $.get('proxy_port'), $.get('kombu_compression'),
$.get('use_ssl'), $.get('service_endpoint'), $.get('glance_api_servers'),
$.get('amqp_hosts'),
$.network_metadata.nodes.values().where(
$.node_roles.any($.matches('controller'))).network_roles.select(
$.get('mgmt/messaging')))
parameters:
puppet_manifest: puppet/manifests/site.pp
puppet_modules: puppet/modules:/etc/puppet/modules
timeout: 360

BIN
docs/figures/cinder-solidfire-plugin-1.1.0.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 166 KiB

BIN
docs/figures/cinder-solidfire-plugin-2.0.0.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 92 KiB

BIN
docs/figures/cinder-solidfire-plugin-3.0.0.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 83 KiB

217
docs/solidfire-cinder-guide.rst
View File

@ -1,217 +0,0 @@
***************************************************************
Guide to the SolidFire Cinder Plugin version 3.0.0 for Fuel 9.x
***************************************************************
This document provides instructions for installing, configuring and using
SolidFire Cinder plugin for Fuel.
Key terms, acronyms and abbreviations
=====================================
MVIP
Management Virtual IP (MVIP) is the IP address (or hostname) of
the management interface to the SolidFire cluster
SVIP
Storage Virtual IP (SVIP) is the IP address (or hostname) of the
storage interface of the SolidFire cluster. SolidFire supports
multiple SVIPs on separate VLANs.
Cluster Admin account
The Cluster Admin account on a SolidFire cluster is the account by
which you administer the SolidFire cluster.
SolidFire accounts
SolidFire accounts are automatically created by the SolidFire
OpenStack driver as needed based on the Project ID. These accounts
manage the CHAP authentication for the volumes allocated by that
project. No configuration is needed for these accounts.
SolidFire Cinder
================
The SolidFire Cinder Fuel plugin provides an automated method
to insert the necessary lines into the cinder.conf file. The plugin
extends the Fuel GUI to provide the necessary entry locations for the
information for the configuration file.
Please see the
`SolidFire OpenStack Configuration Guide <http://www.solidfire.com/solutions/cloud-orchestration/openstack/>`_
for complete details.
License
-------
======================= ==================
Component License type
======================= ==================
No Components are present
============================================
Requirements
------------
======================= ==================
Requirement Version/Comment
======================= ==================
Fuel 9.0
============================================
Prerequisites
--------------
* The SolidFire cluster should be configured and on the network prior to starting
Cinder with the SolidFire configuration in place.
* Cinder relies on the open-iscsi package to preform many functions such as image
to volume. This plugin requires (and installs) the open-iscsi package, so it must
be avaliable in one of the repositories avaliable to Fuel.
* See the `Mirantis, SolidFire joint reference architecture <https://content.mirantis.com/rs/451-RBY-185/images/SolidfireMirantisUnlockedReferenceArchitecture-4-25-2016.pdf>`_.
Limitations
-----------
* The SolidFire Cinder Fuel plugin no longer supports a single backend in the
DEFAULT section. The option has been removed from the GUI for multiple
backends and the plugin will always assume multiple backends.
============================================
Installation Guide
==================
SolidFire Cinder plugin installation
------------------------------------
#. Download the plugin from
`Fuel Plugins Catalog <https://www.mirantis.com/products/openstack-drivers-and-plugins/fuel-plugins/>`_.
or clone this repository, install the fuel plugin builder with the
following command
::
pip install fuel-plugin-builder
and then build the plugin using the following command:
::
cd fuel-plugin-solidfire-cinder; fpb --build ./
#. Copy the plugin to an already installed Fuel Master node. If you do not
have the Fuel Master node yet, follow the instructions from the
official Mirantis OpenStack documentation:
::
# scp cinder_solidfire-3.0-3.0.0-1.noarch.rpm \
root@:<the_Fuel_Master_node_IP>:/tmp
#. Log into the Fuel Master node and install the plugin:
::
# cd /tmp
# fuel plugins --install /tmp/cinder_solidfire-3.0-3.0.0-1.noarch.rpm
...
# fuel plugins list
id | name | version | package_version | releases
---+------------------+---------+-----------------+--------------------
1 | cinder_netapp | 5.0.0 | 4.0.0 | ubuntu (mitaka-9.0)
SolidFire Cinder plugin configuration
-------------------------------------
#. After plugin is installed, create a new OpenStack environment following
`the instructions <http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/create-environment/start-create-env.html>`_.
#. Configure your environment following
`the official OpenStack documentation <http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/configure-environment.html>`_.
#. Open the *Storage tab* of the Fuel web UI and scroll down the page to
'Fuel plugin for SolidFire in Cinder.'
#. Select the Fuel plugin checkbox to enable SolidFire Cinder plugin for Fuel:
.. image:: figures/cinder-solidfire-plugin-3.0.0.png
:width: 100%
#. The default configuration is that the SolidFire configuration stanza is a self contained stanza
within the Cinder config file. In addition the enabled_backends directive is placed in the 'default'
section to enable the SolidFire Stanza. This option allows for multiple backends to be configured and
configures Cinder to place the proper routing information into the database.
#. Enter the Cluster Admin account information (account and password) and the IP address
of the Management Virtual IP (MVIP) of the SolidFire Cluster.
#. It is recommended to select the defaults for all other SolidFire options, but explanations
of each field are below.
#. 'Cluster endpoint port' defines the port number to communicate with the SolidFire API on. Generally
this is not changed unless a HTTPs proxy is used or the port is otherwise changed.
#. 'Enable Caching' and 'Template Account' allow the SolidFire cluster to cache Glance images on the
SolidFire cluster for all tenants. The template account will be automatically created on the SolidFire
cluster and the cached images will be contained within this account. The account will be prefixed with
the 'SF account prefix' if defined.
#. 'SF account prefix' will prefix all accounts on the SolidFire cluster with the defined prefix. The
prefix is useful (but not required) when multiple OpenStack instances access the same SolidFire cluster
such that each instance can quickly identify accounts that belong to that instance. NOTE: Accounts
on SolidFire are named using the Project/Tenant ID, optionally prefixed as defined here.
#. 'SF volume prefix' will cause all volumes on teh SolidFire cluster to be prefixed with with the
configured characters. This is useful and recommended when multiple OpenStack instances are
utilizing the same SolidFire cluster. This field is pre-populated with the default value of 'UUID-'.
#. Once configuration is done, you can run
`network verification <http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/configure-environment/verify-networks.html>`_
check and `deploy the environment <http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/deploy-environment.html>`_.
User Guide
==========
Once the OpenStack instance is deployed by Fuel, the SolidFire plugin provides no
user configurable or maintainable options.
The SolidFire driver (once configured by Fuel) will output all logs into the
cinder-volume process log file with the 'solidfire' title.
Known issues
============
For Mitaka (Fuel 9.0) the following change is required to be in place
https://review.openstack.org/#/c/347066/ in file
/etc/puppet/mitaka-9.0/modules/cinder/manifests/backend/solidfire.pp on the
fuel master.
Release Notes
=============
* Version 1.0.1 supports Fuel 6.x.
* Version 1.1.0 supports Fuel 7.x.
* Version 1.1.1 adds automated install of the open-iscsi package which is required by SolidFire, but not installed
by Fuel if Ceph is selected in the starting wizzard. Supports Fuel 7.x.
* Version 2.0.0 refactors the code to support Fuel 8.0
* Version 3.0.0 refactors the code to support Fuel 9.0
Troubleshooting
===============
All SolidFire messages are output into the Cinder-volume log file. Search for 'solidfire'.
Appendix
========
`The SolidFire driver documentation
<http://docs.openstack.org/mitaka/config-reference/block-storage/drivers/solidfire-volume-driver.html>`_
contains complete information on all SolidFire driver options.

BIN
docs/testing/TestPlanforSolidFireCinderFuelPlugin-1.1.0.docx
View File

Binary file not shown.

BIN
docs/testing/TestPlanforSolidFireCinderFuelPlugin-1.1.1.docx
View File

Binary file not shown.

BIN
docs/testing/TestReportforPluginnameFuelPlugin-1.1.0.docx
View File

Binary file not shown.

BIN
docs/testing/TestReportforPluginnameFuelPlugin-1.1.1.docx
View File

Binary file not shown.

54
environment_config.yaml
View File

@ -1,54 +0,0 @@
attributes:
metadata:
group: 'storage'
solidfire_mvip:
value: ''
label: 'Cluster MVIP (san_ip)'
description: 'The hostname (or IP address) for the SolidFire Cluster API endpoint.'
weight: 20
type: "text"
solidfire_admin_login:
value: ''
label: 'Login for Cluster Admin account (san_login)'
description: 'Cluster account used by Cinder service.'
weight: 30
type: "text"
regex:
source: '\S'
error: "Username field cannot be empty"
solidfire_admin_password:
value: ''
label: 'Password for Cluster Admin account (san_password)'
description: 'Cluster account used by Cinder service.'
weight: 40
type: "password"
solidfire_api_port:
value: '443'
label: 'Cluster endpoint port'
description: 'The TCP port to use for API communication with the cluster or proxy server.'
weight: 50
type: "text"
solidfire_allow_template_caching:
value: true
label: 'Enable Caching'
description: 'When creating bootable volumes, create an image cache on the SolidFire cluster.'
weight: 51
type: "checkbox"
solidfire_template_account:
value: 'openstack-vtemplate'
label: 'Template Account'
description: 'SolidFire account to use to hold the template cache.'
weight: 52
type: "text"
solidfire_account_prefix:
value: ''
label: 'SF account prefix'
description: 'Prefix to use for all SolidFire accounts related to this OpenStack.'
weight: 70
type: "text"
solidfire_volume_prefix:
value: 'UUID-'
label: 'SF volume prefix'
description: 'Prefix to use for all SolidFire volumes related to this OpenStaack Cloud.'
weight: 80
type: 'text'

21
metadata.yaml
View File

@ -1,21 +0,0 @@
name: cinder_solidfire
title: Fuel plugin for SolidFire in Cinder
version: '3.0.0'
description: Enables the SolidFire driver in Cinder
fuel_version: ['9.0']
licenses: ['Apache License Version 2.0']
authors: ['Ed Balduf <ed.balduf@solidfire.com>']
homepage: 'https://github.com/stackforge/fuel-plugin-solidfire-cinder'
groups: ['storage::cinder']
is_hotpluggable: true
releases:
- os: ubuntu
version: mitaka-9.0
mode: ['ha']
deployment_scripts_path: deployment_scripts/
repository_path: repositories/ubuntu
# Version of plugin package
package_version: '4.0.0'

5
pre_build_hook
View File

@ -1,5 +0,0 @@
#!/bin/bash
# Add here any the actions which are required before plugin build
# like packages building, packages downloading from mirrors and so on.
# The script should return 0 if there were no errors.

0
repositories/centos/.gitkeep
View File

0
repositories/ubuntu/.gitkeep
View File

141
specs/solidfire-plugin-specs.rst
View File

@ -1,141 +0,0 @@
This work is licensed under the Apache License, Version 2.0.
http://www.apache.org/licenses/LICENSE-2.0
==================================================
Fuel plugin for SolidFire clusters as a Cinder backend
==================================================
SolidFire plugin for Fuel extends Mirantis OpenStack functionality by adding
support for SolidFire clusters in Cinder using iSCSI protocol.
It replaces Cinder LVM driver which is the default volume backend that uses
local volumes managed by LVM.
Problem description
===================
Currently, Fuel has no support for SolidFire clusters as block storage for
OpenStack environments. Solidfire plugin aims to provide support for it.
Proposed change
===============
Implement a Fuel plugin that will configure the SolidFire driver for
Cinder on all Controller nodes. Cinder volume service will be managed
by Pacemaker/Corosync to provide HA. Having all Cinder services run
on controllers no additional Cinder node is required in environment.
Alternatives
------------
It might have been implemented as part of Fuel core but we decided to make it
as a plugin for several reasons:
* This isn't something that all operators may want to deploy.
* Any new additional functionality makes the project's testing more difficult,
which is an additional risk for the Fuel release.
Data model impact
-----------------
None
REST API impact
---------------
None
Upgrade impact
--------------
None
Security impact
---------------
None
Notifications impact
--------------------
None
Other end user impact
---------------------
None
Performance Impact
------------------
The SolidFire storage clusters provide high performance block storage for
OpenStack envirnments, and therefore enabling the SolidFire driver in OpenStack
will greatly improve peformance of OpenStack.
Other deployer impact
---------------------
The deployer should configure the IP addresses on the SolidFire array before
they deloy the Fuel Plugin to the controllers. If not, the Cinder-volume service
will need to be restarted once the SolidFire cluster is configured
Developer impact
----------------
None
Implementation
==============
The plugin generates the approriate cinder.conf stanzas to enable the SolidFire
cluster within OpenStack. There are NO other packages required, the SolidFire driver
which is included in the OpenStack distribution is all that is necessary.
Plugin has two tasks. Each task per role. They are run in the following order:
* The first task installs and configures cinder-volume on Primary Controller.
* The second task installs and configures cinder-volume on Controller nodes.
Cinder-volume service is installed on all Controller nodes and is managed by
Pacemaker. It runs in active/passive mode where only one instance is active.
All instances of cinder-volume have the same “host” parameter in cinder.conf
file. This is required to achieve ability to manage all volumes in the
environment by any cinder-volume instance.
Assignee(s)
-----------
| Edward Balduf <ed.balduf@solidfire.com>
| John Griffith <john.griffith@solidfire.com>
Work Items
----------
* Implement the Fuel plugin.
* Implement the Puppet manifests.
* Testing.
* Write the documentation.
Dependencies
============
* Fuel 6.1 and higher.
Testing
=======
* Prepare a test plan.
* Test the plugin by deploying environments with all Fuel deployment modes.
Documentation Impact
====================
* Deployment Guide (how to install the storage backends, how to prepare an
environment for installation, how to install the plugin, how to deploy an
OpenStack environment with the plugin).
* User Guide (which features the plugin provides, how to use them in the
deployed OpenStack environment).
* Test Plan.
* Test Report.