Actions
Task #3371
closedSupport OSTree in pulp3 (based on pulp2 implementation)
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Target Release - OSTree:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Overview¶
Add a pulp3 plugin to support OSTree. Most of the heavy lifting can be canablized from the pulp2 plugin.
Mainly just need to:
- Port mongoengine models to django models.
- Add django scaffolding (viewset, serializers, etc).
- Port code from Steps to tasks.
- Directly reuse the libostree (lib) module.
Model¶
Metadata(GenericKeyValueModel):
Remote(Model):
"This is a local OSTree repository where everything is stored."
- url (CharField)
- storage_path (CharField)
Commit(Model):
- hash (CharField)
- metadata (GenericKeyValueRelation) => Metadata (cascade)
- remote (ForeignKey) => Remote (cascade)
Ref (Model):
- path (CharField)
- commit (ForeignKey) => Commit (cascade)
- remote (ForeignKey) => Remote (cascade)
Branch(Content):
- ref (ForeignKey) => Ref (protect)
RemoteSummary(Model):
- remote (ForeignKey) => Remote (protect)
- repository (ForeignKey) => Repository (cascade)
- ref (ForeignKey) => Ref (protect)
Questions:¶
- How do orphaned refs, commits and remotes get cleaned up?
Updated by ttereshc over 3 years ago
- Subject changed from Support OSTree in pulp3. to Support OSTree in pulp3 (based on pulp2 implementation)
- Status changed from NEW to CLOSED - WONTFIX
There were critical issues found in the pulp 2 implementation of the plugin. The design and use cases needs to be revisited. Users are expected to open a story if there is an interest in OSTree support, and we'll work from there.
Actions