Improvement: Store plan.raw_content in swift for scalability
Bug #1276905 reported by
Adrian Otto
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Solum |
Opinion
|
Wishlist
|
Pierre Padrixe (stannie) |
Bug Description
The Plan resource has raw_content (the Plan YAML content) that is stored in the database. This has an effective maximum size of whatever the database servers max_allowed_packet setting is. Produce an implementation that stores a reference to an object in swift in the Plan database, instead of the raw_content. When a Plan object is accessed, use the reference to fetch the content from swift.
See: https:/
Changed in solum: | |
assignee: | nobody → Pierre Padrixe (stannie) (pierre-padrixe) |
tags: | added: add-plan-in-swift |
Changed in solum: | |
status: | New → Confirmed |
summary: |
- Scalability: Store plan.raw_content in swift + Improvement: Store plan.raw_content in swift for scalability |
Changed in solum: | |
milestone: | none → juno-2 |
To post a comment you must log in.
Note: The entire Plan resource could be back ended by swift, including all of its metadata. The various attributes could be stored in the swift metadata attached to the YAML object.