)]}'
{"magnum/objects/service.py":[{"author":{"_account_id":2834,"name":"Steven Dake","email":"steven.dake@gmail.com","username":"sdake"},"change_message_id":"b4dd0f5865a21d06ba3161093e1ba74a4cda852d","unresolved":false,"context_lines":[{"line_number":34,"context_line":"    fields \u003d {"},{"line_number":35,"context_line":"        \u0027id\u0027: int,"},{"line_number":36,"context_line":"        \u0027uuid\u0027: obj_utils.str_or_none,"},{"line_number":37,"context_line":"        \u0027desc\u0027: obj_utils.str_or_none,"},{"line_number":38,"context_line":"        \u0027bay_uuid\u0027: obj_utils.str_or_none,"},{"line_number":39,"context_line":"    }"},{"line_number":40,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"3a961159_cf6efd2e","line":37,"updated":"2014-12-11 18:30:51.000000000","message":"I dont think we need a desc field.  The Desc can come from parsing the k8s yaml/json passed into the service registration.  If we really want, we can make the client print out the contents of the yaml/json in a user friendly format.  So really what we need is a \"k8s_data_blob\" or something similar, not desc.","commit_id":"13e588767e3b1c526cc687a687ea15cc32325431"}]}