)]}'
{"specs/kilo/hardware-capabilities.rst":[{"author":{"_account_id":114,"name":"Victor Lowther","email":"victor.lowther@gmail.com","username":"victor-lowther"},"change_message_id":"726fbe123c73d7e13093a97d12375ab4d298a84c","unresolved":false,"context_lines":[{"line_number":16,"context_line":"hardware or hardware configurations. Ironic should then ensure these assertions"},{"line_number":17,"context_line":"about the hardware are made valid during the deploy process."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"For instance, a machine booted with capabilities [\"vt_on\", \"turbo_mode_off\"]"},{"line_number":20,"context_line":"would have Ironic properly configure those BIOS settings before deploying an"},{"line_number":21,"context_line":"image onto the node. "},{"line_number":22,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7a8c0949_8473367f","line":19,"updated":"2014-11-06 09:51:26.000000000","message":"Ugh, these need to be key-value pairs, not single-word capabilities, lest the list of node capabilities explode when BIOS settings that can have many possible values are exposed.","commit_id":"3e436fb2d2492ca51d6d49a581f44c45c8e22b77"},{"author":{"_account_id":10202,"name":"Wan-yen Hsu","email":"wanyenhsu@gmail.com"},"change_message_id":"0336ca72df6af473da75de48674621df65c42d9a","unresolved":false,"context_lines":[{"line_number":19,"context_line":"For instance, a machine booted with capabilities [\"vt_on\", \"turbo_mode_off\"]"},{"line_number":20,"context_line":"would have Ironic properly configure those BIOS settings before deploying an"},{"line_number":21,"context_line":"image onto the node. "},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Problem description"},{"line_number":24,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":25,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_34d104ce","line":22,"updated":"2014-11-19 23:41:10.000000000","message":"I tend to think BIOS setting is \"configuration\" rather than \"capability\".   Currently capability is used for scheduling.  So, if  a user creates a flavor for \"capability: vt_on: True\" then Nova scheduler will use this flavor as one of the node selection criteria.  Correspondingly, a bare-metal node will need to configure \"capability: vt_on: True\" as its capability so that Nova will consider it as a candidate..  Since BIOS has many settings, it could result in many capabilitites.  Therefore, Nova scheduler will need to scan a long list of node properties.  I am a bit concern that this will have impact on scheduling performance.  Capability like vt_on can be inferred from CPU processor.   Most (if not all unless it\u0027s very old hardware ) x86 comes with vt capability.  So, if cpu_arch is x86 then we can reasonably assume it has the vt capability.  If this assumption is reasonable, then we don\u0027t need to use vt_on as a scheduling criteria since it\u0027s implied by cpu_arch: x86.  Nova ironic virt driver can then just pass the BIOS setting as part of the instance_info for configuration purpose but not to pass it to Nova scheduler.  Alternatively, we can bundle a few key BIOS setings suitable for a Nova compute host into one single capability, e.g., \"capability: nova_compute_host: True\" so that we won\u0027t have over crowded capabilities.","commit_id":"3e436fb2d2492ca51d6d49a581f44c45c8e22b77"},{"author":{"_account_id":10202,"name":"Wan-yen Hsu","email":"wanyenhsu@gmail.com"},"change_message_id":"0336ca72df6af473da75de48674621df65c42d9a","unresolved":false,"context_lines":[{"line_number":34,"context_line":"Possible use cases include:"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"* Setting specific BIOS settings at deploy time"},{"line_number":37,"context_line":"* Specifying desired firmware versions (and applying that firmware version) at deploy time"},{"line_number":38,"context_line":"* Configuring boot mode (uefi vs bios) at deploy time"},{"line_number":39,"context_line":"* Configuring a boot disk raid at deploy time"},{"line_number":40,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_a81f54b6","line":37,"updated":"2014-11-19 23:41:10.000000000","message":"The desired firmware version is a tricky one to configure as a node capability.  Also,  I am not sure it can be standardized or auto discovered.   Most BMC will be able to discover what firmwre version is currently on the system but not what versions that it can support.   Therefore, most likely a user will need to manually configure all firmware versions or at least min/max firmware versions that a node can support which is a very cumbersome process.  My question is similar, can we use it for configuration but not for scheduling purpose?   My concern is the same that using it as a scheduling capability will complicate the node capability configuration and will have impact on Nova scheduler becuase the scheduler will need to scan a long list of node capabilities.","commit_id":"3e436fb2d2492ca51d6d49a581f44c45c8e22b77"},{"author":{"_account_id":10202,"name":"Wan-yen Hsu","email":"wanyenhsu@gmail.com"},"change_message_id":"fa3ca658e4915ee4661d7510283db84ae52dd449","unresolved":false,"context_lines":[{"line_number":36,"context_line":"* Setting specific BIOS settings at deploy time"},{"line_number":37,"context_line":"* Specifying desired firmware versions (and applying that firmware version) at deploy time"},{"line_number":38,"context_line":"* Configuring boot mode (uefi vs bios) at deploy time"},{"line_number":39,"context_line":"* Configuring a boot disk raid at deploy time"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Proposed change"},{"line_number":42,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7a8c0949_dd4817cf","line":39,"updated":"2014-10-30 04:17:20.000000000","message":"Specifying extra hardware attributes (e.g., server model, secure boot, TPM, ..etc) for Nova scheduling","commit_id":"3e436fb2d2492ca51d6d49a581f44c45c8e22b77"},{"author":{"_account_id":10202,"name":"Wan-yen Hsu","email":"wanyenhsu@gmail.com"},"change_message_id":"fa3ca658e4915ee4661d7510283db84ae52dd449","unresolved":false,"context_lines":[{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Ironic nodes can expose capabilities generally in mutually exclusive sets, for"},{"line_number":48,"context_line":"instance, a node could expose both \"uefi_boot\" and \"bios_boot\", but Ironic"},{"line_number":49,"context_line":"would validate that both were not specified "},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"typically positive and negative, but can be other things that are muFor"},{"line_number":52,"context_line":"instance, vt_on and vt_off might be used to determine if the VT bit should be"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7a8c0949_9d25af0c","line":49,"updated":"2014-10-30 04:17:20.000000000","message":"Can you articualte?  Don\u0027t quite understadn what you meant that \"Ironic would validate that both were not specified\".","commit_id":"3e436fb2d2492ca51d6d49a581f44c45c8e22b77"},{"author":{"_account_id":114,"name":"Victor Lowther","email":"victor.lowther@gmail.com","username":"victor-lowther"},"change_message_id":"726fbe123c73d7e13093a97d12375ab4d298a84c","unresolved":false,"context_lines":[{"line_number":48,"context_line":"instance, a node could expose both \"uefi_boot\" and \"bios_boot\", but Ironic"},{"line_number":49,"context_line":"would validate that both were not specified "},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"typically positive and negative, but can be other things that are muFor"},{"line_number":52,"context_line":"instance, vt_on and vt_off might be used to determine if the VT bit should be"},{"line_number":53,"context_line":"on or off. "},{"line_number":54,"context_line":"Here is where you cover the change you propose to make in detail. How do you"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7a8c0949_e4ff9aa8","line":51,"updated":"2014-11-06 09:51:26.000000000","message":"We should not assume that node settings will be binary, as they are not in general.","commit_id":"3e436fb2d2492ca51d6d49a581f44c45c8e22b77"},{"author":{"_account_id":11297,"name":"Nisha Agarwal","email":"agarwalnisha1980@gmail.com","username":"Nisha"},"change_message_id":"6d22211c5831ff2cefb2f3f1816a2fc637df7c41","unresolved":false,"context_lines":[{"line_number":48,"context_line":"instance, a node could expose both \"uefi_boot\" and \"bios_boot\", but Ironic"},{"line_number":49,"context_line":"would validate that both were not specified "},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"typically positive and negative, but can be other things that are muFor"},{"line_number":52,"context_line":"instance, vt_on and vt_off might be used to determine if the VT bit should be"},{"line_number":53,"context_line":"on or off. "},{"line_number":54,"context_line":"Here is where you cover the change you propose to make in detail. How do you"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_7269d724","line":51,"in_reply_to":"5a890539_887378e6","updated":"2014-11-23 17:50:43.000000000","message":"The spec is already proposed for enhancing ComputeCapability filter.\nhttps://review.openstack.org/#/c/133534/\n\nBut still as i am not sure if Nova will really take it as priority, we can choose to go with the boolean approach.","commit_id":"3e436fb2d2492ca51d6d49a581f44c45c8e22b77"},{"author":{"_account_id":10202,"name":"Wan-yen Hsu","email":"wanyenhsu@gmail.com"},"change_message_id":"0336ca72df6af473da75de48674621df65c42d9a","unresolved":false,"context_lines":[{"line_number":48,"context_line":"instance, a node could expose both \"uefi_boot\" and \"bios_boot\", but Ironic"},{"line_number":49,"context_line":"would validate that both were not specified "},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"typically positive and negative, but can be other things that are muFor"},{"line_number":52,"context_line":"instance, vt_on and vt_off might be used to determine if the VT bit should be"},{"line_number":53,"context_line":"on or off. "},{"line_number":54,"context_line":"Here is where you cover the change you propose to make in detail. How do you"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_887378e6","line":51,"in_reply_to":"7a8c0949_e4ff9aa8","updated":"2014-11-19 23:41:10.000000000","message":"Nova ComputeCapabilityFilter currently can only handle single key value.  It  will require changes to that scheduler to support key value as a list with multiple values.  Alterantively, we can specify each node setting as a boolean setting to work around Nova scheduler issue.  We need to make a decision on which approach to take.","commit_id":"3e436fb2d2492ca51d6d49a581f44c45c8e22b77"}]}