From ebb5451c8ff9c77b1b4fa3946cb8c7ce3a9a17d2 Mon Sep 17 00:00:00 2001 From: Andreas Jaeger Date: Wed, 18 Dec 2019 19:45:22 +0100 Subject: [PATCH] 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: I4d787ba03e9168bc593365675e3124c650546b33 --- .gitignore | 23 - .gitmodules | 0 CONTRIBUTING.md | 53 --- LICENSE | 201 -------- README.md | 180 ------- README.rst | 10 + Vagrantfile | 31 -- deployment_scripts/puppet/manifests/cinder.pp | 38 -- .../puppet/manifests/cluster.pp | 450 ------------------ .../puppet/manifests/discovery_cluster.pp | 37 -- .../puppet/manifests/environment.pp | 180 ------- .../manifests/environment_existing_mdm_ips.pp | 30 -- .../puppet/manifests/gateway_server.pp | 43 -- deployment_scripts/puppet/manifests/glance.pp | 19 - .../puppet/manifests/mdm_package.pp | 22 - .../puppet/manifests/mdm_server.pp | 68 --- deployment_scripts/puppet/manifests/nova.pp | 48 -- deployment_scripts/puppet/manifests/os.pp | 127 ----- .../puppet/manifests/resize_cluster.pp | 123 ----- deployment_scripts/puppet/manifests/sdc.pp | 26 - .../puppet/manifests/sdc_server.pp | 22 - .../puppet/manifests/sds_server.pp | 122 ----- .../modules/scaleio_fuel/files/.gitkeep | 0 .../scaleio_fuel/lib/facter/cluster_info.rb | 243 ---------- .../modules/scaleio_fuel/lib/facter/disks.rb | 78 --- .../scaleio_fuel/lib/facter/env_info.rb | 15 - .../lib/facter/ip_address_array.rb | 17 - .../scaleio_fuel/lib/facter/os_info.rb | 22 - .../scaleio_fuel/lib/facter/sds_config.rb | 43 -- .../parser/functions/convert_sds_config.rb | 38 -- .../puppet/parser/functions/filter_nodes.rb | 9 - .../functions/get_pools_from_sds_config.rb | 23 - .../lib/puppet/parser/functions/pw_hash.rb | 24 - .../parser/functions/update_sds_to_pd_map.rb | 43 -- deployment_tasks.yaml | 229 --------- doc/source/Makefile | 177 ------- doc/source/appendix.rst | 6 - doc/source/build | 7 - doc/source/conf.py | 39 -- doc/source/guide.rst | 219 --------- doc/source/images/block-storage-services.png | Bin 82760 -> 0 bytes doc/source/images/deploy-result.png | Bin 156949 -> 0 bytes doc/source/images/deploy.png | Bin 204619 -> 0 bytes doc/source/images/devices_compute.png | Bin 178189 -> 0 bytes doc/source/images/devices_controller.png | Bin 195707 -> 0 bytes doc/source/images/devices_scaleio.png | Bin 176631 -> 0 bytes .../fuel-plugin-scaleio-Architecture.jpg | Bin 158487 -> 0 bytes doc/source/images/fuel-plugin-scaleio.vsd | Bin 355840 -> 0 bytes doc/source/images/network.png | Bin 274151 -> 0 bytes doc/source/images/role_scaleio.png | Bin 219410 -> 0 bytes doc/source/images/scaleio-cp.png | Bin 128417 -> 0 bytes doc/source/images/scaleio-login.png | Bin 24722 -> 0 bytes doc/source/images/scaleio-sds.png | Bin 143496 -> 0 bytes doc/source/images/settings1.png | Bin 337566 -> 0 bytes doc/source/images/settings2.png | Bin 325344 -> 0 bytes doc/source/images/settings2_nh.png | Bin 309217 -> 0 bytes doc/source/images/settings3.png | Bin 337100 -> 0 bytes .../images/settings_existing_cluster.png | Bin 211077 -> 0 bytes doc/source/images/sio-volume-defined.png | Bin 12858 -> 0 bytes doc/source/images/sio-volume-mapped.png | Bin 12166 -> 0 bytes doc/source/images/wizard.png | Bin 209203 -> 0 bytes doc/source/index.rst | 15 - doc/source/installation.rst | 34 -- doc/source/introduction.rst | 63 --- doc/source/release_notes.rst | 42 -- doc/testing/TestPlanforScaleIOFuelPlugin.docx | Bin 258917 -> 0 bytes .../TestPlanforScaleIOFuelPlugin.pages | Bin 1075155 -> 0 bytes doc/testing/TestReportScaleIOFuelPlugin.docx | Bin 183305 -> 0 bytes doc/testing/TestReportScaleIOFuelPlugin.pages | Bin 962148 -> 0 bytes environment_config.yaml | 331 ------------- metadata.yaml | 69 --- node_roles.yaml | 29 -- pre_build_hook | 55 --- repositories/centos/.gitkeep | 0 repositories/ubuntu/.gitkeep | 0 spec/scaleio-plugin-spec.rst | 124 ----- volumes.yaml | 84 ---- 77 files changed, 10 insertions(+), 3921 deletions(-) delete mode 100644 .gitignore delete mode 100644 .gitmodules delete mode 100644 CONTRIBUTING.md delete mode 100644 LICENSE delete mode 100644 README.md create mode 100644 README.rst delete mode 100644 Vagrantfile delete mode 100644 deployment_scripts/puppet/manifests/cinder.pp delete mode 100644 deployment_scripts/puppet/manifests/cluster.pp delete mode 100644 deployment_scripts/puppet/manifests/discovery_cluster.pp delete mode 100644 deployment_scripts/puppet/manifests/environment.pp delete mode 100644 deployment_scripts/puppet/manifests/environment_existing_mdm_ips.pp delete mode 100644 deployment_scripts/puppet/manifests/gateway_server.pp delete mode 100644 deployment_scripts/puppet/manifests/glance.pp delete mode 100644 deployment_scripts/puppet/manifests/mdm_package.pp delete mode 100644 deployment_scripts/puppet/manifests/mdm_server.pp delete mode 100644 deployment_scripts/puppet/manifests/nova.pp delete mode 100644 deployment_scripts/puppet/manifests/os.pp delete mode 100644 deployment_scripts/puppet/manifests/resize_cluster.pp delete mode 100644 deployment_scripts/puppet/manifests/sdc.pp delete mode 100644 deployment_scripts/puppet/manifests/sdc_server.pp delete mode 100644 deployment_scripts/puppet/manifests/sds_server.pp delete mode 100644 deployment_scripts/puppet/modules/scaleio_fuel/files/.gitkeep delete mode 100644 deployment_scripts/puppet/modules/scaleio_fuel/lib/facter/cluster_info.rb delete mode 100644 deployment_scripts/puppet/modules/scaleio_fuel/lib/facter/disks.rb delete mode 100644 deployment_scripts/puppet/modules/scaleio_fuel/lib/facter/env_info.rb delete mode 100644 deployment_scripts/puppet/modules/scaleio_fuel/lib/facter/ip_address_array.rb delete mode 100644 deployment_scripts/puppet/modules/scaleio_fuel/lib/facter/os_info.rb delete mode 100644 deployment_scripts/puppet/modules/scaleio_fuel/lib/facter/sds_config.rb delete mode 100644 deployment_scripts/puppet/modules/scaleio_fuel/lib/puppet/parser/functions/convert_sds_config.rb delete mode 100644 deployment_scripts/puppet/modules/scaleio_fuel/lib/puppet/parser/functions/filter_nodes.rb delete mode 100644 deployment_scripts/puppet/modules/scaleio_fuel/lib/puppet/parser/functions/get_pools_from_sds_config.rb delete mode 100644 deployment_scripts/puppet/modules/scaleio_fuel/lib/puppet/parser/functions/pw_hash.rb delete mode 100644 deployment_scripts/puppet/modules/scaleio_fuel/lib/puppet/parser/functions/update_sds_to_pd_map.rb delete mode 100644 deployment_tasks.yaml delete mode 100644 doc/source/Makefile delete mode 100644 doc/source/appendix.rst delete mode 100755 doc/source/build delete mode 100644 doc/source/conf.py delete mode 100644 doc/source/guide.rst delete mode 100644 doc/source/images/block-storage-services.png delete mode 100644 doc/source/images/deploy-result.png delete mode 100644 doc/source/images/deploy.png delete mode 100644 doc/source/images/devices_compute.png delete mode 100644 doc/source/images/devices_controller.png delete mode 100644 doc/source/images/devices_scaleio.png delete mode 100644 doc/source/images/fuel-plugin-scaleio-Architecture.jpg delete mode 100644 doc/source/images/fuel-plugin-scaleio.vsd delete mode 100644 doc/source/images/network.png delete mode 100644 doc/source/images/role_scaleio.png delete mode 100644 doc/source/images/scaleio-cp.png delete mode 100644 doc/source/images/scaleio-login.png delete mode 100644 doc/source/images/scaleio-sds.png delete mode 100644 doc/source/images/settings1.png delete mode 100644 doc/source/images/settings2.png delete mode 100644 doc/source/images/settings2_nh.png delete mode 100644 doc/source/images/settings3.png delete mode 100644 doc/source/images/settings_existing_cluster.png delete mode 100644 doc/source/images/sio-volume-defined.png delete mode 100644 doc/source/images/sio-volume-mapped.png delete mode 100644 doc/source/images/wizard.png delete mode 100644 doc/source/index.rst delete mode 100644 doc/source/installation.rst delete mode 100644 doc/source/introduction.rst delete mode 100644 doc/source/release_notes.rst delete mode 100644 doc/testing/TestPlanforScaleIOFuelPlugin.docx delete mode 100644 doc/testing/TestPlanforScaleIOFuelPlugin.pages delete mode 100644 doc/testing/TestReportScaleIOFuelPlugin.docx delete mode 100644 doc/testing/TestReportScaleIOFuelPlugin.pages delete mode 100644 environment_config.yaml delete mode 100644 metadata.yaml delete mode 100644 node_roles.yaml delete mode 100755 pre_build_hook delete mode 100644 repositories/centos/.gitkeep delete mode 100644 repositories/ubuntu/.gitkeep delete mode 100644 spec/scaleio-plugin-spec.rst delete mode 100644 volumes.yaml diff --git a/.gitignore b/.gitignore deleted file mode 100644 index 471dc6a..0000000 --- a/.gitignore +++ /dev/null @@ -1,23 +0,0 @@ -# Mac -.DS_Store - -# Vagrant -.vagrant/ - -# Fuel Plugin Builder -.build/ -*.rpm - -# Python virtualenv -.venv/ - -# Sphinx -_build/ - -# PDF -*.pdf - -.project -.doctrees -.buildpath -.pydevproject diff --git a/.gitmodules b/.gitmodules deleted file mode 100644 index e69de29..0000000 diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index 40e57ff..0000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,53 +0,0 @@ -# Contributions - -The Fuel plugin for ScaleIO project has been licensed under the [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0") License. In order to contribute to the project you will to do two things: - - -1. License your contribution under the [DCO](http://elinux.org/Developer_Certificate_Of_Origin "Developer Certificate of Origin") + [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0") -2. Identify the type of contribution in the commit message - - -### 1. Licensing your Contribution: - -As part of the contribution, in the code comments (or license file) associated with the contribution must include the following: - -Copyright (c) 2015, EMC Corporation - -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. - -This code is provided under the Developer Certificate of Origin- [Insert Name], [Date (e.g., 1/1/15]” - - -**For example:** - -A contribution from **Joe Developer**, an **independent developer**, submitted in **May 15th of 2015** should have an associated license (as file or/and code comments) like this: - -Copyright (c) 2015, Joe Developer - -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. - -This code is provided under the Developer Certificate of Origin- Joe Developer, May 15th 2015” - -### 2. Identifying the Type of Contribution - -In addition to identifying an open source license in the documentation, **all Git Commit messages** associated with a contribution must identify the type of contribution (i.e., Bug Fix, Patch, Script, Enhancement, Tool Creation, or Other). diff --git a/LICENSE b/LICENSE deleted file mode 100644 index 81fa3e6..0000000 --- a/LICENSE +++ /dev/null @@ -1,201 +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 (c) 2015, EMC Corporation - - 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. diff --git a/README.md b/README.md deleted file mode 100644 index 4a047cd..0000000 --- a/README.md +++ /dev/null @@ -1,180 +0,0 @@ -# ScaleIO Plugin for Fuel - -## Overview - -The `ScaleIO` plugin allows to: - * Deploy an EMC ScaleIO v.2.0 cluster together with OpenStack and configure OpenStack to use ScaleIO - as the storage for persistent and ephemeral volumes - * Configure OpenStack to use an existing ScaleIO cluster as a volume backend - * Support the following ScaleIO custer modes: 1_node, 3_node and 5_node - the mode is chosen automatically depending on the number of controller nodes - - -## Requirements - -| Requirement | Version/Comment | -|----------------------------------|-----------------| -| Mirantis OpenStack | 8.0 | -| Mirantis OpenStack | 9.0 | - -## Recommendations - -1. Use configuration with 3 controllers or 5 controllers. - Although 1 controller mode is supported is suitable for testing purposees only. -2. Assign Cinder role for all controllers with allocating minimal diskspace for this role. - Some space is needed because of FUEL framework limitation (this space will not used). - Rest of the space keep for images. -3. Use nodes with similar HW configuration within one group of roles. -4. Deploy SDS coponents only on compute nodes. - Deploymen SDS-es on controllers is supported but it is more suitable for testing than for production environment. -5. On compute nodes keep minimal space for virtual storage on the first disk, rest disks use for ScaleIO. - Some space is needed because of FUEL framework limitations. - Other disks should be unallocated and can be used for ScaleIO. -6. In case of extending cluster with new compute nodes not to forget to run update_hosts tasks on controller nodes via FUEL cli. - -## Limitations - -1. Plugin supports Ubuntu environment only. -2. Multi storage backend is not supported. -3. It is not possible to use different backends for persistent and ephemeral volumes. -4. Disks for SDS-es should be unallocated before deployment via FUEL UI or cli. -5. MDMs and Gateways are deployed together and only onto controller nodes. -6. Adding and removing node(s) to/from the OpenStack cluster won't re-configure the ScaleIO. - -# Installation Guide - -## ScaleIO Plugin install from source code - -To install the ScaleIO Plugin from source code, you first need to prepare an environment to build the RPM file of the plugin. The recommended approach is to build the RPM file directly onto the Fuel Master node so that you won't have to copy that file later. - -Prepare an environment for building the plugin on the **Fuel Master node**. - -0. You might want to make sure that kernel you have on the nodes for ScaleIO SDC installation (compute and cinder nodes) is suitable for the drivers present here: ``` ftp://QNzgdxXix:Aw3wFAwAq3@ftp.emc.com/ ```. Look for something like ``` Ubuntu/2.0.5014.0/4.2.0-30-generic ```. Local kernel version can be found with ``` uname -a ``` command. - -1. Install the standard Linux development tools: - ``` - $ yum install createrepo rpm rpm-build dpkg-devel dpkg-dev git - ``` - -2. Install the Fuel Plugin Builder. To do that, you should first get pip: - ``` - $ easy_install pip - ``` - -3. Then install the Fuel Plugin Builder (the `fpb` command line) with `pip`: - ``` - $ pip install fuel-plugin-builder - ``` - -*Note: You may also have to build the Fuel Plugin Builder if the package version of the -plugin is higher than package version supported by the Fuel Plugin Builder you get from `pypi`. -In this case, please refer to the section "Preparing an environment for plugin development" -of the [Fuel Plugins wiki](https://wiki.openstack.org/wiki/Fuel/Plugins) if you -need further instructions about how to build the Fuel Plugin Builder.* - -4. Clone the ScaleIO Plugin git repository: - ``` - $ git clone https://github.com/openstack/fuel-plugin-scaleio.git - $ cd fuel-plugin-scaleio - $ git checkout "tags/v2.1.3" - ``` - -5. Check that the plugin is valid: - ``` - $ fpb --check . - ``` - -6. Build the plugin: - ``` - $ fpb --build . - ``` - -7. Install plugin: - ``` - $ fuel plugins --install ./scaleio-2.1-2.1.3-1.noarch.rpm - ``` - -## ScaleIO Plugin install from Fuel Plugins Catalog - -To install the ScaleIOv2.0 Fuel plugin: - -1. Download it from the [Fuel Plugins Catalog](https://www.mirantis.com/products/openstack-drivers-and-plugins/fuel-plugins/) - -2. Copy the rpm file to the Fuel Master node - ``` - [root@home ~]# scp scaleio-2.1-2.1.3-1.noarch.rpm root@fuel-master:/tmp - ``` - -3. Log into Fuel Master node and install the plugin using the Fuel CLI - ``` - $ fuel plugins --install ./scaleio-2.1-2.1.3-1.noarch.rpm - ``` - -4. Verify that the plugin is installed correctly - ``` - [root@fuel-master ~]# fuel plugins - id | name | version | package_version - ---|-----------------------|---------|---------------- - 1 | scaleio | 2.1.3 | 3.0.0 - ``` - -# User Guide - -Please read the [ScaleIO Plugin User Guide](doc/source/builddir/ScaleIO-Plugin_Guide.pdf) for full description. - -First of all, ScaleIOv2.0 plugin functionality should be enabled by switching on ScaleIO in the Settings. - -ScaleIO section contains the following info to fill in: - -1. Existing ScaleIO Cluster. - - Set "Use existing ScaleIO" checkbox. - The following parameters should be specified: - * Gateway IP address - IP address of ScaleIO gateway - * Gateway port - Port of ScaleIO gateway - * Gateway user - User to access ScaleIO gateway - * Admin password - Password to access ScaleIO gateway - * Protection domain - The protection domain to use - * Storage pools - Comma-separated list of storage pools - -2. New ScaleIO deployment - - The following parameters should be specified: - * Admin password - Administrator password to set for ScaleIO MDM - * Protection domain - The protection domain to create for ScaleIO cluster - * Storage pools - Comma-separated list of storage pools to create for ScaleIO cluster - * Storage devices - Path to storage devices, comma separated (/dev/sdb,/dev/sdd) - - The following parameters are optional and have default values suitable for most cases: - * Controller as Storage - Use controller nodes for ScaleIO SDS (by default only compute nodes are used for ScaleIO SDS deployment) - * Provisioning type - Thin/Thick provisioning for ephemeral and persistent volumes - * Checksum mode - Checksum protection. ScaleIO protects data in-flight by calculating and validating the checksum value for the payload at both ends. - Note, the checksum feature may have a minor effect on performance. ScaleIO utilizes hardware capabilities for this feature, where possible. - * Spare policy - % out of total space to be reserved for rebalance and redundancy recovery cases. - * Enable Zero Padding for Storage Pools - New volumes will be zeroed if the option enabled. - * Background device scanner - This options enables the background device scanner on the devices in device only mode. - * XtremCache devices - List of SDS devices for SSD caching. Cache is disabled if list empty. - * XtremCache storage pools - List of storage pools which should be cached with XtremCache. - * Capacity high priority alert - Threshold of the non-spare capacity of the Storage Pool that will trigger a high-priority alert, in percentage format. - * Capacity critical priority alert - Threshold of the non-spare capacity of the Storage Pool that will trigger a critical-priority alert, in percentage format. - * Use RAM cache (RMCache) - Enable/Disable use of SDS Servers RAM for caching storage devices in a Storage Pool. - * Passthrough RMCache storage pools - List of Storage Pools to be cached in SDS Servers RAM in passthrough mode (if the 'Use RAM cache (RMCache)' option is enabled) - * Cached RMCache storage pools - List od Storage Pools to be cached in SDS Servers RAM in cached mode (if the 'Use RAM cache (RMCache)' option is enabled) - * Glance images on ScaleIO - Enable/Disable ScaleIO backend for Glance images (It uses cinder backend in Glance to store images on ScaleIO). - This option is available since MOS9.0. - - Configuration of disks for allocated nodes: - The devices listed in the "Storage devices" and "XtremCache devices" should be left unallocated for ScaleIO SDS to work. - -# Contributions - -Please read the [CONTRIBUTING.md](CONTRIBUTING.md) document for the latest information about contributions. - -# Bugs, requests, questions - -Please use the [Launchpad project site](https://launchpad.net/fuel-plugin-scaleio) to report bugs, request features, ask questions, etc. - -# License - -Please read the [LICENSE](LICENSE) document for the latest licensing information. - diff --git a/README.rst b/README.rst new file mode 100644 index 0000000..86e34d6 --- /dev/null +++ b/README.rst @@ -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. diff --git a/Vagrantfile b/Vagrantfile deleted file mode 100644 index 74c00ee..0000000 --- a/Vagrantfile +++ /dev/null @@ -1,31 +0,0 @@ -# -*- mode: ruby -*- -# vi: set ft=ruby : - -$script = <