)]}'
{"nova/objects/block_device.py":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"523bbc856345bcbabfbd4d4ccfdc9287145c4a4f","unresolved":false,"context_lines":[{"line_number":87,"context_line":"        \u0027connection_info\u0027: fields.SensitiveStringField(nullable\u003dTrue),"},{"line_number":88,"context_line":"        \u0027tag\u0027: fields.StringField(nullable\u003dTrue),"},{"line_number":89,"context_line":"        \u0027attachment_id\u0027: fields.UUIDField(nullable\u003dTrue),"},{"line_number":90,"context_line":"        \u0027old_attachment_id\u0027: fields.UUIDField(nullable\u003dTrue),"},{"line_number":91,"context_line":"    }"},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"    def obj_make_compatible(self, primitive, target_version):"}],"source_content_type":"text/x-python","patch_set":1,"id":"df140735_90812ec6","line":90,"range":{"start_line":90,"start_character":9,"end_line":90,"end_character":26},"updated":"2017-06-05 22:04:17.000000000","message":"Instances have a concept of an old/new flavor for resizes (which are just cold migrations with a different flavor).\n\nOur migrations records have an old/new instance type (flavor) and I\u0027m wondering if we could do the same in the migrations table for old/new volume attachments:\n\nhttps://github.com/openstack/nova/blob/master/nova/objects/migration.py#L50\n\nThey would have to be a list since an instance could have multiple volume attachments when it\u0027s being migrated. But storing information relevant to migrations in the migrations object/table would be a much cleaner interface in my opinion rather than cramming it into the BDMs object/table.","commit_id":"184905986715f7605535569f9893bb6662bffff3"}]}