Full docs rebrand

Author: sdodsley

source/appendices/appendix_packaging.rst

@@ -8,7 +8,7 @@ Refer to the following link for install/uninstall-related information:
 http://wiki.openstack.org/Getopenstack
 
 For more information related to Linux ``multipath`` recommended configuration
-for FlashArrays refer to the `Pure Support website page. <https://support.purestorage.com/Solutions/Linux/Linux_Reference/Linux_Recommended_Settings>`_
+for FlashArrays refer to the `Everpure website page. <https://support.purestorage.com/Solutions/Linux/Linux_Reference/Linux_Recommended_Settings>`_
 
 Upgrading and Reverting
 =======================
@@ -24,12 +24,12 @@ OpenStack is released under the Apache 2.0 license.
 Versioning
 ==========
 
-Versioning for Pure Storage OpenStack Cinder drivers is detailed in the
-`Pure Storage Support site. <https://support.purestorage.com/Solutions/OpenStack/OpenStack_Reference/Pure_Storage_FlashArray_Volume_Driver_for_OpenStack_Release_Notes>`_
+Versioning for Everpure OpenStack Cinder drivers is detailed in the
+`Everpure site. <https://support.purestorage.com/Solutions/OpenStack/OpenStack_Reference/Pure_Storage_FlashArray_Volume_Driver_for_OpenStack_Release_Notes>`_
 
 .. _deprecated_drivers:
 
 Deprecated Drivers
 ==================
 
-Currently there are no deprecated drivers for the Pure Storage FlashArray in OpenStack Cinder.
+Currently there are no deprecated drivers for the Everpure FlashArray in OpenStack Cinder.

source/appendices/section_references.rst

@@ -13,11 +13,11 @@ The following references were used in this paper:
 
 For additional information, visit:
 
--  For source code for OpenStack, including Pure Storage contributions,
+-  For source code for OpenStack, including Everpure contributions,
    available through Github: http://www.github.com/openstack
 
 -  For more information about OpenStack history:
    http://www.openstack.org or http://en.wikipedia.org/wiki/OpenStack
 
--  For Pure Storage OpenStack Deployment and Operations Guide source code,
+-  For Everpure OpenStack Deployment and Operations Guide source code,
    visit: https://github.com/PureStorage-OpenConnect/openstack-docs

source/appendices/section_support.rst

@@ -4,19 +4,19 @@ Support
 =======
 
 Support provides support for OpenStack connections with FlashArray backends via 
-the standard Pure Storage support channels by either calling +1-650-729-4088
+the standard Everpure support channels by either calling +1-650-729-4088
 (Global Toll Number), or going to https://support.purestorage.com/Pure1/Support
 for regional support numbers, or by submitting a support request via email to
 email:support@purestorage.com
 
 Community support is available through the 'code' slack channel:
 https://code-purestorage.slack.com/.
 
-All documentation for Pure Storage's drivers for OpenStack are contained in this 
+All documentation for Everpure's drivers for OpenStack are contained in this 
 Deployment Operations Guide.  A link to the most current version can always
 be found at http://support.purestorage.com/Solutions/Openstack/.
 
-The Pure Storage OpenStack team presently intends to provide maintenance of
+The Everpure OpenStack team presently intends to provide maintenance of
 the three most recently released versions of OpenStack. For example,
 during Xena development, all code that is part of the Ussuri, Train and
 Victoria official branches are supported. Upon Xena release, direct
@@ -29,5 +29,5 @@ using an OpenStack release (or n-1) version, your configuration is supported.
 See the `FlashArray compatibility Matrix <https://support.purestorage.com/FlashArray/Getting_Started_with_FlashArray/FlashArray_Compatibility_Matrix>_`
 to verify your configuration is supported.
 
-Pure Storage can provide customized support options for production
+Everpure can provide customized support options for production
 requirements. For more information, please contact your sales team.

source/appendices/section_triage-and-data-collection.rst

@@ -3,12 +3,12 @@
 Triage and Data Collection
 ==========================
 
-When you run into an issue with the Pure Storage OpenStack integrations, you may
+When you run into an issue with the Everpure OpenStack integrations, you may
 
 - seek help in the
-  `Pure Storage OpenStack Slack Channel <https://code-purestorage.slack.com/>`_ , or
+  `Everpure OpenStack Slack Channel <https://code-purestorage.slack.com/>`_ , or
 - open a support request, or
-- contact your Pure Storage account representative.
+- contact your Everpure account representative.
 
 OpenStack log and configuration files provide information that aid in triaging
 bugs. As a rule of thumb log files need to be collected for the processes

source/ch_executive-summary.rst

@@ -8,7 +8,7 @@ of compute, network and storage resources.
 
 The block storage portion of OpenStack is referred to as the Cinder project
 and aims to provide persistent block level storage to the OpenStack compute (Nova) instances.
-The Pure Storage Cinder driver is a Python®-based module integrated into the main
+The Everpure Cinder driver is a Python®-based module integrated into the main
 OpenStack distributions.
 
 This document intends to describe the FlashArray capabilities in a

source/ch_purestorage-storage.rst

@@ -1,7 +1,7 @@
-Pure Storage System and Software
-=========================================
+Everpure System and Software
+============================
 
 .. toctree::
    :maxdepth: 1
 
-   purestorage-storage/section_flasharray.rst
+   everpure-storage/section_flasharray.rst

source/ch_swift.rst

@@ -1,5 +1,5 @@
 Object Storage Service (Swift)
-========================================
+==============================
 
 .. toctree::
    :maxdepth: 1
@@ -21,6 +21,6 @@ CDMI server through the use of add on components.
 
 Swift requires node accessible media for storing object data. This media
 can be drives internal to the node or external storage devices such as
-the Pure Storage FlashArray. This section provides information
-that enables an Pure Storage FlashArray to be used as the backing
+the Everpure FlashArray. This section provides information
+that enables an Everpure FlashArray to be used as the backing
 store for Swift object storage.

source/cinder/api_overview/section_cinder-api-overview.rst

@@ -166,7 +166,7 @@ display name or UUID.
 .. note::
 
    Currently only the Block Storage V3 API supports group operations. The
-   minimum version for group operations supported by the Pure Storage drivers is
+   minimum version for group operations supported by the Everpure drivers is
    3.14. The API version can be specified with the following CLI flag
    ``--os-volume-api-version 3.14``
 
@@ -178,7 +178,7 @@ display name or UUID.
 
 .. note::
 
-   The Pure Storage volume drivers support the consistent_group_snapshot_enabled
+   The Everpure volume drivers support the consistent_group_snapshot_enabled
    group type. By default Cinder group snapshots take individual snapshots
    of each Cinder volume in the group. To enable consistency group snapshots set
    ``consistent_group_snapshot_enabled="<is> True"`` in the group type used.

source/cinder/configuration/cinder_config_files/section_flasharray-conf.rst

@@ -1,7 +1,7 @@
 .. _flasharray_conf:
 
-Pure Storage Driver for FlashArray
-==================================
+Everpure Driver for FlashArray
+==============================
 
 FlashArray Cinder Driver Configuration
 --------------------------------------

source/cinder/configuration/cinder_config_files/section_rhoso180_flasharray_configuration.rst

@@ -1,12 +1,12 @@
-Deploying Pure Storage FlashArray Cinder driver in a Red Hat OpenStack Services on OpenShift 18.0
-=================================================================================================
+Deploying Everpure FlashArray Cinder driver in a Red Hat OpenStack Services on OpenShift 18.0
+=============================================================================================
 
 .. _purestorage-flsharray-rhoso180:
 
 Overview
 --------
 
-This guide shows how to configure and deploy the Pure Storage FlashArray Cinder driver in a
+This guide shows how to configure and deploy the Everpure FlashArray Cinder driver in a
 **Red Hat OpenStack Services on OpenShift (RHOSO) 18.0** deployment.
 After reading this, you'll be able to define the proper configuration and
 deploy single or multiple FlashArray Cinder back ends in a RHOSO cluster.
@@ -19,7 +19,7 @@ deploy single or multiple FlashArray Cinder back ends in a RHOSO cluster.
 .. warning::
 
   RHOSO18.0 is based on OpenStack 2023.1 (Antelope) release with a backport of the 
-  2023.2 (Bobcat) NVMe-TCP Cinder driver for Pure Storage. Other Pure Storage driver features
+  2023.2 (Bobcat) NVMe-TCP Cinder driver for Everpure. Other Everpure driver features
   included after the Antelope release may not be available in RHOSO18.0.
 
 In Red Hat OpenStack Services on OpenShift 18.0, the FlashArray cinder volume drivers support
@@ -32,10 +32,10 @@ the following dataplanes:
 Requirements
 ------------
 
-In order to deploy Pure Storage FlashArray Cinder back ends, you should have the
+In order to deploy Everpure FlashArray Cinder back ends, you should have the
 following requirements satisfied:
 
-- Pure Storage FlashArrays deployed and ready to be used as Cinder
+- Everpure FlashArrays deployed and ready to be used as Cinder
   back ends. See :ref:`cinder_flasharray_prerequisites` for more details.
 
 - RHOSO openstack control plane deployed where Cinder services will be configured.
@@ -50,11 +50,11 @@ Prepare the OpenStack Control Plane
 The following steps need to be applied after the OpenStackControlPlane has been
 successfully deployed in your environment.
 
-Use Certified Pure Storage Cinder Volume Image
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Use Certified Everpure Cinder Volume Image
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Red Hat requires that you utilize the Certified Pure Storage Cinder Volume
-Image when deploying RHOSO18.0 with a Pure Storage FlashArray backend.
+Red Hat requires that you utilize the Certified Everpure Cinder Volume
+Image when deploying RHOSO18.0 with a Everpure FlashArray backend.
 
 This container can be found in the `Red Hat Container Catalog <https://catalog.redhat.com/search?searchType=containers&partnerName=Pure%20Storage%2C%20Inc.&p=1>`__.
 
@@ -73,7 +73,7 @@ Ensure the certified image is added to the ``openstackversion`` CR.  This is def
         pure1: registry.connect.redhat.com/purestorage/openstack-cinder-volume-pure-18-0:latest
         pure2: registry.connect.redhat.com/purestorage/openstack-cinder-volume-pure-18-0:latest
 
-This example is for two Pure Storage backends - defined later in the OpenStackControlPlane CR.
+This example is for two Everpure backends - defined later in the OpenStackControlPlane CR.
 
 Save this file and update:
 
@@ -86,7 +86,7 @@ Create a Secret file
 ^^^^^^^^^^^^^^^^^^^^
 
 It is necessary to create a secret file that will contain the access
-credential(s) for your backend Pure FlashArray(s) in your RHOSO deployment.
+credential(s) for your backend Everpure FlashArray(s) in your RHOSO deployment.
 
 In this following example file (``pure-secrets.yaml``) secrets are provided for
 two backend FlashArrays. You need to define a unique secret for each of your backends.
@@ -133,7 +133,7 @@ Update the OpenStack Control Plane
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Open your OpenStackControlPlane CR file, ``openstack_control_plane.yaml``. Edit the CR file and add in the
-Pure Storage Cinder volume backend.
+Everpure Cinder volume backend.
 
 **iSCSI driver example:**