)]}'
{"specs/mitaka/approved/data-security-enforcements.rst":[{"author":{"_account_id":4992,"name":"malini-k-bhandaru","email":"malini.k.bhandaru@intel.com","username":"malini-k-bhandaru"},"change_message_id":"1984cdb9004f1277f8138fb8f4d73217041183ee","unresolved":false,"context_lines":[{"line_number":30,"context_line":"(storage) as well as in motion (over the wire). While Nova has features such as"},{"line_number":31,"context_line":"transparent data encryption, ephemeral storage encryption, etc., the burden of"},{"line_number":32,"context_line":"ensuring that these features are enabled falls on the operator. In other words,"},{"line_number":33,"context_line":"the operator needs to manually check that nova.conf has ephemeral encryption"},{"line_number":34,"context_line":"enabled, that only encrypted Cinder volumes are attached to a VM instance etc."},{"line_number":35,"context_line":"We propose a declarative approach where the operator declares, via image"},{"line_number":36,"context_line":"metadata, that any data generated by a VM instance launched from the image"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a2fa921_553ea328","line":33,"updated":"2015-10-09 08:55:03.000000000","message":"Can a single compute host provide both unencrypted and encrypted volume support?","commit_id":"4c9f81544a79432ce922428f122cb83a034c5f2e"},{"author":{"_account_id":1779,"name":"Daniel Berrange","email":"berrange@redhat.com","username":"berrange"},"change_message_id":"f27545babe3d64b15cdd43d566c77da5bfa820f8","unresolved":false,"context_lines":[{"line_number":70,"context_line":"operators."},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"Please see meeting minutes from etherpad:"},{"line_number":73,"context_line":"https://etherpad.openstack.org/p/PAO-ops-product-wg"},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"Proposed change"},{"line_number":76,"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":2,"id":"9a1a9d01_70c0f27c","line":73,"updated":"2015-10-05 08:58:18.000000000","message":"There are no Mitaka priorities define, since this section should simply say \"None\" and nothing else.  This is not the place to justify your own priorities.","commit_id":"4c9f81544a79432ce922428f122cb83a034c5f2e"},{"author":{"_account_id":1779,"name":"Daniel Berrange","email":"berrange@redhat.com","username":"berrange"},"change_message_id":"f27545babe3d64b15cdd43d566c77da5bfa820f8","unresolved":false,"context_lines":[{"line_number":82,"context_line":"\"data-security-required\" metadata. The specifics of the metadata can be read"},{"line_number":83,"context_line":"in this Glance blueprint -"},{"line_number":84,"context_line":"https://blueprints.launchpad.net/glance/+spec/data-security-metadata"},{"line_number":85,"context_line":"but essentially two pieces of information can be conveyed by such metadata."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"1) Desire for data security."},{"line_number":88,"context_line":"2) The encryption algorithm and strength of keys to be used for encrypting"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a1a9d01_30b59a30","line":85,"updated":"2015-10-05 08:58:18.000000000","message":"Please fully describe the new image property in this spec. Also since this relates to handling of the image, the property name should have a prefix of \u0027img_\u0027 to comply with Nova\u0027s naming conventions for properties it handles. Also you should use underscores rather than hyphens.","commit_id":"4c9f81544a79432ce922428f122cb83a034c5f2e"},{"author":{"_account_id":4992,"name":"malini-k-bhandaru","email":"malini.k.bhandaru@intel.com","username":"malini-k-bhandaru"},"change_message_id":"1984cdb9004f1277f8138fb8f4d73217041183ee","unresolved":false,"context_lines":[{"line_number":82,"context_line":"\"data-security-required\" metadata. The specifics of the metadata can be read"},{"line_number":83,"context_line":"in this Glance blueprint -"},{"line_number":84,"context_line":"https://blueprints.launchpad.net/glance/+spec/data-security-metadata"},{"line_number":85,"context_line":"but essentially two pieces of information can be conveyed by such metadata."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"1) Desire for data security."},{"line_number":88,"context_line":"2) The encryption algorithm and strength of keys to be used for encrypting"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a2fa921_68af477d","line":85,"in_reply_to":"9a1a9d01_30b59a30","updated":"2015-10-09 08:55:03.000000000","message":"Daniel, where should Deepti be presenting the above logic to aid in Mitaka prioritization?","commit_id":"4c9f81544a79432ce922428f122cb83a034c5f2e"},{"author":{"_account_id":4992,"name":"malini-k-bhandaru","email":"malini.k.bhandaru@intel.com","username":"malini-k-bhandaru"},"change_message_id":"1984cdb9004f1277f8138fb8f4d73217041183ee","unresolved":false,"context_lines":[{"line_number":96,"context_line":"   should fail to create an instance."},{"line_number":97,"context_line":"2) A VM instance running the image should connect only to an encrypted"},{"line_number":98,"context_line":"   cinder volume. If user tries to connect to an unencrypted volume, then"},{"line_number":99,"context_line":"   such a request must be declined."},{"line_number":100,"context_line":"3) The encryption algorithm and keys used by ephemeral encryption as well"},{"line_number":101,"context_line":"   as volume encryption are at least as strong as what is specified in the"},{"line_number":102,"context_line":"   image metadata."}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a2fa921_55954384","line":99,"updated":"2015-10-09 08:55:03.000000000","message":"Should there be a manual override?","commit_id":"4c9f81544a79432ce922428f122cb83a034c5f2e"},{"author":{"_account_id":1779,"name":"Daniel Berrange","email":"berrange@redhat.com","username":"berrange"},"change_message_id":"f27545babe3d64b15cdd43d566c77da5bfa820f8","unresolved":false,"context_lines":[{"line_number":120,"context_line":"------------"},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"Other than complete manual enforcement mentioned above, there is no other"},{"line_number":123,"context_line":"alternative that we know of."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Data model impact"},{"line_number":126,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a1a9d01_d0e9be1b","line":123,"updated":"2015-10-05 08:58:18.000000000","message":"The obvious alternative is to define a flavour that provides data security characteristics, then when booting an image that requires data security, choose the appropriate flavour based on required security level. IMHO, use of a flavour makes more sense than use of image metadata. First if a large portion of images need data security, then use of a flavour avoids the need to repeatedly set image properties - admins have to choose a flavour regardless. Use of a flavour also allows the operator to potentially restrict which tenant users are permitted to use the data security enhancements. This may be desirable to either conserve access to a limited hardware resource, or in order to have different billing levels for access of regular vs secure flavours.","commit_id":"4c9f81544a79432ce922428f122cb83a034c5f2e"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"420157d3b9082406ce00da8a861829e1863b543d","unresolved":false,"context_lines":[{"line_number":120,"context_line":"------------"},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"Other than complete manual enforcement mentioned above, there is no other"},{"line_number":123,"context_line":"alternative that we know of."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Data model impact"},{"line_number":126,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ba8a016a_462af991","line":123,"in_reply_to":"7a2fa921_35d527e7","updated":"2015-11-23 16:30:09.000000000","message":"+1 for using flavor here, possibly along side an image property such that an image fails to boot if the flavor does not include this requirement.","commit_id":"4c9f81544a79432ce922428f122cb83a034c5f2e"},{"author":{"_account_id":4992,"name":"malini-k-bhandaru","email":"malini.k.bhandaru@intel.com","username":"malini-k-bhandaru"},"change_message_id":"1984cdb9004f1277f8138fb8f4d73217041183ee","unresolved":false,"context_lines":[{"line_number":120,"context_line":"------------"},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"Other than complete manual enforcement mentioned above, there is no other"},{"line_number":123,"context_line":"alternative that we know of."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Data model impact"},{"line_number":126,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a2fa921_35d527e7","line":123,"in_reply_to":"9a1a9d01_d0e9be1b","updated":"2015-10-09 08:55:03.000000000","message":"Agree that a security flavor is a good alternative, and should be one supported by this BP in addition to image secure metadata. The enforcement should be common to both and as described above. The argument to support image meta data requiring security is to ensure no inadvertent launch of the virtual machine or its volumes in a promiscuous manner. Often flavors are cited for billing purposes. One could argue that regardless of where the constraints arise, when met, appropriate billing should follow. However, until such billing is supported, the secure metadata tag as a first step during launch confirm that the flavor is also secure. A flavor would be \"secure\" if its extra specs mentions the tag \"secure\" and once again enforcement is as described.","commit_id":"4c9f81544a79432ce922428f122cb83a034c5f2e"},{"author":{"_account_id":1779,"name":"Daniel Berrange","email":"berrange@redhat.com","username":"berrange"},"change_message_id":"f27545babe3d64b15cdd43d566c77da5bfa820f8","unresolved":false,"context_lines":[{"line_number":135,"context_line":"Security impact"},{"line_number":136,"context_line":"---------------"},{"line_number":137,"context_line":""},{"line_number":138,"context_line":"Does not define any new security functionality; enforces use of existing ones."},{"line_number":139,"context_line":""},{"line_number":140,"context_line":"Notifications impact"},{"line_number":141,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a1a9d01_d0d0de55","line":138,"updated":"2015-10-05 08:58:18.000000000","message":"It has an impact in so much as any tenant user now has the ability to choose to use specific hosts that support the encryption flavour. This is potentially undesirable as the operator may wish to restrict which tenants are permitted to access such resources. Use of a flavour would avoid opening this up to tenant users directly since access to flavours can be controlled.","commit_id":"4c9f81544a79432ce922428f122cb83a034c5f2e"},{"author":{"_account_id":4992,"name":"malini-k-bhandaru","email":"malini.k.bhandaru@intel.com","username":"malini-k-bhandaru"},"change_message_id":"1984cdb9004f1277f8138fb8f4d73217041183ee","unresolved":false,"context_lines":[{"line_number":159,"context_line":"tagged with data security metadata if the cloud provider is unable to support"},{"line_number":160,"context_line":"the requirements. For example, the end user will not be able to launch a VM"},{"line_number":161,"context_line":"from such an image if the cloud provider has not enabled ephemeral encryption"},{"line_number":162,"context_line":"in the compute nodes."},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"Developer impact"},{"line_number":165,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a2fa921_3571a70f","line":162,"updated":"2015-10-09 08:55:03.000000000","message":"Need to specify the error messages that will be provided users.","commit_id":"4c9f81544a79432ce922428f122cb83a034c5f2e"}]}