)]}'
{"specs/backlog/approved/instance-users.rst":[{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"0a2c2e0bdfe48b711f1b273b6e8bf567adff6d21","unresolved":false,"context_lines":[{"line_number":115,"context_line":" * Octavia"},{"line_number":116,"context_line":" * Any other that uses a Guest Agent"},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"Varous new applications can be created that interact with OpenStack services."},{"line_number":119,"context_line":" * A website VM that stores/retrieves stuff in Swift"},{"line_number":120,"context_line":" * A Nagios application could be written that uses credentials to monitor the"},{"line_number":121,"context_line":"   VM\u0027s in the tenant its running on automatically."}],"source_content_type":"text/x-rst","patch_set":14,"id":"ba3cc151_1d74e033","line":118,"updated":"2015-07-02 04:35:59.000000000","message":"s/Varous/Various","commit_id":"91aeff4656444768ef7d5688ece0cfeaa12ac14f"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"0a2c2e0bdfe48b711f1b273b6e8bf567adff6d21","unresolved":false,"context_lines":[{"line_number":215,"context_line":"   returned synchronously from the create call. This will be used by"},{"line_number":216,"context_line":"   orchestration systems such as Heat to enable the Instance User permissions"},{"line_number":217,"context_line":"   to resources it needs. For example, via Barbican Container ACL\u0027s."},{"line_number":218,"context_line":"   The instance_user_id will be fetched from Keystone synchronously."},{"line_number":219,"context_line":" * The instance delete code will be extended to notify Keystone when an"},{"line_number":220,"context_line":"   instance_user_id is set and needs deleting."},{"line_number":221,"context_line":" * The Nova Meta Data server and Config Drive data are extended to contain the"}],"source_content_type":"text/x-rst","patch_set":14,"id":"ba3cc151_dd05187a","line":218,"updated":"2015-07-02 04:35:59.000000000","message":"Who created the instance_user_id?  Keystone?  What if my Keystone is using a read-only LDAP driver (thus no user creation)?","commit_id":"91aeff4656444768ef7d5688ece0cfeaa12ac14f"},{"author":{"_account_id":8119,"name":"Eric Brown","email":"eric_wade_brown@yahoo.com","username":"ericwb"},"change_message_id":"0a2c2e0bdfe48b711f1b273b6e8bf567adff6d21","unresolved":false,"context_lines":[{"line_number":231,"context_line":"   Note: The data only shows in Config Drive if the instance user flag was"},{"line_number":232,"context_line":"   specified on server create."},{"line_number":233,"context_line":" * A new InstanceUserMetaData plugin named SerialConsoleLogInstanceUserMetaData"},{"line_number":234,"context_line":"   inheriting from InstanceUserMetaData wil be created. It will add the"},{"line_number":235,"context_line":"   \"instance_user_url\" key with a url value and set the value of \"auth_type\" to"},{"line_number":236,"context_line":"   \"SerialConsoleLog\"."},{"line_number":237,"context_line":" * The nova-api will be extended with another server similar to the Meta Data"}],"source_content_type":"text/x-rst","patch_set":14,"id":"ba3cc151_9dfb107b","line":234,"updated":"2015-07-02 04:35:59.000000000","message":"s/wil/will","commit_id":"91aeff4656444768ef7d5688ece0cfeaa12ac14f"},{"author":{"_account_id":16277,"name":"Pradeep Kumar Singh","email":"ps4openstack@gmail.com","username":"pradeep_singh"},"change_message_id":"03d80afe8827053e96e92bfec861115d6b7214a3","unresolved":false,"context_lines":[{"line_number":29,"context_line":"securely to the Instance in order to get a Secret from the Secret store?\""},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"Another need is getting a secret to an Instance in order for it to connect to"},{"line_number":32,"context_line":"a Zarqar queue in order to process requests directed to a Guest Agent running"},{"line_number":33,"context_line":"on that Instance. Zaqar only allows you to talk to it with a Keystone Token."},{"line_number":34,"context_line":"Heat for example needs to bind its Guest Agent to Zaqar to enable Software"},{"line_number":35,"context_line":"Deployments to work securely and with low overhead."}],"source_content_type":"text/x-rst","patch_set":17,"id":"1a4dcd0f_2e701372","line":32,"updated":"2015-08-04 06:43:35.000000000","message":"small typo s/Zarqar/Zaqar/","commit_id":"accd4955858c3dee73d0cd0a746d8ff4a2e3beda"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"0fb2011db38e83ec32702ee1b67529b7c51a7130","unresolved":false,"context_lines":[{"line_number":29,"context_line":"securely to the Instance in order to get a Secret from the Secret store?\""},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"Another need is getting a secret to an Instance in order for it to connect to"},{"line_number":32,"context_line":"a Zarqar queue in order to process requests directed to a Guest Agent running"},{"line_number":33,"context_line":"on that Instance. Zaqar only allows you to talk to it with a Keystone Token."},{"line_number":34,"context_line":"Heat for example needs to bind its Guest Agent to Zaqar to enable Software"},{"line_number":35,"context_line":"Deployments to work securely and with low overhead."}],"source_content_type":"text/x-rst","patch_set":17,"id":"da20952f_e1c808ab","line":32,"in_reply_to":"1a4dcd0f_2e701372","updated":"2015-09-01 21:03:26.000000000","message":"Done","commit_id":"accd4955858c3dee73d0cd0a746d8ff4a2e3beda"},{"author":{"_account_id":16277,"name":"Pradeep Kumar Singh","email":"ps4openstack@gmail.com","username":"pradeep_singh"},"change_message_id":"03d80afe8827053e96e92bfec861115d6b7214a3","unresolved":false,"context_lines":[{"line_number":61,"context_line":" * ConfigDrive data\u0027s cant be refreshed."},{"line_number":62,"context_line":" * Technologies change. The API should be abstract enough to allow the"},{"line_number":63,"context_line":"   Authentication mechanism to change without the user knowing."},{"line_number":64,"context_line":" * If the CA is ever compromized or the certificate algorithm is, there needs"},{"line_number":65,"context_line":"   to be a way to reissue all the certificates."},{"line_number":66,"context_line":" * Because so many different hypervisors exist, perhaps part of the"},{"line_number":67,"context_line":"   authentication mechanism should be left up to the driver. That way, the"}],"source_content_type":"text/x-rst","patch_set":17,"id":"1a4dcd0f_ae8d0333","line":64,"updated":"2015-08-04 06:43:35.000000000","message":"compromized -\u003e compromised","commit_id":"accd4955858c3dee73d0cd0a746d8ff4a2e3beda"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"0fb2011db38e83ec32702ee1b67529b7c51a7130","unresolved":false,"context_lines":[{"line_number":61,"context_line":" * ConfigDrive data\u0027s cant be refreshed."},{"line_number":62,"context_line":" * Technologies change. The API should be abstract enough to allow the"},{"line_number":63,"context_line":"   Authentication mechanism to change without the user knowing."},{"line_number":64,"context_line":" * If the CA is ever compromized or the certificate algorithm is, there needs"},{"line_number":65,"context_line":"   to be a way to reissue all the certificates."},{"line_number":66,"context_line":" * Because so many different hypervisors exist, perhaps part of the"},{"line_number":67,"context_line":"   authentication mechanism should be left up to the driver. That way, the"}],"source_content_type":"text/x-rst","patch_set":17,"id":"da20952f_213600b5","line":64,"in_reply_to":"1a4dcd0f_ae8d0333","updated":"2015-09-01 21:03:26.000000000","message":"Done","commit_id":"accd4955858c3dee73d0cd0a746d8ff4a2e3beda"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"907ba4259cb647df39ce0d1a85b551fc798f3cfe","unresolved":false,"context_lines":[{"line_number":124,"context_line":"Token to tell LBaaS to administratively disable itself from the Pool."},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"There are many many other use cases....."},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"Project Priority"},{"line_number":129,"context_line":"-----------------"},{"line_number":130,"context_line":""}],"source_content_type":"text/x-rst","patch_set":17,"id":"fa1b9901_d0fd996f","line":127,"updated":"2015-08-18 11:04:16.000000000","message":"I think this should cover the need for supporting config drive only clouds, and metadata service only clouds (and those with both).","commit_id":"accd4955858c3dee73d0cd0a746d8ff4a2e3beda"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"0fb2011db38e83ec32702ee1b67529b7c51a7130","unresolved":false,"context_lines":[{"line_number":124,"context_line":"Token to tell LBaaS to administratively disable itself from the Pool."},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"There are many many other use cases....."},{"line_number":127,"context_line":""},{"line_number":128,"context_line":"Project Priority"},{"line_number":129,"context_line":"-----------------"},{"line_number":130,"context_line":""}],"source_content_type":"text/x-rst","patch_set":17,"id":"da20952f_a17bf028","line":127,"in_reply_to":"fa1b9901_d0fd996f","updated":"2015-09-01 21:03:26.000000000","message":"I think that goes in the problem description section maybe? I hinted at it with the metadata server/config drive constraints, but your right, it isn\u0027t called out explicitly. I\u0027ll add it. Thanks.","commit_id":"accd4955858c3dee73d0cd0a746d8ff4a2e3beda"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"907ba4259cb647df39ce0d1a85b551fc798f3cfe","unresolved":false,"context_lines":[{"line_number":190,"context_line":" * Instance contacts Keystone using the Instance User Certificate it obtained"},{"line_number":191,"context_line":"   through Phase 1, getting back a token."},{"line_number":192,"context_line":""},{"line_number":193,"context_line":""},{"line_number":194,"context_line":"------------------------------------------"},{"line_number":195,"context_line":""},{"line_number":196,"context_line":"For the initial implementation, to ensure the maximum number of hypervisors are"}],"source_content_type":"text/x-rst","patch_set":17,"id":"fa1b9901_90dba1ed","line":193,"updated":"2015-08-18 11:04:16.000000000","message":"Note the above should really move into the alternatives section.","commit_id":"accd4955858c3dee73d0cd0a746d8ff4a2e3beda"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"0fb2011db38e83ec32702ee1b67529b7c51a7130","unresolved":false,"context_lines":[{"line_number":190,"context_line":" * Instance contacts Keystone using the Instance User Certificate it obtained"},{"line_number":191,"context_line":"   through Phase 1, getting back a token."},{"line_number":192,"context_line":""},{"line_number":193,"context_line":""},{"line_number":194,"context_line":"------------------------------------------"},{"line_number":195,"context_line":""},{"line_number":196,"context_line":"For the initial implementation, to ensure the maximum number of hypervisors are"}],"source_content_type":"text/x-rst","patch_set":17,"id":"da20952f_a1f7708b","line":193,"in_reply_to":"fa1b9901_90dba1ed","updated":"2015-09-01 21:03:26.000000000","message":"I was thinking the alternatives section was for alternatives to the whole spec, but I\u0027ll move these there since they are alternative plugins that use the spec and wont be initially implemented.","commit_id":"accd4955858c3dee73d0cd0a746d8ff4a2e3beda"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"907ba4259cb647df39ce0d1a85b551fc798f3cfe","unresolved":false,"context_lines":[{"line_number":211,"context_line":"   for Phase 1 Authentication."},{"line_number":212,"context_line":" * The App Catalog and Operators need to be able to easily install this, and"},{"line_number":213,"context_line":"   already need to install the additional Barbican Service. Too many additional"},{"line_number":214,"context_line":"   services are undesirable."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":"Diagram showing basic workflow. It shows:"},{"line_number":217,"context_line":" * User getting a user getting back the instance user id (To allow its use with"}],"source_content_type":"text/x-rst","patch_set":17,"id":"fa1b9901_4ed9bef2","line":214,"updated":"2015-08-18 11:04:16.000000000","message":"IMHO, these are not good enough reasons. Nova is too big, and we are trying to shrink the scope. This seems like a good thing to try and add outside of Nova, if at all possible.\n\nI would like to see us look at the alternative appoaches where there are much more minimal changes to Nova.\n\nHeat can detect when Nova instances are created and delete, for example. It could ensure to delete the keystone user when the instance is deleted.\n\nWe could just inject the tempURL via config drive, using the existing user_data API, and prototype this, without Nova being involved.","commit_id":"accd4955858c3dee73d0cd0a746d8ff4a2e3beda"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"0fb2011db38e83ec32702ee1b67529b7c51a7130","unresolved":false,"context_lines":[{"line_number":211,"context_line":"   for Phase 1 Authentication."},{"line_number":212,"context_line":" * The App Catalog and Operators need to be able to easily install this, and"},{"line_number":213,"context_line":"   already need to install the additional Barbican Service. Too many additional"},{"line_number":214,"context_line":"   services are undesirable."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":"Diagram showing basic workflow. It shows:"},{"line_number":217,"context_line":" * User getting a user getting back the instance user id (To allow its use with"}],"source_content_type":"text/x-rst","patch_set":17,"id":"da20952f_1ce80316","line":214,"in_reply_to":"fa1b9901_4ed9bef2","updated":"2015-09-01 21:03:26.000000000","message":"\"The code\u0027s done not when there is nothing more to add, but nothing more to remove.\" While I applaud your goal, I respectfully disagree that its best to pull it out. Nova\u0027s the closest to the VM so it has the most knowledge of whether the VM is what it is. Taking that part of the logic out of Nova makes things less secure and fragile in my opinion.\n\ntempURL\u0027s don\u0027t meet the constraints above talking about vm\u0027s being shutoff, paused or whatever for long enough periods that certificates expire. It also requires features of Barbican that that team doesn\u0027t seem willing to implement.","commit_id":"accd4955858c3dee73d0cd0a746d8ff4a2e3beda"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"907ba4259cb647df39ce0d1a85b551fc798f3cfe","unresolved":false,"context_lines":[{"line_number":279,"context_line":"The following changes will therefore be needed to be made to Nova:"},{"line_number":280,"context_line":" * The DB will be modified to add the following fields to an instance"},{"line_number":281,"context_line":"   * instance_user_id - The instance_user_id associated with an Instance. Its"},{"line_number":282,"context_line":"   nullable. It is null if an instance user has not been created yet."},{"line_number":283,"context_line":" * A new flag will be added to the Nova Server Create API to enable the"},{"line_number":284,"context_line":"   server\u0027s instance_user_id to be allocated at the time of server create and"},{"line_number":285,"context_line":"   returned synchronously from the create call. This will be used by"}],"source_content_type":"text/x-rst","patch_set":17,"id":"fa1b9901_eee532a8","line":282,"updated":"2015-08-18 11:04:16.000000000","message":"Can\u0027t this ID be generated somehow?","commit_id":"accd4955858c3dee73d0cd0a746d8ff4a2e3beda"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"0fb2011db38e83ec32702ee1b67529b7c51a7130","unresolved":false,"context_lines":[{"line_number":279,"context_line":"The following changes will therefore be needed to be made to Nova:"},{"line_number":280,"context_line":" * The DB will be modified to add the following fields to an instance"},{"line_number":281,"context_line":"   * instance_user_id - The instance_user_id associated with an Instance. Its"},{"line_number":282,"context_line":"   nullable. It is null if an instance user has not been created yet."},{"line_number":283,"context_line":" * A new flag will be added to the Nova Server Create API to enable the"},{"line_number":284,"context_line":"   server\u0027s instance_user_id to be allocated at the time of server create and"},{"line_number":285,"context_line":"   returned synchronously from the create call. This will be used by"}],"source_content_type":"text/x-rst","patch_set":17,"id":"da20952f_01809c45","line":282,"in_reply_to":"fa1b9901_eee532a8","updated":"2015-09-01 21:03:26.000000000","message":"The ID\u0027s are from Keystone. If you can get Keystone to move that responsibility in to Nova, then yes.","commit_id":"accd4955858c3dee73d0cd0a746d8ff4a2e3beda"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"907ba4259cb647df39ce0d1a85b551fc798f3cfe","unresolved":false,"context_lines":[{"line_number":467,"context_line":""},{"line_number":468,"context_line":"None currently. More specs will be added in Barbican, Keystone, Keystone"},{"line_number":469,"context_line":"Client, Heat, Barbican, Barbican Client, OpenStackClient and Nova Client to"},{"line_number":470,"context_line":"make this feature truly useful to the community."},{"line_number":471,"context_line":""},{"line_number":472,"context_line":""},{"line_number":473,"context_line":"Testing"}],"source_content_type":"text/x-rst","patch_set":17,"id":"fa1b9901_0ef0a68f","line":470,"updated":"2015-08-18 11:04:16.000000000","message":"I think we need to link to all the keystone and barbican specs here that this implementation seems to depend on.\n\nOr at least discuss the dependent APIs, I guess.","commit_id":"accd4955858c3dee73d0cd0a746d8ff4a2e3beda"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"0fb2011db38e83ec32702ee1b67529b7c51a7130","unresolved":false,"context_lines":[{"line_number":467,"context_line":""},{"line_number":468,"context_line":"None currently. More specs will be added in Barbican, Keystone, Keystone"},{"line_number":469,"context_line":"Client, Heat, Barbican, Barbican Client, OpenStackClient and Nova Client to"},{"line_number":470,"context_line":"make this feature truly useful to the community."},{"line_number":471,"context_line":""},{"line_number":472,"context_line":""},{"line_number":473,"context_line":"Testing"}],"source_content_type":"text/x-rst","patch_set":17,"id":"da20952f_818cac80","line":470,"in_reply_to":"fa1b9901_0ef0a68f","updated":"2015-09-01 21:03:26.000000000","message":"Yeah, sounds good. I\u0027ll try and find them all.","commit_id":"accd4955858c3dee73d0cd0a746d8ff4a2e3beda"}],"specs/liberty/approved/instance-users.rst":[{"author":{"_account_id":7385,"name":"Thomas Herve","email":"therve@redhat.com","username":"therve"},"change_message_id":"5174c5924c2a377f6af2533f03c801e3d1ae27b7","unresolved":false,"context_lines":[{"line_number":55,"context_line":"that don\u0027t need an instance user to not get one. After creation, the Keystone"},{"line_number":56,"context_line":"User UUID will be added to the Instances user visible metadata as well. The"},{"line_number":57,"context_line":"Password is never returned to the user, only kept internally. It is used to"},{"line_number":58,"context_line":"Hand out unscoped Keystone tokens to the user of the api."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a016987_e20dd43e","line":58,"updated":"2015-05-29 20:35:16.000000000","message":"From what I understand, the external service (for example heat) would need to fetch that user UUID at some point to be able to grant access to some resources using trusts. With the current proposal (AFAIU), it would mean polling the server metadata until it\u0027s populated, which sounds counter-productive.\n\nSo I feel the creation of that user should be either done when creating the server, or with an call on the public API.","commit_id":"9c1a688816bc2cc73fee7c92ea380f63b977075b"},{"author":{"_account_id":7385,"name":"Thomas Herve","email":"therve@redhat.com","username":"therve"},"change_message_id":"5174c5924c2a377f6af2533f03c801e3d1ae27b7","unresolved":false,"context_lines":[{"line_number":92,"context_line":"          \"version\": \"v3\","},{"line_number":93,"context_line":"          \"issued_at\": \"2015-05-28T00:37:54.270572Z\","},{"line_number":94,"context_line":"          \"auth_token\": \"xxxxxxx\","},{"line_number":95,"context_line":"          \"expires_at\": \"2015-05-29T00:37:54.270552Z\","},{"line_number":96,"context_line":"          \"user\": {"},{"line_number":97,"context_line":"              \"domain\": {"},{"line_number":98,"context_line":"                  \"id\": \"53d6bfad58074b4cbff99e8e12108081\","}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a016987_dd14fd44","line":95,"updated":"2015-05-29 20:35:16.000000000","message":"It\u0027s unclear how expiration is managed with this proposal. Presumably you get a different token every time the API is called? I think it\u0027s worth documenting in this spec.","commit_id":"9c1a688816bc2cc73fee7c92ea380f63b977075b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"1491141075b30f5123f9ebd20587eb46fcb5a532","unresolved":false,"context_lines":[{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Various OpenStack services that launch Instances with Guest Agents can use"},{"line_number":33,"context_line":"This to allow communication between controller nodes and the guest agent via"},{"line_number":34,"context_line":"Zaqar."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"Project Priority"},{"line_number":37,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_3ba8e8da","line":34,"updated":"2015-06-09 10:33:26.000000000","message":"I am not sure we need to include Zaqar here.\n\nMight be better to have a full example included though:\n\ne.g. FooBar agent talks to FooBar using the token and zaqar (or whatever).","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"c9a0c577eec9d59e9ef933efeb89042f2ff75d77","unresolved":false,"context_lines":[{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Various OpenStack services that launch Instances with Guest Agents can use"},{"line_number":33,"context_line":"This to allow communication between controller nodes and the guest agent via"},{"line_number":34,"context_line":"Zaqar."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"Project Priority"},{"line_number":37,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_06d701ee","line":34,"in_reply_to":"3afb71cf_3ba8e8da","updated":"2015-06-09 18:52:57.000000000","message":"Sure. Should the example workflow go into Use Cases or a different section, or even a new section?","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"1491141075b30f5123f9ebd20587eb46fcb5a532","unresolved":false,"context_lines":[{"line_number":36,"context_line":"Project Priority"},{"line_number":37,"context_line":"-----------------"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Unknown"},{"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":3,"id":"3afb71cf_fb95b086","line":39,"updated":"2015-06-09 10:33:26.000000000","message":"None","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"c9a0c577eec9d59e9ef933efeb89042f2ff75d77","unresolved":false,"context_lines":[{"line_number":36,"context_line":"Project Priority"},{"line_number":37,"context_line":"-----------------"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Unknown"},{"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":3,"id":"3afb71cf_e62d05ff","line":39,"in_reply_to":"3afb71cf_fb95b086","updated":"2015-06-09 18:52:57.000000000","message":"Done","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"1491141075b30f5123f9ebd20587eb46fcb5a532","unresolved":false,"context_lines":[{"line_number":65,"context_line":""},{"line_number":66,"context_line":"A more specific, Barbican only solution is is specified here:"},{"line_number":67,"context_line":"https://blueprints.launchpad.net/barbican/+spec/vm-integration"},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Data model impact"},{"line_number":70,"context_line":"-----------------"},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_3baea898","line":68,"updated":"2015-06-09 10:33:26.000000000","message":"What about using trusts so we don\u0027t have to ever store the password for each instance?","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"c9a0c577eec9d59e9ef933efeb89042f2ff75d77","unresolved":false,"context_lines":[{"line_number":65,"context_line":""},{"line_number":66,"context_line":"A more specific, Barbican only solution is is specified here:"},{"line_number":67,"context_line":"https://blueprints.launchpad.net/barbican/+spec/vm-integration"},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Data model impact"},{"line_number":70,"context_line":"-----------------"},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_067dc1b0","line":68,"in_reply_to":"3afb71cf_3baea898","updated":"2015-06-09 18:52:57.000000000","message":"I don\u0027t quite follow. Trusts allow you to delegate a user\u0027s access with another. The VM itself needs an account I think. The user can do a trust with that VM user, allowing the VM to become them, but Nova will still need a password to give to Keystone to get a token for the instance user to hand back to the VM.","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"1491141075b30f5123f9ebd20587eb46fcb5a532","unresolved":false,"context_lines":[{"line_number":78,"context_line":"This change adds one method to the metadata server at:"},{"line_number":79,"context_line":"http://169.254.169.254/openstack/latest/keystone.json"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"It supports only the GET method."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"It is expected to return a json document that looks something like:"},{"line_number":84,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_dbc2f433","line":81,"updated":"2015-06-09 10:33:26.000000000","message":"should this not be a POST request, given this generates something and modifies the server?\n\nPOST requests are not proxied into config drive, and this is something we would not want in config drive, so it fits quite nicely.","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"c9a0c577eec9d59e9ef933efeb89042f2ff75d77","unresolved":false,"context_lines":[{"line_number":78,"context_line":"This change adds one method to the metadata server at:"},{"line_number":79,"context_line":"http://169.254.169.254/openstack/latest/keystone.json"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"It supports only the GET method."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"It is expected to return a json document that looks something like:"},{"line_number":84,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_a18017f8","line":81,"in_reply_to":"3afb71cf_dbc2f433","updated":"2015-06-09 18:52:57.000000000","message":"I was debating that. I was thinking the following are in GET\u0027s favor:\n * The fact that it might lazily generate the user is an implementation detail the user shouldn\u0027t need to know happens\n * The user is simply trying to get a token. It would be confusing to ask them to make a PUT request to \"get\" a token.\n   That\u0027s counter intuitive to me.\n * It simplifies the scripts inside the vm to get a token. \n    \"curl http://169.254.169.254/openstack/latest/keystone.json\" rather then\n    \"curl -d \"\" http://169.254.169.254/openstack/latest/keystone.json\" or\n    \"curl -X POST http://169.254.169.254/openstack/latest/keystone.json\"\n\nAre those good enough reasons or do you think we still should change it to POST? They are realitively minor in the grand scheme of things so I\u0027m open to changing it to POST.\n\nI agree it shouldn\u0027t ever hit the config drive though. I\u0027m guessing there\u0027s got to be another way to get it to not land in config drive.","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"1491141075b30f5123f9ebd20587eb46fcb5a532","unresolved":false,"context_lines":[{"line_number":106,"context_line":"      },"},{"line_number":107,"context_line":"      \"auth_url\": \"http://10.254.254.1:35357/v3\","},{"line_number":108,"context_line":"      \"region\": \"RegionOne\""},{"line_number":109,"context_line":"  }"},{"line_number":110,"context_line":""},{"line_number":111,"context_line":"It is basically just the output of the keystoneclient v3"},{"line_number":112,"context_line":"Client.service_catalog.catalog, along with a keystone endpoint url,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_7bf54055","line":109,"updated":"2015-06-09 10:33:26.000000000","message":"it would be nice for the user API to also provide these instance specific tokens, although maybe thats a silly information leak...","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"c9a0c577eec9d59e9ef933efeb89042f2ff75d77","unresolved":false,"context_lines":[{"line_number":106,"context_line":"      },"},{"line_number":107,"context_line":"      \"auth_url\": \"http://10.254.254.1:35357/v3\","},{"line_number":108,"context_line":"      \"region\": \"RegionOne\""},{"line_number":109,"context_line":"  }"},{"line_number":110,"context_line":""},{"line_number":111,"context_line":"It is basically just the output of the keystoneclient v3"},{"line_number":112,"context_line":"Client.service_catalog.catalog, along with a keystone endpoint url,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_01eecbb3","line":109,"in_reply_to":"3afb71cf_7bf54055","updated":"2015-06-09 18:52:57.000000000","message":"Which regular users would be able to get per instance tokens? All tenant users? It may be useful for debugging, but the user could also just login to the vm and get one from there. Is that too much of an extra step?","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"1491141075b30f5123f9ebd20587eb46fcb5a532","unresolved":false,"context_lines":[{"line_number":111,"context_line":"It is basically just the output of the keystoneclient v3"},{"line_number":112,"context_line":"Client.service_catalog.catalog, along with a keystone endpoint url,"},{"line_number":113,"context_line":"and the Region the Instance is in. Each GET request will fetch a fresh"},{"line_number":114,"context_line":"unscoped token. In this way, an Instance get always get fresh tokens."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"This change also adds two paramaters to the metadata server at:"},{"line_number":117,"context_line":"/v2.1/servers type POST."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_fe123e56","line":114,"updated":"2015-06-09 10:33:26.000000000","message":"We need to talk about not adding this into configdrive, its the default, and we don\u0027t want that here, I suspect?","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"c9a0c577eec9d59e9ef933efeb89042f2ff75d77","unresolved":false,"context_lines":[{"line_number":111,"context_line":"It is basically just the output of the keystoneclient v3"},{"line_number":112,"context_line":"Client.service_catalog.catalog, along with a keystone endpoint url,"},{"line_number":113,"context_line":"and the Region the Instance is in. Each GET request will fetch a fresh"},{"line_number":114,"context_line":"unscoped token. In this way, an Instance get always get fresh tokens."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"This change also adds two paramaters to the metadata server at:"},{"line_number":117,"context_line":"/v2.1/servers type POST."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_01736b16","line":114,"in_reply_to":"3afb71cf_fe123e56","updated":"2015-06-09 18:52:57.000000000","message":"Done","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"1491141075b30f5123f9ebd20587eb46fcb5a532","unresolved":false,"context_lines":[{"line_number":121,"context_line":"* \"createInstanceUser\": \u003cBool\u003e (Default: \"False\")"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"The first, \"createShutdown\" causes the Instance to be created exactly as it is"},{"line_number":124,"context_line":"today but it is not started."},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"The second, pre-creates the Instance User as described in the metadata"},{"line_number":127,"context_line":"extention and returns the Keystone UUID for the Instance User in the response"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_bb44d8b6","line":124,"updated":"2015-06-09 10:33:26.000000000","message":"this seems like a totally unrelated spec, why is this here?","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"c9a0c577eec9d59e9ef933efeb89042f2ff75d77","unresolved":false,"context_lines":[{"line_number":121,"context_line":"* \"createInstanceUser\": \u003cBool\u003e (Default: \"False\")"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"The first, \"createShutdown\" causes the Instance to be created exactly as it is"},{"line_number":124,"context_line":"today but it is not started."},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"The second, pre-creates the Instance User as described in the metadata"},{"line_number":127,"context_line":"extention and returns the Keystone UUID for the Instance User in the response"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_21e427aa","line":124,"in_reply_to":"3afb71cf_bb44d8b6","updated":"2015-06-09 18:52:57.000000000","message":"The next 3 comments are all tied up in the same thing. I\u0027ll try and answer it in the 3rd.","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"1491141075b30f5123f9ebd20587eb46fcb5a532","unresolved":false,"context_lines":[{"line_number":125,"context_line":""},{"line_number":126,"context_line":"The second, pre-creates the Instance User as described in the metadata"},{"line_number":127,"context_line":"extention and returns the Keystone UUID for the Instance User in the response"},{"line_number":128,"context_line":"document under the \"server\" secion with key \"user_id\"."},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"These two will be used together in a Heat template to allow, for example,"},{"line_number":131,"context_line":"an Instance to be created stopped, the Instance User ID to be retrieved, the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_1b29ace6","line":128,"updated":"2015-06-09 10:33:26.000000000","message":"Not sure I understand why we need that?","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"1491141075b30f5123f9ebd20587eb46fcb5a532","unresolved":false,"context_lines":[{"line_number":130,"context_line":"These two will be used together in a Heat template to allow, for example,"},{"line_number":131,"context_line":"an Instance to be created stopped, the Instance User ID to be retrieved, the"},{"line_number":132,"context_line":"User ID to be added to Barbican Secret ACL\u0027s, and then the Instance booted."},{"line_number":133,"context_line":"The Instance will then be able to boot and use cloud-init to fetch secrets."},{"line_number":134,"context_line":""},{"line_number":135,"context_line":"Security impact"},{"line_number":136,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_bb72980f","line":133,"updated":"2015-06-09 10:33:26.000000000","message":"Can\u0027t the instance just wait for the barbican secret to be added?\n\nI do think this should be a separate spec...","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"c9a0c577eec9d59e9ef933efeb89042f2ff75d77","unresolved":false,"context_lines":[{"line_number":130,"context_line":"These two will be used together in a Heat template to allow, for example,"},{"line_number":131,"context_line":"an Instance to be created stopped, the Instance User ID to be retrieved, the"},{"line_number":132,"context_line":"User ID to be added to Barbican Secret ACL\u0027s, and then the Instance booted."},{"line_number":133,"context_line":"The Instance will then be able to boot and use cloud-init to fetch secrets."},{"line_number":134,"context_line":""},{"line_number":135,"context_line":"Security impact"},{"line_number":136,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_dc84185f","line":133,"in_reply_to":"3afb71cf_bb72980f","updated":"2015-06-09 18:52:57.000000000","message":"I was originally going to do this as a seperate spec, but someone recommended it be done all together since the whole workflow might require both pieces. I can split it up into a second spec if you think that will help though.\n\nIn the Barbican case, how do you know the difference between the user is not authorized yet to download the secret, and the user will never be able to download the secret because they are going after the wrong one?\n\nIf you changed the script to simply poll periodically till the acl was established, it might poll forever.\nIt places more load on the various servers.\nIt also makes it harder to write init scripts that have to talk to other services, since every service will need the same retry loops and deal with the 404/401 races.\n\nOn the plus side, it does make things a bit more parallel so an instance may provision faster.\n\nI\u0027m exploring an idea with the Heat folks that maybe if you could condition Heat Software Config\u0027s with wait conditions, you could make Heat deal with the race condition, so it wouldn\u0027t be necessary at all though. Let me get back to you on that one with what I find.","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"1391786b08a063da57a4b352ebcb47402eeccfcf","unresolved":false,"context_lines":[{"line_number":130,"context_line":"These two will be used together in a Heat template to allow, for example,"},{"line_number":131,"context_line":"an Instance to be created stopped, the Instance User ID to be retrieved, the"},{"line_number":132,"context_line":"User ID to be added to Barbican Secret ACL\u0027s, and then the Instance booted."},{"line_number":133,"context_line":"The Instance will then be able to boot and use cloud-init to fetch secrets."},{"line_number":134,"context_line":""},{"line_number":135,"context_line":"Security impact"},{"line_number":136,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_7260a4cf","line":133,"in_reply_to":"3afb71cf_dc84185f","updated":"2015-06-09 19:53:32.000000000","message":"I had a chat with some of the Heat developers. They say Heat SoftwareDeployments should allow handling the race condition entirely in the Heat engine. So I think I\u0027m going to drop out the create stopped functionality. The precreate instance flag would still be needed I think. Should I create a separate spec just for that one flag, or leave it here since its fairly intimately tied to the whole instance user concept?","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"1491141075b30f5123f9ebd20587eb46fcb5a532","unresolved":false,"context_lines":[{"line_number":147,"context_line":"storing it in those databases unencrypted and storing the password permanently"},{"line_number":148,"context_line":"in the Instance. With this change, all of those things are avoided. No one can"},{"line_number":149,"context_line":"login to the Instance and copy its credentials since it is never given direct"},{"line_number":150,"context_line":"access to them."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"Notifications impact"},{"line_number":153,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_7b6ae0ef","line":150,"updated":"2015-06-09 10:33:26.000000000","message":"I would love some keystone reviews on this spec.","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"c9a0c577eec9d59e9ef933efeb89042f2ff75d77","unresolved":false,"context_lines":[{"line_number":147,"context_line":"storing it in those databases unencrypted and storing the password permanently"},{"line_number":148,"context_line":"in the Instance. With this change, all of those things are avoided. No one can"},{"line_number":149,"context_line":"login to the Instance and copy its credentials since it is never given direct"},{"line_number":150,"context_line":"access to them."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"Notifications impact"},{"line_number":153,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_dcd2d85b","line":150,"in_reply_to":"3afb71cf_7b6ae0ef","updated":"2015-06-09 18:52:57.000000000","message":"+1.","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"1491141075b30f5123f9ebd20587eb46fcb5a532","unresolved":false,"context_lines":[{"line_number":190,"context_line":"throwing it out there to see who picks it up?"},{"line_number":191,"context_line":""},{"line_number":192,"context_line":"If more than one person is working on the implementation, please designate the"},{"line_number":193,"context_line":"primary author and contact."},{"line_number":194,"context_line":""},{"line_number":195,"context_line":"Primary assignee:"},{"line_number":196,"context_line":"  kevpn"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_3b158848","line":193,"updated":"2015-06-09 10:33:26.000000000","message":"These two bits of boiler plate from the template should be removed please","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"c9a0c577eec9d59e9ef933efeb89042f2ff75d77","unresolved":false,"context_lines":[{"line_number":190,"context_line":"throwing it out there to see who picks it up?"},{"line_number":191,"context_line":""},{"line_number":192,"context_line":"If more than one person is working on the implementation, please designate the"},{"line_number":193,"context_line":"primary author and contact."},{"line_number":194,"context_line":""},{"line_number":195,"context_line":"Primary assignee:"},{"line_number":196,"context_line":"  kevpn"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3afb71cf_410cc340","line":193,"in_reply_to":"3afb71cf_3b158848","updated":"2015-06-09 18:52:57.000000000","message":"Done","commit_id":"4fe445e3f95fc6b241a81af8269ee8caa006d25f"},{"author":{"_account_id":2218,"name":"Adam Young","email":"adam@younglogic.com","username":"ayoung"},"change_message_id":"bda6c9d9560928decad0cd3932fcf0c40d776406","unresolved":false,"context_lines":[{"line_number":55,"context_line":"that don\u0027t need an instance user to not get one. After creation, the Keystone"},{"line_number":56,"context_line":"User UUID will be added to the Instances user visible metadata as well. The"},{"line_number":57,"context_line":"Password is never returned to the user, only kept internally. It is used to"},{"line_number":58,"context_line":"Hand out unscoped Keystone tokens to the user of the api."},{"line_number":59,"context_line":"4. The server create api will be extended to support one new input."},{"line_number":60,"context_line":"createInstanceUser."},{"line_number":61,"context_line":"5. The delete server path will delete the instance user if created."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1af86dd1_132573aa","line":58,"updated":"2015-06-12 18:41:42.000000000","message":"You should not be using unscoped tokens.  The tokens should be  scoped to the domain that the new users are going into.","commit_id":"9500f7c32036b68374901c4572d82ad4e6cc71e9"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"acb95c166922a39b1369a5dc225d4380e8f7cb20","unresolved":false,"context_lines":[{"line_number":55,"context_line":"that don\u0027t need an instance user to not get one. After creation, the Keystone"},{"line_number":56,"context_line":"User UUID will be added to the Instances user visible metadata as well. The"},{"line_number":57,"context_line":"Password is never returned to the user, only kept internally. It is used to"},{"line_number":58,"context_line":"Hand out unscoped Keystone tokens to the user of the api."},{"line_number":59,"context_line":"4. The server create api will be extended to support one new input."},{"line_number":60,"context_line":"createInstanceUser."},{"line_number":61,"context_line":"5. The delete server path will delete the instance user if created."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1af86dd1_092544aa","line":58,"in_reply_to":"1af86dd1_132573aa","updated":"2015-06-12 19:38:22.000000000","message":"I was under the impression that a scoped token can\u0027t be converted to a different scoped token (or some day that won\u0027t be allowed). If you gave the instance the Unscoped token, it can contact Keystone and scope it appropriately for the tasks that it wants to do.\n\nIdeally long term Keystone will support Service scoped tokens, and the Instance would get, for example, a Barbican scoped token using the Unscoped token by talking to Keystone, and then give Barbican the scoped token. This will provide enhanced security since Barbican would not be able to give the user\u0027s token to any other service and have it work.\n\nWith this arrangement, when Keystone gains Service scoped tokens, Nova will not require any changes to start supporting that more secure workflow.","commit_id":"9500f7c32036b68374901c4572d82ad4e6cc71e9"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"15586b3779d4820191a77a303b2a8b85bccf8de2","unresolved":false,"context_lines":[{"line_number":30,"context_line":"storing secrets in the Nova and/or Heat database."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Various OpenStack services that launch Instances with Guest Agents can use"},{"line_number":33,"context_line":"This to allow communication between controller nodes and the guest agent via"},{"line_number":34,"context_line":"Zaqar."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"Project Priority"}],"source_content_type":"text/x-rst","patch_set":5,"id":"fa32b979_cc94fe38","line":33,"updated":"2015-06-15 16:41:17.000000000","message":"(nit) this","commit_id":"0c155d69fa6c6996ede65987b4870c634055aa35"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"09cac4e6036a583ef922a9c4e1a057a7b1cffc53","unresolved":false,"context_lines":[{"line_number":30,"context_line":"storing secrets in the Nova and/or Heat database."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Various OpenStack services that launch Instances with Guest Agents can use"},{"line_number":33,"context_line":"This to allow communication between controller nodes and the guest agent via"},{"line_number":34,"context_line":"Zaqar."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"Project Priority"}],"source_content_type":"text/x-rst","patch_set":5,"id":"fa32b979_e706bb1f","line":33,"in_reply_to":"fa32b979_cc94fe38","updated":"2015-06-15 16:59:18.000000000","message":"Done","commit_id":"0c155d69fa6c6996ede65987b4870c634055aa35"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"15586b3779d4820191a77a303b2a8b85bccf8de2","unresolved":false,"context_lines":[{"line_number":45,"context_line":"Nova, the Instance, and other OpenStack services."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"1. The nova database will be extended to support extra metadata of a Keystone"},{"line_number":48,"context_line":"password per Instance."},{"line_number":49,"context_line":"2. Config options will be added to nova.conf to specify a Keystone Domain to"},{"line_number":50,"context_line":"use and which Keystone endpoint url to hand to the Instance."},{"line_number":51,"context_line":"3. The metadata server api will be extended to provide a place to fetch a"}],"source_content_type":"text/x-rst","patch_set":5,"id":"fa32b979_4cc8ee55","line":48,"updated":"2015-06-15 16:41:17.000000000","message":"is this a clear text password?","commit_id":"0c155d69fa6c6996ede65987b4870c634055aa35"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"09cac4e6036a583ef922a9c4e1a057a7b1cffc53","unresolved":false,"context_lines":[{"line_number":45,"context_line":"Nova, the Instance, and other OpenStack services."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"1. The nova database will be extended to support extra metadata of a Keystone"},{"line_number":48,"context_line":"password per Instance."},{"line_number":49,"context_line":"2. Config options will be added to nova.conf to specify a Keystone Domain to"},{"line_number":50,"context_line":"use and which Keystone endpoint url to hand to the Instance."},{"line_number":51,"context_line":"3. The metadata server api will be extended to provide a place to fetch a"}],"source_content_type":"text/x-rst","patch_set":5,"id":"fa32b979_074cffc5","line":48,"in_reply_to":"fa32b979_4cc8ee55","updated":"2015-06-15 16:59:18.000000000","message":"I don\u0027t believe Keystone accepts hashed passwords currently? It can be stored in what ever form Keystone will allow.","commit_id":"0c155d69fa6c6996ede65987b4870c634055aa35"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"15586b3779d4820191a77a303b2a8b85bccf8de2","unresolved":false,"context_lines":[{"line_number":49,"context_line":"2. Config options will be added to nova.conf to specify a Keystone Domain to"},{"line_number":50,"context_line":"use and which Keystone endpoint url to hand to the Instance."},{"line_number":51,"context_line":"3. The metadata server api will be extended to provide a place to fetch a"},{"line_number":52,"context_line":"fresh keystone token. This api will create a new Keystone user in the"},{"line_number":53,"context_line":"specified Keystone Domain with a username of the Instance\u0027s UUID and a random"},{"line_number":54,"context_line":"password, if a password is not already stored in the db. This allows Instances"},{"line_number":55,"context_line":"that don\u0027t need an instance user to not get one. After creation, the Keystone"}],"source_content_type":"text/x-rst","patch_set":5,"id":"fa32b979_6c8372cd","line":52,"updated":"2015-06-15 16:41:17.000000000","message":"(nit) Keystone","commit_id":"0c155d69fa6c6996ede65987b4870c634055aa35"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"09cac4e6036a583ef922a9c4e1a057a7b1cffc53","unresolved":false,"context_lines":[{"line_number":49,"context_line":"2. Config options will be added to nova.conf to specify a Keystone Domain to"},{"line_number":50,"context_line":"use and which Keystone endpoint url to hand to the Instance."},{"line_number":51,"context_line":"3. The metadata server api will be extended to provide a place to fetch a"},{"line_number":52,"context_line":"fresh keystone token. This api will create a new Keystone user in the"},{"line_number":53,"context_line":"specified Keystone Domain with a username of the Instance\u0027s UUID and a random"},{"line_number":54,"context_line":"password, if a password is not already stored in the db. This allows Instances"},{"line_number":55,"context_line":"that don\u0027t need an instance user to not get one. After creation, the Keystone"}],"source_content_type":"text/x-rst","patch_set":5,"id":"fa32b979_67e86b7d","line":52,"in_reply_to":"fa32b979_6c8372cd","updated":"2015-06-15 16:59:18.000000000","message":"Done","commit_id":"0c155d69fa6c6996ede65987b4870c634055aa35"},{"author":{"_account_id":7725,"name":"David Stanek","email":"dstanek@dstanek.com","username":"dstanek"},"change_message_id":"15586b3779d4820191a77a303b2a8b85bccf8de2","unresolved":false,"context_lines":[{"line_number":59,"context_line":"4. The server create api will be extended to support one new input."},{"line_number":60,"context_line":"createInstanceUser."},{"line_number":61,"context_line":"5. The delete server path will delete the instance user if created."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Alternatives"},{"line_number":64,"context_line":"------------"},{"line_number":65,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"fa32b979_0c9186f0","line":62,"updated":"2015-06-15 16:41:17.000000000","message":"Is this password only used with the instance is initially being setup or throughout it\u0027s life? Since the record lives forever would there ever be a need to change/remove password due to a security issue?","commit_id":"0c155d69fa6c6996ede65987b4870c634055aa35"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"09cac4e6036a583ef922a9c4e1a057a7b1cffc53","unresolved":false,"context_lines":[{"line_number":59,"context_line":"4. The server create api will be extended to support one new input."},{"line_number":60,"context_line":"createInstanceUser."},{"line_number":61,"context_line":"5. The delete server path will delete the instance user if created."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Alternatives"},{"line_number":64,"context_line":"------------"},{"line_number":65,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"fa32b979_e72f9b9f","line":62,"in_reply_to":"fa32b979_0c9186f0","updated":"2015-06-15 16:59:18.000000000","message":"Its used whenever the Instance wants to fetch a fresh Keystone Token for itself.\n\nSince the password is never exposed to the Instance, it should be simple to write a script that generates a new random password for every instance user and update the password in Keystone should this ever become a problem.","commit_id":"0c155d69fa6c6996ede65987b4870c634055aa35"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"c3685a7f2ecdd2dd9c42db601be550968b0e680d","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"https://blueprints.launchpad.net/nova/+spec/example"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Instances have need to some times interact with the cloud that it is running"},{"line_number":14,"context_line":"under. This can include getting keys from Barbican, putting messages in a"},{"line_number":15,"context_line":"Zaqar queue, getting a file from Swift, etc. All of these services require"},{"line_number":16,"context_line":"a fresh Keystone token."}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_7d75a961","line":13,"updated":"2015-06-18 22:08:40.000000000","message":"Wow, if each instance require a unique user account in Keystone that would probably be unmanageable. Also, Keystone user accounts are supposed to be highly static. I would imagine instances are fairly dynamic (i.e. create/destroy very frequently), no?","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"301b90582c3e2495aac53f62528b16bfd9b9e09c","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"https://blueprints.launchpad.net/nova/+spec/example"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Instances have need to some times interact with the cloud that it is running"},{"line_number":14,"context_line":"under. This can include getting keys from Barbican, putting messages in a"},{"line_number":15,"context_line":"Zaqar queue, getting a file from Swift, etc. All of these services require"},{"line_number":16,"context_line":"a fresh Keystone token."}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_0332faa6","line":13,"in_reply_to":"fa32b979_7d75a961","updated":"2015-06-18 23:23:49.000000000","message":"Only instances that interact with other OpenStack services.\n\nStill, even in the 100\u0027s of thousands of instances range, thats not a huge number of users.\n\nWith is spec, Keystone doesn\u0027t actually have the users but trusts Nova\u0027s CA (managed by Barbican). So its fairly light weight.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"c3685a7f2ecdd2dd9c42db601be550968b0e680d","unresolved":false,"context_lines":[{"line_number":13,"context_line":"Instances have need to some times interact with the cloud that it is running"},{"line_number":14,"context_line":"under. This can include getting keys from Barbican, putting messages in a"},{"line_number":15,"context_line":"Zaqar queue, getting a file from Swift, etc. All of these services require"},{"line_number":16,"context_line":"a fresh Keystone token."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Problem description"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_3d02c1b4","line":16,"updated":"2015-06-18 22:08:40.000000000","message":"Zaqar require Keystone token or Barbican key (i.e. signed message)?","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"301b90582c3e2495aac53f62528b16bfd9b9e09c","unresolved":false,"context_lines":[{"line_number":13,"context_line":"Instances have need to some times interact with the cloud that it is running"},{"line_number":14,"context_line":"under. This can include getting keys from Barbican, putting messages in a"},{"line_number":15,"context_line":"Zaqar queue, getting a file from Swift, etc. All of these services require"},{"line_number":16,"context_line":"a fresh Keystone token."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Problem description"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_43c24254","line":16,"in_reply_to":"fa32b979_3d02c1b4","updated":"2015-06-18 23:23:49.000000000","message":"Keystone token. Any guest agent that runs on the Instance can use this mechanism to get a token to allow the guest agent to talk to an OpenStack Service it needs to talk to. So, for example, the Trove instance can use it to get a token to talk to a Zaqar queue on which Trove\u0027s controller is sitting on the other end. Or it could use the same token to talk directly to the Trove API if that was needed/supported by Trove.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"c3685a7f2ecdd2dd9c42db601be550968b0e680d","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Developers will use this when writing heat templates to allow Instances to"},{"line_number":29,"context_line":"securely fetch secrets they need to properly operate from Barbican without"},{"line_number":30,"context_line":"storing secrets in the Nova and/or Heat database."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Various OpenStack services that launch Instances with Guest Agents can use"},{"line_number":33,"context_line":"this to allow communication between controller nodes and the guest agent via"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_9ddbcd7b","line":30,"updated":"2015-06-18 22:08:40.000000000","message":"A sequence diagram here would be very helpful.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"301b90582c3e2495aac53f62528b16bfd9b9e09c","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Developers will use this when writing heat templates to allow Instances to"},{"line_number":29,"context_line":"securely fetch secrets they need to properly operate from Barbican without"},{"line_number":30,"context_line":"storing secrets in the Nova and/or Heat database."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Various OpenStack services that launch Instances with Guest Agents can use"},{"line_number":33,"context_line":"this to allow communication between controller nodes and the guest agent via"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_8324ca0c","line":30,"in_reply_to":"fa32b979_9ddbcd7b","updated":"2015-06-18 23:23:49.000000000","message":"Sure, but I can\u0027t really get it to fit in a \u003c 80 character limit spec. What format should be used?\n\nI could try and break it up between the Nova/launch side, and the Instance side, but I think we\u0027d loose some of the picture.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"c3685a7f2ecdd2dd9c42db601be550968b0e680d","unresolved":false,"context_lines":[{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Various OpenStack services that launch Instances with Guest Agents can use"},{"line_number":33,"context_line":"this to allow communication between controller nodes and the guest agent via"},{"line_number":34,"context_line":"Zaqar."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"Project Priority"},{"line_number":37,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_3de64144","line":34,"updated":"2015-06-18 22:08:40.000000000","message":"Same, a sequence diagram please.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"c3685a7f2ecdd2dd9c42db601be550968b0e680d","unresolved":false,"context_lines":[{"line_number":45,"context_line":"Nova, the Instance, and other OpenStack services."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"1. The Nova database will be extended to support the extra metadata of a x509"},{"line_number":48,"context_line":"user certificate."},{"line_number":49,"context_line":"2. Config options will be added to nova.conf to specify which Barbican CA to"},{"line_number":50,"context_line":"use and which Keystone endpoint url to hand to the Instance."},{"line_number":51,"context_line":"3. A function will be added that will contact Barbican and create a new"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_a876c2d4","line":48,"updated":"2015-06-18 22:08:40.000000000","message":"I presume we have a unique x.509 cert and private key per instance? So we can either provision the cert at instance creation (i.e via ephemeral CA) or directly request the cert when we boot up the instance the first time.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"301b90582c3e2495aac53f62528b16bfd9b9e09c","unresolved":false,"context_lines":[{"line_number":45,"context_line":"Nova, the Instance, and other OpenStack services."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"1. The Nova database will be extended to support the extra metadata of a x509"},{"line_number":48,"context_line":"user certificate."},{"line_number":49,"context_line":"2. Config options will be added to nova.conf to specify which Barbican CA to"},{"line_number":50,"context_line":"use and which Keystone endpoint url to hand to the Instance."},{"line_number":51,"context_line":"3. A function will be added that will contact Barbican and create a new"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_83d92af5","line":48,"in_reply_to":"fa32b979_a876c2d4","updated":"2015-06-18 23:23:49.000000000","message":"True for instance creation time. We delay even farther to the point of first token request. That way if a Instance never tries to request a token, a user is never created.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":7973,"name":"Douglas Mendizábal","email":"dmendiza@redhat.com","username":"dougmendizabal"},"change_message_id":"bae9699c22182e7629acfa4c153673d99a5e06c6","unresolved":false,"context_lines":[{"line_number":47,"context_line":"1. The Nova database will be extended to support the extra metadata of a x509"},{"line_number":48,"context_line":"user certificate."},{"line_number":49,"context_line":"2. Config options will be added to nova.conf to specify which Barbican CA to"},{"line_number":50,"context_line":"use and which Keystone endpoint url to hand to the Instance."},{"line_number":51,"context_line":"3. A function will be added that will contact Barbican and create a new"},{"line_number":52,"context_line":"certificate with the Instance UUID as an attribute. The returned certificate"},{"line_number":53,"context_line":"is stored in the Nova database associated with the Instance UUID. Keystone is"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_a90c9aec","line":50,"updated":"2015-06-17 16:42:15.000000000","message":"I\u0027m interested in learning more about the interaction between Keystone and Nova.  How does Nova use the x.509 certificate to provision the instance user?  How does it use the cert to authenticate and retrieve a token?  Will Keystone hold the root cert for verification or does Barbican need to provide the root cert to Keystone?\n\n/me steps away to go dig through Keystone\u0027s IRC logs...","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"301b90582c3e2495aac53f62528b16bfd9b9e09c","unresolved":false,"context_lines":[{"line_number":47,"context_line":"1. The Nova database will be extended to support the extra metadata of a x509"},{"line_number":48,"context_line":"user certificate."},{"line_number":49,"context_line":"2. Config options will be added to nova.conf to specify which Barbican CA to"},{"line_number":50,"context_line":"use and which Keystone endpoint url to hand to the Instance."},{"line_number":51,"context_line":"3. A function will be added that will contact Barbican and create a new"},{"line_number":52,"context_line":"certificate with the Instance UUID as an attribute. The returned certificate"},{"line_number":53,"context_line":"is stored in the Nova database associated with the Instance UUID. Keystone is"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_c3a09244","line":50,"in_reply_to":"fa32b979_37a98024","updated":"2015-06-18 23:23:49.000000000","message":"Barbican already has what it needs. Nova talks to Barbican using its regular admin token to get certs signed by the CA.\n\nWhen the Instance talks to Barbican, its via a Keystone Token as well. So Barbican is never aware x509 certs were used as part of the authentication process.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"c3685a7f2ecdd2dd9c42db601be550968b0e680d","unresolved":false,"context_lines":[{"line_number":47,"context_line":"1. The Nova database will be extended to support the extra metadata of a x509"},{"line_number":48,"context_line":"user certificate."},{"line_number":49,"context_line":"2. Config options will be added to nova.conf to specify which Barbican CA to"},{"line_number":50,"context_line":"use and which Keystone endpoint url to hand to the Instance."},{"line_number":51,"context_line":"3. A function will be added that will contact Barbican and create a new"},{"line_number":52,"context_line":"certificate with the Instance UUID as an attribute. The returned certificate"},{"line_number":53,"context_line":"is stored in the Nova database associated with the Instance UUID. Keystone is"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_37a98024","line":50,"in_reply_to":"fa32b979_5fc6e09a","updated":"2015-06-18 22:08:40.000000000","message":"That\u0027s for tokenless authz. Barbican will also need to support this feature independently.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"0e54f114e9c95675a8cc1904ae6d567cb8169d34","unresolved":false,"context_lines":[{"line_number":47,"context_line":"1. The Nova database will be extended to support the extra metadata of a x509"},{"line_number":48,"context_line":"user certificate."},{"line_number":49,"context_line":"2. Config options will be added to nova.conf to specify which Barbican CA to"},{"line_number":50,"context_line":"use and which Keystone endpoint url to hand to the Instance."},{"line_number":51,"context_line":"3. A function will be added that will contact Barbican and create a new"},{"line_number":52,"context_line":"certificate with the Instance UUID as an attribute. The returned certificate"},{"line_number":53,"context_line":"is stored in the Nova database associated with the Instance UUID. Keystone is"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_5fc6e09a","line":50,"in_reply_to":"fa32b979_a90c9aec","updated":"2015-06-17 17:20:10.000000000","message":"There is a Keystone spec schedualed for Liberty that can do this here:\nhttp://specs.openstack.org/openstack/keystone-specs/specs/liberty/keystone-tokenless-authz-with-x509-ssl-client-cert.html\n\nKeystone will need to have the Barbican\u0027s CA cert loaded into it and a trust relationship created.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":1916,"name":"Guang Yee","email":"gyee@suse.com","username":"guang-yee"},"change_message_id":"c3685a7f2ecdd2dd9c42db601be550968b0e680d","unresolved":false,"context_lines":[{"line_number":49,"context_line":"2. Config options will be added to nova.conf to specify which Barbican CA to"},{"line_number":50,"context_line":"use and which Keystone endpoint url to hand to the Instance."},{"line_number":51,"context_line":"3. A function will be added that will contact Barbican and create a new"},{"line_number":52,"context_line":"certificate with the Instance UUID as an attribute. The returned certificate"},{"line_number":53,"context_line":"is stored in the Nova database associated with the Instance UUID. Keystone is"},{"line_number":54,"context_line":"then contacted with the certificate and a Keystone User ID is returned. The"},{"line_number":55,"context_line":"Keystone User ID is stored in the Instance\u0027s metadata for retrieval by the end"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_1dc01d4f","line":52,"updated":"2015-06-18 22:08:40.000000000","message":"What\u0027s instance UUID? That the instance ID in Nova?","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"301b90582c3e2495aac53f62528b16bfd9b9e09c","unresolved":false,"context_lines":[{"line_number":49,"context_line":"2. Config options will be added to nova.conf to specify which Barbican CA to"},{"line_number":50,"context_line":"use and which Keystone endpoint url to hand to the Instance."},{"line_number":51,"context_line":"3. A function will be added that will contact Barbican and create a new"},{"line_number":52,"context_line":"certificate with the Instance UUID as an attribute. The returned certificate"},{"line_number":53,"context_line":"is stored in the Nova database associated with the Instance UUID. Keystone is"},{"line_number":54,"context_line":"then contacted with the certificate and a Keystone User ID is returned. The"},{"line_number":55,"context_line":"Keystone User ID is stored in the Instance\u0027s metadata for retrieval by the end"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_438d62d1","line":52,"in_reply_to":"fa32b979_1dc01d4f","updated":"2015-06-18 23:23:49.000000000","message":"Correct. I\u0027ll add that clarification to the next rev.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":7973,"name":"Douglas Mendizábal","email":"dmendiza@redhat.com","username":"dougmendizabal"},"change_message_id":"bae9699c22182e7629acfa4c153673d99a5e06c6","unresolved":false,"context_lines":[{"line_number":53,"context_line":"is stored in the Nova database associated with the Instance UUID. Keystone is"},{"line_number":54,"context_line":"then contacted with the certificate and a Keystone User ID is returned. The"},{"line_number":55,"context_line":"Keystone User ID is stored in the Instance\u0027s metadata for retrieval by the end"},{"line_number":56,"context_line":"user."},{"line_number":57,"context_line":"4. The metadata server api will be extended to provide a place to fetch a"},{"line_number":58,"context_line":"fresh Keystone token. If the cert does not exist in the database, it will call"},{"line_number":59,"context_line":"the function specified in #3 first. This allows Instances that don\u0027t need an"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_e9bb82e3","line":56,"updated":"2015-06-17 16:42:15.000000000","message":"It\u0027s not clear who is holding the private key for the certificate.  Does the private key remain in Barbican?  If so Nova would need to fetch the private key to be able to issue requests to Keystone.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"0e54f114e9c95675a8cc1904ae6d567cb8169d34","unresolved":false,"context_lines":[{"line_number":53,"context_line":"is stored in the Nova database associated with the Instance UUID. Keystone is"},{"line_number":54,"context_line":"then contacted with the certificate and a Keystone User ID is returned. The"},{"line_number":55,"context_line":"Keystone User ID is stored in the Instance\u0027s metadata for retrieval by the end"},{"line_number":56,"context_line":"user."},{"line_number":57,"context_line":"4. The metadata server api will be extended to provide a place to fetch a"},{"line_number":58,"context_line":"fresh Keystone token. If the cert does not exist in the database, it will call"},{"line_number":59,"context_line":"the function specified in #3 first. This allows Instances that don\u0027t need an"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_44a85377","line":56,"in_reply_to":"fa32b979_e9bb82e3","updated":"2015-06-17 17:20:10.000000000","message":"I think Nova generates it, sticks it in the Nova db, and passes the csr to Barbican for signing. That way, whenever the Instance goes to get a fresh token from the nova metadata server, it can talk directly to Keystone to get the token without needing to contact Barbican.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":7973,"name":"Douglas Mendizábal","email":"dmendiza@redhat.com","username":"dougmendizabal"},"change_message_id":"bae9699c22182e7629acfa4c153673d99a5e06c6","unresolved":false,"context_lines":[{"line_number":69,"context_line":"------------"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"A more specific, Barbican only solution is is specified here:"},{"line_number":72,"context_line":"https://blueprints.launchpad.net/barbican/+spec/vm-integration"},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"Data model impact"},{"line_number":75,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_6e5d3846","line":72,"updated":"2015-06-17 16:42:15.000000000","message":"The Barbican team would prefer to see this spec implemented instead of the linked Barbican only spec.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"0e54f114e9c95675a8cc1904ae6d567cb8169d34","unresolved":false,"context_lines":[{"line_number":69,"context_line":"------------"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"A more specific, Barbican only solution is is specified here:"},{"line_number":72,"context_line":"https://blueprints.launchpad.net/barbican/+spec/vm-integration"},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"Data model impact"},{"line_number":75,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":7,"id":"fa32b979_ffbc94bc","line":72,"in_reply_to":"fa32b979_6e5d3846","updated":"2015-06-17 17:20:10.000000000","message":"K. I\u0027ll stick this note in the spec here in the next revision.","commit_id":"aec3c9b4cdeceb2c9843b43419d2b1fa38814be5"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"ef95e43250fb5a43dfbc5287847d220852a1d37e","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Instance Users for Cloud Interaction"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"https://blueprints.launchpad.net/nova/+spec/example"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Instances have need to some times interact with the cloud that it is running"},{"line_number":14,"context_line":"under. This can include getting keys from Barbican, putting messages in a"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_48c43a3f","line":11,"updated":"2015-06-22 18:55:14.000000000","message":"Please set the above to your blueprint on Launchpad..","commit_id":"f46865dedb99eafc22db45b1a27e2a65e946b0c7"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"15f2e1924dec911841328d02f2eab415b40c20dc","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Instance Users for Cloud Interaction"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"https://blueprints.launchpad.net/nova/+spec/example"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Instances have need to some times interact with the cloud that it is running"},{"line_number":14,"context_line":"under. This can include getting keys from Barbican, putting messages in a"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_1e7c2cea","line":11,"in_reply_to":"fa32b979_48c43a3f","updated":"2015-06-22 20:33:43.000000000","message":"Done","commit_id":"f46865dedb99eafc22db45b1a27e2a65e946b0c7"},{"author":{"_account_id":7973,"name":"Douglas Mendizábal","email":"dmendiza@redhat.com","username":"dougmendizabal"},"change_message_id":"557ca3760f1c2c5b61a0c11c36d5a4f89f7b5628","unresolved":false,"context_lines":[{"line_number":53,"context_line":"is stored in the Nova database associated with the Nova Instance UUID. Keystone"},{"line_number":54,"context_line":"is then contacted with the certificate and a Keystone User ID is returned. The"},{"line_number":55,"context_line":"Keystone User ID is stored in the Instance\u0027s metadata for retrieval by the end"},{"line_number":56,"context_line":"user."},{"line_number":57,"context_line":"4. The metadata server api will be extended to provide a place to fetch a"},{"line_number":58,"context_line":"fresh Keystone token. If the cert does not exist in the database, it will call"},{"line_number":59,"context_line":"the function specified in #3 first. This allows Instances that don\u0027t need an"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_d03ef328","line":56,"updated":"2015-06-19 18:12:55.000000000","message":"I should point out that provisioning a certificate in Barbican has the side effect of also storing it.  You don\u0027t necessarily need to store the cert or key in nova, since the cert will already be stored in Barbican, you could just store the certificate container reference.  And if you ask Barbican to also generate the key, the reference to it will also be in the container.","commit_id":"f46865dedb99eafc22db45b1a27e2a65e946b0c7"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"8aae085711cd617619d5f3cc0772a2e58552a829","unresolved":false,"context_lines":[{"line_number":53,"context_line":"is stored in the Nova database associated with the Nova Instance UUID. Keystone"},{"line_number":54,"context_line":"is then contacted with the certificate and a Keystone User ID is returned. The"},{"line_number":55,"context_line":"Keystone User ID is stored in the Instance\u0027s metadata for retrieval by the end"},{"line_number":56,"context_line":"user."},{"line_number":57,"context_line":"4. The metadata server api will be extended to provide a place to fetch a"},{"line_number":58,"context_line":"fresh Keystone token. If the cert does not exist in the database, it will call"},{"line_number":59,"context_line":"the function specified in #3 first. This allows Instances that don\u0027t need an"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_cbc9645c","line":56,"in_reply_to":"fa32b979_d03ef328","updated":"2015-06-19 18:37:43.000000000","message":"I was thinking we probably should store it in Nova\u0027s db since the metadata server already needs to contact it. In the case where the user cert is already provisioned, the workflow to get a token is just Instance -\u003e nova md -\u003e kestyone rather then Instance -\u003e nova md (-\u003e barbican, then -\u003e keystone). This means less load for Instances that are refreshing tokens. Though I can see some other benifits in just storing it in Barbican. I guess we could drop out the db requirement and if its too much load add it back as a cache later. What do you think?","commit_id":"f46865dedb99eafc22db45b1a27e2a65e946b0c7"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"0be0ff77ed466c573dc9f8db7f2c9d03cd4cd86f","unresolved":false,"context_lines":[{"line_number":58,"context_line":"fresh Keystone token. If the cert does not exist in the database, it will call"},{"line_number":59,"context_line":"the function specified in #3 first. This allows Instances that don\u0027t need an"},{"line_number":60,"context_line":"instance user to not get one. The api call authenticates with Keystone using"},{"line_number":61,"context_line":"the certificate in the database and returns a Token to the Instance."},{"line_number":62,"context_line":"5. The server create api will be extended to support one new input."},{"line_number":63,"context_line":"createInstanceUser that synchronously calls function #3 and returns the"},{"line_number":64,"context_line":"Instance User ID as part of the response. This allows orchestration engines"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_6f010806","line":61,"updated":"2015-06-22 18:03:30.000000000","message":"So, I don\u0027t understand why the token is being passed back to the instance. This doesn\u0027t seem correct. The instance should get the cert and talk to keystone directly I think? The proxy getting a token from keystone might be a little weird. \n\nI\u0027m not giving a -1 for this, but it seems like it becomes he metadata services job to maintain the token then. Which would appear to be added and superfluous overhead. \n\nBe careful about caching (etc) that might occur in metadata service. How will this work in the case of no metadata service (aka config drive)? If you passed the cert back to the instance, the instance can do the heavy lifting even in alternative deployments without the metadata service.","commit_id":"f46865dedb99eafc22db45b1a27e2a65e946b0c7"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"15f2e1924dec911841328d02f2eab415b40c20dc","unresolved":false,"context_lines":[{"line_number":58,"context_line":"fresh Keystone token. If the cert does not exist in the database, it will call"},{"line_number":59,"context_line":"the function specified in #3 first. This allows Instances that don\u0027t need an"},{"line_number":60,"context_line":"instance user to not get one. The api call authenticates with Keystone using"},{"line_number":61,"context_line":"the certificate in the database and returns a Token to the Instance."},{"line_number":62,"context_line":"5. The server create api will be extended to support one new input."},{"line_number":63,"context_line":"createInstanceUser that synchronously calls function #3 and returns the"},{"line_number":64,"context_line":"Instance User ID as part of the response. This allows orchestration engines"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_999e1653","line":61,"in_reply_to":"fa32b979_6f010806","updated":"2015-06-22 20:33:43.000000000","message":"The concern is that if vm\u0027s had access to the cert itself, they could not be easily refreshed or worse, someone could login to the vm, copy the cert to another machine, and use the vm\u0027s credentials to gain vm tokens without needing continued access to the vm.\n\nFor example, consider the project admin that leaves the project. When the certs are passed to the vm\u0027s, you can\u0027t know that the project admin who left still has access to the keystone cert. So you must delete the vm\u0027s to invalidate the certs. Or, you must have machinery inside the vm to be able to refresh updated certs. With just passing the token, only the VM can request a token via the instance-\u003emd authentication, proving that it came from the VM at the time, and only lasts as long as the token expiration. If an admin copied the token to another machine, it would only be valid until it times out. The admin has no other way to refresh them but physical access to the vm. \n\nCaching will be disabled for the one endpoint. That shouldn\u0027t be a problem. The admin has no other way to refresh them but physical access to the vm. This should be more secure.\n\nConfig drive isn\u0027t supported due to needing a server to hand out fresh tokens. I was hoping to deal with config drive at some other point with some other solution. I really prefer the instances not having access to certs, but for the config drive case, at the moment, I can\u0027t think of a much better way of handling it so maybe in that case, the instance cert is just handed through config drive like you suggest and the instance is required to have some kind of cert refresh mechanism built in to it?\n\nI\u0027ll revise the spec to include the why only tokens answer if you think its reasonable.","commit_id":"f46865dedb99eafc22db45b1a27e2a65e946b0c7"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"5021c99220d228de8864a9ad9fdb861e355193ce","unresolved":false,"context_lines":[{"line_number":58,"context_line":"fresh Keystone token. If the cert does not exist in the database, it will call"},{"line_number":59,"context_line":"the function specified in #3 first. This allows Instances that don\u0027t need an"},{"line_number":60,"context_line":"instance user to not get one. The api call authenticates with Keystone using"},{"line_number":61,"context_line":"the certificate in the database and returns a Token to the Instance."},{"line_number":62,"context_line":"5. The server create api will be extended to support one new input."},{"line_number":63,"context_line":"createInstanceUser that synchronously calls function #3 and returns the"},{"line_number":64,"context_line":"Instance User ID as part of the response. This allows orchestration engines"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_f934ffde","line":61,"in_reply_to":"fa32b979_999e1653","updated":"2015-06-22 21:01:32.000000000","message":"So, lets be clear, you\u0027re not really preventing the Admin from having access to the system(s). If a project admin is leaving, the access to a VM (etc) would still need to be deleted. There is nothing stopping the admin from having a back door VM instantated and just asking the metadata service for a token and doing the same things you\u0027re trying to prevent.\n\nThe reality is if an admin leaves, you need to invalidate the certs for the project and/or refresh them. the mechanism(s) inside the VM need to know that they need to check to see if the cert was updated / invalidated so that they can get the updated cert.\n\nSo the workflow (in case if the project admin leaves) looks like this:\n\n  * Admin leaves\n  * All instances are evaluated / respun up with a clean image to ensure no backdoors\n  * All certs for project are invalidated / updated\n  * Instances in project find that the certs are invalid/updated and refresh\n  * Instances refresh Certs\n  * Instances use new certs for getting tokens.\n\nThe reality is this is cloud software. In all likelyhood you should be able to teardown and spin up a replacement node that you know the admin does not have access to. Ensuring access is revoked by having the metadata service issue tokens is just shuffling the same concern and hiding it a little. I feel better having things be a little more transparent and avoid having Nova\u0027s metadata service do tons of extra heavy lifting.\n\nThis also has the added benefit that it is interoperable (in theory) with non-metadata running openstack deployments that choose to build these certs on instance creation and embed the data in config drive-like constructs.","commit_id":"f46865dedb99eafc22db45b1a27e2a65e946b0c7"},{"author":{"_account_id":7973,"name":"Douglas Mendizábal","email":"dmendiza@redhat.com","username":"dougmendizabal"},"change_message_id":"557ca3760f1c2c5b61a0c11c36d5a4f89f7b5628","unresolved":false,"context_lines":[{"line_number":63,"context_line":"createInstanceUser that synchronously calls function #3 and returns the"},{"line_number":64,"context_line":"Instance User ID as part of the response. This allows orchestration engines"},{"line_number":65,"context_line":"like Heat to perform extra operations on the Instance User such as setting up"},{"line_number":66,"context_line":"Barbican ACL\u0027s or create Keystone Trusts."},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"Alternatives"},{"line_number":69,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_6bd4d846","line":66,"updated":"2015-06-19 18:12:55.000000000","message":"Would it be useful to list the token requirements here?  For the Barbican ACLs to work, the token has to have a User-ID to match in the ACL.\n\nI think having the Project-ID and Role(s) may be useful as well, but not necessary for the ACL use case.","commit_id":"f46865dedb99eafc22db45b1a27e2a65e946b0c7"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"8aae085711cd617619d5f3cc0772a2e58552a829","unresolved":false,"context_lines":[{"line_number":63,"context_line":"createInstanceUser that synchronously calls function #3 and returns the"},{"line_number":64,"context_line":"Instance User ID as part of the response. This allows orchestration engines"},{"line_number":65,"context_line":"like Heat to perform extra operations on the Instance User such as setting up"},{"line_number":66,"context_line":"Barbican ACL\u0027s or create Keystone Trusts."},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"Alternatives"},{"line_number":69,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":8,"id":"fa32b979_0b3aece7","line":66,"in_reply_to":"fa32b979_6bd4d846","updated":"2015-06-19 18:37:43.000000000","message":"Yeah, The User ID in the Token needs to match the User ID Keystone gives us back when we ask for it. I think that\u0027s all part of the Keystone Tokenless Auth workflow. Its will be needed by anything using Tokenless Auth, not just this spec so I\u0027m not sure its important to explicitly mention it here. But I\u0027ll circle back with Keystone developers to ensure that info is passed correctly.","commit_id":"f46865dedb99eafc22db45b1a27e2a65e946b0c7"},{"author":{"_account_id":6488,"name":"Clint Byrum","email":"clint@fewbar.com","username":"clint-fewbar"},"change_message_id":"0e65dd9f061893a26f34955b02945fd4500deac8","unresolved":false,"context_lines":[{"line_number":50,"context_line":"certificate with the Instance UUID as an attribute. Keystone will be contacted"},{"line_number":51,"context_line":"with parameters based on cert data and Keystone returns the Keystone User ID"},{"line_number":52,"context_line":"for it. The Keystone User ID is stored in the Instance\u0027s metadata for retrieval"},{"line_number":53,"context_line":"by the user."},{"line_number":54,"context_line":"3. The metadata server api will be extended to provide a place to fetch the"},{"line_number":55,"context_line":"Instance User\u0027s certificate. The metadata server will fetch the Instances"},{"line_number":56,"context_line":"certificate from Barbican using its Instance ID. If the cert does not exist"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_34289396","line":53,"updated":"2015-06-25 16:49:53.000000000","message":"Forgive me if this has been asked before. Why don\u0027t you just do all of this from outside Nova before booting the instance, and use the name that you select, rather than the UUID, as the attribute? Then just put that in the boot requests\u0027s userdata. I don\u0027t see any reason this should be private inside Nova.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":6488,"name":"Clint Byrum","email":"clint@fewbar.com","username":"clint-fewbar"},"change_message_id":"db94042460e3e0f087a0cd05002bd4970bf1f017","unresolved":false,"context_lines":[{"line_number":50,"context_line":"certificate with the Instance UUID as an attribute. Keystone will be contacted"},{"line_number":51,"context_line":"with parameters based on cert data and Keystone returns the Keystone User ID"},{"line_number":52,"context_line":"for it. The Keystone User ID is stored in the Instance\u0027s metadata for retrieval"},{"line_number":53,"context_line":"by the user."},{"line_number":54,"context_line":"3. The metadata server api will be extended to provide a place to fetch the"},{"line_number":55,"context_line":"Instance User\u0027s certificate. The metadata server will fetch the Instances"},{"line_number":56,"context_line":"certificate from Barbican using its Instance ID. If the cert does not exist"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_49f01292","line":53,"in_reply_to":"fa32b979_179ea6b8","updated":"2015-06-25 22:09:58.000000000","message":"No I\u0027m addressing the authentication issue as well. Put a one time use key in the form of a URL in the userdata. Your window for compromise is the time between saying \"nova boot this\" and the time until the workload retrieves the one time key and feeds it back to the URL to get the real secrets. In that time, an attacker must MITM between the user and either of the services to intercept the key *and* spoof as the source IP nova gives the instance to retrieve the real secrets.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"28706d4bfa50119ce3d999b696cee74386555c9d","unresolved":false,"context_lines":[{"line_number":50,"context_line":"certificate with the Instance UUID as an attribute. Keystone will be contacted"},{"line_number":51,"context_line":"with parameters based on cert data and Keystone returns the Keystone User ID"},{"line_number":52,"context_line":"for it. The Keystone User ID is stored in the Instance\u0027s metadata for retrieval"},{"line_number":53,"context_line":"by the user."},{"line_number":54,"context_line":"3. The metadata server api will be extended to provide a place to fetch the"},{"line_number":55,"context_line":"Instance User\u0027s certificate. The metadata server will fetch the Instances"},{"line_number":56,"context_line":"certificate from Barbican using its Instance ID. If the cert does not exist"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_ff9e7868","line":53,"in_reply_to":"fa32b979_2c1b5c82","updated":"2015-06-25 23:07:48.000000000","message":"hmm... this still runs into the problem of needing a CA per tenant and registering them all with Keystone.\n\nAnd it also allows the users to create way more effective keystone users then the maximum number of vm\u0027s their quota allows them to launch, so they need some quotas on this other service as well....\n\nNo, I\u0027m back to thinking it should be part of nova because its way more complicated to not be in nova. :/","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"c15e05750df35400cc71a683410e5223ae968e84","unresolved":false,"context_lines":[{"line_number":50,"context_line":"certificate with the Instance UUID as an attribute. Keystone will be contacted"},{"line_number":51,"context_line":"with parameters based on cert data and Keystone returns the Keystone User ID"},{"line_number":52,"context_line":"for it. The Keystone User ID is stored in the Instance\u0027s metadata for retrieval"},{"line_number":53,"context_line":"by the user."},{"line_number":54,"context_line":"3. The metadata server api will be extended to provide a place to fetch the"},{"line_number":55,"context_line":"Instance User\u0027s certificate. The metadata server will fetch the Instances"},{"line_number":56,"context_line":"certificate from Barbican using its Instance ID. If the cert does not exist"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_179ea6b8","line":53,"in_reply_to":"fa32b979_31f09a91","updated":"2015-06-25 21:28:52.000000000","message":"I\u0027ll add that no storage requirement more clearly to the spec. Its only the most recent version of the spec that hasn\u0027t stored anything in nova so that part can indeed use some refinement. I\u0027ll add it asap.\n\nYour addressing the discovery issue without the authentication issue. I don\u0027t see a way to add it as an external micro service. how does the vm prove that it is who it says it is without getting some secret to it, to contact the microservice with? Your back to passing secrets through userdata. Nova is in the sweet spot because the metadata server has a trusted channel from nova to the vm, and so does nova to vm through config drive for authentication purposes. This spec relies on this authenticated channel being used to allow secrets not to need to be passed through nova metadata via the db.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"e651b070cd6a35f969f376ca79eb27d4b7c64371","unresolved":false,"context_lines":[{"line_number":50,"context_line":"certificate with the Instance UUID as an attribute. Keystone will be contacted"},{"line_number":51,"context_line":"with parameters based on cert data and Keystone returns the Keystone User ID"},{"line_number":52,"context_line":"for it. The Keystone User ID is stored in the Instance\u0027s metadata for retrieval"},{"line_number":53,"context_line":"by the user."},{"line_number":54,"context_line":"3. The metadata server api will be extended to provide a place to fetch the"},{"line_number":55,"context_line":"Instance User\u0027s certificate. The metadata server will fetch the Instances"},{"line_number":56,"context_line":"certificate from Barbican using its Instance ID. If the cert does not exist"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_a50f8838","line":53,"in_reply_to":"fa32b979_34289396","updated":"2015-06-25 19:24:20.000000000","message":"Its for the security chicken and the egg problem. How do you securely get a secret to the vm so it can get secrets securely from the secret storage service (Barbican).\n\nPutting the cert in the nova database through user-data is not a very good mechanism. Currently users have to put keystone usernames/passwords in userdata. this enters the nova db unencrypted and when the instance is deleted, those usernames/passwords continue on in the db since deletes are soft. Nova\u0027s DB then has a much bigger security target painted on it. Storing these secrets in the official OpenStack secret storage system is much preferred.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"51ce4d74ef29a2cc8fce3ec34039774237bce245","unresolved":false,"context_lines":[{"line_number":50,"context_line":"certificate with the Instance UUID as an attribute. Keystone will be contacted"},{"line_number":51,"context_line":"with parameters based on cert data and Keystone returns the Keystone User ID"},{"line_number":52,"context_line":"for it. The Keystone User ID is stored in the Instance\u0027s metadata for retrieval"},{"line_number":53,"context_line":"by the user."},{"line_number":54,"context_line":"3. The metadata server api will be extended to provide a place to fetch the"},{"line_number":55,"context_line":"Instance User\u0027s certificate. The metadata server will fetch the Instances"},{"line_number":56,"context_line":"certificate from Barbican using its Instance ID. If the cert does not exist"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_2c1b5c82","line":53,"in_reply_to":"fa32b979_49f01292","updated":"2015-06-25 22:51:55.000000000","message":"hmm... well, back when it was about never giving credentials to the vm\u0027s only keystone tokens, that wouldn\u0027t have worked. but since its now handing certs to the vm, I guess maybe we just extend barbican to support one time password retrieval of certs? Then like you said, nova doesn\u0027t have to deal with any of this process at all, and the cloud deployers don\u0027t have to deploy yet another service besides barbican.\n\nDouglas Mendizábal: what do you think of that idea?\n\nThere\u0027s been a lot of project A pushes all the work to project B, project B pushes all the work to project C, project C pushes all the work to project A going on here. It feels like we finally got Barbican and Keystone to agree (quite difficult) and Nova\u0027s now trying to get out of their part. We need to find a solution all 3 projects are comfortable supporting. Unfortunately I think the project silo\u0027s mean that politically viable is as much part of the solution as the technically viable part :/","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":6488,"name":"Clint Byrum","email":"clint@fewbar.com","username":"clint-fewbar"},"change_message_id":"bd29480f987ce836160ede512bdad1cddff23e5a","unresolved":false,"context_lines":[{"line_number":50,"context_line":"certificate with the Instance UUID as an attribute. Keystone will be contacted"},{"line_number":51,"context_line":"with parameters based on cert data and Keystone returns the Keystone User ID"},{"line_number":52,"context_line":"for it. The Keystone User ID is stored in the Instance\u0027s metadata for retrieval"},{"line_number":53,"context_line":"by the user."},{"line_number":54,"context_line":"3. The metadata server api will be extended to provide a place to fetch the"},{"line_number":55,"context_line":"Instance User\u0027s certificate. The metadata server will fetch the Instances"},{"line_number":56,"context_line":"certificate from Barbican using its Instance ID. If the cert does not exist"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_31f09a91","line":53,"in_reply_to":"fa32b979_a50f8838","updated":"2015-06-25 20:54:01.000000000","message":"Please make sure you state that nothing will be stored in Nova more clearly. That is _THE ONLY_ reason this can\u0027t be done with userdata alone.\n\nHowever, it is not a reason why it needs to be part of Nova. You can just as easily have this as a micro service which does everything you\u0027ve described in the spec, but in the end just feeds in a little piece of userdata that tells the instance \"go to this URL to fetch your secrets\". In fact, you could also just use DNSSEC and SRV records to do that, or DHCP options, or a host of other methods that _do not_ involve Nova and the metadata service. Once that\u0027s done, the service opens up Barbican ACLs to only allow that particular host to fetch those particular secrets one time, and then those secrets are never used again, as they basically just grant access to \"the real secrets\" which is the user. The consumer can just delete them from Barbican after fetching, and all is well.\n\nNova really does not need to be involved in this, and it will be _less_ work to make it into an external service, and less intrusive for deployers who don\u0027t choose to host any of the API\u0027s that make use of it.\n\nNow, I can see such a service having a similar relationship to Nova as Neutron and Cinder, with Nova eventually growing some flags to automatically make use of this service because users find it useful. But I do not believe this service should try and mature inside Nova, only to be moved out later. De-couple from day 1, and then your spec shrinks to \"Integrate Nova with Instance Users service\" and the few extra API bits. So for now you\u0027d have this on your heat/mistral/etc. side:\n\n    secrets_url\u003d$(instance-user-service create-instance-user)\n    instance_uuid\u003d$(nova boot --userdata\u003d$secrets_url)\n    instance-user-service set-instance-id $secrets_url $instance_uuid\n\nAnd then eventually, when you\u0027ve proven out this concept, you can ask Nova to just do that for you inside because it makes sense for a lot of users.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":6488,"name":"Clint Byrum","email":"clint@fewbar.com","username":"clint-fewbar"},"change_message_id":"0e65dd9f061893a26f34955b02945fd4500deac8","unresolved":false,"context_lines":[{"line_number":59,"context_line":"4. The metadata server api will be extended to provide a place to fetch"},{"line_number":60,"context_line":"minimal data about the cloud its running on so that the certificate can be"},{"line_number":61,"context_line":"used. This includes the Keystone URL and what Region the Instance is running"},{"line_number":62,"context_line":"in."},{"line_number":63,"context_line":"5. The server create api will be extended to support one new input."},{"line_number":64,"context_line":"createInstanceUser that synchronously calls function #2 and returns the"},{"line_number":65,"context_line":"Instance User ID as part of the response. This allows orchestration engines"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_af09ac2c","line":62,"updated":"2015-06-25 16:49:53.000000000","message":"Some people use configdrive. MANY people don\u0027t trust the metadata service for various reasons. Perhaps consider how that would affect the usefuleness of this plan?","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"e651b070cd6a35f969f376ca79eb27d4b7c64371","unresolved":false,"context_lines":[{"line_number":59,"context_line":"4. The metadata server api will be extended to provide a place to fetch"},{"line_number":60,"context_line":"minimal data about the cloud its running on so that the certificate can be"},{"line_number":61,"context_line":"used. This includes the Keystone URL and what Region the Instance is running"},{"line_number":62,"context_line":"in."},{"line_number":63,"context_line":"5. The server create api will be extended to support one new input."},{"line_number":64,"context_line":"createInstanceUser that synchronously calls function #2 and returns the"},{"line_number":65,"context_line":"Instance User ID as part of the response. This allows orchestration engines"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_c5464c7b","line":62,"in_reply_to":"fa32b979_254cd8c7","updated":"2015-06-25 19:24:20.000000000","message":"See line 91. Everything will show up in config drive.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"c15e05750df35400cc71a683410e5223ae968e84","unresolved":false,"context_lines":[{"line_number":59,"context_line":"4. The metadata server api will be extended to provide a place to fetch"},{"line_number":60,"context_line":"minimal data about the cloud its running on so that the certificate can be"},{"line_number":61,"context_line":"used. This includes the Keystone URL and what Region the Instance is running"},{"line_number":62,"context_line":"in."},{"line_number":63,"context_line":"5. The server create api will be extended to support one new input."},{"line_number":64,"context_line":"createInstanceUser that synchronously calls function #2 and returns the"},{"line_number":65,"context_line":"Instance User ID as part of the response. This allows orchestration engines"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_37b72a3c","line":62,"in_reply_to":"fa32b979_51719e43","updated":"2015-06-25 21:28:52.000000000","message":"Ah. Gotcha. I\u0027ll add it explicitly in the next version. Thanks.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"4829f0b415e96c6f521c0aee072a73845a08ef09","unresolved":false,"context_lines":[{"line_number":59,"context_line":"4. The metadata server api will be extended to provide a place to fetch"},{"line_number":60,"context_line":"minimal data about the cloud its running on so that the certificate can be"},{"line_number":61,"context_line":"used. This includes the Keystone URL and what Region the Instance is running"},{"line_number":62,"context_line":"in."},{"line_number":63,"context_line":"5. The server create api will be extended to support one new input."},{"line_number":64,"context_line":"createInstanceUser that synchronously calls function #2 and returns the"},{"line_number":65,"context_line":"Instance User ID as part of the response. This allows orchestration engines"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_254cd8c7","line":62,"in_reply_to":"fa32b979_af09ac2c","updated":"2015-06-25 19:01:31.000000000","message":"yup, any change that doesn\u0027t support config drive is bad.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":6488,"name":"Clint Byrum","email":"clint@fewbar.com","username":"clint-fewbar"},"change_message_id":"bd29480f987ce836160ede512bdad1cddff23e5a","unresolved":false,"context_lines":[{"line_number":59,"context_line":"4. The metadata server api will be extended to provide a place to fetch"},{"line_number":60,"context_line":"minimal data about the cloud its running on so that the certificate can be"},{"line_number":61,"context_line":"used. This includes the Keystone URL and what Region the Instance is running"},{"line_number":62,"context_line":"in."},{"line_number":63,"context_line":"5. The server create api will be extended to support one new input."},{"line_number":64,"context_line":"createInstanceUser that synchronously calls function #2 and returns the"},{"line_number":65,"context_line":"Instance User ID as part of the response. This allows orchestration engines"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_51719e43","line":62,"in_reply_to":"fa32b979_c5464c7b","updated":"2015-06-25 20:54:01.000000000","message":"The point is, don\u0027t leave config drive out here.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":6488,"name":"Clint Byrum","email":"clint@fewbar.com","username":"clint-fewbar"},"change_message_id":"0e65dd9f061893a26f34955b02945fd4500deac8","unresolved":false,"context_lines":[{"line_number":73,"context_line":"https://blueprints.launchpad.net/barbican/+spec/vm-integration"},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"The Barbican team has expressed its preference towards the instance-user spec"},{"line_number":76,"context_line":"over the vm-integration spec."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"Data model impact"},{"line_number":79,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_4f434042","line":76,"updated":"2015-06-25 16:49:53.000000000","message":"Consider adding the alternative I presented above to this section if there is some reason stated why that wouldn\u0027t work.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"4829f0b415e96c6f521c0aee072a73845a08ef09","unresolved":false,"context_lines":[{"line_number":73,"context_line":"https://blueprints.launchpad.net/barbican/+spec/vm-integration"},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"The Barbican team has expressed its preference towards the instance-user spec"},{"line_number":76,"context_line":"over the vm-integration spec."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"Data model impact"},{"line_number":79,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_a5cea82b","line":76,"in_reply_to":"fa32b979_4f434042","updated":"2015-06-25 19:01:31.000000000","message":"agreed.  The more we can reasonably do outside of nova the better IMHO.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"e651b070cd6a35f969f376ca79eb27d4b7c64371","unresolved":false,"context_lines":[{"line_number":73,"context_line":"https://blueprints.launchpad.net/barbican/+spec/vm-integration"},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"The Barbican team has expressed its preference towards the instance-user spec"},{"line_number":76,"context_line":"over the vm-integration spec."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"Data model impact"},{"line_number":79,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_e87fa767","line":76,"in_reply_to":"fa32b979_a5cea82b","updated":"2015-06-25 19:24:20.000000000","message":"It requires each tenant to have their own CA in Barbican, trusts to each CA be setup in Keystone, certs to be preallocated before the vm is launched, and the cert to be placed in userdata. Its a huge amount of manual work. Is that process good enough to be considered an alternate? From a Security/Usability perspective, I see it as a non option. If that\u0027s gotta happen, the whole spec should just be abandoned since Nova no longer needs to be in the mix at all.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":6488,"name":"Clint Byrum","email":"clint@fewbar.com","username":"clint-fewbar"},"change_message_id":"0e65dd9f061893a26f34955b02945fd4500deac8","unresolved":false,"context_lines":[{"line_number":78,"context_line":"Data model impact"},{"line_number":79,"context_line":"-----------------"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"None."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"REST API impact"},{"line_number":84,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_afa52c03","line":81,"updated":"2015-06-25 16:49:53.000000000","message":"If this is separate from userdata, as point 4 and 5 suggest above, wouldn\u0027t the data model require more fields for this new data?","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"e651b070cd6a35f969f376ca79eb27d4b7c64371","unresolved":false,"context_lines":[{"line_number":78,"context_line":"Data model impact"},{"line_number":79,"context_line":"-----------------"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"None."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"REST API impact"},{"line_number":84,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_c85ae3f2","line":81,"in_reply_to":"fa32b979_afa52c03","updated":"2015-06-25 19:24:20.000000000","message":"nova\u0027s essentially just relaying messages between barbican and keystone to setup the initial certificate. The database doesn\u0027t change at all in this iteration of the specification. Am I misunderstanding what the Data model section is about?","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":6488,"name":"Clint Byrum","email":"clint@fewbar.com","username":"clint-fewbar"},"change_message_id":"0e65dd9f061893a26f34955b02945fd4500deac8","unresolved":false,"context_lines":[{"line_number":120,"context_line":"returned Instance User ID to a Barbican Container ACL to enable the instance"},{"line_number":121,"context_line":"to access the secrets, and then trigger a SoftwareDeployment that depends on"},{"line_number":122,"context_line":"the ACL to inject code into the instance that will download the secret from"},{"line_number":123,"context_line":"Barbican using the new Nova metadata api and the Barbican api."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Security impact"},{"line_number":126,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_4fc6e09a","line":123,"updated":"2015-06-25 16:49:53.000000000","message":"So, with my proposal, just create an instance user in your domain, pass that user to barbican container acl, boot the instance with the user key in userdata, ... from there its basically the same.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":6488,"name":"Clint Byrum","email":"clint@fewbar.com","username":"clint-fewbar"},"change_message_id":"bd29480f987ce836160ede512bdad1cddff23e5a","unresolved":false,"context_lines":[{"line_number":120,"context_line":"returned Instance User ID to a Barbican Container ACL to enable the instance"},{"line_number":121,"context_line":"to access the secrets, and then trigger a SoftwareDeployment that depends on"},{"line_number":122,"context_line":"the ACL to inject code into the instance that will download the secret from"},{"line_number":123,"context_line":"Barbican using the new Nova metadata api and the Barbican api."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Security impact"},{"line_number":126,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_71706274","line":123,"in_reply_to":"fa32b979_082f6b3f","updated":"2015-06-25 20:54:01.000000000","message":"That does not mean you can\u0027t make a separate, outside of nova service that your policy-constrained cases can use to provide all of the things this spec proposes, but without Nova being involved at all.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"e651b070cd6a35f969f376ca79eb27d4b7c64371","unresolved":false,"context_lines":[{"line_number":120,"context_line":"returned Instance User ID to a Barbican Container ACL to enable the instance"},{"line_number":121,"context_line":"to access the secrets, and then trigger a SoftwareDeployment that depends on"},{"line_number":122,"context_line":"the ACL to inject code into the instance that will download the secret from"},{"line_number":123,"context_line":"Barbican using the new Nova metadata api and the Barbican api."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Security impact"},{"line_number":126,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_082f6b3f","line":123,"in_reply_to":"fa32b979_4fc6e09a","updated":"2015-06-25 19:24:20.000000000","message":"There are policy reasons at our and various other sites where domain\u0027s will not be given to projects. so allowing users to directly create other users is not an option. Instance users should not need that level of functionality though. See other comments on why I think passing secrets through userdata is bad.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"c15e05750df35400cc71a683410e5223ae968e84","unresolved":false,"context_lines":[{"line_number":120,"context_line":"returned Instance User ID to a Barbican Container ACL to enable the instance"},{"line_number":121,"context_line":"to access the secrets, and then trigger a SoftwareDeployment that depends on"},{"line_number":122,"context_line":"the ACL to inject code into the instance that will download the secret from"},{"line_number":123,"context_line":"Barbican using the new Nova metadata api and the Barbican api."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Security impact"},{"line_number":126,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_17854658","line":123,"in_reply_to":"fa32b979_71706274","updated":"2015-06-25 21:28:52.000000000","message":"If authentication to the microservice can be resolved, then this will work. but I don\u0027t see a way to do it.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":6488,"name":"Clint Byrum","email":"clint@fewbar.com","username":"clint-fewbar"},"change_message_id":"0e65dd9f061893a26f34955b02945fd4500deac8","unresolved":false,"context_lines":[{"line_number":138,"context_line":"storing it in those databases unencrypted and storing the password permanently"},{"line_number":139,"context_line":"in the Instance. With this change, all of those things are avoided. No one can"},{"line_number":140,"context_line":"login to the Instance and copy its credentials since it is never given direct"},{"line_number":141,"context_line":"access to them."},{"line_number":142,"context_line":""},{"line_number":143,"context_line":"Notifications impact"},{"line_number":144,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_cfb750d6","line":141,"updated":"2015-06-25 16:49:53.000000000","message":"This security enhancement lies in Keystone and Barbican, not in Nova. You can do the same thing without anything different in Nova.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"e651b070cd6a35f969f376ca79eb27d4b7c64371","unresolved":false,"context_lines":[{"line_number":138,"context_line":"storing it in those databases unencrypted and storing the password permanently"},{"line_number":139,"context_line":"in the Instance. With this change, all of those things are avoided. No one can"},{"line_number":140,"context_line":"login to the Instance and copy its credentials since it is never given direct"},{"line_number":141,"context_line":"access to them."},{"line_number":142,"context_line":""},{"line_number":143,"context_line":"Notifications impact"},{"line_number":144,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_a8a8bf8d","line":141,"in_reply_to":"fa32b979_cfb750d6","updated":"2015-06-25 19:24:20.000000000","message":"The security enhancement is related to Nova. IE, not using userdata for secrets.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":6488,"name":"Clint Byrum","email":"clint@fewbar.com","username":"clint-fewbar"},"change_message_id":"0e65dd9f061893a26f34955b02945fd4500deac8","unresolved":false,"context_lines":[{"line_number":163,"context_line":"---------------------"},{"line_number":164,"context_line":""},{"line_number":165,"context_line":"To enable the feature, a new Keystone Domain will need to be created by the"},{"line_number":166,"context_line":"deployer and passed in the config to Nova."},{"line_number":167,"context_line":""},{"line_number":168,"context_line":"Developer impact"},{"line_number":169,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_0fc21834","line":166,"updated":"2015-06-25 16:49:53.000000000","message":"And the deployer is required to have Barbican available.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"e651b070cd6a35f969f376ca79eb27d4b7c64371","unresolved":false,"context_lines":[{"line_number":163,"context_line":"---------------------"},{"line_number":164,"context_line":""},{"line_number":165,"context_line":"To enable the feature, a new Keystone Domain will need to be created by the"},{"line_number":166,"context_line":"deployer and passed in the config to Nova."},{"line_number":167,"context_line":""},{"line_number":168,"context_line":"Developer impact"},{"line_number":169,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_88905b50","line":166,"in_reply_to":"fa32b979_0fc21834","updated":"2015-06-25 19:24:20.000000000","message":"Good catch. thanks. This was a left over from before Barbican was made a requirement of the spec. I\u0027ll add it.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":1297,"name":"Joshua Harlow","email":"jxharlow@godaddy.com","username":"harlowja"},"change_message_id":"83cb7c87363241992c9385454a58cf3ea32fac22","unresolved":false,"context_lines":[{"line_number":192,"context_line":"None currently. More specs will be added in Barbican, Keystone, Keystone"},{"line_number":193,"context_line":"Client, Heat, Barbican, Barbican Client, OpenStackClient and Nova Client to"},{"line_number":194,"context_line":"make this feature truly useful to the community."},{"line_number":195,"context_line":""},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Testing"},{"line_number":198,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_cbe9191c","line":195,"updated":"2015-06-23 00:02:56.000000000","message":"Does cloud-init need anything to support this?","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"},{"author":{"_account_id":9237,"name":"Kevin Fox","email":"kevin@efox.cc","username":"kfox1111"},"change_message_id":"a81288cc924f01c2b10a1907873755f1d20e5f6a","unresolved":false,"context_lines":[{"line_number":192,"context_line":"None currently. More specs will be added in Barbican, Keystone, Keystone"},{"line_number":193,"context_line":"Client, Heat, Barbican, Barbican Client, OpenStackClient and Nova Client to"},{"line_number":194,"context_line":"make this feature truly useful to the community."},{"line_number":195,"context_line":""},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Testing"},{"line_number":198,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":10,"id":"fa32b979_eb15fd9a","line":195,"in_reply_to":"fa32b979_cbe9191c","updated":"2015-06-23 00:16:05.000000000","message":"It doesn\u0027t need to do anything to support it. The end user can use userdata executed through cloud-init to do the tasks it needs.\n\nThat being said, if cloud-init wanted to add additional helper support using this API for allowing, for example, the user to more easily fetch keys from Barbican, that would be great.","commit_id":"8d67ee580e39a62b249340d1f0d8846f786a768c"}],"specs/mitaka/approved/instance-users.rst":[{"author":{"_account_id":13997,"name":"SHIGEMATSU Mitsuhiro","email":"shigematsu.mitsuhiro@lab.ntt.co.jp","username":"pshige"},"change_message_id":"5a74c7c09e4606cd0e4ee034569d1242c221ad98","unresolved":false,"context_lines":[{"line_number":53,"context_line":"   time. (Can\u0027t refresh certificates before they expire)"},{"line_number":54,"context_line":" * Instances can be snapshotted. Secrets stored on the root drive will get"},{"line_number":55,"context_line":"   copied to new instances."},{"line_number":56,"context_line":" * Non root ephemeral drives arn\u0027t snapshotted."},{"line_number":57,"context_line":" * Heat would like to use Zaqar for its Guest Agent. This means Heat Software"},{"line_number":58,"context_line":"   Deployments can not be relied upon."},{"line_number":59,"context_line":" * While the Nova MD server is arguably secure for VM\u0027s, It is not for Bare"}],"source_content_type":"text/x-rst","patch_set":19,"id":"da20952f_de6cb038","line":56,"updated":"2015-09-02 06:04:26.000000000","message":"s/arn\u0027t/aren\u0027t/","commit_id":"fd044fc84cb32ee00a2b03b8bab322bf404a0059"}]}
