Cleanup instance metadata access in nova/compute

Bug #1052557 reported by Rick Harris
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
High
Unassigned

Bug Description

We currently access attributes in a way that obscures the actual system_metadata key, automatically prefixing "image_" for instance.. This makes it difficult for people to read the code to figure out which image-properties they need to be set.

The goal here is to make code more transparent.

Changed in nova:
assignee: nobody → Rick Harris (rconradharris)
importance: Undecided → High
status: New → In Progress
Revision history for this message
Brian Waldon (bcwaldon) wrote :

This feels more like a refactoring blueprint than a bug, no?

Revision history for this message
Tiantian Gao (gtt116) wrote :

As Brian said, it is better to be a blueprint. And it seems like long time no update.

Please feel free to reopen it if continue to work.

Changed in nova:
status: In Progress → Incomplete
assignee: Rick Harris (rconradharris) → nobody
ugvddm (271025598-9)
Changed in nova:
status: Incomplete → Confirmed
status: Confirmed → Incomplete
status: Incomplete → Invalid
status: Invalid → Incomplete
Revision history for this message
Sean Dague (sdague) wrote :

old incomplete bug. Seems like it should actually be a blueprint if it's going to exist at all.

Changed in nova:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.