Subtask #5878: erasure plugin mechanism and abstract API - Ceph - Ceph

Custom queries

Backports: mimic
Backports: missing release
Backports: nautilus
Bluestore
Bug queue
Bug queue - no subprojects
Bug triage
Ceph backlog
Crash queue
Crash triage
Feature Requests
Feedback
My issues
Need Review
Pending backports
Priority queue
Product Backlog Scrub
Project Triage
Test Failures

Actions

Copy link

Subtask #5878

closed

Feature #4929: Erasure encoded placement group

Subtask #5877: Plugable erasure code library

erasure plugin mechanism and abstract API

Added by Loïc Dachary over 10 years ago. Updated about 10 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Loïc Dachary

Category:

OSD

Target version:

% Done:

100%

Source:

Development

Tags:

Backport:

Reviewed:

Affected Versions:

Pull request ID:

Description

work in progress

The abstract API is provided by dynamically loaded plugins.

Abstract Interface
Plugin loader
unit tests
- in the test file load the plugin from source
- simple minded xor based erasure code plugin that only supports M=2,K=1
- the plugin can be directed to trigger errors for tests purposes
- implement the test plugin to be the basis of a documented example to follow when implementing a new plugin

Discussions¶

Review request : Erasure Code plugin loader implementation

Related issues 1 (0 open — 1 closed)

Related to Ceph - Feature #6000: EC: [link] erasure plugin mechanism and abstract API

Resolved

Loïc Dachary

08/15/2013

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Loïc Dachary over 10 years ago

Category set to OSD

Actions

Copy link

Updated by Loïc Dachary over 10 years ago

Source changed from other to Development

Actions

Copy link

Updated by Loïc Dachary over 10 years ago

Description updated (diff)

Actions

Copy link

Updated by Loïc Dachary over 10 years ago

Description updated (diff)

Actions

Copy link

Updated by Loïc Dachary over 10 years ago

Description updated (diff)

Actions

Copy link

Updated by Loïc Dachary over 10 years ago

Assignee set to Loïc Dachary

Actions

Copy link

Updated by Loïc Dachary over 10 years ago

Status changed from New to In Progress

Actions

Copy link

Updated by Loïc Dachary over 10 years ago

Description updated (diff)

Actions

Copy link

Updated by Loïc Dachary over 10 years ago

Description updated (diff)

Actions

Copy link

#10

Updated by Loïc Dachary over 10 years ago

Description updated (diff)

Actions

Copy link

#11

Updated by Loïc Dachary over 10 years ago

Description updated (diff)

Actions

Copy link

#12

Updated by Loïc Dachary over 10 years ago

Description updated (diff)

Actions

Copy link

#13

Updated by Loïc Dachary over 10 years ago

Description updated (diff)

Actions

Copy link

#14

Updated by Loïc Dachary over 10 years ago

Description updated (diff)

Actions

Copy link

#15

Updated by Loïc Dachary over 10 years ago

Description updated (diff)

Actions

Copy link

#16

Updated by Loïc Dachary over 10 years ago

Description updated (diff)

Actions

Copy link

#17

Updated by Loïc Dachary over 10 years ago

Description updated (diff)

Actions

Copy link

#18

Updated by Wido den Hollander over 10 years ago

I haven't looked at it in-depth, but one thing I noticed is that Reed-Solomon is always spelled with the first two letters capatalized.

Will this be case sensitve? I would suggest not, since that will confuse users. I personally dislike CLI tools which are case sensitive for key=value parameters. I always prefer lowercase.

Actions

Copy link

#19

Updated by Loïc Dachary over 10 years ago

Wido den Hollander wrote:

Will this be case sensitve? I would suggest not, since that will confuse users. I personally dislike CLI tools which are case sensitive for key=value parameters. I always prefer lowercase.

In this case Reed-Solomon is the value interpreted by the plugin and I agree with you : it would be better if case is ignored :-)

Actions

Copy link

#20