)]}'
{"specs/queens/approved/flavor-description.rst":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"90b49772a08dcebf479ca06ab1e87a9f475883f3","unresolved":false,"context_lines":[{"line_number":39,"context_line":"a flavor and returning the description when showing flavor details."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Microversion 2.47 also changed how the embedded flavor in a server response"},{"line_number":42,"context_line":"body looks by showing the full flavor details rather than just an id/link. As"},{"line_number":43,"context_line":"part of this change, we would also include the ``original_description`` in the"},{"line_number":44,"context_line":"server response body, like we do with the ``original_name``."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Alternatives"},{"line_number":47,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7f515b1d_517db51a","line":44,"range":{"start_line":42,"start_character":75,"end_line":44,"end_character":60},"updated":"2017-09-22 13:51:37.000000000","message":"We said at the PTG that we wouldn\u0027t do this for original_description.","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"d20b8a1bb31bd57ca134a08d338f0053d47be1a7","unresolved":false,"context_lines":[{"line_number":52,"context_line":"-----------------"},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"A new nullable ``description`` String column will be added to the ``flavors``"},{"line_number":55,"context_line":"table in the API database with a maximum length of 255."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"REST API impact"},{"line_number":58,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7f287b81_fed2d15b","line":55,"range":{"start_line":55,"start_character":51,"end_line":55,"end_character":54},"updated":"2017-09-06 16:58:54.000000000","message":"Should this be longer to accommodate non-English characters, like Chinese?\n\nNote that the server description is 255.","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"dc071842bfb4544c1de9e8463ed5fc00c3fce4c7","unresolved":false,"context_lines":[{"line_number":52,"context_line":"-----------------"},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"A new nullable ``description`` String column will be added to the ``flavors``"},{"line_number":55,"context_line":"table in the API database with a maximum length of 255."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"REST API impact"},{"line_number":58,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f2577a7_4a57b6cb","line":55,"range":{"start_line":55,"start_character":51,"end_line":55,"end_character":54},"in_reply_to":"5f2577a7_1181fec3","updated":"2017-09-15 20:57:32.000000000","message":"255 seems fine to me.  People are going to use what you give them, and make it work.  Agree if they need more, they can provide some kind of reference/link.","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"36fb7406b60ad99e54fb85db8e9ff075a4e76050","unresolved":false,"context_lines":[{"line_number":52,"context_line":"-----------------"},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"A new nullable ``description`` String column will be added to the ``flavors``"},{"line_number":55,"context_line":"table in the API database with a maximum length of 255."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"REST API impact"},{"line_number":58,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f2577a7_1181fec3","line":55,"range":{"start_line":55,"start_character":51,"end_line":55,"end_character":54},"in_reply_to":"5f2577a7_1c7eee18","updated":"2017-09-14 22:24:31.000000000","message":"If you went beyond 255 I guess you could provide a high level description and then link to something more detailed in your product documentation...if you haven\u0027t already for your baremetal flavors. Just a thought. I think we definitely want this bound though so we can validate the size in the request schema.","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":5754,"name":"Alex Xu","email":"hejie.xu@intel.com","username":"xuhj"},"change_message_id":"d1fc9e48d120179af46ea6690e4c1626dd5727a2","unresolved":false,"context_lines":[{"line_number":52,"context_line":"-----------------"},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"A new nullable ``description`` String column will be added to the ``flavors``"},{"line_number":55,"context_line":"table in the API database with a maximum length of 255."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"REST API impact"},{"line_number":58,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f2577a7_2cca344d","line":55,"range":{"start_line":55,"start_character":51,"end_line":55,"end_character":54},"in_reply_to":"5f2577a7_4a57b6cb","updated":"2017-09-18 06:51:54.000000000","message":"255 is enough for Chinese.","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":7156,"name":"Mathieu Gagné","email":"mgagne@calavera.ca","username":"mgagne"},"change_message_id":"ae98caa97c3461441a7a43701e56c40f347c223b","unresolved":false,"context_lines":[{"line_number":52,"context_line":"-----------------"},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"A new nullable ``description`` String column will be added to the ``flavors``"},{"line_number":55,"context_line":"table in the API database with a maximum length of 255."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"REST API impact"},{"line_number":58,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f2577a7_1c7eee18","line":55,"range":{"start_line":55,"start_character":51,"end_line":55,"end_character":54},"in_reply_to":"7f287b81_fed2d15b","updated":"2017-09-13 01:46:23.000000000","message":"I don\u0027t have any strong opinion on that one as I only use English characters. For what it\u0027s worth, I tried to build a super long/verbose description for our most complex baremetal flavor and couldn\u0027t reach 255 characters.","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":7730,"name":"Sahid Orentino Ferdjaoui","email":"sahid.ferdjaoui@industrialdiscipline.com","username":"sahid"},"change_message_id":"379f334bea191a1bd76f3139e82026352fce1d29","unresolved":false,"context_lines":[{"line_number":179,"context_line":""},{"line_number":180,"context_line":"  TODO(mriedem): discuss this at the PTG; if the flavor behavior changes"},{"line_number":181,"context_line":"  based on extra specs, the description might need to be updated, so we could"},{"line_number":182,"context_line":"  provide an update flavor mechanism but only for the description field, not"},{"line_number":183,"context_line":"  the name or any other attributes."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":".. _schema: https://github.com/openstack/nova/blob/16.0.0/nova/api/validation/parameter_types.py#L266"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f2577a7_e5c7df11","line":182,"updated":"2017-09-14 10:13:17.000000000","message":"It something we should provide in that first implementation, at least to provide ability for operators to set \u0027description\u0027 to their current flavors.","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"90b49772a08dcebf479ca06ab1e87a9f475883f3","unresolved":false,"context_lines":[{"line_number":179,"context_line":""},{"line_number":180,"context_line":"  TODO(mriedem): discuss this at the PTG; if the flavor behavior changes"},{"line_number":181,"context_line":"  based on extra specs, the description might need to be updated, so we could"},{"line_number":182,"context_line":"  provide an update flavor mechanism but only for the description field, not"},{"line_number":183,"context_line":"  the name or any other attributes."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":".. _schema: https://github.com/openstack/nova/blob/16.0.0/nova/api/validation/parameter_types.py#L266"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7f515b1d_51e6d518","line":182,"in_reply_to":"5f2577a7_e5c7df11","updated":"2017-09-22 13:51:37.000000000","message":"Yeah we agreed at the PTG that we should allow updating the flavor description.","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"dc071842bfb4544c1de9e8463ed5fc00c3fce4c7","unresolved":false,"context_lines":[{"line_number":202,"context_line":""},{"line_number":203,"context_line":"The python-novaclient CLI and API bindings will be updated to allow creating"},{"line_number":204,"context_line":"and showing flavor details with a description field, including the embedded"},{"line_number":205,"context_line":"flavor when showing server instance details."},{"line_number":206,"context_line":""},{"line_number":207,"context_line":"Performance Impact"},{"line_number":208,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f2577a7_eac30288","line":205,"updated":"2017-09-15 20:57:32.000000000","message":"OSC parity too, please.","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"549447bf162b4a149c45038580debec8d92d2ad7","unresolved":false,"context_lines":[{"line_number":202,"context_line":""},{"line_number":203,"context_line":"The python-novaclient CLI and API bindings will be updated to allow creating"},{"line_number":204,"context_line":"and showing flavor details with a description field, including the embedded"},{"line_number":205,"context_line":"flavor when showing server instance details."},{"line_number":206,"context_line":""},{"line_number":207,"context_line":"Performance Impact"},{"line_number":208,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f2577a7_6dd96c55","line":205,"in_reply_to":"5f2577a7_4d57d0cb","updated":"2017-09-15 21:52:59.000000000","message":"Yeah, so dtroyer and I talked about this some on Monday.  Thing is, we don\u0027t necessarily need to come up to parity on everything in order to implement a new feature.  This seems like a perfect example of that.  It seems like, where possible, it would be a good idea to update OSC for new features moving forward so we don\u0027t continue to widen the parity gap indefinitely.","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":23942,"name":"Matt Kucia","email":"maciej@kucia.net","username":"maciejkucia"},"change_message_id":"7233b0434f81c925ebb66d929ca94892e7c0588b","unresolved":false,"context_lines":[{"line_number":202,"context_line":""},{"line_number":203,"context_line":"The python-novaclient CLI and API bindings will be updated to allow creating"},{"line_number":204,"context_line":"and showing flavor details with a description field, including the embedded"},{"line_number":205,"context_line":"flavor when showing server instance details."},{"line_number":206,"context_line":""},{"line_number":207,"context_line":"Performance Impact"},{"line_number":208,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f2577a7_a4e762ac","line":205,"in_reply_to":"5f2577a7_6dd96c55","updated":"2017-09-17 22:24:58.000000000","message":"255 is a value already used in nova DB:\n- instance display_description\n- security_group description","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"a38398fb7fc5a09252f8d51aa8c1dd76be34da75","unresolved":false,"context_lines":[{"line_number":202,"context_line":""},{"line_number":203,"context_line":"The python-novaclient CLI and API bindings will be updated to allow creating"},{"line_number":204,"context_line":"and showing flavor details with a description field, including the embedded"},{"line_number":205,"context_line":"flavor when showing server instance details."},{"line_number":206,"context_line":""},{"line_number":207,"context_line":"Performance Impact"},{"line_number":208,"context_line":"------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f2577a7_4d57d0cb","line":205,"in_reply_to":"5f2577a7_eac30288","updated":"2017-09-15 21:47:08.000000000","message":"If you want to implement 2.2 -\u003e 2.53 in OSC first, be my guest. :) But that\u0027s why we don\u0027t call out updating OSC for microversions in nova specs, since we don\u0027t have any parity in OSC already.","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"dc071842bfb4544c1de9e8463ed5fc00c3fce4c7","unresolved":false,"context_lines":[{"line_number":235,"context_line":"* Add a description field to the Flavor versioned object."},{"line_number":236,"context_line":"* Add a microversion to the REST API to create and show flavors with a"},{"line_number":237,"context_line":"  description."},{"line_number":238,"context_line":"* CLI and API binding changes to python-novaclient."},{"line_number":239,"context_line":""},{"line_number":240,"context_line":""},{"line_number":241,"context_line":"Dependencies"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f2577a7_8a38fe9f","line":238,"updated":"2017-09-15 20:57:32.000000000","message":"and osc","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"dc071842bfb4544c1de9e8463ed5fc00c3fce4c7","unresolved":false,"context_lines":[{"line_number":255,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":256,"context_line":""},{"line_number":257,"context_line":"The compute REST API reference would be updated for the new microversion."},{"line_number":258,"context_line":""},{"line_number":259,"context_line":"References"},{"line_number":260,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":261,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5f2577a7_0a4c0e40","line":258,"updated":"2017-09-15 20:57:32.000000000","message":"Might also be neat to go back through existing user docs and update (some) examples to show use of the new field.","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"90b49772a08dcebf479ca06ab1e87a9f475883f3","unresolved":false,"context_lines":[{"line_number":255,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":256,"context_line":""},{"line_number":257,"context_line":"The compute REST API reference would be updated for the new microversion."},{"line_number":258,"context_line":""},{"line_number":259,"context_line":"References"},{"line_number":260,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":261,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7f515b1d_71af9194","line":258,"in_reply_to":"5f2577a7_0a4c0e40","updated":"2017-09-22 13:51:37.000000000","message":"Yeah I could update https://docs.openstack.org/nova/latest/admin/flavors.html","commit_id":"b7ec7bbcd956c85117aa6c0999ed408be0e9ee18"},{"author":{"_account_id":7156,"name":"Mathieu Gagné","email":"mgagne@calavera.ca","username":"mgagne"},"change_message_id":"c46942e4fbcbcd612556dd58a3a5afbeffb091bc","unresolved":false,"context_lines":[{"line_number":49,"context_line":"   resource, we will make the following changes to the ``POST /flavors``"},{"line_number":50,"context_line":"   request schema:"},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"   * The ``id`` field will be limited to a maximum length of 36 characters."},{"line_number":53,"context_line":"     If an id is not specified when creating a flavor, the compute API"},{"line_number":54,"context_line":"     generates one using a UUID."},{"line_number":55,"context_line":"   * The ``name`` field will be limited to a maximum length of 64 characters."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_547afef0","line":52,"updated":"2017-10-12 15:07:58.000000000","message":"This kind of change is unrelated to adding a description field. Furthermore, this is a non-backward compatible change. Some of our flavorid are longer than 36 characters.\n\nI don\u0027t see the technical need to limit this field, it feels more like a subjective one which has huge technical impact. So I\u0027m against such restrictions.","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"479dfd1b13146f33dee5f62e31513b366d892677","unresolved":false,"context_lines":[{"line_number":49,"context_line":"   resource, we will make the following changes to the ``POST /flavors``"},{"line_number":50,"context_line":"   request schema:"},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"   * The ``id`` field will be limited to a maximum length of 36 characters."},{"line_number":53,"context_line":"     If an id is not specified when creating a flavor, the compute API"},{"line_number":54,"context_line":"     generates one using a UUID."},{"line_number":55,"context_line":"   * The ``name`` field will be limited to a maximum length of 64 characters."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_a64900d1","line":52,"in_reply_to":"5f4e5783_547afef0","updated":"2017-10-12 18:48:32.000000000","message":"\u003e This kind of change is unrelated to adding a description field.\n \u003e Furthermore, this is a non-backward compatible change. Some of our\n \u003e flavorid are longer than 36 characters.\n \u003e \n \u003e I don\u0027t see the technical need to limit this field, it feels more\n \u003e like a subjective one which has huge technical impact. So I\u0027m\n \u003e against such restrictions.\n\nIt\u0027s backward compatible in the sense that you need to opt-in to the restriction with the new microversion. You can still crate flavors with long ids and names before the new microversion, you would just have an annoying two-step dance if you also wanted the flavor to have a description once created (you\u0027d have to use the new PUT /flavors API).\n\nThere is no technical reason to limit the field, it was made at sdague\u0027s request to limit the number of 255-length fields for flavors, because the argument was made that you don\u0027t need a description if you just use the full 255 length available for the flavorid and/or name. So this was a compromise.","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":7156,"name":"Mathieu Gagné","email":"mgagne@calavera.ca","username":"mgagne"},"change_message_id":"29887854ea425128503af239b818f920c37d7fe6","unresolved":false,"context_lines":[{"line_number":49,"context_line":"   resource, we will make the following changes to the ``POST /flavors``"},{"line_number":50,"context_line":"   request schema:"},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"   * The ``id`` field will be limited to a maximum length of 36 characters."},{"line_number":53,"context_line":"     If an id is not specified when creating a flavor, the compute API"},{"line_number":54,"context_line":"     generates one using a UUID."},{"line_number":55,"context_line":"   * The ``name`` field will be limited to a maximum length of 64 characters."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_c65bdc51","line":52,"in_reply_to":"5f4e5783_868e04ce","updated":"2017-10-12 19:01:58.000000000","message":"\u003e Are there other levels of restrictions that you\u0027d be ok with. \n\nWhy do you feel the need to introduce restrictions that wasn\u0027t there before? What will it accomplish? For me as a user, it introduces pain I don\u0027t need for no actual gain.","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"f070a6b0218c6fbe10dd81db0f7ea9ebe0210aee","unresolved":false,"context_lines":[{"line_number":49,"context_line":"   resource, we will make the following changes to the ``POST /flavors``"},{"line_number":50,"context_line":"   request schema:"},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"   * The ``id`` field will be limited to a maximum length of 36 characters."},{"line_number":53,"context_line":"     If an id is not specified when creating a flavor, the compute API"},{"line_number":54,"context_line":"     generates one using a UUID."},{"line_number":55,"context_line":"   * The ``name`` field will be limited to a maximum length of 64 characters."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_868e04ce","line":52,"in_reply_to":"5f4e5783_a64900d1","updated":"2017-10-12 18:57:40.000000000","message":"Are there other levels of restrictions that you\u0027d be ok with. I think it just gets confusing to say:\n\nHere are 3 x 255 character fields, one you can update, and all cloud providers will use them differently. I\u0027d be fine with other restrictions like 64 or even 120 characters on these non description fields, or make name updatable, and just have people use name as the description.","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":7156,"name":"Mathieu Gagné","email":"mgagne@calavera.ca","username":"mgagne"},"change_message_id":"fefbf333c50d0c99bec41556a24ad45038892efa","unresolved":false,"context_lines":[{"line_number":49,"context_line":"   resource, we will make the following changes to the ``POST /flavors``"},{"line_number":50,"context_line":"   request schema:"},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"   * The ``id`` field will be limited to a maximum length of 36 characters."},{"line_number":53,"context_line":"     If an id is not specified when creating a flavor, the compute API"},{"line_number":54,"context_line":"     generates one using a UUID."},{"line_number":55,"context_line":"   * The ``name`` field will be limited to a maximum length of 64 characters."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_0671f4e0","line":52,"in_reply_to":"5f4e5783_a64900d1","updated":"2017-10-12 18:59:42.000000000","message":"Therefore I see no real gain for the end user to limit those fields, except a very subjective one. The user will have to go through hopes to get what he had before. My suggestion is to not limit them.\n\n\u003e because the argument was made that you don\u0027t need a description if you just use the full 255 length available for the flavorid and/or name.\n\nThis is missing the point that flavorid/name have unique keys on them while description won\u0027t. This is artificially limiting the \"usefulness\" of flavorid/name fields to justify the introduction of description field because \"why 3x 255 fields?\".","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"d2f788e06635f60c19d1b4f75d93dbe8b096c6fd","unresolved":false,"context_lines":[{"line_number":49,"context_line":"   resource, we will make the following changes to the ``POST /flavors``"},{"line_number":50,"context_line":"   request schema:"},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"   * The ``id`` field will be limited to a maximum length of 36 characters."},{"line_number":53,"context_line":"     If an id is not specified when creating a flavor, the compute API"},{"line_number":54,"context_line":"     generates one using a UUID."},{"line_number":55,"context_line":"   * The ``name`` field will be limited to a maximum length of 64 characters."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_1a03880f","line":52,"in_reply_to":"5f4e5783_c65bdc51","updated":"2017-10-12 19:08:13.000000000","message":"Ok, the uniqueness constraint does pretty much remove the ability to use name descriptively.\n\nGiven that, and real operator feedback here, I\u0027m fine with these as 255 character values.","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":7156,"name":"Mathieu Gagné","email":"mgagne@calavera.ca","username":"mgagne"},"change_message_id":"c46942e4fbcbcd612556dd58a3a5afbeffb091bc","unresolved":false,"context_lines":[{"line_number":57,"context_line":"   Those two changes are in the REST API schema validation *only*. There will"},{"line_number":58,"context_line":"   be no changes to the size of the ``flavors.flavorid`` or ``flavors.name``"},{"line_number":59,"context_line":"   columns in the database, since that would potentially break any existing"},{"line_number":60,"context_line":"   deployments with long flavor ids and names."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Alternatives"},{"line_number":63,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_f45faa6f","line":60,"updated":"2017-10-12 15:07:58.000000000","message":"This would prevent new flavors with current pattern to be created.","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"182da2679b8557eff3f05ad4d7146ec22c173051","unresolved":false,"context_lines":[{"line_number":72,"context_line":"table in the API database with a maximum length of 255."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"255 should be sufficient for a detailed flavor description. Anything needed"},{"line_number":75,"context_line":"beyond that could provide a link to deployment-specific documentation."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"REST API impact"},{"line_number":78,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_d19840c1","line":75,"updated":"2017-10-12 14:17:22.000000000","message":"Yeah, that\u0027s what we agreed at the PTG.","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"96efb3602b8334493a6c4e3e088e830177c3885e","unresolved":false,"context_lines":[{"line_number":128,"context_line":"               }"},{"line_number":129,"context_line":"           ],"},{"line_number":130,"context_line":"           \"name\": \"2vcpu-1024ram-10disk-baremetal-10gb\","},{"line_number":131,"context_line":"           \"description\": \"Baremetal flavor with 10GB network card.\","},{"line_number":132,"context_line":"           \"ram\": 1024,"},{"line_number":133,"context_line":"           \"swap\": \"\","},{"line_number":134,"context_line":"           \"rxtx_factor\": 1.0,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_fbeb2ad9","line":131,"range":{"start_line":131,"start_character":0,"end_line":131,"end_character":69},"updated":"2017-10-12 03:09:27.000000000","message":"just to be clear- \u0027description\u0027 will be mandatory in response and with default value of null if not provided in request. (same as description behavior in /servers API)","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"7c0d8b2e7ed74cc5be334482a65d61c40359543e","unresolved":false,"context_lines":[{"line_number":128,"context_line":"               }"},{"line_number":129,"context_line":"           ],"},{"line_number":130,"context_line":"           \"name\": \"2vcpu-1024ram-10disk-baremetal-10gb\","},{"line_number":131,"context_line":"           \"description\": \"Baremetal flavor with 10GB network card.\","},{"line_number":132,"context_line":"           \"ram\": 1024,"},{"line_number":133,"context_line":"           \"swap\": \"\","},{"line_number":134,"context_line":"           \"rxtx_factor\": 1.0,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_b1d6e4c2","line":131,"range":{"start_line":131,"start_character":0,"end_line":131,"end_character":69},"in_reply_to":"5f4e5783_91b9a82f","updated":"2017-10-12 14:37:18.000000000","message":"Sorry for confusion. i mean \u0027description\u0027 (server description not flavor description) in POST server API.  like you gave the ref in L87.\n\nWe are on same page now as you mentioned it is required field.","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":5754,"name":"Alex Xu","email":"hejie.xu@intel.com","username":"xuhj"},"change_message_id":"e627c0990f0fc2da9ce84f814a48c3cf1b954826","unresolved":false,"context_lines":[{"line_number":128,"context_line":"               }"},{"line_number":129,"context_line":"           ],"},{"line_number":130,"context_line":"           \"name\": \"2vcpu-1024ram-10disk-baremetal-10gb\","},{"line_number":131,"context_line":"           \"description\": \"Baremetal flavor with 10GB network card.\","},{"line_number":132,"context_line":"           \"ram\": 1024,"},{"line_number":133,"context_line":"           \"swap\": \"\","},{"line_number":134,"context_line":"           \"rxtx_factor\": 1.0,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_b3714d0f","line":131,"range":{"start_line":131,"start_character":0,"end_line":131,"end_character":69},"in_reply_to":"5f4e5783_fbeb2ad9","updated":"2017-10-12 12:58:45.000000000","message":"+1","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"c31d51681b5deb98007dadb50cc04e0aaeb2f257","unresolved":false,"context_lines":[{"line_number":128,"context_line":"               }"},{"line_number":129,"context_line":"           ],"},{"line_number":130,"context_line":"           \"name\": \"2vcpu-1024ram-10disk-baremetal-10gb\","},{"line_number":131,"context_line":"           \"description\": \"Baremetal flavor with 10GB network card.\","},{"line_number":132,"context_line":"           \"ram\": 1024,"},{"line_number":133,"context_line":"           \"swap\": \"\","},{"line_number":134,"context_line":"           \"rxtx_factor\": 1.0,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_91b9a82f","line":131,"range":{"start_line":131,"start_character":0,"end_line":131,"end_character":69},"in_reply_to":"5f4e5783_fbeb2ad9","updated":"2017-10-12 14:13:49.000000000","message":"\u003e same as description behavior in /servers API\n\nI\u0027m not sure what you\u0027re referring to in the /servers API - the spec says we won\u0027t include the embedded flavor description in the server details. Maybe you meant something else. Otherwise yes, description would be a required field in the response for showing flavor details at the new microversion.","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"96efb3602b8334493a6c4e3e088e830177c3885e","unresolved":false,"context_lines":[{"line_number":190,"context_line":"               }"},{"line_number":191,"context_line":"           ],"},{"line_number":192,"context_line":"           \"name\": \"2vcpu-1024ram-10disk-baremetal-10gb\","},{"line_number":193,"context_line":"           \"description\": \"Baremetal flavor with 10GB network card.\","},{"line_number":194,"context_line":"           \"ram\": 1024,"},{"line_number":195,"context_line":"           \"swap\": \"\","},{"line_number":196,"context_line":"           \"rxtx_factor\": 1.0,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_9bab1688","line":193,"range":{"start_line":193,"start_character":11,"end_line":193,"end_character":69},"updated":"2017-10-12 03:09:27.000000000","message":"ditto. about \"description\" mandatory in response.","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"96efb3602b8334493a6c4e3e088e830177c3885e","unresolved":false,"context_lines":[{"line_number":207,"context_line":"  scheduling behavior with host aggregates, so in that case the description may"},{"line_number":208,"context_line":"  need to be updated also."},{"line_number":209,"context_line":""},{"line_number":210,"context_line":"  .. note:: The only field that can be updated is the ``description`` field."},{"line_number":211,"context_line":"            Nova has historically intentionally not included an API to update"},{"line_number":212,"context_line":"            a flavor because that would be confusing for instances already"},{"line_number":213,"context_line":"            created with that flavor. Needing to change any other aspect of a"},{"line_number":214,"context_line":"            flavor requires deleting and/or creating a new flavor."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":"  Request sample::"},{"line_number":217,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_1b9f2660","line":214,"range":{"start_line":210,"start_character":0,"end_line":214,"end_character":66},"updated":"2017-10-12 03:09:27.000000000","message":"+1","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"96efb3602b8334493a6c4e3e088e830177c3885e","unresolved":false,"context_lines":[{"line_number":217,"context_line":""},{"line_number":218,"context_line":"     {"},{"line_number":219,"context_line":"       \"flavor\": {"},{"line_number":220,"context_line":"           \"description\": \"Baremetal flavor with 10GB network card.\""},{"line_number":221,"context_line":"       }"},{"line_number":222,"context_line":"     }"},{"line_number":223,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_db8f4d2c","line":220,"range":{"start_line":220,"start_character":0,"end_line":220,"end_character":68},"updated":"2017-10-12 03:09:27.000000000","message":"this can be mandatory field in PUT as it is the only field to update ?","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":5754,"name":"Alex Xu","email":"hejie.xu@intel.com","username":"xuhj"},"change_message_id":"e627c0990f0fc2da9ce84f814a48c3cf1b954826","unresolved":false,"context_lines":[{"line_number":217,"context_line":""},{"line_number":218,"context_line":"     {"},{"line_number":219,"context_line":"       \"flavor\": {"},{"line_number":220,"context_line":"           \"description\": \"Baremetal flavor with 10GB network card.\""},{"line_number":221,"context_line":"       }"},{"line_number":222,"context_line":"     }"},{"line_number":223,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_f37105e0","line":220,"range":{"start_line":220,"start_character":0,"end_line":220,"end_character":68},"in_reply_to":"5f4e5783_db8f4d2c","updated":"2017-10-12 12:58:45.000000000","message":"+1 also, it should be the required field","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"96efb3602b8334493a6c4e3e088e830177c3885e","unresolved":false,"context_lines":[{"line_number":241,"context_line":"               }"},{"line_number":242,"context_line":"           ],"},{"line_number":243,"context_line":"           \"name\": \"2vcpu-1024ram-10disk-baremetal-10gb\","},{"line_number":244,"context_line":"           \"description\": \"Baremetal flavor with 10GB network card.\","},{"line_number":245,"context_line":"           \"ram\": 1024,"},{"line_number":246,"context_line":"           \"swap\": \"\","},{"line_number":247,"context_line":"           \"rxtx_factor\": 1.0,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_7b8a991b","line":244,"range":{"start_line":244,"start_character":11,"end_line":244,"end_character":68},"updated":"2017-10-12 03:09:27.000000000","message":"ditto to have it mandatory in response.","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"182da2679b8557eff3f05ad4d7146ec22c173051","unresolved":false,"context_lines":[{"line_number":262,"context_line":"--------------------"},{"line_number":263,"context_line":""},{"line_number":264,"context_line":"The ``flavor.create``, ``flavor.update`` and ``flavor.delete`` versioned"},{"line_number":265,"context_line":"notifications will be updated to include the new nullable description field."},{"line_number":266,"context_line":""},{"line_number":267,"context_line":"Other end user impact"},{"line_number":268,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5f4e5783_b1d8247f","line":265,"updated":"2017-10-12 14:17:22.000000000","message":"++","commit_id":"409c9be5c28ba2ce5a4f4a253bbcdcf5ca8d39c2"},{"author":{"_account_id":5754,"name":"Alex Xu","email":"hejie.xu@intel.com","username":"xuhj"},"change_message_id":"cda83203131779adb55b2031ac6d0daa1801d676","unresolved":false,"context_lines":[{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Microversion 2.47 changed how the embedded flavor in a server response"},{"line_number":42,"context_line":"body looks by showing the full flavor details rather than just an id/link."},{"line_number":43,"context_line":"Despite this change, we will *not* include the embedded flavor description in"},{"line_number":44,"context_line":"the server response body."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Alternatives"},{"line_number":47,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5f4e5783_6ef4f1cf","line":44,"range":{"start_line":43,"start_character":21,"end_line":44,"end_character":25},"updated":"2017-10-13 06:07:24.000000000","message":"From the use-case in the line 30, actually I think it is useful in the server response, that help the user to know the instance created with which flavor special when the original flavor deleted...I see the comment about why not put in the server response, it is only about we can\u0027t put it in the instance_extra table? that sounds like we deny a use-case because of some technical problem.","commit_id":"c37930d604063c44e919d81209f3e1d46a19a283"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"a303d43d350e13b6f91e70b67fd5d6912dd00c86","unresolved":false,"context_lines":[{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Microversion 2.47 changed how the embedded flavor in a server response"},{"line_number":42,"context_line":"body looks by showing the full flavor details rather than just an id/link."},{"line_number":43,"context_line":"Despite this change, we will *not* include the embedded flavor description in"},{"line_number":44,"context_line":"the server response body."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Alternatives"},{"line_number":47,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5f4e5783_c8dd1843","line":44,"range":{"start_line":43,"start_character":21,"end_line":44,"end_character":25},"in_reply_to":"5f4e5783_080690cf","updated":"2017-10-13 07:47:49.000000000","message":"to correct: identifying the flavor in server by current attribute name, ram, cpu etc only","commit_id":"c37930d604063c44e919d81209f3e1d46a19a283"},{"author":{"_account_id":5754,"name":"Alex Xu","email":"hejie.xu@intel.com","username":"xuhj"},"change_message_id":"e9dbac9693c6e804920cae7719b928602759a6a7","unresolved":false,"context_lines":[{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Microversion 2.47 changed how the embedded flavor in a server response"},{"line_number":42,"context_line":"body looks by showing the full flavor details rather than just an id/link."},{"line_number":43,"context_line":"Despite this change, we will *not* include the embedded flavor description in"},{"line_number":44,"context_line":"the server response body."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Alternatives"},{"line_number":47,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5f4e5783_29e497e0","line":44,"range":{"start_line":43,"start_character":21,"end_line":44,"end_character":25},"in_reply_to":"5f4e5783_5ead622f","updated":"2017-10-14 02:43:17.000000000","message":"Agree with catalog, and as Gmann said, the original name in the server response can be used to link to the catalog(even the flavor removed, and the operators will keep those the old flavor info in the catalog also). But if we say catalog, then description field becomes useless again :)\n\nIf we have catalog, I think the description field is quick hint for the user, then user need to look up the catalog.","commit_id":"c37930d604063c44e919d81209f3e1d46a19a283"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"c098c1af089470efc40aa75c974e617948815544","unresolved":false,"context_lines":[{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Microversion 2.47 changed how the embedded flavor in a server response"},{"line_number":42,"context_line":"body looks by showing the full flavor details rather than just an id/link."},{"line_number":43,"context_line":"Despite this change, we will *not* include the embedded flavor description in"},{"line_number":44,"context_line":"the server response body."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Alternatives"},{"line_number":47,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5f4e5783_080690cf","line":44,"range":{"start_line":43,"start_character":21,"end_line":44,"end_character":25},"in_reply_to":"5f4e5783_6ef4f1cf","updated":"2017-10-13 07:45:55.000000000","message":"If we show \u0027flavor description\u0027 in server response, then one point to consider is that \u0027description\u0027 is modifiable so there will be chance to have stale flavor\u0027s description in server response. \n\nHonestly saying i am ok with just identifying the flavor in server by name, id only","commit_id":"c37930d604063c44e919d81209f3e1d46a19a283"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"4b7bc0f68fe84eeaa931a97840e6d9dbc016895c","unresolved":false,"context_lines":[{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Microversion 2.47 changed how the embedded flavor in a server response"},{"line_number":42,"context_line":"body looks by showing the full flavor details rather than just an id/link."},{"line_number":43,"context_line":"Despite this change, we will *not* include the embedded flavor description in"},{"line_number":44,"context_line":"the server response body."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Alternatives"},{"line_number":47,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5f4e5783_5ead622f","line":44,"range":{"start_line":43,"start_character":21,"end_line":44,"end_character":25},"in_reply_to":"5f4e5783_c8dd1843","updated":"2017-10-13 09:00:35.000000000","message":"I don\u0027t really see the need for embedding the flavor description in the server response. I rather see the usecase for operators wanting to provide something like a catalog of flavors and explaining each of them so users can take one of them. That said, once the user takes a flavor and uses it, he knows *why* he did that, right? So, why should we again provide the catalog ? \nIf he doesn\u0027t remember *why* he used it, then he can still look at the Flavors API to find the reason (exactly like when I\u0027m not remembering why I paid for my car so I\u0027m looking at the manufactors catalog ;) )","commit_id":"c37930d604063c44e919d81209f3e1d46a19a283"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"4b7bc0f68fe84eeaa931a97840e6d9dbc016895c","unresolved":false,"context_lines":[{"line_number":53,"context_line":"-----------------"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"A new nullable ``description`` `TEXT`_ column will be added to the ``flavors``"},{"line_number":56,"context_line":"table in the API database with a maximum length of 65535."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"Since we will not index or filter on this field, making it a TEXT (65536 bytes)"},{"line_number":59,"context_line":"versus TINYTEXT (256 bytes) field is not really a concern."}],"source_content_type":"text/x-rst","patch_set":4,"id":"5f4e5783_1e7c8ab3","line":56,"updated":"2017-10-13 09:00:35.000000000","message":"I thought we agreed at the PTG to not do that but since I wasn\u0027t in the IRC channel yesterday, I understand that some operators prefer to have a TEXT for it.","commit_id":"c37930d604063c44e919d81209f3e1d46a19a283"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"8203c5a63fb8f8b45ecb3c6727c363c5ca30b522","unresolved":false,"context_lines":[{"line_number":53,"context_line":"-----------------"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"A new nullable ``description`` `TEXT`_ column will be added to the ``flavors``"},{"line_number":56,"context_line":"table in the API database with a maximum length of 65535."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"Since we will not index or filter on this field, making it a TEXT (65536 bytes)"},{"line_number":59,"context_line":"versus TINYTEXT (256 bytes) field is not really a concern."}],"source_content_type":"text/x-rst","patch_set":4,"id":"5f4e5783_d895e134","line":56,"in_reply_to":"5f4e5783_1e7c8ab3","updated":"2017-10-13 13:39:58.000000000","message":"The IRC discussion was here:\n\nhttp://eavesdrop.openstack.org/irclogs/%23openstack-operators/%23openstack-operators.2017-10-12.log.html#t2017-10-12T18:48:52\n\nThe point being what I say on L58 below. If we\u0027re not going to return the thing in the server response or store it with the embedded instance.flavor, and there really shouldn\u0027t be much if any performance difference between storing TINYTEXT or VARCHAR(255) and TEXT in the database, we might as well allow it.\n\nI pointed out that server description is only 255 but sdague correctly pointed out that server description is really a \u0027note to self\u0027 on a per-instance basis, whereas flavors are global so it makes sense to allow more verbose descriptions in those.","commit_id":"c37930d604063c44e919d81209f3e1d46a19a283"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"15aa4f2e5f5dd3abbc121ab199b2daafc0d6ab4e","unresolved":false,"context_lines":[{"line_number":53,"context_line":"-----------------"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"A new nullable ``description`` `TEXT`_ column will be added to the ``flavors``"},{"line_number":56,"context_line":"table in the API database with a maximum length of 65535."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"Since we will not index or filter on this field, making it a TEXT (65536 bytes)"},{"line_number":59,"context_line":"versus TINYTEXT (256 bytes) field is not really a concern."}],"source_content_type":"text/x-rst","patch_set":4,"id":"5f4e5783_db371bff","line":56,"in_reply_to":"5f4e5783_d895e134","updated":"2017-10-13 14:23:22.000000000","message":"Okay thanks for having taken time to describe the main motivation.\n\nAnd yeah, I agree, describing flavors is more like a catalog, compared to describing my servers that I know of.","commit_id":"c37930d604063c44e919d81209f3e1d46a19a283"}]}