Opened at 2015-11-03T04:48:18Z
Closed at 2020-10-30T12:35:44Z
#2566 closed defect (wontfix)
RAIC: remove HP authentication endpoints from code and docs for OpenStack
| Reported by: | daira | Owned by: | daira |
|---|---|---|---|
| Priority: | minor | Milestone: | undecided |
| Component: | code-storage | Version: | 1.10.1 |
| Keywords: | hp raic openstack docs | Cc: | |
| Launchpad Bug: |
Description (last modified by daira)
Dear HP Helion Public Cloud Customer,
As you have been previously notified, HP has announced that HP Helion Public Cloud will cease providing services to customers on January 31, 2016. This email serves as written notice that HP will terminate the Customer Agreement between you and HP, pursuant to the termination for convenience provision therein, effective January 31, 2016.
It is important that you shut down or move any workloads or data now on HP Helion Public Cloud by January 31, 2016, as there will be no access to your account after that date. If you have any questions contact HP Cloud Support.
So these HP authentication endpoints should be removed from the code and docs.
Change History (2)
comment:1 Changed at 2015-11-03T04:49:07Z by daira
- Description modified (diff)
- Status changed from new to assigned
comment:2 Changed at 2020-10-30T12:35:44Z by exarkun
- Resolution set to wontfix
- Status changed from assigned to closed
The established line of development on the "cloud backend" branch has been abandoned. This ticket is being closed as part of a batch-ticket cleanup for "cloud backend"-related tickets.
If this is a bug, it is probably genuinely no longer relevant. The "cloud backend" branch is too large and unwieldy to ever be merged into the main line of development (particularly now that the Python 3 porting effort is significantly underway).
If this is a feature, it may be relevant to some future efforts - if they are sufficiently similar to the "cloud backend" effort - but I am still closing it because there are no immediate plans for a new development effort in such a direction.
Tickets related to the "leasedb" are included in this set because the "leasedb" code is in the "cloud backend" branch and fairly well intertwined with the "cloud backend". If there is interest in lease implementation change at some future time then that effort will essentially have to be restarted as well.