cloud backend OpenStack: crawlers are not working correctly with HP Cloud Object Storage #1923

Closed
opened 2013-02-26 02:48:21 +00:00 by davidsarah · 6 comments
davidsarah commented 2013-02-26 02:48:21 +00:00
Owner

The smoke-testing I did to confirm that the OpenStack code was working with HP Cloud Object Storage, only covered basic upload/download. It appears that list queries done by the accounting crawler are not finding any existing shares, causing the accounting crawler to treat all shares in the leasedb as "disappeared". This doesn't happen with Rackspace Cloud Files.

List queries done in order to find specific shares for download are working, so it's probably something to do with the prefix handling (unless I'm misinterpreting the logs).

The smoke-testing I did to confirm that the OpenStack code was working with HP Cloud Object Storage, only covered basic upload/download. It appears that list queries done by the accounting crawler are not finding any existing shares, causing the accounting crawler to treat all shares in the leasedb as "disappeared". This doesn't happen with Rackspace Cloud Files. List queries done in order to find specific shares for download *are* working, so it's probably something to do with the prefix handling (unless I'm misinterpreting the logs).
tahoe-lafs added the
code-storage
normal
defect
cloud-branch
labels 2013-02-26 02:48:21 +00:00
tahoe-lafs added this to the undecided milestone 2013-02-26 02:48:21 +00:00
davidsarah commented 2013-02-26 03:04:09 +00:00
Author
Owner

Hmm, the ability to run tests against an actual cloud storage service rather than mock_cloud (as suggested by itamar) would help here.

Hmm, the ability to run tests against an actual cloud storage service rather than mock_cloud (as suggested by itamar) would help here.
davidsarah commented 2013-03-01 01:42:35 +00:00
Author
Owner

This appears to be unrelated to #1921, even though it has superficially similar symptoms.

This appears to be unrelated to #1921, even though it has superficially similar symptoms.
tahoe-lafs modified the milestone from undecided to 1.12.0 2014-12-06 15:44:38 +00:00
warner commented 2016-03-22 05:02:25 +00:00
Author
Owner

Milestone renamed

Milestone renamed
tahoe-lafs modified the milestone from 1.12.0 to 1.13.0 2016-03-22 05:02:25 +00:00
warner commented 2016-06-28 18:17:14 +00:00
Author
Owner

renaming milestone

renaming milestone
tahoe-lafs modified the milestone from 1.13.0 to 1.14.0 2016-06-28 18:17:14 +00:00
exarkun commented 2020-06-30 14:45:13 +00:00
Author
Owner

Moving open issues out of closed milestones.

Moving open issues out of closed milestones.
tahoe-lafs modified the milestone from 1.14.0 to 1.15.0 2020-06-30 14:45:13 +00:00
exarkun commented 2020-10-30 12:35:44 +00:00
Author
Owner

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.

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.
tahoe-lafs added the
wontfix
label 2020-10-30 12:35:44 +00:00
exarkun closed this issue 2020-10-30 12:35:44 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1923
No description provided.