Cannot enable HPE3PAR

[Maria Yousaf]

Brief Description
-----------------
After provisioning HPE3PAR settings in the system service-parameters and enabling the backend, I was not able to run system service-parameter-apply cinder due to cinder service not being present in the storage backends.

Severity
--------
Major

Steps to Reproduce
------------------
1. Provision HPE3PAR parameters for any HPE3PAR backend
2. Run:
[wrsroot@controller-0 ~(keystone_admin)]$ system service-parameter-apply cinder
Cannot apply Cinder configuration. Cinder is not currently enabled on either the lvm or ceph backends.
3. Looking at the backends, the following are present:
[wrsroot@controller-0 ~(keystone_admin)]$ system storage-backend-list
+--------------------------------------+-------------+----------+------------+---------------------+----------+--------------------+
| uuid | name | backend | state | task | services | capabilities |
+--------------------------------------+-------------+----------+------------+---------------------+----------+--------------------+
| 5ae9f07a-7614-4c11-a83d-2724296e5c00 | ceph-store | ceph | configured | reconfig-controller | None | min_replication: 1 |
| | | | | | | replication: 2 |
| f26063ff-af50-476c-85d8-e743b02228d6 | shared_serv | external | configured | None | glance | |
| | ices | | | | | |
| | | | | | | |
+--------------------------------------+-------------+----------+------------+---------------------+--------

Expected Behavior
------------------
It should be possible to enable HPE3PAR

Actual Behavior
----------------
It is not possible to enable HPE3PAR

Reproducibility
---------------
Reproducible

System Configuration
--------------------
Dedicated Storage

Branch/Pull Time/Commit
-----------------------
Designer load aligned with April 25th code

Last Pass
---------
First time run in StarlingX

Timestamp/Logs
--------------
N/A. Easy to reproduce

Test Activity
-------------
Regression testing

[Ghada Khalil (gkhalil)]

Marking as release gating for now given this was supported in the previous stx release. As the storage prime, Frank Miller can decide if this support is no longer needed.

[Frank Miller (sensfan22)]

We have no StarlingX user requests at this time to support the HPE 3PAR storage backend in the stx2.0 timeframe. As such removing the stx.2.0 tag and leaving this LP in our backlog.

[Ramaswamy Subramanian (rsubrama)]

No progress on this bug for more than 2 years. Candidate for closure.

If there is no update, this issue is targeted to be closed by Dec 14th.

[Ramaswamy Subramanian (rsubrama)]

Changing the status to 'Won't Fix' as there is no activity.