)]}'
{"specs/pike/approved/pxe-boot-instances.rst":[{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"774abf5d4b70368223cd24d4e233c4406eadf0e3","unresolved":false,"context_lines":[{"line_number":41,"context_line":"Currently OVB does PXE booting in one of two ways: a Nova patch applied to the"},{"line_number":42,"context_line":"host cloud or a PXE boot image.  The patch is obviously a problem because it"},{"line_number":43,"context_line":"requires modification of Nova, and the PXE boot image is not ideal because it"},{"line_number":44,"context_line":"can only be used once.  After the \"baremetal\" deployment has been done, the"},{"line_number":45,"context_line":"image has been overwritten and the instance can no longer PXE boot without"},{"line_number":46,"context_line":"being rebuilt to the initial image again.  For automated CI where instances"},{"line_number":47,"context_line":"are deleted and recreated for each test run this is not a problem, but for"},{"line_number":48,"context_line":"interactive developer use it tends to cause problems because developers often"},{"line_number":49,"context_line":"do multiple deployments in a single environment.  It\u0027s very easy to forget to"},{"line_number":50,"context_line":"rebuild the instances and end up booting something you didn\u0027t expect."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Legacy/Non-Cloud Deployment Tooling"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa31d9ce_723a3036","line":49,"range":{"start_line":44,"start_character":24,"end_line":49,"end_character":48},"updated":"2017-02-17 14:55:39.000000000","message":"What about using the PXE image as the rescue image? With lyarwood\u0027s stable rescue disk layout, that should mean you don\u0027t even get your disks reordered during rescue.","commit_id":"c486169291ab05e85d038ffdeb86792dd3118b0e"},{"author":{"_account_id":10135,"name":"Lee Yarwood","display_name":"Lee Yarwood","email":"lyarwood@redhat.com","username":"lyarwood"},"change_message_id":"5022436b335eac9f875c7a8108b2b3a6a100dbb1","unresolved":false,"context_lines":[{"line_number":46,"context_line":"being rebuilt to the initial image again.  For automated CI where instances"},{"line_number":47,"context_line":"are deleted and recreated for each test run this is not a problem, but for"},{"line_number":48,"context_line":"interactive developer use it tends to cause problems because developers often"},{"line_number":49,"context_line":"do multiple deployments in a single environment.  It\u0027s very easy to forget to"},{"line_number":50,"context_line":"rebuild the instances and end up booting something you didn\u0027t expect."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Legacy/Non-Cloud Deployment Tooling"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da36d5c6_ebb3c008","line":49,"updated":"2017-02-18 12:44:55.000000000","message":"stable rescue would allow the instance to pxe from an image without rebuilding but I would assume a user would want to pxe in order to rebuild the instance anyway right? It also wouldn\u0027t allow you to control how the instance is going to pxe outside of whatever you have configured in the env or in the image.","commit_id":"c486169291ab05e85d038ffdeb86792dd3118b0e"},{"author":{"_account_id":10135,"name":"Lee Yarwood","display_name":"Lee Yarwood","email":"lyarwood@redhat.com","username":"lyarwood"},"change_message_id":"5191c958620df270f5a5305c46455b291af53166","unresolved":false,"context_lines":[{"line_number":46,"context_line":"being rebuilt to the initial image again.  For automated CI where instances"},{"line_number":47,"context_line":"are deleted and recreated for each test run this is not a problem, but for"},{"line_number":48,"context_line":"interactive developer use it tends to cause problems because developers often"},{"line_number":49,"context_line":"do multiple deployments in a single environment.  It\u0027s very easy to forget to"},{"line_number":50,"context_line":"rebuild the instances and end up booting something you didn\u0027t expect."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Legacy/Non-Cloud Deployment Tooling"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da36d5c6_eba577b5","line":49,"in_reply_to":"da36d5c6_e030360a","updated":"2017-02-19 21:02:24.000000000","message":"Right sorry, I had the dumb cobbler provisioning image in my head for some reason. Something like iPXE would give you full control.","commit_id":"c486169291ab05e85d038ffdeb86792dd3118b0e"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"17d12bd433ef4ebab33e15a3c6543caa2682e8b5","unresolved":false,"context_lines":[{"line_number":46,"context_line":"being rebuilt to the initial image again.  For automated CI where instances"},{"line_number":47,"context_line":"are deleted and recreated for each test run this is not a problem, but for"},{"line_number":48,"context_line":"interactive developer use it tends to cause problems because developers often"},{"line_number":49,"context_line":"do multiple deployments in a single environment.  It\u0027s very easy to forget to"},{"line_number":50,"context_line":"rebuild the instances and end up booting something you didn\u0027t expect."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Legacy/Non-Cloud Deployment Tooling"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da36d5c6_e030360a","line":49,"in_reply_to":"da36d5c6_ebb3c008","updated":"2017-02-19 18:50:01.000000000","message":"I\u0027m not sure what you mean. I as a user can choose to rescue my instance with any image I want. Given that iPXE has tons of configurable knobs and even some scripting ability, being able to rescue to an iPXE image that I control gives me way more control over what is going on than merely saying \"PXE me please\" and taking whatever behavior I get from qemu.","commit_id":"c486169291ab05e85d038ffdeb86792dd3118b0e"},{"author":{"_account_id":6928,"name":"Ben Nemec","email":"openstack@nemebean.com","username":"bnemec"},"change_message_id":"46228bdac3bf4970e8628eabd863a964f6213ebe","unresolved":false,"context_lines":[{"line_number":41,"context_line":"Currently OVB does PXE booting in one of two ways: a Nova patch applied to the"},{"line_number":42,"context_line":"host cloud or a PXE boot image.  The patch is obviously a problem because it"},{"line_number":43,"context_line":"requires modification of Nova, and the PXE boot image is not ideal because it"},{"line_number":44,"context_line":"can only be used once.  After the \"baremetal\" deployment has been done, the"},{"line_number":45,"context_line":"image has been overwritten and the instance can no longer PXE boot without"},{"line_number":46,"context_line":"being rebuilt to the initial image again.  For automated CI where instances"},{"line_number":47,"context_line":"are deleted and recreated for each test run this is not a problem, but for"},{"line_number":48,"context_line":"interactive developer use it tends to cause problems because developers often"},{"line_number":49,"context_line":"do multiple deployments in a single environment.  It\u0027s very easy to forget to"},{"line_number":50,"context_line":"rebuild the instances and end up booting something you didn\u0027t expect."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"Legacy/Non-Cloud Deployment Tooling"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da36d5c6_3e7e6119","line":49,"range":{"start_line":44,"start_character":24,"end_line":49,"end_character":48},"in_reply_to":"fa31d9ce_723a3036","updated":"2017-02-23 15:11:13.000000000","message":"Thanks, this sounds promising.  I will look into it.","commit_id":"c486169291ab05e85d038ffdeb86792dd3118b0e"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"774abf5d4b70368223cd24d4e233c4406eadf0e3","unresolved":false,"context_lines":[{"line_number":64,"context_line":"I\u0027m unsure of the best way to handle this, but will discuss a few of the"},{"line_number":65,"context_line":"options I\u0027m aware of.  Note that none of them solve all the problems."},{"line_number":66,"context_line":"Part of the motivation for this spec is to get input from the Nova team on"},{"line_number":67,"context_line":"how best to proceed."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Alternatives"},{"line_number":70,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa31d9ce_355b42f8","line":67,"updated":"2017-02-17 14:55:39.000000000","message":"I think we need to have something here to discuss. It\u0027s hard to stimulate conversation when there isn\u0027t something proposed.\n\nI think we can ignore the instance metadata approach as there\u0027s no way we\u0027re going to go that route.\n\nDanB\u0027s prior patchset may be the starting point.\n\nWith that, I have concerns that we\u0027ve previously discussed, like how we ensure that the VM is PXEing on the right interface, or rather, on an interface that isn\u0027t going to expose them to an attacker trying to offer up something malicious for them to boot. Merely saying \"well, they asked for PXE, so the behavior is defined by the hypervisor\" does not make this a feature that is easily usable regardless of the backend.","commit_id":"c486169291ab05e85d038ffdeb86792dd3118b0e"},{"author":{"_account_id":10135,"name":"Lee Yarwood","display_name":"Lee Yarwood","email":"lyarwood@redhat.com","username":"lyarwood"},"change_message_id":"5022436b335eac9f875c7a8108b2b3a6a100dbb1","unresolved":false,"context_lines":[{"line_number":82,"context_line":"  the boot order via the IPMI server linked in the references section."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* Use image metadata.  I haven\u0027t tried this, but I expect it would have the"},{"line_number":85,"context_line":"  same drawbacks as flavor extra-specs."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"* Continue using a PXE boot image.  I\u0027ve discussed the drawbacks to this"},{"line_number":88,"context_line":"  approach above, but it does work for many PXE boot use cases."}],"source_content_type":"text/x-rst","patch_set":1,"id":"da36d5c6_0bb9f4e9","line":85,"updated":"2017-02-18 12:44:55.000000000","message":"Right, however Dan\u0027s proposal doesn\u0027t cover future restarts of the instance that I think is the use case OVB also wants addressed. To cover that we would need to extend that spec to also cover nova start etc.","commit_id":"c486169291ab05e85d038ffdeb86792dd3118b0e"},{"author":{"_account_id":6772,"name":"Stephen Gordon","email":"sgordon@redhat.com","username":"sgordon"},"change_message_id":"88f7d92ddcd154b64e8367fb81a81ef814deae29","unresolved":false,"context_lines":[{"line_number":81,"context_line":"  system behavior as much as possible, it is not ideal to be unable to change"},{"line_number":82,"context_line":"  the boot order via the IPMI server linked in the references section."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* Use image metadata.  I haven\u0027t tried this, but I expect it would have the"},{"line_number":85,"context_line":"  same drawbacks as flavor extra-specs."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"* Continue using a PXE boot image.  I\u0027ve discussed the drawbacks to this"},{"line_number":88,"context_line":"  approach above, but it does work for many PXE boot use cases."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa31d9ce_40a0f5a5","line":85,"range":{"start_line":84,"start_character":0,"end_line":85,"end_character":39},"updated":"2017-02-17 14:12:04.000000000","message":"The biggest difference between this and previous requests I have seen for PXE boot (which have been addressed with the PXE Image in Glance workaround) is that you need to toggle the boot options on a per boot basis.\n\nThere\u0027s not really a mechanism to do this today, regardless of whether you start off the original setting from the flavor extra_specs, metadata, or the image properties.\n\nThe closest proposal I\u0027m aware of was Dan\u0027s virt-image-props-boot-override blueprint:\n\nhttps://blueprints.launchpad.net/nova/+spec/virt-image-props-boot-override\nhttps://review.openstack.org/#/c/230382/\n\nI think this could still be done in two parallel phases though:\n\n1) Add the ability to specify PXE boot based on image properties.\n\n2) Add the ability to override this and other image properties on a per boot basis by reviving Dan\u0027s proposal.","commit_id":"c486169291ab05e85d038ffdeb86792dd3118b0e"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"17d12bd433ef4ebab33e15a3c6543caa2682e8b5","unresolved":false,"context_lines":[{"line_number":82,"context_line":"  the boot order via the IPMI server linked in the references section."},{"line_number":83,"context_line":""},{"line_number":84,"context_line":"* Use image metadata.  I haven\u0027t tried this, but I expect it would have the"},{"line_number":85,"context_line":"  same drawbacks as flavor extra-specs."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"* Continue using a PXE boot image.  I\u0027ve discussed the drawbacks to this"},{"line_number":88,"context_line":"  approach above, but it does work for many PXE boot use cases."}],"source_content_type":"text/x-rst","patch_set":1,"id":"da36d5c6_c055f21d","line":85,"in_reply_to":"da36d5c6_0bb9f4e9","updated":"2017-02-19 18:50:01.000000000","message":"Being able to control that per-start and not just at \"nova boot\" time is really begging for something more robust than extra specs, IMHO. Certainly being able to override extra specs at each start time would provide some very confusing behavior for the user for anything that would have resulted in you being scheduled to a particular host. For that matter, I would expect any cloud wanting to enable this behavior would be expecting to schedule PXE-able instances to specific hosts with known networking that supports the thing they\u0027re trying to do.","commit_id":"c486169291ab05e85d038ffdeb86792dd3118b0e"}]}