)]}'
{"specs/pike/approved/specify-keymap-on-server-boot.rst":[{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"5c65f9167eaf10516673a2013b7c35795bc5b02a","unresolved":false,"context_lines":[{"line_number":11,"context_line":"https://blueprints.launchpad.net/nova/+spec/specify-keymap-on-server-boot"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Currently the keymap of a server (VM instance) is defined"},{"line_number":14,"context_line":"in the configuretion file of the compute node."},{"line_number":15,"context_line":"This blueprint enables us to specify a keymap when creating a server."},{"line_number":16,"context_line":"It is possible to make servers that have different keymaps coexist"},{"line_number":17,"context_line":"by specifying a keymap."}],"source_content_type":"text/x-rst","patch_set":4,"id":"dfeb2761_d190344d","line":14,"updated":"2017-04-04 12:02:31.000000000","message":"configuration","commit_id":"c1893a9ec5c841bd525ca0c553ac40464fd38f15"},{"author":{"_account_id":7634,"name":"Takashi Natsume","email":"takanattie@gmail.com","username":"natsumet"},"change_message_id":"1e837633fc016461dca99ea8551038618336a479","unresolved":false,"context_lines":[{"line_number":11,"context_line":"https://blueprints.launchpad.net/nova/+spec/specify-keymap-on-server-boot"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Currently the keymap of a server (VM instance) is defined"},{"line_number":14,"context_line":"in the configuretion file of the compute node."},{"line_number":15,"context_line":"This blueprint enables us to specify a keymap when creating a server."},{"line_number":16,"context_line":"It is possible to make servers that have different keymaps coexist"},{"line_number":17,"context_line":"by specifying a keymap."}],"source_content_type":"text/x-rst","patch_set":4,"id":"7ffa3b31_222bdf94","line":14,"in_reply_to":"dfeb2761_d190344d","updated":"2017-04-17 04:30:23.000000000","message":"Done","commit_id":"c1893a9ec5c841bd525ca0c553ac40464fd38f15"}],"specs/queens/approved/specify-keymap-on-server-boot.rst":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"48d7d2ccd39930c48d9b600141edf25d186ef7df","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"https://blueprints.launchpad.net/nova/+spec/specify-keymap-on-server-boot"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The keymap of a server (VM instance) is defined"},{"line_number":14,"context_line":"in both the configuration of OS and the configuration file"},{"line_number":15,"context_line":"of the compute node. Currently users cannot change the value"},{"line_number":16,"context_line":"in the configuration file of the compute node."},{"line_number":17,"context_line":"This blueprint enables us to specify a keymap when creating a server"},{"line_number":18,"context_line":"and override the keymap in the configuration file of the compute node."},{"line_number":19,"context_line":"It is possible to make servers that have different keymaps coexist"}],"source_content_type":"text/x-rst","patch_set":10,"id":"1f1a1f67_e1b5dfce","line":16,"range":{"start_line":13,"start_character":0,"end_line":16,"end_character":46},"updated":"2017-07-21 13:57:14.000000000","message":"So, we want to actually drop the second one of these, as seen in https://bugs.launchpad.net/nova/+bug/1682020/. To summarize that bug, we should not be passing keymap configuration to the hypervisor because it\u0027s unnecessary and breaks things for non-US keyboards. The patch I have up for this, https://review.openstack.org/483994, unsets these options by default and will deprecate them in the future.\n\nIn short: extending this feature isn\u0027t necessary because the whole thing should be going away soon","commit_id":"6ad56fae4fe7987cbe6782a4f05eaeb4e37c40e5"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"7354fa5377fce06e0bfdae9aef8c0b760e9bc98b","unresolved":false,"context_lines":[{"line_number":60,"context_line":"Alternatives"},{"line_number":61,"context_line":"------------"},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"There is a way to configure host aggregates for each keymap"},{"line_number":64,"context_line":"and select the aggregate by scheduling filters."},{"line_number":65,"context_line":"But there is an issue about an resource usage efficiency of compute nodes"},{"line_number":66,"context_line":"because host aggregates are required for each keymap."},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"Data model impact"},{"line_number":69,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"df3967d1_2aa621c3","line":66,"range":{"start_line":63,"start_character":0,"end_line":66,"end_character":53},"updated":"2017-07-31 19:16:17.000000000","message":"Per Sean Dague\u0027s earlier -1:\n\n\u003e My question is would it be better to do this via user-data and cloud init? This seems like one of the things that could be done pretty well in that mechanism.\nI get concerned with making this a top level part of the server create, and expecting Nova to change the images here, because by the time we figure out that it\u0027s not possible for the image in question, it\u0027s going to be very late in the process.\n\nI didn\u0027t see a clear response to that - why do we need to do this as part of the top-level server create request with a new field? Why can\u0027t we do this with user-data or even image metadata?","commit_id":"6ad56fae4fe7987cbe6782a4f05eaeb4e37c40e5"}]}