)]}'
{"specs/newton/approved/flavor-class.rst":[{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"beee521d648944592669d0f7f4c07a7c19aee23f","unresolved":false,"context_lines":[{"line_number":74,"context_line":"will be created. These has been work related to Quota policy engine"},{"line_number":75,"context_line":"proposed which makes sure that these validation for quota allocation,"},{"line_number":76,"context_line":"reservations are done and governed by a quota engine framework but discussion"},{"line_number":77,"context_line":"about it is out of the scope of this spec."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"Alternatives"},{"line_number":80,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"bab6814e_48a2514c","line":77,"updated":"2016-05-20 21:26:55.000000000","message":"The above doesn\u0027t make sense to me. What precisely does the vm_flavor_class {...} represent? What is 100 cores and 20G of RAM?\n\nOverall, I\u0027m not a fan of expanding the definition of flavors in the Compute API any further. The extra_specs crap was an abomination that has forced upon Nova API users a random unstandardized mess of key/value tags. The I/O \"quota\" stuff uses extra_specs to encode bandwidth quota quantities into a string key/value pair. It\u0027s also extremely unclear in this spec why you seem to be mixing the concept of a hardware configuration with a flavor. The two are entirely separate things.\n\nWe are actively moving *away* from storing the flavor (and thus the flavor \"class\" in this proposal) at all. Once an instance launch request is received by the API server, that flavor is exploded almost immediately into its component quantitative resources and qualitative strings (capabiities) as represented by the RequestSpec object. The flavor, long-term, is nothing more than a way for public cloud operators to provide instance type templates to their users as billing entities. The flavor won\u0027t be used in scheduling decisions -- instead, its quantitative resources and qualitative capability representations will be used by the scheduler to make its placement decisions.","commit_id":"17354b2924b16b0ada34038e2ee3c51243f04000"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"beee521d648944592669d0f7f4c07a7c19aee23f","unresolved":false,"context_lines":[{"line_number":137,"context_line":"Work Items"},{"line_number":138,"context_line":"----------"},{"line_number":139,"context_line":""},{"line_number":140,"context_line":"1. An extension for manage flavor classes needs to be introduced."},{"line_number":141,"context_line":"2. Methods to create/update/delete/get flavor class details needs to"},{"line_number":142,"context_line":"   be introduced."},{"line_number":143,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"bab6814e_a88bfdc1","line":140,"updated":"2016-05-20 21:26:55.000000000","message":"-1 no more API extensions.","commit_id":"17354b2924b16b0ada34038e2ee3c51243f04000"}]}